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

2014-07, 2014-08, 2014-10, 2014-11 Proposals Accepted (Language Clarification Proposals)
by Marco Schmidt 11 Mar '15

11 Mar '15

Dear colleagues, Consensus has been reached, and the proposals for changes to the following RIPE Documents have been accepted by the RIPE community: ripe-632, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" ripe-452, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" ripe-233, "IPv6 Addresses for Internet Root Servers In The RIPE Region" ripe-476, "Allocating/Assigning Resources to the RIPE NCC" These policy changes replace the term "should" with "must" in cases where the previous wording created unwanted ambiguity in policy documents. You can find the full proposals at: http://www.ripe.net/ripe/policies/proposals/2014-07 http://www.ripe.net/ripe/policies/proposals/2014-08 http://www.ripe.net/ripe/policies/proposals/2014-10 http://www.ripe.net/ripe/policies/proposals/2014-11 The new RIPE Documents are called ripe-634, ripe-635, ripe-636 and ripe-637 and are available at: https://www.ripe.net/ripe/docs/ripe-634 https://www.ripe.net/ripe/docs/ripe-637 https://www.ripe.net/ripe/docs/ripe-636 https://www.ripe.net/ripe/docs/ripe-635 Note: the order of the original documents, proposals and new RIPE Documents in the lists above all correspond to one another. These proposals are implemented with immediate effect, as the RIPE NCC's procedures, tools and documentation are already in line with the policy understanding that these updates reflect. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
by sandrabrown＠ipv4marketgroup.com 11 Mar '15

11 Mar '15

Hi Andrea, At APNIC39 in Fukuoka, I spoke with Adam Gosling of APNIC. He suggested that the APNIC EC would wait for an interpretation and implementation of the new RIPE inter-RIR policy before making a decision. But, as reflected in the discussion already made, he did feel that an APNIC to RIPE transfer would not be subjected to needs justification because he (and APNIC in general) do not interpret APNIC policy as requiring needs justification if the receiving RIR does not. Two comments on this: Why would APNIC to RIPE not require needs justification when APNIC to APNIC does? Secondly, there are so few IPs within APNIC, how often will there ever be IPs transferred from APNIC to RIPE region under the inter-RIR policy? I would not think this is a big transfer path. The reality is that the huge supply of IPs for transfer to RIPE is in ARIN region and this supply is the target of the new RIPE inter-RIR policy. If APNIC never allows transfer to RIPE region, this would be ok from the perspective of supply to RIPE region. In fact this would be preferable to APNIC allowing transfers with no needs justification, such that ARIN then flipped its position to block transfers to APNIC because they could subsequently to transferred to RIPE. A more tangible flaw is that APNIC has no time delay on re-transfers. While ARIN would not allow a transferred block to be re-transferred for 12 months and RIPE would not allow a transferred block to be re-transferred for 24 months, APNIC has no limitation. But this problem exists today for IPs transferred to APNIC; they can immediately be re-transferred within APNIC. No change just because they could now be transferred to RIPE region, so I can't see ARIN complaining about this now. ARIN being concerned with APNIC allowing transfers to APNIC being subsequently transferred to RIPE should not influence the implementation of direct transfers from ARIN to RIPE using the new needs justification criteria of 50% use over 5 years that ARIN had agreed was compatible with its policy. Based on this analysis, I don't see the initial buy-in or non-buy-in by APNIC as a concern. It is ARIN as a supply that is needed. Sandra Brown Message: 3 Date: Tue, 10 Mar 2015 17:03:03 +0000 From: Nick Hilliard <nick(a)inex.ie> To: Andrea Cima <andrea(a)ripe.net>, Address Policy Working Group <address-policy-wg(a)ripe.net> Subject: Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC? Message-ID: <54FF23C7.4020403(a)inex.ie> Content-Type: text/plain; charset=utf-8 Hi Andrea, On 10/03/2015 16:05, Andrea Cima wrote: > While I cannot answer on behalf of the other RIRs, we have given an > update about the inter-RIR transfer policy proposal last week, during > APNIC 39. I hope the video and transcripts will provide you with the > clarification requested (please see session Policy SIG-3) thanks for the reference. The context is located at pages 35-49 of: https://conference.apnic.net/data/39/5-March-Policy-SIG-3.txt and at: https://www.youtube.com/watch?v=2iKK_8iJU6E#t=1h09m11s Nick

