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

RIPE70 meeting agenda, draft 1
by Gert Doering 14 Apr '15

14 Apr '15

Hi APWG folks, RIPE meeting orga, below you can find a draft for the RIPE address policy WG meeting's agenda, which will take place in Amsterdam in the following time slots: Wednesday, May 13, 09:00 - 10:30 Wednesday, May 13, 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. So far, the agenda is fairly light - if you have something you want to address, or that bothers you, let us know and we make room for you :-) The distribution of items to the two timeslot is somewhat subject to the time spent on discussion - but we'll try to stick to what's published. regards, Gert Doering, APWG chair ---------------------------------------------------------------------- Wednesday, 09:00-10:30 ---------------------------------------------------------------------- A. Administrative Matters 5 min (welcome, thanking the scribe, approving the minutes, etc.) B. WG Chair Selection Process [15 min?] - presenting the current draft document - discussion C. Current Policy Topics - Marco Schmidt, NCC PDO [15-20 min] - 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 RIPE69 2014-04 Removing IPv6 Requirement for Receiving Space from the Final /8 (consensus, policy) 2014-05 Policy for Inter-RIR Transfers of Internet Resources (consensus, policy) 2014-07 Language Clarification 2014-08 Language Clarification 2014-10 Language Clarification 2014-11 Language Clarification (consensus, policy) 2014-09 Language Clarification in "IPv6 Address Space for IXPs" **no consensus, withdrawn** 2014-12 Allow IPv6 Transfers (consensus, policy) 2014-13 Allow AS Number Transfers (consensus, policy) - brief overview over new proposals (if any) D. Feedback From NCC Registration Service - Andrea Cima (NCC RS) [10-15 min] (+ discussion with the group) F. Discussion of open policy proposals 2014-03 Remove Multihoming Requirement for AS Number .. (Job Snijders) 2015-01 Alignment of Transfer Requirements for IPv4 Allocations (Elvis Velea) [some bits might get moved to "after coffee break" if we run out of time] ---------------------------------------------------------------------- Wednesday, 11:00-12:30 ---------------------------------------------------------------------- Welcome back F. Discussion of open policy proposals [60 min?] 2015-02 Keep IPv6 PI When Requesting IPv6 Allocation (James Kennedy) N.N. "On IPv6 Allocation Criteria" (no formal proposal yet) G. New Ideas under Discussion - Elvis Daniel Velea - change size of last /22 allocations Y. Open Policy Hour "The Open Policy Hour (OPH) 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 Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

2 2

2015-01 Impact Analysis will be produced (Alignment of Transfer Requirements for IPv4 Allocations)
by Marco Schmidt 14 Apr '15

14 Apr '15

Dear colleagues, The discussion period for the proposal described in 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations" has ended. The RIPE NCC Impact Analysis will now be prepared for review. We will publish the document shortly and we will make an announcement. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-01 Regards Marco Schmidt Policy Development Officer RIPE NCC

4 3

