- address-policy-wg - mailman.ripe.net

2019-06 Extended Review Period has ended (Multiple Editorial Changes in IPv6 Policy)
by Erik Bais 11 Feb '20

11 Feb '20

Dear Workingroup, After the extended review we received enough support (and no objections or voices against the policy proposal. ) As the AP-WG chairs, we think that the policy proposal should go to Last Call. If there is something in the policy that you don’t agree with, please let it know after the formal announcement for Last Call by Petrit. And if you do agree with the policy moving forward, please let it know in the Last Call phase as well, as it is easier for us as Chairs to call consensus or not, if we have some response. Regards, Erik Bais On behalf of the AP-WG Chair collective

6 5

Co-Chair re-election - Address policy WG
by Erik Bais 03 Feb '20

03 Feb '20

Dear WG, As time flies while we are having fun, it is almost the time to re-do the chair dance again. And this time it will be my seat that is up for a re-election. If the WG is willing to put up with me as a co-chair, that I'm more than willing to go for another 2 years. If someone would like to become co-chair of AP-WG, it is possible to send Gert an email and we can have an actual election ... If we don't have multiple candidates 1 month before the next RIPE meeting in Berlin, it will be a step down - step up process. ( most likely ) ... It would be nice if we would get a (third?) young WG chair, someone who has been to a couple meetings, but doesn't fall in the category .. old-white male .. that has been longer around than the initial IPv4 runout .. Both Gert and myself tend to fall in that category .. or are getting close to it .. and a young padiwan that we can help settle into the WG collective would be highly appreciated. Kind regards, Erik Bais Co-chair for Address Policy WG - RIPE

4 3

Policy Proposal Implemented: 2019-05 "Revised IPv4 assignment policy for IXPs"
by Marco Schmidt 21 Jan '20

21 Jan '20

Dear colleagues, We are pleased to announce that we have fully implemented the RIPE Policy Proposal 2019-05 "Revised IPv4 assignment policy for IXPs”. This policy increased the reserved IPv4 pool for IXPs to a /15 and finetuned assignment criteria. The default IPv4 assignment size for IXP remains a /24 however on request or once there are no more assignments of /24 (or larger) available, assignments can be made down to /27. The pool management part of this proposal was already implemented in October 2019. The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2019-05 The 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, Marco Schmidt Registration Services and Policy Development Assistant Manager RIPE NCC

1 0

2019-06 Review Phase Extended (Multiple Editorial Changes in IPv6 Policy)
by Marco Schmidt 21 Jan '20

21 Jan '20

Dear colleagues, Policy proposal 2019-06, "Multiple Editorial Changes in IPv6 Policy" is now in the extended Review Phase. This proposal aims to remove obsoleted text and simplify the IPv6 policy. You can find the full proposal and the RIPE NCC impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-06 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 extended Review Phase is to continue discussing 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 <address-policy-wg(a)ripe.net> before 6 February 2020. Kind regards, Marco Schmidt Registration Services and Policy Development Assistant Manager RIPE NCC

13 13

2019-07 Policy Proposal Withdrawn (Default assignment size for IXPs)
by Marco Schmidt 09 Jan '20

09 Jan '20

Dear colleagues, The policy proposal 2019-07, "Default assignment size for IXPs" has been withdrawn. This proposal aimed to change the default IXP assignment size from a /24 to a needs-based model, with a /27 as a minimum. The proposal is archived and can be found at: https://www.ripe.net/participate/policies/archived-policy-proposals/archive… Reason for withdrawal: The proposer felt that there was no clear direction on how to proceed with the proposal. Kind regards, Marco Schmidt Registration Services and Policy Development Assistant Manager RIPE NCC

1 0

FW: ASNs of organizations in reported IPv4 transfers
by Giotsas, Vasileios 08 Jan '20

08 Jan '20

Hello everyone, I'm a researcher from Lancaster University (UK) studying the IPv4 transfer market, and I'm trying to correlate IPv4 transfers with BGP routing dynamics. I've collected the reported transfers but they list only owner organizations names and not AS numbers (ASN). Same with the reported transfers of other RIRs. I tried to map the organization names to ASNs using WHOIS but I couldn’t find a match for about 50% of the organizations involved in transfers. What is the rationale behind not listing the AS number? Is it because organizations without an ASN (e.g. enterprise networks) can obtain an address? Is there a suggested way of mapping the organizations to ASNs besides WHOIS lookup? Thank you and best wishes for 2020! Vasileios Giotsas Lecturer School of Computing and Communications Lancaster University ☎ 01524 595130 https://bit.ly/LancsGiotsas

