You are here: Home > Participate > Policy Development > Policy Proposals > Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text

Changes to Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted
delete: <h2> How Policy has Been Modernised, and Why Clean-up is Needed delete: </h2> delete: <p> Key operative provisions in the existing insert: <h3 class=" ">

Summary of Proposal insert: </h3>

insert: <p class=" ">

This proposal removes the need-based requirement for IPv4 delegations in the RIPE NCC service area. It also incorporates section 5.6 "Use of last /8 for PA Allocations" into the main policy text, removing all references to the "last /8" itself, and to the reaching of it as a future event. insert: </p>

insert: <p class=" ">

In short, the proposal does the following changes to the active policy: insert: </p>

insert: <ul>
    insert: <li>
  • Removes "Conservation" as a stated goal of the policy. insert: </li>
  • insert: <li>
  • Removes all active policy text were designed to delay the depletion of the IPv4 free address pool. Following the depletion of the IANA free pool referring to documentation, evaluation of need, and validation of actual usage for both assignments and allocations. insert: </li>
  • insert: <li>
  • Removes all text referring to the slow-start principle. insert: </li>
  • insert: <li>
  • Removes all text referring to the assignment window mechanism. insert: </li>
  • insert: <li>
  • Removes limitations on 3 February 2011, and the subsequent depletion of the RIPE NCC free pool on 14 September 2012, these are now obsolete. delete: </p> delete: <p> In anticipation of depletion, the RIPE community adopted new policies for allocations in the “last /8” (see delete: <a class="internal-link" href="resolveuid/6a95db39532fe8efc06fd305f2b82b67" target="_self" title="" data-val="6a95db39532fe8efc06fd305f2b82b67" data-linktype="internal"> 2010-02 delete: </a> ). Having reserved a /16 for unforeseen contingencies and made special provision for IXPs, the remaining space is made available on the basis of seeking to maximise the number of LIRs who will receive at least some IPv4 space, by making only a small allocation to each. Thus, each LIR is entitled to exactly a /22, even if their own needs would justify a larger allocation. delete: </p> delete: <p> These new policies governing allocations from the last /8 also apply to address space subsequently recovered by the RIPE NCC or IANA (see delete: <a class="internal-link" href="resolveuid/0d827934656098813405eef42d92d5d6" target="_self" title="" data-val="0d827934656098813405eef42d92d5d6" data-linktype="internal"> 2011-03 delete: </a> ), or redesignated for allocation from reserved blocks, if any. In other words, since depletion of the RIPE NCC free pool on 14 September 2012, these policies control all allocations by the RIPE NCC. delete: </p> delete: <p> Despite the above, LIRs applying for allocations are still also required to undergo the application procedures that were used in the previous allocation process. End Users have to provide documentation to the LIR (and/or the RIPE NCC) that prove their size and frequency of sub-allocations. insert: </li>
  • insert: </ul>
insert: <p class=" ">

  insert: </p>

insert: <p class=" ">

The goal that precipitated the requirement to demonstrate need for address space, and the LIR needs to provide similar documentation to the RIPE NCC. In all cases, the documentation has to be thoroughly vetted and archived for later auditing. The collection and collation of this information is costly, but is no longer used by the RIPE NCC to evaluate the size of the address block that should be allocated, except in the special case of IXP applicants. delete: </p> delete: <p> The policy also regulates transfers between LIRs. Before the depletion of the free address pool, LIRs had no independent incentive to avoid inappropriate transfers; an LIR could simply apply for more address space from the RIPE NCC. This created an externality (premature depletion of the free address pool) that had to be addressed through policy. After depletion of the free address pool this is no longer the case, and so the original justification for a costly delete: <i> ex ante delete: </i> assessment of need in the transfer market no longer applies. delete: </p> delete: <h2> Update of Stated Policy Goal delete: </h2> delete: <p> Existing RIPE Policy goals for IP allocation combine the concepts of conservation of the address pool, and fair distribution on the basis of need. delete: </p> delete: <p> Section delegations is explicitly stated in section 3.0.3 of the current address allocation policy policy, which reads:

delete: <p> delete: <i> “Conservation: insert: <p class=" " style="padding-left: 30px; ">

Conservation: Public IPv4 address space must be fairly distributed to the End Users operating networks. delete: <b> To maximise the lifetime of the public IPv4 address space, addresses must be distributed according to need, and stockpiling must be prevented.” delete: </b> delete: </i> delete: <i> [emphasis added] delete: </i> delete: <br /> delete: </p> delete: <p> This combines the concepts of “conservation” and “fair distribution”, the principles of distribution according to need and the imperative to avoid stockpiling, with the aim to “maximise the lifetime prevented. insert: </p>

insert: <p class=" ">

Following the depletion of the IANA free pool on the 3rd of February 2011, and the subsequent depletion of the RIPE NCC free pool on the 14th of September 2012, the "lifetime of the public IPv4 address space”. Such conflation space" in the RIPE NCC region has not weathered the transition from a situation where stewardship of the reached zero, making the stated goal unattainable and therefore obsolete. This proposal attempts to recognise this fact by removing all policy requirements that was working exclusively towards attaining this "Conservation" goal. insert: </p>

