From phasani at ripe.net Mon Dec 9 11:06:28 2019 From: phasani at ripe.net (Petrit Hasani) Date: Mon, 9 Dec 2019 11:06:28 +0100 Subject: [address-policy-wg] 2019-06 Review Phase (Multiple Editorial Changes in IPv6 Policy) Message-ID: <8615449F-32E5-4237-8621-8835F5196076@ripe.net> Dear colleagues, Policy proposal 2019-06, "Multiple Editorial Changes in IPv6 Policy" is now in the Review Phase. This proposal aims to remove unnecessary text and simplify the IPv6 policy. The proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - Clarifies the definition of 'end site' The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community?s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-06 https://www.ripe.net/participate/policies/proposals/2019-06#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-06/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussion of the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to before 7 January 2020. -- Petrit Hasani Policy Officer RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: From npediaditi at ripe.net Fri Dec 13 15:38:19 2019 From: npediaditi at ripe.net (Nikolas Pediaditis) Date: Fri, 13 Dec 2019 15:38:19 +0100 Subject: [address-policy-wg] A list of actions during quarantine In-Reply-To: References: Message-ID: <23253C34-8FF9-4F6B-8D9E-B4D49AE70C27@ripe.net> Dear T?ma, Thank you for your question and my apologies for the delayed reply. We de-register resources in accordance with "Closure of Members, Deregistration of Internet Resources and Legacy Internet Resources?: https://www.ripe.net/publications/docs/ripe-716#b The steps we take with regards to de-registration and quarantine are also described in: https://www.ripe.net/manage-ips-and-asns/resource-management/quarantine-for-returned-internet-number-resources The resources are held in quarantine long enough to allow interested parties to notice the de-registration and remove potential blacklisting records. Furthermore, we only re-use address space that is not routed. We'd like to note that in April 2018, we finished allocating IPv4 blocks from the previously-unused 185.0.0.0/8. https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations Since then, we issued more than 9,000 /22 IPv4 allocations - all of them were from address blocks that were already issued in the past and then de-registered and re-used. Sometimes we receive questions about incorrect geo-location for such address blocks (which are still pointing to the previous resource holders). In a few recent cases, we have seen reports about newly issued blocks being blacklisted. When requested, we contact relevant blacklisting providers to clarify the situation about resources being re-used and ask them to remove existing listings related to previous resource holders. We are currently reviewing our procedures to see if we could pro-actively provide blacklisting providers with information on address blocks returned to our free pools. This could help to reduce the possibility of re-issued blocks being blacklisted. Please also note that RIPE Policy Proposal 2019-08 is currently open and (if accepted) will require the creation of ROAs for all unallocated and unassigned address space under our control.: https://www.ripe.net/participate/policies/proposals/2019-08 If you have any questions, please let me know. Kind regards, Nikolas Pediaditis Registration Services and Policy Development Manager RIPE NCC > On 26 Nov 2019, at 16:47, T?ma Gavrichenkov wrote: > > Peace, > > There's a page[1] on the NCC web site which says: > > "When we recover IPv4 addresses, we hold on to them for a quarantine > period. During this time, we take a number of actions that help to > make it clear the addresses are no longer associated with their > previous holder and should be considered as ?new? address space." > > Is the particular list of actions applied to an IPv4 prefix outlined > somewhere? Is it only prevention of routing, or e.g. trash cans like > Spamhaus are contacted too? > > [1] https://www.ripe.net/manage-ips-and-asns/ipv4/how-waiting-list-works > > -- > T?ma >