- ipv6-wg - mailman.ripe.net

[ipv6-wg@ripe.net] FW: [arin-council] IANA to RIR IPv6 Allocation
by Jeroen Massar 20 Aug '04

20 Aug '04

For people not on the arin-council (not likely ;) or the ppml@arin lists: -----Forwarded Message----- From: "Sweeting, John" <John.Sweeting(a)teleglobe.com> To: 'ppml(a)arin.net' <ppml(a)arin.net> Subject: [ppml] FW: [arin-council] IANA to RIR IPv6 Allocation Date: Thu, 19 Aug 2004 17:36:56 -0400 I am submitting the following proposal IAW ARIN's Internet Resource Policy Evaluation Process. In the interest of all I would like to disclose up front that the information used to prepare this template was provided by ARIN staff. ############################################ Template: ARIN-POLICY-PROPOSAL-TEMPLATE-1.0 1. Policy Proposal Name: Allocation of IPv6 Address Space by the Internet Assigned Numbers Authority (IANA) Policy to Regional Internet Registries 2. Author a. name: John Sweeting b. email: john.sweeting(a)teleglobe.com c. telephone: 703-766-3042 d. organization: ARIN Advisory Council 3. Proposal Version: 1 4. Submission Date: 8/17/04 5. Proposal type: new, global 6. Policy term: permanent 7. Policy statement: 1. Minimum Allocation Size. The minimum size of any allocation of IPv6 address space from IANA to an RIR is prefix length /12. If this address space is not sufficient to meet the needs of an RIR for a projected 18 month period, IANA shall allocate to that RIR the address space for which it can provide justification. 2. Reservation of Unicast Address space. 2.1 IANA. By RFC 3513 the IANA has been allocated the range of IPv6 addresses beginning at binary value 001 (prefix length /3) for its allocations of unicast address space. In order to support regional aggregation of IPv6 address space IANA shall establish a reservation of a prefix length of /6 from this space for each established RIR and for each emerging RIR. Allocations to each RIR will be from the appropriate reservation. 2.2. RIRs. Each RIR may apply its own respective chosen allocation and reservation strategy in order to meet the needs of its community and to ensure the efficiency and efficacy of its work. Such reservations made by an RIR will be considered as being allocated by that RIR when that RIR applies for an allocation of address space from the IANA. 3. Initial Allocation. 3.1. Upon implementation of this policy IANA shall allocate to each established RIR a /12 from the reservation established for each particular RIR. 3.2. Upon recognition of an RIR by ICANN that RIR shall receive a /12 from the reservation set aside for that RIR. 4. Subsequent Allocation. An RIR shall be eligible for an allocation of at least a minimal allocation from the IANA when its current holdings are less than 50% of its 18 month requirement or when it has less than 180 days of holdings available. The IANA shall evaluate the requested allocation using a set of administrative procedures that are mutually agreed to by the IANA and the NRO. This set of procedures shall be enacted within 30 days of the implentation of this policy. 5. Announcement of IANA allocations to the RIRs When address space is allocated to a RIR, the IANA will send a detailed announcement to the receiving RIR. The IANA will also make announcements to all other RIRs, informing them of the recent allocation. The IANA will make appropriate modifications to the "Internet Protocol V6 Address Space" page of the IANA website and may make announcements to only its own global announcement lists. The IANA announcements will be limited to which address ranges, the time of allocation and to which Registry they have been allocated. 8. Rationale: The current IANA allocation policy for IPv6 is an interim policy that was promulgated in 1999. Operational experience has demonstrated the current minimum allocation size is too small; that the built in reservation system that must be followed by the RIRs does not allow for efficient and effective management of the resource by the RIR; and does not provide for an well known evaluation criteria. This document does not stipulate performance requirements in the provision of services by IANA to an RIR in accordance with the policy. Such requirements should be specified by appropriate agreements between the NRO and ICANN. 9. Timetable for implementation: Thirty days after ratification by the ICANN Board of Directors in accordance with the global policy development process. 10. Meeting presenter: Elected AC Member or the President of ARIN. END OF TEMPLATE ################################################

4 5

[ipv6-wg@ripe.net] Re: 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
by Daniel Roesen 20 Aug '04

20 Aug '04

