status attribute of the inetnum object.

Dear Hank & colleagues,

 Hank Nussbacher <HANK at VM.TAU.AC.IL> writes:
 * On Thu, 09 Jul 1998 21:19:18 +0200 you said:
 * >
 * >Dear Colleagues,
 * >
 * >We intend to make the status attribute of the inetnum
 * >object mandatory on Monday, 13th July next.  This has
 * >been discussed and agreed previously.  However, if you
 * >have software that is _unavoidably_ dependent on this
 * >attribute being optional, please contact us.
 * >
 * >The new version of the inetnum object will be:
 * >
 * >
 * >inetnum:     [mandatory]  [single]     [primary/look-up key]
 * >netname:     [mandatory]  [single]     [look-up key]
 * >descr:       [mandatory]  [multiple]   [ ]
 * >country:     [mandatory]  [multiple]   [ ]
 * >admin-c:     [mandatory]  [multiple]   [inverse key]
 * >tech-c:      [mandatory]  [multiple]   [inverse key]
 * >rev-srv:     [optional]   [multiple]   [ ]
 * >status:      [mandatory]   [single]    [ ]   # mandatory !!!
 * >remarks:     [optional]   [multiple]   [ ]
 * >notify:      [optional]   [multiple]   [inverse key]
 * >mnt-by:      [optional]   [multiple]   [inverse key]
 * >mnt-lower:   [optional]   [multiple]   [ ]
 * >changed:     [mandatory]  [multiple]   [ ]
 * >source:      [mandatory]  [single]     [ ]
 * >
 * >If you have anymore questions, please contact
 * ><ripe-dbm at ripe.net>.
 * >
 * >Regards,
 * >
 * >Ambrose Magee
 * >____________________________
 * >RIPE Database Administration.
 * >
 * >
 * 
 * I think the RIPE documentation needs some updating.
 * 
 * -----------------------------------------------
 * The status field can have one of these values:
 * 
 *      ALLOCATED PA (the most common allocation type for Local IR's)
 * 
 *      ALLOCATED PI (rare for Local IR's)
 * 
 *      ALLOCATED UNSPECIFIED
 * 
 *      ASSIGNED PA
 * 
 *      ASSIGNED PI
 * 
 *      These five values are explained in ripe-140.
 * -------------------------------------------------
 * There is no ripe-140.
 
Yes, you're right that needs to be updated. This quote comes from the database 
document ripe-157 and the document should actually point to ripe-159, we'll 
change that with the next version of ripe-157. We're also changing the output 
of "whois -t inetnum" right now to mention ripe-159.

 * Next.
 * 
 * >From ripe-142:
 * ----------------------------------------------------
 * status:       Specifies  whether the request is provider
 *                    aggregatable  or   provider   independent.
 *                    Should  be filled in with either "ASSIGNED
 *                    PA" or "ASSIGNED PI".
 * ----------------------------------------------------
 * 
 * No mention of "allocated PA" or "allocated PI" or
 * "allocated unspecified".
 
The reason why we don't mention the various "allocated" attributes in ripe-142 
is because only the RIPE NCC makes allocations, registries should only be 
entering "assignments" into the database, and therefore should always put 
"ASSIGNED" in the status attribute on the ripe-141 form which this document 
describes.

In ripe-159, the general policy and procedures document, however, all types of 
allocation and assignment status types are described. (section 3.4.2 for 
assignments and section 4.4 for allocations)

 
 * I think the RIPE documents need to be updated.  There should be
 * a pointer to ripe-127 instead.
 
Good idea! It's added to the to-do list. :-)


Kind regards,


Paula Caslav
Registration Services
Manager
RIPE NCC

 * -Hank
 * 
 *