insert: <p class=" ">

The requirement to document need at the lower levels of the distribution hierarchy (LIR and below) made perfect sense when there still was remaining space in the public pools at the higher levels (RIPE NCC and IANA), because excessive delegations at the lower levels would in turn create a higher consumption rate at the higher levels, something would impact all members of the Internet community by reducing the remaining lifetime of, and preventing equal access to, the public free-for-all resource that was the remaining unallocated IPv4 address pool. insert: </p>

insert: <p class=" ">

Today, however, excessive consumption of the private IPv4 address pools on the LIR levels and below can no longer translate into an increased consumption and reduced lifetime of the remaining public IPv4 address space primarily entailed extending the lifetime of the free allocation pool to one where the free allocation pool has been depleted. delete: </p> delete: <p> This proposal would simplify the goal: delete: </p> delete: <p> delete: <i> “Fairness: Public IPv4 space, since there is nothing left. Simply put: An LIR that uses more address space must be fairly distributed to the than it needs to, only ends up hurting itself, and not the rest of the community. insert: </p>

insert: <p class=" ">

The requirement that all delegations needed to demonstrate need came with a considerable amount of bureaucracy. End Users operating networks.” delete: </i> delete: </p> delete: <p> This implicitly continues the anti-stockpiling provision: had to provide documentation to the LIR (and/or the RIPE NCC) that proved their need for address space, and the LIR need to provide similar documentation to the RIPE NCC. In all cases, the documentation had to be thoroughly vetted and archived for later auditing. The need for address space must be distributed to was also artificially limited in time, making it impossible to obtain address space to support long-term business plans. This created extra work for everyone involved. While these negative effects were previously accepted by the community as necessary to attain the "conservation" goal, they serve no real purpose today. insert: </p>

insert: <p class=" ">

By removing the requirement to document need, each individual LIR will be allowed to decide on and implement its own conservationalist policies according to what makes the most sense for them, for example based on the size of their own remaining IPv4 pool, their typical End Users operating networks. delete: </p> delete: <p> Consistent with previous RIPE Policy, we do not attempt to fully define what is a “fair distribution”, but allow that to be inferred from policy provisions present and future. This policy goal does not confer on the RIPE NCC a responsibility to judge the “fairness” of particular allocations and assignments in the abstract. The new policy goal continues to assert the RIPE community’s right to institute new policies to address User profile, or any unfairness that may arise, in the collective view of the community on the basis of rough consensus. This brings IPv4 policy into line with RIPE IPv6 Policy, which has from the beginning made a clear distinction between the two goals "Conservation" and "Fairness". delete: </p> delete: <h2> Removal of Requirement for Ex Ante Documentation of Need delete: </h2> delete: <p> This proposal would remove the delete: <i> ex ante delete: </i> documentation of need from the LIR’s application process. Such documentation was previously used by the RIPE NCC to assess whether the LIR’s need justified the allocation of the size of the address block for which the LIR had applied. delete: </p> delete: <p> Now that the RIPE NCC only allocates a single small (/22) address block, even when a larger allocation is needed, documentation of the scale of actual need is no longer necessary. delete: </p> delete: <p> The proposal other factors. They would also remove the requirement for an delete: <i> ex ante delete: </i> documentation of need by the End User seeking an assignment of be able to acquire (through transfers) address blocks sized according to their own perception of current and future need. insert: </p>

insert: <p class=" ">

The other part of the proposal incorporates the separate section describing the use of the "last /8" into the main policy text. This is prudent, as after the "last /8" policy was implemented, all address space from an LIR. Furthermore, removing this requirement would also implicitly lift the “two-year assignment period”, that is, the requirement that there must be a documented need for 50% of the assigned space within the first year of the assignment. This requirement undermines business planning, but was justified handled by the need to prevent the depletion of the free address pool. Now that that reason no longer applies, it is no longer appropriate to damage business certainty in this manner. delete: </p> delete: <p> The proposal would also remove the delete: <i> ex ante delete: </i> documentation of need for the approval by the RIPE NCC of transfers. This will maintain consistency with allocation policy. The requirement to document need in the transfer process never had an independent justification, but existed to maintain consistency with allocation policy and to prevent that policy being circumvented, leading to premature depletion of the free pool delete: <a class="anchor-link" href="#ref1" target="_self" title=""> [1] delete: </a> . delete: </p> delete: <p> Note that adoption of this proposal would not remove the requirement for need: LIR allocations and transfers, and IXP assignments issued by the RIPE NCC, will all remain is subject to a need evaluation. LIRs will still be required to confirm that they intend to make assignments to their End Users and/or their own infrastructure, and IXPs will receive an assignment sized according to their actual utilisation. delete: </p> delete: <p> The main concern that has been raised concerning the transfer market – that it might lead to stockpiling for purely speculative purposes – will remain prohibited by the policy. This is further reinforced by a provision preventing the re-transfer of address space within 24 months, a provision that also remains in place. delete: </p> delete: <h2> Making the Policy More Legible: “Clean-up” delete: </h2> delete: <p> Policy for the allocation of the last /8 was adopted in anticipation of depletion of the free pool. We therefore retained the previous policy at that time, the "last /8" policy, even blocks which continued in effect until the free pool was actually depleted on 14 September 2012. delete: </p> delete: <p> The continued presence in the policy text of those historic elements of policy which are no longer operative leads to confusion. In particular, the nomenclature of (general) “policy” and “policy for the last /8” leads to the incorrect perception that IP address blocks fall outside of the actual last /8 block (185.0.0.0/8) continue to be governed by the previous policy. In fact, IP address space recovered by the RIPE NCC is returned to the last /8 pool, and is governed by the “last /8 policy”. This proposal would clarify the text so that this is more obvious. delete: </p> delete: <p> (185.0.0.0/8), something which led to significant confusion. The proposal would does not change the effective "last /8" policy - the intention is only to clean up and reorganise the policy to make it more easily understandable. insert: </p>