On Wed, Aug 04, 2004 at 03:59:35AM +0000, bmanning(a)vacation.karoshi.com wrote: > > So the whole delegation thing is broken. The int. TLD servers delegate > > ip6.int to imag.imag.fr which feels it self authoritative, but isn't > > in the NS RRset of the ip6.int zone. And ip6.int is delegated to > > munnari.oz.au which doesn't know about this (anymore). > > so... this was apparently enough to get the attention it > deserved. the long postponed migration from imag.imag.fr. > to ns3.nic.fr. is now "done" and imag.imag.fr. has been removed > from the NS list in the INT zone. > and munnari.oz.au has been removed. - more cleanup in the > next week or two. Well, two weeks down the road and things got even worse: NS list summary for ip6.int. from parent (int.) servers == flag.ep.net. ns3.nic.fr. y.ip6.int. == z.ip6.int. $ dig @flag.ep.net. int. SOA +norec | fgrep status: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9740 $ dig @ns3.nic.fr int. SOA +norec | fgrep status: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 334 $ dig @y.ip6.int int. SOA +norec | fgrep status: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17872 $ dig @z.ip6.int int. SOA +norec ;; connection timed out; no servers could be reached So we have 3 out of 4 servers totally broken. Looks like the importance of ip6.int is way overstated by some folks. Regards, Daniel

6 6

[ipv6-wg@ripe.net] RE: [sig-ipv6] Re: 9/9/2004 IP6.INT Removal (Was: 9/9/2006 :ip6.int shutdown?)
by Bound, Jim 20 Aug '04

20 Aug '04

> Can you identify those vendors which didn't react to a RFC > from 3 years ago? No that is up to those vendors product managers etc. What I know is from interoperability testing and cannot reveal. You missed mine and Bill's entire point. No one is against doing this it is a matter getting it into the production DNS code base. I think Bill should answer your other questions as you integrated my mail with Bill's. Your complaining here in IETF at least is irrelevant. And not the purpose of the IETF list IMO. I will not respond to other mail. If you want to discuss offline send me mail and I suggest you copy Bill. Ipv6.arpa is supported in the latest BIND releases and IMO all should be doing it, but I don't attribute it to being lazy at all. Again IPv6 is production code now vendors can't just change it as we do the public domain and university code base, it requires QA et al per the customer and that has cost and all changes to IPv6 at this point. /jim

2 1

[ipv6-wg@ripe.net] New IPv6 Address Block Allocated to RIPE NCC
by leo vegoda 18 Aug '04

18 Aug '04

Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:4600::/23 from the IANA in August 2004. You may want to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <https://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

[ipv6-wg@ripe.net] 2.0.0.2.ip6.arpa broken
by Daniel Roesen 17 Aug '04

17 Aug '04

