You are here: Home > Participate > Policy Development > Policy Proposals > RIPE NCC Services to Legacy Internet Resource Holders

Changes to RIPE NCC Services to Legacy Internet Resource Holders

Legend (+) Added (-) Deleted
Changed Tag Added Tag Deleted

Summary of Proposal

A framework is proposed as the basis for rigorous maintenance of registration data and for delivery of registry services to legacy Internet resource holders in the RIPE NCC service region.

delete: <b> Policy Text delete: </b>

delete: <p> delete: <b> New delete: </b> delete: </p>

[Following text will result in a new RIPE Policy Document “RIPE NCC Services to Legacy Internet Resource Holders“]

delete: <b> Abstract: delete: </b> Abstract

This proposed framework establishes the principles to be applied by the RIPE community in offering and implementing registry services for legacy Internet resource holders. The importance of maintaining accurate records in the RIPE database is recognised as principal. the NCC's principal task.  The community of legacy Internet resource holders is defined. Some rights of members of this community are described, as are the principles governing the manner in which the RIPE NCC should engage with and provide services to this community.

delete: <p>   delete: </p>

delete: <b> 1.0 Introduction and Definitions delete: </b>

Legacy resource holders were granted internet resources before the creation of the RIPE NCC. The principal purpose of the RIPE NCC is to maintain an accurate RIPE NCC maintains and publishes registry of Internet IP number and AS resources in the RIPE service region: Europe, the Middle East, and Central Asia. To this end, the RIPE NCC maintains a registry (the 'RIPE database') of data for resources held by their members and for these legacy resources [ insert: <a class="anchor-link" href="#refs"> 1 insert: </a> ], [ insert: <a class="anchor-link" href="#refs"> 2 insert: </a> ], [ insert: <a class="anchor-link" href="#refs"> 3 insert: </a> ], [ insert: <a class="anchor-link" href="#refs"> 4 insert: </a> ].It strives to maintain the accuracy of these data.  The RIPE NCC also provides reverse DNS delegation and a routing registry for IP address and Autonomous System Numbers, both members and of which include legacy resources. insert: </p>

insert: <p>

Historically, legacy resource holders. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> Members delete: </b> are those local Internet registries (LIRs) who holdings have signed a contract for services and pay recurring fees to the RIPE NCC for those services. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> Legacy resource been kept outside any insert: <b> insert: </b> formal relationship between their holders delete: </b> are those (natural or formal persons) who hold Internet and the RIPE NCC, even in insert: <b> insert: </b> cases where such a relationship covers other resources assigned before the creation of the RIPE NCC; these have not signed contracts for services for those resources and have not paid corresponding fees. delete: </p> delete: <p> The RIPE NCC maintains accurate held by the insert: <b> insert: </b> same holder. To improve the accuracy and trustworthiness of the insert: <b> insert: </b> registry data for both member resources and legacy resources. In respect of these data, it provides as delete: <b> basic services: delete: </b> the means for resource holders to maintain the registry data relating to their resources; publication, via delete: <i> whois delete: </i> and related services, of this data; and the provisioning of relevant delegation records in the reverse DNS. delete: </p> delete: <p> In addition, the RIPE NCC provides, or may provide, delete: <b> additional services delete: </b> complementing these basic services. delete: </p> delete: <p> Legacy resource holders are willing to contribute to the costs of the services which they use. In addition, provision of new services, such as certification of legacy resources is a desirable goal, and it is understood that such services will have costs. delete: </p> delete: <p> This proposal outlines a framework under which the RIPE NCC and a number of legacy resource holders insert: <b> insert: </b> have indicated that a formal relationship is desirable. insert: </p>

insert: <p>

Some of the legacy holders are also interested in a more formal relationship which would give clarity regarding services and allow them to participate in the RIPE NCC's cost-sharing model. insert: </p>

insert: <p>

This framework defines the basis for rigorous maintenance of registration data and for delivery of registry services to legacy Internet resource holders in the RIPE NCC service region. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <b> 1.1 Definitions insert: </b> insert: </p>

insert: <p>

