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

status of 2011-02
by Gert Doering 05 Jan '12

05 Jan '12

Dear AP WG, 2011-02 has been a difficult one, and you have noticed the lack of visible progress. So let us explain, and propose a way forward. The RIPE policy development process calls for "consensus" to make policy from policy proposals. Sometimes it's very clear if consensus has been reached, and sometimes it's very clear that consensus has NOT been reached. When looking for consensus, we have to see if there are objections to the proposal, and if those objections are justified - see the beginning of section 2 of RIPE-500: 'In all phases of the RIPE PDP, suggestions for changes to the proposal and objections regarding the proposal must be justified with supporting arguments'. This is explicitly repeated in section 2.4. In 2011-02, we have the case of "rough consensus with objections": We have a number of people who spoke up in favour of the proposal, both during the discussion/review phases and during Last Call. A few persons had serious doubts about routing table growth and about PI in general, but still spoke in favour of the proposal, or abstained. One person opposes the proposal, based on worries about highly accelerated and thus unsustainable routing table growth as a consequence of the proposal. Given that some of the other RIRs already have less restrictive IPv6 PI policies, the available numbers on their PI assignments and the routes seen in the global IPv6 BGP table do not back this assumption. Neither does the data from the global IPv4 BGP table, where the RIPE region has always had a very relaxed PI policy. So the AP WG chairs have decided (after long discussion) that we do have rough consensus on this policy proposal, and the remaining objections will be ignored. Sander Steffann announced this at the APWG meeting - and one member of the WG spoke up at the microphone and disagreed with our conclusion. So we spent some more weeks discussing and thinking about this, and this is what we do now: - the WG chairs declare consensus - but the *working group* has the last word on any policy decision, so we call for two weeks of "Last Call" on this decision Procedure-wise, this is not about the *content* of the proposal now, and it's not useful to repeat the discussion about routing table growth etc. now - we've heard all arguments. What we need to decide now is whether the voices from the community so far form "rough consensus" on the proposal, or not. If you, the WG, decides that we do not have consensus, the policy proposal goes back to "discussion phase", and the proposer will need to work with those people that spoke up against the proposal to integrate their ideas, and come up with a new version of the policy proposal that might then reach consensus. sincerly yours, Gert Doering & Sander Steffann, APWG chairs -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

21 52

Re: [address-policy-wg] 2011-04 Discussion Period extended until 30 January (Extension of the Minimum Size for IPv6 Initial Allocation)
by Sascha Lenz 03 Jan '12

03 Jan '12

Hi, > Dear Colleagues, > > The text of RIPE Policy Proposal 2011-04, "Extension of the Minimum > Size for IPv6 Initial Allocation", has been revised based on the > community feedback received on the mailing list. We have published > the new version (version 2.0) today. As a result, a new Discussion > Phase is set for the proposal. > > Highlights of the changes in version 2.0 are: > > - The proposed new section 5.1.2 was reworded > - Section 5.7 was not removed but it was reworded > > > You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2011-04 > > > We encourage you to review this policy proposal and send your comments > to <address-policy-wg(a)ripe.net> before 30 January 2012. > looks basically fine to me - the new version doesn't change anything i liked about the initial one. Although maybe.. "Organisations that meet the initial allocation criteria are eligible to receive an initial allocation of /32. For allocations up to /29 no additional documentation is necessary." ... is a little vague for people who haven't followed the discussion here ("why no /29 per default in the first place?"). I don't see a general problem with that wording and have no better idea, just saying that some might be confused about what's the point here when reading the updated policy later. Or maybe it's just me _because_ i followed the discussion :-) -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect

1 0

Re: [address-policy-wg] [policy-announce] 2011-04 Discussion Period extended until 30 January (Extension of the Minimum Size for IPv6 Initial Allocation)
by Jan Zorz ＠ go6.si 02 Jan '12

02 Jan '12

On 1/2/12 3:10 PM, Emilio Madaio wrote: > Dear Colleagues, > > The text of RIPE Policy Proposal 2011-04, "Extension of the Minimum > Size for IPv6 Initial Allocation", has been revised based on the > community feedback received on the mailing list. We have published > the new version (version 2.0) today. As a result, a new Discussion > Phase is set for the proposal. > > Highlights of the changes in version 2.0 are: > > - The proposed new section 5.1.2 was reworded > - Section 5.7 was not removed but it was reworded Hi, Emilio, thnx for your efforts and all the help with this proposal. Just to add my .2 cents - we considered Remco's and James's suggestions, first one to give out /32 by default and give out more only if LIR asks for it (Remco) and we re-added section 5.7 with clarification, that every holder of legacy /32 can ask for extension of allocation. This is what we heard from you - community - in last few months of discussion. Hope that we made this proposal more acceptable for everyone. Thnx for all your input, Jan Zorz

