[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: ggm@apnic.net
Cc: dnsop@cafax.se
From: Alain Durand <Alain.Durand@Sun.COM>
Date: Thu, 27 Jun 2002 17:08:35 -0700
In-reply-to: <3199.1025256060@garlic.apnic.net>
Sender: owner-dnsop@cafax.se
Subject: Re: draft-durand-ngtrans-dns-issues-00.txt

On Friday, June 28, 2002, at 02:21 AM, ggm@apnic.net wrote:

I don't understand why you say 6to4 use of 2.0.0.2.ip6.arpa has scaling
problems.

There was a brief discussion in the corridor at NANOG-Toronto, and as
far as I can see, it should be easy to manage the reverse tree for existing
IPv4 users by forseeable RIR processes when the time comes.

Can you please elaborate how this will work?
Will it require collaboration from the IPv4 upstream provider?
(i.e. will the delegation under the 2.0.0.2.ip6.arpa follow the same
path as under in-addr.arpa?
Another way to ask the question is where will 6to4 users have
to go to get reverse delegation? to their ISP or directly to the RIR?

How will it work when the IPv4 address is transient, i.e. DHCP allocated
for a short lease (typically less than a day)?



You also don't say anything about ip6.int to ip6.arpa transition. Since
its now deprecated, it might be a good idea to address what happens during
the transition window (ie while vendors don't yet have resolvers doing
an initial lookup in ip6.arpa, failing over to ip6.int before returning null)

good point, I will add a section about this in the next revision.

- Alain.


Home | Date list | Subject list