The following definitions apply in this policy and are of particular importance to the understanding of the goals described in this document. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <b> Internet Resource: insert: </b> An IP address block or Autonomous System number. insert: </p>

insert: <p>

insert: <b> Legacy Internet Resource: insert: </b> Any Internet Resource granted before the current system of insert: <b> insert: </b> hierarchical distribution (by allocation or assignment) insert: <b> insert: </b> through the Regional Internet Registries became operational. insert: </p>

insert: <p>

insert: <b> Legacy Internet Resource Holder: insert: </b> The holder of a Legacy Internet Resource. Either by receiving insert: <b> insert: </b> these resources directly or by receiving (part of) Legacy Internet insert: <b> insert: </b> Resources from a Legacy Internet Resource Holder. insert: </p>

insert: <p>

insert: <b> Registry Services: insert: </b> Services provided by the RIPE NCC in its capacity as a Regional insert: <b> insert: </b> Internet Registry, including the following and such additional insert: <b> insert: </b> services as may become first class citizens of the family which they founded in the distant past, and pay the reasonable costs of the services which they use. delete: </p> delete: <p>   delete: </p> delete: <h3> 2.0   Legacy be identified from time to time as registry services: insert: </p>

insert: <ul>
    insert: <li>
  • Maintenance of data relating to Internet Resources and the RIPE Database delete: </h3> delete: <p> delete: <b> 2.1   RIPE NCC as RIR delete: </b> delete: </p> delete: <p> The registry function of RIPE NCC was originally defined in RIPE-19 [2]: delete: </p> delete: <p> "The RIPE NCC will function as a `Delegated Registry' for IP numbers in Europe, as anticipated and defined in RFC 1174.” delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 2.2   Responsibility of RIR to maintain registry delete: </b> delete: </p> delete: <p> The responsibility of RIPE NCC to maintain a registry of Internet resources, both for resources allocated by RIPE NCC itself and legacy resources, is acknowledged in RIPE-508 [3]: delete: </p> delete: <p> "The responsibility for record keeping covers Internet number resources allocated to the RIPE NCC by the IANA, as well as Internet number resources that were distributed in the RIPE NCC region by the IANA prior to the RIPE NCC's existence. These resources are known as Early Registration Transfers (ERX), or legacy space." delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 2.3   Benefit of this registry not only to resource holder but to community delete: </b> delete: </p> delete: <p> The maintenance and publication of accurate registry the NCC in their Internet Resource registry; insert: </li>
  • insert: <li>
  • Access to these data for each Internet resource provide necessary information for a number of essential network-management activities, including technical troubleshooting and response to incidents of abuse.  Availability of this data is thus of benefit to the Internet community as a whole, and not just to the holder of the resource. delete: </p> delete: <p> In view of this benefit, neither deliberate removal of nor refusal to allow legitimate updates to registry data should be considered. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 2.4   Joint responsibility between RIR and resource holder for quality of data delete: </b> delete: </p> delete: <p> The joint responsibility for keeping the registry data correct and up to date is recognised in RIPE-508 [3]: delete: </p> delete: <p> "The RIPE NCC has the responsibility for keeping the Registry comprehensive, correct and up-to-date. To do this, the RIPE NCC relies on Resource Holders to supply data that pertains specifically to the Resource Holder, as documented in the RIPE NCC Standard Services Agreement [ripe-435] and/or the Independent Assignment Request and Maintenance Agreement [ripe-462]. For holders of legacy resources this responsibility is derived from the original allocation by the IANA Internet Registry." delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 2.5   Requirement on RIR not to obstruct application of updates by holder delete: </b> delete: </p> delete: <p> The RIR must not obstruct the application of legitimate updates to legacy resource data. It must continue to provide means to authenticate access to legacy resource data update by or on behalf of the holder, and so protect against abusive updates. delete: </p> respective holder; insert: </li>
  • insert: <li>
  • Public availability of registration data; insert: </li>
  • insert: <li>
  • Certification of these data; and insert: </li>
  • insert: <li>
  • Delegation of reverse DNS to the registered DNS servers. insert: </li>
  • insert: </ul>

 

insert: <p>

insert: <b> 1.2 Scope insert: </b> insert: </p>

