[db-wg] Draft: "status:" re-evaluation

All,

We recently proposed changes to the "status:" attribute values in the
RIPE Database:

http://www.ripe.net/ripe/draft-documents/status-attributes.html

We have received input from APNIC on the subject.  They proposed a
simpler layout, and we think their suggestion makes sense.  However,
we would like to go forward with a slightly modified version that
incorporates the "organisation" object we are working on.

In the meantime, we do not want to delay the implementation of the
Sub-Allocation policy.  For that reason we'd like to have an interim
status attribute value for that.

Proposal:

Add "SUB-ALLOCATED PA" to the allowed "status:" values.

"SUB-ALLOCATED PA" inetnum object may have an "ALLOCATED PA" or an
"LIR-PARTITIONED PA" less specific inetnum object.

A range of IP's can only have a single "SUB-ALLOCATED PA" in it.  That
is, you cannot sub-allocate twice.

--
Shane Kerr
RIPE NCC