1 0

2011-04 Discussion Period extended until 30 January (Extension of the Minimum Size for IPv6 Initial Allocation)
by Emilio Madaio 02 Jan '12

02 Jan '12

Dear Colleagues, The text of RIPE Policy Proposal 2011-04, "Extension of the Minimum Size for IPv6 Initial Allocation", has been revised based on the community feedback received on the mailing list. We have published the new version (version 2.0) today. As a result, a new Discussion Phase is set for the proposal. Highlights of the changes in version 2.0 are: - The proposed new section 5.1.2 was reworded - Section 5.7 was not removed but it was reworded You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2011-04 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net> before 30 January 2012. Regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

Re: [address-policy-wg] status of 2011-02
by poty＠iiat.ru 13 Dec '11

13 Dec '11

>... we are constraining the IPv6 > address distribution because of ...? > > Jan > There are so many people using as the main and the last argument the concern about weak distribution of IPv6, that I'm personally becoming against anything they suggest. Vladislav Potapov Ru.iiat

6 5

Update in the RIPE document for IPv6 Allocation and Assignment policies
by Emilio Madaio 07 Dec '11

07 Dec '11

Dear colleagues, An editorial correction has been made to ripe-523 "IPv6 Address Allocation and Assignment Policy". The updated document has been renumbered to ripe-538. It is available at: http://www.ripe.net/ripe/docs/ripe-538 There was a mismatch between the policy text and the index title for section 5.4.2. This mismatch occurred between the updates from ripe-421 to ripe-450. Apologies for any inconvenience caused. Kind regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

RIPE NCC address request retracted
by Axel Pawlik 07 Dec '11

07 Dec '11

Dear colleagues, as a matter of good housekeeping I would like to announce that the RIPE NCC has retracted its request for addresses for "Business Operations", as presented at RIPE 63 (http://ripe63.ripe.net/presentations/53-resource-request.pdf). kind regards, Axel Pawlik

7 8

128.0.0.0/16 configured as martians in some routers
by Alex Le Heux 05 Dec '11

05 Dec '11

Dear Colleagues, The RIPE NCC is aware that 128.0.0.0/16 is configured as a martian by default in (some) Juniper OS, even though RFC 5735 and RFC3330 outline that this /16 should no longer be reserved as specialised address space. All allocations that were already issued have been exchanged and for now we will hold this space in quarantine. We urge everyone to change the default behaviour of their Juniper routers: set routing-options martians 128.0.0.0/16 orlonger allow set routing-options martians 191.255.0.0/16 orlonger allow set routing-options martians 223.255.255.0/24 exact allow 128.0.0.0/16 has been added to the RIPE NCC's Debogonising Project: http://www.ris.ripe.net/debogon/ To facilitate testing, the following prefixes are being announced: prefix pinagble address 128.0.0.0/16 128.0.0.1 128.0.8.0/21 128.0.8.1 128.0.24.0/24 128.0.24.1 Best regards, Alex Le Heux Policy Implementation Co-ordinator RIPE NCC

3 3

Final minutes from RIPE 62
by Emilio Madaio 01 Dec '11

01 Dec '11

Dear colleagues, The minutes from the Address Policy Working Group session from RIPE 62 were approved during RIPE 63. The minutes are available here: http://www.ripe.net/ripe/groups/wg/ap/minutes/minutes-from-ripe-62 Best Regards, Emilio Madaio Policy Development Officer RIPE NCC

2 1

Policy Proposal 2010-01 "Temporary Internet Number Assignment Policies" implemented
by Radha Ramphul 30 Nov '11

30 Nov '11

[Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that RIPE Policy Proposal 2010-01,"Temporary Internet Number Assignment Policies", has been implemented. The RIPE NCC is now ready to accept requests for Temporary Internet Number Assignments under this policy. The full proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2010-01 The new policy "Temporary Internet Number Assignment Policies" is available at: https://www.ripe.net/ripe/docs/ripe-526 The following documents now appear online as part of this policy implementation. 1. A new contract template has been formulated which can be used as the agreement between LIRs and End-users. It can be downloaded at: http://ripe.net/lir-services/resource-management/temp-assign-agreement 2. A new request template (currently in text format only) is now available. The LIR portal version will be coming soon. http://www.ripe.net/ripe/docs/ripe-536 3. Supporting notes explaining the various sections of the form and how to complete them have been added as well. http://www.ripe.net/ripe/docs/ripe-535 4. A new FAQ page can be accessed at: https://www.ripe.net/lir-services/resource-management/number-resources/temp… The following resources have been reserved for this purpose: IPv4: 151.216.0.0/13 16-bit ASN: AS58352-AS58367 No reservations have been made for IPv6 and 32-bit ASN. Regards Radha Ramphul RIPE NCC Registration Services

1 0