insert: <p class=" ">

It also add a self-executing removal adds a "self destruct" clause (a “self destruct” clause) to the “Unforeseen Circumstances” to the "Unforeseen Circumstances" section that will ensure the prompt removal of the section if the reserved address space returns to the free pool - an event which would make the section defunct. This  would avoid the need to re-open the policy process in a completely foreseeable circumstance. delete: </p> delete: <p> prevents the community from having to to through a new PDP to clean it up. insert: </p>

insert: <p class=" ">

Furthermore, the it proposal would remove removes text suggesting that the RIPE NCC will assign PI address space to End Users in section 8.0 "PA vs. PI Address Space", also renaming it to "Types of Address Space".

delete: <p> insert: <p class=" ">

Finally, the proposal it incorporates a number of editorial improvements suggested by the RIPE NCC's Policy Development Officer.

delete: <div> delete: <br clear="all" /> delete: <hr align="left" size="1" width="33%" /> delete: <div> delete: <p> delete: <a name="ref1"> delete: </a> [1] The requirement to document need existed to prevent an LIR with need collaborating with an LIR without need acquiring address space by applying for one allocation, transferring it to the second LIR, and then re-applying to replace that address block. Such behaviour would have circumvented the allocation policy’s requirement to document need, resulting in premature depletion of the free address pool. delete: </p> delete: <p>   delete: </p> delete: <h2> insert: <h3 class=" ">

Policy Text delete: </h2> insert: </h3>

a. delete: <a class="internal-link" href="resolveuid/5a8d40ed67ea4cf0960d1a188a16eb0d" target="_self" title="" data-val="5a8d40ed67ea4cf0960d1a188a16eb0d" data-linktype="internal"> insert: <a class="internal-link" href="resolveuid/ce9d4267-d501-4c53-92a4-a2430ced54e1" target="_self" title="" data-val="ce9d4267-d501-4c53-92a4-a2430ced54e1" data-linktype="internal"> Current policy text
b. delete: <a class="internal-link" href="resolveuid/a4fb84dad3ce4575a10854afe93aa7e9" target="_self" title="" data-val="a4fb84dad3ce4575a10854afe93aa7e9" data-linktype="internal"> insert: <a class="internal-link" href="resolveuid/589dff2f-e010-4f21-ba15-b89e9903f2e1" target="_self" title="" data-val="589dff2f-e010-4f21-ba15-b89e9903f2e1" data-linktype="internal"> New policy text

delete: <h3> insert: <h3 class=" ">

Rationale

delete: <p> insert: <p class=" ">

a. Arguments supporting the proposal

