This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[news] RIPE Policy Proposals - April Update
- Previous message (by thread): RIPE Labs article on how Website Redesign affects Policy Proposal Discussions
- Next message (by thread): RIPE Programme Committee elections at RIPE70
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Thu Apr 23 10:04:14 CEST 2015
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: 2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation" – discussion open until 13 May 2015 2014-03, "Remove Multihoming Requirement for AS Number Assignments" – discussion open until 19 May 2015 Proposals awaiting impact analysis: 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations" Proposals accepted: 2014-05, "Policy for Inter-RIR Transfers of Internet Resources" Proposal Overviews: PROPOSAL: 2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation" Overview: This proposal aims to remove the requirement that LIRs should return their IPv6 Provider Independent (PI) assignment when requesting an IPv6 allocation. STATUS: Discussion Phase WHERE TO COMMENT: The Address Policy Working Group – address-policy-wg at ripe.net DEADLINE: 13 May 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02 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 – address-policy-wg at ripe.net DEADLINE: 19 May 2015 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03 ===== 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 Impact Analysis* FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-01 *The goal of the impact analysis is to provide supporting information to facilitate discussions about the proposal and to outline its possible impact if it were to be accepted. ===== The following proposal has been accepted since the last RIPE Policy Proposal Update. The RIPE NCC has started the implementation of this policy change. 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: Accepted EXPECTED IMPLEMENTATION: August 2015* FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-05 *Note: the RIPE NCC will only follow a policy change once it has been completely implemented and announced to the community. This means that inter-RIR transfers will only be possible from around August 2015. The implementation status of accepted policy proposals can be reviewed here: https://www.ripe.net/manage-ips-and-asns/resource-management/policy-implementation-status The RIPE NCC provides an overview of current RIPE Policy Proposals on www.ripe.net: https://www.ripe.net/participate/policies/current-proposals/current-policy-proposals During the upcoming RIPE Meeting, the Address Policy Working Group will hold two sessions where ongoing and possible future policy proposals will be discussed. If you can not attend the RIPE Meeting in person, we invite you to join remotely. A live webcast and IRC chat facility will be available for remote participation. The two sessions will begin on 13 May at 7:00 and 9:00 (UTC). The remote participation will be available at: https://ripe70.ripe.net/ We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC
- Previous message (by thread): RIPE Labs article on how Website Redesign affects Policy Proposal Discussions
- Next message (by thread): RIPE Programme Committee elections at RIPE70
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]