- policy-announce - mailman.ripe.net

Automatic updates to the RIPE Policy Document "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"
by Petrit Hasani 25 Nov '19

25 Nov '19

Dear Colleagues, As a result of the depletion of the RIPE NCC free IPv4 pool, the following automatic updates were initiated to the "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", as described in the policy document itself. 1) On Friday, 22 November 2019, in accordance with section 5.2 "Unforeseen circumstances" of the policy document, the RIPE NCC started distributing equivalents of /22 IPv4 allocations from the /16 IPv4 block that was reserved for unforeseen circumstances. The relevant section [5.2 “Unforeseen circumstances”] has therefore been deleted from the document and the subsequent sections have been renumbered accordingly. 2) Today, Monday 25 November 2019, the RIPE NCC distributed the last equivalent of /22 IPv4 address space from the available pool. Therefore, as described in the policy document, section 5.1 was replaced with the contents of section 5.1bis, and section 5.1bis was deleted from the policy document. Section 5.1 "Allocations made by the RIPE NCC to LIRs" now states: "On application for IPv4 resources LIRs will receive IPv4 addresses according to the following: 1. All allocation requests are placed on a first-come-first-served waiting list. No guarantees are given about the waiting time. 2. The size of the allocation made will be exactly one /24. 3. The sum of all allocations made to a single LIR by the RIPE NCC is limited to a maximum of 256 IPv4 addresses (a single /24). If this allocation limit has been reached or exceeded, an LIR cannot request an IPv4 allocation under this policy." The updated RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is available at: https://www.ripe.net/publications/docs/ripe-733 Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-07 Discussion Period extended until 19 December (Default assignment size for IXPs)
by Petrit Hasani 20 Nov '19

20 Nov '19

Dear colleagues, The Discussion Period for the policy proposal 2019-07, "Default assignment size for IXPs" has been extended until 19 December 2019. This proposal aims to change the default IXP assignment size from a /24 to a needs-based model, with a /27 as a minimum. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-07 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net>. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-04 Discussion Period extended until 9 December 2019 (Validation of "abuse-mailbox")
by Petrit Hasani 08 Nov '19

08 Nov '19

Dear colleagues, The Discussion Period for the policy proposal 2019-04, "Validation of "abuse-mailbox"" has been extended until 09 December 2019. This proposal aims to have the RIPE NCC validate "abuse-c:" information more often, and introduces a new validation process that requires input from resource holders. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-04 We encourage you to review this proposal and send your comments to <anti-abuse-wg(a)ripe.net>. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2018-06 Proposal Accepted (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
by Petrit Hasani 06 Nov '19

06 Nov '19

Dear colleagues, Consensus has been reached on 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". This proposal aimed at creating a process to delete a non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-06 The new RIPE Document is called ripe-731 and is available at: https://www.ripe.net/publications/docs/ripe-731 We estimate that this proposal will take around two to three months 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 us with your input. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
by Petrit Hasani 31 Oct '19

31 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space" is now available for discussion. This proposal aims to instructs the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-08 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 <routing-wg(a)ripe.net> before 29 November 2019. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-07 New Policy Proposal (Default assignment size for IXPs)
by Marco Schmidt 15 Oct '19

15 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-07, "Default assignment size for IXPs" is now available for discussion. This proposal aims to change the default IXP assignment size from a /24 to a needs-based model, with a /27 as a minimum. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-07 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 13 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-05 Proposal Accepted (Revised IPv4 assignment policy for IXPs)
by Marco Schmidt 10 Oct '19

10 Oct '19

Dear colleagues, Consensus has been reached on 2019-05, "Revised IPv4 assignment policy for IXPs". This proposal aimed to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 The new RIPE Document is called ripe-730 and is available at: https://www.ripe.net/publications/docs/ripe-730 We have already implemented the pool management part of this proposal (185.0.0.0/16 and the IPv4 fragments smaller than /24 have been added to the reserved IPv4 pool for IXPs). We estimate that this proposal will take around two months 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 us with your input. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy)
by Marco Schmidt 08 Oct '19

08 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-06, "Multiple Editorial Changes in IPv6 Policy" is now available for discussion. This proposal aims to remove obsoleted text and simplify the IPv6 policy. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-06 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 6 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-06 Last Call (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
by Marco Schmidt 07 Oct '19

07 Oct '19

Dear colleagues, Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in Concluding Phase. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. The WG co-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 before 5 November 2019 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 co-chairs for final consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-06 Please e-mail any final comments about this proposal to <routing-wg(a)ripe.net> before 5 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-03 Policy Proposal Withdrawn (Resource Hijacking is a RIPE Policy Violation)
by Marco Schmidt 02 Oct '19

02 Oct '19

Dear colleagues, The policy proposal 2019-03, "Resource Hijacking is a RIPE Policy Violation" has been withdrawn. This proposal aimed to define that BGP hijacking is not accepted as normal practice within the RIPE NCC service region. The proposal is archived and can be found at: https://www.ripe.net/participate/policies/archived-policy-proposals/archive… Reason for withdrawal: The proposers felt they were unable to address concerns that the policy would expose the RIPE NCC to unacceptable liability risks. These concerns were expressed by both the Executive Board and some community members. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0