insert: <p>

The framework described in this document applies to the provision of Registry Services by the RIPE NCC in respect of Legacy Internet Resources. Any other services offered by the RIPE NCC (whether different in nature, or relating to other kinds of resources) are out of scope for this policy. insert: </p>

insert: <p>

  insert: </p>

3.0   Rights and Obligations of Legacy Internet Resource Holders insert: <b> 2.0 Relationship between Legacy Internet Resource Holder and RIPE NCC insert: </b>

delete: <b> 3.1   Rights pre-date formation of RIRs delete: </b> delete: </p> delete: <p> Legacy Internet resources were assigned directly to their original holders either A direct or indirect contractual relationship between a Legacy Internet Resource Holder and the RIPE NCC provides contractual certainty to both parties regarding services, rights, and responsibilities.  Such a relationship also provides for payment of appropriate fees for services provided by IANA itself or by a global Internet registry acting under IANA's delegated authority prior to the formation of any of the regional Internet registries.  The rights and obligations of the current holder of any the RIPE NCC. Different methods for establishing such resource a relationship are restricted only by the terms of the original direct assignment, except in case the resource holder for the time being has freely exercised the right to surrender the resource. delete: </p> delete: <p> The following subsections (3.2 — 3.7) identify, but not exhaustively, those rights which must be understood, in the absence of contemporary documentation relating to the original assignment, to be enjoyed by legacy Internet resource holders with respect to the legacy resources which they hold. delete: </p> delete: <p> In case such documentation is available, the conditions therein specified as to the rights and obligations of the resource holder shall have force. In case the originally specified conditions make provision for the conditions to be amended and amendments have been made according to such provision, the most recently amended version of the conditions as to rights and obligations shall have force. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 3.2   Right to use delete: </b> delete: </p> delete: <p> Unless otherwise specified in the documentation (if any) mentioned in subsection 3.1 above, legacy Internet resources may be used as their holders see fit. This includes, but described below in sections 2.1, 2.2, 2.3, and 2.4. insert: </p>

insert: <p>

If, through no fault of the Legacy Internet Resource Holder involved, it is not restricted to their use as end-point and routing identifiers on the global public Internet. possible for such a contractual relationship to be established between the Resource Holder and the RIPE NCC, it may still be possible to establish a relationship which gives sufficient certainty to either party for the registry services available from the RIPE NCC to be offered to the Resource Holder. The approach to be taken in such circumstances is described below in section 2.5. insert: </p>

insert: <p>

Section 2.6 below applies in all other cases.

 

3.3 Right to exercise responsibility for quality of data delete: </b> delete: </p> delete: <p> In any case, the holder of a legacy resource shall have the right to exercise the responsibility mentioned in subsection 2.4 above. 2.1 Legacy Internet Resource Holder is already a RIPE NCC member insert: </b> insert: </p>

insert: <p>

If the Legacy Internet Resource Holder is already a RIPE NCC member then there is already a contractual relationship between the RIPE NCC and the Resource Holder, who may extend the existing contract by registering the Legacy Internet Resources involved subject to the conditions defined in section 3 below.

 

3.4   Right of succession delete: </b> delete: </p> delete: <p> Unless otherwise specified in the documentation (if any) mentioned in subsection 3.1 above, legacy Internet resources may be inherited and assigned. 2.2 Option to become a RIPE NCC member insert: </b>

A legacy Internet resource holder may be subject to merger, acquisition, or change in legal personality.  A legacy Internet resource holder Legacy Internet Resource Holder who is a natural person not already a RIPE NCC member may opt to become a member by establishing a membership contract under which the Legacy Internet Resources involved will sooner or later suffer death. delete: </p> delete: <p> In such an event, that holder's heir, successor, or assign (as the case may be) shall immediately after the event enjoy the same rights and then be registered subject to the same obligations with regard to each legacy Internet resource involved as the prior holder enjoyed or was subject to immediately before the event. conditions defined in section 3 below.

 