insert: <p>

  insert: </p>

  1. insert: <p>

    Reduced bureaucracy. insert: </p>

    Under the proposed policy, End Users, sub-allocation holders, and LIRs will no longer be required to document their need for IPv4 addresses in order to receive PA assignments, sub-allocations, or (transferred) PA allocations. Consequently, LIRs will not be required to vet such requests, nor to maintain an archive of such requests. This greatly reduces the bureaucracy required to operate an LIR or sub-allocation holder, and may allow for things like fully automated provisioning of IPv4 addresses to End Users or LIR infrastructure.

    LIRs and sub-allocation holders will of course be free to continue to demand need-based justification from their End Users before making assignments. It is expected that most (if not all) LIRs and sub-allocation holders will do so, considering the scarcity of IPv4 addresses and their value, it would be very unwise to throw them all out the window. However, the LIR or sub-allocation holder's local conservation policies and procedures may now be adapted to suit the exact business needs of the organisation in question, instead of being limited by the RIPE community policies.

  2. insert: <p>

    Allows for long-term business planning. insert: </p>

    Under the proposed policy, the need-based time period will be raised from the current one/two years (allocation/assignments) to essentially infinity. This allow organisations to plan their use of IPv4 addresses for as long as they themselves deem sensible, without being artificially constrained by RIPE policies.

  3. insert: <p>

    Makes the policy easier to read and understand. insert: </p>

    The proposal will remove large amounts of policy text, which in itself makes the policy neater and more approachable. In particular, the removal of the Assignment Window concept is likely to help out in this regard, and also by ceasing to refer to "the last /8", which in actuality is all space held by the RIPE NCC, not only 185.0.0.0/8.

    As noted by the RIPE NCC in the delete: <a href="../resolveuid/0da918df-1407-4d35-ac09-d3c9b089efcc#impact-analysis" data-val="0da918df-1407-4d35-ac09-d3c9b089efcc#impact-analysis" data-linktype="internal"> insert: <a class="internal-link" href="resolveuid/0da918df-1407-4d35-ac09-d3c9b089efcc#impact-analysis" target="_self" title="" data-val="0da918df-1407-4d35-ac09-d3c9b089efcc#impact-analysis" data-linktype="internal"> Impact Analysis of proposal 2012-06 , " delete: <a href="../resolveuid/0da918df-1407-4d35-ac09-d3c9b089efcc" data-val="0da918df-1407-4d35-ac09-d3c9b089efcc" data-linktype="internal"> insert: <a class="internal-link" href="resolveuid/0da918df-1407-4d35-ac09-d3c9b089efcc" data-val="0da918df-1407-4d35-ac09-d3c9b089efcc" data-linktype="internal"> Revert Run Out Fairly ", diverging assignment and allocation times periods caused confusion. These are currently one and two years, respectively. By removing the need period concept completely, the assignment and allocation time periods will be perfectly harmonised.

    The proposal also removes a number passages made obsolete by depletion and subsequent implementation of the "last /8" policy, such as: "The RIPE NCC allocates enough address space to LIRs to meet their needs for a period of for a period of up to 12 months".

  4. insert: <p>

    Removes conflict between "conservation" and "aggregation". insert: </p>

    Current policy states:

    delete: <p> insert: <p style="padding-left: 30px; ">

    Conservation and aggregation are often conflicting goals.

    By removing conservation as a goal, this dilemma is no more.

  5. insert: <p>

    LIR Audits becomes less time-consuming. insert: </p>

    It is the proposer's understanding that a major part of being subjected to an LIR Audit is related to ensuring adequate documentation exists for each PA assignment having been made by the LIR being audited, and making sure that they do correctly justify the amount of assigned space. Under the proposed policy, however, LIRs will no longer be required to maintain such a documentation archive, and therefore there would be no need to validate its existence or quality as part of an LIR Audit.

  6. insert: <p>

    Reduction of RIPE NCC workload. insert: </p>

    Currently, the RIPE NCC IP Resource Analysts need to vet any assignment requests that exceed an LIRs Assignment Window, as well as to (pre-) approve any requests for allocation transfers, to make sure that the need for address space is adequately documented in each case. In addition, they need to re-examine past assignments as part of LIR Audits. Under the proposed policy, none of these tasks will be necessary, which would lead to a reduction in workload for the NCC. This in turn may lead to reduced membership fees and/or an increased focus on developing member services.

  7. Eliminate competitive advantage for insert: <p>

    Elimination of incentive to "game the system". insert: </p>

    insert: <p>

    It has been suggested on several times on public mailing lists that some LIRs that misreport need delete: <p> The need requirement in existing policy arbitrarily limits the maximum length of the LIR's business planning horizon. LIR customer contracts may have a longer duration; where this is so, the existing policy requires LIRs to under-report their true need (by only considering fall for the temptation to "game" the needs-based system, by requesting more space than they need within that the time period), leaving the periods determined by the policy. This could be anywhere from being excessively optimistic with regards to their own business growth, to outright fraud. Doing so will put those dishonest LIRs at an advantage, compared to those that to things strictly by the book. Even if an LIR to shoulder a degree of business risk. Thus LIRs that comply fully with the policy suffer increased business risk compared with LIRs that (carelessly or deliberately) overestimate their need within the planning horizon. accused of cheating in this manner is completely innocent, the mere suspicion of it is creating a hostile and unfriendly environment.

    By eliminating the planning horizon for calculating need, this policy proposal also eliminates the unintended effect of endowing non-compliant LIRs with lower business risk than their more compliant competitors. removing the need-based requirements, the playing field becomes level and fair for everyone involved, and will become impossible to get ahead by cheating.

  8. insert: <p>

    Makes IPv4 and IPv6 policies more similar in practise insert: </p>

    The current IPv6 address policy states that LIRs may receive PA allocations up to and including a /29 without providing any documentation or justification for their need. Similarly, end users may receive PA/PI assignments up to and including a /48 without providing any documentation or justification for their need. These limits so generous that they are sufficient for all but the very largest ISPs and end users. In practise, this means that the vast majority of IPv6 allocations and assignments are made without having their size be justified based on actual need. At the time of writing, this was the case for 99.3% of all IPv6 PA allocations, and 95.3% of all IPv6 PI assignments.

    This stands in stark contrast with the current IPv4 address policy, which mandates that all allocations and assignments must be sized according to documented need.

    By removing the need principle from the IPv4 policy, it will become more similar to the IPv6 policy in practise, in the sense that need justification will not be mandated for the vast majority of delegations.

