Re: [apnic-talk] Status field for inet6num objects
To clarify, the values that APNIC would prefer to use are:
ALLOCATED PORTABLE ALLOCATED NON-PORTABLE ASSIGNED PORTABLE ASSIGNED NON-PORTABLE
As I mentioned before, these values would be consistent with those in IPv4 (which take effect in August when the migration to version 3 of the RIPE database is complete).
Comments?
I would be in favour of this clarity in the field regarding PORTABLE and NON_PORTABLE. However, the distinction between "ALLOCATED" and "ASSIGNED" is perhaps a bit subtle. regards, Geoff
At 06:00 AM 6/12/2002, Geoff Huston wrote:
However, the distinction between "ALLOCATED" and "ASSIGNED" is perhaps a bit subtle.
When these attributes were created, those particular words were in deemed both descriptive and clear. Maybe the language concerned has shifted underneath in the meantime ;-). As a native speaker of one of its dialects, would you make a suggestion for improvement? Daniel
On Wed, 2002-06-12 at 07:11, Daniel Karrenberg wrote:
At 06:00 AM 6/12/2002, Geoff Huston wrote:
However, the distinction between "ALLOCATED" and "ASSIGNED" is perhaps a bit subtle.
When these attributes were created, those particular words were in deemed both descriptive and clear. Maybe the language concerned has shifted underneath in the meantime ;-). As a native speaker of one of its dialects, would you make a suggestion for improvement?
Well actually as a native speaker of (another) of its dialects, I've never considered the distinction of ALLOCATED and ASSIGNED to be other than subtle. I'd much prefer DELEGATED and ASSIGNED or some such. This may be a matter of taste however. Nigel
"LEASED"
"LEASED" has has interesting legal ramifications in some jurisdictions. In the ARIN region, council has advised against using that term. -- --bill
"LEASED" has has interesting legal ramifications in some jurisdictions. In the ARIN region, council has advised against using that term.
<delurk> It also has technical connotations - DHCP address leases at least - which may not be appropriate in this context. </delurk> Sam Wilson Network Services Division Computing Services, The University of Edinburgh Edinburgh, Scotland, UK
participants (6)
-
Bill Manning -
Daniel Karrenberg -
Geoff Huston -
Nigel Titley -
Randy Bush -
Sam.Wilson＠ed.ac.uk