3.5   Right of transfer delete: </b> delete: </p> delete: <p> Unless otherwise specified in the documentation (if any) mentioned in subsection 3.1 above, the holder for the time being of a legacy Internet resource may transfer or sell that resource. delete: </p> delete: <p> In such an event, the recipient of the resource shall immediately after the event enjoy the same rights and be subject to the same obligations with regard to each legacy Internet resource involved as the prior holder enjoyed or was subject to immediately before the event. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 3.6 Right of surrender delete: </b> delete: </p> delete: <p> Unless otherwise specified in the documentation (if any) mentioned in subsection 3.1 above, the holder for the time being of any legacy Internet resource is free to surrender the resource irrevocably at any time and at the holder's sole discretion either directly to IANA or to the Regional Internet Registry of the holder's choice. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 3.7   Freedom from obligations delete: </b> delete: </p> delete: <p> Unless otherwise specified in the documentation (if any) mentioned in subsection 3.1 above, the holder for the time being of a legacy Internet resource  is not subject to any obligations in relation to the resource. delete: </p> delete: <p>   delete: </p> delete: <h3> 4.0   Engagement with Holders of Legacy Internet Resources delete: </h3> delete: <p> When engaging with the holders of legacy Internet resources, communications from the RIPE NCC should be transparent, so that all parties understand the full situation, and should have respect for any existing relationships between legacy resource holders and NCC members so that the most appropriate contact channel can be used (be that directly or via an existing LIR.) delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 4.1   Transparency: delete: </b> delete: </p> delete: <p> delete: <b> 4.1.1   Acknowledgement of rights delete: </b> delete: </p> delete: <p> RIPE NCC acknowledges that it has no authority to curtail or modify the rights or obligations of the holder of any legacy resource with regard to that resource. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 4.1.2   Disclosure of options delete: </b> delete: </p> delete: <p> All options available to the legacy resource holder should be disclosed in the initial communication, including those specified in section 5.0. Any difference from the services currently provided to a legacy resource holder should be described. Charges for each option and corresponding services should be clearly described. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 4.1.3   Offer of additional services delete: </b> delete: </p> delete: <p> Additional services, if any, offered by an RIR only to a member or through a member as intermediary, and which have not  historically been available available to non-members,  may also be described and offered. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 4.2 Respect delete: </b> delete: </p> delete: <p> delete: <b> 4.2.1 No coercion delete: </b> delete: </p> delete: <p> Legacy Resource Holders may not be rushed or coerced into a quick decision because of urgent operational needs. delete: </p> delete: <p> In particular, when the holder of legacy Internet resource requires the data for that resource to be updated for pressing operational reasons, the RIR must not seek to impose the conclusion of a (direct or indirect) contractual relationship as a precondition to accepting the update. delete: </p> delete: <p> Each legacy resource holder who has agreed to terms with the RIPE NCC prior to the adoption of this policy must be individually contacted and offered terms consistent with this policy, without the establishment of any deadline to produce a decision. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 4.2.2   Contact via LIR using apparent existing relationships delete: </b> delete: </p> delete: <p> The objective of reliable registration data is most likely to be met if the RIPE NCC uses the help of its existing members to contact legacy resource holders with whom there is an apparent relationship. delete: </p> delete: <p> A phased procedure should be followed similar to that followed in the implementation of RIPE-452. Existing members who contact their legacy holder customers should be given adequate information to describe the available options to their customers, and offer the appropriate services (such as registration through a sponsoring LIR) where preferred. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 4.2.3   Contact directly only in last resort delete: </b> delete: </p> delete: <p> Consistent with phase 3 of the implementation of RIPE-452 for Provider-Independent space holders, the holders of legacy resources that cannot be associated with a likely sponsoring LIR should be contacted directly by the RIPE NCC. delete: </p> delete: <p>   delete: </p> delete: <h3> 5.0   Services for Legacy Internet Resource Holders delete: </h3> delete: <p> delete: <b> 5.1   Reasonable conditions delete: </b> delete: </p> delete: <p> delete: <b> 5.1.1 Maintenance of rights delete: </b> delete: </p> delete: <p> No offer by the NCC of service to the holder of any legacy Internet resource, whether directly or through a sponsoring LIR, may be subject to a condition of waiver or surrender of any of the holder's rights in respect of that resource. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 5.1.2 Protection against abuse of RIR monopoly delete: </b> delete: </p> delete: <p> No basic service which is required to support the effective use of a legacy Internet resource may be withdrawn or withheld from the holder of that resource unless an equivalent service is available at a cost which is reasonably justifiable by reference to current market availability of comparable services. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 5.2   2.3 Option to engage via sponsoring LIR

