[address-policy-wg] Proposed Implementation Plan for Policy Proposal 2010-06 in the RIPE Database

[Apologies for duplicate emails]

Dear Colleagues,

To prepare for the possible acceptance of RIPE Policy Proposal 2010-06,
"Registration Requirements for IPv6 End User Assignments", the Database
Group at the RIPE NCC proposes the following implementation plan.

We will implement a new attribute ("assignment-size:") in INET6NUM
objects, add some business logic for its use and add a new value
(AGGREGATED-BY-LIR) for the "status:" attribute of an INET6NUM object.

Schema and syntax changes in INET6NUM objects:
- New attribute "assignment-size:"
- Syntax is numeric value > 0
- INET6NUM object will include "assignment-size:" as an optional, single
attribute
- "assignment-size:" will not be an inverse searchable attribute
- New value for the "status:" attribute of an INET6NUM object will be
AGGREGATED-BY-LIR

Business rules:
- "assignment-size:" is optional in INET6NUM objects but required if
"status:" is AGGREGATED-BY-LIR
- The value of "assignment-size:" must be greater than the prefix size
of the INET6NUM object containing the attribute
- Parent status of INET6NUM object with status AGGREGATED-BY-LIR can be:
  ALLOCATED-BY-RIR
  ALLOCATED-BY-LIR
  AGGREGATED-BY-LIR
- If parent status is AGGREGATED-BY-LIR, grandparent status cannot be
AGGREGATED-BY-LIR
- If an object has the status AGGREGATED-BY-LIR, a more specific object
can only have the status AGGREGATED-BY-LIR (subject to the
aforementioned constraints)

We will prepare implementation of this plan during the week commencing
31 January 2011. It will be deployed during the week commencing 7
February 2011 should RIPE Policy Proposal 2010-06 be formally approved.

Regards,

Denis Walker
Business Analyst
RIPE NCC Database Group