April 2003 - ipv6-wg - mailman.ripe.net

[ipv6-wg@ripe.net] ipv6 address format
by Jeroen Valcke 09 Apr '03

09 Apr '03

Hello, I'm in the process of reviving ipv6 on our network. I'm new to IPv6 so this questions is perhaps obvious. I found an old company document which lists the following format for an IPv6 address. | 16 | 19 | 13 | 16 | 64 bits | +-+---------+------+-----------+--------+-----------------+ | 0x2001 | sTLA | NLA | SLA ID | Interface ID | +-+---------+------+-----------+--------+-----------------+ I'm confused here, reading RFC2373 I found the folowing format |3| 13 | 8 | 24 | 16 | 64 bits | +-+---------+-----+------------+--------+-----------------+ | | TLA ID | RES | NLA ID | SLA ID | Interface ID | +-+---------+-----+------------+--------+-----------------+ Hmmm, what's wrong. -Jeroen- -- Jeroen Valcke sst(a)belnet.be jeroen.valcke(a)belnet.be

3 2

[ipv6-wg@ripe.net] Reverse delegation for 6bone address space in ip6.arpa
by Andrei Robachevsky 04 Apr '03

04 Apr '03

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.

2 2

[ipv6-wg@ripe.net] Experimental IPv6 address allocations policy
by Pekka Savola 04 Apr '03

04 Apr '03

Hi, I just recently noted that experimental IPv6 address allocations have been "sneaked in" the policy, as seen in: http://www.ripe.net/ripe/docs/ipv6policy.html#experiment-assignments I must heavily object to this for a few reasons: 1) the intent is to keep the policy uniform, and this has not been discussed in the global-v6 policy mailing list. 2) RIPE43 minutes (posted on Oct 19 2002) list that this should be turned into a draft proposal [note: the URL for the presentation does not work]; There was a draft proposal on 28 Nov 2002 on "DRAFT: Experimental Internet Resource Allocations & Assignments". This is no longer available so I cannot verify the contents. 3) On 22 Jan 2003, new RIPE documents, 263 and 267 are available; these incorporate an experimental addressing policy. To my knowledge and according to my mail archives, neither of these has *ever* been as much as mentioned in the mailing lists (either ipv6 or lir wg) - not a single message. Is this sufficient in determining this is really what community wants? To clarify, are only those organizations which meet the criteria in section 5.1.1 applicable for experimental address allocations in: http://www.ripe.net/ripe/docs/ipv6policy.html#experiment-assignments ? If the others can get experimental blocks, I'd be very much against it. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

3 2