The holder of a legacy Internet Resource shall have the option of obtaining NCC services in respect of that resource via a sponsoring LIR. This option will require the signing of a A Legacy Internet Resource Holder who either is not already a RIPE NCC member or, being a member, does not wish to extend the membership contract as provided in section 2.1 above may opt to enter into a contract with a RIPE NCC member who is willing to act as a Sponsoring LIR for the purposes of registering the Legacy Resources involved, subject to the conditions defined in section 3 below, and subject to approval by the RIPE NCC of the form of contract between the sponsoring Resource Holder and the Sponsoring LIR. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <b> 2.4 Option to engage directly with the RIPE NCC insert: </b> insert: </p>

insert: <p>

A Legacy Internet Resource Holder whose circumstances match those described in section 2.3 above, but cannot find a Sponsoring LIR and the holder of the resource, describing with which services will be provided.  The a mutually satisfactory contract must explicitly acknowledge of the kind mentioned in that the rights and obligations of the section, may opt to enter a non-member service contract with the RIPE NCC for the purposes of registering the Legacy Resources involved, subject to the conditions defined in Section 3 below. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <b> 2.5 When there are obstacles for 2.1/2.2/2.3/2.4 insert: </b> insert: </p>

insert: <p>

Due to specific enduring or temporary circumstances, a legacy Internet resource holder with regard to the legacy resources involved remain unchanged as they were prior to conclusion of the contract. delete: </p> delete: <p> The sponsoring LIR acting in good faith may be unable to enter into a relationship of any of the kinds described above (2.1 .. 2.4).  In such a case, the RIPE NCC will be responsible for declaring the existence of each such contract concluded with a legacy Internet resource holder to the RIPE NCC and also for giving sight of the contract to the RIPE NCC if so requested. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 5.3 Option to become a RIPE NCC member delete: </b> delete: </p> delete: <p> The holder of a legacy Internet resource shall have the option of becoming a member of the RIPE NCC.  The contract for membership and service must explicitly acknowledge that the rights and obligations of the legacy Internet resource holder with regard to each legacy resource involved remain unchanged as they were prior to conclusion of the contract. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 5.5 Recommendations as to charging for services delete: </b> delete: </p> delete: <p> Current market prices for a comparable service must be taken as a point of reference in identifying the reasonable cost of a service offered by the RIPE NCC in respect of a legacy Internet resource. delete: </p> delete: <p> It is noted that, as of August 2012, commercial domain-name registrars are able to offer and provide services comparable to the basic services defined above at a tax-inclusive retail price of about twenty euro. delete: </p> delete: <p> In the case that the holder of a legacy Internet resource opts to engage via a sponsoring LIR and wishes to avail only of basic registry services as defined above, assessment of the billing category of the sponsoring LIR should take account of the legacy resource using a score if a contractual relationship of one of the kinds described above had been established, and shall do so for as long as the circumstances continue which constitute an obstruction to the establishment of a contract. insert: </p>

insert: <p>

However, notwithstanding the preceding paragraph, the RIPE NCC may refuse to provide any specific registry service for which particular technical requirements apply, which the Resource Holder is unable to meet. insert: </p>

insert: <p>

  insert: </p>

insert: <p>

insert: <b> 2.6 No relationship insert: </b> insert: </p>

insert: <p>

