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

2006-01 Proposal Accepted (Provider Independent (PI) IPv6 Assignments for End User Organisations)
by Filiz Yilmaz 22 Apr '09

22 Apr '09

PDP Number: 2006-01 Provider Independent (PI) IPv6 Assignments for End User Organisations Dear Colleagues, Consensus has been reached, and the proposal described in 2006-01, "Provider Independent (PI) IPv6 Assignments for End User Organisations" has been accepted by the RIPE community. The related RIPE policy document is now updated, published and can be found at: http://www.ripe.net/ripe/docs/ripe-466.html or http://www.ripe.net/ripe/docs/ipv6-policies.html The proposal is now archived and can be found at: http://www.ripe.net/ripe/policies/proposals/2006-01.html The RIPE NCC will implement this new policy within one month. Thank you for your input. Regards Filiz Yilmaz Policy Development Officer RIPE NCC

2 1

Draft Proposal: Assignment of an IPv4 /24 for documentation purposes
by Peter Koch 21 Apr '09

21 Apr '09

Dear WG, this is a rough draft policy proposal. I'd appreciate some feedback before I decide whether to invoke the formal process. Summary: The RIPE NCC is asked to assign an IPv4 /24 for documentation purposes. Background: In example configurations, RFCs, training material and other documentation it is necessary from time to time to include IP addresses, domain names or even phone numbers as examples. These resources should meet all syntactical requirements (e.g., be "real" IP addresses), but should not interfere with assignments or registrations by innocent third parties. See RFC 4085 (BCP 105) for what could happen in the worst case. For the DNS, RFC 2606 (BCP 32) has set aside several top level and second level domain names and the network 192.0.2/24 has been dedicated for documentation and test purposes by the IANA in the past (see RFC 3330). RFC 3849 ("IPv6 Address Prefix Reserved for Documentation") documents APNIC's assignment of 2001:DB8::/32 for the sole use in example texts. Motivation: During recent discussion within the IETF, but also on other occasions in the past, it appeared that a single /24 is often not enough to support instructive examples. This may include more complex network designs, or the use of addresses for DNS name servers, where good practice (see RFC 2182, BCP 16) suggests topological diversity. Sometimes, address space from RFC 1918 (BCP 5) is used in addition to or as a replacement for 192.0.2/24, but this is also a source of confusion due to the special nature of the "private address space". It also conflicts with the goal to avoid any collision with addresses used in real life, even if the burden would be spread across many users of RFC 1918 address space. Request: The RIPE NCC is asked to assign and dedicate a /24 that is reasonable visually distinct from 192.0.2/24 for documentation only purposes. The network is not to be used and the prefix is never expected to be announced in any BGP session (cf. 3849). The new assignment is not intended to serve as a supplement to RFC 1918 address space. It is intentionally left open here whether similar considerations would suggest an additional assignment in v6 space, as well. The pros should be obvious to anyone who ever had to write documentation or example configurations, but there are also some cons: o another /24 is a waste of space o just a /24 won't be enough o this creates yet another bogon o any invest in IPv4 is a waste of resources, anyway o nobody knew 192.0.2/24 in the first place, so why add to the confusion? o this doesn't need a policy proposal, but could be dealt with through a specially "sponsored" PI assignment A special action seems cleaner to me than some random PI assignment, but this is why I'd like to ask the WG for feedback. Also, if anyone is aware of other address space similar to 192.0.2/24, I'd appreciate a pointer. Best regards, Peter

7 9

do you believe ? the time is near.
by Frederic 21 Apr '09

21 Apr '09

hi, http://www.ripe.net/ripe/policies/proposals/2006-01.html it is time to permit IPV6-PI assignement. That the way to permit to IPV6 to be alive in the entire network. Awaiting Decision from WG Chairs : Please give you décision. we need, we want ask our Ipv6-PI ! Bst regards. F.

1 0

New Document available: RIPE-465
by RIPE NCC Document Announcement Service 20 Apr '09

20 Apr '09

Dear Colleagues, The mention of 0.8 as the HD ratio (in two occurrences) in ripe-450 is an error. In RIPE, the HD ratio for IPv6 has been set at 0.94 since November 2007 and was documented correctly in the previous IPv6 Address Allocation and Assignment Policy (ripe-421). We have corrected the error and published an updated document (ripe-465) that you can find at: http://test-www.ripe.net/ripe/docs/ripe-465.html We apologise for any confusion this may have caused and will put in place additional checks to prevent similar errors in the future Kind Regards Adrian Bedford Web Services Team Leader RIPE NCC and Filiz Yilmaz Policy Development Officer RIPE NCC

2 2

2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
by Ingrid Wijte 18 Apr '09

18 Apr '09

