Sounds like a good idea to me. Ray
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Jeroen Massar Sent: Tuesday, July 20, 2004 7:54 AM To: ipv6-wg@ripe.net Subject: [ipv6-wg@ripe.net] 9/9/2006 : ip6.int shutdown?
Hi,
As e.f.f.3.ip6.arpa has finally been delegated and works as of today I want to propose the end-day for ip6.int.
ip6.int has been deprecated in favor of ip6.arpa for almost 3 years already (RFC3152 dates August 2001) thus it is time to clean up the mess. Vendors have been able to update their stacks for almost 3 years, ip6.arpa has been deployed on production (read RIR) IPv6 space already for quite some time too. Thus now, with 6bone also having a working ip6.arpa tree this seems to be a perfect opportunity to start shutting down ip6.int.
At the moment only Cisco IOS and Windows XP don't have ip6.arpa support, but IOS has been addressed (they say) and Windows XP will be fixed with SP2 due out per August. As neither of these are server OS's this doesn't pose much of a problem anyway. People using IPv6 need to keep their systems up-to-date anyways.
I propose that RIPE, and actually any other RIR, stops any delegations for ip6.int per 9/9/2006. Which is more than 3 years after the RFC has been released.
Greets, Jeroen