December 2011 - address-policy-wg

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] status of 2011-02
by poty＠iiat.ru 12 Dec '11

12 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 06 Dec '11

06 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