- policy-announce - mailman.ripe.net

2017-02 New Policy Proposal (Regular abuse-c Validation)
by Marco Schmidt 07 Sep '17

07 Sep '17

Dear colleagues, A new RIPE Policy proposal, 2017-02, "Regular abuse-c Validation", is now available for discussion. The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-c:" information and to follow up in cases where contact information is found to be invalid. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2017-02 As per the RIPE Policy Development Process (PDP), the purpose of this four-week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the RIPE Working Group Chairs, decides how to proceed with the proposal. We encourage you to review this proposal and send your comments to <anti-abuse-wg(a)ripe.net> before 6 October 2017. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2017-01 New Policy Proposal (Publish statistics on Intra-RIR Legacy updates)
by Marco Schmidt 25 Apr '17

25 Apr '17

Dear colleagues, A new RIPE Policy proposal, 2017-01, "Publish statistics on Intra-RIR Legacy updates" is now available for discussion. The goal of this proposal is to require the RIPE NCC to publish all changes to the holdership of legacy resources in the existing transfer statistics. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2017-01 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 24 May 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

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

2016-05 Last Call for Comments (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
by Marco Schmidt 27 Feb '17

27 Feb '17

Dear colleagues, Proposal 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies", is now in Concluding Phase. The goal of this proposal is to match the subsequent IPv6 allocation requirements with the initial allocation requirements. The WG Chair has declared that rough consensus has been reached and the proposal will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of this four week Concluding Phase is to give an opportunity to present well-justified objections for those who missed the previous two phases and wish to oppose the proposal. Any objection must be made by 28 March 2017 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG Chairs for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-05 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 28 March 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-04 Last Call for Comments (RIPE Resource Transfer Policies)
by Marco Schmidt 08 Feb '17

08 Feb '17

Dear colleagues, Proposal 2015-04, "RIPE Resource Transfer Policies", is now in Concluding Phase. The goal of this proposal is 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. The WG Chair has declared that rough consensus has been reached and the proposal will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of this four week Concluding Phase is to give an opportunity to present well-justified objections for those who missed the previous two phases and wish to oppose the proposal. Any objection must be made by 9 March 2017 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG Chairs for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-04 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 9 March 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-05 New Version and Impact Analysis Published (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
by Marco Schmidt 24 Jan '17

24 Jan '17

Dear colleagues, The draft documents for version 2.0 of the policy proposal 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies" has now been published, along with an impact analysis conducted by the RIPE NCC. The goal of this proposal is to match the subsequent IPv6 allocation requirements with the initial allocation requirements. Some of the differences from version 1.0 include: - Revert initial changes to the HD-ratio calculation - Clarification as to when the new need justifies a subsequent allocation - Clarification as to what the subsequent allocation size will be based on You can find the full proposal and the impact analysis at: https://www.ripe.net/participate/policies/proposals/2016-05 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2016-05/draft We encourage you to read the draft document and send any comments to <address-policy-wg(a)ripe.net> before 22 February 2017. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-04 Review Phase: Draft Document and Impact Analysis Published (IPv6 PI Sub-assignment Clarification)
by Marco Schmidt 02 Jan '17

02 Jan '17

Dear colleagues, The draft document for the proposal described in 2016-04, "IPv6 PI Sub-assignment Clarification" has been published. The impact analysis that was conducted for this proposal has also been published. The goal of this proposal is to define sub-assignments in IPv6 PI assignments as subnets of /64 and shorter. You can find the full proposal and the impact analysis at: https://www.ripe.net/participate/policies/proposals/2016-04 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2016-04/draft We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 31 January 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-05 New Policy Proposal (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
by Marco Schmidt 24 Nov '16

24 Nov '16

Dear colleagues, A new RIPE Policy proposal 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies" is now available for discussion. The goal of this proposal is to match the subsequent IPv6 allocation requirements with the initial allocation requirements. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-05 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 23 December 2016. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-03 Policy Proposal Withdrawn (Locking Down the Final /8 Policy)
by Marco Schmidt 15 Nov '16

15 Nov '16

Dear colleagues, The proposal 2016-03, "Locking Down the Final /8 Policy" has been withdrawn. It is now archived and can be found at: https://www.ripe.net/participate/policies/archived-policy-proposals/archive… Reason for withdrawal: The proposer decided to abandon the proposal as he felt that the ongoing discussion was damaging the RIPE community’s reputation. As nobody stepped forward to take over the authorship this proposal, the proposal was withdrawn. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0