April 2018 - address-policy-wg

New on RIPE Labs: So Long Last /8 and Thanks For All the Allocations
by Mirjam Kuehne 28 Aug '19

28 Aug '19

Dear colleagues, On 17 April 2018, we allocated the last available block of 1,024 addresses in 185/8 - the last /8 we received from IANA back in 2011. This article on RIPE Labs looks at how this address space was allocated and how it is used today: https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the… It's important to keep in mind that while 185/8 is finished, we still have around nine million recovered IPv4 addresses in our available pool. Under current policy and growth rates, we expect these to last a further two years. Kind regards, Mirjam Kühne RIPE NCC

3 2

2018-01 New Policy Proposal (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 16 May '18

16 May '18

Dear colleagues, A new RIPE Policy proposal, 2018-01, "Organisation-LIR Clarification in IPv6 Policy" is now available for discussion. This proposal aims to clarify the wording used in ripe-684 regarding terms such as "organisation" and "LIR". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-01 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 proposers, 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 23 March 2018. Regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

11 11

FW: WG chair change
by Erik Bais 12 May '18

12 May '18

Hi Gert, Sander & AP-WG members, Thank you for the email and I would like to formally put my name in the hat. For those that don't know me personally, my name is Erik Bais, Dutch, I'm 45, married for 16 year with my wife Wilhelmina and we have 2 sons. I'm the owner of a Dutch ISP named A2B Internet and I'm one of the co-founders of the IPv4 broker : Prefix Broker. I've lived most of my life in The Netherlands and as a family, we lived for almost a year in the UAE (Dubai) in 2008/2009, when I worked for a US based system integrator and I've worked in Germany for a US based company in the 90's for a year. I have a been working in the ISP community since the 2000. And started A2B Internet in 2010 in The Netherlands. In our work as a connectivity ISP, we started to request AS numbers and IP space for customers in order to get them migrated to our network and while doing so, we noticed some things that needed improvement in the AP policies. That is how it all got started ... I've been the author of the following proposals that have been accepted by the community: https://www.ripe.net/participate/policies/proposals/2011-02 : Removal of multihomed requirement for IPv6 PI # co-author together with Jordi https://www.ripe.net/participate/policies/proposals/2013-04 : Resource Certification for non-RIPE NCC Members # Services WG - allowing PI space holders and Legacy space holders the option for RPKI certification. https://www.ripe.net/participate/policies/proposals/2014-02 : Allow IPv4 PI transfer https://www.ripe.net/participate/policies/proposals/2014-12 : Allow IPv6 Transfers https://www.ripe.net/participate/policies/proposals/2014-13 : Allow AS Number Transfers https://www.ripe.net/participate/policies/proposals/2015-04 : RIPE Resource Transfer Policies And I've been quite active on the discussions on the mailinglist and in the GM's. Besides the various presentations about the policies, I've also done some presentations in the plenary of the RIPE meetings and different WG's about various topics.. Examples are: https://ripe72.ripe.net/archives/video/116/ : Naughty Port project about a different way of making a peering decision based on Network Naughty-ness using a rating system against DDOS's. https://ripe74.ripe.net/archives/video/119/ : IRR Filtering at IXP Route Servers https://ripe75.ripe.net/archives/video/165/ : Pre-Transfer Clean-Up of Abused Prefixes I really like the RIPE community and as an active policy proposer, I think I can say that I have been around the block on the PDP and can work with the sometimes harsh way of communication that a co-chair role has need to deal with in the heat of some discussions. I understand what it requires in effort from time to time and as I'm living in the Netherlands, it makes it easy to visit the Amsterdam RIPE office for me if needed. I hope that the community appreciates the transparent way of communicating and knowledge sharing that I like and that I will be selected as the co-chair for the AP-WG. Regards, Erik Bais

2 1

WG chair change
by Gert Doering 07 May '18

07 May '18

Dear AP WG, as announced, my co-chairs of amazingly many years, Sander Steffann, will be stepping down as a WG chair at the next RIPE meeting. Our WG chair selection policy is described here: https://www.ripe.net/participate/ripe/wg/ap https://www.ripe.net/participate/ripe/wg/ap/address-policy-wg-chair-selecti… according to this, we'll spend a few minutes at the next APWG session in Marseilles to select a new co-chair. To avoid lengthy rounds of introduction at the meeting, I want to ask for volunteers here on the list - please step forward if you want to take up this work, and introduce yourself on why you think you're a good candidate and what your plans for the WG are for the next two years (or longer). A short recap of the WG chairs duties: - chair the APWG session at the RIPE meetings (so generally it is expected that both co-chairs can attend most RIPE meetings and feel halfway confident talking on stage and moderate a discussion) - read - and if necessary, moderate - the APWG mailing list (thus, fluency in written English is necessary, and while discussions are going on, some amount time spent at least every few days) - help policy proposers bring their policy proposal through the PDP (answering questions, helping with the wording of proposed text, spending some time discussing 'next steps' for a proposal) - judge consensus at the end of discussion and review phases according to our policy development process (usually done by both co-chairs together, unless a conflict of interest appears) - help shape the format of RIPE meetings together with all the other WG chairs and the RIPE PC - by mailing list and by attending the "WG chair lunch" on RIPE meeting Thursdays - see also: https://www.ripe.net/publications/docs/ripe-692 A definite plus for an APWG chair is "operational experience with these pesky numbers" - either by operating the address management side (LIR) of an Internet Service Provider or Enterprise network, or by being an address broker, etc. Sander and I have spoken to a few of you who would make good chairs already - but ultimately, it's up the working group to decide. So even if you have spoken to us privately before, please speak up now. So, come forward, dear candidates and make yourself known! :-) Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

4 5

WG Chair selection
by Paul Hoogsteder 06 May '18

06 May '18

Hello AP-WG, I don't think I've seen any support for either candidate for the position of WG chair on the list yet. I think Erik Bais is more than qualified for such a position, he's been active in the RIPE community and this working group for years and has made many valuable contributions. +many for Erik! Best regards, Paul Hoogsteder Meanie AS31019 Breedband Delft AS34108

13 12

2018-03 New Policy Proposal (Fixing Outdated Information in the IPv4 Policy)
by Marco Schmidt 26 Apr '18

26 Apr '18

Dear colleagues, A new RIPE Policy proposal, 2018-03, "Fixing Outdated Information in the IPv4 Policy" is now available for discussion. This proposal aims to fix outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-03 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 23 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

4 3

2018-04 New Proposal (PDP Clarification) to be discussed on RIPE Discussion Mailing List
by Marco Schmidt 26 Apr '18

26 Apr '18

Dear colleagues, A new RIPE proposal, 2018-04, "PDP Clarification" has been published on the RIPE Discussion mailing list for discussion. This proposal aims to clarify the options available to the WG chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). Please note that since changes to the PDP can affect all RIPE Working Groups, the RIPE Chair decided to discuss this proposal on the RIPE Discussion mailing list. The RIPE Chair will also moderate the proposal discussion. We wanted to notify the Address Policy Working Group in particular, as most of the policy proposals are discussed here. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-04 We encourage you to review this proposal and join the discussion on the RIPE Discussion mailing list (ripe-list(a)ripe.net). Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

