RE: On the issue of name assignment for identifiers

["Michelle S. Cotton" <cotton@icann.org>]

Harald, Bob, or Bert,

Can you assist me updating the RSVP registry so that
we include the (source standard) where appropriate?

Thanks,

Michelle

-----Original Message-----
From: iesg-admin@ietf.org [mailto:iesg-admin@ietf.org]On Behalf Of
Harald Tveit Alvestrand
Sent: Tuesday, February 18, 2003 2:13 AM
To: braden@isi.edu
Cc: iesg@ietf.org
Subject: On the issue of name assignment for identifiers


Bob,

the IESG has discussed the idea you mentioned on Jan 27 that one should 
allocate identifiers for RSVP values (or other values) in such a way that 
the formal identifier includes the name of the source standards 
organization, such as using ITU_CALL_OPS rather than CALL_OPS for an RSVP 
Class Number.

The IESG thinks that including semantics-irrelevant stuff in identifiers is 
not a slope we want to start down - after all, many identifiers have very 
many classifications that some people could want to include as part of an 
identifier, so starting here could lead us into places we would not want to 
go.

Adding informal comments in the identifier registry saying who the 
sponsoring organization is in addition to where the identifier's semantics 
is documented, such as saying, for example,

  228  CALL_OPS (ASON, ITU-T G.8080) 
[RFC-lin-ccamp-gmpls-ason-rsvpte-04.txt]

is, however, an idea that we think is good, and that we wish to recommend 
to the IANA if such an identification is easy for IANA to make.

               Harald Alvestrand for the IESG.