3 3

A list of actions during quarantine
by Töma Gavrichenkov 13 Dec '19

13 Dec '19

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

2 1

2019-06 Review Phase (Multiple Editorial Changes in IPv6 Policy)
by Petrit Hasani 09 Dec '19

09 Dec '19

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 <address-policy-wg(a)ripe.net> before 7 January 2020. -- Petrit Hasani Policy Officer RIPE NCC

1 0

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-07 New Policy Proposal (Default assignment size for IXPs)
by Marco Schmidt 15 Nov '19

15 Nov '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

12 18

2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
by Petrit Hasani 04 Nov '19

04 Nov '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 in the Routing Working Group 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 This proposed policy may be of interest to the Address Policy working group as well. Therefore, we encourage you to review this proposal and send your comments to <routing-wg(a)ripe.net> before 29 November 2019. -- Petrit Hasani Policy Officer RIPE NCC

10 18

Re: [address-policy-wg] [policy-announce] 2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
by Sander Steffann 31 Oct '19

31 Oct '19

Hi, > 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 I have read the policy and I don't see any downside to doing this. Creating those ROAs reflects the intention correctly, so let's do this. Cheers, Sander

2 1

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

10 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

5 4

Re: [address-policy-wg] 2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy)
by Carlos Friaças 10 Oct '19

10 Oct '19

Hi, +1 support. Regards, Carlos ---------- Forwarded message ---------- Date: Tue, 8 Oct 2019 16:51:14 From: Nick Hilliard <nick(a)foobar.org> To: Sander Steffann <sander(a)steffann.nl> Cc: RIPE Address Policy Working Group <address-policy-wg(a)ripe.net> Subject: Re: [address-policy-wg] 2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy) Sander Steffann wrote on 08/10/2019 15:01: >> 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. > > I think this is a sensible update. Support. agreed - this looks like a good idea, and thanks to Jordi for doing some housekeeping in this area. Nick

2 1

Re: [address-policy-wg] [policy-announce] 2019-05 Proposal Accepted (Revised IPv4 assignment policy for IXPs)
by Erik Bais 10 Oct '19

10 Oct '19

Thanks for the update Marco. And thanks to all the WG members and the proposal authors for making this happen for the community. Regards, Erik Bais Co-chair AP-WG. On 10/10/2019, 12:01, "policy-announce on behalf of Marco Schmidt" <policy-announce-bounces(a)ripe.net on behalf of mschmidt(a)ripe.net> wrote: 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-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

62.222.0.0/15
by Ronald F. Guilmette 10 Oct '19

10 Oct '19

I didn't realize till now that RIPE NCC was still giving out IPv4 /15 blocks as recently as August. Now that I know, may I have one too please? ================================================================= inetnum: 62.222.0.0 - 62.223.255.255 netname: IE-COOLWAVE-20010321 country: IE org: ORG-CCL78-RIPE admin-c: DW5409-RIPE tech-c: DW5409-RIPE status: ALLOCATED PA mnt-by: mnt-ie-coolwave-1 mnt-by: RIPE-NCC-HM-MNT created: 2019-08-20T11:55:01Z last-modified: 2019-08-20T11:55:01Z source: RIPE

12 23

2019-05 Last Call for Comments (Revised IPv4 assignment policy for IXPs)
by Marco Schmidt 08 Oct '19

08 Oct '19

Dear colleagues, Proposal 2019-05, "Revised IPv4 assignment policy for IXPs", is now in Concluding Phase. This proposal aims to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. The WG co-chairs have 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 8 October 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. As this policy change has reaches rough consensus, the RIPE NCC has now reserved 185.0.0.0/16 for this policy change. If final consensus is achieved, the /16 will be used as per the policy proposal, and alternatively, if the proposal is withdrawn, the address space will be returned to the IPv4 pool for allocations. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 8 October 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

2 1

RIPE 78 Address Policy WG Draft Minutes
by Marco Schmidt 08 Oct '19

08 Oct '19

Dear colleagues, The draft minutes from the Address Policy Working Group sessions at RIPE 78 have now been published: https://www.ripe.net/participate/ripe/wg/ap/minutes/ripe-78-address-policy-… Please let us know of any corrections or amendments. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

