[ncc-announce] [news] RIPE Policy Proposals - August Update

Dear colleagues,

Please find below our 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 discussion about a particular proposal, please 
do so on the relevant working group mailing list.

Proposals Open for Discussion:
NEW: 2015-04, “RIPE Resource Transfer Policies” – Discussion Phase until 
14 September 2015

Proposals Accepted:
2015-02, “Keep IPv6 PI When Requesting IPv6 Allocation”

Proposals Awaiting Input:
2015-03, “Assessment Criteria for IPv6 Initial Allocation Size”
2014-03, “Remove Multihoming Requirement for AS Number Assignments”


Proposal Overviews:

NEW PROPOSAL: 2015-04, “RIPE Resource Transfer Policies”
OVERVIEW: This proposal 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.
STATUS: Discussion Phase
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 14 September 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-04

=====

The following proposal has been accepted since the last update.

PROPOSAL: 2015-02, “Keep IPv6 PI When Requesting IPv6 Allocation”
OVERVIEW: This proposal removes the requirement that LIRs must return 
their IPv6 Provider Independent (PI) assignment when requesting an IPv6 
allocation.
STATUS: Accepted
IMPLEMENTATION: Implemented on 10 August 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02

=====

The following proposals are awaiting input before they go any further in 
the PDP.

PROPOSAL: 2015-03, “Assessment Criteria for IPv6 Initial Allocation Size”
OVERVIEW: This proposal introduces new criteria for the evaluation of 
large IPv6 allocation requests. These new criteria are hierarchical and 
geographical structure and segmentation for security and planned 
longevity. The current requirements, number of users and extent of 
infrastructure, are retained.
RIPE NCC IMPACT ANALYSIS: Includes the RIPE NCC’s understanding of what 
are reasonable limits for each of the criteria.
STATUS: Review Phase - awaiting decision from Working Group Chair
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-03

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. To this end, the following actions are 
proposed:
- Remove the need for evaluation
- Limit the number of AS Numbers per organisation to 1,000
- Require that 16-bit AS Numbers are multihomed after nine months
RIPE NCC IMPACT ANALYSIS: Includes the point that it will be the End 
User that decides if the need for an AS Number is technically reasonable.
STATUS: Review Phase - awaiting new proposal version
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03

=====

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

We look forward to your involvement in the PDP.

Kind regards,

Marco Schmidt
RIPE Policy Development Officer
RIPE NCC