Fwd: Re: CLEI Code URN draft
Kaj Tesink <[email protected]> Mon, 13 Dec 2004 17:27:46 -0500
| Newsgroups | gmane.ietf.entmib |
|---|---|
| Message-ID | <[email protected]> |
>Date: Mon, 13 Dec 2004 13:55:57 -0500 >To: [email protected] >From: Kaj Tesink <[email protected]> >Subject: Re: [Entmib] CLEI Code URN draft >Cc: [email protected] > >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 >>[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 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/