PDP Number: 2009-05 Multiple IPv6 /32 Allocations for LIRs Dear Colleagues A new RIPE 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/2009-05.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 12 May 2009. Regards Ingrid Wijte Assistant Policy Development Officer RIPE NCC

20 73

RE: Multiple IPv6 /32 Allocations for LIRs
by Stream Service 15 Apr '09

15 Apr '09

Hello, (ab)using IPv6 PI is also not a good solution for it I guess. How should we make it possible? With kind regards, Mark Scholten -----Original Message----- From: Andy Davidson [mailto:andy.davidson@netsumo.com] Sent: woensdag 15 april 2009 13:54 To: Stream Service Subject: Re: Multiple IPv6 /32 Allocations for LIRs On 15 Apr 2009, at 12:18, Stream Service wrote: > It should be aggegatable for as far as the LIR wants. It should also > be > possible to split it up to /48's without a problem (for example is 1 > LIR has > multiple ASN's or when some address space should only be available via > peering). It is possible with IPv4 for as far as I know, why don't > make it > possible with IPv6? Hi, Mark Thank you for your email. It is possible with IPv6. The question is, do we really want the v6 table to be as fragmented as the v4 one ? Of course we do not. We want fast convergence in the default free zone. We wont get this if we don't look after the policies which govern assignment though. Andy -- Regards, Andy Davidson, NetSumo Limited D: +44 (0) 20 7993 1702 S: +44 (0) 20 7993 1700 E: andy.davidson(a)netsumo.com

1 0

Policy Proposal : "Run Out Fairly"
by Daniel Karrenberg 15 Apr '09

15 Apr '09

Dear colleagues, attached you will find a policy proposal we call "Run Out Fairly". It is based on a discussion instigated by your's truly during the open policy hour at the latest RIPE meeting. This is a proposal to gradually reduce the allocation and assignment periods in step with the expected life time of the IPv4 unallocated pool in order to address the perception of unfairness once the pool has run out. The proposal is not intended to stretch the lifetime of the unallocated pool. The proposal is independent of other proposals to reserve address space for transition purposes and/or new entrants. It can be implemented independently of these. We thank Filiz Yilmaz for her help, invite discussion of this proposal and look forward to high quality comments. For the authors Daniel Karrenberg PS: Can we refer to this proposal by name and not by number? ;-)

11 17

Volker Frank/PLZ/CSC is out of the office.
by Volker Frank 14 Apr '09

14 Apr '09

I will be out of the office starting 08.04.2009 and will not return until 20.04.2009.

1 0

2009-04 New Policy Proposal (IPv4 Allocationand Assignments to Facilitate IPv6 Deployment)
by alain.bidron＠orange-ftgroup.com 10 Apr '09

10 Apr '09

