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

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 21 Mar '15

21 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

2015-01 New Policy Proposal (Alignment ofTransfer Requirements for IPv4 Allocations)
by Sonia Garbi Gomez 20 Mar '15

20 Mar '15

Hi Elvis, see my reply inline > *From: *Elvis Daniel Velea <elvis(a)v4escrow.net > <mailto:elvis@v4escrow.net>> > *Subject: **Re: [address-policy-wg] 2015-01 New Policy Proposal > (Alignment ofTransfer Requirements for IPv4 Allocations)* > *Date: *19 Mar 2015 11:13:18 GMT+1 > *To: *address-policy-wg(a)ripe.net <mailto:address-policy-wg@ripe.net> > > Hi Sonia, > > those numbers were quite clear. What we were wondering is whether it > is possible to register an LIR in Q4 2015, pay the €2400, receive the > /22, transfer the /22, close the LIR within the same quarter. > This was correct. If a new LIR was joined at the end of the year, the LIR had to pay only for the last quarter as well as the sign-up fee. However, the RIPE NCC Executive Board held it latest meeting on 20 March 2015. The Board made a resolution that LIRs that join the RIPE NCC and close within 12 months, have to pay the full annual service fee before commencement of a merger, transfer or a closure procedure. This means that from now on, an LIR that joins the RIPE NCC in the course of the year (for example in June 2015) and wishes to close before the end of the year, will have to pay the full service fee for 2015 (rather than the last two quarters as was previously the case) before a merger, transfer or closure procedure can commence. An official announcement will follow shortly along with the minutes of the Executive Board Meeting. Have a lovely weekend. Sonia > Or, does the LIR need to pay the fee for a whole year (4 quarters) > when they close (or transfer the /22) - regardless on which Q they > were opened? > > Regards, > Elvis > > On 19/03/15 10:02, Sonia Garbi Gomez wrote: >> Dear all >> >> For 2015, all RIPE NCC members are charged an annual service fee of € 1,600 for each LIR account they hold. >> For New LIRs that are established during the year, the service fee is applied pro rata, meaning thus that new LIRs established during the course of 2015, are charged as follow: >> >> New LIR established: Total fee: How the fee is made up: >> * during first quarter € 3,600 Sign up fee (€ 2,000) + service fee (€ 1,600) >> * during second quarter € 3,200 Sign up fee (€ 2,000) + service fee (€ 1,200) >> * during third quarter € 2,800 Sign up fee (€ 2,000) + service fee (€ 800) >> * during fourth quarter € 2,400 Sign up fee (€ 2,000) + service fee (€ 400) >> I hope this clarifies the question. >> best regards >> >> Sonia Garbi Gomez >> Finance Manager >> RIPE NCC > > > -- > <http://v4escrow.net/> > > > Elvis Daniel Velea > > > Chief Executive Officer > > Email: elvis(a)V4Escrow.net <mailto:elvis@v4escrow.net> > US Phone: +1 (702) 475 5914 > EU Phone: +31 (0) 61458 1914 > > Recognised IPv4 Broker/Facilitator in: > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you have > received this email in error, please notify the sender immediately and > delete the original.Any other use of this email is strictly prohibited. >

1 0

Re: [address-policy-wg] 2015-01 New Policy Proposal (Alignment ofTransfer Requirements for IPv4 Allocations)
by Sonia Garbi Gomez 19 Mar '15

19 Mar '15

Dear all For 2015, all RIPE NCC members are charged an annual service fee of € 1,600 for each LIR account they hold. For New LIRs that are established during the year, the service fee is applied pro rata, meaning thus that new LIRs established during the course of 2015, are charged as follow: New LIR established: Total fee: How the fee is made up: * during first quarter € 3,600 Sign up fee (€ 2,000) + service fee (€ 1,600) * during second quarter € 3,200 Sign up fee (€ 2,000) + service fee (€ 1,200) * during third quarter € 2,800 Sign up fee (€ 2,000) + service fee (€ 800) * during fourth quarter € 2,400 Sign up fee (€ 2,000) + service fee (€ 400) I hope this clarifies the question. best regards Sonia Garbi Gomez Finance Manager RIPE NCC

2 1

Policy Proposal Implemented: 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8"
by Nikolas Pediaditis 19 Mar '15

19 Mar '15

Dear colleagues, We are pleased to announce that we have implemented the policy proposal 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8". In accordance with the new policy, RIPE NCC members can now request to receive a one time /22 IPv4 allocation from the last /8 without the requirement to already have an IPv6 allocation. The archived policy proposal can be found at: https://www.ripe.net/ripe/policies/proposals/2014-04 The updated RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", is available at: https://www.ripe.net/ripe/docs/ripe-634 Kind regards, Nikolas Pediaditis RIPE NCC Registration Services

1 0

Re: [address-policy-wg] 2015-01 New Policy Proposal (Alignment ofTransfer Requirements for IPv4 Allocations)
by Nick Hilliard 18 Mar '15

18 Mar '15

> I think that the more we talk about it, the more this loophole will be > (ab)used. The part that was just theoretical was estimating how long it > will take a company to decide that instead of going to the market, they > could actually go to the RIPE NCC and get a /16 or maybe a /12 at €2.3 - > €3.4 per IP (depending in which quarter you decide to do it). from what I understand, the procedures clarified in RIPE-640 mean that the price of a /22 obtained by LIR churn will remain at startup fee + 1Y membership, and that it doesn't make any difference to the overall cost whether this is done in Q1 or Q4 because when you open a LIR, you are liable for a full year's membership fees. I.e. cost of doing this in 2015 is 1600+2000 = 3600, or €3.51 per ip address. Nick

3 2

2014-12 Last Call for Comments (Allow IPv6 Transfers)
by Marco Schmidt 18 Mar '15

18 Mar '15

Dear colleagues, The proposal described in 2014-12, "Allow IPv6 Transfers", is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 18 March 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-12 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 18 March 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

2 1

APNIC temporarily freezing v4 transfers to RIPE NCC?
by Nick Hilliard 13 Mar '15

13 Mar '15

thanks to Tore for pointing this out, but page 6 of: > http://www.apnic.net/__data/assets/pdf_file/0011/80786/apnic-ec-minutes-201… contains the following: > 21. Inter-RIR transfer policy discussion > > The EC considered the Inter-RIR transfer policy discussions (attached). > > The EC unanimously resolved to place a temporary moratorium on inter RIR > transfer with RIPE NCC, pending discussions and confirmation with APNIC, > ARIN and RIPE communities that such transfers will not change APNIC’s > status as sharing reciprocal, compatible, needs-based policy with ARIN. > > Motion proposed by Paul Wilson, seconded by Akinori Maemura. Could someone from APNIC, ARIN or both explain the background to this decision? I haven't seen any discussions in the RIPE community about this, and without knowing the background it seems peculiar that APNIC feels it necessary to consult ARIN about APNIC->RIPE NCC resource transfers. Nick

10 17

2014-13 Proposal Accepted (Allow AS Number Transfers)
by Marco Schmidt 12 Mar '15

12 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-525, "Autonomous System (AS) Number Assignment Policies", has been accepted by the RIPE community. This policy change allows the transfer of Autonomous System (AS) numbers within the RIPE NCC service region. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-13 The new RIPE Document is called ripe-638 and is available at: https://www.ripe.net/ripe/docs/ripe-638 We estimate that this proposal will take about three months to fully implement. 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