delete: <p> insert: <p class=" ">

 

delete: <p> insert: <p class=" ">

b. Arguments opposing the proposal

  1. insert: <p>

    Conflicts with RFC 2050 insert: </p>

    RFC 2050 section 1, goal 1, states:

    delete: <p> insert: <p style="padding-left: 30px; ">

    1) Conservation: Fair distribution of globally unique Internet address space according to the operational needs of the end-users and Internet Service Providers operating networks using this address space. Prevention of stockpiling in order to maximize the lifetime of the Internet address space.

    Removing the needs-based principle from the IPv4 policy would be a violation of this principle. delete: <strong> delete: </strong> delete: </p> delete: <p>  

    Counter-argument:

    This goal is no longer applicable today. Following the depletion of  the the IANA and RIPE NCC allocation unallocated pools, there is nothing left to conserve. insert: </p>

    insert: <p>

    Furthermore, there is already precedence in the RIPE Community for not following RFC 2050's guidelines strictly, such as: insert: </p>

    insert: <ul>
      insert: <li>
    • The passing of proposal 2010-02 "Allocations from the last /8" was a radical departure from the needs-based distribution guidelines set forth in RFC 2050 has recently formally obsoleted by RFC 7020, whose updated goal reads: delete: </p> delete: <p style="padding-left: 30px; "> 1)  Allocation Pool Management: Due to the fixed lengths of IP addresses and AS numbers, the pools from which these resources are allocated are finite.  As such, allocations must be made in accordance with the operational needs of those running the networks that make use of these number resources and by taking into consideration pool limitations at the time of allocation. delete: </p> delete: <p> The proposed policy upholds the (e.g., "Initial allocation will not be based on any current level of operational need  justification required in order to receive IPv4 addresses from the NCC's allocation pool (the so-called "last /8" pool): LIRs must confirm that they will make assignments to their End Users and/or their own infrastructure in order to receive their final /22 allocation, while IXPs must demonstrate or future utilisation requirements in order to receive an assignment larger than the minimum size. Therefore, the proposed policy is compliant with RFC 7020's goal 1 (at least to the same extent our current policy is). delete: </p> delete: <p>   delete: </p> routing restrictions but on demonstrated requirements").
    • RFC 2050 section 2.1 demands that in order to qualify for an allocation, an ISP must be either connected to an IXP or be multihomed. However, neither of these requirements are present in the current IPv4 policy document. insert: </li>
    • insert: </ul>
    insert: </li>
  2. insert: <li>
  3. insert: <p>

    Conflict with ARIN's Inter-RIR transfer policy delete: <p> delete: <a class="external-link" href="https://www.arin.net/resources/request/transfers_8_4.html" target="_self" title=""> insert: </p>

    insert: <p>

    https://www.arin.net/resources/request/transfers_8_4.html delete: </a> states:

    delete: <p> insert: <p style="padding-left: 30px; ">

    Inter-RIR transfers may be completed between ARIN and another RIR as long as that RIR RIRf has: [...]

    delete: <p> insert: <p style="padding-left: 30px; ">

    * Needs-based general number resource policies

    The proposed policy would conflict with the above requirement, making transfers beween the RIPE NCC and ARIN service areas impossible. delete: <strong> delete: </strong> delete: </p> delete: <p>  

    Counter-argument:

    The ARIN policy goes on to say:

    delete: <p> insert: <p style="padding-left: 30px; ">

    Currently, APNIC is the only RIR with a reciprocal, compatible inter-RIR transfer policy.

    In other words, transfers between the RIPE NCC and ARIN service areas are impossible to begin with. The proposed policy will not change this one way or the other.

    Furthermore, it is worth noting that ARIN still have remaining addresses in their free pool. It is therefore prudent of them to insist that all downstream delegation paths uphold the needs based principle, even including out-of-region transfers. When ARIN depletes, it could well be that their priorities in this regard will change.

    delete: <p>   delete: </p>
  4. insert: <p>

    A (wealthy) LIR may hoard all space available on the market. insert: </p>

    In the words of Michiel Klaver ( delete: <a class="external-link" href="https://www.ripe.net/ripe/mail/archives/address-policy-wg/2012-October/007258.html" target="_self" title=""> insert: <a class="external-link" href="http://www.ripe.net/ripe/mail/archives/address-policy-wg/2012-October/007258.html" target="_self" title=""> https://www.ripe.net/ripe/mail/archives/address-policy-wg/2012-October/007258.html ):

    delete: <p> insert: <p style="padding-left: 30px; ">

    Removing the needs-based requirement would break open the entire IPv4 market, letting big corporations to buy everything available and then decide who they are willing to sell it for the highest price.

    delete: <p> insert: <p style="padding-left: 30px; ">

    IP addresses will become a tool to obstruct competitors, wipe-out all smaller players and locking the market for newcomers. An authority validating each request with the current policies could somewhat prevent that from happening. delete: <strong> delete: </strong> delete: </p> delete: <p>  

    Counter-argument:

    This argument would apply equally well to any freely traded commodity, especially ones that are in limited supply (for example real estate). However, these markets function well and in a competitive manner, and there is no reason why the trade of IPv4 addresses will be any different. Even if that turns out not to be the case, most (if not all) juridstictions in the RIPE NCC service area have laws against anti-competitive practices, monopolies, cartels, price fixing, et cetera. There is no reason to duplicate these in the RIPE policies, as the law will in any case always take precedence.

    Furthermore, there is a 24 months cooling-off period during which a recently transferred resource cannot be transferred further. This prevents LIRs from using IPv4 address space as a short-term investment or speculation object. This particular restriction is not lifted by this policy proposal.

delete: <p>   delete: </p>

Impact Analysis

In order to provide additional information related to the proposal, details of an impact analysis carried out by the RIPE NCC are documented below. The projections presented in this analysis are based on existing data and should be viewed only as an indication of the possible impact that the proposal might have if it is accepted and implemented.

insert: <p>

  insert: </p>

A. The RIPE NCC's Understanding of the Proposed Policy

The RIPE NCC’s understanding of the proposed policy is presented with emphasis on the following matters: delete: <strong> delete: </strong> delete: </p> delete: <p> delete: <strong> delete: <br /> delete: </strong> delete: </p> delete: <p> delete: <strong> insert: </p>

insert: <p>

insert: <b> Final IPv4 /22 Allocations delete: </strong> insert: </b>

It is the RIPE NCC’s understanding that final IPv4 /22 allocations issued from the last /8 would require LIRs to confirm that assignment(s) will be made from that allocation. would not require a demonstration of need. This would be true for both new LIRs receiving their first (and final) /22 allocation, and existing LIRs receiving their final /22.

delete: <br /> delete: </b> delete: </p> delete: <p> delete: <b> Transfer of Allocations delete: </b> delete: </p> delete: <p> It is stated in section 5.5:  delete: </p> delete: <p> delete: <em> “Re-allocated blocks are no different from the allocations made directly by the RIPE NCC and so they must be used by the receiving LIR according to the policies described in this document.” delete: </em> delete: </p> delete: <p> It is the RIPE NCC’s understanding that the receiving LIR would be required to confirm that it would make assignment(s) from the transferred allocation(s). delete: <em> delete: </em> delete: </p> delete: <p> delete: <strong> delete: <br /> delete: </strong> delete: </p> delete: <p> delete: <strong> Validity of an Assignment delete: </strong> insert: </b>

It is stated in section 6.3:  delete: <em> delete: </em> delete: </p> delete: <p> delete: <em> insert: </p>

insert: <p>

insert: <i> "All assignments are valid as long as the original criteria on which the assignment was based are still valid…" delete: </em> insert: </i>

Assignments made prior to the proposed policy were based on the evaluation of demonstrated need, and for a specific purpose. The RIPE NCC understands that these criteria must still be in place for these assignments to be considered valid. delete: <strong> delete: </strong> delete: </p> delete: <p> delete: <strong> delete: <br /> delete: </strong> delete: </p> delete: <p> delete: <strong> insert: </p>

insert: <p>

insert: <b> Contractual Requirements for Independent Internet Number Resources delete: </strong> insert: </b>

The policy proposal removes references to ripe-452, “ delete: <em> insert: <i> Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region delete: </em> insert: </i> ”.

Despite this reference being removed, the RIPE NCC understands that a contractual relationship with a sponsoring LIR or the RIPE NCC would remain a policy requirement for Provider Independent (PI) Internet provider independent number resources. This requirement would cover independent resources that have already been assigned, as well as those that will be assigned in future (e.g. IXP assignments).     delete: <strong> delete: </strong> delete: </p> delete: <p> delete: <strong> delete: <br /> delete: </strong> delete: </p> delete: <p> delete: <strong> insert: </p>

insert: <p>

insert: <b> Internet Exchange Point Assignments delete: </strong> insert: </b>

It is stated in section 6.1:  delete: <em> delete: </em> delete: </p> delete: <p> delete: <em> insert: </p>

insert: <p>

insert: <i> "New IXPs Internet Exchange points will be assigned a /24. Should they require a larger assignment, they must Internet exchange points may return their current assignment this /24 (or existing PI used as an IXP an IXP peering LAN) should they run out of space and receive a replacement /23 larger (/23, or /22. After one year the /22 if utilisation of the new assignment must be at least 50%, unless special circumstances are defined. delete: </em> " requires) assignment." insert: </i>

