Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

[Doug Barton <[e-mail]>]

On 02/15/2011 20:17, Jay Ashworth wrote:
> And, as has been pointed out in some other venues, and which seems
> applicable here also, some approachs to certain things *depend on trying
> a DNS lookup and having it break*.  I'm damned if I can remember what
> the canonical example was, but it fell in the general category of
> "please don't make this change to try to 'help' 'the web', cause you'll
> break*my*  protocol which isn't http".

It would be really great if we could find a pointer to that discussion, 
since some of us are still working on trying to solve the problem and 
would prefer not to make things worse. :)

Meanwhile I'm concerned about what seems to be a thread of "We can't 
work to solve the DNS part of this problem because solving the DNS part 
won't solve the whole problem." *If* we can solve the DNS part of the 
problem now there are solutions available now for all the other problems 
that people have mentioned so far, even if they are potentially onerous 
(such as acquiring SSL certs for all variants, etc.). But without a 
solution for the DNS part of the problem it's going to be awfully hard 
to move forward in the other areas.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/

_______________________________________________
dnsext mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dnsext