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
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
|
<pre>Network Working Group O. Aboul-Magd
Request for Comments: 3475 Nortel Networks
Category: Informational March 2003
<span class="h1">Documentation of IANA assignments for</span>
<span class="h1">Constraint-Based LSP setup using LDP (CR-LDP) Extensions</span>
<span class="h1">for Automatic Switched Optical Network (ASON)</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 (2003). All Rights Reserved.
Abstract
Automatic Switched Optical Network (ASON) is an architecture,
specified by ITU-T Study Group 15, for the introduction of a control
plane for optical networks. The ASON architecture specifies a set of
reference points that defines the relationship between the ASON
architectural entities. Signaling over interfaces defined in those
reference points can make use of protocols that are defined by the
IETF in the context of Generalized Multi-Protocol Label Switching
(GMPLS) work. This document describes Constraint-Based LSP setup
using LDP (CR-LDP) extensions for signaling over the interfaces
defined in the ASON reference points. The purpose of the document is
to request that the IANA assigns code points necessary for the CR-LDP
extensions. The protocol specifications for the use of the CR-LDP
extensions are found in ITU-T documents.
Table of Contents
<a href="#section-1">1</a>. Introduction ................................................. <a href="#page-2">2</a>
<a href="#section-2">2</a>. Overview of CR-LDP Extensions for ASON ....................... <a href="#page-2">2</a>
<a href="#section-3">3</a>. CR-LDP Messages for ASON ..................................... <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a> Call Setup Message ........................................ <a href="#page-4">4</a>
<a href="#section-3.1.2">3.1.2</a> Call Setup Procedure ................................. <a href="#page-5">5</a>
<a href="#section-3.2">3.2</a> The Call Release Message .................................. <a href="#page-5">5</a>
<a href="#section-3.2.1">3.2.1</a> Call Release Procedure ............................... <a href="#page-6">6</a>
<a href="#section-4">4</a>. CR-LDP TLV for ASON .......................................... <a href="#page-6">6</a>
<a href="#section-4.1">4.1</a> Call ID TLV ............................................... <a href="#page-6">6</a>
<a href="#section-4.1.1">4.1.1</a> Call ID Procedure .................................... <a href="#page-8">8</a>
<a href="#section-4.2">4.2</a> Call Capability TLV ....................................... <a href="#page-9">9</a>
<span class="grey">Aboul-Magd Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
<a href="#section-4.3">4.3</a> Crankback TLV ............................................. <a href="#page-9">9</a>
<a href="#section-5">5</a>. Additional Error Codes ....................................... <a href="#page-10">10</a>
<a href="#section-6">6</a>. IANA Consideration ........................................... <a href="#page-11">11</a>
<a href="#section-9">9</a>. Security Considerations ...................................... <a href="#page-11">11</a>
<a href="#section-10">10</a>. Normative References ......................................... <a href="#page-11">11</a>
<a href="#section-11">11</a>. Intellectual Property ........................................ <a href="#page-12">12</a>
<a href="#section-12">12</a>. Author's Address ............................................. <a href="#page-12">12</a>
<a href="#section-13">13</a>. Full Copyright Statement ..................................... <a href="#page-13">13</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Automatic Switched Optical Network (ASON) is an architecture,
specified by ITU-T Study Group 15 (SG15), for the introduction of a
control plane for optical networks. The development and the
standardization of ASON has been done by ITU-T SG15 and is documented
in recommendation G.8080 [<a href="#ref-1" title=" ITU-T recommendation G.8080">1</a>]. The architecture includes a control
plane with a set of reference points between the architectural
components. The ASON signaling that runs over interfaces defined in
those reference points are described in ITU-T recommendation G.7713
[<a href="#ref-2" title="ITU-T recommendation G.7713">2</a>].
Constraint-Based LSP Setup using LDP (CR-LDP) [<a href="#ref-3" title=""Constraint-Based LSP Setup using LDP"">3</a>] is one of the
protocols selected by the ITU for the realization of G.7713 and its
dynamic connection management. The work specific to CR-LDP extensions
for ASON is documented in ITU-T recommendation G.7713.3 [<a href="#ref-8" title="ITU G.7713.3">8</a>].
This document introduces those CR-LDP extensions that are specific to
ASON and requests IANA allocation of code points for these
extensions. The document does not specify how these extensions are
used; that is the subject of the above mentioned ITU-T documents.
This document should be considered in conjunction with <a href="./rfc3036">RFC 3036</a> [<a href="#ref-4" title=""LDP Specifications"">4</a>],
<a href="./rfc3212">RFC 3212</a> [<a href="#ref-3" title=""Constraint-Based LSP Setup using LDP"">3</a>], and CR-LDP extensions for GMPLS [<a href="#ref-5" title=""Generalized Multi- Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions"">5</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview of CR-LDP Extensions for ASON</span>
This document describes ASON specific CR-LDP extensions covering the
following ASON signaling requirements:
- Call and connection control separation
- Support of Soft Permanent Connections (SPC)
- Crankback
- Additional error codes
An important ASON architectural principle is the separation between
the call and the connection controllers as described in G.8080. Call
and connection control separation allows for a call with multiple
connections associated with it. It also allows for a call with no
<span class="grey">Aboul-Magd Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
connections (a temporary situation that might be useful during
recovery).
The separation of the call and the connection controllers could be
achieved using one of two models. The first model is one where the
call set up request is always accompanied by a connection request.
The second model is one in which call set up is done independently
from connection set up. The first model is usually referred to as
logical separation, while the second model is usually referred to as
complete separation. CR-LDP extensions for ASON support the two
separation models.
Two new messages are introduced for call operations (set up and
release). The Call Setup message is used for those cases where
complete separation is required. Otherwise the LDP Label Request
message is used for logical separation.
A connection set up request must indicate the call to which the
connection needs to be associated. A Call ID TLV is introduced to
achieve this goal. The structure of the Call ID allows it to have a
global or an operator scope.
Call release is always achieved using the Call Release message. The
reception of the call Release messages signifies the intention to
remove all connections that are associated to the call. Connection
release is achieved using the CR-LDP label release procedure (using
LDP Label Release and Label Withdraw messages) as defined in [<a href="#ref-4" title=""LDP Specifications"">4</a>].
A Call Capability TLV is also introduced to explicitly indicate the
capability of the requested call.
An Soft Permanent Connection (SPC) service assumes that both source
and destination user-to-network connection segments are provisioned
while the network connection segment is set up via the control plane.
For example when the initial request is received from an external
source, e.g. from a management system, there is an implicit
assumption that the control plane has adequate information to
determine the specific destination (network-to-user) link connection
to use. Support for CR-LDP is provided by the use of the Egress
Label TLV as defined in the OIF UNI 1.0 <a href="#section-11.7.5">section 11.7.5</a> [<a href="#ref-6" title="The Optical Internetworking Forum">6</a>] from the
Optical Internetworking Forum and in <a href="./rfc3476">RFC3476</a> [<a href="#ref-7" title=""Label Distribution Protocol (LDP) and Resource ReserVation Protocol (RSVP) Extensions for Optical UNI Signaling"">7</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. CR-LDP Messages for ASON</span>
This section describes the formats and the procedures of the two
messages that are required for ASON call and connection control
separation. Those messages are the Call Setup messages and the Call
Release message.
<span class="grey">Aboul-Magd Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Call Setup Message</span>
The format of the Call Setup message is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Call Setup (0x0500) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source ID TLV |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dest ID TLV |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Call ID TLV |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Call Capability TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message ID:
Is as defined in <a href="./rfc3036">RFC3036</a> [<a href="#ref-4" title=""LDP Specifications"">4</a>].
Source ID TLV:
Is as defined in UNI 1.0 [<a href="#ref-6" title="The Optical Internetworking Forum">6</a>] and in [<a href="#ref-7" title=""Label Distribution Protocol (LDP) and Resource ReserVation Protocol (RSVP) Extensions for Optical UNI Signaling"">7</a>].
Dest ID TLV:
Is as defined in UNI 1.0 [<a href="#ref-6" title="The Optical Internetworking Forum">6</a>] and in [<a href="#ref-7" title=""Label Distribution Protocol (LDP) and Resource ReserVation Protocol (RSVP) Extensions for Optical UNI Signaling"">7</a>].
Call ID TLV:
Is as defined in <a href="#section-4.1">section 4.1</a> of this document.
Call Capability TLV:
Is as defined in <a href="#section-4.2">section 4.2</a> of this document.
<span class="grey">Aboul-Magd Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a> Call Setup Procedure</span>
The Calling party sends the Call Setup message whenever a new call
needs to be set up with no connection associated with it. The Call
Setup message shall contain all the information required by the
network to process the call. In particular, the Call Setup message
shall include the calling and called party addresses as specified by
the Source ID and Dest ID TLV. The setup message must include Call
ID TLV. The call control entity shall identify the call using the
selected identifier for the lifetime of the call. The Call Setup
message shall progress through the network to the called party. The
called party may accept or reject the incoming call. An LDP
Notification message with the appropriate status code shall be used
to inform the calling party whether the setup is successful. The
call can be rejected by either the network, e.g. for policy reasons,
or by the called party.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> The Call Release Message</span>
This format of the Call Release message is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| Call Release (0x0501) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source ID TLV |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dest ID TLV |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Call ID TLV |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Parameters |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">Aboul-Magd Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a> Call Release Procedure</span>
The Call Release message is sent by any entity of the network to
terminate an already established call. The Call Release message must
include the Call ID TLV of the call to be terminated. Confirmation
of call release is indicated to the request initiator using a
Notification message with the appropriate status code. Reception and
processing of the Call Release message must trigger the release of
all connections that are associated with that call. Connection
release follows the normal CR-LDP procedure using Label Release and
Label Withdraw messages.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. CR-LDP TLVs for ASON</span>
This section describes the operator specific Call ID TLV, the
globally unique Call ID TLV, the Call Capability TLV and the
Crankback TLV introduced for ASON.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Call ID TLV</span>
An established call may be identified by a Call ID. The Call ID is a
globally unique identifier that is set by the source network. The
structure for the Call ID (to guarantee global uniqueness) is to
concatenate a globally unique fixed identifier (composed of country
code, carrier code, unique access point code) with an operator
specific identifier (where the operator specific identifier is
composed of ingress network element (NE) address and a local
Identifier).
Therefore, a generic CALL_ID with global uniqueness includes <global
Id> (composed of <country code> plus <carrier code> plus <unique
access point code>) and <operator specific Id> (composed of <NE
address> plus <local Identifier>). For a CALL_ID that requires only
operator specific uniqueness, only the <operator specific Id> is
needed, while for a CALL_ID that is required to be globally unique
both <global ID> and <operator specific Id> are needed.
The <global Id> shall consist of a three-character International
Segment (the <country code>) and a twelve-character National Segment
(the <carrier code> plus <unique access point code>). These
characters shall be coded according to ITU-T Recommendation T.50.
<span class="grey">Aboul-Magd Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
The format of the operator specific (Op-Sp) CALL_ID TLV:
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|Op-Sp Call ID (0x0831) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NE Address (NEA Sub TLV) |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Identifier (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
NEA Sub TLV:
The Source NE Address is an address of the transport network
element controlled by the source network. Its length can be 4, 6,
16, or 20 bytes long. The NEA Sub TLV is TLV Type 1.
Local Identifier:
A 64-bit identifier that remains constant over the life of the
call.
The format of the globally unique (GU) Call ID TLV:
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|GU Call ID (0x0832) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | IS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NS |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NE Address (NEA Sub TLV) |
~ ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Identifier (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">Aboul-Magd Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
International Segment (IS):
To be coded according to ITU-T recommendation T.50. The
International Segment (IS) field provides a 3 character ISO 3166
Geographic/Political Country Code. The country code is based on
the three-character uppercase alphabetic ISO 3166 Country Code
(e.g., USA, FRA).
National Segment (NS):
The National Segment (NS) field consists of two sub-fields:
- the first subfield contains the ITU Carrier Code
- the second subfield contains a Unique Access Point Code.
The ITU Carrier Code is a code assigned to a network
operator/service provider, maintained by the ITU-T
Telecommunication Service Bureauin association with Recommendation
M.1400. This code consists of 1-6 left-justified alphabetic, or
leading alphabetic followed by numeric, characters (bytes). If
the code is less than 6 characters (bytes), it is padded with a
trailing NULL to fill the subfield.
The Unique Access Point Code is a matter for the organization to
which the country code and ITU carrier code have been assigned,
provided that uniqueness is guaranteed. This code consists of 1-6
characters (bytes), trailing NULL, completing the 12-character
National Segment. If the code is less than 6 characters, it is
padded by a trailing NULL to fill the subfield.
Format of the National Segment
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ITU carrier code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ITU carrie dode (cont) | Unique access point code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unique access point code (continued) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a> Call ID Procedure</span>
The following processing rules are applicable to the CALL ID TLV:
- For initial calls, the calling/originating party call controller
must set the CALL ID values to all-zeros.
<span class="grey">Aboul-Magd Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
- For a new call request, the source networks call controller (SNCC)
sets the appropriate type and value for the CALL ID.
- For an existing call (in case Call ID is non zero) the SNCC
verifies existence of the call.
- Intermediate nodes are not allowed to alter the Call ID TLV set by
the ingress node.
- The destination user/client receiving the request uses the CALL ID
values as a reference to the requested call between the source
user and itself. Subsequent actions related to the call uses the
CALL ID as the reference identifier.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Call Capability TLV</span>
The format of the Call Capability TLV is:
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| Call Capabaility(0x0833) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Call Capability |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Call Capability TLV contains a 4 byte Call Capability field. The
Call Capability Field is used to explicitly indicate the
configuration potentiality of the call.
An example of values of the Call Capability field is:
0x0000 Point to Point call
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Crankback TLV</span>
Crankback requires that when the Label Request message is blocked at
a particular node due to unavailable resources, the node will inform
the initiator of the Label Request message of the location of the
blockage. The initiator can then re-compute new explicit routes that
avoid the area where resource shortage is detected. A new Label
Request message is sent that includes the new route.
The support of crankback in CR-LDP is facilitated by the introduction
of a Crankback TLV. An LDP Notification message is used to inform
the Label Request message initiator of the blocking condition. The
Notification message includes the Crankback TLV that indicates the
location of resource shortage. The location of the resource shortage
is identified using the ER-HOP TLV. The encoding of the Crankback
TLV is:
<span class="grey">Aboul-Magd Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</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| Crankback(0x0834) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ER-HOP TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The ER-HOP TLV is specified in <a href="./rfc3212">rfc3212</a> [<a href="#ref-3" title=""Constraint-Based LSP Setup using LDP"">3</a>], and consists of an n x 4
bytes field, it could e.g. contain an IPv4 or an IPv6 address.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Additional Error Codes</span>
G.7713 includes a number of error codes that are currently not
defined in earlier CR-LDP related RFCs. The list of those error
conditions is given below:
Invalid SNP ID (0x04000009)
Calling Party busy (0x0400000a)
Unavailable SNP ID (0x0400000b)
Invalid SNPP ID (0x0400000c)
Unavailable SNPP ID (0x0400000d)
Failed to create SNC (0x0400000e)
Failed to establish LC (0x040000f)
Invalid Source End-User Name (0x04000010)
Invalid Destination End-User Name (0x04000011)
Invalid CoS (0x04000012)
Unavailable CoS (0x04000013)
Invalid GoS (0x04000014)
Unavailable GoS (0x04000015)
Failed Security Check (0x04000016)
TimeOut (0x04000017)
Invalid Call Name (0x04000018)
Failed to Release SNC (0x04000019)
Failed to Free LC (0x0400001a)
Acronyms used in above error codes:
SNP Sub-network Point
SNPP Sub-network Point Pool
SNC Sub-network Connection
LC Link Connection
CoS Class of Service
GoS Grade of Service
<span class="grey">Aboul-Magd Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Consideration</span>
This document uses the LDP <a href="./rfc3036">RFC 3036</a> [<a href="#ref-4" title=""LDP Specifications"">4</a>] name spaces; see
<a href="http://www.iana.org/assignments/ldp-namespaces">http://www.iana.org/assignments/ldp-namespaces</a>.
Call Setup (0x0500)
Call Release (0x0501)
The assignment for the following TLVs:
Op-Sp Call ID TLV (0x0831)
GU Call ID TLV (0x0832)
Call Capability TLV (0x0833)
Crankback TLV (0x0834)
The assignment for the new error codes as listed in <a href="#section-5">section 5</a> of this
document.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span>
This document does not introduce any new security concerns other than
those defined in <a href="./rfc3036">RFC 3036</a> and <a href="./rfc3212">RFC 3212</a>.
Security aspects (if any) w.r.t. the G.8080 and G.7713 documents need
to be addressed in those documents.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Normative References</span>
[<a id="ref-1">1</a>] Architecture for Automatically Switched Optical Network (ASON),
ITU-T recommendation G.8080, Nov. 2001
[<a id="ref-2">2</a>] Distributed Call and Connection Management (DCM), ITU-T
recommendation G.7713, Dec. 2001
[<a id="ref-3">3</a>] Jamoussi, B., Ed., Andersson, L., Callon, R., Dantu, R., Wu, L.,
Doolan, P., Worster, T., Feldman, N., Fredette, A., Girish, M.,
Gray, E., Heinanen, J., Kilty, T. and A. Malis, "Constraint-Based
LSP Setup using LDP", <a href="./rfc3212">RFC 3212</a>, January 2002.
[<a id="ref-4">4</a>] Andersson, L., Doolan, P., Feldman, N., Fredette, A. and B.
Thomas, "LDP Specifications", <a href="./rfc3036">RFC 3036</a>, January 2001.
[<a id="ref-5">5</a>] Ashwood-Smith, P. and L. Berger, (Editors),"Generalized Multi-
Protocol Label Switching (GMPLS) Signaling Constraint-based
Routed Label Distribution Protocol (CR-LDP) Extensions", <a href="./rfc3472">RFC</a>
<a href="./rfc3472">3472</a>, January 2003.
<span class="grey">Aboul-Magd Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
[<a id="ref-6">6</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>
[<a id="ref-7">7</a>] Rajagopalan, B., "Label Distribution Protocol (LDP) and Resource
ReserVation Protocol (RSVP) Extensions for Optical UNI
Signaling", <a href="./rfc3476">RFC 3476</a>, March 2003.
[<a id="ref-8">8</a>] Distributed Call and Connection Management signalling using GMPLS
CR-LDP, ITU G.7713.3, Januray 2003.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</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="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Author's Addresses</span>
Osama Aboul-Magd
Nortel Networks
P.O. Box 3511, Station C
Ottawa, Ontario, Canada
K1Y 4H7
Phone: 613-599-9104
EMail: osama@nortelnetworks.com
<span class="grey">Aboul-Magd Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc3475">RFC 3475</a> CR-LDP Extensions for ASON March 2003</span>
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</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.
Aboul-Magd Informational [Page 13]
</pre>
|