It is the RIPE NCC’s understanding that Internet Exchange Point assignments larger than /24 would be made based on documented calculations that allow the some form of utilisation to be estimated one year after the date of assignment. This requirement. It is not clear, however, whether the RIPE NCC would evaluate this requirement. If so, there is no specified timeframe to base the utilisation upon, nor what utilisation percentage should be at least 50% of the assignment.  delete: </p> delete: <p> delete: <strong> delete: <br /> delete: </strong> delete: </p> delete: <p> delete: <strong> used. More guidance from the community is required. insert: </p>

insert: <p>

insert: <b> Inter-RIR Transfers delete: </strong> delete: </p> delete: <p> There is currently no inter-RIR transfer policy in place in the RIPE NCC service region. If such a policy were to be adopted in future, it insert: </b> insert: <b> insert: </b> insert: </p>

insert: <p>

It is the RIPE NCC’s understanding that removing the the proposed policy would conflict with the requirements for inter-RIR transfers from regions where a needs-based requirement for transfers could conflict with the requirements for inter-RIR transfers in other RIR service regions where a needs-based requirement is still in place. This potential lack of compatibility could result in between the policies may lead to organisations being unable to transfer Internet number resources to/from other RIR service regions.  regions. insert: </p>

insert: <p>

 

B. Impact of Policy on Registry and the Addressing System

