IETF Logo Mail Archive

Re: [Entmib] Entity MIB Publication Schedule

Kaj Tesink <kaj@research.telcordia.com> Wed, 05 January 2005 19:00 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00932 for <entmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 14:00:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmGLw-0004xc-Ia; Wed, 05 Jan 2005 13:57:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmGJZ-0004YM-HM for entmib@megatron.ietf.org; Wed, 05 Jan 2005 13:55:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00637 for <entmib@ietf.org>; Wed, 5 Jan 2005 13:55:23 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmGW3-0002TC-9v for entmib@ietf.org; Wed, 05 Jan 2005 14:08:28 -0500
Received: from shannon.research.telcordia.com (shannon-83.research.telcordia.com [128.96.83.11]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id j05IsQ5u025679; Wed, 5 Jan 2005 13:54:26 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (KAJ-2.cc.telcordia.com [128.96.208.56]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA13720; Wed, 5 Jan 2005 13:54:25 -0500 (EST)
Message-Id: <6.1.2.0.2.20050105133434.041c3388@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 05 Jan 2005 13:54:50 -0500
To: Andy Bierman <abierman@cisco.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
In-Reply-To: <6.1.2.0.2.20050104132350.01dc6ec0@128.96.81.11>
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net> <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net> <4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com> <20050104174401.GA2834@james> <6.1.2.0.2.20050104132350.01dc6ec0@128.96.81.11>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: entmib@ietf.org, j.schoenwaelder@iu-bremen.de
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
Sender: entmib-bounces@ietf.org
Errors-To: entmib-bounces@ietf.org

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
>>Entmib@ietf.org
>>https://www1.ietf.org/mailman/listinfo/entmib
>
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>Kaj Tesink
>Telcordia Technologies. Inc.
>One Telcordia drive
>Piscataway, NJ 08854
>Email: kaj@research.telcordia.com
>Tel: (732) 699-6068
>Fax: (732) 336-2336
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


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

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: kaj@research.telcordia.com
Tel: (732) 699-6068
Fax: (732) 336-2336

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


_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib

v2.23.0 | Report a Bug | By Email