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/ipv6-wg@ripe.net/
[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 ]
Christian Schild
join at uni-muenster.de
Thu Jul 22 13:12:02 CEST 2004
Am Do, den 22.07.2004 schrieb Daniel Roesen um 12:59: > On Thu, Jul 22, 2004 at 12:35:02PM +0200, Kurt Erik Lindqvist wrote: > > 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. > > Agreed. The period of coexistence of both trees should be kept as short > as possible to avoid confusion and fostering lazyness. Half a year is > more than enough to get delegations in ip6.arpa done. I think the problem is not populating the new tree, but the resolvers that try to query a reverse address. E.g. standard Fedora Core 1 (which is not so old) still tries to query in ip6.int. It will take some time to get rid of the "ancient" operating systems and as long as they exist, ip6.int. might be necessary. Christian
- 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 ]