davePremium,MVM
join:2000-05-04
not in ohio
kudos:7 Reviews:
 ·Verizon FiOS
 ·Verizon Online DSL
1 edit | reply to Skippy25
Re: Who Cares? said by Skippy25:Does a redirection even affect applications outside of HTTP request (mail appears to work one user said)? What is stopping innovation from going to only HTTP being affected? Oh that's right.... it's been like that for the 20 years you know of so why move on. It's DNS. DNS has nothing to do with HTTP. You can't tell from a DNS query that the application intends to talk HTTP. That's the whole problem.
You're framing this as me being 'against innovation', but my argument is that they shouldn't break a basic Internet protocol just to benefit web users. If it could be confined to web users, that would be more-or-less ok. But the protocol does not carry enough information for anyone to make that distinction.
said by Skippy25:DNS is not perfect, maybe determining the type of name request would be an improvement. Yes, that's the sort of innovation that would actually make some sense.
As it stands, DNS mostly resolves 'network layer' names - you get an IP address (MX would seem to be an exception).
What a service like this needs is to handle 'transport layer' names (mapping to IP address, protocol, port number). Given such an arrangement, you could reply with the address of a web server if it was a name lookup from a web app, or with 'no such name' if it was one of these protocols that I'm more worried about.
The trouble is, that requires client code. As such, it's hard to unilaterally declare you've got a new service. You need to either write code for all clients, or persuade client implementors that you're on to a good thing. (This last is what the Internet RFC mechanism is all about). |
