Re: New draft: "New Values of the 'status:' attribute for inet6num Objects"

Dear Leo and "Team",
The new draft is available from our web site at:
<http://www.ripe.net/ripe/draft-documents/new-value-status.html>
Looks good!
We would welcome comments on this new draft until Thursday, 1 August 2002. All comments and suggestions should be sent to <lir-wg@ripe.net>.
Procedural question: How are we going to modify existing objects to conform to this proposal? Right now the template query returns: bash-2.05a$ wripe -t inet6num [ ... ] inet6num: [mandatory] [single] [primary/look-up key] [ ... ] status: [generated] [single] [ ] [ ... ] and it seems to be "optional" for the (new) ALLOCATED-BY-RIR case: bash-2.05a$ wripe -r 2001:0628::/35 [ ... ] inet6num: 2001:0628::/35 netname: AT-ACONET-19990920 descr: ACOnet Sub-TLA block country: AT admin-c: WW144 tech-c: WW144 tech-c: WK42 tech-c: CP8-RIPE notify: Domain-Admin@UniVie.ac.at mnt-by: RIPE-NCC-HM-MNT mnt-lower: ACONET-LIR-MNT changed: hostmaster@ripe.net 19990920 changed: hostmaster@ripe.net 20011019 source: RIPE Is this going to change? E.g. to: status: [mandatory] [single] [ ] The wording used in the draft seems to indicate [optional] [single] [ ]. I think some clarification would be helpful. Thanks, cheers, Wilfried. _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber@CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Wilfried, On Fri, Jul 26, 2002 at 11:39:44AM +0200, Wilfried Woeber, UniVie/ACOnet wrote: Re: Re: New draft: "New Values of the 'status:' attribute for inet6num Objects" [...]
How are we going to modify existing objects to conform to this proposal? Right now the template query returns:
bash-2.05a$ wripe -t inet6num [ ... ] inet6num: [mandatory] [single] [primary/look-up key] [ ... ] status: [generated] [single] [ ] [ ... ]
and it seems to be "optional" for the (new) ALLOCATED-BY-RIR case:
[...]
Is this going to change? E.g. to:
status: [mandatory] [single] [ ]
The wording used in the draft seems to indicate [optional] [single] [ ]. I think some clarification would be helpful.
The status attribute will be mandatory. The template and verbose information on whois.ripe.net will be updated to make this clear. The RIPE NCC will use ASSIGNED status inet6nums to determine the HD ratio of an allocation when a request is made for an additional allocation. We intend to update all inet6num objects maintianed by our maintainer on the day the new functionality is implemented. Best regards, -- leo vegoda RIPE NCC, Registration Services Assistant Manager

leo vegoda <leo@ripe.net> writes:
We intend to update all inet6num objects maintianed by our maintainer on the day the new functionality is implemented.
I would suggest to update all objects: - /32 and /35 with "status: SUBTLA" to ALLOCATED-BY-RIR - /48 to ASSIGNED - everything else to ALLOCATED-BY-LIR This way there's a consistent state any we don't need to deal with legacy attribute values. This would also ensure that all objects have a status attribute, thus eliminating the exception (no status attribute) which occured during database software migration. Robert
participants (3)
-
leo vegoda
-
Robert Kiessling
-
Wilfried Woeber, UniVie/ACOnet