March 2015 - address-policy-wg

2014-03 New Draft Document and Impact Analysis Published (Remove Multihoming Requirement for AS Number Assignments)
by Marco Schmidt 07 Nov '15

07 Nov '15

Dear colleagues, The draft document for version 2.0 of the policy proposal 2014-03, "Remove Multihoming Requirement for AS Number Assignments" has now been published, along with an impact analysis conducted by the RIPE NCC. Some of the differences from version 1.0 include: - AS Numbers can now be assigned for any need that cannot be satisfied with an existing AS Number - The RIPE NCC's need evaluation has been removed - A limit of 1,000 AS Numbers per organisation has been added - There is now a requirement that 16-bit AS Numbers be multihomed after nine months - The requirement that the routing policy must be new and unique has been removed - 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-03 And the draft document at: https://www.ripe.net/ripe/policies/proposals/2014-03/draft We encourage you to read the draft document text and send any comments to <address-policy-wg(a)ripe.net> before 22 January 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

16 41

2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
by Marco Schmidt 20 May '15

20 May '15

Dear colleagues, The Review Period for the proposal 2014-03, "Remove Multihoming Requirement for AS Number Assignments" has been extended until 19 May 2015. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-03 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

10 15

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

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

2014-07, 2014-08, 2014-10, 2014-11 Proposals Accepted (Language Clarification Proposals)
by Marco Schmidt 11 Mar '15

11 Mar '15

Dear colleagues, Consensus has been reached, and the proposals for changes to the following RIPE Documents have been accepted by the RIPE community: ripe-632, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" ripe-452, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" ripe-233, "IPv6 Addresses for Internet Root Servers In The RIPE Region" ripe-476, "Allocating/Assigning Resources to the RIPE NCC" These policy changes replace the term "should" with "must" in cases where the previous wording created unwanted ambiguity in policy documents. You can find the full proposals at: http://www.ripe.net/ripe/policies/proposals/2014-07 http://www.ripe.net/ripe/policies/proposals/2014-08 http://www.ripe.net/ripe/policies/proposals/2014-10 http://www.ripe.net/ripe/policies/proposals/2014-11 The new RIPE Documents are called ripe-634, ripe-635, ripe-636 and ripe-637 and are available at: https://www.ripe.net/ripe/docs/ripe-634 https://www.ripe.net/ripe/docs/ripe-637 https://www.ripe.net/ripe/docs/ripe-636 https://www.ripe.net/ripe/docs/ripe-635 Note: the order of the original documents, proposals and new RIPE Documents in the lists above all correspond to one another. These proposals are implemented with immediate effect, as the RIPE NCC's procedures, tools and documentation are already in line with the policy understanding that these updates reflect. Thank you to everyone who provided their input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?
by sandrabrown＠ipv4marketgroup.com 11 Mar '15

11 Mar '15

