- policy-announce - mailman.ripe.net

2015-03 Proposal Accepted (Assessment Criteria for IPv6 Initial Allocation Size)
by Marco Schmidt 01 Oct '15

01 Oct '15

Dear colleagues, Consensus has been reached on the proposal to amend RIPE Document ripe-650, "IPv6 Address Allocation and Assignment Policy". This policy change introduces new criteria for the evaluation of large IPv6 allocation requests: * Hierarchical and geographical structure * Segmentation for security * Planned longevity The existing requirements in the policy that stipulate the number of users a nd extent of the infrastructure remain unchanged. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-03 The new RIPE Document is called ripe-655 and is available at: https://www.ripe.net/publications/docs/ripe-655 We estimate that this proposal will take about one week 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 input. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-04 Discussion Period extended until 25 September 2015 (RIPE Resource Transfer Policies)
by Marco Schmidt 16 Sep '15

16 Sep '15

Dear colleagues, The Discussion Period for the proposal 2015-04, "RIPE Resource Transfer Policies" has been extended until 25 September 2015. The goal of this proposal is to create a single document with all relevant information regarding the transfer of Internet number resources. The proposer asked to provide additional feedback or questions. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-04 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

1 0

Re: [policy-announce] [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
by Erik Bais 01 Sep '15

01 Sep '15

Hi James, > Couple of questions/comments... > From 1.0 > Shouldn't the scope be explicit as to what is/isn't included It states what is included ... are you missing anything specific ? > From 2.1 > "Transfers can be on a permanent or non-permanent basis." > How is this going to be recorded and managed within the context of > reflecting it being a non-permanent transfer? That is taken directly from the current policy text and it is managed by the RIPE NCC. I must admit that I haven't seen non-permanent transfers myself (yet), so I would have to ask the NCC on how they are exposing that if at all publicly. The text itself isn't different to what there is already there. > From 2.2 > "assigned by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs)" > Rather than "such as" this needs to be a definitive list of what is > classed as a restricted resource The part between the round brackets was put there as the current examples to what are the almost depleted resources. As IPv4 isn't completely depleted yet ( due to the final /8 policy ) and neither are 16-bit ASN's.. That implies that other resources like IPv6 or 32-bit ASN's are not restrictive by a 24 month transfer restriction as there is no logical requirement that we could find to put it in the policy. > From 3.1 > Again a list of conditions or references to policies that impose restrictions needed You mean other than what is currently in the proposed text ? Currently all resources that we have are possible to be transferred ... > From 4.0 > M&A process is mentioned, should there be other references to this? > Especially as M&A (as I understand it) allows 2.2 to be overridden An M&A is not a transfer ... a M&A is a change in a business where one company or service offering with assets/resources are going from one company to another company. That can be in the same company ( Look at companies like IBM or Philips or GE for instance that are splitting off services to a new business unit .. or buying competing companies and incorporating that into their own business / service..) Sometimes there are stocks being sold, however there are more ways of M&A's within today's business. Typical the goal of M&A's are not the (number) resources, but other services/assets/added value that would create the value ... And with a transfer, the goal is getting or selling the specified resource. Also the M&A is a business (operational) process.. and transfers are a policy. > General > - As this is about transfers should this also cover returning > resources to ripe NCC so all types of transfers be included The text is pretty clear imho on what it covers.. any number resource to and from the RIPE NCC service region ... Both TO and FROM the RIPE region ... > - broadly support the unification of transfer policy into a single > document, just things bits are missing or muddy I hope that we made a good start here :) Erik Bais

1 0

2015-03 Last Call for Comments (Assessment Criteria for IPv6 Initial Allocation Size)
by Marco Schmidt 31 Aug '15

31 Aug '15

Dear colleagues, The proposal described in 2015-03, "Assessment Criteria for IPv6 Initial Allocation Size", 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 29 September 2015 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 co-Chairs of the Working Group for final consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-03 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 29 September 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
by Marco Schmidt 14 Aug '15

14 Aug '15

Dear colleagues, A new RIPE Policy Proposal, "RIPE Resource Transfer Policies" has been made and is now available for discussion. The goal of this proposal is to create a single document with all relevant information regarding the transfer of Internet number resources. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-04 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 14 September. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-02 Proposal Accepted and Implemented (Keep IPv6 PI When Requesting IPv6 Allocation)
by Marco Schmidt 10 Aug '15

10 Aug '15

Dear colleagues, Consensus has been reached, and the proposal for a change to ripe-641, "IPv6 Address Allocation and Assignment Policy", has been accepted by the RIPE community. This policy change removes the requirement that LIRs return their IPv6 Provider Independent (PI) assignment when requesting an IPv6 allocation if there are no specific routing requirements to justify both. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-02 The new RIPE Document is called ripe-650 and is available at: https://www.ripe.net/publications/docs/ripe-650 This proposal is implemented with immediate effect. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-01 Proposal Accepted and Implemented (Alignment of Transfer Requirements for IPv4 Allocations)
by Marco Schmidt 23 Jul '15

23 Jul '15

Dear colleagues, Consensus has been reached, and the proposal for a change to ripe-643, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. This policy change aligns the transfer requirements for all IPv4 allocations. LIRs that receive an IPv4 allocation from the RIPE NCC or via a transfer cannot subsequently transfer this allocation to another party within 24 months. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-01 The new RIPE Document is called ripe-649 and is available at: https://www.ripe.net/publications/docs/ripe-649 This proposal is implemented with immediate effect. Please note that: - All IPv4 allocation transfer requests received by the RIPE NCC after this announcement will be evaluated under the new policy. - The evaluation of transfer requests received before this announcement will be completed under the previous policy. This policy change particularly concerns IPv4 allocations made by the RIPE NCC. If the RIPE NCC made the allocation less than 24 months ago, the allocation cannot be transferred until the defined holding period has passed. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-03 New Draft Document and Impact Analysis Published (Assessment Criteria for IPv6 Initial Allocation Size)
by Marco Schmidt 09 Jul '15

09 Jul '15

Dear colleagues, The draft document for version 2.0 of the policy proposal 2015-03, "Assessment Criteria for IPv6 Initial Allocation Size", has now been published, along with an impact analysis conducted by the RIPE NCC. The proposal aims to expand the criteria for evaluating initial IPv6 allocations larger than a /29. The RIPE NCC would consider additional aspects beyond only the number of existing users and extent of the organisation's infrastructure. Some of the differences from version 1.0 include: - Introduction of new assessment criteria used to evaluate IPv6 allocations larger than a /29 - 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/participate/policies/proposals/2015-03 and the draft document at: https://www.ripe.net/participate/policies/proposals/2015-03/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 7 August 2015. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-02 Last Call for Comments (Keep IPv6 PI When Requesting IPv6 Allocation)
by Marco Schmidt 08 Jul '15

08 Jul '15

Dear colleagues, The proposal described in 2015-02, "Keep IPv6 PI When Requesting IPv6 Allocation", 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 6 August 2015 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. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-02 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 6 August 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-01 Last Call for Comments (Alignment of Transfer Requirements for IPv4 Allocations)
by Marco Schmidt 22 Jun '15

22 Jun '15

Dear colleagues, The proposal described in 2015-01, "Alignment of Transfer Requirements for IPv4 Allocations", is now in its Concluding Phase. The Address Policy Working Group co-Chair has declared that rough 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 21 July 2015 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 co-Chairs of all RIPE Working Groups for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-01 Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 21 July 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0