You are here: Home > Participate > Policy Development > Policy Proposals > Registration Requirements for IPv6 End User Assignments

You're looking at an older or unpublished version: 1

DRAFT: Value of the "status:" and "assignment-size:" attributes in inet6num objects for sub-assigned PA space


This document describes the new value of the "status:" attribute and the "assignment-size:" of the inet6num object.

1.0 Motivation

For verification of efficient use of allocated space, there is a requirement for LIRs to keep records of IPv6 address assignments made to End Users. However, for calculating the efficiency (HD-ratio) there is no need to keep track of personal data associated with these assignments. The number and size of the assignments is sufficient to calculate the HD-ratio and verify efficiency.

To standardise these registrations and to provide an open and transparent method of verification, this document introduces a new value of the "status:" attribute for inet6num objects (SUB-ASSIGNED PA) and a new attribute called "assignment-size:". This new value allows the creation of inet6num objects indicating them as aggregated End User assignments. The "assignment-size:" attribute is used to indicate the size of the individual End User assignments in this aggregate.

2.0 Database Objects Affected

Only inet6nums object may contain a "status:" value of "SUB-ASSIGNED PA" or attribute called "assignment size:". When the inet6num has a status of "SUB-ASSIGNED PA", the "assignment-size:" attribute is mandatory. In all other cases, the attribute is optional.

3.0 Usage

The <SUB-ASSIGNED PA> feature allows registration of individual End User assignments by means of a less specific aggregate object containing multiple assignments of the same size, which is indicated in the "assignment size:" attribute.

This allows for efficient registration of assignments when there is either neither the need nor the possibility to register details of individual End Users - such as the use of dynamic address pools for broadband Internet access.

When creating a pool for 1000 /56 assignments, the object would be similar to:

inet6num: 2000::/46


assignment-size: 56


This indicates a block of /46 internally further split into /56 End User assignments. Optionally, the "remarks:" and "description:" attributes can be used to further clarify usage or give hints such as "used for dynamic assignments".

4.0 Functionality

When creating or updating an inet6num object, the database will check the value of the "status:" attribute according to the following rules:

  • The inet6num object may contain an attribute called "assignment-size:".
  • The value of the "assignment-size:" attribute must be less than the size of the object's bit mask.
  • A value of "SUB-ASSIGNED PA" is allowed if a one level less specific object contains a "status:" attribute with a value of "ALLOCATED-BY-RIR", "ALLOCATED-BY-LIR" or "ASSIGNED".
  • When an inet6num contains a "status:" value of "SUB-ASSIGNED PA" the "assignment-size attribute:" becomes mandatory.
Get Involved

The IPv6 Working Group is for anyone with an interest in the next generation Internet Protocol. The activities of the WG include education and outreach, sharing deployment experiences and discussing and fixing operational issues. 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.