| 1 |
<pre>Internet Engineering Task Force (IETF) F. Zhang, Ed. |
| 2 |
Request for Comments: 7551 Huawei |
| 3 |
Category: Standards Track R. Jing |
| 4 |
ISSN: 2070-1721 China Telecom |
| 5 |
R. Gandhi, Ed. |
| 6 |
Cisco Systems |
| 7 |
May 2015 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">RSVP-TE Extensions</span> |
| 11 |
<span class="h1">for Associated Bidirectional Label Switched Paths (LSPs)</span> |
| 12 |
|
| 13 |
Abstract |
| 14 |
|
| 15 |
This document describes Resource Reservation Protocol (RSVP) |
| 16 |
extensions to bind two point-to-point unidirectional Label Switched |
| 17 |
Paths (LSPs) into an associated bidirectional LSP. The association |
| 18 |
is achieved by defining new Association Types for use in ASSOCIATION |
| 19 |
and in Extended ASSOCIATION Objects. One of these types enables |
| 20 |
independent provisioning of the associated bidirectional LSPs on both |
| 21 |
sides, while the other enables single-sided provisioning. The |
| 22 |
REVERSE_LSP Object is also defined to enable a single endpoint to |
| 23 |
trigger creation of the reverse LSP and to specify parameters of the |
| 24 |
reverse LSP in the single-sided provisioning case. |
| 25 |
|
| 26 |
Status of This Memo |
| 27 |
|
| 28 |
This is an Internet Standards Track document. |
| 29 |
|
| 30 |
This document is a product of the Internet Engineering Task Force |
| 31 |
(IETF). It represents the consensus of the IETF community. It has |
| 32 |
received public review and has been approved for publication by the |
| 33 |
Internet Engineering Steering Group (IESG). Further information on |
| 34 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 35 |
|
| 36 |
Information about the current status of this document, any errata, |
| 37 |
and how to provide feedback on it may be obtained at |
| 38 |
<a href="http://www.rfc-editor.org/info/rfc7551">http://www.rfc-editor.org/info/rfc7551</a>. |
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Zhang, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2015 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 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 |
<span class="grey">Zhang, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-5">5</a> |
| 117 |
<a href="#section-2.1">2.1</a>. Key Word Definitions .......................................<a href="#page-5">5</a> |
| 118 |
<a href="#section-2.2">2.2</a>. Reverse Unidirectional LSPs ................................<a href="#page-5">5</a> |
| 119 |
<a href="#section-2.3">2.3</a>. Message Formats ............................................<a href="#page-5">5</a> |
| 120 |
<a href="#section-3">3</a>. Overview ........................................................<a href="#page-6">6</a> |
| 121 |
<a href="#section-3.1">3.1</a>. Provisioning Model Overview ................................<a href="#page-6">6</a> |
| 122 |
<a href="#section-3.1.1">3.1.1</a>. Single-Sided Provisioning ...........................<a href="#page-6">6</a> |
| 123 |
<a href="#section-3.1.2">3.1.2</a>. Double-Sided Provisioning ...........................<a href="#page-6">6</a> |
| 124 |
<a href="#section-3.2">3.2</a>. Association Signaling Overview .............................<a href="#page-6">6</a> |
| 125 |
<a href="#section-3.2.1">3.2.1</a>. Single-Sided Provisioning ...........................<a href="#page-7">7</a> |
| 126 |
<a href="#section-3.2.2">3.2.2</a>. Double-Sided Provisioning ...........................<a href="#page-7">7</a> |
| 127 |
<a href="#section-3.3">3.3</a>. Asymmetric Bandwidth Signaling Overview ....................<a href="#page-8">8</a> |
| 128 |
<a href="#section-3.3.1">3.3.1</a>. Single-Sided Provisioning ...........................<a href="#page-8">8</a> |
| 129 |
<a href="#section-3.3.2">3.3.2</a>. Double-Sided Provisioning ...........................<a href="#page-8">8</a> |
| 130 |
<a href="#section-3.4">3.4</a>. Recovery LSP Overview ......................................<a href="#page-8">8</a> |
| 131 |
<a href="#section-4">4</a>. Message and Object Definitions ..................................<a href="#page-9">9</a> |
| 132 |
<a href="#section-4.1">4.1</a>. RSVP Message Formats .......................................<a href="#page-9">9</a> |
| 133 |
<a href="#section-4.2">4.2</a>. ASSOCIATION Object .........................................<a href="#page-9">9</a> |
| 134 |
<a href="#section-4.3">4.3</a>. Extended ASSOCIATION Object ...............................<a href="#page-10">10</a> |
| 135 |
<a href="#section-4.4">4.4</a>. REVERSE_LSP Object Definition .............................<a href="#page-11">11</a> |
| 136 |
<a href="#section-4.4.1">4.4.1</a>. REVERSE_LSP Object Format ..........................<a href="#page-11">11</a> |
| 137 |
<a href="#section-4.4.2">4.4.2</a>. REVERSE_LSP Subobjects .............................<a href="#page-11">11</a> |
| 138 |
<a href="#section-5">5</a>. Processing Rules ...............................................<a href="#page-12">12</a> |
| 139 |
<a href="#section-5.1">5.1</a>. Rules for ASSOCIATION Object ..............................<a href="#page-12">12</a> |
| 140 |
<a href="#section-5.1.1">5.1.1</a>. Compatibility for ASSOCIATION Object ...............<a href="#page-14">14</a> |
| 141 |
<a href="#section-5.2">5.2</a>. Rules for REVERSE_LSP Object ..............................<a href="#page-14">14</a> |
| 142 |
<a href="#section-5.2.1">5.2.1</a>. Compatibility for REVERSE_LSP Object ...............<a href="#page-16">16</a> |
| 143 |
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-16">16</a> |
| 144 |
<a href="#section-6.1">6.1</a>. Association Types .........................................<a href="#page-16">16</a> |
| 145 |
<a href="#section-6.2">6.2</a>. REVERSE_LSP Object ........................................<a href="#page-16">16</a> |
| 146 |
<a href="#section-6.3">6.3</a>. Reverse LSP Failure PathErr Sub-code ......................<a href="#page-17">17</a> |
| 147 |
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-17">17</a> |
| 148 |
<a href="#section-8">8</a>. References .....................................................<a href="#page-18">18</a> |
| 149 |
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-18">18</a> |
| 150 |
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-19">19</a> |
| 151 |
Acknowledgements ..................................................<a href="#page-20">20</a> |
| 152 |
Contributors ......................................................<a href="#page-20">20</a> |
| 153 |
Authors' Addresses ................................................<a href="#page-20">20</a> |
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Zhang, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
The MPLS Transport Profile (MPLS-TP) requirements document [<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>] |
| 172 |
specifies that MPLS-TP MUST support associated bidirectional point- |
| 173 |
to-point Label Switched Paths (LSPs). These requirements are given |
| 174 |
in <a href="#section-2.1">Section 2.1</a> ("General Requirements") of that document and are |
| 175 |
partially rephrased below: |
| 176 |
|
| 177 |
7. MPLS-TP MUST support associated bidirectional point-to-point |
| 178 |
LSPs. |
| 179 |
|
| 180 |
11. The end points of an associated bidirectional LSP MUST be aware |
| 181 |
of the pairing relationship of the forward and reverse LSPs used |
| 182 |
to support the bidirectional service. |
| 183 |
|
| 184 |
12. Nodes on the LSP of an associated bidirectional LSP where both |
| 185 |
the forward and backward directions transit the same node in the |
| 186 |
same (sub)layer as the LSP SHOULD be aware of the pairing |
| 187 |
relationship of the forward and the backward directions of the |
| 188 |
LSP. |
| 189 |
|
| 190 |
50. The MPLS-TP control plane MUST support establishing associated |
| 191 |
bidirectional P2P LSP including configuration of protection |
| 192 |
functions and any associated maintenance functions. |
| 193 |
|
| 194 |
The above requirements are also repeated in [<a href="./rfc6373" title=""MPLS Transport Profile (MPLS-TP) Control Plane Framework"">RFC6373</a>]. |
| 195 |
|
| 196 |
Furthermore, an associated bidirectional LSP is also useful for |
| 197 |
protection-switching for Operations, Administration, and Maintenance |
| 198 |
(OAM) messages that require a return path. |
| 199 |
|
| 200 |
A variety of applications, such as Internet services and the return |
| 201 |
paths of OAM messages, exist and may have different upstream and |
| 202 |
downstream bandwidth requirements. [<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>] specifies an asymmetric |
| 203 |
bandwidth requirement in <a href="#section-2.1">Section 2.1</a> ("General Requirements"), and it |
| 204 |
is repeated below: |
| 205 |
|
| 206 |
14. MPLS-TP MUST support bidirectional LSPs with asymmetric |
| 207 |
bandwidth requirements, i.e., the amount of reserved bandwidth |
| 208 |
differs between the forward and backward directions. |
| 209 |
|
| 210 |
The approach for supporting asymmetric bandwidth co-routed |
| 211 |
bidirectional LSPs is defined in [<a href="./rfc6387" title=""GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"">RFC6387</a>]. |
| 212 |
|
| 213 |
The method of association and the corresponding Resource Reservation |
| 214 |
Protocol (RSVP) ASSOCIATION Object are defined in [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>], |
| 215 |
[<a href="./rfc4873" title=""GMPLS Segment Recovery"">RFC4873</a>], and [<a href="./rfc6689" title=""Usage of the RSVP ASSOCIATION Object"">RFC6689</a>]. In that context, the ASSOCIATION Object is |
| 216 |
used to associate a recovery LSP with the LSP it is protecting. This |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Zhang, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 223 |
|
| 224 |
|
| 225 |
object also has broader applicability as a mechanism to associate |
| 226 |
RSVP states. [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>] defines the Extended ASSOCIATION Objects that |
| 227 |
can be more generally applied for this purpose. This document uses |
| 228 |
the term "(Extended) ASSOCIATION Objects" to refer collectively to |
| 229 |
the ASSOCIATION Objects defined in [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>] and the Extended |
| 230 |
ASSOCIATION Objects defined in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. |
| 231 |
|
| 232 |
This document specifies mechanisms for binding two reverse |
| 233 |
unidirectional LSPs into an associated bidirectional LSP. The |
| 234 |
association is achieved by defining new Association Types for use in |
| 235 |
(Extended) ASSOCIATION Objects. One of these types enables |
| 236 |
independent provisioning of the associated bidirectional LSPs, while |
| 237 |
the other enables single-sided provisioning. The REVERSE_LSP Object |
| 238 |
is also defined to enable a single endpoint to trigger creation of |
| 239 |
the reverse LSP and to specify parameters of the reverse LSP in the |
| 240 |
single-sided provisioning case. For example, the REVERSE_LSP Object |
| 241 |
allow asymmetric upstream and downstream bandwidths for the |
| 242 |
associated bidirectional LSP. |
| 243 |
|
| 244 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span> |
| 245 |
|
| 246 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Key Word Definitions</span> |
| 247 |
|
| 248 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 249 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 250 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 251 |
|
| 252 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Reverse Unidirectional LSPs</span> |
| 253 |
|
| 254 |
Two reverse unidirectional LSPs are setup in the opposite directions |
| 255 |
between a pair of source and destination nodes to form an associated |
| 256 |
bidirectional LSP. A reverse unidirectional LSP originates on the |
| 257 |
same node where the forward unidirectional LSP terminates, and it |
| 258 |
terminates on the same node where the forward unidirectional LSP |
| 259 |
originates. |
| 260 |
|
| 261 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Message Formats</span> |
| 262 |
|
| 263 |
This document uses the Routing Backus-Naur Form (RBNF) to define |
| 264 |
message formats as defined in [<a href="./rfc5511" title=""Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications"">RFC5511</a>]. |
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Zhang, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span> |
| 282 |
|
| 283 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Provisioning Model Overview</span> |
| 284 |
|
| 285 |
This section provides an overview and definition of the models for |
| 286 |
provisioning associated bidirectional LSPs. |
| 287 |
|
| 288 |
The associated bidirectional LSP's forward and reverse unidirectional |
| 289 |
LSPs are established, monitored, and protected independently as |
| 290 |
specified by [<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>]. Configuration information regarding the LSPs |
| 291 |
can be provided at one or both endpoints of the associated |
| 292 |
bidirectional LSP. Depending on the method chosen, there are two |
| 293 |
models of creating an associated bidirectional LSP -- single-sided |
| 294 |
provisioning and double-sided provisioning. |
| 295 |
|
| 296 |
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Single-Sided Provisioning</span> |
| 297 |
|
| 298 |
For the single-sided provisioning, the Traffic Engineering (TE) |
| 299 |
tunnel is configured only on one endpoint. An LSP for this tunnel is |
| 300 |
initiated by the initiating endpoint with the (Extended) ASSOCIATION |
| 301 |
and REVERSE_LSP Objects inserted in the Path message. The other |
| 302 |
endpoint then creates the corresponding reverse TE tunnel and signals |
| 303 |
the reverse LSP in response using information from the REVERSE_LSP |
| 304 |
Object and other objects present in the received Path message. |
| 305 |
|
| 306 |
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Double-Sided Provisioning</span> |
| 307 |
|
| 308 |
For the double-sided provisioning, two unidirectional TE tunnels are |
| 309 |
configured independently, one on each endpoint. The LSPs for the |
| 310 |
tunnels are signaled with (Extended) ASSOCIATION Objects inserted in |
| 311 |
the Path message by both endpoints to indicate that the two LSPs are |
| 312 |
to be associated to form a bidirectional LSP. |
| 313 |
|
| 314 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Association Signaling Overview</span> |
| 315 |
|
| 316 |
This section provides an overview of the association signaling |
| 317 |
methods for the associated bidirectional LSPs. |
| 318 |
|
| 319 |
Three scenarios exist for binding two unidirectional LSPs together to |
| 320 |
form an associated bidirectional LSP. These are: |
| 321 |
|
| 322 |
1) Neither unidirectional LSP exists, and both must be established. |
| 323 |
|
| 324 |
2) Both unidirectional LSPs exist, but the association must be |
| 325 |
established. |
| 326 |
|
| 327 |
3) One LSP exists, but the reverse associated LSP must be |
| 328 |
established. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Zhang, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 335 |
|
| 336 |
|
| 337 |
The following sections describe the applicable provisioning models |
| 338 |
for each of these scenarios. |
| 339 |
|
| 340 |
Path Computation Element (PCE)-based approaches [<a href="./rfc4655" title=""A Path Computation Element (PCE)-Based Architecture"">RFC4655</a>] may be used |
| 341 |
for path computation of an associated bidirectional LSP. However, |
| 342 |
these approaches are outside the scope of this document. |
| 343 |
|
| 344 |
Consider the topology described in Figure 1. LSP1 from node A to B, |
| 345 |
takes the path A,D,B, and LSP2 from node B to A takes the path |
| 346 |
B,D,C,A. These two LSPs, once established and associated, form an |
| 347 |
associated bidirectional LSP between nodes A and B. |
| 348 |
|
| 349 |
LSP1 --> |
| 350 |
A-------D-------B |
| 351 |
\ / <-- LSP2 |
| 352 |
\ / |
| 353 |
\ / |
| 354 |
C |
| 355 |
|
| 356 |
Figure 1: An Example of Associated Bidirectional LSP |
| 357 |
|
| 358 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Single-Sided Provisioning</span> |
| 359 |
|
| 360 |
For the single-sided provisioning model, creation of reverse LSP1 |
| 361 |
shown in Figure 1 is triggered by LSP2, or creation of reverse LSP2 |
| 362 |
is triggered by LSP1. When creation of reverse LSP2 is triggered by |
| 363 |
LSP1, LSP1 is provisioned first (or refreshed, if LSP1 already |
| 364 |
exists) at node A. LSP1 is then signaled with an (Extended) |
| 365 |
ASSOCIATION, and REVERSE_LSP Objects are inserted in the Path |
| 366 |
message. The Association Type indicates single-sided provisioning. |
| 367 |
Upon receiving this Path message for LSP1, node B establishes reverse |
| 368 |
LSP2. The (Extended) ASSOCIATION Object inserted in LSP2's Path |
| 369 |
message is the same as that received in LSP1's Path message. |
| 370 |
|
| 371 |
A similar procedure is used if LSP2 is provisioned first at node B, |
| 372 |
and the creation of reverse LSP1 at node A is triggered by LSP2. In |
| 373 |
both scenarios, the two unidirectional LSPs are bound together to |
| 374 |
form an associated bidirectional LSP based on identical (Extended) |
| 375 |
ASSOCIATION Objects in the two LSPs' Path messages. |
| 376 |
|
| 377 |
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Double-Sided Provisioning</span> |
| 378 |
|
| 379 |
For the double-sided provisioning model, both LSP1 and LSP2 shown in |
| 380 |
Figure 1 are signaled independently with (Extended) ASSOCIATION |
| 381 |
Objects inserted in the Path messages, in which the Association Type |
| 382 |
indicating double-sided provisioning is included. In this case, the |
| 383 |
two unidirectional LSPs are bound together to form an associated |
| 384 |
bidirectional LSP based on identical (Extended) ASSOCIATION Objects |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Zhang, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 391 |
|
| 392 |
|
| 393 |
in the two LSPs' Path messages. In all three scenarios described in |
| 394 |
<a href="#section-3.2">Section 3.2</a>, the LSPs to be selected for the association are |
| 395 |
provisioned by the management action applied at both endpoints. |
| 396 |
|
| 397 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Asymmetric Bandwidth Signaling Overview</span> |
| 398 |
|
| 399 |
This section provides an overview of the methods for signaling |
| 400 |
asymmetric upstream and downstream bandwidths for the associated |
| 401 |
bidirectional LSPs. |
| 402 |
|
| 403 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Single-Sided Provisioning</span> |
| 404 |
|
| 405 |
A new REVERSE_LSP Object for use in the single-sided provisioning |
| 406 |
model is defined in this document, in <a href="#section-4.4">Section 4.4</a>. The REVERSE_LSP |
| 407 |
Object allows the initiating node of the single-sided provisioned LSP |
| 408 |
to trigger creation of the reverse LSP on the remote node. When the |
| 409 |
single-sided provisioning model is used, a SENDER_TSPEC Object can be |
| 410 |
added in the REVERSE_LSP Object as a subobject in the initiating |
| 411 |
LSP's Path message to specify a different bandwidth for the reverse |
| 412 |
LSP. As described in <a href="#section-4.4">Section 4.4</a>, addition of the REVERSE_LSP Object |
| 413 |
also allows the initiating node to control other aspects of the |
| 414 |
reverse LSP (such as its path) by including other objects in a |
| 415 |
REVERSE_LSP Object. |
| 416 |
|
| 417 |
Consider again the topology described in Figure 1, where the creation |
| 418 |
of reverse LSP2 is triggered by LSP1. Node A signals LSP1 with the |
| 419 |
(Extended) ASSOCIATION Object with Association Type indicating |
| 420 |
single-sided provisioning and inserts a SENDER_TSPEC subobject for |
| 421 |
use by LSP2 in the REVERSE_LSP Object in the Path message. Node B |
| 422 |
then establishes the LSP2 in the reverse direction using the |
| 423 |
asymmetric bandwidth thus specified by LSP1 and allows node A to |
| 424 |
control the reverse LSP2. |
| 425 |
|
| 426 |
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Double-Sided Provisioning</span> |
| 427 |
|
| 428 |
When the double-sided provisioning model is used, the two |
| 429 |
unidirectional LSPs are established with separate bandwidths, which |
| 430 |
may or may not be identical. However, these LSPs are associated |
| 431 |
purely based on the identical contents of their (Extended) |
| 432 |
ASSOCIATION Objects. |
| 433 |
|
| 434 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Recovery LSP Overview</span> |
| 435 |
|
| 436 |
Recovery of each unidirectional LSP forming the bidirectional LSP is |
| 437 |
independent [<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>] and is based on the parameters signaled in |
| 438 |
their respective RSVP Path messages. |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Zhang, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 447 |
|
| 448 |
|
| 449 |
Recovery LSP association is based on the identical content of the |
| 450 |
(Extended) ASSOCIATION Objects signaled in their Path messages during |
| 451 |
the initial LSP setup for both single-sided and double-sided |
| 452 |
provisioning. As defined in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>], multiple ASSOCIATION Objects |
| 453 |
may be present in the signaling of a single LSP. |
| 454 |
|
| 455 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Message and Object Definitions</span> |
| 456 |
|
| 457 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. RSVP Message Formats</span> |
| 458 |
|
| 459 |
This section presents the RSVP message-related formats as modified by |
| 460 |
this document. Unmodified RSVP message formats are not listed. |
| 461 |
|
| 462 |
The format of a Path message is as follows: |
| 463 |
|
| 464 |
<Path Message> ::= <Common Header> [ <INTEGRITY> ] |
| 465 |
[ [<MESSAGE_ID_ACK> | <MESSAGE_ID_NACK>] ... ] |
| 466 |
[ <MESSAGE_ID> ] |
| 467 |
<SESSION> <RSVP_HOP> |
| 468 |
<TIME_VALUES> |
| 469 |
[ <EXPLICIT_ROUTE> ] |
| 470 |
<LABEL_REQUEST> |
| 471 |
[ <PROTECTION> ] |
| 472 |
[ <LABEL_SET> ... ] |
| 473 |
[ <SESSION_ATTRIBUTE> ] |
| 474 |
[ <NOTIFY_REQUEST> ... ] |
| 475 |
[ <ADMIN_STATUS> ] |
| 476 |
[ <ASSOCIATION> ... ] |
| 477 |
[ <REVERSE_LSP> ... ] |
| 478 |
[ <POLICY_DATA> ... ] |
| 479 |
<sender descriptor> |
| 480 |
|
| 481 |
The format of the <sender descriptor> is not modified by this |
| 482 |
document. |
| 483 |
|
| 484 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. ASSOCIATION Object</span> |
| 485 |
|
| 486 |
The ASSOCIATION Object is populated using the rules defined below for |
| 487 |
associating two reverse unidirectional LSPs to form an associated |
| 488 |
bidirectional LSP. |
| 489 |
|
| 490 |
Association Types: |
| 491 |
|
| 492 |
In order to bind two reverse unidirectional LSPs to be an |
| 493 |
associated bidirectional LSP, the Association Type MUST be set to |
| 494 |
indicate either single-sided or double-sided LSPs. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Zhang, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 503 |
|
| 504 |
|
| 505 |
The new Association Types are defined as follows: |
| 506 |
|
| 507 |
Value Type |
| 508 |
----- ----- |
| 509 |
3 Double-Sided Associated Bidirectional LSP (D) |
| 510 |
4 Single-Sided Associated Bidirectional LSP (A) |
| 511 |
|
| 512 |
Association ID: |
| 513 |
|
| 514 |
For both single-sided and double-sided provisioning, Association |
| 515 |
ID MUST be set to a value assigned by the node that originates the |
| 516 |
association for the bidirectional LSP. |
| 517 |
|
| 518 |
Association Source: |
| 519 |
|
| 520 |
Association Source MUST be set to an address selected by the node |
| 521 |
that originates the association for the bidirectional LSP. For |
| 522 |
example, this may be a management entity or, in the case of |
| 523 |
single-sided provisioning, an address assigned to the node that |
| 524 |
originates the LSP. |
| 525 |
|
| 526 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Extended ASSOCIATION Object</span> |
| 527 |
|
| 528 |
The Extended ASSOCIATION Object is populated using the rules defined |
| 529 |
below for associating two reverse unidirectional LSPs to form a |
| 530 |
bidirectional LSP. |
| 531 |
|
| 532 |
The Association Type, Association ID, and Association Source MUST be |
| 533 |
set as defined for the ASSOCIATION Object in <a href="#section-4.1">Section 4.1</a>. |
| 534 |
|
| 535 |
Global Association Source: |
| 536 |
|
| 537 |
For both single-sided and double-sided provisioning, Global |
| 538 |
Association Source, when used, MUST be set to the Global_ID |
| 539 |
[<a href="./rfc6370" title=""MPLS Transport Profile (MPLS-TP) Identifiers"">RFC6370</a>] of the node that originates the association for the |
| 540 |
bidirectional LSP. |
| 541 |
|
| 542 |
Extended Association ID: |
| 543 |
|
| 544 |
For both single-sided and double-sided provisioning, Extended |
| 545 |
Association ID, when used, MUST be set to a value selected by the |
| 546 |
node that originates the association for the bidirectional LSP. |
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Zhang, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. REVERSE_LSP Object Definition</span> |
| 562 |
|
| 563 |
<span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a>. REVERSE_LSP Object Format</span> |
| 564 |
|
| 565 |
The REVERSE_LSP Object is carried in the Path message of a forward |
| 566 |
LSP to provide information to be used by the reverse LSP. The object |
| 567 |
also indicates that the LSP is the forward LSP of a single-sided |
| 568 |
associated bidirectional LSP. |
| 569 |
|
| 570 |
The Object has the following format: |
| 571 |
|
| 572 |
Class_Num = 203, C_Type = 1. |
| 573 |
|
| 574 |
0 1 2 3 |
| 575 |
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 |
| 576 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 577 |
| | |
| 578 |
// (Subobjects) // |
| 579 |
| | |
| 580 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 581 |
|
| 582 |
<span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a>. REVERSE_LSP Subobjects</span> |
| 583 |
|
| 584 |
Subobjects are used to override the default contents of a Path |
| 585 |
message of a reverse LSP; see <a href="#section-5.2">Section 5.2</a>. The contents of a |
| 586 |
REVERSE_LSP Object is zero or more variable-length subobjects that |
| 587 |
have the same format as RSVP Objects; see <a href="./rfc2205#section-3.1.2">Section 3.1.2 of [RFC2205]</a>. |
| 588 |
Any object that may be carried in a Path message MAY be carried in |
| 589 |
the REVERSE_LSP Object. Subobject ordering MUST follow any Path |
| 590 |
message Object ordering requirements. |
| 591 |
|
| 592 |
Examples of the Path message Objects that can be carried in the |
| 593 |
REVERSE_LSP Object are (but not limited to): |
| 594 |
|
| 595 |
- SENDER_TSPEC [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] |
| 596 |
- EXPLICIT_ROUTE Object (ERO) [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>] |
| 597 |
- SESSION_ATTRIBUTE Object [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>] |
| 598 |
- ADMIN_STATUS Object [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] |
| 599 |
- LSP_REQUIRED_ATTRIBUTES Object [<a href="./rfc5420" title=""Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)"">RFC5420</a>] |
| 600 |
- PROTECTION Object [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>] |
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Zhang, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Processing Rules</span> |
| 618 |
|
| 619 |
In general, the processing rules for the ASSOCIATION Object are as |
| 620 |
specified in [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>], and those for the Extended ASSOCIATION Object |
| 621 |
are as specified in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. The following sections describe the |
| 622 |
rules for processing (Extended) ASSOCIATION Objects for both double- |
| 623 |
sided and single-sided associated bidirectional LSPs and REVERSE_LSP |
| 624 |
Objects for single-sided associated bidirectional LSPs. |
| 625 |
|
| 626 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Rules for ASSOCIATION Object</span> |
| 627 |
|
| 628 |
This section defines the processing for the association of two |
| 629 |
unidirectional LSPs to form an associated bidirectional LSP. Such |
| 630 |
association is based on the use of an (Extended) ASSOCIATION Object. |
| 631 |
|
| 632 |
The procedures related to the actual identification of associations |
| 633 |
between LSPs based on (Extended) ASSOCIATION Objects are defined in |
| 634 |
[<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>] specifies that in the absence of rules for |
| 635 |
identifying the association that are specific to the Association |
| 636 |
Type, the included (Extended) ASSOCIATION Objects in the LSPs MUST be |
| 637 |
identical in order for an association to exist. This document adds |
| 638 |
no specific rules for the new Association Types defined, and the |
| 639 |
identification of an LSP association therefore proceeds as specified |
| 640 |
in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. |
| 641 |
|
| 642 |
As described in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>], association of LSPs can be upstream or |
| 643 |
downstream initiated, as indicated by (Extended) ASSOCIATION Objects |
| 644 |
in Path or Resv Messages. The association of bidirectional LSPs is |
| 645 |
always upstream initiated; therefore, the Association Types defined |
| 646 |
in this document are only to be interpreted in Path Messages. These |
| 647 |
types SHOULD NOT be used in ASSOCIATION Objects carried in Resv |
| 648 |
messages and SHOULD be ignored if present. |
| 649 |
|
| 650 |
To indicate an associated bidirectional LSP, an ingress node MUST |
| 651 |
insert an (Extended) ASSOCIATION Object into the Path message of the |
| 652 |
unidirectional LSP that is part of the associated bidirectional LSP |
| 653 |
it initiates. If either Global Association Source or Extended |
| 654 |
Association Address is required, then an Extended ASSOCIATION Object |
| 655 |
[<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>] MUST be inserted in the Path message. Otherwise, an |
| 656 |
ASSOCIATION Object MAY be used. (Extended) ASSOCIATION Objects with |
| 657 |
both single-sided and double-sided Association Types MUST NOT be |
| 658 |
added or sent in the same Path message. |
| 659 |
|
| 660 |
The ingress node MUST set the Association Type field in the |
| 661 |
(Extended) ASSOCIATION Object to "Single-Sided Associated |
| 662 |
Bidirectional LSP" when single-sided provisioning is used, and to |
| 663 |
"Double-Sided Associated Bidirectional LSP" when double-sided |
| 664 |
provisioning is used. |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Zhang, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 671 |
|
| 672 |
|
| 673 |
A transit node MAY identify the unidirectional LSPs of an associated |
| 674 |
bidirectional LSP based on (Extended) ASSOCIATION Objects, with the |
| 675 |
Association Type values defined in this document, carried in Path |
| 676 |
messages. Clearly, such associations are only possible when the LSPs |
| 677 |
transit the node. As mentioned above, such associations are made per |
| 678 |
the rules defined in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. |
| 679 |
|
| 680 |
Egress nodes that support the Association Types defined in this |
| 681 |
document identify the unidirectional LSPs of an associated |
| 682 |
bidirectional LSP based on (Extended) ASSOCIATION Objects carried in |
| 683 |
Path messages. Note that an ingress node will normally be the |
| 684 |
ingress for one of the unidirectional LSPs that make up an associated |
| 685 |
bidirectional LSP. When an egress node receives a Path message |
| 686 |
containing an (Extended) ASSOCIATION Object with one of the |
| 687 |
Association Types defined in this document, it MUST attempt to |
| 688 |
identify other LSPs (including ones for which it is an ingress node) |
| 689 |
with which the LSP being processed is associated. As defined above, |
| 690 |
such associations are made per the rules defined in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. An |
| 691 |
LSP not being associated at the time of signaling (for example, |
| 692 |
during rerouting or re-optimization) on an egress node is not |
| 693 |
necessarily considered an error condition. |
| 694 |
|
| 695 |
Associated bidirectional LSP teardown follows the standard procedures |
| 696 |
defined in [<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>] either without or with the |
| 697 |
administrative status. Generally, the teardown procedures of the |
| 698 |
unidirectional LSPs forming an associated bidirectional LSP are |
| 699 |
independent of each other, so it is possible that while one LSP |
| 700 |
follows graceful teardown with administrative status, the reverse LSP |
| 701 |
is torn down without administrative status (using |
| 702 |
PathTear/ResvTear/PathErr with state removal). See <a href="#section-5.2">Section 5.2</a> for |
| 703 |
additional rules related to LSPs established using single-sided |
| 704 |
provisioning. |
| 705 |
|
| 706 |
When an LSP signaled with a Path message containing an (Extended) |
| 707 |
ASSOCIATION Object with an Association Type defined in this document |
| 708 |
is torn down, the processing node SHALL remove the binding of the LSP |
| 709 |
to any previously identified associated bidirectional LSP. |
| 710 |
|
| 711 |
No additional processing is needed for Path messages with an |
| 712 |
(Extended) ASSOCIATION Object containing an Association Type field |
| 713 |
set to "Double-Sided Associated Bidirectional LSP". |
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Zhang, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Compatibility for ASSOCIATION Object</span> |
| 730 |
|
| 731 |
The ASSOCIATION Object has been defined in [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>] and the Extended |
| 732 |
ASSOCIATION Object has been defined in [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>], both with class |
| 733 |
numbers in the form 11bbbbbb, which ensures compatibility with non- |
| 734 |
supporting nodes. Per [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>], such nodes will ignore the object |
| 735 |
but forward it without modification. |
| 736 |
|
| 737 |
Operators wishing to use a function supported by a particular |
| 738 |
Association Type SHOULD ensure that the type is supported on any node |
| 739 |
that is expected to act on the association [<a href="./rfc6780" title=""RSVP ASSOCIATION Object Extensions"">RFC6780</a>]. |
| 740 |
|
| 741 |
An egress node that does not support the Association Types defined in |
| 742 |
this document is expected to return a PathErr with Error Code |
| 743 |
"Admission Control Failure" (1) [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] and Sub-code "Bad |
| 744 |
Association Type" (5) [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>]. |
| 745 |
|
| 746 |
LSP recovery as defined in [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>] and [<a href="./rfc4873" title=""GMPLS Segment Recovery"">RFC4873</a>] is not impacted by |
| 747 |
this document. The recovery mechanisms defined in [<a href="./rfc4872" title=""RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"">RFC4872</a>] and |
| 748 |
[<a href="./rfc4873" title=""GMPLS Segment Recovery"">RFC4873</a>] rely on the use of the (Extended) ASSOCIATION Objects, but |
| 749 |
they use a different value for Association Type; multiple ASSOCIATION |
| 750 |
Objects can be present in the LSP Path message and can coexist with |
| 751 |
the procedures defined in this document. |
| 752 |
|
| 753 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Rules for REVERSE_LSP Object</span> |
| 754 |
|
| 755 |
When a node initiates setup of an LSP using a Path message containing |
| 756 |
an ASSOCIATION or Extended ASSOCIATION Object, and the Association |
| 757 |
Type set to "Single-Sided Associated Bidirectional LSP", the Path |
| 758 |
message MUST carry the REVERSE_LSP Object to trigger creation of a |
| 759 |
reverse LSP on the egress node. |
| 760 |
|
| 761 |
The REVERSE_LSP subobject MAY contain any of the objects that the |
| 762 |
initiating node desires to have included in the Path message for the |
| 763 |
associated reverse LSP. The REVERSE_LSP Object SHOULD NOT be |
| 764 |
included in a REVERSE_LSP Object. |
| 765 |
|
| 766 |
A transit node receiving a valid Path message containing a |
| 767 |
REVERSE_LSP Object MUST forward the REVERSE_LSP Object unchanged in |
| 768 |
the outgoing Path message. |
| 769 |
|
| 770 |
An egress node, upon receiving a Path message containing an |
| 771 |
REVERSE_LSP Object MUST verify that the Path message contains an |
| 772 |
ASSOCIATION or Extended ASSOCIATION Object with the Association Type |
| 773 |
set to "Single-Sided Associated Bidirectional LSP". If it does not, |
| 774 |
the Path message MUST NOT trigger a reverse LSP. This verification |
| 775 |
failure SHOULD NOT trigger any RSVP message but can be logged |
| 776 |
locally, and perhaps reported through network management mechanisms. |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Zhang, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 783 |
|
| 784 |
|
| 785 |
Once validated, the egress node MUST create an LSP in the reverse |
| 786 |
direction or reject the Path message. If the creation of a reverse |
| 787 |
LSP fails, the egress node MUST return a PathErr with Error Code |
| 788 |
"Admission Control Failure" (1) [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] and Sub-code "Reverse LSP |
| 789 |
Failure" (6) defined in this document. Note that normal Resv |
| 790 |
processing SHOULD NOT be impacted by the presence of an ASSOCIATION |
| 791 |
Object with an Association Type set to "Single-Sided Associated |
| 792 |
Bidirectional LSP". |
| 793 |
|
| 794 |
The egress node MUST use the subobjects contained in the REVERSE_LSP |
| 795 |
Object for initiating the reverse LSP. When a subobject is not |
| 796 |
present in the received REVERSE_LSP Object, the egress node SHOULD |
| 797 |
initiate the reverse LSP based on the information contained in the |
| 798 |
received Path message of the forward LSP as follows: |
| 799 |
|
| 800 |
o The egress node SHOULD copy the information from the received |
| 801 |
SESSION_ATTRIBUTE, CLASS_TYPE, LABEL_REQUEST, ASSOCIATION, |
| 802 |
ADMIN_STATUS, and PROTECTION Objects in the forward LSP Path |
| 803 |
message to form the Path message of the reverse LSP when the |
| 804 |
object is not present in the received REVERSE_LSP Object. |
| 805 |
|
| 806 |
o The IP address in the reverse LSP's SESSION Object SHOULD be set |
| 807 |
to the IP address carried in the received SENDER_TEMPLATE Object; |
| 808 |
and conversely, the IP address in the SENDER_TEMPLATE Object |
| 809 |
SHOULD be set to the IP address carried in the received SESSION |
| 810 |
Object. There are no additional requirements related to the IDs |
| 811 |
carried in the SESSION and SENDER_TEMPLATE Objects. |
| 812 |
|
| 813 |
o When the forward LSP Path message contains a RECORD_ROUTE Object, |
| 814 |
the egress node SHOULD include the received RECORD_ROUTE Object in |
| 815 |
the reverse LSP Path message. Local node information SHOULD also |
| 816 |
be recorded per standard Path message processing. |
| 817 |
|
| 818 |
o There are no specific requirements related to other objects. |
| 819 |
|
| 820 |
The resulting Path message is used to create the reverse LSP. From |
| 821 |
this point on, standard Path message processing is used in processing |
| 822 |
the resulting Path message. |
| 823 |
|
| 824 |
Note that the contents of a forward LSP, including a carried |
| 825 |
REVERSE_LSP Object, may change over the life of an LSP, and such |
| 826 |
changes MUST result in corresponding changes in the reverse LSP. In |
| 827 |
particular, any object or subobject that was copied during the |
| 828 |
creation of the initial reverse LSP's Path message MUST be copied |
| 829 |
when modified in the forward LSP, and a trigger Path message MUST be |
| 830 |
processed. |
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Zhang, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 839 |
|
| 840 |
|
| 841 |
The removal of the REVERSE_LSP Object in the received Path message |
| 842 |
SHOULD cause the egress node to tear down any previously established |
| 843 |
reverse LSP. |
| 844 |
|
| 845 |
When the egress node receives a PathTear message for the forward LSP |
| 846 |
or whenever the forward LSP is torn down, the node MUST remove the |
| 847 |
associated reverse LSP using standard PathTear message processing. |
| 848 |
Teardown of the reverse LSP for other reasons SHOULD NOT trigger |
| 849 |
removal of the initiating LSP, but it SHOULD result in the egress |
| 850 |
node sending a PathErr with Error Code "Admission Control Failure" |
| 851 |
(1) [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>] and Sub-code "Reverse LSP Failure" (6) defined in this |
| 852 |
document. |
| 853 |
|
| 854 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Compatibility for REVERSE_LSP Object</span> |
| 855 |
|
| 856 |
The REVERSE_LSP Object is defined with class numbers in the form |
| 857 |
11bbbbbb, which ensures compatibility with non-supporting nodes. Per |
| 858 |
[<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>], such nodes will ignore the object but forward it without |
| 859 |
modification. |
| 860 |
|
| 861 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 862 |
|
| 863 |
IANA has registered values for the namespace defined in this document |
| 864 |
and summarized in this section. |
| 865 |
|
| 866 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Association Types</span> |
| 867 |
|
| 868 |
IANA maintains the "Generalized Multi-Protocol Label Switching |
| 869 |
(GMPLS) Signaling Parameters" registry (see |
| 870 |
<<a href="http://www.iana.org/assignments/gmpls-sig-parameters">http://www.iana.org/assignments/gmpls-sig-parameters</a>>). The |
| 871 |
"Association Type" subregistry is included in this registry. |
| 872 |
|
| 873 |
This registry has been updated by new Association Types for |
| 874 |
ASSOCIATION and Extended ASSOCIATION Objects defined in this document |
| 875 |
as follows: |
| 876 |
|
| 877 |
Value Name Reference |
| 878 |
3 Double-Sided Associated Bidirectional LSP (D) <a href="#section-4.2">Section 4.2</a> |
| 879 |
4 Single-Sided Associated Bidirectional LSP (A) <a href="#section-4.2">Section 4.2</a> |
| 880 |
|
| 881 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. REVERSE_LSP Object</span> |
| 882 |
|
| 883 |
IANA maintains the "Resource Reservation Protocol (RSVP) Parameters" |
| 884 |
registry (see <<a href="http://www.iana.org/assignments/rsvp-parameters">http://www.iana.org/assignments/rsvp-parameters</a>>). |
| 885 |
The "Class Names, Class Numbers, and Class Types" subregistry is |
| 886 |
included in this registry. |
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Zhang, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 895 |
|
| 896 |
|
| 897 |
This registry has been extended for new Class Number (Class-Num) and |
| 898 |
Class Type (C-type) for RSVP REVERSE_LSP Object requested in the |
| 899 |
11bbbbbb range defined in this document as follows: |
| 900 |
|
| 901 |
Class Number Class Name Reference |
| 902 |
203 REVERSE_LSP <a href="#section-4.4">Section 4.4</a> |
| 903 |
|
| 904 |
o REVERSE_LSP : Class Type or C-type = 1 |
| 905 |
|
| 906 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Reverse LSP Failure PathErr Sub-code</span> |
| 907 |
|
| 908 |
IANA maintains the "Resource Reservation Protocol (RSVP) Parameters" |
| 909 |
registry (see <<a href="http://www.iana.org/assignments/rsvp-parameters">http://www.iana.org/assignments/rsvp-parameters</a>>). |
| 910 |
The "Error Codes and Globally-Defined Error Value Sub-Codes" |
| 911 |
subregistry is included in this registry. |
| 912 |
|
| 913 |
This registry has been extended for the new PathErr Sub-code defined |
| 914 |
in this document as follows: |
| 915 |
|
| 916 |
Error Code = 01: "Admission Control Failure" (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]) |
| 917 |
|
| 918 |
o "Reverse LSP Failure" (6) |
| 919 |
|
| 920 |
|
| 921 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 922 |
|
| 923 |
This document introduces two new Association Types for the (Extended) |
| 924 |
ASSOCIATION Object, Double-Sided Associated Bidirectional LSP and |
| 925 |
Single-Sided Associated Bidirectional LSP. These types, by |
| 926 |
themselves, introduce no additional information to signaling. |
| 927 |
Related security considerations are already covered for this in <a href="./rfc6780">RFC</a> |
| 928 |
<a href="./rfc6780">6780</a>. |
| 929 |
|
| 930 |
The REVERSE_LSP Object is carried in the Path message of a forward |
| 931 |
LSP of the single-sided associated bidirectional LSP. It can carry |
| 932 |
parameters for the reverse LSP. This does allow for additional |
| 933 |
information to be conveyed, but this information is not fundamentally |
| 934 |
different from the information that is already carried in a |
| 935 |
bidirectional LSP message. The processing of such messages is |
| 936 |
already subject to local policy as well as security considerations |
| 937 |
discussions. For a general discussion on MPLS- and GMPLS-related |
| 938 |
security issues, see the MPLS/GMPLS security framework [<a href="./rfc5920" title=""Security Framework for MPLS and GMPLS Networks"">RFC5920</a>]. |
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Zhang, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 954 |
|
| 955 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 956 |
|
| 957 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 958 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, |
| 959 |
DOI 10.17487/RFC2119, March 1997, |
| 960 |
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>. |
| 961 |
|
| 962 |
[<a id="ref-RFC2205">RFC2205</a>] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. |
| 963 |
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 |
| 964 |
Functional Specification", <a href="./rfc2205">RFC 2205</a>, DOI 10.17487/RFC2205, |
| 965 |
September 1997, <<a href="http://www.rfc-editor.org/info/rfc2205">http://www.rfc-editor.org/info/rfc2205</a>>. |
| 966 |
|
| 967 |
[<a id="ref-RFC3209">RFC3209</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., |
| 968 |
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP |
| 969 |
Tunnels", <a href="./rfc3209">RFC 3209</a>, DOI 10.17487/RFC3209, December 2001, |
| 970 |
<<a href="http://www.rfc-editor.org/info/rfc3209">http://www.rfc-editor.org/info/rfc3209</a>>. |
| 971 |
|
| 972 |
[<a id="ref-RFC3473">RFC3473</a>] Berger, L., Ed., "Generalized Multi-Protocol Label |
| 973 |
Switching (GMPLS) Signaling Resource ReserVation Protocol- |
| 974 |
Traffic Engineering (RSVP-TE) Extensions", <a href="./rfc3473">RFC 3473</a>, |
| 975 |
DOI 10.17487/RFC3473, January 2003, |
| 976 |
<<a href="http://www.rfc-editor.org/info/rfc3473">http://www.rfc-editor.org/info/rfc3473</a>>. |
| 977 |
|
| 978 |
[<a id="ref-RFC4872">RFC4872</a>] Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou, |
| 979 |
Ed., "RSVP-TE Extensions in Support of End-to-End |
| 980 |
Generalized Multi-Protocol Label Switching (GMPLS) |
| 981 |
Recovery", <a href="./rfc4872">RFC 4872</a>, DOI 10.17487/RFC4872, May 2007, |
| 982 |
<<a href="http://www.rfc-editor.org/info/rfc4872">http://www.rfc-editor.org/info/rfc4872</a>>. |
| 983 |
|
| 984 |
[<a id="ref-RFC4873">RFC4873</a>] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel, |
| 985 |
"GMPLS Segment Recovery", <a href="./rfc4873">RFC 4873</a>, DOI 10.17487/RFC4873, |
| 986 |
May 2007, <<a href="http://www.rfc-editor.org/info/rfc4873">http://www.rfc-editor.org/info/rfc4873</a>>. |
| 987 |
|
| 988 |
[<a id="ref-RFC5511">RFC5511</a>] Farrel, A., "Routing Backus-Naur Form (RBNF): A Syntax |
| 989 |
Used to Form Encoding Rules in Various Routing Protocol |
| 990 |
Specifications", <a href="./rfc5511">RFC 5511</a>, DOI 10.17487/RFC5511, April |
| 991 |
2009, <<a href="http://www.rfc-editor.org/info/rfc5511">http://www.rfc-editor.org/info/rfc5511</a>>. |
| 992 |
|
| 993 |
[<a id="ref-RFC6780">RFC6780</a>] Berger, L., Le Faucheur, F., and A. Narayanan, "RSVP |
| 994 |
ASSOCIATION Object Extensions", <a href="./rfc6780">RFC 6780</a>, |
| 995 |
DOI 10.17487/RFC6780, October 2012, |
| 996 |
<<a href="http://www.rfc-editor.org/info/rfc6780">http://www.rfc-editor.org/info/rfc6780</a>>. |
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Zhang, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 1010 |
|
| 1011 |
[<a id="ref-RFC4655">RFC4655</a>] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path |
| 1012 |
Computation Element (PCE)-Based Architecture", <a href="./rfc4655">RFC 4655</a>, |
| 1013 |
DOI 10.17487/RFC4655, August 2006, |
| 1014 |
<<a href="http://www.rfc-editor.org/info/rfc4655">http://www.rfc-editor.org/info/rfc4655</a>>. |
| 1015 |
|
| 1016 |
[<a id="ref-RFC5420">RFC5420</a>] Farrel, A., Ed., Papadimitriou, D., Vasseur, JP., and A. |
| 1017 |
Ayyangarps, "Encoding of Attributes for MPLS LSP |
| 1018 |
Establishment Using Resource Reservation Protocol Traffic |
| 1019 |
Engineering (RSVP-TE)", <a href="./rfc5420">RFC 5420</a>, DOI 10.17487/RFC5420, |
| 1020 |
February 2009, <<a href="http://www.rfc-editor.org/info/rfc5420">http://www.rfc-editor.org/info/rfc5420</a>>. |
| 1021 |
|
| 1022 |
[<a id="ref-RFC5654">RFC5654</a>] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., |
| 1023 |
Sprecher, N., and S. Ueno, "Requirements of an MPLS |
| 1024 |
Transport Profile", <a href="./rfc5654">RFC 5654</a>, DOI 10.17487/RFC5654, |
| 1025 |
September 2009, <<a href="http://www.rfc-editor.org/info/rfc5654">http://www.rfc-editor.org/info/rfc5654</a>>. |
| 1026 |
|
| 1027 |
[<a id="ref-RFC5920">RFC5920</a>] Fang, L., Ed., "Security Framework for MPLS and GMPLS |
| 1028 |
Networks", <a href="./rfc5920">RFC 5920</a>, DOI 10.17487/RFC5920, July 2010, |
| 1029 |
<<a href="http://www.rfc-editor.org/info/rfc5920">http://www.rfc-editor.org/info/rfc5920</a>>. |
| 1030 |
|
| 1031 |
[<a id="ref-RFC6370">RFC6370</a>] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport |
| 1032 |
Profile (MPLS-TP) Identifiers", <a href="./rfc6370">RFC 6370</a>, |
| 1033 |
DOI 10.17487/RFC6370, September 2011, |
| 1034 |
<<a href="http://www.rfc-editor.org/info/rfc6370">http://www.rfc-editor.org/info/rfc6370</a>>. |
| 1035 |
|
| 1036 |
[<a id="ref-RFC6373">RFC6373</a>] Andersson, L., Ed., Berger, L., Ed., Fang, L., Ed., Bitar, |
| 1037 |
N., Ed., and E. Gray, Ed., "MPLS Transport Profile |
| 1038 |
(MPLS-TP) Control Plane Framework", <a href="./rfc6373">RFC 6373</a>, |
| 1039 |
DOI 10.17487/RFC6373, September 2011, |
| 1040 |
<<a href="http://www.rfc-editor.org/info/rfc6373">http://www.rfc-editor.org/info/rfc6373</a>>. |
| 1041 |
|
| 1042 |
[<a id="ref-RFC6387">RFC6387</a>] Takacs, A., Berger, L., Caviglia, D., Fedyk, D., and J. |
| 1043 |
Meuric, "GMPLS Asymmetric Bandwidth Bidirectional Label |
| 1044 |
Switched Paths (LSPs)", <a href="./rfc6387">RFC 6387</a>, DOI 10.17487/RFC6387, |
| 1045 |
September 2011, <<a href="http://www.rfc-editor.org/info/rfc6387">http://www.rfc-editor.org/info/rfc6387</a>>. |
| 1046 |
|
| 1047 |
[<a id="ref-RFC6689">RFC6689</a>] Berger, L., "Usage of the RSVP ASSOCIATION Object", |
| 1048 |
<a href="./rfc6689">RFC 6689</a>, DOI 10.17487/RFC6689, July 2012, |
| 1049 |
<<a href="http://www.rfc-editor.org/info/rfc6689">http://www.rfc-editor.org/info/rfc6689</a>>. |
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Zhang, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc7551">RFC 7551</a> RSVP-TE Extensions for Associated LSP May 2015</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Acknowledgements |
| 1066 |
|
| 1067 |
The authors would like to thank Lou Berger and George Swallow for |
| 1068 |
their great guidance in this work; Jie Dong for the discussion of the |
| 1069 |
recovery LSP; Lamberto Sterling for his valuable comments about |
| 1070 |
asymmetric bandwidth signaling; Attila Takacs for the discussion of |
| 1071 |
the provisioning model; Siva Sivabalan, Eric Osborne, and Robert |
| 1072 |
Sawaya for the discussions on the ASSOCIATION Object; and Matt |
| 1073 |
Hartley for providing useful suggestions on the document. At the |
| 1074 |
same time, the authors would like to acknowledge the contributions of |
| 1075 |
Bo Wu, Xihua Fu, and Lizhong Jin for the initial discussions; Wenjuan |
| 1076 |
He for the prototype implementation; and Lou Berger, Daniel King, and |
| 1077 |
Deborah Brungard for the review of the document. |
| 1078 |
|
| 1079 |
Contributors |
| 1080 |
|
| 1081 |
Fan Yang |
| 1082 |
ZTE |
| 1083 |
|
| 1084 |
EMail: [email protected] |
| 1085 |
|
| 1086 |
|
| 1087 |
Weilian Jiang |
| 1088 |
ZTE |
| 1089 |
|
| 1090 |
EMail: [email protected] |
| 1091 |
|
| 1092 |
Authors' Addresses |
| 1093 |
|
| 1094 |
Fei Zhang (editor) |
| 1095 |
Huawei |
| 1096 |
|
| 1097 |
EMail: [email protected] |
| 1098 |
|
| 1099 |
|
| 1100 |
Ruiquan Jing |
| 1101 |
China Telecom |
| 1102 |
|
| 1103 |
EMail: [email protected] |
| 1104 |
|
| 1105 |
|
| 1106 |
Rakesh Gandhi (editor) |
| 1107 |
Cisco Systems |
| 1108 |
|
| 1109 |
EMail: [email protected] |
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
Zhang, et al. Standards Track [Page 20] |
| 1117 |
</pre> |