[6bone] DNS support for IPv6

[Christian Nickel]

Hi,


> > > > Currently you can use both ip6.int and ip6.arpa with 3ffe::/16 and 2001::/16,
> > > > but ip6.arpa should be preferred.
> > > 
> > > That's just a tad bit misleading.  You *can*, sure; but there is no
> > > reverse delegation for 3ffe::/16 under ip6.arpa, only ip6.int.
> > 
> > Aaron thats not correct there is an ip6.arpa reverse delegation for 3ffe::/16!
> 
> Really?  When did this happen?  ::is clueless::


since January 2003


> Dear Colleagues,
>
> In accordance with RFC 3152, the administration of the name space within
> ip6.arpa has been delegated to the RIRs. The 3FFE::/16 address space has 
> Not yet been allocated to the RIRs by the IANA. It is the intention that 
> the RIRs administer this space. The community has expressed a need for 
> 3FFE reverse space to be in the ip6.arpa domain. The RIR CEOs sent a 
> message to the IAB requesting a waiver regarding the RFC 3152 
> requirement and received a positive response. The RIRs are prepared to 
> administer e.f.f.3.ip6.arpa domain in the manner as described below.
>
> We plan to implement it in the next few weeks and deliver the solution 
> soon after the RIPE 44 Meeting in January.
>
> Regards,
>
> Andrei Robachevsky
> CTO, RIPE NCC 
>
>
> Support for reverse delegation for 6bone address space in ip6.arpa DNS tree
> ---------------------------------------------------------------------------
>
> Phase I. Before a final decision is made on future management of the 
> 3FFE address space
>
> The delegation for e.f.f.3.ip6.arpa is made by IANA to one of the RIRs. 
> Zone information for this space is produced by copying the existing 
> delegations in the e.f.f.3.ip6.int zone. Additional check is done to 
> ensure that the servers corresponding to the NS RR are also 
> authoritative in .arpa space. Zone information is updated whenever 
> changes are detected in the e.f.f.3.ip6.int zone.
>
> This approach has a couple of advantages. It keeps the RIRs out of the 
> 6bone registration process until a final decision is made on future 
> management of the 3FFE address space. It also implies no procedural 
> changes from a user's perspective since changes are made in only one 
> place, while at the same time it moves responsibility for maintaining 
> the e.f.f.3.ip6.arpa zone to the RIRs. This then prepares for a smoother 
> transition to Phase II.
>
> The main constraint of this approach is that it forces registrants to 
> use the same name servers for .arpa as for .int.
>
>
> Phase II. Registration of 3FFE space is transferred to the RIRs
>
> A shared zone management process will be implemented similar to that
> currently implemented by the RIRs for the legacy v4 space (ERX project,
> http://www.ripe.net/db/erx/). That is, holders of 6bone address space 
> will be served for reverse delegation by the respective RIR in their 
> region, and the generation of the e.f.f.3.ip6.arpa zone can be entirely 
> automated using zone merging.


Greets,
 Christian

------------------------------------------
TDOI Network | www.tdoi.org | noc@tdoi.org