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
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
|
<pre>Network Working Group B. Rajagopalan
Request for Comments: 3476 Tellium, Inc.
Category: Informational March 2003
<span class="h1">Documentation of IANA Assignments for Label Distribution Protocol</span>
<span class="h1">(LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation</span>
<span class="h1">Protocol-Traffic Engineering (RSVP-TE) Extensions</span>
for Optical UNI Signaling
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 (2003). All Rights Reserved.
Abstract
The Optical Interworking Forum (OIF) has defined extensions to the
Label Distribution Protocol (LDP) and the Resource ReSerVation
Protocol (RSVP) for optical User Network Interface (UNI) signaling.
These extensions consist of a set of new data objects and error
codes. This document describes these extensions.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The OIF UNI signaling specification is described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>]. This
specification utilizes IETF protocol standards as well as IETF work
in progress. Specifically, the following IETF specifications are
used:
o Label distribution protocol (LDP) [<a href="#ref-6" title=""LDP Specification"">6</a>]
o Resource reservation protocol (RSVP) [<a href="#ref-5" title=""RSVP Functional Specification"">5</a>]
o GMPLS signaling and GMPLS extensions for SONET/SDH [<a href="#ref-4" title=""GMPLS Extensions for SONET and SDH Control"">4</a>]
o GMPLS RSVP-TE and CR-LDP extensions [<a href="#ref-2" title=""Generalized Multi-Protocol Label Switching (MPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">2</a>, <a href="#ref-3" title=""Generalized Multi- Protocol Label Switching (MPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions"">3</a>]
The aim of the OIF UNI specification is the maximal re-use of IETF
protocol definitions. A few extensions to IETF protocols, however,
have been defined to serve UNI-specific needs. These extensions are
described in this document.
<span class="grey">Rajagopalan Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. LDP Extensions for UNI Signaling</span>
The LDP extensions for UNI signaling consist of new TLVs that capture
UNI-specific parameters and new UNI-specific status codes. The new
TLVs are Source ID (3 TLVs), Destination ID (3 TLVs), Egress Label,
Local Connection ID, Diversity, Contract ID, and UNI Service Level
[<a href="#ref-8" title="The Optical Internetworking Forum">8</a>]. These are described below. The new status codes are assigned
from the private use space of LDP codes, as described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>]. The
UNI specification [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>] also defines two new LDP messages, Status
Enquiry and Status Response. These messages have been obsoleted and
hence no code points are requested in this document for them.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Source ID TLVs</span>
Three TLVs have been defined to encode the Source ID. The content and
usage of these TLVs are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a> IPv4 Source ID</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Source ID Type (0x0960) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a> IPv6 Source ID</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Source ID Type (0x0961) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">Rajagopalan Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h4"><a class="selflink" id="section-2.1.3" href="#section-2.1.3">2.1.3</a> NSAP Source ID</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Source ID Type (0x0962) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Destination ID TLVs</span>
Three TLVs have been defined to encode the Destination ID. The
content and usage of these TLVs are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a> IPv4 Destination ID</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Dest ID Type (0x0963) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a> IPv6 Destination ID</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Dest ID Type (0x0964) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">Rajagopalan Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a> NSAP Destination ID</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Dest ID Type (0x0965) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Egress Label TLV</span>
The Egress Label TLV is encoded as:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Egress Label (0x966) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The content and usage of this TLV are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Local Connection ID TLV</span>
The Local Connection ID TLV is encoded as:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Local Conn. ID (0x967) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The content and usage of this TLV are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="grey">Rajagopalan Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a> Diversity TLV</span>
The Diversity TLV is encoded as:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Diversity (0x968) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The content and usage of this TLV are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a> Contract ID TLV</span>
The Contract ID TLV is encoded as:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Contract ID (0x969) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The content and usage of this TLV are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a> UNI Service Level TLV</span>
The UNI Service Level TLV is encoded as:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Service Level (0x970) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The content and usage of this TLV are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="grey">Rajagopalan Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. RSVP Extensions for UNI Signaling</span>
A single new object class, called "Generalized_UNI" is defined. In
addition, extension to the RSVP session object and new UNI-specific
error codes are defined. These are described below.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Generalized_UNI Object</span>
The GENERALIZED_UNI object has the following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length (>8) | CNum(229) | C-Type (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// (Subobjects) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subobjects:
The contents of a GENERALIZED_UNI object are a series of variable-
length data items. The common format of the sub-objects is shown
below:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Type | Sub-Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Value //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following sub-objects are defined. The contents of these sub-
objects are described in [<a href="#ref-8" title="The Optical Internetworking Forum">8</a>]:
- Source Transport Network Assigned (TNA) Address sub-object:
Type = 1. The following sub-types are defined:
Ipv4 (Sub-type = 1);
Ipv6 (Sub-type = 2);
NSAP (Sub-type = 3).
- Destination TNA Address sub-object: Type = 2;
The following sub-types are defined:
Ipv4 (Sub-type = 1);
Ipv6 (Sub-type = 2);
NSAP (Sub-type = 3).
<span class="grey">Rajagopalan Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
- Diversity sub-object: Type = 3, Sub-type = 1.
- Egress label sub-object: Type = 4, Sub-type = 1.
- Service level sub-object: Type = 5, Sub-type = 1.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> UNI_Ipv4_Session Object</span>
This object [<a href="#ref-7" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">7</a>] has the following format:
UNI_IPv4_SESSION object: Class = 1, C-Type = 11
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length (16) | Class-Num(1) |C-Type (11) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MUST be zero | Tunnel ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extended IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The C-Type value (11) will distinguish UNI-related RSVP Sessions
from other RSVP sessions. The usage of this object is described in
[<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Error Codes</span>
UNI-specific errors fall under the "Routing Problem" (error code =
24) [<a href="#ref-7" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">7</a>] and "Policy Control Failure" (error code = 2) [<a href="#ref-5" title=""RSVP Functional Specification"">5</a>] errors, and
they require the assignment of sub-codes. The following is the list
of errors and proposed assignments of sub-codes:
- Routing Problem: Diversity not available (Error code = 24, sub-
code = 100)
- Routing Problem: Service level not available (Error code = 24,
sub-code = 101)
- Routing problem: Invalid/Unknown connection ID (Error code = 24,
sub-code = 102)
- Policy control failure: Unauthorized sender (Error code = 2, sub-
code = 100)
- Policy control failure: Unauthorized receiver (Error code = 2,
sub-code = 101)
<span class="grey">Rajagopalan Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
The OIF UNI 1.0 specification defines new objects and error codes
under LDP and RSVP. The majority of these extensions require code
point assignments via IETF consensus action. These are summarized
below.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> LDP Messages, TLVs and Status Codes</span>
TLV types 0x0960 - 0x0970 as described in Sections <a href="#section-2.1">2.1</a> - <a href="#section-2.7">2.7</a> above.
UNI-specific status codes have been allocated out of the Private Use
space, i.e., 0x3Fxxxxxx. These do not require IANA administration.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> RSVP Object Class and Error Codes</span>
Generalized_UNI object class (<a href="#section-3.1">Section 3.1</a>), Class Number 229, C-Type
1. Further sub-objects are defined, with Type numbers 1-5 and
various Sub-Type numbers, as described in <a href="#section-3.1">Section 3.1</a>. The code
points for the Generalized_UNI object and the associated sub-objects
require IANA administration.
UNI_Ipv4_Session Object (Class-Num = 1, C-Type = 11), as described in
<a href="#section-3.2">Section 3.2</a>.
UNI-specific errors fall under the Routing Problem and Policy Control
Failure errors (error codes 24 and 2). Sub-codes under error code 24
are 100, 101 and 102, as described in <a href="#section-3.3">Section 3.3</a>. Sub-codes under
error code 2 are 100 and 101, as described in <a href="#section-3.3">Section 3.3</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Security considerations related to RSVP, RSVP-TE and LDP are
described in <a href="#section-2.8">Section 2.8</a>, <a href="#section-6">Section 6</a> and <a href="#section-5">Section 5</a> of RFCs 2205 [<a href="#ref-5" title=""RSVP Functional Specification"">5</a>],
3209 [9] and 3036 [<a href="#ref-6" title=""LDP Specification"">6</a>], respectively. Security considerations
pertaining to UNI signaling using the extensions described in this
document and how these relate to the security aspects of RSVP, RSVP-
TE and LDP are described in <a href="#section-13.4">Section 13.4</a> of the UNI specification
[<a href="#ref-8" title="The Optical Internetworking Forum">8</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
[<a id="ref-1">1</a>] Berger, L., Editor, "Generalized Multi-Protocol Label Switching
(MPLS) Signaling Functional Description", <a href="./rfc3471">RFC 3471</a>, January 2003.
[<a id="ref-2">2</a>] Berger, L., Editor, "Generalized Multi-Protocol Label Switching
(MPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", <a href="./rfc3473">RFC 3473</a>, January 2003.
<span class="grey">Rajagopalan Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
[<a id="ref-3">3</a>] Ashwood-Smith, P. and L. Berger, Editors, "Generalized Multi-
Protocol Label Switching (MPLS) Signaling Constraint-based Routed
Label Distribution Protocol (CR-LDP) Extensions", <a href="./rfc3472">RFC 3472</a>,
January 2003.
[<a id="ref-4">4</a>] E. Mannie, et al., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22GMPLS+Extensions+for+SONET+and+SDH+Control%22'>"GMPLS Extensions for SONET and SDH Control"</a>,
Work in Progress.
[<a id="ref-5">5</a>] Braden, R., Editor, Zhang, L., Berson, S., Herzog, S. and S.
Jamin, "RSVP Functional Specification", <a href="./rfc2205">RFC 2205</a>, September 1997.
[<a id="ref-6">6</a>] Andersson, L., Doolan, P., Feldman, N., Fredette, A. and B.
Thomas, "LDP Specification", <a href="./rfc3036">RFC 3036</a>, January 2001.
[<a id="ref-7">7</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V. and G.
Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", <a href="./rfc3209">RFC 3209</a>,
December 2001.
[<a id="ref-8">8</a>] UNI 1.0 Signaling Specification, The Optical Internetworking
Forum, <a href="http://www.oiforum.com/public/UNI_1.0_ia.html">http://www.oiforum.com/public/UNI_1.0_ia.html</a>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Intellectual Property</span>
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 <a href="./rfc2028">RFC 2028</a>.
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.
<span class="grey">Rajagopalan Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span>
Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
Ocean Port, NJ 07757
Phone: +1-732-923-4237
EMail: braja@tellium.com
<span class="grey">Rajagopalan Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3476">RFC 3476</a> LDP & RSVP Extensions for Optical UNI Signaling March 2003</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Rajagopalan Informational [Page 11]
</pre>
|
