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>Internet Engineering Task Force (IETF) A. Takacs
Request for Comments: 6387 Ericsson
Obsoletes: <a href="./rfc5467">5467</a> L. Berger
Category: Standards Track LabN Consulting, L.L.C.
ISSN: 2070-1721 D. Caviglia
Ericsson
D. Fedyk
Alcatel-Lucent
J. Meuric
France Telecom Orange
September 2011
<span class="h1">GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)</span>
Abstract
This document defines a method for the support of GMPLS asymmetric
bandwidth bidirectional Label Switched Paths (LSPs). The approach
presented is applicable to any switching technology and builds on the
original Resource Reservation Protocol (RSVP) model for the transport
of traffic-related parameters. This document moves the experiment
documented in <a href="./rfc5467">RFC 5467</a> to the standards track and obsoletes <a href="./rfc5467">RFC 5467</a>.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6387">http://www.rfc-editor.org/info/rfc6387</a>.
<span class="grey">Takacs, et. al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Background . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Approach Overview . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.3">1.3</a>. Conventions Used in This Document . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Generalized Asymmetric Bandwidth Bidirectional LSPs . . . . . <a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. UPSTREAM_FLOWSPEC Object . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.1.1">2.1.1</a>. Procedures . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.2">2.2</a>. UPSTREAM_TSPEC Object . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.2.1">2.2.1</a>. Procedures . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.3">2.3</a>. UPSTREAM_ADSPEC Object . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.3.1">2.3.1</a>. Procedures . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3">3</a>. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.1">5.1</a>. UPSTREAM_FLOWSPEC Object . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.2">5.2</a>. UPSTREAM_TSPEC Object . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.3">5.3</a>. UPSTREAM_ADSPEC Object . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
GMPLS [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] introduced explicit support for bidirectional Label
Switched Paths (LSPs). The defined support matched the switching
technologies covered by GMPLS, notably Time Division Multiplexing
(TDM) and lambdas; specifically, it only supported bidirectional LSPs
with symmetric bandwidth allocation. Symmetric bandwidth
requirements are conveyed using the semantics objects defined in
[<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] and [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>].
<span class="grey">Takacs, et. al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
GMPLS asymmetric bandwidth bidirectional LSPs are bidirectional LSPs
that have different bandwidth reservations in each direction.
Support for bidirectional LSPs with asymmetric bandwidth was
previously discussed in the context of Ethernet, notably [<a href="./rfc6060" title=""Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)"">RFC6060</a>]
and [<a href="./rfc6003" title=""Ethernet Traffic Parameters"">RFC6003</a>]. In that context, asymmetric bandwidth support was
considered to be a capability that was unlikely to be deployed, and
hence [<a href="./rfc5467" title=""GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"">RFC5467</a>] was published as Experimental. The MPLS Transport
Profile, MPLS-TP, requires that asymmetric bandwidth bidirectional
LSPs be supported (see [<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>]); therefore, this document is being
published on the Standards Track. This document has no technical
changes from the approach defined in [<a href="./rfc5467" title=""GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"">RFC5467</a>]. This document moves
the experiment documented in [<a href="./rfc5467" title=""GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"">RFC5467</a>] to the standards track and
obsoletes [<a href="./rfc5467" title=""GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"">RFC5467</a>]. This document also removes the Ethernet-
technology-specific alternative approach discussed in the appendix of
[<a href="./rfc5467" title=""GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"">RFC5467</a>] and maintains only one approach that is suitable for use
with any technology.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Background</span>
Bandwidth parameters are transported within RSVP ([<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>],
[<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>], and [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>]) via several objects that are opaque to
RSVP. While opaque to RSVP, these objects support a particular model
for the communication of bandwidth information between an RSVP
session sender (ingress) and receiver (egress). The original model
of communication, defined in [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] and maintained in [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>],
used the SENDER_TSPEC and ADSPEC objects in Path messages and the
FLOWSPEC object in Resv messages. The SENDER_TSPEC object was used
to indicate a sender's data generation capabilities. The FLOWSPEC
object was issued by the receiver and indicated the resources that
should be allocated to the associated data traffic. The ADSPEC
object was used to inform the receiver and intermediate hops of the
actual resources available for the associated data traffic.
With the introduction of bidirectional LSPs in [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>], the model
of communication of bandwidth parameters was implicitly changed. In
the context of [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] bidirectional LSPs, the SENDER_TSPEC object
indicates the desired resources for both upstream and downstream
directions. The FLOWSPEC object is simply confirmation of the
allocated resources. The definition of the ADSPEC object is either
unmodified and only has meaning for downstream traffic, or is
implicitly or explicitly ([<a href="./rfc4606" title=""Generalized Multi- Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control"">RFC4606</a>] and [<a href="./rfc6003" title=""Ethernet Traffic Parameters"">RFC6003</a>]) irrelevant.
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Approach Overview</span>
The approach for supporting asymmetric bandwidth bidirectional LSPs
defined in this document builds on the original RSVP model for the
transport of traffic-related parameters and GMPLS's support for
bidirectional LSPs.
<span class="grey">Takacs, et. al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
The defined approach is generic and can be applied to any switching
technology supported by GMPLS. With this approach, the existing
SENDER_TSPEC, ADSPEC, and FLOWSPEC objects are complemented with the
addition of new UPSTREAM_TSPEC, UPSTREAM_ADSPEC, and
UPSTREAM_FLOWSPEC objects. The existing objects are used in the
original fashion defined in [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] and [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>], and refer only
to traffic associated with the LSP flowing in the downstream
direction. The new objects are used in exactly the same fashion as
the old objects, but refer to the upstream traffic flow Figure 1
shows the bandwidth-related objects used for asymmetric bandwidth
bidirectional LSPs.
|---| Path |---|
| I |------------------->| E |
| n | -SENDER_TSPEC | g |
| g | -ADSPEC | r |
| r | -UPSTREAM_FLOWSPEC | e |
| e | | s |
| s | Resv | s |
| s |<-------------------| |
| | -FLOWSPEC | |
| | -UPSTREAM_TSPEC | |
| | -UPSTREAM_ADSPEC | |
|---| |---|
Figure 1: Generic Asymmetric Bandwidth Bidirectional LSPs
The extensions defined in this document are limited to Point-to-Point
(P2P) LSPs. Support for Point-to-Multipoint (P2MP) bidirectional
LSPs is not currently defined and, as such, not covered in this
document.
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Generalized Asymmetric Bandwidth Bidirectional LSPs</span>
The setup of an asymmetric bandwidth bidirectional LSP is signaled
using the bidirectional procedures defined in [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] together with
the inclusion of the new UPSTREAM_FLOWSPEC, UPSTREAM_TSPEC, and
UPSTREAM_ADSPEC objects.
The new upstream objects carry the same information and are used in
the same fashion as the existing downstream objects; they differ in
that they relate to traffic flowing in the upstream direction while
<span class="grey">Takacs, et. al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
the existing objects relate to traffic flowing in the downstream
direction. The new objects also differ in that they are carried in
messages traveling in the opposite direction.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. UPSTREAM_FLOWSPEC Object</span>
The format of an UPSTREAM_FLOWSPEC object is the same as a FLOWSPEC
object [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>]. This includes the definition of class types and
their formats. The class number of the UPSTREAM_FLOWSPEC object is
120 (of the form 0bbbbbbb).
<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Procedures</span>
The Path message of an asymmetric bandwidth bidirectional LSP MUST
contain an UPSTREAM_FLOWSPEC object and MUST use the bidirectional
LSP formats and procedures defined in [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>]. The C-Type of the
UPSTREAM_FLOWSPEC object MUST match the C-Type of the SENDER_TSPEC
object used in the Path message. The contents of the
UPSTREAM_FLOWSPEC object MUST be constructed using a format and
procedures consistent with those used to construct the FLOWSPEC
object that will be used for the LSP, e.g., [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>] or [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>].
Nodes processing a Path message containing an UPSTREAM_FLOWSPEC
object MUST use the contents of the UPSTREAM_FLOWSPEC object in the
upstream label and the resource allocation procedure defined in
<a href="./rfc3473#section-3.1">Section 3.1 of [RFC3473]</a>. Consistent with [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>], a node that is
unable to allocate a label or internal resources based on the
contents of the UPSTREAM_FLOWSPEC object MUST issue a PathErr message
with a "Routing problem/MPLS label allocation failure" indication.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. UPSTREAM_TSPEC Object</span>
The format of an UPSTREAM_TSPEC object is the same as a SENDER_TSPEC
object, which includes the definition of class types and their
formats. The class number of the UPSTREAM_TSPEC object is 121 (of
the form 0bbbbbbb).
<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Procedures</span>
The UPSTREAM_TSPEC object describes the traffic flow that originates
at the egress. The UPSTREAM_TSPEC object MUST be included in any
Resv message that corresponds to a Path message containing an
UPSTREAM_FLOWSPEC object. The C-Type of the UPSTREAM_TSPEC object
MUST match the C-Type of the corresponding UPSTREAM_FLOWSPEC object.
The contents of the UPSTREAM_TSPEC object MUST be constructed using a
format and procedures consistent with those used to construct the
FLOWSPEC object that will be used for the LSP, e.g., [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>] or
[<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>]. The contents of the UPSTREAM_TSPEC object MAY differ from
<span class="grey">Takacs, et. al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
contents of the UPSTREAM_FLOWSPEC object based on application data
transmission requirements.
When an UPSTREAM_TSPEC object is received by an ingress, the ingress
MAY determine that the original reservation is insufficient to
satisfy the traffic flow. In this case, the ingress MAY tear down
the LSP and send a PathTear message. Alternatively, the ingress MAY
issue a Path message with an updated UPSTREAM_FLOWSPEC object to
modify the resources requested for the upstream traffic flow. This
modification might require the LSP to be re-routed, and in extreme
cases might result in the LSP being torn down when sufficient
resources are not available along the path of the LSP.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. UPSTREAM_ADSPEC Object</span>
The format of an UPSTREAM_ADSPEC object is the same as an ADSPEC
object. This includes the definition of class types and their
formats. The class number of the UPSTREAM_ADSPEC object is 122 (of
the form 0bbbbbbb).
<span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Procedures</span>
The UPSTREAM_ADSPEC object MAY be included in any Resv message that
corresponds to a Path message containing an UPSTREAM_FLOWSPEC object.
The C-Type of the UPSTREAM_TSPEC object MUST be consistent with the
C-Type of the corresponding UPSTREAM_FLOWSPEC object. The contents
of the UPSTREAM_ADSPEC object MUST be constructed using a format and
procedures consistent with those used to construct the ADSPEC object
that will be used for the LSP, e.g., [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>] or [<a href="./rfc6003" title=""Ethernet Traffic Parameters"">RFC6003</a>]. The
UPSTREAM_ADSPEC object is processed using the same procedures as the
ADSPEC object and, as such, MAY be updated or added at transit nodes.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Packet Formats</span>
This section presents the RSVP message-related formats as modified by
this section. This document modifies formats defined in [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>],
[<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>], and [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>]. See [<a href="./rfc5511" title=""Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications"">RFC5511</a>] for the syntax used by RSVP.
Unmodified formats are not listed. Three new objects are defined in
this section:
Object name Applicable RSVP messages
--------------- ------------------------
UPSTREAM_FLOWSPEC Path, PathTear, PathErr, and Notify
(via sender descriptor)
UPSTREAM_TSPEC Resv, ResvConf, ResvTear, ResvErr, and
Notify (via flow descriptor list)
UPSTREAM_ADSPEC Resv, ResvConf, ResvTear, ResvErr, and
Notify (via flow descriptor list)
<span class="grey">Takacs, et. al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
The format of the sender description for bidirectional asymmetric
LSPs is:
<sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC>
[ <ADSPEC> ]
[ <RECORD_ROUTE> ]
[ <SUGGESTED_LABEL> ]
[ <RECOVERY_LABEL> ]
<UPSTREAM_LABEL>
<UPSTREAM_FLOWSPEC>
The format of the flow descriptor list for bidirectional asymmetric
LSPs is:
<flow descriptor list> ::= <FF flow descriptor list>
| <SE flow descriptor>
<FF flow descriptor list> ::= <FLOWSPEC>
<UPSTREAM_TSPEC> [ <UPSTREAM_ADSPEC> ]
<FILTER_SPEC>
<LABEL> [ <RECORD_ROUTE> ]
| <FF flow descriptor list>
<FF flow descriptor>
<FF flow descriptor> ::= [ <FLOWSPEC> ]
[ <UPSTREAM_TSPEC>] [ <UPSTREAM_ADSPEC> ]
<FILTER_SPEC> <LABEL>
[ <RECORD_ROUTE> ]
<SE flow descriptor> ::= <FLOWSPEC>
<UPSTREAM_TSPEC> [ <UPSTREAM_ADSPEC> ]
<SE filter spec list>
<SE filter spec list> is unmodified by this document.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Compatibility</span>
This extension reuses and extends semantics and procedures defined in
[<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>], [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>], and [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] to support bidirectional LSPs
with asymmetric bandwidth. Three new objects are defined to indicate
the use of asymmetric bandwidth. Each of these objects is defined
with class numbers in the form 0bbbbbbb. Per [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>], nodes not
supporting this extension will not recognize the new class numbers
and will respond with an "Unknown Object Class" error. The error
message will propagate to the ingress, which can then take action to
avoid the path with the incompatible node or can simply terminate the
session.
<span class="grey">Takacs, et. al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
The IANA has made the assignments described below in the "Class
Names, Class Numbers, and Class Types" section of the "RSVP
PARAMETERS" registry.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. UPSTREAM_FLOWSPEC Object</span>
The class named UPSTREAM_FLOWSPEC has been assigned in the 0bbbbbbb
range (120) with the following definition:
Class Types or C-types:
Same values as FLOWSPEC object (C-Num 9)
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. UPSTREAM_TSPEC Object</span>
The class named UPSTREAM_TSPEC has been assigned in the 0bbbbbbb
range (121) with the following definition:
Class Types or C-types:
Same values as SENDER_TSPEC object (C-Num 12)
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. UPSTREAM_ADSPEC Object</span>
The class named UPSTREAM_ADSPEC has been assigned in the 0bbbbbbb
range (122) with the following definition:
Class Types or C-types:
Same values as ADSPEC object (C-Num 13)
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
This document introduces new message objects for use in GMPLS
signaling [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] -- specifically the UPSTREAM_TSPEC,
UPSTREAM_ADSPEC, and UPSTREAM_FLOWSPEC objects. These objects
parallel the existing SENDER_TSPEC, ADSPEC, and FLOWSPEC objects but
are used in the opposite direction. As such, any vulnerabilities
that are due to the use of the old objects now apply to messages
flowing in the reverse direction.
From a message standpoint, this document does not introduce any new
signaling messages or change the relationship between LSRs that are
adjacent in the control plane. As such, this document introduces no
additional message- or neighbor-related security considerations.
<span class="grey">Takacs, et. al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
See [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] for relevant security considerations and [<a href="./rfc5920" title=""Security Framework for MPLS and GMPLS Networks"">RFC5920</a>] for
a more general discussion on RSVP-TE security discussions.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC2205">RFC2205</a>] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and
S. Jamin, "Resource ReSerVation Protocol (RSVP) --
Version 1 Functional Specification", <a href="./rfc2205">RFC 2205</a>, September
1997.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2210">RFC2210</a>] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", <a href="./rfc2210">RFC 2210</a>, September 1997.
[<a id="ref-RFC3209">RFC3209</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-RFC3473">RFC3473</a>] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE) Extensions", <a href="./rfc3473">RFC</a>
<a href="./rfc3473">3473</a>, January 2003.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-RFC4606">RFC4606</a>] Mannie, E. and D. Papadimitriou, "Generalized Multi-
Protocol Label Switching (GMPLS) Extensions for
Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control", <a href="./rfc4606">RFC 4606</a>, August 2006.
[<a id="ref-RFC4328">RFC4328</a>] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", <a href="./rfc4328">RFC 4328</a>, January 2006.
[<a id="ref-RFC5511">RFC5511</a>] Farrel, A., "Routing Backus-Naur Form (RBNF): A Syntax
Used to Form Encoding Rules in Various Routing Protocol
Specifications", <a href="./rfc5511">RFC 5511</a>, April 2009.
[<a id="ref-RFC5654">RFC5654</a>] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M.,
Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile", <a href="./rfc5654">RFC 5654</a>, September 2009.
[<a id="ref-RFC5920">RFC5920</a>] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", <a href="./rfc5920">RFC 5920</a>, July 2010.
<span class="grey">Takacs, et. al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
[<a id="ref-RFC5467">RFC5467</a>] Berger, L., Takacs, A., Caviglia, D., Fedyk, D., and J.
Meuric, "GMPLS Asymmetric Bandwidth Bidirectional Label
Switched Paths (LSPs)", <a href="./rfc5467">RFC 5467</a>, March 2009.
[<a id="ref-RFC6003">RFC6003</a>] Papadimitriou, D., "Ethernet Traffic Parameters", <a href="./rfc6003">RFC</a>
<a href="./rfc6003">6003</a>, October 2010.
[<a id="ref-RFC6060">RFC6060</a>] Fedyk, D., Shah, H., Bitar, N., and A. Takacs,
"Generalized Multiprotocol Label Switching (GMPLS)
Control of Ethernet Provider Backbone Traffic Engineering
(PBB-TE)", <a href="./rfc6060">RFC 6060</a>, March 2011.
<span class="grey">Takacs, et. al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6387">RFC 6387</a> Asymmetric Bandwidth Bidirectional LSP September 2011</span>
Authors' Addresses
Attila Takacs
Ericsson
Konyves Kalman krt. 11.
Budapest, 1097
Hungary
EMail: attila.takacs@ericsson.com
Lou Berger
LabN Consulting, L.L.C.
EMail: lberger@labn.net
Diego Caviglia
Ericsson
Via A. Negrone 1/A
Genova-Sestri Ponente,
Italy
Phone: +390106003738
Fax:
EMail: diego.caviglia@ericsson.com
Don Fedyk
Alcatel-Lucent
Groton, MA
USA
EMail: donald.fedyk@alcatel-lucent.com
Julien Meuric
France Telecom Orange
2, avenue Pierre Marzin
Lannion Cedex, 22307
France
EMail: julien.meuric@orange.com
Takacs, et. al. Standards Track [Page 11]
</pre>
|
