| 1 |
<pre>Internet Engineering Task Force (IETF) R. Aggarwal |
| 2 |
Request for Comments: 6389 Juniper Networks |
| 3 |
Category: Standards Track JL. Le Roux |
| 4 |
ISSN: 2070-1721 Orange |
| 5 |
November 2011 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">MPLS Upstream Label Assignment for LDP</span> |
| 9 |
|
| 10 |
Abstract |
| 11 |
|
| 12 |
This document describes procedures for distributing upstream-assigned |
| 13 |
labels for the Label Distribution Protocol (LDP). It also describes |
| 14 |
how these procedures can be used for avoiding branch Label Switching |
| 15 |
Router (LSR) traffic replication on a LAN for LDP point-to-multipoint |
| 16 |
(P2MP) Label Switched Paths (LSPs). |
| 17 |
|
| 18 |
Status of This Memo |
| 19 |
|
| 20 |
This is an Internet Standards Track document. |
| 21 |
|
| 22 |
This document is a product of the Internet Engineering Task Force |
| 23 |
(IETF). It represents the consensus of the IETF community. It has |
| 24 |
received public review and has been approved for publication by the |
| 25 |
Internet Engineering Steering Group (IESG). Further information on |
| 26 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 27 |
|
| 28 |
Information about the current status of this document, any errata, |
| 29 |
and how to provide feedback on it may be obtained at |
| 30 |
<a href="http://www.rfc-editor.org/info/rfc6389">http://www.rfc-editor.org/info/rfc6389</a>. |
| 31 |
|
| 32 |
Copyright Notice |
| 33 |
|
| 34 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 35 |
document authors. All rights reserved. |
| 36 |
|
| 37 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 38 |
Provisions Relating to IETF Documents |
| 39 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 40 |
publication of this document. Please review these documents |
| 41 |
carefully, as they describe your rights and restrictions with respect |
| 42 |
to this document. Code Components extracted from this document must |
| 43 |
include Simplified BSD License text as described in Section 4.e of |
| 44 |
the Trust Legal Provisions and are provided without warranty as |
| 45 |
described in the Simplified BSD License. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
This document may contain material from IETF Documents or IETF |
| 58 |
Contributions published or made publicly available before November |
| 59 |
10, 2008. The person(s) controlling the copyright in some of this |
| 60 |
material may not have granted the IETF Trust the right to allow |
| 61 |
modifications of such material outside the IETF Standards Process. |
| 62 |
Without obtaining an adequate license from the person(s) controlling |
| 63 |
the copyright in such materials, this document may not be modified |
| 64 |
outside the IETF Standards Process, and derivative works of it may |
| 65 |
not be created outside the IETF Standards Process, except to format |
| 66 |
it for publication as an RFC or to translate it into languages other |
| 67 |
than English. |
| 68 |
|
| 69 |
Table of Contents |
| 70 |
|
| 71 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 72 |
<a href="#section-2">2</a>. Specification of Requirements ...................................<a href="#page-3">3</a> |
| 73 |
<a href="#section-3">3</a>. LDP Upstream Label Assignment Capability ........................<a href="#page-3">3</a> |
| 74 |
<a href="#section-4">4</a>. Distributing Upstream-Assigned Labels in LDP ....................<a href="#page-4">4</a> |
| 75 |
<a href="#section-4.1">4.1</a>. Procedures .................................................<a href="#page-4">4</a> |
| 76 |
<a href="#section-5">5</a>. LDP Tunnel Identifier Exchange ..................................<a href="#page-5">5</a> |
| 77 |
<a href="#section-6">6</a>. LDP Point-to-Multipoint LSPs on a LAN ...........................<a href="#page-9">9</a> |
| 78 |
<a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-11">11</a> |
| 79 |
<a href="#section-7.1">7.1</a>. LDP TLVs ..................................................<a href="#page-11">11</a> |
| 80 |
<a href="#section-7.2">7.2</a>. Interface Type Identifiers ................................<a href="#page-11">11</a> |
| 81 |
<a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-12">12</a> |
| 82 |
<a href="#section-9">9</a>. Acknowledgements ...............................................<a href="#page-12">12</a> |
| 83 |
<a href="#section-10">10</a>. References ....................................................<a href="#page-12">12</a> |
| 84 |
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-12">12</a> |
| 85 |
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-13">13</a> |
| 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">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
This document describes procedures for distributing upstream-assigned |
| 116 |
labels [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>] for Label Distribution Protocol (LDP) [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>]. |
| 117 |
These procedures follow the architecture for MPLS upstream label |
| 118 |
assignment described in [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>]. |
| 119 |
|
| 120 |
This document describes extensions to LDP that a Label Switching |
| 121 |
Router (LSR) can use to advertise whether the LSR supports upstream |
| 122 |
label assignment to its neighboring LSRs. |
| 123 |
|
| 124 |
This document also describes extensions to LDP to distribute |
| 125 |
upstream-assigned labels. |
| 126 |
|
| 127 |
The usage of MPLS upstream label assignment using LDP to avoid branch |
| 128 |
LSR traffic replication on a LAN for LDP point-to-multipoint (P2MP) |
| 129 |
Label Switched Paths (LSPs) [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>] is also described. |
| 130 |
|
| 131 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification of Requirements</span> |
| 132 |
|
| 133 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 134 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 135 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 136 |
|
| 137 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. LDP Upstream Label Assignment Capability</span> |
| 138 |
|
| 139 |
According to [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>], upstream-assigned label bindings MUST NOT be |
| 140 |
used unless it is known that a downstream LSR supports them. This |
| 141 |
implies that there MUST be a mechanism to enable an LSR to advertise |
| 142 |
to its LDP neighbor LSR(s) its support of upstream-assigned labels. |
| 143 |
|
| 144 |
A new Capability Parameter, the LDP Upstream Label Assignment |
| 145 |
Capability, is introduced to allow an LDP peer to exchange with its |
| 146 |
peers, its support of upstream label assignment. This parameter |
| 147 |
follows the format and procedures for exchanging Capability |
| 148 |
Parameters defined in [<a href="./rfc5561" title=""LDP Capabilities"">RFC5561</a>]. |
| 149 |
|
| 150 |
Following is the format of the LDP Upstream Label Assignment |
| 151 |
Capability Parameter: |
| 152 |
|
| 153 |
0 1 2 3 |
| 154 |
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 |
| 155 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 156 |
|1|0| Upstrm Lbl Ass Cap(0x0507)| Length (= 1) | |
| 157 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 158 |
|1| Reserved | |
| 159 |
+-+-+-+-+-+-+-+-+ |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
If an LSR includes the Upstream Label Assignment Capability in LDP |
| 170 |
Initialization messages, it implies that the LSR is capable of both |
| 171 |
distributing upstream-assigned label bindings and receiving upstream- |
| 172 |
assigned label bindings. The reserved bits MUST be set to zero on |
| 173 |
transmission and ignored on receipt. The Upstream Label Assignment |
| 174 |
Capability Parameter MUST be carried only in LDP Initialization |
| 175 |
messages and MUST be ignored if received in LDP Capability messages. |
| 176 |
|
| 177 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Distributing Upstream-Assigned Labels in LDP</span> |
| 178 |
|
| 179 |
An optional LDP TLV, Upstream-Assigned Label Request TLV, is |
| 180 |
introduced. To request an upstream-assigned label, an LDP peer MUST |
| 181 |
include this TLV in a Label Request message. |
| 182 |
|
| 183 |
0 1 2 3 |
| 184 |
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 |
| 185 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 186 |
|0|0|Upstrm-Ass Lbl Req (0x0205)| Length | |
| 187 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 188 |
| Reserved | |
| 189 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 190 |
|
| 191 |
An optional LDP TLV, Upstream-Assigned Label TLV, is introduced to |
| 192 |
signal an upstream-assigned label. Upstream-Assigned Label TLVs are |
| 193 |
carried by the messages used to advertise, release, and withdraw |
| 194 |
upstream-assigned label mappings. |
| 195 |
|
| 196 |
0 1 2 3 |
| 197 |
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 |
| 198 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 199 |
|0|0| Upstrm-Ass Label (0x0204) | Length | |
| 200 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 201 |
| Reserved | |
| 202 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 203 |
| Label | |
| 204 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 205 |
|
| 206 |
The Label field is a 20-bit label value as specified in [<a href="./rfc3032" title=""MPLS Label Stack Encoding"">RFC3032</a>], |
| 207 |
represented as a 20-bit number in a 4-octet field as specified in |
| 208 |
<a href="./rfc5036#section-3.4.2.1">Section 3.4.2.1 of RFC 5036</a> [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>]. |
| 209 |
|
| 210 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Procedures</span> |
| 211 |
|
| 212 |
Procedures for Label Mapping, Label Request, Label Abort, Label |
| 213 |
Withdraw, and Label Release follow [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>] other than the |
| 214 |
modifications pointed out in this section. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
An LDP LSR MUST NOT distribute the Upstream-Assigned Label TLV to a |
| 226 |
neighboring LSR if the neighboring LSR has not previously advertised |
| 227 |
the Upstream Label Assignment Capability in its LDP Initialization |
| 228 |
messages. An LDP LSR MUST NOT send the Upstream-Assigned Label |
| 229 |
Request TLV to a neighboring LSR if the neighboring LSR has not |
| 230 |
previously advertised the Upstream Label Assignment Capability in its |
| 231 |
LDP Initialization messages. |
| 232 |
|
| 233 |
As described in [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>], the distribution of upstream-assigned |
| 234 |
labels is similar to either ordered LSP control or independent LSP |
| 235 |
control of the downstream-assigned labels. |
| 236 |
|
| 237 |
When the label distributed in a Label Mapping message is an upstream- |
| 238 |
assigned label, the Upstream-Assigned Label TLV MUST be included in |
| 239 |
the Label Mapping message. When an LSR receives a Label Mapping |
| 240 |
message with an Upstream-Assigned Label TLV and it does not recognize |
| 241 |
the TLV, it MUST generate a Notification message with a status code |
| 242 |
of "Unknown TLV" [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>]. If it does recognize the TLV but is |
| 243 |
unable to process the upstream label, it MUST generate a Notification |
| 244 |
message with a status code of "No Label Resources". If the Label |
| 245 |
Mapping message was generated in response to a Label Request message, |
| 246 |
the Label Request message MUST contain an Upstream-Assigned Label |
| 247 |
Request TLV. An LSR that generates an upstream-assigned label |
| 248 |
request to a neighbor LSR, for a given FEC, MUST NOT send a |
| 249 |
downstream label mapping to the neighbor LSR for that FEC unless it |
| 250 |
withdraws the upstream-assigned label binding. Similarly, if an LSR |
| 251 |
generates a downstream-assigned label request to a neighbor LSR, for |
| 252 |
a given FEC, it MUST NOT send an upstream label mapping to that LSR |
| 253 |
for that FEC, unless it aborts the downstream-assigned label request. |
| 254 |
|
| 255 |
The Upstream-Assigned Label TLV may be optionally included in Label |
| 256 |
Withdraw and Label Release messages that withdraw/release a |
| 257 |
particular upstream-assigned label binding. |
| 258 |
|
| 259 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. LDP Tunnel Identifier Exchange</span> |
| 260 |
|
| 261 |
As described in [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>], a specific upstream LSR (Ru) MAY transmit |
| 262 |
an MPLS packet, the top label of which (L) is upstream assigned, to |
| 263 |
its downstream neighbor LSR (Rd). In this case, the fact that L is |
| 264 |
upstream assigned is determined by Rd by the tunnel on which the |
| 265 |
packet is received. There must be a mechanism for Ru to inform Rd |
| 266 |
that a particular tunnel from Ru to Rd will be used by Ru for |
| 267 |
transmitting MPLS packets with upstream-assigned MPLS labels. |
| 268 |
|
| 269 |
When LDP is used for upstream label assignment, the Interface ID TLV |
| 270 |
[<a href="./rfc3472" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions"">RFC3472</a>] is used for signaling the Tunnel Identifier. If Ru uses an |
| 271 |
IP or MPLS tunnel to transmit MPLS packets with upstream assigned |
| 272 |
labels to Rd, Ru MUST include the Interface ID TLV in the Label |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
Mapping messages along with the Upstream-Assigned Label TLV. The |
| 282 |
IPv4/IPv6 Next/Previous Hop Address and the Logical Interface ID |
| 283 |
fields in the Interface ID TLV SHOULD be set to 0 by the sender and |
| 284 |
ignored by the receiver. The Length field indicates the total length |
| 285 |
of the TLV, i.e., 4 + the length of the Value field in octets. A |
| 286 |
Value field whose length is not a multiple of four MUST be zero- |
| 287 |
padded so that the TLV is four-octet aligned. |
| 288 |
|
| 289 |
Hence the IPv4 Interface ID TLV has the following format: |
| 290 |
|
| 291 |
0 1 2 3 |
| 292 |
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 |
| 293 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 294 |
|0|0| Type (0x082d) | Length | |
| 295 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 296 |
| IPv4 Next/Previous Hop Address (0) | |
| 297 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 298 |
| Logical Interface ID (0) | |
| 299 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 300 |
| Sub-TLVs | |
| 301 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 302 |
|
| 303 |
The IPv6 Interface ID TLV has the following format: |
| 304 |
|
| 305 |
0 1 2 3 |
| 306 |
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 |
| 307 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 308 |
|0|0| Type (0x082e) | Length | |
| 309 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 310 |
| IPv6 Next/Previous Hop Address (0) | |
| 311 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 312 |
| Logical Interface ID (0) | |
| 313 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 314 |
| Sub-TLVs | |
| 315 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 316 |
|
| 317 |
As shown in the above figures, the Interface ID TLV carries sub-TLVs. |
| 318 |
Four new Interface ID sub-TLVs are introduced to support RSVP - |
| 319 |
Traffic Engineering (RSVP-TE) P2MP LSPs, LDP P2MP LSPs, IP Multicast |
| 320 |
Tunnels, and context labels. The sub-TLV value in the sub-TLV acts |
| 321 |
as the tunnel identifier. |
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
The following sub-TLVs are introduced: |
| 338 |
|
| 339 |
1. RSVP-TE P2MP LSP TLV (Type = 28) |
| 340 |
|
| 341 |
The value of the TLV is the RSVP-TE P2MP LSP SESSION Object |
| 342 |
[<a href="./rfc4875" title=""Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)"">RFC4875</a>]. |
| 343 |
|
| 344 |
Below is the RSVP-TE P2MP LSP TLV format when carried in the IPv4 |
| 345 |
Interface ID TLV: |
| 346 |
|
| 347 |
0 1 2 3 |
| 348 |
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 |
| 349 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 350 |
| Type (0x1c) | 16 | |
| 351 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 352 |
| P2MP ID | |
| 353 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 354 |
| MUST be zero | Tunnel ID | |
| 355 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 356 |
| Extended Tunnel ID | |
| 357 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 358 |
|
| 359 |
Below is the RSVP-TE P2MP LSP TLV format when carried in the IPv6 |
| 360 |
Interface ID TLV: |
| 361 |
|
| 362 |
0 1 2 3 |
| 363 |
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 |
| 364 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 365 |
| Type (0x1c) | 28 | |
| 366 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 367 |
| P2MP ID | |
| 368 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 369 |
| MUST be zero | Tunnel ID | |
| 370 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 371 |
| Extended Tunnel ID | |
| 372 |
| | |
| 373 |
| ....... | |
| 374 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 375 |
|
| 376 |
This TLV identifies the RSVP-TE P2MP LSP. It allows Ru to tunnel an |
| 377 |
"inner" LDP P2MP LSP, the label for which is upstream assigned, over |
| 378 |
an "outer" RSVP-TE P2MP LSP that has leaves <Rd1...Rdn>. The RSVP-TE |
| 379 |
P2MP LSP IF_ID TLV allows Ru to signal to <Rd1...Rdn> the binding of |
| 380 |
the inner LDP P2MP LSP to the outer RSVP-TE P2MP LSP. The control- |
| 381 |
plane signaling between Ru and <Rd1...Rdn> for the inner P2MP LSP |
| 382 |
uses targeted LDP signaling messages. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
2. LDP P2MP LSP TLV (Type = 29) |
| 394 |
|
| 395 |
The value of the TLV is the LDP P2MP FEC as defined in [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>] and |
| 396 |
has to be set as per the procedures in [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>]. Here is the format |
| 397 |
of the LDP P2MP FEC as defined in [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>]: |
| 398 |
|
| 399 |
0 1 2 3 |
| 400 |
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 |
| 401 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 402 |
|P2MP Type | Address Family | Address Length| |
| 403 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 404 |
~ Root Node Address ~ |
| 405 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 406 |
| Opaque Length | Opaque Value ... | |
| 407 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 408 |
~ ~ |
| 409 |
| | |
| 410 |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 411 |
| | |
| 412 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 413 |
|
| 414 |
The Address Family MUST be set to IPv4, the Address Length MUST be |
| 415 |
set to 4, and the Root Node Address MUST be set to an IPv4 address |
| 416 |
when the LDP P2MP LSP TLV is carried in the IPv4 Interface ID TLV. |
| 417 |
The Address Family MUST be set to IPv6, the Address Length MUST be |
| 418 |
set to 16, and the Root Node Address MUST be set to an IPv6 address |
| 419 |
when the LDP P2MP LSP TLV is carried in the IPv6 Interface ID TLV. |
| 420 |
|
| 421 |
The TLV value identifies the LDP P2MP LSP. It allows Ru to tunnel an |
| 422 |
inner LDP P2MP LSP, the label for which is upstream assigned, over an |
| 423 |
outer LDP P2MP LSP that has leaves <Rd1...Rdn>. The LDP P2MP LSP |
| 424 |
IF_ID TLV allows Ru to signal to <Rd1...Rdn> the binding of the inner |
| 425 |
LDP P2MP LSP to the outer LDP-P2MP LSP. The control-plane signaling |
| 426 |
between Ru and <Rd1...Rdn> for the inner P2MP LSP uses targeted LDP |
| 427 |
signaling messages. |
| 428 |
|
| 429 |
3. IP Multicast Tunnel TLV (Type = 30) |
| 430 |
|
| 431 |
In this case, the TLV value is a <Source Address, Multicast Group |
| 432 |
Address> tuple. Source Address is the IP address of the root of the |
| 433 |
tunnel (i.e., Ru), and Multicast Group Address is the Multicast Group |
| 434 |
Address used by the tunnel. The addresses MUST be IPv4 addresses |
| 435 |
when the IP Multicast Tunnel TLV is included in the IPv4 Interface ID |
| 436 |
TLV. The addresses MUST be IPv6 addresses when the IP Multicast |
| 437 |
Tunnel TLV is included in the IPv6 Interface ID TLV. |
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 447 |
|
| 448 |
|
| 449 |
4. MPLS Context Label TLV (Type = 31) |
| 450 |
|
| 451 |
In this case, the TLV value is a <Source Address, MPLS Context Label> |
| 452 |
tuple. The Source Address belongs to Ru and the MPLS Context Label |
| 453 |
is an upstream-assigned label, assigned by Ru. The Source Address |
| 454 |
MUST be set to an IPv4 address when the MPLS Context Label TLV is |
| 455 |
carried in the IPv4 Interface ID TLV. The Source Address MUST be set |
| 456 |
to an IPv6 address when the MPLS Context Label TLV is carried in the |
| 457 |
IPv6 Interface ID TLV. This allows Ru to tunnel an inner LDP P2MP |
| 458 |
LSP, the label of which is upstream assigned, over an outer one-hop |
| 459 |
MPLS LSP, where the outer one-hop LSP has the following property: |
| 460 |
|
| 461 |
o The label pushed by Ru for the outer MPLS LSP is an upstream- |
| 462 |
assigned context label, assigned by Ru. When <Rd1...Rdn> |
| 463 |
perform an MPLS label lookup on this label, a combination of |
| 464 |
this label and the incoming interface MUST be sufficient for |
| 465 |
<Rd1...Rdn> to uniquely determine Ru's context-specific label |
| 466 |
space to look up the next label on the stack. <Rd1...Rdn> MUST |
| 467 |
receive the data sent by Ru with the context-specific label |
| 468 |
assigned by Ru being the top label on the label stack. |
| 469 |
|
| 470 |
Currently, the usage of the Context Label TLV is limited only to LDP |
| 471 |
P2MP LSPs on a LAN as specified in the next section. The Context |
| 472 |
Label TLV MUST NOT be used for any other purpose. |
| 473 |
|
| 474 |
Note that when the outer P2MP LSP is signaled with RSVP-TE or MLDP, |
| 475 |
the above procedures assume that Ru has a priori knowledge of all the |
| 476 |
<Rd1, ... Rdn>. In the scenario where the outer P2MP LSP is signaled |
| 477 |
using RSVP-TE, Ru can obtain this information from RSVP-TE. However, |
| 478 |
in the scenario where the outer P2MP LSP is signaled using MLDP, MLDP |
| 479 |
does not provide this information to Ru. In this scenario, the |
| 480 |
procedures by which Ru could acquire this information are outside the |
| 481 |
scope of this document. |
| 482 |
|
| 483 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. LDP Point-to-Multipoint LSPs on a LAN</span> |
| 484 |
|
| 485 |
This section describes one application of upstream label assignment |
| 486 |
using LDP. Further applications are to be described in separate |
| 487 |
documents. |
| 488 |
|
| 489 |
[<a id="ref-RFC6388">RFC6388</a>] describes how to setup P2MP LSPs using LDP. On a LAN the |
| 490 |
solution relies on "ingress replication". An LSR on a LAN, that is a |
| 491 |
branch LSR for a P2MP LSP (say Ru), sends a separate copy of a packet |
| 492 |
that it receives on the P2MP LSP to each of the downstream LSRs on |
| 493 |
the LAN (say <Rd1...Rdn>) that are adjacent to it in the P2MP LSP. |
| 494 |
|
| 495 |
It is desirable for Ru to send a single copy of the packet for the |
| 496 |
LDP P2MP LSP on the LAN, when there are multiple downstream routers |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 503 |
|
| 504 |
|
| 505 |
on the LAN that are adjacent to Ru in that LDP P2MP LSP. This |
| 506 |
requires that each of <Rd1...Rdn> must be able to associate the label |
| 507 |
L, used by Ru to transmit packets for the P2MP LSP on the LAN, with |
| 508 |
that P2MP LSP. It is possible to achieve this using LDP upstream- |
| 509 |
assigned labels with the following procedures. |
| 510 |
|
| 511 |
Consider an LSR Rd that receives the LDP P2MP FEC [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>] from its |
| 512 |
downstream LDP peer. Additionally, consider that the upstream |
| 513 |
interface to reach LSR Ru that is the next hop to the P2MP LSP root |
| 514 |
address (Pr) in the LDP P2MP FEC is a LAN interface (Li) and that Rd |
| 515 |
and Ru support upstream-assigned labels. In this case, instead of |
| 516 |
sending a Label Mapping message as described in [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>], Rd sends a |
| 517 |
Label Request message to Ru. This Label Request message MUST contain |
| 518 |
an Upstream-Assigned Label Request TLV. |
| 519 |
|
| 520 |
On receiving this message, Ru sends back a Label Mapping message to |
| 521 |
Rd with an upstream-assigned label. This message also contains an |
| 522 |
Interface ID TLV with an MPLS Context Label sub-TLV, as described in |
| 523 |
the previous section, with the value of the MPLS label set to a value |
| 524 |
assigned by Ru on interface Li as specified in [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>]. Processing |
| 525 |
of the Label Request and Label Mapping messages for LDP upstream- |
| 526 |
assigned labels is as described in <a href="#section-4.1">Section 4.1</a>. If Ru receives a |
| 527 |
Label Request for an upstream-assigned label for the same P2MP FEC |
| 528 |
from multiple downstream LSRs on the LAN, <Rd1...Rdn>, it MUST send |
| 529 |
the same upstream-assigned label to each of <Rd1...Rdn>. |
| 530 |
|
| 531 |
Ru transmits the MPLS packet using the procedures defined in |
| 532 |
[<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>] and [<a href="./rfc5332" title=""MPLS Multicast Encapsulations"">RFC5332</a>]. The MPLS packet transmitted by Ru contains |
| 533 |
as the top label the context label assigned by Ru on the LAN |
| 534 |
interface, Li. The bottom label is the upstream label assigned by Ru |
| 535 |
to the LDP P2MP LSP. The top label is looked up in the context of |
| 536 |
the LAN interface (Li) by a downstream LSR on the LAN. This lookup |
| 537 |
enables the downstream LSR to determine the context-specific label |
| 538 |
space in which to look up the inner label. |
| 539 |
|
| 540 |
Note that <Rd1...Rdn> may have more than one equal-cost next hop on |
| 541 |
the LAN to reach Pr. It MAY be desirable for all of them to send the |
| 542 |
label request to the same upstream LSR and they MAY select one |
| 543 |
upstream LSR using the following procedure: |
| 544 |
|
| 545 |
1. The candidate upstream LSRs are numbered from lower to higher IP |
| 546 |
address. |
| 547 |
|
| 548 |
2. The following hash is performed: H = (Sum Opaque value) modulo N, |
| 549 |
where N is the number of candidate upstream LSRs. The Opaque |
| 550 |
value is defined in [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>] and comprises the P2MP LSP |
| 551 |
identifier. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 559 |
|
| 560 |
|
| 561 |
3. The selected upstream LSR U is the LSR that has the number H. |
| 562 |
|
| 563 |
This allows for load balancing of a set of LSPs among a set of |
| 564 |
candidate upstream LSRs, while ensuring that on a LAN interface, a |
| 565 |
single upstream LSR is selected. It is also to be noted that the |
| 566 |
procedures in this section can still be used by Rd and Ru if other |
| 567 |
LSRs on the LAN do not support upstream label assignment. Ingress |
| 568 |
replication and downstream label assignment will continue to be used |
| 569 |
for LSRs that do not support upstream label assignment. |
| 570 |
|
| 571 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 572 |
|
| 573 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. LDP TLVs</span> |
| 574 |
|
| 575 |
IANA maintains a registry of LDP TLVs at the registry "Label |
| 576 |
Distribution Protocol" in the sub-registry called "TLV Type Name |
| 577 |
Space". |
| 578 |
|
| 579 |
This document defines a new LDP Upstream Label Assignment Capability |
| 580 |
TLV (<a href="#section-3">Section 3</a>). IANA has assigned the value 0x0507 to this TLV. |
| 581 |
|
| 582 |
This document defines a new LDP Upstream-Assigned Label TLV (<a href="#section-4">Section</a> |
| 583 |
<a href="#section-4">4</a>). IANA has assigned the type value of 0x204 to this TLV. |
| 584 |
|
| 585 |
This document defines a new LDP Upstream-Assigned Label Request TLV |
| 586 |
(<a href="#section-4">Section 4</a>). IANA has assigned the type value of 0x205 to this TLV. |
| 587 |
|
| 588 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Interface Type Identifiers</span> |
| 589 |
|
| 590 |
[<a id="ref-RFC3472">RFC3472</a>] defines the LDP Interface ID IPv4 and IPv6 TLV. These top- |
| 591 |
level TLVs can carry sub-TLVs dependent on the interface type. These |
| 592 |
sub-TLVs are assigned "Interface ID Types". IANA maintains a |
| 593 |
registry of Interface ID Types for use in GMPLS in the registry |
| 594 |
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling |
| 595 |
Parameters" and sub-registry "Interface_ID Types". IANA has made the |
| 596 |
corresponding allocations from this registry as follows: |
| 597 |
|
| 598 |
- RSVP-TE P2MP LSP TLV (value 28) |
| 599 |
|
| 600 |
- LDP P2MP LSP TLV (value 29) |
| 601 |
|
| 602 |
- IP Multicast Tunnel TLV (value 30) |
| 603 |
|
| 604 |
- MPLS Context Label TLV (value 31) |
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 618 |
|
| 619 |
The security considerations discussed in [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>], [<a href="./rfc5331" title=""MPLS Upstream Label Assignment and Context-Specific Label Space"">RFC5331</a>], and |
| 620 |
[<a href="./rfc5332" title=""MPLS Multicast Encapsulations"">RFC5332</a>] apply to this document. |
| 621 |
|
| 622 |
More detailed discussion of security issues that are relevant in the |
| 623 |
context of MPLS and GMPLS, including security threats, related |
| 624 |
defensive techniques, and the mechanisms for detection and reporting, |
| 625 |
are discussed in "Security Framework for MPLS and GMPLS Networks" |
| 626 |
[<a href="./rfc5920" title=""Security Framework for MPLS and GMPLS Networks"">RFC5920</a>]. |
| 627 |
|
| 628 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span> |
| 629 |
|
| 630 |
Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei |
| 631 |
and Thomas Morin for their comments. The hashing algorithm used on |
| 632 |
LAN interfaces is taken from [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>]. Thanks to Loa Andersson, |
| 633 |
Adrian Farrel, and Eric Rosen for their comments and review. |
| 634 |
|
| 635 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span> |
| 636 |
|
| 637 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span> |
| 638 |
|
| 639 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 640 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 641 |
|
| 642 |
[<a id="ref-RFC5036">RFC5036</a>] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., |
| 643 |
"LDP Specification", <a href="./rfc5036">RFC 5036</a>, October 2007. |
| 644 |
|
| 645 |
[<a id="ref-RFC4875">RFC4875</a>] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. Yasukawa, |
| 646 |
Ed., "Extensions to Resource Reservation Protocol - Traffic |
| 647 |
Engineering (RSVP-TE) for Point-to-Multipoint TE Label |
| 648 |
Switched Paths (LSPs)", <a href="./rfc4875">RFC 4875</a>, May 2007. |
| 649 |
|
| 650 |
[<a id="ref-RFC5331">RFC5331</a>] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream |
| 651 |
Label Assignment and Context-Specific Label Space", <a href="./rfc5331">RFC</a> |
| 652 |
<a href="./rfc5331">5331</a>, August 2008. |
| 653 |
|
| 654 |
[<a id="ref-RFC5332">RFC5332</a>] Eckert, T., Rosen, E., Ed., Aggarwal, R., and Y. Rekhter, |
| 655 |
"MPLS Multicast Encapsulations", <a href="./rfc5332">RFC 5332</a>, August 2008. |
| 656 |
|
| 657 |
[<a id="ref-RFC5561">RFC5561</a>] Thomas, B., Raza, K., Aggarwal, S., Aggarwal, R., and JL. |
| 658 |
Le Roux, "LDP Capabilities", <a href="./rfc5561">RFC 5561</a>, July 2009. |
| 659 |
|
| 660 |
[<a id="ref-RFC6388">RFC6388</a>] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. |
| 661 |
Thomas, "Label Distribution Protocol Extensions for Point- |
| 662 |
to-Multipoint and Multipoint-to-Multipoint Label Switched |
| 663 |
Paths", <a href="./rfc6388">RFC 6388</a>, November 2011. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Aggarwal & Le Roux 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="./rfc6389">RFC 6389</a> MPLS Upstream Label Assignment for LDP November 2011</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span> |
| 674 |
|
| 675 |
[<a id="ref-RFC3032">RFC3032</a>] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., |
| 676 |
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack |
| 677 |
Encoding", <a href="./rfc3032">RFC 3032</a>, January 2001. |
| 678 |
|
| 679 |
[<a id="ref-RFC3472">RFC3472</a>] Ashwood-Smith, P., Ed., and L. Berger, Ed., "Generalized |
| 680 |
Multi-Protocol Label Switching (GMPLS) Signaling |
| 681 |
Constraint-based Routed Label Distribution Protocol |
| 682 |
(CR-LDP) Extensions", <a href="./rfc3472">RFC 3472</a>, January 2003. |
| 683 |
|
| 684 |
[<a id="ref-RFC5920">RFC5920</a>] Fang, L., Ed., "Security Framework for MPLS and GMPLS |
| 685 |
Networks", <a href="./rfc5920">RFC 5920</a>, July 2010. |
| 686 |
|
| 687 |
Author's Address |
| 688 |
|
| 689 |
Rahul Aggarwal |
| 690 |
Juniper Networks |
| 691 |
1194 North Mathilda Ave. |
| 692 |
Sunnyvale, CA 94089 |
| 693 |
Phone: +1-408-936-2720 |
| 694 |
EMail: [email protected] |
| 695 |
|
| 696 |
|
| 697 |
Jean-Louis Le Roux |
| 698 |
France Telecom |
| 699 |
2, avenue Pierre-Marzin |
| 700 |
22307 Lannion Cedex |
| 701 |
France |
| 702 |
EMail: [email protected] |
| 703 |
|
| 704 |
|
| 705 |
|
| 706 |
|
| 707 |
|
| 708 |
|
| 709 |
|
| 710 |
|
| 711 |
|
| 712 |
|
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
Aggarwal & Le Roux Standards Track [Page 13] |
| 725 |
</pre> |