[news] RIPE Policy Proposals - June Update
Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. There is now new way for you to participate in policy discussions if you wish. The RIPE Forum is a web-based solution that allows you to subscribe, search, read and post to RIPE community mailings lists from your browser. This is entirely optional and the mailing lists will continue to be supported as normal. We invite you to have a look: https://www.ripe.net/participate/mail/forum/ Proposals Open for Discussion: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" 2016-02, “Resource Authentication Key ( RAK ) code for third party authentication” 2016-03, “Locking Down the Final /8 Policy” Proposals Awaiting Input: 2015-04, "RIPE Resource Transfer Policies" Proposal Withdrawn: 2015-05, "Revision of Last /8 Allocation Criteria" Proposal Overviews: PROPOSAL: 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy" OVERVIEW: Aims for a mandatory abuse contact for Legacy Internet Resource Holders in the RIPE Database. STATUS: Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg@ripe.net DEADLINE: 21 June 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01 PROPOSAL: 2016-02, “Resource Authentication Key ( RAK ) code for third party authentication” OVERVIEW: Aims to allow all number resources, in exacts and more specifics, to be authenticated via an API-key that expires on a certain date. STATUS: Extended Discussion Phase WHERE TO COMMENT: RIPE NCC Services Working Group: ncc-services-wg@ripe.net DEADLINE: 29 June 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-02 PROPOSAL: 2016-03, “Locking Down the Final /8 Policy” OVERVIEW: The second version aims to ban transfers of allocations made under the final /8 policy. Several restrictions from the first version of the proposal have been removed. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg@ripe.net DEADLINE: 15 July 2016 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-03 ===== The following proposal is awaiting input before it can go any further in the PDP. PROPOSAL: 2015-04, "RIPE Resource Transfer Policies" OVERVIEW: Aims to create a single transfer policy with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The proposal also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. RIPE NCC IMPACT ANALYSIS: Describes how the 24-month holding period for scarce resources will be applied. STATUS: Review Phase – Awaiting decision from working group chair FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04 The following proposal has been withdrawn. PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria" OVERVIEW: Aimed to allow LIRs to request an additional /22 IPv4 allocation from the RIPE NCC every 18 months. STATUS: Withdrawn - The proposers decided to withdraw the proposal due to the inability to find an acceptable agreement which satisfied all parties. FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05 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-p... We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC
participants (1)
-
Marco Schmidt