Removing the needs-based requirement would facilitate transfers within the RIPE NCC service region. intra-RIR transfers. This may have a positive effect on the quality of registry the Registry data, as organisations will have greater incentive to inform the RIPE NCC when a transfer takes place.

As mentioned above, it is important to highlight that the proposed policy would not be compatible with the inter-RIR transfer policies in other RIR service regions as they currently stand. This could be considered an impediment to organisations that want to transfer Internet number resources between regions. between  regions. This may create an incentive not to inform the RIR about inter-RIR transfers, which could lead to a reduction of data accuracy in the registry. Registry.

 

delete: <strong> Address/Internet Number Resource Consumption delete: </strong> Consumption:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

 

delete: <strong> Fragmentation/Aggregation delete: </strong> Fragmentation/Aggregation:

The RIPE NCC is not aware of related historical datasets to analyse, or applicable projections to apply to this situation. The amount of fragmentation/aggregation will mostly depend on the number of blocks being transferred and the size and alignment of these blocks. In the majority of cases, the RIPE NCC expects that a transfer would result in the original block becoming fragmented. Most likely, the degree of extra fragmentation will be correlated with the number of transfers made.

insert: <p>

  insert: </p>

C. Impact of Policy on RIPE NCC Operations/Services

The RIPE NCC expects that the adoption of this policy would have a significant impact on our operations and services. Many external and internal procedures, documentation, tools and services would need to change. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> Registration Services delete: </strong> delete: </p> delete: <p> If accepted, Services: insert: </p>

insert: <p>

It is expected that the proposed policy would remove the lead to a reduction in the workload of the RIPE NCC, as there would be no more need to evaluate assignments. The related Provider Aggregatable (PA) assignments, which assignment tickets represent around 10% between 10-11% of the overall tickets handled by Registration Services since reaching the last /8. However, when further considerations are taken into account, this is expected to have a neutral impact, rather than lead to a reduction in workload.

As defined in section 3.0.3 of the policy proposal:

“Registration: Registration: delete: </i> delete: <em> The provision of a public registry documenting address space allocations and assignments…” delete: </em> insert: </i>  

Registration remains a goal of the registry Registry system. Currently, LIRs need to register a RIPE Database object for each assignment made, in order to demonstrate utilisation of the address space. Furthermore, the RIPE Database object for an assignment is often created automatically when the assignment request has been approved (through the LIR Portal “PA Assignment Wizard”). With the removal abolishment of the needs-based requirement, these two incentives for registering the assignment in the RIPE Database will no longer exist.

For this reason, there is an expectation that the RIPE NCC’s activities will shift from evaluating assignment requests to ensuring that assignments made by LIRs are properly registered in the RIPE Database (via auditing activity). It is also expected that new LIRs will need more education on assignment registrations, as well as increased assistance to help them develop their internal assignment guidelines.

The expected increase in workload to support proper registration will be balanced by no longer having to evaluate PA assignments. As a result, the overall impact on Registration Services is expected to be neutral. delete: </p> delete: <p>  

delete: <strong> External Relations delete: </strong> delete: </p> delete: <p> Even though it remains important to explain the nature of this policy change to the various stakeholders, impact to the external relations department is expected to be limited and doesn't impose a change in regular operational workload. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <strong> Billing/Finance Department delete: </strong> Department:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

 

delete: <strong> RIPE Database delete: </strong> RIPE Database:

After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.

 

delete: <p> delete: <strong> Business Applications Department delete: </strong> delete: </p> delete: <p> This proposal is expected to have a low-to-medium impact if it is implemented. delete: </p>

D. RIPE NCC Executive Board

The RIPE NCC Executive Board notes the improvement to the would like to emphasise the following considerations relating to the discussion of the policy proposal and its implementation if accepted: insert: </p>

