1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Network Working Group K. Tesink
Request for Comments: 4152 R. Fox
Category: Informational Telcordia Technologies
August 2005
<span class="h1">A Uniform Resource Name (URN) Namespace</span>
<span class="h1">for the Common Language Equipment Identifier (CLEI) Code</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes a Uniform Resource Name (URN) namespace
(<a href="./rfc3406">RFC 3406</a>) for the assignment of the Common Language Equipment
Identifier (CLEI) code, which is used in messages standardized by
ANSI. The URN namespace is managed by Telcordia Technologies, Inc.,
as the maintenance agent for ANSI T1.213. 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 (the manufacturer's name and the part
number along with its version number).
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Specification Template ..........................................<a href="#page-2">2</a>
<a href="#section-3">3</a>. Examples ........................................................<a href="#page-4">4</a>
<a href="#section-4">4</a>. Namespace and Community Considerations ..........................<a href="#page-4">4</a>
<a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-5">5</a>
<a href="#section-8">8</a>. Normative References ............................................<a href="#page-5">5</a>
<span class="grey">Tesink & Fox Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4152">RFC 4152</a> URN Namespace for the CLEI Code August 2005</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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. Service providers utilize the CLEI
code to:
o Track inventory, both working and spare
o Handle 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 of 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; such equipment will have the same CLEI code
if their product ID is the same.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification Template</span>
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
Piscataway, NJ 08854
<span class="grey">Tesink & Fox Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4152">RFC 4152</a> URN Namespace for the CLEI Code August 2005</span>
U.S.A.
+1.732.699.5577
<a href="http://www.commonlanguage.com">http://www.commonlanguage.com</a>
Declaration of syntactic structures:
The structure of the Namespace Specific String is a flat space of
10 characters, as defined in [<a href="#ref-T1.213" title="2001">T1.213</a>][T1.213a].
Relevant ancillary documentation:
[<a id="ref-T1.213">T1.213</a>] and [<a href="#ref-T1.213a" title="Supplement to T1.213-2001">T1.213a</a>].
Identifier uniqueness considerations:
Identifiers are assigned by Telcordia URN registration that
guarantees uniqueness for items with different form, fit,
functions, and features. This is achieved simply by comparing all
new proposed names to the already assigned names contained in a
database. If the name already exists, a new one is created per
the rules of the process. See [<a href="#ref-T1.213" title="2001">T1.213</a>][T1.213a] for assignment
examples.
Identifiers persistence considerations:
The process defined by ANSI and the CLEI maintenance agent ensure
that 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, and 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 a
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 [<a href="#ref-GR485" title=" Generic Requirements for Processes And Guidelines">GR485</a>].
<span class="grey">Tesink & Fox Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4152">RFC 4152</a> URN Namespace for the CLEI Code August 2005</span>
Process for identifier resolution:
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 [<a href="#ref-T1.213" title="2001">T1.213</a>] and
[<a href="#ref-T1.213a" title="Supplement to T1.213-2001">T1.213a</a>] for further information.
Conformance with URN syntax:
No special consideration.
Validation mechanism:
None specified.
Scope:
Global.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples</span>
The following three examples are based on the examples provided in
[<a href="#ref-T1.213a" title="Supplement to T1.213-2001">T1.213a</a>], 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
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Namespace and Community Considerations</span>
CLEI codes have historically been used in a variety of communications
equipment (see examples above and [<a href="#ref-T1.213a" title="Supplement to T1.213-2001">T1.213a</a>]). There are
circumstances in which entities with CLEI codes need to be managed or
exposed in a larger context, such as the general Internet. In these
<span class="grey">Tesink & Fox Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4152">RFC 4152</a> URN Namespace for the CLEI Code August 2005</span>
cases, the use of the CLEI URN namespace will provide general
interoperability benefits to the Internet at large, as well as to
specific internets.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general.
However, note that attempting to resolve a Telcordia URN through a
resolver other than the one provided by Telcordia is not considered
authoritative.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
The IANA has registered the formal URN namespace CLEI within the IANA
registry of URN NIDs.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
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.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
[<a id="ref-RFC3406">RFC3406</a>] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition
Mechanisms", <a href="./rfc3406">RFC 3406</a>, October 2002.
[<a id="ref-T1.213">T1.213</a>] ATIS T1.213-2001, Coded Identification of Equipment
Entities in the North American Telecommunications System
for Information Exchange, 2001, www.ansi.org.
[<a id="ref-T1.213a">T1.213a</a>] 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.
[<a id="ref-GR485">GR485</a>] GR-485-CORE, COMMON LANGUAGE Equipment Codes (CLEI Codes),
Generic Requirements for Processes And Guidelines, Issue
5, Telcordia Technologies, April 2004.
<span class="grey">Tesink & Fox Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4152">RFC 4152</a> URN Namespace for the CLEI Code August 2005</span>
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
<span class="grey">Tesink & Fox Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4152">RFC 4152</a> URN Namespace for the CLEI Code August 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
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.
Intellectual Property
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
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
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Tesink & Fox Informational [Page 7]
</pre>
|
