[news] RIPE Policy Proposals - July Update

Dear colleagues,

Please find below the 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:
2015-03, “Assessment Criteria for IPv6 Initial Allocation Size” - 
discussion open until 7 August 2015

Proposals in Last Call:
2015-02, “Keep IPv6 PI When Requesting IPv6 Allocation” - Last Call 
until 6 August 2015

Proposals accepted:
2015-01, “Alignment of Transfer Requirements for IPv4 Allocations”

Proposals Awaiting Input:
2014-03, “Remove Multihoming Requirement for AS Number Assignments”

Proposal Overviews:

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
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 7 August 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-03

=====

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-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: Last Call
WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net
DEADLINE: 6 August 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02

=====

The following proposal has been accepted since the last RIPE Policy 
Proposal Update.

PROPOSAL: 2015-01, “Alignment of Transfer Requirements for IPv4 
Allocations”
OVERVIEW: Currently, IPv4 allocations received from another LIR can only 
be re-allocated after a 24 months, while IPv4 allocations made by the 
RIPE NCC can be transferred immediately. This proposal aims to align the 
transfer requirements by applying the same 24-month holding period to 
all IPv4 allocations.
STATUS: Accepted
EXPECTED IMPLEMENTATION: Implemented on 23 July 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-01

=====

The following proposal is awaiting input before it proceeds in the PDP.

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