November 2003 - address-policy-wg

FORMAL PROPOSAL: change of initial PA allocation size
by Gert Doering 23 Dec '03

23 Dec '03

Hi, this was discussed on the list before the last RIPE meeting, and we had it on the address policy working group meeting (presented by me). I think we mostly have consensus on this issue, but I want to present it as a formal proposal, before it's incorporated into the policy. PROPOSAL: * the minimum initial allocation size (for new LIRs) is reduced from a /20, as of today, to a /21. (If a new LIR can demonstrate need for a bigger initial allocation, they can get a larger address block. This will not be changed). * the requirement to show an immediate need for 25% of the allocated address space is removed for the "minimum initial allocation" The motivation for that is that under the current policy, startup LIRs that do not already hold address space cannot get an initial PA allocation (which would be a /20 as of today, or bigger), because in many cases, they cannot demonstrate immediate need, or prior utilization of sufficient address space. To work around this, many startup LIRs use PI address space as a start, and when they have filled enough of this, apply for their own PA again. The problem with this is that in the end, it's very likely that more than one route will end up in the global BGP table (where one PA route would be sufficient), and also it encourages lying to the RIRs (PI space must not be distributed to third parties, i.e., LIR customers). The drawback of the changes are that it's potentially wasting address space for "very small LIRs" (that would be happy with a /23 PI space and will now get a "huge" /21). The wastage would only happen for very small LIRs that will never grow to fill the initial /21. A rough calculation shows that "1000 new LIR /21 allocations" would need a /11, which is not an unbearable strain on the conservation side, judging from the total number of LIRs in RIPE land today. A second drawback of this is that people may need to adapt their BGP filters to permit /21s from the network block(s) where these allocations are made from. So the RIPE NCC needs to document this accordingly, and ideally, well in advance. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 57785 (56883) SpaceNet AG Mail: netmaster(a)Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

4 6

IANA Policies for Allocation of IPv4 Blocks to RIRs
by Axel Pawlik 15 Dec '03

15 Dec '03

Dear Colleagues, The Regional Internet Registries (RIRs) have been working together with the Internet Assigned Numbers Authority (IANA) on a policy for the allocation of IPv4 address space to the RIRs. The proposed policy was presented to the RIPE Address Policy Working Group at RIPE 46 in September. The presentation can be found at: http://www.ripe.net/ripe/meetings/ripe-46/presentations/ripe46-ap-iana-rir/ Following discussion in all four RIR regions, this policy proposal and discussion results will be forwarded to the ICANN ASO Address Council for review and submission to the ICANN Board. It is considered a global policy proposal. Please review the document "Internet Assigned Numbers Authority (IANA) Policies for Allocation of IPv4 Blocks to Regional Internet Registries". The document can be found at: http://www.ripe.net/ripe/draft-documents/iana-rir-allocation-policies.html Comments on this proposal should be sent to this list. The review period is six weeks and will end on 16 November. A webcast recording of the entire RIPE Address Policy Working Group session can be found at: mms://webcast.ripe.net/ripe46/ap-1a.wmv mms://webcast.ripe.net/ripe46/ap-2a.wmv Kind regards, Axel

2 1

Final Reminder - RIPE NCC Dubai Meeting, Dec. 2003
by Membership Liason Officer 24 Nov '03

24 Nov '03

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC Regional Meeting, Middle East, will be held 7 - 9 December 2003 at the Taj Palace Hotel, Dubai, U.A.E. The meeting will focus on Internet resource management issues. Attendance to the RIPE NCC Regional Meeting is free of charge. However, attendees are responsible for covering their own travel and accommodation costs. AGENDA The agenda has been recently updated with more information about speakers and presentations. For the full agenda, please see: http://www.ripe.net/ripencc/regional-meetings/dubai-2003/plan.html REGISTRATION To register for the RIPE NCC Regional Meeting, Middle East, please see: http://www.ripe.net/cgi-bin/dubai-reg HOTEL RESERVATIONS: The RIPE NCC has arranged for a block of rooms to be held for meeting attendees at the Metropolitan Palace Hotel and the Metropolitan Hotel Sheikh Zayed Road, Dubai. There are a limited number of rooms available. Please note that rooms will be held only until 25 November 2003. After this date we cannot guarantee room availability. To reserve a room directly with the hotel, please use the reservation forms at: http://www.ripe.net/ripencc/regional-meetings/dubai-2003/hotel-information.… Any further questions about the RIPE NCC Regional Meeting, Middle East, can be sent directly to: <contact(a)ripe.net>. Regards, Sabrina Wilmot Membership Liaison Officer RIPE NCC

