[ncc-announce] [news] RIPE Policy Proposals - November 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.
The RIPE Forum provides an easy access to all working group mailing 
lists https://www.ripe.net/participate/mail/forum/

Proposals Open for Discussion:
NEW: 2016-04, “IPv6 PI Sub-assignment Clarification”

Proposals Awaiting Input:
2015-04, "RIPE Resource Transfer Policies"

Proposal Withdrawn:
2016-03, “Locking Down the Final /8 Policy”

Proposal Overview:

NEW PROPOSAL: 2016-04, “IPv6 PI Sub-assignment Clarification”
OVERVIEW:  The goal of this proposal is to define sub-assignments in 
IPv6 PI assignments as subnets of /64 and shorter.
STATUS: Discussion Phase
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 21 November 2016
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-04

=====

The following proposal is 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

=====

The following proposal has been withdrawn.

PROPOSAL: 2016-03, “Locking Down the Final /8 Policy”
OVERVIEW: This proposal aimed to ban transfers of allocations made under 
the final /8 policy.
STATUS: Withdrawn. The proposer decided to abandon the proposal as he 
felt that the ongoing discussion was damaging the RIPE community’s 
reputation. As nobody stepped forward to take over the authorship of 
this proposal, the proposal was withdrawn.
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-03

The RIPE NCC provides an overview of current RIPE Policy Proposals here:
https://www.ripe.net/participate/policies/current-proposals/current-policy-proposals

We look forward to your involvement in the PDP.

Kind regards,

Marco Schmidt
RIPE Policy Development Officer
RIPE NCC