This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

Updating inet6num objects with a legacy status attribute

Previous message (by thread): Some updates were not processed today
Next message (by thread): Phase 4 of the MAIL-FROM deprecation

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

leo vegoda leo at ripe.net
Tue Aug 6 16:28:03 CEST 2002

Dear Colleagues,

The RIPE Database server, whois.ripe.net, has been updated to
allow the new status attributes specified in the document:
"New Values of the 'status:' Attribute for inet6num Objects"

   <http://www.ripe.net/docs/new-value-status.html>

The status values of all inet6num objects maintained by the RIPE
NCC have been updated as appropriate.

We would be grateful if everyone maintaining inet6num objects
would update them to use the new status attribute values.

The RIPE NCC will use the "ASSIGNED" status value to determine
the HD ratio when it receives a request for an additional IPv6
allocation. A request form for additional IPv6 allocations
will be published in the near future.

Best regards,

--
leo vegoda
RIPE NCC
Registration Services

Previous message (by thread): Some updates were not processed today
Next message (by thread): Phase 4 of the MAIL-FROM deprecation

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]