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/2006 : ip6.int shutdown?
- Previous message (by thread): [ipv6-wg at ripe.net] 9/9/2006 : ip6.int shutdown?
- Next message (by thread): [ipv6-wg at ripe.net] 9/9/2006 : ip6.int shutdown?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Thu Jul 22 12:04:44 CEST 2004
On 22-jul-04, at 11:46, Gert Doering wrote: >> In fact, it would >> probably be a good idea to keep ip6.int around forever. If nobody uses >> it, there is no harm in it being there. If people still use it, then >> removing it causes problems. > Maintaining both trees does cause quite some administrative overhead > (depending on the name server software and zone file format you use, > you > cannot just point both zones to the same file. Then you probably also use an OS that doesn't support file system links? :-) The way I understand it, it's even possible to use the dname mechanism to fix all of this, so this argument isn't all that convincing. But even if: > Even if you can, the > whole thing falls apart if you want to delegate a /48 to your customer, > and the customer has only ip6.arpa, but not ip6.int -> lame delegation, > or distinct zone files further up the tree). I'm not arguing EVERYONE should continue to support ip6.int forever, just that the delegations to those who still do should remain in place. If you feel you shouldn't support ip6.int in your network, by all means, remove it.
- Previous message (by thread): [ipv6-wg at ripe.net] 9/9/2006 : ip6.int shutdown?
- Next message (by thread): [ipv6-wg at ripe.net] 9/9/2006 : ip6.int shutdown?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]