Fwd: Re: [Entmib] CLEI Code URN draft

Kaj Tesink <kaj@research.telcordia.com> Mon, 13 December 2004 23:32 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 SAA08591 for <entmib-archive@lists.ietf.org>; Mon, 13 Dec 2004 18:32:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cdzaj-000702-3X; Mon, 13 Dec 2004 18:26:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdzV6-0004rC-Um for entmib@megatron.ietf.org; Mon, 13 Dec 2004 18:21:08 -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 SAA07921 for <entmib@ietf.org>; Mon, 13 Dec 2004 18:21:06 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdzcx-0005tX-BW for entmib@ietf.org; Mon, 13 Dec 2004 18:29:18 -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 iBDNKRwX018616; Mon, 13 Dec 2004 18:20:27 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (KAJ-2.cc.telcordia.com [128.96.171.169]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id SAA00784; Mon, 13 Dec 2004 18:20:27 -0500 (EST)
Message-Id: <6.1.2.0.2.20041213171740.01de1df8@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Mon, 13 Dec 2004 17:27:46 -0500
To: j.schoenwaelder@iu-bremen.de
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Fwd: Re: [Entmib] CLEI Code URN draft
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: entmib@ietf.org
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

>Date: Mon, 13 Dec 2004 13:55:57 -0500
>To: j.schoenwaelder@iu-bremen.de
>From: Kaj Tesink <kaj@research.telcordia.com>
>Subject: Re: [Entmib] CLEI Code URN draft
>Cc: entmib@ietf.org
>
>At 06:47 PM 12/10/2004, Juergen Schoenwaelder wrote:
>>On Thu, Dec 02, 2004 at 06:44:15PM -0500, Kaj Tesink wrote:
>>
>> >    The following three examples are based on the examples provided in
>> >    [T1.213a], and correspond with three different sets of features by
>> >    three different manufacturers (Nortel Networks, Lear and Lucent
>> >    Technologies) producing "D4CE" (a particular D4 channel bank type)
>> >    equipment. The fourth example refers to a SONET power unit convertor
>> >    of Alcatel.
>> >
>> >
>> >       URN:CLEI:D4CE18B7AA
>> >       URN:CLEI:D4CE4248AA
>> >       URN:CLEI:D4CE363PAB
>> >       URN:CLEI:SNPWBBC7AA
>>
>>Are these URNs always uppercase? Does case matter here? Would some or
>>all of the following be illegal?
>>
>>         urn:CLEI:D4CE18B7AA
>>         urn:clei:D4CE18B7AA
>>         urn:clei:d4ce18b7aa
>>         urn:CLEI:D4CE18B7AA
>>         URN:CLEI:d4ce18b7aa
>>         URN:clei:d4ce18b7aa
>>         URN:clei:D4CE18B7AA
>>
>>According to RFC 2141, the leading "urn:" sequence is case-insensitive.
>>What about the rest?
>
>
>thanks, good catch; the rest is up to the particular name space.
>in the CLEI case i believe that CLEI codes are always
>uppercase.
>i'll fix that in the CLEI URN name space request
>together with the format issues that Bert found.

i verified with the CLEI gurus; it turns out that while CLEI codes
are usually represented in uppercase, the codes are actually case-insensitive.

as a result, i suggest that we clarify the lexical equivalence clause
as follows:

Rules for lexical equivalence:

Lexical equivalence of two CLEI URN namespace specific strings
is defined as an exact, case-insensitive string match.  CLEI codes
are assigned in a case-insensitive fashion, so that there will
not be two CLEI codes that differ only in case.
See [T1.213] and [T1.213a] for further information.


kaj









>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