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]/
[apnic-talk] Status field for inet6num objects
- Previous message (by thread): [hostmaster-staff] Re: [apnic-talk] Status field for inet6num objects
- Next message (by thread): [apnic-talk] Status field for inet6num objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kiessling
Robert.Kiessling at de.easynet.net
Wed Jun 12 03:30:54 CEST 2002
Anne Lord <anne at apnic.net> writes: > In addition, I seem to remember (as in ripe-127?) the main reason for > introducing the "status" field, was to assist in the identification of > address space as PA or PI. There is no PI in IPv6. This can't be said often enough. > With the values suggested: > > RIR-allocated > LIR-allocated > Assigned > > this does not seem possible anymore. Right. It is not necessary. > To clarify, the values that APNIC would prefer to use are: > > ALLOCATED PORTABLE > ALLOCATED NON-PORTABLE > ASSIGNED PORTABLE > ASSIGNED NON-PORTABLE This does not take into account that there are no portable addresses, and that there is an additional level "LIR-allocated" which IPv4 does not have. I like the original proposal of not having the status generated automatically, and giving them a meaning clearly reflected in the name. Robert
- Previous message (by thread): [hostmaster-staff] Re: [apnic-talk] Status field for inet6num objects
- Next message (by thread): [apnic-talk] Status field for inet6num objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]