On Sat, Aug 14, 2004 at 09:17:56AM +0100, David Malone wrote: > 2.0.0.2.ip6.int has become completely unavailable in the last few > days, resulting in delays for people connecting from 6to4 addresses > via ssh and the like. 2.0.0.2.ip6.arpa is also broken in all colors. soa @ns.apnic.net. for ip6.arpa. has serial: 2004071900 soa @ns.icann.org. for ip6.arpa. has serial: 2004071900 soa @ns-sec.ripe.net. for ip6.arpa. has serial: 2004071900 dig @tinnie.arin.net. for SOA of parent (ip6.arpa.) failed ==> tinnie.arin.net IPv6 connectivity is broken: $ dig @69.25.34.195 ip6.arpa. SOA +short dns1.icann.org. hostmaster.icann.org. 2004071900 3600 1800 604800 10800 $ dig @2001:440:2000:1::22 ip6.arpa. SOA ; <<>> DiG 9.2.3 <<>> @2001:440:2000:1::22 ip6.arpa. SOA ;; global options: printcmd ;; connection timed out; no servers could be reached Found 0 NS and 0 glue records for 2.0.0.2.ip6.arpa. @ns.apnic.net. (AUTH) Found 0 NS and 0 glue records for 2.0.0.2.ip6.arpa. @ns.icann.org. (AUTH) Found 4 NS and 4 glue records for 2.0.0.2.ip6.arpa. @ns-sec.ripe.net. (AUTH) DNServers for ip6.arpa. === 3 were also authoritatve for 2.0.0.2.ip6.arpa. === 0 were non-authoritative for 2.0.0.2.ip6.arpa. ERROR: Found 2 diff sets of NS records === from servers authoritative for 2.0.0.2.ip6.arpa. WARNING: ns.apnic.net. claims to be authoritative for 2.0.0.2.ip6.arpa. == but no NS record at parent zone WARNING: ns.icann.org. claims to be authoritative for 2.0.0.2.ip6.arpa. == but no NS record at parent zone WARNING: ns-sec.ripe.net. claims to be authoritative for 2.0.0.2.ip6.arpa. == but no NS record at parent zone ==> so although the three remaining NS for ip6.arpa have the same SOA serial, they obviously have a different view on the NS RRset for 2.0.0.2.ip6.arpa... and all are authoritative for 2.0.0.2.ip6.arpa. Now looking at the NS RRset ns-sec.ripe.net returns for 2.0.0.2.ip6.arpa: == ns-apnic.6to4.nro.net. ns-arin.6to4.nro.net. ns-lacnic.6to4.nro.net. == ns-ripe.6to4.nro.net. soa @ns-apnic.6to4.nro.net. for 2.0.0.2.ip6.arpa. serial: 2004072901 dig @ns-arin.6to4.nro.net. for SOA of 2.0.0.2.ip6.arpa. failed soa @ns-lacnic.6to4.nro.net. for 2.0.0.2.ip6.arpa. serial: 2004072901 soa @ns-ripe.6to4.nro.net. for 2.0.0.2.ip6.arpa. serial: 2004072901 ==> ns-arin.6to4.nro.net == tinnie.arin.net, so we have the same IPv6 reachability problem again What a mess all over... why do ns.apnic.net and ns.icann.org return NXDOMAIN when queried for the NS RRset for 2.0.0.2.ip6.arpa, but ns-sec.ripe.net returning one? It looks like the whole 2.0.0.2.ip6.arpa is missing in the ip6.arpa zone, and ns-sec.ripe.net is only by chance carrying the 2.0.0.2.ip6.arpa zone, thus returning the NS RRset. I wonder where's the right place to report such global (multi-RIR/org) DNS problems to, if not v6ops. I see no "global IPv6 operations" list, can anyone enlighten me? Best regards, Daniel

2 4

[ipv6-wg@ripe.net] Re: [address-policy-wg] Policy for allocation of IPv6 address space from IANA to RIRs
by Daniel Roesen 13 Aug '04

13 Aug '04

On Wed, Aug 11, 2004 at 09:04:21AM +0100, Jon Lawrence wrote: > Yes, doubling does seem unwise. > It would make sense (to me anyway) that once xx% of a /12 is allocated then > another /12 is issued to the RIR. Indeed. I see no point in unconditional doubling. I'm pretty confident that /12 blocks are large enough to serve a RIR long enough so that ordering a new /12 is not hampering anything. My suggestion would be to set aside a /8 per RIR (perhaps also a DNS reverse delegation for that) and allocate /12s to the RIRs upon their request. A RIR qualifies for a new /12 block as soon as nn% usage of the current /12 block is reached. nn might be 50% or more. As Randy suggests, the percentage should be low enough so that the RIRs can get new space without delaying allocation to LIRs (as it happens nowadays). Best regards, Daniel

3 2

[ipv6-wg@ripe.net] Policy for allocation of IPv6 address space from IANA to RIRs
by leo vegoda 10 Aug '04

10 Aug '04

Dear Colleagues, The Number Resource Organisation (NRO) has published a proposal for a policy for the allocation of IPv6 address space from the IANA to the RIRs. It is intended that this proposed policy should be agreed by all RIRs' open policy fora and then approved by the ASO and ICANN as a global policy. The proposal is available on our web site at: http://www.ripe.net/ripe/draft-documents/ipv6.html Comment on the proposal is sought. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC

9 15

[ipv6-wg@ripe.net] inet6num missing for allocation - more?
by Daniel Roesen 04 Aug '04

04 Aug '04

Hi, I've just noticed, that the allocation 2001:478::/32 is not registered in the RIPE DB: $ whois -h whois.ripe.net -r 2001:478::/32 | fgrep inet6num: inet6num: 0::/0 Could RIPE check wether this problem does exist for other allocations too? Or is EP.NET "special"? :-) Best regards, Daniel

2 2

