This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
- Previous message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
- Next message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Massar
jeroen at unfix.org
Wed Mar 15 11:17:03 CET 2006
On Tue, 2006-03-14 at 19:02 -1000, Randy Bush wrote: > > now if the IETF & the RIRs could just get rid of all that > > deployed resolver code that looks for ip6.int by fiat. > > actually, i think it was kazu yamamoto who just gave a good > analysis of why this is really not going to cause significant > issues. I don't know what Kazu San said about it, but one of the main reasons being that the roots will from 1/6/2006 nicely return NXDOMAIN and the resolver code won't try any further. Indeed the application won't get a reverse, but hell, they should upgrade then. Too bad that the nice ip6.int private domain is going away for the people running it though. But experimentation has to end at a certain point, now lets go to production ;) Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 242 bytes Desc: This is a digitally signed message part URL: </ripe/mail/archives/dns-wg/attachments/20060315/54dc8eda/attachment.sig>
- Previous message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
- Next message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]