In cases where the current holder of Legacy Internet Resources cannot be contacted, does not reply to contact from the RIPE NCC or rate less than that applicable for a corresponding PI resource. delete: </p> delete: <p> In the case that the holder of a legacy Internet resource opts to engage via a sponsoring LIR and wishes to avail of additional services as defined above, assessment of the billing category of the sponsoring LIR should take account of the legacy resource using a score no greater than that applicable for a corresponding PI resource. delete: </p> delete: <p> Legacy Internet Resource Holders that choose to become RIPE NCC Members shall be charged fees, and enjoy services, in accordance with their RIPE NCC Membership agreement. delete: </p> delete: <p>   delete: </p> delete: <h3> 6.0   Revisions and Extensions to this Policy delete: </h3> delete: <p> delete: <b> 6.1   RIPE NCC may not act in "policy-free zone" delete: </b> delete: </p> delete: <p> The RIPE NCC can develop activities and services for the Internet Community or the RIPE NCC Members without this activity or service being defined in a policy. The management of resources however is a task entrusted to the RIPE NCC by the Internet community. The Memorandum of Understanding with ICANN [5] and specifically the Criteria for Establishment of New Regional Internet Registries [6] state that an RIR must have a "bottom-up self-governance structure for setting local policies". delete: </p> delete: <p> The policies as implemented by the RIPE NCC are developed in the bottom-up Policy Development Process [4]. The RIPE NCC has decided to try to make Legacy Resource Holders sign documents that force them to comply with RIPE policies. While unknown,  there is no policy that forbids RIPE NCC formal relationship between the holder and the RIPE NCC. insert: </p>

insert: <p>

In such a case, the RIPE NCC will continue to provide those registry services which are already being provided in respect of the Legacy Internet Resource or Resources involved, and may update the related entries in the RIPE Database from doing this, there is also no policy that states that this time to time to correspond to current actual situation. insert: </p>

insert: <p>

  insert: </p>

insert: <h3>

3.0 Contractual requirements insert: </h3>

insert: <p>

The service agreement covering registration of a legacy Internet resource between the corresponding Resource Holder and either the Sponsoring LIR or the RIPE NCC must be done. RIPE NCC is currently acting in a "policy-free zone" which is following a top-down approach instead of the required bottom-up Policy Development Process. delete: </p> delete: <p>   delete: </p> delete: <p> delete: <b> 6.2   Revised or additional policy required for action not include insert: </p>

insert: <ul>
    insert: <li>
  • identification of each resource covered by present the service agreement; insert: </li>
  • insert: <li>
  • specification of the service or services offered in respect of each resource identified; insert: </li>
  • insert: <li>
  • a statement of the responsibility of the resource holder to maintain accurate data in the registry in respect of each resource identified; insert: </li>
  • insert: <li>
  • acknowledgement that the terms and conditions under which the resources were originally granted are outside the scope of, and unchanged by, the service agreement. insert: </li>
  • insert: </ul>
insert: <p>

  insert: </p>

insert: <h3>

4.0 Services to be offered and provided insert: </h3>

insert: <p>

The RIPE NCC will offer and provide services in respect of a given Legacy Internet Resource corresponding to the relationship established with the holder of that resource. insert: </p>

insert: <p>

In the case of any of the forms of relationship described in sections 2.1, 2.2, or 2.3 above, this policy delete: </b> delete: </p> delete: <p> This document proposes a framework for future policies. As soon shall not exclude any service from being offered and/or provided in respect of a Legacy Internet Resource registered under the terms of the corresponding direct or indirect contractual agreement relationship with the RIPE NCC. insert: </p>

insert: <p>

In the case of any of the forms of relationship described in sections 2.1, 2.2, 2.3, or 2.4 above, the RIPE NCC shall offer Registry Services as there defined in section 1.1 above in respect of each Legacy Internet Resource involved and as requested by the corresponding Resource Holder. insert: </p>

insert: <p>

In case the situation corresponds to section 2.5 above, the RIPE NCC shall maintain each Registry Service already provided in respect of any corresponding Legacy Internet Resource. insert: </p>

insert: <p>

  insert: </p>

insert: <h3>

5.0 Arbitration in case of conflict insert: </h3>

insert: <p>

In case of conflicts between Legacy Internet Resource Holders and the RIPE NCC about services offered by the RIPE NCC, the RIPE NCC Conflict Arbitration Procedure is consensus within the RIPE community on this framework any future policy development must be done within the bounds of this framework. applied. Conflicts about who the holder is are explicitly out of scope.

 

