[news] RIPE Policy Proposals - June Update

Dear colleagues,

Please find below the monthly overview of open policy proposals and the 
stage each has 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:
2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation" – Discussion 
open until 7 July 2015

Proposals in Last Call:
2015-01, "Alignment of Transfer Requirements for IPv4 Allocations"– Last 
Call until 21 July 2015

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

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.
RIPE NCC IMPACT ANALYSIS: Includes the point that little impact is 
expected in terms of routing table growth.
STATUS: Review Phase
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 7 July 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02

=====

The following proposal is in Last Call. Rough consensus has been 
declared and the purpose of this phase is to give the community a final 
opportunity to present any well-justified objections to the proposal 
that have not already been raised and addressed during the previous 
discussion phases.

PROPOSAL: 2015-01, "Alignment of Transfer Requirements for IPv4 
Allocations"
OVERVIEW: Currently, IPv4 allocations received from another LIR can only 
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.
RIPE NCC IMPACT ANALYSIS: Includes the point that currently around 10% 
of the allocations made by the RIPE NCC are transferred shortly after 
they have been allocated.
STATUS: Last Call
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 21 July 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-01

=====

The following proposals are awaiting input before they proceed in the PDP.

PROPOSAL: 2015-03, "Assessment Criteria for IPv6 Initial Allocation Size"
OVERVIEW: This proposal aims to remove the requirement that large IPv6 
allocations are based only on existing users and network infrastructure. 
As a result of this policy implementation, the RIPE NCC will be able to 
consider additional criteria when evaluating IPv6 allocation requests.
STATUS: Discussion Phase - Awaiting impact analysis*
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
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2014-03

*The goal of the impact analysis is to provide supporting information to 
facilitate discussions about the proposal and to outline the proposal’s 
possible impact if it were to be accepted.

=====

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/ripe-list/attachments/20150624/93b31646/attachment.html>