[ipv6-wg@ripe.net] Reverse delegation for 6bone address space in ip6.arpa
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.
Dear diary, on Fri, Jan 10, 2003 at 12:39:47PM CET, I got a letter, where Andrei Robachevsky <andrei@ripe.net> told me, that...
Dear Colleagues,
Hello,
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.
yet another month passed already so I would like to ask again about progress of this issue. I can already see something living in e.f.f.3.ip6.arpa., but there are no hints available about status of these delegations etc. There are rumours in the community that some (non-RIR) people are blocking an establishment of the domain, thus I (and others as well, presumably) would welcome some statement about this. Thanks in advance, -- Petr "Pasky" Baudis . "A computer is a state machine. Threads are for people who can't program state machines." -- Alan Cox . Crap: http://pasky.ji.cz/
Dear all, As many of you already know after discussions between the 6bone and the RIR communities it was agreed at the San Francisco IETF meeting in March 2003 that it was more practical for the 6bone to provide this service for itself. For more detailed information please see a recently published draft http://www.ietf.org/internet-drafts/draft-ymbk-6bone-arpa-delegation-01.txt Regards, Andrei Robachevsky CTO, RIPE NCC
participants (2)
-
Andrei Robachevsky -
Petr Baudis