This policy proposal has been accepted
The new RIPE Document is: ripe-639

Publication of Sponsoring LIR for Legacy Internet Resource Holders

Summary of Proposal

Following the adoption of the RIPE community policy, "Publication of Sponsoring LIR for Independent Number Resources", the RIPE NCC was requested to publish an identifying link between all Provider Independent Internet resource holders and their sponsoring LIR. However, due to an explicit exclusion clause in the "RIPE NCC Services to Legacy Internet Resource Holders" document, the sponsoring LIR publication policy does not apply to legacy resources. This policy proposal applies the "Publication of Sponsoring LIR for Independent Resources" policy to legacy resource holders.

Policy Text

[The following text will update section 3.0 in the RIPE Policy Document “RIPE NCC Services to Legacy Internet Resource Holders”, if the proposal reaches consensus.]

a. Current policy text

3.0 Contractual requirements

[…]

  • a statement of the measures which the RIPE NCC is entitled to take in case the resource holder does not meet their contractual responsibilities.

b. New policy text

3.0 Contractual requirements

[…]

  • a statement of the measures which the RIPE NCC is entitled to take in case the resource holder does not meet their contractual responsibilities.

    Legacy resources are subject to the RIPE community policy, "Publication of Sponsoring LIR for Independent Resources".

Rationale

a. Arguments supporting the proposal

  • This policy proposal brings the RIPE Legacy Internet Resource policy into line with the same RIPE policy that applies to other Provider Independent resources.

b. Arguments opposing the proposal

  • None

 


Impact Analysis

Note: 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 policy might have if the proposal is accepted and implemented.

A. The RIPE NCC’s Understanding of the Policy Proposal

This policy proposal would require the RIPE NCC to publish the identity of the sponsoring LIR for each legacy Internet resource. If it is accepted, the proposal would make publicly visible the link between sponsoring LIRs and the organisations they have contracts with, regarding legacy Internet resources.

B. Impact of Policy on Registry and Addressing System

Address/Internet Number Resource 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.

Fragmentation/Aggregation:

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.

C. Impact of Policy on RIPE NCC Operations/Services

Registration Services:

Based on the contracts and documentation already received from LIRs under related policies, the RIPE NCC will publish the link between legacy Internet resources and their sponsoring LIRs. LIRs are responsible for providing accurate and up-to-date information to the RIPE NCC.

During implementation of this proposal, the RIPE NCC will contact those organisations acting as sponsoring LIRs for legacy Internet resources to notify them of this change and allow them time to react appropriately, by reviewing their sponsoring LIR agreements and terminating any that they do not want to be associated with (or all of them if they wish).

Legacy holders will often be unfamiliar with RIPE Policies and RIPE NCC processes, and so may need additional support from Registration Services for this implementation. This is not expected to cause a significant change in workload.

RIPE Database:

The “sponsoring-org:” attribute for INETNUM and AUT-NUM objects will be added to those resources with the value of “LEGACY”, for which the RIPE NCC holds approved documents with a sponsoring LIR. If the legacy resource holder is in any other relationship with the RIPE NCC (including no relationship), this attribute will not be added to the resource object.

The RIPE NCC will take an initial data list from its internal records and add the new attribute to the appropriate objects based on this list. It will then need to become part of a regular RIPE NCC process to maintain this data in the RIPE Database. This new attribute/value will need to be added, changed or deleted, subject to the conditions stated above, when:

  • A resource moves to another sponsoring LIR
  • A sponsoring LIR notifies the RIPE NCC that a contract has been cancelled, or the sponsoring LIR closes
  • A resource moves from a sponsoring LIR to the infrastructure of an LIR
  • A resource moves from a sponsoring LIR to a non-member service contract with the RIPE NCC
  • Documents are received for a resource where no documents were previously available

Billing/Finance 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.

D. Legal Impact of Policy

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.

E. Implementation

The amount of work needed to technically implement the change is considered to be of a low impact.