<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <meta name="Title" content=""> Dear colleagues, Please find below the monthly overview of open policy proposals and the stage they have reached in the RIPE Policy Development Process (PDP). If you wish to join the discussions about a proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: 2014-03, "Remove Multihoming Requirement for AS Number Assignments" – discussion open until 19 May 2015 Proposals at Last Call: 2014-05, "Policy for Inter-RIR Transfers of Internet Resources" - opinion can be stated until 3 April 2015 Proposals awaiting decision from proposer: 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations" Proposals accepted: 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8" 2014-06, "Publication of Sponsoring LIR for Legacy Internet Resource Holders" 2014-12, "Allow IPv6 Transfers" 2014-13, "Allow AS Number Transfers" Proposal Overviews: PROPOSAL: 2014-03, "Remove Multihoming Requirement for AS Number Assignments" OVERVIEW: This proposal aims to ease the requirements when requesting an Autonomous System (AS) Number. It is proposed to remove the need evaluation, limit the amount of AS Numbers per organization to 1,000 and require that 16-bit AS Numbers are multihomed after nine months. RIPE NCC IMPACT ANALYSIS: Includes point that it will be the End User that decides if the need for an AS Number is technically reasonable. STATUS: Review Phase (extended) WHERE TO COMMENT: The Address Policy Working Group – <a class="moz-txt-link-abbreviated" href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a> DEADLINE: 19 May 2015 FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2014-03">http://www.ripe.net/ripe/policies/proposals/2014-03</a> ===== The following proposal is in Last Call. Rough consensus has been declared and the purpose of this phase is to give the community a final opportunity to present well-justified objections in case anyone wants to oppose the proposal. PROPOSAL: 2014-05, "Policy for Inter-RIR Transfers of Internet Resources" OVERVIEW: This proposal aims to allow the global transfer of Internet resources. For transfers to the RIPE NCC service region from RIRs that require needs-based policies, recipients must provide the RIPE NCC with a plan for the use of at least 50% of the transferred resources within five years. STATUS: Last Call WHERE TO COMMENT: The Address Policy Working Group – <a class="moz-txt-link-abbreviated" href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a> DEADLINE: 3 April FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2014-05">http://www.ripe.net/ripe/policies/proposals/2014-05</a> ===== The following proposal is awaiting decision from proposer on how to proceed. PROPOSAL: 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations" OVERVIEW: Currently IPv4 allocations received from another LIR only can be re-allocated after 24 months, while IPv4 allocations made by the RIPE NCC can be transferred immediately. This proposal aims to align the transfer requirements with a 24 month holding period for all IPv4 allocations. STATUS: Discussion Phase - Awaiting Decision from Proposer FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2015-01">http://www.ripe.net/ripe/policies/proposals/2015-01</a> ===== The following proposals have been accepted since the last RIPE Policy Proposal Update. The RIPE NCC has started the implementation of these policy changes. The RIPE NCC will follow the policy change once the implementation is complete and the new procedures are in place. PROPOSAL: 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8" OVERVIEW: Previously, in order to receive a final /22 IPv4 allocation from the RIPE NCC, Local Internet Registries (LIRs) must have an IPv6 allocation in the RIPE NCC service region. This proposal removed this requirement. STATUS: Accepted EXPECTED IMPLEMENTATION: Implemented on 18 March 2015 FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2014-04">http://www.ripe.net/ripe/policies/proposals/2014-04</a> PROPOSAL: 2014-06, "Publication of Sponsoring LIR for Legacy Internet Resource Holders" OVERVIEW: This proposal requested the RIPE NCC to publish the link between legacy holders and their sponsoring Local Internet Registry (LIR). STATUS: Accepted EXPECTED IMPLEMENTATION: April 2015 FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2014-06">http://www.ripe.net/ripe/policies/proposals/2014-06</a> PROPOSAL: 2014-12, "Allow IPv6 Transfers" OVERVIEW: This proposal allowed the transfer of IPv6 allocations and IPv6 Provider Independent (PI) assignments. STATUS: Accepted EXPECTED IMPLEMENTATION: June/July 2015 FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2014-12">http://www.ripe.net/ripe/policies/proposals/2014-12</a> PROPOSAL: 2014-13, "Allow AS Number Transfers" OVERVIEW: This proposal allowed to transfer Autonomous System (AS) numbers. STATUS: Accepted EXPECTED IMPLEMENTATION: June/July 2015 FULL PROPOSAL: <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/policies/proposals/2014-13">http://www.ripe.net/ripe/policies/proposals/2014-13</a> The implementation status of accepted policy proposals can be reviewed here: <a class="moz-txt-link-freetext" href="https://www.ripe.net/lir-services/resource-management/policy-implementation-status">https://www.ripe.net/lir-services/resource-management/policy-implementation-status</a> The RIPE NCC provides an overview of current RIPE Policy Proposals on <a class="moz-txt-link-abbreviated" href="http://www.ripe.net">www.ripe.net</a>: <a class="moz-txt-link-freetext" href="https://www.ripe.net/ripe/policies/current-proposals/current-policy-proposals">https://www.ripe.net/ripe/policies/current-proposals/current-policy-proposals</a> Full information about how the PDP works is available in ripe-614, "Policy Development Process in RIPE": <a class="moz-txt-link-freetext" href="http://www.ripe.net/ripe/docs/ripe-614">http://www.ripe.net/ripe/docs/ripe-614</a> We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC <meta name="Keywords" content=""> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="ProgId" content="Word.Document"> <meta name="Generator" content="Microsoft Word 14"> <meta name="Originator" content="Microsoft Word 14"> <link rel="File-List" href="file://localhost/Users/mschmidt/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml">  <link rel="themeData" href="file://localhost/Users/mschmidt/Library/Caches/TemporaryItems/msoclip/0/clip_themedata.xml">  <style>  </style> </body> </html>