1 0

New IPv4 blocks allocated to RIPE NCC
by leo vegoda 18 Nov '03

18 Nov '03

Dear Colleagues, The RIPE NCC received the IPv4 address ranges 83.0.0.0/8 and 84.0.0.0/8 from the IANA in November 2003. We will begin allocating from these ranges in the near future. On 24 October 2003 there was a formal proposal to the RIPE Address Policy Working Group to lower the minimum allocation size from /20 to /21. For the text of this proposal please see: <http://www.ripe.net/ripe/mail-archives/address-policy-wg/2003/msg00189.html> It is likely that there will be formal consensus on this proposal in the near future. Consequently, the minimum allocation size for these blocks has been set at /21. Nonetheless, the RIPE NCC will not make /21 allocations from these blocks until after there is formal consensus to do so. You may wish 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: <http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Kind regards, -- leo vegoda RIPE NCC Registration Services Manager

1 0

RE: [address-policy-wg] FORMAL PROPOSAL: change of initial PA all ocation size
by Titley, Nigel 17 Nov '03

17 Nov '03

Gert Doering wrote: > Hi, > > this was discussed on the list before the last RIPE meeting, and we > had it on the address policy working group meeting (presented by me). > > I think we mostly have consensus on this issue, but I want to present > it as a formal proposal, before it's incorporated into the policy. I am strongly in favour of this, it helps to solve the bootstrapping problem that many small LIRs suffer from, and which many have to lie about to get around. > > PROPOSAL: > > * the minimum initial allocation size (for new LIRs) is reduced from > a /20, as of today, to a /21. > (If a new LIR can demonstrate need for a bigger initial > allocation, they can get a larger address block. This will not > be changed). > > * the requirement to show an immediate need for 25% of the allocated > address space is removed for the "minimum initial allocation" > > > The motivation for that is that under the current policy, startup LIRs > that do not already hold address space cannot get an initial > PA allocation > (which would be a /20 as of today, or bigger), because in > many cases, they > cannot demonstrate immediate need, or prior utilization of sufficient > address space. > > To work around this, many startup LIRs use PI address space > as a start, > and when they have filled enough of this, apply for their own > PA again. > The problem with this is that in the end, it's very likely that more > than one route will end up in the global BGP table (where one PA route > would be sufficient), and also it encourages lying to the > RIRs (PI space > must not be distributed to third parties, i.e., LIR customers). > > > The drawback of the changes are that it's potentially wasting address > space for "very small LIRs" (that would be happy with a /23 PI space > and will now get a "huge" /21). The wastage would only happen for > very small LIRs that will never grow to fill the initial /21. > A rough calculation shows that "1000 new LIR /21 allocations" would > need a /11, which is not an unbearable strain on the conservation > side, judging from the total number of LIRs in RIPE land today. > > A second drawback of this is that people may need to adapt their BGP > filters to permit /21s from the network block(s) where these > allocations are made from. So the RIPE NCC needs to document this > accordingly, and ideally, well in advance. > > Gert Doering > -- NetMaster ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. **********************************************************************

2 1

ETNO Common Position on IANA policies for allocation of IPV4 blocks
by Debecker Leo 10 Nov '03

10 Nov '03

