DRAFT: Value of the “status:” and “assignment-size:” attributes in INET6NUM objects
How to read this draft document:
This document is part of a project to improve the readability of RIPE Policy documents. If approved, it will replace ripe-513. To show you how the new document will differ from the current one, we've provided a summary of the changes made and listed both the current and the proposed text in this document.
Another version of this draft document is available that contains both the current and the proposed text side by side.
Summary of changes:
- Wording throughout the document has been improved
- The policy title has been reworded
- All title sections have been reworded
- The old sections 2.0 and 4.0 have been merged and reworded
- Part of section 3.0 has been merged into the new section 2.0
- The real example has been moved into section 3.0
- Section 2.0 – the text has the structure of definitions, specifics and details on how to use the attributes defined
- Old section 4.0 – removed the first bullet point since this is covered by the last bullet point
Added in new draft document:
- Index of Contents
- Section 4.0 - Attribution
This document describes the "AGGREGATED-BY-LIR" value of the "status:" attribute and the "assignment-size:" attribute in the inet6num object.
2.0 Database Definitions and Functionality
In order to verify efficient use of allocation space, LIRs are required to keep a record of the IPv6 address assignments made to End Users. However, for calculating the efficiency (HD-ratio) there is no need to keep track of individual assignments. The number and size of these assignments is sufficient to calculate the HD-ratio and verify efficiency.
This document introduces the "AGGREGATED-BY-LIR" value of the “status:” attribute for inet6num objects and the attribute “assignment-size:”. Taken together, they accomplish the purpose of creating a standard registration in the database that provides an open and transparent method for verification.
2.0 Database Definitions and Functionality
Value of the "status:" attribute in an inet6num object. It indicates that individual End User assignments are represented by this inet6num object. Multiple End User assignments, each of the same size specified by the “assignment-size:” value, do not need to be registered in the database.
Attribute contained in an inet6num object with the “status:” value “AGGREGATED-BY-LIR”. It indicates the size of the multiple End User assignments contained within the aggregate.
Only the inet6num object may use the value of "AGGREGATED-BY-LIR" for the “status:" attribute and contain the attribute “assignment-size:”.
Only when an inet6num contains a "status:" value of "AGGREGATED-BY-LIR" the "assignment-size:" attribute becomes required.
When creating or updating an inet6num object, the database will check the value of the "status:" attribute according to the following rules:
- The value of the "assignment-size:" attribute must be a longer prefix than the prefix of the object itself.
- The inet6num attribute “status:” may contain the value "AGGREGATED-BY-LIR" only if the one level less specific object contains a "status:" attribute with value
- "ALLOCATED-BY-RIR"; or
- "ALLOCATED-BY-LIR"; or
The usage of “Aggregated-BY-LIR” and “assignment-size:" allows for efficient registration of assignments in cases where there is no need or it is not possible to register the details of individual End Users. An example of this would be the use of dynamic address pools for broadband Internet access. If, for instance, you wish to create a pool of 1000 /56 assignments, you would create an object similar to:
This indicates that the block 2000::/46 is further split into /56 End User assignments. Optionally the "remarks:" and "description:" attributes can be used to further clarify the usage or for instance give hints such as "used for dynamic assignments".
When needed, more specific inet6num objects are allowed to contain the attribute “assignment-size:” with a larger value and have the status “AGGREGATED-BY-LIR”. However, only one level of more specific objects is allowed to aggregate End Users with a different assignment size.
This document is compiled from policies developed by the RIPE community.
The following people actively contributed by making proposals through the RIPE Policy Development Process:
Marco Hogewoning, Remco Van Mook