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 discussions about a proposal, please do so on
the relevant working group mailing list.
Proposals Open for Discussion:
New proposal: 2015-03, "Assessment Criteria for IPv6 Initial Allocation
Size" – discussion open until 27 May 2015
2015-01, "Alignment of Transfer Requirements for IPv4 Allocations"–
discussion
open until 9 June 2015
Proposals Awaiting Impact Analysis:
2014-03, "Remove Multihoming Requirement for AS Number Assignments"
2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation"
Proposal Overviews:
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, when evaluating
IPv6 allocation requests, will be able to consider additional criteria.
STATUS: Discussion phase
WHERE TO COMMENT: Address Policy Working Group: [email protected]
DEADLINE: 27 May 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-03
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: Review phase
WHERE TO COMMENT: Address Policy Working Group: [email protected]
DEADLINE: 09 June 2015
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-01
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.
STATUS: Discussion phase - awaiting impact analysis*
FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2015-02
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. It is proposed to remove the need for
evaluation, limit the number of AS Numbers per organisation to 1,000,
and 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 and following new
impact analysis*
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
During the RIPE 70 Meeting, the Address Policy Working Group held two
sessions on 13 May, where ongoing and possible future policy proposals
were discussed. Besides the proposals mentioned above, ideas for two new
policy proposals were also presented. One proposal would unify the
transfer policies for the different Internet resources into one policy
document. The other proposal would aim to allocate more IPv4 address
space from the RIPE NCC to its members. A video with the presentations
for these ideas can be found online:
https://ripe70.ripe.net/archives/video/55/
We look forward to your involvement in the PDP.
Kind regards,
Marco Schmidt
RIPE Policy Development Officer
RIPE NCC