insert: <ul>
    insert: <li>
  • In light of the legal considerations outlined in the following section, it may be prudent to increase the budget allocated to the RIPE NCC’s legal activities. insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • The new approach to resource distribution outlined in the proposal has the potential to put pressure on the understanding the RIPE NCC has established with the Dutch tax authorities relating to its operations. insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • The RIPE NCC has been under increased scrutiny from multiple parties outside the technical community. In many cases, the RIPE NCC has referred to the needs-based principle as evidence of the fairness and transparency of allocations under the RIR system. If this principle were to be eliminated, one of the main argumentative mainstays to defend bottom-up industry self regulation would be gone. The RIPE NCC, as well as the technical community, would have to prepare for increased outreach and education efforts with participants in the Internet Governance debate. insert: </li>
  • insert: </ul>
insert: <p>

  insert: </p>

insert: <p>

In addition, the Executive Board would like to highlight the following potential consequences for LIRs:   insert: </p>

insert: <ul>
    insert: <li>
  • As mentioned in previous sections, the policy proposal would negatively affect the ability of LIRs to engage in inter-RIR transfers, as the RIPE NCC’s service region would be the only one without a needs-based requirement for transfers. insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • Implementation of the policy could expose LIRs to legal challenges under EU competition impact analysis by the introduction of the "fairness" principle. Unless the community comes up with an appropriate definition of "fairness", the Executive Board suggests that definition of this principle in this context be left to the RIPE NCC. law. insert: </li>
  • insert: </ul>
insert: <p>

 

E. Legal Impact of Policy

delete: <p class=" "> insert: <p>

EU Competition Law Considerations

delete: <p class=" "> As mentioned in the insert: <p>

An impact analyses prepared for previous versions of analysis regarding EU competition law considerations has been carried out in cooperation with an external legal advisor and is available insert: <a class="internal-link" href="resolveuid/89b79496-cb4f-495c-98ef-2aa4592b3de9" target="_self" title="" data-val="89b79496-cb4f-495c-98ef-2aa4592b3de9" data-linktype="internal"> here insert: </a> . insert: </p>

insert: <p>

The basic points from this proposal, from analysis are: insert: </p>

insert: <ul>
    insert: <li>
  • From an EU competition point of view, it is important that IPv4 allocations and transfers are conducted in a way that cannot be seen as discriminatory or exclusionary. delete: </p> delete: <p class=" "> insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • The fact that the allocation of IP addresses by the RIPE NCC has allocated IPv4 addresses occurred on the basis of the proof of objective need, rather than purely economic considerations, has protected the RIPE NCC from competition law claims. insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • After depletion, IPv4 allocations and transfers should continue to be conducted in a non-discriminatory or non-exclusionary way, the needs-based requirement continues to be relevant, particularly if there is a risk of stockpiling. delete: </p> delete: <p class=" "> The “fairness” requirement, which is even broader than the “need” requirement, can indeed insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • Removing the needs-based requirement would create an exposure to competition law claims based on discriminatory treatment or refusal to supply. insert: </li>
  • insert: </ul>
insert: <ul>
    insert: <li>
  • Competition law claims would be mainly addressed to LIRs that could be seen as a way to prevent coordinating in stockpiling and applying discriminatory or exclusionary behavior. delete: </p> delete: <p class=" "> Details about the “fairness” requirement are given in the explanatory text of the proposed policy. In particular: delete: </p> practices. Such claims may also be addressed to the RIPE NCC, if only in order to make more publicity for the claim. insert: </li>
  • insert: </ul>
  • LIR allocations and transfers, and IXP assignments issued As these kinds of complaints can be initiated by the RIPE NCC will remain subject to a need evaluation: LIRs will still be required to confirm that they intend to make assignments to End Users and/or their own infrastructure, and IXPs will receive a national competition authority or the European Commission, it is important to highlight that removing the needs-based requirement could be an assignment sized according to their actual utilisation. delete: </li> delete: <li> Stockpiling for purely speculative purposes will remain prohibited by the policy. This is further reinforced by a provision preventing the re-transfer of address space within 24 months. incentive for governmental actors wanting to step in.
The explanatory text also clarifies that the new policy goal continues to assert the RIPE community’s right to institute new policies to address any unfairness that may arise, in the collective view of the community on the basis of rough consensus. delete: </div> delete: </div> insert: <p>

  insert: </p>

insert: <p>

Draft documents relating to "No Need – Post-Depletion Reality Adjustment and Cleanup": insert: </p>

Draft documents relating to "Post Depletion Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text"
Post Depletion No Need – Post-Depletion Reality Adjustment of Procedures to Match Policy Objectives, and Clean-up of Obsolete Policy Text Cleanup
Get Involved

The Address Policy Working Group develops policies relating to the allocation and registration of Internet number resources (IPv4 and IPv6 addresses and ASNs) by the RIPE NCC and its members. Anyone with an interest in Internet numbering issues is welcome to observe, participate and contribute to the WG. To post a message to the list, send an email to [email protected] Please note that only subscribers can post messages.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.