[ripe-list] [news] RIPE Policy Proposals - May 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.

Proposals Open for Discussion:
NEW: 2016-02, "Resource Authentication Key ( RAK ) code for third party 
authentication"
NEW: 2016-03, "Locking Down the Final /8 Policy"

Proposals Awaiting Input:
2015-05, "Revision of Last /8 Allocation Criteria"
2015-04, "RIPE Resource Transfer Policies"
2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy"


Proposal Overviews:

NEW 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: Discussion Phase
WHERE TO COMMENT: RIPE NCC Services Working Group: ncc-services-wg at ripe.net
DEADLINE: 31 May 2016
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-02

NEW PROPOSAL: 2016-03, "Locking Down the Final /8 Policy"
OVERVIEW: Aims to limit IPv4 from the remaining address pool to one /22 
per LIR (regardless of how they were received). These allocations will 
receive a separate status with several restrictions, including that the 
address space will not be transferrable.
STATUS: Discussion Phase
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 15 June 2016
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-03

=====

The following proposals are awaiting input before they 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

PROPOSAL: 2015-05, "Revision of Last /8 Allocation Criteria"
OVERVIEW: Aims to allow LIRs to request an additional /22 IPv4 
allocation from the RIPE NCC every 18 months. The latest version of the 
proposal introduces several requirements, such as that the LIR cannot 
hold more than a /20 of IPv4, must document their IPv6 deployment, and 
must not have transferred any IPv4 address space before.
STATUS: Discussion Phase – Awaiting decision from proposer
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-05

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 – Awaiting decision from proposer
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-01


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 25 May at 7:00 and 9:00 (UTC).

The remote participation will be available at:
https://ripe72.ripe.net/

We look forward to your involvement in the PDP.

Kind regards,

Marco Schmidt
RIPE Policy Development Officer
RIPE NCC