RE: [ipv6-wg@ripe.net] inet6num missing for allocation - more?
by Wilfried Woeber, UniVie/ACOnet 04 Aug '04

04 Aug '04

>I've just noticed, that the allocation 2001:478::/32 is not registered >in the RIPE DB: But it is in ARIN's: > warin 2001:478:: OrgName: EP.NET, LLC. OrgID: V6EP Address: PO 12317 City: Marina del Rey StateProv: CA PostalCode: 90295 Country: US NetRange: 2001:0478:0000:0000:0000:0000:0000:0000 - 2001:0478:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF CIDR: 2001:0478:0000:0000:0000:0000:0000:0000/32 NetName: EP-NET NetHandle: EP-NET-NET Parent: ARIN-001-NET NetType: Direct Allocation NameServer: FLAG.EP.NET NameServer: Z.IP6.INT Comment: RegDate: 2001-05-21 Updated: 2002-08-05 TechHandle: WM110-ARIN TechName: Manning, Bill TechPhone: +1-310-322-8102 TechEmail: bmanning(a)karoshi.com > ... Or is EP.NET "special"? :-) Who knows :-) >Best regards, >Daniel Wilfried ( https://cert.aco.net/ ) _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

[ipv6-wg@ripe.net] RE: [sig-ipv6] Re: 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
by Bound, Jim 31 Jul '04

31 Jul '04

Thank you. /jim > -----Original Message----- > From: bmanning(a)vacation.karoshi.com > [mailto:bmanning@vacation.karoshi.com] > Sent: Wednesday, July 28, 2004 7:20 AM > To: Bound, Jim > Cc: bmanning(a)vacation.karoshi.com; Jeroen Massar; Anand > Kumria; Rob Blokzijl; v6ops(a)ops.ietf.org; sig-ipv6(a)apnic.net; > ipv6-wg(a)ripe.net > Subject: Re: [sig-ipv6] Re: 9/9/2004 IP6.INT Removal (Was: > 9/9/2006 : ip6.int shutdown?) > > > both ip6.arpa and ip6.int > > --bill > > > > > P.S. Bill - the new initial IPv6 AAA at root for JP and KR > are they to > > use ipv6.arpa? Thanks. > > > > /jim > > > > > > > > > -----Original Message----- > > > From: owner-v6ops(a)ops.ietf.org > > > [mailto:owner-v6ops@ops.ietf.org] On Behalf Of > > > bmanning(a)vacation.karoshi.com > > > Sent: Sunday, July 25, 2004 5:45 PM > > > To: Jeroen Massar > > > Cc: Anand Kumria; Rob Blokzijl; v6ops(a)ops.ietf.org; > > > sig-ipv6(a)apnic.net; ipv6-wg(a)ripe.net > > > Subject: Re: [sig-ipv6] Re: 9/9/2004 IP6.INT Removal (Was: > > > 9/9/2006 : ip6.int shutdown?) > > > > > > > > > whjile i applaud each and everyone who has expunged > > > all ip6.int from their lives, the fact of the matter is that > > > IETF fiat or no, there exist -many- systems that can only use > > > reverse maps in the ip6.int tree. > > > > > > it will be maintained as long as there are queries for > > > it. for those of you for whom ip6.int is a distant memory, > > > pleae understand and respect the fact that you can not, > > > despite public posturing, force others to change their > > > systems. to practically remove ip6.int incures real cost > > > in both time and cash. in the US there is a term for what > > > the IETF is trying to do w/ ip6.int. Its called an unfunded > > > mandate. Unless or until the good folk in the IETF who are > > > calling for the removal of ip6.int are ready to put up the > > > cash to effect real change, I wish they would stop. > > > > > > > > > > > > On Thu, 2004-07-22 at 09:58, Kurt Erik Lindqvist wrote: > > > > > > > > > > > > > On 2004-07-22, at 09.43, Jeroen Massar wrote: > > > > > > > > > > > > > > > But indeed, if there is concensus or not 9/9/2004 > > > and ip6.int > > > > > > > > is gone for me. > > > > > > > > > > > > > > I vote for 9/9/2004 and getting rid of it properly. > > > Maintaining > > > > > > > two reverse threes will create more problems than it > > > will solve. > > > > > > > > > > What, specifically, is the hurry? > > > > > > > > That this has been overdue for three years already and > that even > > > > though the deprecation was marked in August 2001 some vendors > > > > still not have done the change. And as it is a > > > s/ip6.int/ip6.arpa/g which is > > > > very easy, if vendors did not do that yet they are way > > > overdue and you > > > > got to wonder how much their interest is in keeping > > > software upto date. > > > > > > > > Basically we (at least me) have been waiting for the 6bone > > > to get the > > > > delegation so that we could remove the 2 trees and only > keep one: > > > > ip6.arpa. This was decided by the IAB thus we should > live up to it. > > > > > > > > If we do not remove ip6.int then still implementations > > > using it will > > > > not show up. They have had 3 years already to update... > > > > > > > > > > Take your pick: > > > > > > > > > > > > > > > http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int- > > > > > > removal-00.html > > > > > > > > > http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int- > > > > > > removal-00.txt > > > > > > > > > http://unfix.org/~jeroen/archive/drafts/draft-massar-v6ops-ip6int- > > > > > > removal-00.xml > > > > > > > > > > > > Short, quick and easy. > > > > > > If no comments are risen for 16:00 today I'll submit > > > this as an ID. > > > > > > > > > > Comments: > > > > > e.f.f.3.ip6.arpa was documented in RFC3681 > published in February > > > > > 2004 and actioned in July 2004. > > > > > > > > Added, but note that this was all long overdue and > there where a > > > > number of other solutions that would have worked already 2 > > > years ago > > > > if there had not been any of the political arguments > > > holding back this > > > > technical issue. Note also that 6bone will end per 6/6/6 > > > and that it is a TESTbed. > > > > The TESTbed is delaying and thus hurting the production > networks > > > > in this case. > > > > > > > > > I'm assuming the actioning of e.f.f.3.ip6.arpa > is the trigger > > > > > for this I-D; if so, why do you want to wait so > little time (2 > > > > > months) between e.f.f.3.ip6.arpa becoming available and > > > > > requiring people to have updated resolver libraries? > > > > > > > > People should have updated their resolvers in the last > *3 years*. > > > > If you have not done that already then you are not maintaining > > > > your machines properly and there is a big chance that you have > > > > bigger problems than a IPv6 reverse DNS that doesn't > work anymore > > > > because ip6.int is gone. > > > > > > > > > Personally I'd be more in favour of a 6 month > timeout - i.e > > > > > around last December or so. > > > > > > > > Of course the date is up to discussion, but IMHO: ASAP and at > > > > least before the end of the year, the sooner the better. > > > > > > > > Note that Cisco's IOS updates will be done before that date and > > > > Windows > > > > XP2 will come out in August (they say) thus everybody using > > > IPv6 has > > > > time enough to upgrade. All "free unix flavors" already > support it > > > > > > > > Also users agree: http://www.sixxs.net/forum/?msg=general-83948 > > > > Note the begin date of that thread, we where really waiting > > > for 6bone > > > > just as being nice to the people still using it. > > > > > > > > On Thu, 2004-07-22 at 10:57, Rob Blokzijl wrote: > > > > > > > > > > If no comments are risen for 16:00 today I'll submit > > > this as an ID. > > > > > > > > > > two minor points. In the abstract and the > > > introduction you write: > > > > > > > > > > RFC 3152 delegates IP6.ARPA for reverse IPv6 > > > delegations. For RIRs > > > > > (RIPE,ARIN,APNIC,LACNIC and soon AFNIC) > > > > > > > > > > Replace RIPE --> RIPE NCC > > > > > > > > That I did that wrong is a major oops, I should by know the > > > difference by now. > > > > > > > > > Replace AFNIC --> AFRINIC > > > > > > > > > > (AFNIC is the .fr registry :-) ) > > > > > > > > Also adjusted and added some xref's in the XML. > > > > > > > > Old version is now draft-massar-v6ops-ip6int-removal-00.a > > > new version > > > > carries the draft-massar-v6ops-ip6int-removal-00 name. > > > > > > > > Greets, > > > > Jeroen > > > > > > > > > > > > > > > > > * sig-ipv6: APNIC SIG on IPv6 technology and > > > policy issues * > > > > _______________________________________________ > > > > sig-ipv6 mailing list > > > > sig-ipv6(a)lists.apnic.net > > > > http://mailman.apnic.net/mailman/listinfo/sig-ipv6 > > > > > > > > > >

1 0