Re: [address-policy-wg] 2019-05 Policy Proposal (Revised IPv4 assignment policy for IXPs) - Moving to Last Call
by Andy Davidson 07 Oct '19

07 Oct '19

Still support this proposal.

9 8

2019-05 Policy Proposal (Revised IPv4 assignment policy for IXPs) - Moving to Last Call
by Erik Bais 07 Oct '19

07 Oct '19

Dear WG, The AP WG Chairs have seen more than sufficient support to get the policy to the next phase. The policy proposal is about extending the IXP pool with an additional /16 from the current IP Pool at the NCC. The next phase is Last Call. The discussion about the default allocation size wasn't part of this policy proposal, but with the response on the subject by Remco, we do think that this is properly addressed. If it is required, he is more than willing to address that in a new proposal after RIPE79. The RIPE NCC will reserve the /16 already for the actual implementation of 2019-05, making sure that we are not left empty handed when the last call ends. For now, we will wait for Marco to do the formal announcement of the start of Last Call and I wish you, on behalf of the AP-WG Chair collective, a nice weekend. Regards, Erik Bais Co-Chair AP-WG

3 2

Draft agenda for RIPE79 APWG meeting
by Gert Doering 04 Oct '19

04 Oct '19

Hi APWG folks, Below you can find a draft for the RIPE address policy WG meeting's agenda, which will take place in Rotterdam in the side-room (diamond room) in the following time slots: Wednesday, Oct 16, 09:00 - 10:30 Wednesday, Oct 16, 11:00 - 12:30 If you have anything else you want to see on the agenda, or if we need to change anything, please let us know. Regards, Gert Döring & Erik Bais, APWG chairs ---------------------------------------------------------------------- Wednesday, 09:00-10:30 ---------------------------------------------------------------------- A. Administrative Matters (welcome, thanking the scribe, approving the minutes, etc.) B. Presentation of the NRO NC candidates - Filiz Yilmaz - Stefan Nikolov C. Panel Discussion on "IPv4 effects after RIPE NCC run-out" <details and participants still under discussion> ---------------------------------------------------------------------- Wednesday, 11:00-12:30 ---------------------------------------------------------------------- Welcome back D. Current Policy Topics - Marco Schmidt, NCC PDO - global policy overview "what's going on?" - common policy topics in all regions (end of IPv4, transfers, ...) - overview over concluded proposals in the RIPE region since RIPE 78 - brief overview of new proposals (if any) E. Feedback From NCC Registration Service - Nikolas Pediaditis - IPv4 runout status - expectations for the waiting list phase (+ discussion with the group) F. Discussion of open policy proposals * tbd Y. Open Policy Hour The Open Policy Hour is a showcase for your policy ideas. If you have a policy proposal you'd like to debut, prior to formally submitting it, here is your opportunity. Z. AOB Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

1 0

New on RIPE Labs: 25, 000 LIRs - An End to the Milestone Highs?
by Mirjam Kuehne 03 Oct '19

03 Oct '19

Dear colleagues, Little more than twelve months after we passed the 20,000 active LIRs mark, the number of LIR accounts reached a new milestone. As the number of available IPv4 addresses in our pool dropped to 3 million, applications for new LIRs exploded. In July alone, we saw a record number of 788 new accounts being activated. At this new milestone, we once more look back at the historical developments, report on the run-out of available IPv4 and share some some insights on what the future might bring for our membership numbers. Please find more details on RIPE Labs: https://labs.ripe.net/Members/wilhelm/25-000-lirs-an-end-to-the-milestone-h… Kind regards, Mirjam Kühne RIPE NCC

1 0

Policy Proposal Implemented: 2019-02 "IPv4 Waiting List Implementation”
by Petrit Hasani 19 Sep '19

19 Sep '19

Dear colleagues, We are pleased to announce that we have implemented RIPE Policy Proposal 2019-02, "IPv4 Waiting List Implementation”. This policy established a waiting list with an allocation size of /24 once the RIPE NCC’s free IPv4 pool is exhausted. Please note: although this policy has been implemented (our software and procedures have been updated), it is not yet active. The policy is triggered when the RIPE NCC can no longer allocate the equivalent of a /22. We will send another announcement once the policy becomes active. The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2019-02 The RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is available at: https://www.ripe.net/publications/docs/ripe-725 -- Kind regards, Petrit Hasani RIPE NCC Registration Services

1 0