delete: <p> delete: <b> 6.3   Revision by normal RIPE PDP process delete: </b> delete: </p> delete: <p> As for any RIPE policy this framework is also subject to revision by the RIPE Policy Development Process [5]. However, such future revisions must never restrict the rights of Legacy Resource Holders to their legacy resources. delete: </p> delete: <p>   delete: </p>

7.0 insert: <a name="refs"> insert: </a> 6.0 References

[1] delete: <a class="external-link" href="http://www.bbc.com/news/technology-12859585"> Microsoft spends $7.5m on net addresses delete: </a> delete: </p> delete: <p> [2] ripe-019, RIPE Network Coordination Centre Center (RIPE NCC) insert: </a> insert: </p>

insert: <p>

[2] insert: <a class="external-link" href="ftp://ftp.ietf.org/rfc/rfc2050.txt"> RFC 2050, Internet Registry IP Allocation Guidelines

[3] ripe-508, The RIPE Registry

[4] delete: <a class="external-link" href="http://www.ripe.net/ripe/docs/pdp"> Policy Development Process in RIPE delete: </a> delete: </p> delete: <p> [5] delete: <a class="external-link" href="http://aso.icann.org/documents/memorandum-of-understanding/"> ICANN Address Supporting Organization (ASO) MoU delete: </a> delete: </p> delete: <p> [6] ICP-2: ICP-2, Criteria for For Establishment of New Regional Internet Registries

 

insert: <b> insert: </b> Rationale

delete: <p> delete: <b> a. insert: <ul>
    insert: <li>
  • insert: <b> Arguments supporting the proposal delete: </p> delete: <p> Since RIPE 63 (Vienna, Oct-Nov 2011), the RIPE NCC has been approaching insert: <br />
    insert: <p>

    New policy covering provision of services to legacy resource holders and offering them the opportunity to have the data held by the NCC in relation to their is needed because the scope of existing RIPE policies extends only to Internet resources distributed through the RIPE NCC.  Such new policy will support the RIPE NCC in addressing what RFC 2050 describes as the "primary function" of a Regional Internet Registry and will give legacy Internet resource holdings updated to ensure accuracy of the records, on terms opportunistically imposed by the NCC.  There was holders clarity as yet no RIPE policy in place to support this initiative.  Furthermore, the NCC began the activity without first engaging in consultation with the affected resource holders.  Consequently, the activity was perceived by many of those affected to the services they may expect. insert: </p>

    insert: <p>

    Extensions to the RIPE NCC service model are proposed because of the need for a "public registry" (rather than a members-only registry) identified in RFC 2050. insert: </p>

    insert: <p>

    [and as inappropriate and leading to a “destruction of trust”. delete: </p> delete: <p> This policy proposal is made in an attempt to recover the unfortunate situation which has arisen and  in the hope that it will help prevent such a situation arising again. delete: </p> delete: <p> Although IPv4 addressing resources were not originally intended to be object of any kind of trade, practice showed otherwise during the last years [1]. The implicit acceptance of trade practices over IPv4 addresses sets the background for any organisation to consider their legacy Internet resources as an asset, which can be potentially traded. delete: </p> delete: <p> delete: <br /> delete: <b> b. Arguments opposing the proposal delete: </b> delete: </p> delete: <p> As may be received during Discussion Phase. the discussion phase]

     

    insert: </li>
  • insert: <li>
  • insert: <b> Arguments opposing the proposal insert: </b> insert: <br />
    insert: <p>

    Extensions to the RIPE NCC service model are proposed. insert: <br />
    [and as may be received during discussion phase] insert: </p>

    insert: </li>
  • insert: </ul>
Get Involved

The RIPE NCC Services Working Group discusses the tools and services provided by the RIPE NCC, and conducts an ongoing evaluation of the RIPE NCC Activity Plan. The WG does not replace RIPE NCC Membership Meetings, and the RIPE NCC Budget and fee structures are beyond the scope of this WG. This mailing list was preceded by “impt-dev” which was a forum for the development of tools specifically for LIRs and is publicly archived on the RIPE NCC website. To post a message to the list, send an email to ncc-services-wg@ripe.net. 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.