Re: draft-ymbk-6to4-arpa-delegation-00.txt
Pekka Savola <pekkas@netcore.fi> Sun, 17 November 2002 21:55 UTC
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26192 for <dnsop-archive@lists.ietf.org>; Sun, 17 Nov 2002 16:55:10 -0500 (EST)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.5/8.12.5) with ESMTP id gAHLZdcE023378 for <dnsop-outgoing@nic.cafax.se>; Sun, 17 Nov 2002 22:35:39 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.5/8.12.5/Submit) id gAHLZdkG023377 for dnsop-outgoing; Sun, 17 Nov 2002 22:35:39 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from netcore.fi (netcore.fi [193.94.160.1]) by nic.cafax.se (8.12.5/8.12.5) with ESMTP id gAHLZXcE023372 for <dnsop@cafax.se>; Sun, 17 Nov 2002 22:35:34 +0100 (MET)
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id gAHLZS111441; Sun, 17 Nov 2002 23:35:28 +0200
Date: Sun, 17 Nov 2002 23:35:27 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Alain Durand <Alain.Durand@sun.com>
cc: Randy Bush <randy@psg.com>, dns op wg <dnsop@cafax.se>
Subject: Re: draft-ymbk-6to4-arpa-delegation-00.txt
In-Reply-To: <3DD03221.7080207@sun.com>
Message-ID: <Pine.LNX.4.44.0211172332130.11375-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-dnsop@cafax.se
Precedence: bulk
On Mon, 11 Nov 2002, Alain Durand wrote: > >[ v6ops removed from cc: ] > > > > > > > >>I have some comments about section 3.1 "6to4 NS records derived > >>from IPv4 NS records" when 6to4 is deployed by end users. > >>Who is going to get the delegation: the ISP or the end customers? > >> > >> > > > >as far down the tree as it can go. and note that the current > >version > > <http://psg.com/~randy/draft-ymbk-6to4-arpa-delegation-00.html> > >makes this a bit clearer. > > > > > > Under the described method, the holders of IPv4 address space can > request the delegation > > of a sub-zone in the 2.0.0.2.ip6.arpa DNS tree to the parties from > which they obtained > > that IPv4 address space, following the mapping of IPv4 delegations. > > This sub-zone can then be populated by the entity deploying the 6to4 > infrastructure. > > > ==> This last sentence is where the problem is. > The "entity deploying the 6to4 infrastructure" is not necessarily > the one who manages the delegation. See my previous example > of end-user customer. Totally agree. Therefore depending on the full v4 delegation path would appear to be useless (and even worse -- if there are only 0.01% of sites where actually any records will be found). More analysis is needed before going down this path.. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Alain Durand
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Alain Durand
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Randy Bush
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Alain Durand
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Pekka Savola
- draft-ymbk-6to4-arpa-delegation-00.txt Randy Bush
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Pekka Savola
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Brad Knowles
- Re: draft-ymbk-6to4-arpa-delegation-00.txt Pekka Savola