RIPE NCC Services to Legacy Internet Resource Holders

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.

Policy Text

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

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 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.

1.0 Introduction

Legacy resource holders were granted internet resources before the creation of the RIPE NCC. The RIPE NCC maintains and publishes registry data for resources held by their members and for these legacy resources [1], [2], [3], [4].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 of which include legacy resources.

Historically, legacy resource holdings have been kept outside anyformal relationship between their holders and the RIPE NCC, even incases where such a relationship covers other resources held by thesame holder. To improve the accuracy and trustworthiness of theregistry data the RIPE NCC and a number of legacy resource holdershave indicated that a formal relationship is desirable.

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.

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.

1.1 Definitions

The following definitions apply in this policy and are of particular importance to the understanding of the goals described in this document.

Internet Resource: An IP address block or Autonomous System number.

Legacy Internet Resource: Any Internet Resource granted before the current system ofhierarchical distribution (by allocation or assignment)through the Regional Internet Registries became operational.

Legacy Internet Resource Holder: The holder of a Legacy Internet Resource. Either by receivingthese resources directly or by receiving (part of) Legacy InternetResources from a Legacy Internet Resource Holder.

Registry Services: Services provided by the RIPE NCC in its capacity as a RegionalInternet Registry, including the following and such additionalservices as may be identified from time to time as registry services:

• Maintenance of data relating to Internet Resources by the NCC in their Internet Resource registry;
• Access to these data for update by or on behalf of the respective holder;
• Public availability of registration data;
• Certification of these data; and
• Delegation of reverse DNS to the registered DNS servers.

1.2 Scope

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.

2.0 Relationship between Legacy Internet Resource Holder and RIPE NCC

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 the RIPE NCC. Different methods for establishing such a relationship are described below in sections 2.1, 2.2, 2.3, and 2.4.

If, through no fault of the Legacy Internet Resource Holder involved, it is not 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.

Section 2.6 below applies in all other cases.

2.1 Legacy Internet Resource Holder is already a RIPE NCC member

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.

2.2 Option to become a RIPE NCC member

A Legacy Internet Resource Holder who is 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 then be registered subject to the conditions defined in section 3 below.

2.3 Option to engage via sponsoring LIR

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 Resource Holder and the Sponsoring LIR.

2.4 Option to engage directly with the RIPE NCC

A Legacy Internet Resource Holder whose circumstances match those described in section 2.3 above, but cannot find a Sponsoring LIR with which a mutually satisfactory contract of the kind mentioned in that 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.

2.5 When there are obstacles for 2.1/2.2/2.3/2.4

Due to specific enduring or temporary circumstances, a legacy resource holder 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 offer and provide registry services as 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.

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.

2.6 No relationship

In cases where the current holder of Legacy Internet Resources cannot be contacted, does not reply to contact from the RIPE NCC or is unknown,  there is no formal relationship between the holder and the RIPE NCC.

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 time to time to correspond to current actual situation.

3.0 Contractual requirements

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 include

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

4.0 Services to be offered and provided

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.

In the case of any of the forms of relationship described in sections 2.1, 2.2, or 2.3 above, this policy 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.

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 defined in section 1.1 above in respect of each Legacy Internet Resource involved and as requested by the corresponding Resource Holder.

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.

5.0 Arbitration in case of conflict

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 applied. Conflicts about who the holder is are explicitly out of scope.

6.0 References

[1] ripe-019, RIPE Network Coordination Center (RIPE NCC)

[2] RFC 2050, Internet Registry IP Allocation Guidelines

[3] ripe-508, The RIPE Registry

[4] ICP-2, Criteria For Establishment of New Regional Internet Registries

Rationale

• Arguments supporting the proposal
  

  New policy covering provision of services to legacy resource holders 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 holders clarity as to the services they may expect.

  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.

  [and as may be received during the discussion phase]

• Arguments opposing the proposal
  

  Extensions to the RIPE NCC service model are proposed.
  [and as may be received during discussion phase]