2014-05 Proposal Accepted (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 09 Apr '15

09 Apr '15

Dear colleagues, Consensus has been reached, and the policy proposal 2014-05, "Policy for Inter-RIR Transfers of Internet Resources" has been accepted by the RIPE community. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-05 The new RIPE Document is ripe-644 and is available at: https://www.ripe.net/ripe/docs/ripe-644 The proposal also amended the policies described in the RIPE Document "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". The new RIPE Document is ripe-643 and is available at: https://www.ripe.net/ripe/docs/ripe-643 We have already begun the implementation and will start with our procedures, including the necessary coordination with the other RIRs. The technical implementation will start in around one month's time, as it needs to link with the ongoing implementation of the recently accepted IPv6 and ASN transfer policies. We estimate that it will take about four months to fully implement this proposal. Details of the implementation status are available at: https://www.ripe.net/lir-services/resource-management/policy-implementation… We will send another announcement when the implementation is finished and the new procedures are in place. Thank you to everyone who provided their input. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-05 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 07 Apr '15

07 Apr '15

Dear colleagues, The draft documents for version 3.0 of the policy proposal 2014-05, "Policy for Inter-RIR Transfers of Internet Resources", have now been published, along with an impact analysis conducted by the RIPE NCC. Some of the differences from version 2.0 include: - Introduction of needs justification for transfers from RIR regions that require need-based policies - Explicit statement about when RIPE policies apply during a transfer - Related wording adjustments in the summary and rationale of the proposal You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-05 The draft documents are available at: https://www.ripe.net/ripe/policies/proposals/2014-05/draft We encourage you to read the draft document text and send any comments to <address-policy-wg(a)ripe.net> before 16 February 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

13 15

Working group chair rotation 1
by Sander Steffann 07 Apr '15

07 Apr '15

Hello working group, As we now have a working group chair rotation/selection process in place it is time to start that process for the first time! After long deliberation (a.k.a. a random number generator) we have decided that Gert is going to be the first chair to step down. He will do so at the upcoming RIPE meeting (RIPE 70 in Amsterdam). He has also volunteered again and is therefore our first candidate. If anybody else wants to volunteer then please make yourself known on this mailing list before the start of RIPE 70. Cheers, Sander & Gert

3 3

Working group chair selection process: consensus
by Sander Steffann 07 Apr '15

07 Apr '15

Hi working group, The last call for the working group chair selection process has ended and no further comments were received. Therefore the working group chairs hereby declare consensus for the process. Cheers, Sander & Gert

1 0

2015-01 New Policy Proposal (Alignment ofTransfer Requirements for IPv4 Allocations)
by Riccardo Gori 03 Apr '15

03 Apr '15

Hi everybody, This policy proposal gets +1 support from me, a rookie. My little experience is so recent but so clear: RIPE wants to burn out this resources or at least make this resources available does not matter to who. Maybe someone thinks this way will be the IPv6 time or maybe someone owns a lot of resources and wants to make much more money from them for a while... don't know. Too young in this to understand, anyway this looks to me slightly far from the spirit of the last /8 policy I read. I think the support of the policy would be correct but it can certainly higher the market price and if there is no way to stop big player this could be converted in a mess. Thee proposal is a good start but I think the community needs something better. I would go this way: - approve 24 months holding time - forbid companies (not LIRs) holding more than one /22 if they already hold resources before allocated before /8 policy Older resource holder allocated before /8 policy had the chance in the past to request resources for sligtly lower costs. They are in the market and they have experience in routing and managin IPs, they should (must) start IPv6 deployment as an example for others. kind regards Riccardo Gori

1 0

aggregating unused allocations
by Antonis Lioumis 24 Mar '15

24 Mar '15

Hello Recently my company got a /22 allocation through the well known transfer procedure between LIR's. In the past we also got the /22 we qualify from RIPE NCC's last /8. This /22 was put aside for future use. For aggregation purposes we asked RIPE NCC to return both /22 and get back a /21 but according to current policies this is forbidden. Since global routing table has exceeded 500000 prefixes and expected to grow more maybe RIPE community should rethink permitting the exchange of smaller IPv4 blocks with contiguous one. Regards Antonis Lioumis

4 3

2014-12 Proposal Accepted (Allow IPv6 Transfers)
by Marco Schmidt 23 Mar '15

23 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to ripe-589, "IPv6 Address Allocation and Assignment Policy", has been accepted by the RIPE community. This policy change allows the transfer of IPv6 allocations and IPv6 Provider Independent (PI) assignments within the RIPE NCC service region. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-12 The new RIPE Document is called ripe-641 and is available at: https://www.ripe.net/ripe/docs/ripe-641 Given the similarity of this policy to the recently accepted Policy Proposal 2014-13, "Allow AS Number Transfers", the RIPE NCC will implement both policy changes together. This is a more efficient execution of the policy implementation process and will lead to an extension of only two weeks to the initial estimated implementation period. We therefore estimate that to fully implement both proposals together will take three and a half months in total. Details of the implementation status are available at: https://www.ripe.net/lir-services/resource-management/policy-implementation… We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Working group chair selection process
by Sander Steffann 20 Mar '15

20 Mar '15

Hi Working Group, We finally have a final draft for the working group chair selection process. Sorry for taking so long. Here is the text we propose to use: --- The RIPE Address Policy Working Group aims to maintain a team of two Chairpersons whenever possible. # Electing a chairperson Once a year one of the chairs will step down, allowing new candidates the opportunity to become chair. The chairs take turns stepping down, and this is announced to the working group mailing list at least one month before the start of a RIPE meeting. The working group will select new chair(s) at the RIPE Address Policy Working Group session. Those present at the session, either in person or remotely, will determine by consensus among themselves who takes the available position(s). The remaining chair will determine whether consensus has been reached. If the working group finds itself without a chair the RIPE chair will determine consensus. If no consensus can be reached then a secret ballot to elect the new chair(s) will be held at the working group session. Everyone physically present at the session can participate in the secret ballot. Votes will be counted by RIPE NCC Staff, and the result will be determined using proportional representation through the single transferable vote, otherwise known as PR-STV. The winner(s) of the secret ballot will become the new chair(s). # Running for chairperson Anybody is allowed to volunteer for a vacant chair position, including former chairs. Those who volunteer to chair the RIPE Address Policy Working Group should be aware of the responsibilities and work this involves. A description of the responsibilities of a RIPE working group chair can be found in "Working Group Chair Job Description and Procedures" (http://www.ripe.net/ripe/docs/ripe-542). # Removing a chairperson When a significant number of participants in the working group are unsatisfied with a particular chair, and this cannot be resolved by discussion within the working group, they can call for a vote of no confidence. The vote must be requested on the mailing list at least one week before a RIPE meeting. The vote will be resolved using a secret ballot, which will be held at the working group session. Everyone physically present at the meeting can participate. The votes will be counted by RIPE NCC Staff and the result is determined by simple majority. If the vote is passed the chair who is the subject of the vote will step down immediately. --- We're doing a two-week last-call on this (ending on Friday 3 April) and if there are no objections we will use this process starting at RIPE70 in Amsterdam. Cheers, Sander & Gert The current APWG chairs

2 3