Thank you for the first comments received on 2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment). Please find hereafter some response. >From Marcus Stoegbauer: >> For a start: I can't really tell if the new policy text should replace >> the old IPv4 address allocation and assignment policy. The new policy >> only talks about address space given out to ISPs for transition >> techniques, so I assume that an ISP with a lot of free (i.e. not >>assigned/unused) IPv4 address space can also get another allocation >>under this policy? Response This policy is done in accordance with existing v4 policies and basic principle is that allocation/assignment should be based on needs. The difference with that policy is the minimum allocation/assignment size is different and filtering policies, should be different in this range. So when requesting additional IPv4 resources (after the IPv4 pool is depleted - from the transition /8) an ISP should still demonstrate the required utilisation of already allocated addresses. If an ISP has already sufficient resources allocated for implementing transition techniques it should not be qualified to receive additional resources from that policy, except if the use of these resources implies fragmentation and filtering issues. This is to be evaluated by the RIPE-NCC when analysing the request. >From Marcus Stoegbauer: > >Then the minimum size of /27. Obviously it would be a brilliant test >> to see if routers will be able to hold all the IPv6 PI prefixes that >> will come to life once we allow them to be handed out. And it would be > >a very handy way to tear down the v4 internet, so it's in full >> compliance with some IPv6 implementation plans. >> But to be serious for a minute: if all those /27 would be announced a > >IPv4 full table would nearly triple in size (or in other words: all > >those /27 are twice the size of a full IPv4 table today). This can't >> possibly end well, so I'm not in favor for this proposal in its >> current form. Response I don't think this policy will really change the size of routing table. If the policy is based on a /24 it would only waste v4 resources, and reduce on medium long term the possibility to provide those necessary resources. The growth of the routing table will be proportional to the growth of the number of new ISPs - PA holders and the use of multi-homing, exactly as today, this proposal will not change this significantly. Please note that a /27 under this proposal will actually represent a today's /21 ( or even shorter prefix). >From Sebastian Wiesinger [ripe+apwg(a)karotte.org] >> First: It won't work. Most people I know filter prefixes smaller than >> /24 in the DFZ. They will not see these allocations. You can't assume >> that they will change their filters for this. I would estimate that >> most of them won't. Many can't do this because it will not fit in >> their RIB/FIB. So if you do this you would have to give out a /24 at least. Response: It won't work in the current situation but will have to work in the new depleted context. Rather than splitting the existing v4 resources in small pieces, the proposal suggests to dedicate a specific /8 where filtering policies could be adapted. >From Sebastian Wiesinger [ripe+apwg(a)karotte.org] >> Second: We do want to facilitate deployment of IPv6. I think this >> proposal could be counterproductive. You're splitting up the remaining >> space in smaller peaces so that more people can use IPv4 for a longer >> timespan. And if you have to give out /24s you can bet that people >> will use it for other things besides NAT-PT etc. Response: No we don't want to prolong v4 lifetime, only to allow for v6 providers to interact with the existing v4 environment that will not disappear overnight. This proposal will not in my views prolong v4. Whether we want this or not, the demand for IPv4 address space after the IPv4 pool is depleted will continue. It will be proportional to the amount of existing IPv4-only resources and the number of newly connected customers, regardless whether they are IPv4 or IPv6-only, or dual-stack. This proposal attempts to satisfy this demand on continuous and predictable basis for the transition period without changing the fundamental principles of resource allocation. >From Sebastian Wiesinger [ripe+apwg(a)karotte.org] > Third: Is it necessary? You already have to demonstrate a need for > address space if you want a new allocation. If an LIR already has an > allocation I assume that they can spare an /27 for IPv6 transition. >> If you have a new LIR you allocate them a /21 if they can demonstrate > the need for it, no change there. Response: I say YES it is necessary because remember we are in a depleted context. It means that the RIPE-NCC will not be in a position to allocate IPv4 addresses under today policies. Are you totally sure that all existing holders of IPv4 resources will be able to spare /27 for IPv6 transition? And regarding new entrants where those /21 will come from? I think we cannot deny that exhaustion is becoming a reality. >From Andy Davidson >> If it's good to restrict the allocation and assignment of v4 resources >> to organisations who have a stated v6 deployment policy, then why do >> we need to wait until the final /8 has been allocated to the NCC >> before we begin such a policy ? Perhaps we should have a phased >> process that asks organisations how they are deploying v6 on the PA >> and PI request forms, and then future requests from that organisation, >> or related organisations are refused if the deployment has not started. Good point Andy, I am not opposed to think about something that could be inserted in the "run out fairly proposal" opening the way to something stricter on the last /8 policy >From Andy Davidson >>Why was /27 selected rather than /26 or /25 ? Since most deployments >>have multiple, separate infrastructure assignments, and services/user >> assignments, it seems that a /27 as a minimum allocation is far to >> small to promote any degree of aggregation whatsoever. This policy is >> therefore counter to one of RIPE's regularly stated aims - to promote >> route aggregation. The counter argument to this is that I might as > >well accept that we the side of common sense has lost the v4 > >aggregation debate, and v4 after-market sales will drive deagg > >further, so why should we care ? Response: Remember that we need a mechanism that allows to provide the small amount of IPv4 addresses needed to interact with the IPv4 environment for a long time (before Ipv4 addresses being completely obsolete).A similar approved policy in ARIN is based on a /28! A downscaling factor of 64 is in my view a good compromise. >From Andy Davidson >> On the other hand, perhaps this policy will be seen as an ipv4 life >> extension policy. We do not want to muddy the message that we send to >> the community. V4's free pool will soon be gone. Do not gamble your >> company on policies designed to extend the availability of a very >> scarce resource. >> Maybe we can pool some of the ideas in 2009-03 and -04, and the >> community response, and build a solid run down policy that encourages >>v6 adoption, but doesn't pretend to be able to extend the life of v4. Response: The intention of the proposal is certainly not to extent the IPv4 life. On the contrary we try to put some incentive for a move to v6 facilitating to those who go that way a fair access to the limited v4 resources strictly needed to interact with the existing v4 environment. We must be realistic even if we all call for a move to v6 Ipv4 will not disappear overnight and transition to IPv6 requires continuous supply of IPv4. Without this we will face an double or triple NAT and walled garden alternatives which will change the architecture and principles of the Internet significantly and will never get us to IPv6. Regards Alain ********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ********************************

1 0

2009-04 New Policy Proposal (IPv4 Allocation and Assignments to Facilitate IPv6 Deployment)
by Filiz Yilmaz 10 Apr '09

10 Apr '09

PDP Number: 2009-04 IPv4 Allocation and Assignments to Facilitate IPv6 Deployment Dear Colleagues, A new RIPE 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/2009-04.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 5 May 2009. Regards Filiz Yilmaz Policy Development Officer RIPE NCC

9 12