policy-announce

Download

policy-announce@ripe.net

March 2017

1 participants
2 discussions

2016-05 Proposal Accepted (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
by Marco Schmidt 30 Mar '17

30 Mar '17

Dear colleagues, Consensus has been reached on 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies". This policy change matches the subsequent IPv6 allocation requirements with the initial allocation requirements. In addition to the existing justification based on past utilisation, it is now also possible to document new needs, including the number of users, the extent of the organisation's infrastructure, the hierarchical and geographical structuring of the organisation, the segmentation of infrastructure for security and the planned longevity of the allocation. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-05 The new RIPE Document is ripe-684 and is available at: https://www.ripe.net/publications/docs/ripe-684 We estimate that this proposal will take around two weeks to fully implement. We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-04 Proposal Accepted (RIPE Resource Transfer Policies)
by Marco Schmidt 14 Mar '17

14 Mar '17

Dear colleagues, Consensus has been reached on 2015-04, "RIPE Resource Transfer Policies". This policy change created a single policy document with all relevant information on the transfer of Internet number resources, replacing text in several RIPE Policies. The policy change also introduces a 24-month holding period for IPv4 addresses and 16-bit ASNs after any change of holdership. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-04 The new RIPE Document is ripe-682, "RIPE Resource Transfer Policies" and is available at: https://www.ripe.net/publications/docs/ripe-682 The following RIPE policies haven been updated as well and received a new document number: ripe-679, "Autonomous System (AS) Number Assignment Policies" https://www.ripe.net/publications/docs/ripe-679 ripe-680, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" https://www.ripe.net/publications/docs/ripe-680 ripe-681, "IPv6 Address Allocation and Assignment Policy" https://www.ripe.net/publications/docs/ripe-681 The following RIPE policy has been marked as obsolete and replaced by ripe-682: ripe-644, "Policy for Inter-RIR Transfers of Internet Resources" We estimate that this proposal will take around three months to fully implement. In order to ensure a correct and consistent handling of requests, the current procedures remain in place until the implementation is completed. This applies in particular to transfers of IPv4 and 16-bit ASNs. Details of the implementation status are available at: https://www.ripe.net/manage-ips-and-asns/resource-management/policy-impleme… We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0