- address-policy-wg - mailman.ripe.net

2011-01 New Policy Proposal (Global Policy for post exhaustion IPv4 mechanisms by the IANA)
by Emilio Madaio 22 Mar '11

22 Mar '11

Dear Colleagues, A new Global Policy Proposal has been made and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2011-01/ We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 18 April 2011. Regards Emilio Madaio Policy Development Officer RIPE NCC

6 7

RE: [address-policy-wg] IPv6 allocations for 6RD
by Kurt Smolderen 21 Mar '11

21 Mar '11

I strongly support the idea of assigning a smaller prefix to ISPs which are in a state of deploying IPv6 but need to use transitional mechanism for (some of) their customers. Mark has described one of the problems very clear in his email: if an ISP has only a /32 prefix and needs to use all 32 IPv4 bits in the 6rd configuration, only a /64 can be delivered to the home instead of the desired /56 or /48. Needing all 32 bits is for instance the case when an ISP offers internet connectivity to some of its customers via a partnership with another ISP. However, I want to point to an additional problem which appears when an ISP wants to deploy native IPv6 but needs to roll out 6rd (or any other transitional technique) as well. For native IPv6, the ISP will create an IPv6 addressing plan. This will normally include separate prefixes for the ISP's own servers, the ISP's backbone, the ISP's customers etc. For the 6rd domain, the full /32 range is however needed. So at this stage, the ISP has two options: 1) Implement 6rd only 2) Implement native IPv6 only and exclude some customers from being able to use IPv6 (those which would normally be connected through 6rd) I strongly believe we all agree 6rd is only a temporary solution. So I can't imagine we would prefer skipping native IPv6 deployments in favor of IPv6 transitional mechanisms. I also believe we all agree we should enable IPv6 for as much customers as we can, which makes me conclude the second 'option' is not really an option at all... My primary concern is that any ISP - regardless of how small or big it is - can independently of other organizations/ ISPs move forward with IPv6 deployment. RIPE can support this by adapting a policy which - albeit for a limited time span - allows the assignment of a contiguous IPv6 prefix which size does not only depend on the amount of customers the ISP has, but also incorporates the needed technologies to 'IPv6-enable' as much customers as possible. Regards, -Kurt

7 17

2010-05 Policy Proposal Withdrawn (Global Policy for IPv4 Allocation by the IANA post exhaustion)
by Emilio Madaio 18 Mar '11

18 Mar '11

Dear Colleagues, The global policy proposal 2010-05, "Global Policy for IPv4 Allocation by the IANA post exhaustion", has been withdrawn. It is now archived and can be found at: http://www.ripe.net/ripe/policies/proposals/2010-05 The reason for withdrawal is: it was agreed with the proposer that the lack of community feedback and the impossibility of the proposal becoming globally accepted due to recent developments in the global PDP at the time were sufficient reasons to have it withdrawn. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

Updated RIPE NCC Procedural Document Available
by Arne Kiessling 15 Mar '11

15 Mar '11

Dear Colleagues, The RIPE NCC has published an updated procedural document, ripe-518, "Implementation of RIPE Policy 'Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region' - Phase 3". This document replaces ripe-511, which was published recently. The updated document is available at: http://www.ripe.net/ripe/docs/ripe-518 -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre

2 2

New RIPE NCC Procedural Document Available
by Arne Kiessling 10 Mar '11

10 Mar '11

Dear Colleagues, The RIPE NCC has published the new procedural document ripe-511, "Implementation of RIPE Policy 'Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region' - Phase 3". This document describes the RIPE NCC procedure when contacting End Users of independent Internet number resources who have not yet entered into a contractual relationship with sponsoring Local Internet Registry (LIR) or the RIPE NCC. It also describes the possible consequences if End Users of independent Internet number resources fail to respond when approached by the RIPE NCC or are not compliant with the policies of the RIPE community. The new document is available at: http://www.ripe.net/ripe/docs/ripe-511 -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre

2 1

Re: [address-policy-wg] IPv6 PI resource question - Not for ISP but hosting
by Adrian Czapek 07 Mar '11

07 Mar '11

My similar request was rejected for the same reasons. Although I did not get a proposal to sub-allocate PA address space from my allocation and deaggreage it over BGP, as Mathieu got, but let's assume that I would get such proposal if I asked for it. What puzzles me, what is the meaning of that action? Let's check the options: 1. They become LIR, they got their allocation - result: +1 prefix i global routing table. 2. They gets PA suballocation from other LIR and deaggreate it - result +1 prefix in global routing table. 3. They gets PI address space - +1 prefix in global routing table. As can be clearly seen above, global routing table growth is not an issue here, since IPRA suggests to deaggregate PA sub-allocations. So, what is an issue here, beacuse I have a strange feeling that only issue are $$ lost by certain RIR due to certain companies refusing to become LIR?! Regards -- Adrian

2 2

Re: [address-policy-wg] IPv6 PI resource question!
by Igor Ybema 03 Mar '11

