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 ]
Iljitsch van Beijnum
iljitsch at muada.com
Thu Jul 22 11:59:06 CEST 2004
On 22-jul-04, at 10:56, Pim van Pelt wrote: > http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int- > removal-00.html > | Short, quick and easy. Can't argue with that. :-) > I for one do not see the need to kill ip6.int 'per se' in 2004. I would > think that the 6bone removal date in 2006 is more realistic. I don't see any benefits to removing the ip6.int delegation in the first place. It makes much more sense to do this from the leaves up than from the root down. However, if this is going to happen, doing it this year is way too soon, as current IOS and Windows XP (both in wide use) rely on ip6.int. Newer versions that support ip6.arpa should be available for at least a year prior to removing ip6.int, in my opinion. So that would probably land us somewhere near 6/6/6, although there is of course no relation to the 6bone sunset. I also think expecting this to be published as an RFC by 9/9/4 is highly optimistic. :-)
- 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 ]