Re: [Entmib] entPhysicalUris object wrap-up

Kaj Tesink <> Thu, 09 December 2004 17:25 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id MAA12344 for <>; Thu, 9 Dec 2004 12:25:23 -0500 (EST)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1CcRgx-0003w6-7X; Thu, 09 Dec 2004 12:02:59 -0500
Received: from ([] by with esmtp (Exim 4.32) id 1CcRct-0001jV-EV for; Thu, 09 Dec 2004 11:58:47 -0500
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id LAA10177 for <>; Thu, 9 Dec 2004 11:58:45 -0500 (EST)
Received: from ([]) by with esmtp (Exim 4.33) id 1CcRjr-0001Kl-BJ for; Thu, 09 Dec 2004 12:06:02 -0500
Received: from (shannon []) by (8.12.9/8.12.9) with ESMTP id iB9Gw1cu006887; Thu, 9 Dec 2004 11:58:01 -0500 (EST)
Received: from ( []) by (8.9.3/8.9.3) with ESMTP id LAA01967; Thu, 9 Dec 2004 11:58:00 -0500 (EST)
Message-Id: <>
X-Sender: kaj@
X-Mailer: QUALCOMM Windows Eudora Version
Date: Thu, 09 Dec 2004 11:57:54 -0500
To: Margaret Wasserman <>, Andy Bierman <>,
From: Kaj Tesink <>
Subject: Re: [Entmib] entPhysicalUris object wrap-up
In-Reply-To: <p0620073ebdde00b935ad@[]>
References: <> <> <p0620073ebdde00b935ad@[]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

At 08:23 AM 12/9/2004, Margaret Wasserman wrote:

>Hi All,
>>At 06:27 PM 12/8/2004, David T. Perkins wrote:
>>>4) This issue has been discussed many times. As was pointed out
>>>    by Kaj in an earlier message, the approach choosen was the
>>>    best solution and was acceptable to all on the WG mailing
>>>    list. I don't believe that it is fair to undo what was
>>>    hammered out over a long period of time where:
>>>    a) it was demonstrated that use of an
>>>       "alternative identification" scheme was needed
>>>       and provided value at little cost.
>>>    b) the scheme was neutral
>>>    c) the scheme provided support for multiple competing
>>>       alternative identifications (limited only by the size
>>>       of the object)
>>>    d) the cost to support a "non implementation" was next
>>>       to nothing
>>I missed all this on the mailing list.
>>I'll let the WG Chair decide, and I'll wait
>>on any edits.
>Kaj's document was never a WG document and, IMO, the Entity MIB WG did not 
>make any official decisions about these objects before we decided to add 
>them to the Entity MIB.  I know that a few people used the Entity MIB 
>mailing list to discuss Kaj's personal submission, and I thought that was 
>fine.  But, I didn't track the discussion closely enough to have a mental 
>record of it, and no official consensus calls were made about it.
>Personally, I agree with Andy that it is a bit lame to have an 
>undiscriminated, unformatted, loosely specified string in the middle of 
>this MIB.   How are applications supposed to know that this 
>contains?  Would it be possible to compare these strings?  Use them as 
>URLs?  Or do anything with them besides just display them on a screen?
>I am not actually religious about this, though.  So, if that's what the WG 
>thinks is the best way to represent this object, so be it.

fair enough, so let me recall again how we got here:
1. the original proposal was for some simple (i thought :-)
    object additions to be added to the entmib itself.
2. support for the objects was demonstrated over time,
    but there were 2 issues:
      a) status of the entmib (trying for Draft)
      b) the CLEI object representation
3. (2a) was solved by coming up with a separate
      supplemental MIB, a procedural move.
4. the supplemental MIB had to be a personal
      submission due to the procedural issue of wg charter.
5. later, the need for a supplemental MIB was removed
      since entmib stays at Proposed. thus,
      removing the procedural issues, and
      we are back to the original objects.
6. (2b) went thru an interesting discussion on concerns
      on how best to represent T1.213 format. this
      resulted eventually IMHO in an elegant proposal
      by Juergen and Dave using the URI representation.
      note that the object's nature is Identification; one
      advantage also pointed out by Juergen is that the URI
      approach allows identification not only of CLEIs
      but of other things as well, avoiding the need to
      rework the entmib in the future on this aspect.
7. to support (6) we needed a URN request for CLEI name space.
      this request has been posted using appropriate format
      and 3406 process.
8. irrespective of (6) and (7), the use and application of
      CLEIs themselves are perfectly clear; see T1.213 for
      details, and years of use.

so, based on (1)-(8) i think Dave's observations above
are reasonable.
(i'd not suse in Dave's item (c) the word 'competing';
rather it accommodates identifiers for different applications,
but i assume that that was meant).

the string in the Uri object, at least for the CLEI
application is well formatted and defined. IANA registries  and
are there to help sort things out, no?


>Entmib mailing list


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


Entmib mailing list