1 0

2014-13 Last Call for Comments (Allow AS Number Transfers)
by Marco Schmidt 11 Mar '15

11 Mar '15

Dear colleagues, The proposal described in 2014-13, "Allow AS Number Transfers", is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 10 March 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-13 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 10 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

4 4

2014-07, 2014-08, 2014-10, 2014-11 Last Call for Comments (Language Clarification Proposals)
by Marco Schmidt 10 Mar '15

10 Mar '15

Dear colleagues, The proposals described in - 2014-07, Language Clarification in "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" - 2014-08, Language Clarification in "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" - 2014-10, Language Clarification in "IPv6 Addresses for Internet Root Servers In The RIPE Region" - 2014-11, Language Clarification for "Allocating/Assigning Resources to the RIPE NCC", are now in the Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for these proposal has been reached and they will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose one of these proposal. Any objection must be made by 9 March 2015 and must be supported by an explanation. You can find the full proposals at: https://www.ripe.net/ripe/policies/proposals/2014-07 https://www.ripe.net/ripe/policies/proposals/2014-08 https://www.ripe.net/ripe/policies/proposals/2014-10 https://www.ripe.net/ripe/policies/proposals/2014-11 Please e-mail any final comments about these proposals to address-policy-wg(a)ripe.net before 9 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

2 1

2015-01 New Policy Proposal (Alignment of Transfer Requirements for IPv4 Allocations)
by Marco Schmidt 10 Mar '15

10 Mar '15

Dear colleagues, A proposed change to RIPE Document "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2015-01 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 12 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

22 57

Policy proposal 2014-03 "Remove Multihoming Requirement for AS Number Assignments"
by Sander Steffann 09 Mar '15

09 Mar '15

Hello working group, There has been a lot of discussion regarding policy proposal 2014-03 "Remove Multihoming Requirement for AS Number Assignments". There has been discussion on the the content of the proposal, the impact that the RIPE NCC charging scheme has and on the 'garbage collection' effects of the different ideas people have. We clearly don't have consensus on how to proceed. The working group chairs (Gert Döring and myself) have therefore decided to extend the review phase. Because of the potential impact of the RIPE NCC charging scheme and because the ideas on this policy proposal seem to be diverging at the moment we have decided to extend it to after the RIPE meeting in Amsterdam. We realise this is a relatively long time but we feel that having a live discussion on this policy proposal is the best way forward. Marco will send the formal announcement shortly. Cheers, Sander Steffann Gert Döring APWG chairs

1 0

2014-05 Last Call for Comments (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 05 Mar '15

05 Mar '15

Dear colleagues, The proposal described in 2014-05, "Policy for Inter-RIR Transfers of Internet Resources", is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 3 April 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-05 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 3 April 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-04 Proposal Accepted (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 04 Mar '15

04 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-623, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-04 The new RIPE Document is called ripe-632 and is available at: https://www.ripe.net/ripe/docs/ripe-632 The RIPE NCC has already begun preparations to implement this policy proposal. We estimate it may take a few weeks to make these changes and fully implement the policy proposal. Details of the implementation status are available at: https://www.ripe.net/lir-services/resource-management/policy-implementation… We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-04 New Draft Document and Impact Analysis Published (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 03 Mar '15

03 Mar '15

Dear colleagues, The draft document for version 3.0 of the policy proposal 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8", has now been published, along with an impact analysis conducted by the RIPE NCC. Some of the differences from version 2.0 include: - Removal of the IPv6 requirement to receive Pv4 addresses from the RIPE NCC - Related wording adjustments in the title, summary and rationale of the proposal You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-04 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-04/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 7 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

17 23

New on RIPE Labs: RIPE NCC Membership - Developments After Reaching the Last /8
by Mirjam Kuehne 23 Feb '15

23 Feb '15

Dear colleagues, On 14 September 2012, the RIPE NCC started allocating IPv4 addresses based on the last /8 policy. With more than two years passed, we look at the effects this had on membership numbers and demographics. We also look at what the last /8 policy meant for IPv6 uptake. Please find the results on RIPE Labs: https://labs.ripe.net/Members/wilhelm/ripe-ncc-membership-statistics-2014 Kind regards, Mirjm Kuehne RIPE NCC

1 0