Hi Andrea, At APNIC39 in Fukuoka, I spoke with Adam Gosling of APNIC. He suggested that the APNIC EC would wait for an interpretation and implementation of the new RIPE inter-RIR policy before making a decision. But, as reflected in the discussion already made, he did feel that an APNIC to RIPE transfer would not be subjected to needs justification because he (and APNIC in general) do not interpret APNIC policy as requiring needs justification if the receiving RIR does not. Two comments on this: Why would APNIC to RIPE not require needs justification when APNIC to APNIC does? Secondly, there are so few IPs within APNIC, how often will there ever be IPs transferred from APNIC to RIPE region under the inter-RIR policy? I would not think this is a big transfer path. The reality is that the huge supply of IPs for transfer to RIPE is in ARIN region and this supply is the target of the new RIPE inter-RIR policy. If APNIC never allows transfer to RIPE region, this would be ok from the perspective of supply to RIPE region. In fact this would be preferable to APNIC allowing transfers with no needs justification, such that ARIN then flipped its position to block transfers to APNIC because they could subsequently to transferred to RIPE. A more tangible flaw is that APNIC has no time delay on re-transfers. While ARIN would not allow a transferred block to be re-transferred for 12 months and RIPE would not allow a transferred block to be re-transferred for 24 months, APNIC has no limitation. But this problem exists today for IPs transferred to APNIC; they can immediately be re-transferred within APNIC. No change just because they could now be transferred to RIPE region, so I can't see ARIN complaining about this now. ARIN being concerned with APNIC allowing transfers to APNIC being subsequently transferred to RIPE should not influence the implementation of direct transfers from ARIN to RIPE using the new needs justification criteria of 50% use over 5 years that ARIN had agreed was compatible with its policy. Based on this analysis, I don't see the initial buy-in or non-buy-in by APNIC as a concern. It is ARIN as a supply that is needed. Sandra Brown Message: 3 Date: Tue, 10 Mar 2015 17:03:03 +0000 From: Nick Hilliard <nick(a)inex.ie> To: Andrea Cima <andrea(a)ripe.net>, Address Policy Working Group <address-policy-wg(a)ripe.net> Subject: Re: [address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC? Message-ID: <54FF23C7.4020403(a)inex.ie> Content-Type: text/plain; charset=utf-8 Hi Andrea, On 10/03/2015 16:05, Andrea Cima wrote: > While I cannot answer on behalf of the other RIRs, we have given an > update about the inter-RIR transfer policy proposal last week, during > APNIC 39. I hope the video and transcripts will provide you with the > clarification requested (please see session Policy SIG-3) thanks for the reference. The context is located at pages 35-49 of: https://conference.apnic.net/data/39/5-March-Policy-SIG-3.txt and at: https://www.youtube.com/watch?v=2iKK_8iJU6E#t=1h09m11s Nick

1 0

2014-13 Last Call for Comments (Allow AS Number Transfers)
by Marco Schmidt 11 Mar '15

11 Mar '15

Dear colleagues, The proposal described in 2014-13, "Allow AS Number 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 10 March 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-13 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 10 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

4 4

2014-07, 2014-08, 2014-10, 2014-11 Last Call for Comments (Language Clarification Proposals)
by Marco Schmidt 10 Mar '15

10 Mar '15

Dear colleagues, The proposals described in - 2014-07, Language Clarification in "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" - 2014-08, Language Clarification in "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" - 2014-10, Language Clarification in "IPv6 Addresses for Internet Root Servers In The RIPE Region" - 2014-11, Language Clarification for "Allocating/Assigning Resources to the RIPE NCC", are now in the Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for these proposal has been reached and they 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 one of these proposal. Any objection must be made by 9 March 2015 and must be supported by an explanation. You can find the full proposals at: https://www.ripe.net/ripe/policies/proposals/2014-07 https://www.ripe.net/ripe/policies/proposals/2014-08 https://www.ripe.net/ripe/policies/proposals/2014-10 https://www.ripe.net/ripe/policies/proposals/2014-11 Please e-mail any final comments about these proposals to address-policy-wg(a)ripe.net before 9 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

2 1

2015-01 New Policy Proposal (Alignment of Transfer Requirements for IPv4 Allocations)
by Marco Schmidt 10 Mar '15

10 Mar '15

Dear colleagues, A proposed change to RIPE Document "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2015-01 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 12 March 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

22 57

Policy proposal 2014-03 "Remove Multihoming Requirement for AS Number Assignments"
by Sander Steffann 09 Mar '15

09 Mar '15

Hello working group, There has been a lot of discussion regarding policy proposal 2014-03 "Remove Multihoming Requirement for AS Number Assignments". There has been discussion on the the content of the proposal, the impact that the RIPE NCC charging scheme has and on the 'garbage collection' effects of the different ideas people have. We clearly don't have consensus on how to proceed. The working group chairs (Gert Döring and myself) have therefore decided to extend the review phase. Because of the potential impact of the RIPE NCC charging scheme and because the ideas on this policy proposal seem to be diverging at the moment we have decided to extend it to after the RIPE meeting in Amsterdam. We realise this is a relatively long time but we feel that having a live discussion on this policy proposal is the best way forward. Marco will send the formal announcement shortly. Cheers, Sander Steffann Gert Döring APWG chairs

1 0

2014-05 Last Call for Comments (Policy for Inter-RIR Transfers of Internet Resources)
by Marco Schmidt 05 Mar '15

05 Mar '15

Dear colleagues, The proposal described in 2014-05, "Policy for Inter-RIR Transfers of Internet Resources", 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 3 April 2015 and must be supported by an explanation. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2014-05 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 3 April 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-04 Proposal Accepted (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 04 Mar '15

04 Mar '15

Dear colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-623, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2014-04 The new RIPE Document is called ripe-632 and is available at: https://www.ripe.net/ripe/docs/ripe-632 The RIPE NCC has already begun preparations to implement this policy proposal. We estimate it may take a few weeks to make these changes and fully implement the policy proposal. 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

2014-04 New Draft Document and Impact Analysis Published (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Marco Schmidt 03 Mar '15

03 Mar '15

Dear colleagues, The draft document for version 3.0 of the policy proposal 2014-04, "Removing IPv6 Requirement for Receiving Space from the Final /8", has now been published, along with an impact analysis conducted by the RIPE NCC. Some of the differences from version 2.0 include: - Removal of the IPv6 requirement to receive Pv4 addresses from the RIPE NCC - Related wording adjustments in the title, 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-04 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-04/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 7 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

17 23