November 2019 - policy-announce

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