RIPE Address Policy WG Concerns: Your document describing the policies governing the allocation of IPv4 address space from IANA to the Regional Internet Registries (RIRs) (call for comments, deadline 16 November 2003). Dear colleagues, Please find below the ETNO Common Position on the aforementioned consultation document. This ETNO Common Positions has been approved by all the members of the ETNO Naming, Addressing and Numbering Working Group and then received a unanimous positive vote from all 39 member companies in ETNO. The paper will equally be published, as of tomorrow, on our web site at: www.etno.be Best regards, Leo Debecker Executive Manager, Operations ETNO Brussels. November 2003 ETNO Common Position on "Internet Assigned Numbers Authority (IANA) Policies for Allocation of IPV4 Blocks to Regional Internet Registries" Executive Summary ETNO supports the proposed global policy and finds it is much more precise than the existing one. In particular, the concept will allow Regional Internet Registries more flexibility in the management of their allocated space. The European Telecommunications Network Operators' Association (1) (ETNO) has carefully reviewed the proposed global policy defining the address allocation of IPV4 Blocks from IANA to the Regional Internet Registries (http://www.ripe.net/ripe/draft-documents/iana-rir-allocation-policies.h tml). This policy has the merit of being much more precise, documented and detailed than the existing one. Clear definitions of available space and necessary space are provided. The proposal will allow more flexibility for the Regional Registries in the management of their allocated address space, based on the: . allocation of a sufficient address space to cover the needs for an 18 month period . possibility to take into account documented special needs to calculate the necessary space. ETNO supports this proposal and is convinced that Local Internet Registries and their customers will benefit from this flexibility. (1) The European Telecommunications Network Operators' Association is representing 39 major companies from 34 European countries, providing electronic communications networks over fixed, mobile or personal communications systems. ETNO's primary purpose is to establish a constructive dialogue between its member companies and actors involved in the development of the European Information Society to the benefit of users. More information on ETNO can be found at: www.etno.be

1 0

Is the time for conservation over?
by Michael.Dillon＠radianz.com 04 Nov '03

04 Nov '03

One area of address policy that is fairly consistent world-wide is the view that IPv4 address space is scarce and that the policy must be conservative, i.e. the policy must make conservation of IPv4 addresses a high priority. I don't think that's true anymore. On the one hand, we have IPv6 deployed commercially in 3 of the 4 policy regions (Europe, AsiaPac, America) which indicates a continuing trend toward a future time where IPv6 service will be almost as easy to find as IPv4 service. On the other hand, the worst possible outcomes discussed when CIDR was first deployed are not going to happen. For instance there was a fear that the People's Republic of China might want 1/4 of the IPv4 space because they have 1/4 of the planet's population. This has not happened and is now quite unlikely to happen. Therefore, I believe that all the RIRs should jointly do some research to establish a prudent date at which IPv6 will be considered to have reached critical mass so that there will be a significant migration of users from IPv4 to IPv6. Once we set our sights on this date we should set aside a certain amount of buffer in the IPv4 space, and then design our policy to consume the rest of the IPv4 space, not to preserve it. At the same time, this policy shift should be presented as part of a global IPv6 migration strategy because that is what it is. In addition, I don't see any good reason to wait until LIRs come and ask for IPv6 space. It's not scarce and the vast majority of IPv4 LIRs will be deploying IPv6 sometime. So why don't we just give every single one of them an IPv6 /32 today. Instead of creating barriers to the adoption of dual v4/v6 networks as we are today, we should be facilitating the operation of dual v4/v6 networks. We need to create an environment in which the end user can choose whether to use v4 or v6 rather than constraining the end users with our v4-centric regulatory bureaucracy. --Michael Dillon

9 14

Re: [address-policy-wg] re: Is the time for conservation over?
by Michael.Dillon＠radianz.com 04 Nov '03

04 Nov '03

>>In addition, I don't see any good reason to wait until LIRs come and ask >>for IPv6 space. It's not scarce and the vast majority of IPv4 LIRs will >>be deploying IPv6 sometime. So why don't we just give every single >>one of them an IPv6 /32 today. Instead of creating barriers to the >>adoption >This was the opinion in the first days op IPv4, please don't make the same mistakes again with IPv6.. We can't look into the future, but we can look at the past!! I don't want to make the same mistakes as IPv4. That is why I want to give an IPv6 /32 to every IPv4 LIR. With IPv4 we made a mistake by trying to be too careful with class C address blocks and again with small CIDR blocks. Instead of giving out large blocks of class C space, we created the swamp. When CIDR came along we continued to give out blocks for one year or less of growth and we bloated the global routing table. With IPv6 we do not have to worry about waste. Every LIR gets a /32 from a reserved /29. When addresses are issued to customers, everybody gets a /48 except in special circumstances where a /64 or a /128 would be assigned. I don't think there will be very many special situation that justify a /64 assignment today. This means that we have a very simple straightforward system that allows LIRs to grow 8 times before we even begin to create anything that is similar to past history. The key to avoiding the mistakes of history is to forget about conserving address space. It is not a scarce resource; we have lots of it. --Michael Dillon

2 1