INTERNET DRAFT Kaj Tesink
Robert H. Fox
Telcordia Technologies
December 31, 2004
A Uniform Resource Name (URN) Namespace for the CLEI Code
<draft-tesink-urn-clei-00.txt>
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of RFC 3668.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This document may not be modified, and derivative works of it may not
be created, except to publish it as an RFC and to translate it into
languages other than English.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 1]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
Abstract
This document describes a Uniform Resource Name (URN) namespace
[RFC3406] that is managed by Telcordia Technologies, Inc., as the
maintenance agent for ANSI T1.213 [T1.213], for the assignment of the
CLEI Code, for usage within messages standardized by ANSI. The CLEI
code is a globally unique, ten-character alphanumeric intelligent
code assigned by Telcordia Technologies at the request of equipment
suppliers. The CLEI code identifies communications equipment by
specifying product type and features. 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).
Table of Contents
1 Introduction .............................................. 3
2 Specification Template .................................... 3
3 Examples .................................................. 5
4 Namespace and Community Considerations .................... 5
5 Security Considerations ................................... 6
6 IANA Considerations ....................................... 6
7 Intellectual Property ..................................... 6
8 Acknowledgments ........................................... 6
9 Normative References ...................................... 7
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 2]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
1. Introduction
Many circuit cards used in the global telecommunications network have
a CLEI Code assigned and have a bar code or two-dimensional symbol on
a label affixed to the front of that circuit card. Service providers
utilize the CLEI Code to:
o Track inventory, both working and spare
o Logistics (movement of circuit cards, along with the serial
number)
o Provision equipment
o Maintain asset records (accounting information)
The goal of the CLEI namespace is to ensure the stability and
uniqueness of the names of various (specific) items that are used
within the messages exchanged between equipment used in the global
telecommunications network.
The assigned maintenance agent for the CLEI Code, Telcordia
Technologies, is responsible for assigning certain equipment and
other identifiers (e.g., location, manufacturer/supplier) for the
telecommunications industry. The code assignment process identifies
the structure and intelligence of the CLEI Code to identify the
circuit card's form, fit, functions, and features. Equipment may
exist in multiple physical locations with the exact same form, fit,
functions, and features and will have the same CLEI Code if their
Product ID is the same.
2. Specification Template
Namespace ID:
"CLEI"
Registration Information:
Version 1
Date: 2004-12-31
Declared registrant of the namespace:
Telcordia Technologies, Inc.
Customer Support Center
8 Corporate Place
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 3]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
Piscataway, NJ 08854
U.S.A.
+1.732.699.5577
http://www.commonlanguage.com
Declaration of syntactic structures:
The structure of the Namespace Specific String is a flat space of
10 characters as defined in [T1.213][T1.213a].
Relevant ancillary Documentation:
[T1.213] and [T1.213a].
Identifier uniqueness considerations:
Identifiers are assigned by Telcordia URN registration that
guarantees Uniqueness for items with different form, fit,
functions, and features. This is simply achieved by keeping track
of already assigned names and comparing all new proposed names to
the database ones. If the name already exists a new one is
created per the rules of the process. See [T1.213][T1.213a] for
assignment examples.
Identifiers persistence considerations:
The process defined by ANSI and the CLEI maintenance agent ensure
the binding between the name and its resource is permanent, and
that names are not reassigned.
Process of identifiers assignment:
A CLEI Code is an intelligent code that consists of 10
alphanumeric characters with 4 data elements. The first data
element is considered the basic code with the first 2 characters
indicating the technology or equipment type with the third and
fourth characters denoting the functional sub-category. The
second data element represents the features and its three
characters denote functional capabilities or changes. The third
data element has one character and denotes a reference to
manufacturer, system ID, specification or drawing. The fourth data
element consists of two characters and contains complementary
data. These two characters provide a means of differentiating or
providing uniqueness between the eight character CLEI Codes by
identifying the manufacturing vintage of the product. Names are
assigned via procedures defined in [GR485].
Process for identifier resolution:
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 4]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
Telcordia URNs are resolved via Telcordia resolvers run under
Telcordia responsibility. For further information see
www.commonlanguage.com.
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.
Conformance with URN syntax:
No special consideration.
Validation mechanism:
None specified.
Scope:
Global.
3. Examples
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
4. Namespace and Community Considerations
CLEI codes have historically been used in a variety of communications
equipment (see examples above and [213a]). There are circumstances
where entities with CLEI codes need to be managed or exposed in a
larger context, such as the general Internet. In these cases, the use
of the CLEI URN namespace will provide general interoperability
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 5]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
benefits to the Internet at large, as well as to specific internets.
5. Security Considerations
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general.
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.
6. IANA Considerations
The IANA has registered formal URN namespace ????, to Telcordia
within the IANA registry of URN NIDs.
7. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
8. Acknowledgments
The contributions of the Entity MIB Working Group members are
gratefully acknowledged. Special thanks go to Mike Heard, Juergen
Schoenwaelder, Dave Perkins and Dan Romascanu.
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 6]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
9. Normative References
[RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom,
"Uniform Resource Name (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, October 2002.
[T1.213] ATIS T1.213-2001, Coded Identification of Equipment Entities
in the North American Telecommunications System for
Information Exchange, 2001, www.ansi.org
[T1.213a] ATIS T1.213a, Supplement to T1.213-2001, Coded
Identification of Equipment Entities in the North American
Telecommunications System for Information Exchange, to
correct the representation of the Basic Code in Figure B.1,
2001, www.ansi.org
[GR485] GR-485-CORE, COMMON LANGUAGE Equipment Codes (CLEI Codes),
Generic Requirements for Processes And Guidelines, Issue 5,
Telcordia Technologies, April 2004.
Authors' addresses
Kaj Tesink
One Telcordia Drive
Piscataway, NJ 08854
USA
Phone: +1 732 699-6068
EMail: kaj@research.telcordia.com
Robert H. Fox
3545 S.Ocean Blvd, #417
Palm Beach, FL 33480-5715
USA
Phone: +1 732 699-8968
EMail: rfox@telcordia.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 7]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 8]
Internet Draft <draft-tesink-urn-clei-00.txt> 12/31/2004
************************************************************
* NOTES TO RFC Editor (to be removed prior to publication) *
* *
* Please replace "????" in the IANA Considerations section *
* with an IANA-assigned URN NID. *
* *
************************************************************
Expires 06/30/2005 URN Namespace for the CLEI Code [Page 9]