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/[email protected]/
[ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
- Previous message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
- Next message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Erik Lindqvist
kurtis at kurtis.pp.se
Thu Jul 22 12:35:02 CEST 2004
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrei, > IP6.INT Phaseout Plan > > To deprecate usage of IP6.INT tree for reverse DNS and enable smooth > transition to IP6.ARPA a process with 3 milestones is proposed: > > > Milestone 1. Stop creating new and modifying existing delegations in > IP6.INT tree. > > Starting from January 1, 2005 new delegations SHOULD NOT be created > and > existing resource records will be modified. This applies to the > IP6.INT zone itself as well as to all child zones down the tree. I can see that removing the ip6.int delegation by 9/9/2004 would be considered agressive. But continuing to populating something that has been deprecated for another 6 months after there is an alternative doesn't make sense to me. I would assume this date to be ASAP. > Milestone 2. Remove all existing delegations from the IP6.INT tree. > > Starting from June 6, 2006, all delegations will be deleted from the > IP6.INT zone and its child zones down the tree. This will > effectively > obsolete IP6.INT reverse delegation tree. > > > Milestone 3. Remove IP6 delegation from the "INT" gTLD. > > Recommend to the IETF to direct IANA to remove the delegation of the > obsolete "IP6" child zone from the "INT" gTLD. Since Milestone 2 > effectively > obsoletes IP6.INT zone this can be done at the same time, on June 6, > 2006. While 9/9/2004 might be optimistic, just as Iljitsch points out, we will not have a RFC by then, June 6th 2006 seems to far away for me. End of the year or mid 2005 by the latest seems more realistic. - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQP+YWqarNKXTPFCVEQJkqgCgounFuCktIjrjdhL8Gts0RFLQEaoAn2a6 hyzq7sTzmdbDxyEJYf81JZlV =pUeg -----END PGP SIGNATURE-----
- Previous message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
- Next message (by thread): [ipv6-wg at ripe.net] 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]