03 Mar '11

Hi, I'm new to the list but would like to comment on this subject. I'm also trying to receive IPv6 PI for a webhosting customer of us which seems to be a big problem. I do not understand why everyone claims that 'the routing table growth' is the reason not to allow too much IPv6 PI. Those currently having IPv4 PI would of course require IPv6 PI because they still want to be indepentent. If they need to be a LIR to get IPv6 PA the problem is not solved for the routing-table issue. A prefix is still entered into the same global routing-table. I would suggest changing the IPv6 PI policy to make it more clear for hosting/isp company's to get IPv6 PI by enforcing that the equipment on which the IPv6 addresses are installed in rooms accessible by that company. Multi-homing is a good reason also. I'm not sure if we should delete that reason. This makes the company more aware that they are really independend. This suggestion solves two things: - large broadband ISP's with CPE in office-building, homes etc do not fit into this policy. The equipment is behind other company's doors. This enforces these company's to assign block to their customers from PA space as it was meant to be. - small ISP's/hosting company's with a few racks installed at one ore more DC's (which we talk about in this postings) do fit into this policy and will be independend to their internet suppliers. Of course, they should request another PI (or get assigned-PA from a LIR) for their customers which buy dedicated racks from them and receiving their own key to the lock. This is exactly what we would like to see it. What do other people on the list think about this? regards, Igor Ybema

8 11

New IPv4 block allocated to RIPE NCC
by Andrea Cima 01 Mar '11

01 Mar '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate mails] Dear Colleagues, The RIPE NCC has received the IPv4 address range 185/8 from the IANA. This is the final allocation of IPv4 address space that the RIPE NCC will receive from the IANA as stated in ripe-436, "Global Policy for the Allocation of the Remaining IPv4 Address Space". The minimum allocation size for this /8 has been set at /22. You may wish to adjust any filters you have in place accordingly. More information on the IP address space administered by the RIPE NCC can be found on our website at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Additionally, please note that three "pilot" prefixes will be announced from this /8. The prefixes are: 185.0.0.0/16 185.1.0.0/21 185.1.24.0/24 They all originate in AS12654. The pingable addresses will be: 185.0.0.1 185.1.0.1 185.1.24.1 More information on this activity is available in the document "De-Bogonising New Address Blocks", which can be found at: http://www.ripe.net/ripe/docs/ripe-351.html Kind regards, Andrea Cima Registration Services Manager RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAk1Pu9kACgkQXOgsmPkFrjM9FgCgsaT8cFxK0YKTFUFzj41L0PQT N1AAoIgmL1zUY8JjkCSa05xt0t8oppgP =woX5 -----END PGP SIGNATURE-----

2 8

RE: [ipv6-wg] RE: [address-policy-wg] IPv6 allocations for 6RD
by Wyatt Mattias Gyllenvarg 01 Mar '11

01 Mar '11

Hi We would like to weigh in here. We feel that it should be RIPEs policy to allocate ONE /32 to any LIR who requests it for 6rd. 6rd is the only way for us to reach all our residential customers. Especially those in Municipal Networks that are very slow to invest in their networks and often do not have the competence and time to impelment IPv6. Also, Cisco has not yet implemented even a small part of the protective mechanisms we rely on in IPv4 to secure our residential networks. Many of these features are required to meet the demands contracted with the customers. We cannot use native IPv6 until Cisco implements these features and we have tested and rolled them out on hundreds of switches. 6rd bypasses all these issues. IF we can get a /32 for that purpuse. -- Med Vänliga Hälsningar - Best regards Mattias Gyllenvarg Network Operations Center Bredband2 ---------------------- end of line ---------------------------

6 8

REMINDER; WAS Re: 2008-08 New Version and Draft Document Published (Initial Certification Policy for Provider Aggregatable Address Space Holders)
by Emilio Madaio 25 Feb '11

25 Feb '11

[Apologies for duplicates. Courtesy copy sent to Routing Working Group and RIPE NCC Services Working Group. Please direct feedback to the Address Policy Working Group mailing list.] Dear Colleagues, The new version of RIPE Policy Proposal 2008-08, "Initial Certification Policy for Provider Aggregatable Address Space Holders", was published on 9 February 2011. The time period for community review ends on 23 February 2011. Some feedback was sent to the Address Policy Working Group mailing list. However, to maintain the discussion, we strongly recommend that you share your ideas and comments and clearly let the community know if you: - Support the implementation of the proposal - Support the general principle of the proposal but would prefer another wording - Support the general principle with some details changed but agree to postpone this discussion until another stage of the policy proposal review. (This is an initial proposal that covers only PA resources. If the community supports extending certification to all resources, then another version of the proposal will be necessary.) - Do not support the proposal (please explain your motivations) You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-08 and the draft document at: http://www.ripe.net/ripe/policies/proposals/2008-08/draft Please send an email with your comments to address-policy-wg(a)ripe.net by 23 February 2011. Best regards, Emilio Madaio

2 2