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

RIPE NCC Executive Board election
by Ronald F. Guilmette 17 Apr '20

17 Apr '20

Greetings all, I know that all is not right with the world right now, and that most of you, like me, have much more pressing things on your minds right now, but someone just sent me the following link and I cannot exactly ignore it: https://www.ripe.net/participate/meetings/gm/meetings/may-2020/confirmed-ca… I would like to call everyone's attention to the last of the three candidates who have, it seems, "qualified" as candidates for open seats of the RIPE NCC Executive Board. As I have already said, I know that things are bad in the world right now, but I must ask this question: Is there really no one other than these three candidates who is willing and/or able to stand for the three open seats on the RIPE NCC Executive board... three open seats that will be voted on at the next general meeting, 13-15 May 2020 ? If not, then it seems that RIPE NCC will soon be following in the new tradition, established first by AFRINIC only last year, of placing well and widely known crooks on it board. I desperately hope it won't come to that, but that is not for me to decide. The decision is in your hands dear friends. Regards, rfg

4 5

New AS Number Blocks Allocated to the RIPE NCC
by Nikolas Pediaditis 02 Apr '20

02 Apr '20

Dear colleagues, On 1 April 2020, the RIPE NCC received the following AS Number blocks from IANA: 210332-211355 211356-212379 212380-213403 You may want to update your records accordingly. All allocations of AS Numbers made by IANA to RIRs are listed here: https://www.iana.org/assignments/as-numbers/as-numbers.xhtml Kind regards, Nikolas Pediaditis Registration Services & Policy Development Manager RIPE NCC

1 0

2019-06 Proposal Accepted (Multiple Editorial Changes in IPv6 Policy)
by Petrit Hasani 16 Mar '20

16 Mar '20

Dear colleagues, Consensus has been reached on 2019-06, "Multiple Editorial Changes in IPv6 Policy". This proposal aimed 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 The new RIPE Document is called ripe-738 and is available at: https://www.ripe.net/publications/docs/ripe-738 We estimate that this proposal will take around one month 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-06 Last Call for Comments (Multiple Editorial Changes in IPv6 Policy)
by Petrit Hasani 11 Mar '20

11 Mar '20

Dear colleagues, Proposal 2019-06, "Multiple Editorial Changes in IPv6 Policy", is now in Concluding Phase. This proposal aims to remove obsoleted text and simplify the IPv6 policy. 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 11 March 2020 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/2019-06 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 11 March 2020. Regards, -- Petrit Hasani Policy Officer RIPE NCC

3 2

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