A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code
RFC 4152

Note: This ballot was opened for revision 00 and is now closed.

(Ted Hardie) Yes

(Harald Alvestrand) No Objection

Comment (2005-03-03)
No email
send info
Review by John Loughney, Gen-ART.

Defining CLEI is a good idea!
Otherwise, nothing important.

(Margaret Cullen) No Objection

(Scott Hollenbeck) No Objection

Comment (2005-02-14)
No email
send info
The IANA Considerations section should probably point to the template in section 2.

(Russ Housley) No Objection

Comment (2005-03-01)
No email
send info
  The document contains non-ASCII characters.

(David Kessens) No Objection

(Allison Mankin) No Objection

Comment (2005-03-02)
No email
send info
 Besides a non-ascii character, this sentence spells uses the wrong spelling of its  
   There is a one-to-one
   relationship between a CLEI Code and supplier�s Product ID
   (Manufacturer's name, part number along with it's version number).

Regarding the following:

   It is noted however that attempting to resolve a Telcordia URN
   through a resolver other than the one provided by Telcordia is not
   considered authoritative.

The CLEI Code is associated with ANSI standards.  This spec says there are
cases where it might provide "general interoperablity to the Internet at
large" but a kind of standard where the resolver appears proprietary
and undocumentable makes me think we should ask to add ANSI
and Telcordia to the title so it's clearer that IETF is not the visionary here.