You are here: Home > Participate > Policy Development > Policy Proposals > Clarification of Definition for "ASSIGNED PA"

This policy proposal has been accepted and has been implemented
The new RIPE Document is: ripe-720

Clarification of Definition for "ASSIGNED PA"

Summary of proposal

This proposal aims to clarify the wording used in ripe-708 regarding term "ASSIGNED PA" in order to make explicit that the status "ASSIGNED PA" can be also used for assignments to the LIRs infrastructure. 

Current Policy Text:

7.0 Types of Address Space
[…]

ASSIGNED PA: This address space has been assigned to an End User for use with services provided by the issuing LIR. […]

New Policy text:

7.0 Types of Address Space
[…]

ASSIGNED PA: This address space has been assigned to the issuing LIR infrastructure or an End User for use with services provided by the issuing LIR. […] 

Rationale:

a. Arguments Supporting the Proposal

  • Makes the definition of "ASSIGNED PA" less ambiguous.

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. RIPE NCC's Understanding of the Proposed Policy

This proposed policy change will explicitly mention that inetnum objects in the RIPE Database using the "status:" attribute ASSIGNED PA can also be used for LIR infrastructure networks.
While this is common practice especially for long-standing members, the policy text currently refers to End User assignments only. Including LIR infrastructure in the definition of ASSIGNED PA will further clarify when this status must be used and for which networks.

B. Impact of the Policy on the RIPE NCC

No significant impact is expected for the registry and addressing system, the RIPE NCC’s operations, services and legal aspects, as this proposed policy change only clarifies a common praxis.

The RIPE NCC has noticed that new members who may not be familiar with the Internet Registry system often need additional guidance or training to understand the importance of accurately documenting assignments in the RIPE Database.

A clear RIPE policy will help increase the awareness and the understanding of what correct registration entails, therefore supporting the RIPE NCC in explaining such registration requirements.   

C. Implementation

The RIPE NCC estimates that the implementation of this proposal would not have any significant impact.

Additional Comments

The RIPE NCC invites the RIPE Community to continue such efforts to review existing policies to ensure that policy wording matches current practice and is clear.

 

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