Agenda for APWG at RIPE 76 in Marseille
by Sander Steffann 18 Apr '18

18 Apr '18

Hi APWG folks, below you can find a draft for the RIPE address policy WG meeting's agenda, which will take place in Marseille in the following time slots: Wednesday, May 16, 09:00 - 10:30 Wednesday, May 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 & Sander Steffann, APWG chairs ---------------------------------------------------------------------- Wednesday, 09:00-10:30 ---------------------------------------------------------------------- A. Administrative Matters (welcome, thanking the scribe, approving the minutes, etc.) B. WG Chair Selection - longest-serving chair (Sander Steffann) stepping down - Sander is not volunteering for another term, so we'll select a new co-chair C. The role and function of the ASO within ICANN Public consultation, Axel Pawlik 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 75 - brief overview of new proposals (if any) ---------------------------------------------------------------------- Wednesday, 12:00-13:30 ---------------------------------------------------------------------- Welcome back E. Feedback From NCC Registration Service - Andrea Cima (+ discussion with the group) F. Discussion of open policy proposals 2018-01 Organisation-LIR Clarification in IPv6 Policy Jordi Palet Martinez / Erik Bais / Juri Bogdanov 2018-02 "Assignment Clarification in IPv6 Policy" Jordi Palet Martinez / Erik Bais 2018-03 Fixing Outdated Information in the IPv4 Policy Andrea Cima 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

2 3

2018-02 New Policy Proposal (Assignment Clarification in IPv6 Policy)
by Marco Schmidt 18 Apr '18

18 Apr '18

Dear colleagues, A new RIPE Policy proposal, 2018-02, "Assignment Clarification in IPv6 Policy" is now available for discussion. This proposal aims to clarify the definition of “Assign” in ripe-699 (section 2.6). The non-permanent provision of up to a /64 prefix to third parties shall not be considered a sub-assignment. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-02 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 15 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

5 8

Proposal Implemented: 2016-04, "IPv6 Sub-assignment Clarification"
by Marco Schmidt 16 Apr '18

16 Apr '18

Dear colleagues, We are pleased to announce that we have implemented the policy proposal 2016-04, "IPv6 Sub-assignment Clarification". The policy change re-defined the term "sub-assignment" for IPv6. The provision of separate addresses (/128) to customers of the assignment holder will not be considered a sub-assignment. More information, especially for IPv6 PI assignments, can be found at: https://www.ripe.net/manage-ips-and-asns/ipv6/request-ipv6/ipv6 The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2016-04 The RIPE Document, "IPv6 Address Allocation and Assignment Policy", is available at: https://www.ripe.net/publications/docs/ripe-699 Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0