Re: Entity MIB Publication Schedule

Andy,

As per below, a way to resolve this could be:

* refer to the Official IANA Registry of URI Schemes
    http://www.iana.org/assignments/uri-schemes
    and the Official IANA Registry of URN Namespaces
    http://www.iana.org/assignments/urn-namespaces
    for current URI/URN assignments

* include a formal URI/URN RFC as normative; a candidate
    could be:
    [RFC2396] Uniform Resource Identifiers (URI): Generic Syntax. T.
      Berners-Lee, R. Fielding, L. Masinter. August 1998. (Format:
      TXT=83639 bytes) (Updates RFC1808, RFC1738) (Updated by RFC2732)
      (Status: DRAFT STANDARD)

* include the CLEI URN as informative:
    [URNCLEI] A Uniform Resource Name (URN) Namespace for the CLEI Code,
     Kaj Tesink, Robert H. Fox, Work in progress, December 31, 2004

kaj


At 01:25 PM 1/4/2005, Kaj Tesink wrote:
>At 12:44 PM 1/4/2005, Juergen Schoenwaelder wrote:
>>On Tue, Jan 04, 2005 at 08:47:15AM -0800, Andy Bierman wrote:
>>
>> > Does 2737bis need a normative reference to the CLEI URN I-D?
>> > I think so, if it's mentioned inside an OBJECT-TYPE macro.
>>
>>Probably depends on the details of the wording. If the CLEI URNs
>>are used as usage examples while the precise format is expressed
>>in terms of general URI formats, one could argue that a suitable
>>URI RFC would be normative while the specific CLEI URNs are
>>informative examples. If we make the ENTITY-MIB depend on the
>>CLEI URN I-D, we open another can of worms and delays.
>
>
>Since the CLEI is just an example of the use of that object
>I'd suggest that the ENTITY-MIB can not depend on it,
>and therefore it should not be normative, no?
>
>kaj
>
>
>
>
>
>>/js
>>
>>--
>>Juergen Schoenwaelder               International University Bremen
>><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany
>>
>>_______________________________________________
>>Entmib mailing list
>>[email protected]
>>https://www1.ietf.org/mailman/listinfo/entmib
>
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>Kaj Tesink
>Telcordia Technologies. Inc.
>One Telcordia drive
>Piscataway, NJ 08854
>Email: [email protected]
>Tel: (732) 699-6068
>Fax: (732) 336-2336
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: [email protected]
Tel: (732) 699-6068
Fax: (732) 336-2336

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/