Debian Codegraph @

rfc7439.html

raw
1 <pre>Internet Engineering Task Force (IETF) W. George, Ed.
2 Request for Comments: 7439 Time Warner Cable
3 Category: Informational C. Pignataro, Ed.
4 ISSN: 2070-1721 Cisco
5 January 2015
6
7
8 <span class="h1">Gap Analysis for Operating IPv6-Only MPLS Networks</span>
9
10 Abstract
11
12 This document reviews the Multiprotocol Label Switching (MPLS)
13 protocol suite in the context of IPv6 and identifies gaps that must
14 be addressed in order to allow MPLS-related protocols and
15 applications to be used with IPv6-only networks. This document is
16 intended to focus on gaps in the standards defining the MPLS suite,
17 and is not intended to highlight particular vendor implementations
18 (or lack thereof) in the context of IPv6-only MPLS functionality.
19
20 In the data plane, MPLS fully supports IPv6, and MPLS labeled packets
21 can be carried over IPv6 packets in a variety of encapsulations.
22 However, support for IPv6 among MPLS control-plane protocols, MPLS
23 applications, MPLS Operations, Administration, and Maintenance (OAM),
24 and MIB modules is mixed, with some protocols having major gaps. For
25 most major gaps, work is in progress to upgrade the relevant
26 protocols.
27
28 Status of This Memo
29
30 This document is not an Internet Standards Track specification; it is
31 published for informational purposes.
32
33 This document is a product of the Internet Engineering Task Force
34 (IETF). It represents the consensus of the IETF community. It has
35 received public review and has been approved for publication by the
36 Internet Engineering Steering Group (IESG). Not all documents
37 approved by the IESG are a candidate for any level of Internet
38 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
39
40 Information about the current status of this document, any errata,
41 and how to provide feedback on it may be obtained at
42 <a href="http://www.rfc-editor.org/info/rfc7439">http://www.rfc-editor.org/info/rfc7439</a>.
43
44
45
46
47
48
49
50
51
52 <span class="grey">George &amp; Pignataro Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 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">George &amp; Pignataro Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 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>. Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
117 <a href="#section-3">3</a>. Gap Analysis . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
118 <a href="#section-3.1">3.1</a>. MPLS Data Plane . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
119 <a href="#section-3.2">3.2</a>. MPLS Control Plane . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
120 <a href="#section-3.2.1">3.2.1</a>. Label Distribution Protocol (LDP) . . . . . . . . . . <a href="#page-6">6</a>
121 <a href="#section-3.2.2">3.2.2</a>. Multipoint LDP (mLDP) . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
122 <a href="#section-3.2.3">3.2.3</a>. RSVP - Traffic Engineering (RSVP-TE) . . . . . . . . <a href="#page-7">7</a>
123 <a href="#section-3.2.3.1">3.2.3.1</a>. Interior Gateway Protocol (IGP) . . . . . . . . . <a href="#page-8">8</a>
124 <a href="#section-3.2.3.2">3.2.3.2</a>. RSVP-TE Point-to-Multipoint (P2MP) . . . . . . . <a href="#page-8">8</a>
125 <a href="#section-3.2.3.3">3.2.3.3</a>. RSVP-TE Fast Reroute (FRR) . . . . . . . . . . . <a href="#page-8">8</a>
126 <a href="#section-3.2.4">3.2.4</a>. Path Computation Element (PCE) . . . . . . . . . . . <a href="#page-8">8</a>
127 <a href="#section-3.2.5">3.2.5</a>. Border Gateway Protocol (BGP) . . . . . . . . . . . . <a href="#page-9">9</a>
128 3.2.6. Generalized Multi-Protocol Label Switching (GMPLS) . 9
129 <a href="#section-3.3">3.3</a>. MPLS Applications . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
130 <a href="#section-3.3.1">3.3.1</a>. Layer 2 Virtual Private Network (L2VPN) . . . . . . . <a href="#page-9">9</a>
131 <a href="#section-3.3.1.1">3.3.1.1</a>. Ethernet VPN (EVPN) . . . . . . . . . . . . . . . <a href="#page-10">10</a>
132 <a href="#section-3.3.2">3.3.2</a>. Layer 3 Virtual Private Network (L3VPN) . . . . . . . <a href="#page-10">10</a>
133 3.3.2.1. IPv6 Provider Edge/IPv4 Provider Edge (6PE/4PE) . 11
134 3.3.2.2. IPv6 Virtual Private Extension/IPv4 Virtual
135 Private Extension (6VPE/4VPE) . . . . . . . . . . <a href="#page-11">11</a>
136 3.3.2.3. BGP Encapsulation Subsequent Address Family
137 Identifier (SAFI) . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
138 <a href="#section-3.3.2.4">3.3.2.4</a>. Multicast in MPLS/BGP IP VPN (MVPN) . . . . . . . <a href="#page-12">12</a>
139 <a href="#section-3.3.3">3.3.3</a>. MPLS Transport Profile (MPLS-TP) . . . . . . . . . . <a href="#page-13">13</a>
140 3.4. MPLS Operations, Administration, and Maintenance (MPLS
141 OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
142 <a href="#section-3.4.1">3.4.1</a>. Extended ICMP . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
143 <a href="#section-3.4.2">3.4.2</a>. Label Switched Path Ping (LSP Ping) . . . . . . . . . <a href="#page-15">15</a>
144 <a href="#section-3.4.3">3.4.3</a>. Bidirectional Forwarding Detection (BFD) . . . . . . <a href="#page-16">16</a>
145 <a href="#section-3.4.4">3.4.4</a>. Pseudowire OAM . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
146 <a href="#section-3.4.5">3.4.5</a>. MPLS Transport Profile (MPLS-TP) OAM . . . . . . . . <a href="#page-16">16</a>
147 <a href="#section-3.5">3.5</a>. MIB Modules . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
148 <a href="#section-4">4</a>. Gap Summary . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
149 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
150 <a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
151 <a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
152 <a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
153 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
154 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
155 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
156
157
158
159
160
161
162
163
164 <span class="grey">George &amp; Pignataro Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
170
171 IPv6 [<a href="./rfc2460" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">RFC2460</a>] is an integral part of modern network deployments. At
172 the time when this document was written, the majority of these IPv6
173 deployments were using dual-stack implementations, where IPv4 and
174 IPv6 are supported equally on many or all of the network nodes, and
175 single-stack primarily referred to IPv4-only devices. Dual-stack
176 deployments provide a useful margin for protocols and features that
177 are not currently capable of operating solely over IPv6, because they
178 can continue using IPv4 as necessary. However, as IPv6 deployment
179 and usage becomes more pervasive, and IPv4 exhaustion begins driving
180 changes in address consumption behaviors, there is an increasing
181 likelihood that many networks will need to start operating some or
182 all of their network nodes either as primarily IPv6 (most functions
183 use IPv6, a few legacy features use IPv4), or as IPv6-only (no IPv4
184 provisioned on the device). This transition toward IPv6-only
185 operation exposes any gaps where features, protocols, or
186 implementations are still reliant on IPv4 for proper function. To
187 that end, and in the spirit of the recommendation in <a href="./rfc6540">RFC 6540</a>
188 [<a href="./rfc6540" title="&quot;IPv6 Support Required for All IP-Capable Nodes&quot;">RFC6540</a>] that implementations need to stop requiring IPv4 for proper
189 and complete function, this document reviews the MPLS protocol suite
190 in the context of IPv6 and identifies gaps that must be addressed in
191 order to allow MPLS-related protocols and applications to be used
192 with IPv6-only networks and networks that are primarily IPv6
193 (hereafter referred to as IPv6-primary). This document is intended
194 to focus on gaps in the standards defining the MPLS suite, and not to
195 highlight particular vendor implementations (or lack thereof) in the
196 context of IPv6-only MPLS functionality.
197
198 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Use Case</span>
199
200 This section discusses some drivers for ensuring that MPLS completely
201 supports IPv6-only operation. It is not intended to be a
202 comprehensive discussion of all potential use cases, but rather a
203 discussion of one use case to provide context and justification to
204 undertake such a gap analysis.
205
206 IP convergence is continuing to drive new classes of devices to begin
207 communicating via IP. Examples of such devices could include set-top
208 boxes for IP video distribution, cell tower electronics (macro or
209 micro cells), infrastructure Wi-Fi access points, and devices for
210 machine-to-machine (M2M) or Internet of Things (IoT) applications.
211 In some cases, these classes of devices represent a very large
212 deployment base, on the order of thousands or even millions of
213 devices network-wide. The scale of these networks, coupled with the
214 increasingly overlapping use of <a href="./rfc1918">RFC 1918</a> [<a href="./rfc1918" title="&quot;Address Allocation for Private Internets&quot;">RFC1918</a>] address space
215 within the average network and the lack of globally routable IPv4
216 space available for long-term growth, begins to drive the need for
217
218
219
220 <span class="grey">George &amp; Pignataro Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
223
224
225 many of the endpoints in this network to be managed solely via IPv6.
226 Even if these devices are carrying some IPv4 user data, it is often
227 encapsulated in another protocol such that the communication between
228 the endpoint and its upstream devices can be IPv6-only without
229 impacting support for IPv4 on user data. As the number of devices to
230 manage increases, the operator is compelled to move to IPv6.
231 Depending on the MPLS features required, it is plausible to assume
232 that the (existing) MPLS network will need to be extended to these
233 IPv6-only devices.
234
235 Additionally, as the impact of IPv4 exhaustion becomes more acute,
236 more and more aggressive IPv4 address reclamation measures will be
237 justified. Many networks are likely to focus on preserving their
238 remaining IPv4 addresses for revenue-generating customers so that
239 legacy support for IPv4 can be maintained as long as necessary. As a
240 result, it may be appropriate for some or all of the network
241 infrastructure, including MPLS Label Switching Routers (LSRs) and
242 Label Edge Routers (LERs), to have its IPv4 addresses reclaimed and
243 transition toward IPv6-only operation.
244
245 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Gap Analysis</span>
246
247 This gap analysis aims to answer the question of what fails when one
248 attempts to use MPLS features on a network of IPv6-only devices. The
249 baseline assumption for this analysis is that some endpoints, as well
250 as Label Switching Routers (Provider Edge (PE) and Provider (P)
251 routers), only have IPv6 transport available and need to support the
252 full suite of MPLS features defined as of the time of this document's
253 writing at parity with the support on an IPv4 network. This is
254 necessary whether they are enabled via the Label Distribution
255 Protocol (LDP) [<a href="./rfc5036" title="&quot;LDP Specification&quot;">RFC5036</a>], RSVP - Traffic Engineering (RSVP-TE)
256 [<a href="./rfc3209" title="&quot;RSVP-TE: Extensions to RSVP for LSP Tunnels&quot;">RFC3209</a>], or Border Gateway Protocol (BGP) [<a href="./rfc3107" title="&quot;Carrying Label Information in BGP-4&quot;">RFC3107</a>], and whether
257 they are encapsulated in MPLS [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>], IP [<a href="./rfc4023" title="&quot;Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)&quot;">RFC4023</a>], Generic
258 Routing Encapsulation (GRE) [<a href="./rfc4023" title="&quot;Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)&quot;">RFC4023</a>], or Layer 2 Tunneling Protocol
259 Version 3 (L2TPv3) [<a href="./rfc4817" title="&quot;Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3&quot;">RFC4817</a>]. It is important when evaluating these
260 gaps to distinguish between user data and control-plane data, because
261 while this document is focused on IPv6-only operation, it is quite
262 likely that some amount of the user payload data being carried in the
263 IPv6-only MPLS network will still be IPv4.
264
265 A note about terminology: Gaps identified by this document are
266 characterized as "Major" or "Minor". Major gaps refer to significant
267 changes necessary in one or more standards to address the gap due to
268 existing standards language having either missing functionality for
269 IPv6-only operation or explicit language requiring the use of IPv4
270 with no IPv6 alternatives defined. Minor gaps refer to changes
271 necessary primarily to clarify existing standards language. Usually
272
273
274
275
276 <span class="grey">George &amp; Pignataro Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
279
280
281 these changes are needed in order to explicitly codify IPv6 support
282 in places where it is either implicit or omitted today, but the
283 omission is unlikely to prevent IPv6-only operation.
284
285 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. MPLS Data Plane</span>
286
287 MPLS labeled packets can be transmitted over a variety of data links
288 [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>], and MPLS labeled packets can also be encapsulated over IP.
289 The encapsulations of MPLS in IP and GRE, as well as MPLS over
290 L2TPv3, support IPv6. See <a href="./rfc4023#section-3">Section&nbsp;3 of RFC 4023</a> [<a href="./rfc4023" title="&quot;Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)&quot;">RFC4023</a>] and
291 <a href="./rfc4817#section-2">Section&nbsp;2 of RFC 4817</a> [<a href="./rfc4817" title="&quot;Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3&quot;">RFC4817</a>], respectively.
292
293 Gap: None.
294
295 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. MPLS Control Plane</span>
296
297 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Label Distribution Protocol (LDP)</span>
298
299 The Label Distribution Protocol (LDP) [<a href="./rfc5036" title="&quot;LDP Specification&quot;">RFC5036</a>] defines a set of
300 procedures for distribution of labels between Label Switching Routers
301 that can use the labels for forwarding traffic. While LDP was
302 designed to use an IPv4 or dual-stack IP network, it has a number of
303 deficiencies that prevent it from working in an IPv6-only network.
304 LDP-IPv6 [<a href="#ref-LDP-IPv6">LDP-IPv6</a>] highlights some of the deficiencies when LDP is
305 enabled in IPv6-only or dual-stack networks and specifies appropriate
306 protocol changes. These deficiencies are related to Label Switched
307 Path (LSP) mapping, LDP identifiers, LDP discovery, LDP session
308 establishment, next-hop address, and LDP Time To Live (TTL) security
309 [<a href="./rfc5082" title="&quot;The Generalized TTL Security Mechanism (GTSM)&quot;">RFC5082</a>] [<a href="./rfc6720" title="&quot;The Generalized TTL Security Mechanism (GTSM) for the Label Distribution Protocol (LDP)&quot;">RFC6720</a>].
310
311 Gap: Major; update to <a href="./rfc5036">RFC 5036</a> in progress via [<a href="#ref-LDP-IPv6">LDP-IPv6</a>], which
312 should close this gap.
313
314 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Multipoint LDP (mLDP)</span>
315
316 Multipoint LDP (mLDP) is a set of extensions to LDP for setting up
317 Point-to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP) LSPs.
318 These extensions are specified in <a href="./rfc6388">RFC 6388</a> [<a href="./rfc6388" title="&quot;Label Distribution Protocol Extensions for Point-to- Multipoint and Multipoint-to-Multipoint Label Switched Paths&quot;">RFC6388</a>]. In terms of
319 IPv6-only gap analysis, mLDP has two identified areas of interest:
320
321 1. LDP Control Plane: Since mLDP uses the LDP control plane to
322 discover and establish sessions with the peer, it shares the same
323 gaps as LDP (<a href="#section-3.2.1">Section 3.2.1</a>) with regards to control plane
324 (discovery, transport, and session establishment) in an IPv6-only
325 network.
326
327
328
329
330
331
332 <span class="grey">George &amp; Pignataro Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
335
336
337 2. Multipoint (MP) Forwarding Equivalence Class (FEC) Root Address:
338 mLDP defines its own MP FECs and rules, different from LDP, to
339 map MP LSPs. An mLDP MP FEC contains a Root Address field that
340 is an IP address in IP networks. The current specification
341 allows specifying the root address according to the Address
342 Family Identifier (AFI), and hence covers both IPv4 or IPv6 root
343 addresses, requiring no extension to support IPv6-only MP LSPs.
344 The root address is used by each LSR participating in an MP LSP
345 setup such that root address reachability is resolved by doing a
346 table lookup against the root address to find corresponding
347 upstream neighbor(s). This will pose a problem if an MP LSP
348 traverses IPv4-only and IPv6-only nodes in a dual-stack network
349 on the way to the root node.
350
351 For example, consider following setup, where R1/R6 are IPv4-only, R3/
352 R4 are IPv6-only, and R2/R5 are dual-stack LSRs:
353
354 ( IPv4-only ) ( IPv6-only ) ( IPv4-only )
355 R1 -- R2 -- R3 -- R4 -- R5 -- R6
356 Leaf Root
357
358 Assume R1 to be a leaf node for a P2MP LSP rooted at R6 (root node).
359 R1 uses R6's IPv4 address as the root address in MP FEC. As the MP
360 LSP signaling proceeds from R1 to R6, the MP LSP setup will fail on
361 the first IPv6-only transit/branch LSRs (R3) when trying to find IPv4
362 root address reachability. <a href="./rfc6512">RFC 6512</a> [<a href="./rfc6512" title="&quot;Using Multipoint LDP When the Backbone Has No Route to the Root&quot;">RFC6512</a>] defines a recursive-
363 FEC solution and procedures for mLDP when the backbone (transit/
364 branch) LSRs have no route to the root. The proposed solution is
365 defined for a BGP-free core in a VPN environment, but a similar
366 concept can be used/extended to solve the above issue of the
367 IPv6-only backbone receiving an MP FEC element with an IPv4 address.
368 The solution will require a border LSR (the one that is sitting on
369 the border of an IPv4/IPv6 island (namely, R2 and R5 in this
370 example)) to translate an IPv4 root address to an equivalent IPv6
371 address (and vice versa) through procedures similar to <a href="./rfc6512">RFC 6512</a>.
372
373 Gap: Major; update in progress for LDP via [<a href="#ref-LDP-IPv6">LDP-IPv6</a>], may need
374 additional updates to <a href="./rfc6512">RFC 6512</a>.
375
376 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. RSVP - Traffic Engineering (RSVP-TE)</span>
377
378 RSVP-TE [<a href="./rfc3209" title="&quot;RSVP-TE: Extensions to RSVP for LSP Tunnels&quot;">RFC3209</a>] defines a set of procedures and enhancements to
379 establish LSP tunnels that can be automatically routed away from
380 network failures, congestion, and bottlenecks. RSVP-TE allows
381 establishing an LSP for an IPv4 or IPv6 prefix, thanks to its
382 LSP_TUNNEL_IPv6 object and subobjects.
383
384 Gap: None.
385
386
387
388 <span class="grey">George &amp; Pignataro Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
391
392
393 <span class="h5"><a class="selflink" id="section-3.2.3.1" href="#section-3.2.3.1">3.2.3.1</a>. Interior Gateway Protocol (IGP)</span>
394
395 <a href="./rfc3630">RFC 3630</a> [<a href="./rfc3630" title="&quot;Traffic Engineering (TE) Extensions to OSPF Version 2&quot;">RFC3630</a>] specifies a method of adding traffic engineering
396 capabilities to OSPF Version 2. New TLVs and sub-TLVs were added in
397 <a href="./rfc5329">RFC 5329</a> [<a href="./rfc5329" title="&quot;Traffic Engineering Extensions to OSPF Version 3&quot;">RFC5329</a>] to extend TE capabilities to IPv6 networks in OSPF
398 Version 3.
399
400 <a href="./rfc5305">RFC 5305</a> [<a href="./rfc5305" title="&quot;IS-IS Extensions for Traffic Engineering&quot;">RFC5305</a>] specifies a method of adding traffic engineering
401 capabilities to IS-IS. New TLVs and sub-TLVs were added in <a href="./rfc6119">RFC 6119</a>
402 [<a href="./rfc6119" title="&quot;IPv6 Traffic Engineering in IS-IS&quot;">RFC6119</a>] to extend TE capabilities to IPv6 networks.
403
404 Gap: None.
405
406 <span class="h5"><a class="selflink" id="section-3.2.3.2" href="#section-3.2.3.2">3.2.3.2</a>. RSVP-TE Point-to-Multipoint (P2MP)</span>
407
408 <a href="./rfc4875">RFC 4875</a> [<a href="./rfc4875" title="&quot;Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)&quot;">RFC4875</a>] describes extensions to RSVP-TE for the setup of
409 Point-to-Multipoint (P2MP) LSPs in MPLS and Generalized MPLS (GMPLS)
410 with support for both IPv4 and IPv6.
411
412 Gap: None.
413
414 <span class="h5"><a class="selflink" id="section-3.2.3.3" href="#section-3.2.3.3">3.2.3.3</a>. RSVP-TE Fast Reroute (FRR)</span>
415
416 <a href="./rfc4090">RFC 4090</a> [<a href="./rfc4090" title="&quot;Fast Reroute Extensions to RSVP-TE for LSP Tunnels&quot;">RFC4090</a>] specifies Fast Reroute (FRR) mechanisms to
417 establish backup LSP tunnels for local repair supporting both IPv4
418 and IPv6 networks. Further, [<a href="./rfc5286" title="&quot;Basic Specification for IP Fast Reroute: Loop-Free Alternates&quot;">RFC5286</a>] describes the use of loop-free
419 alternates to provide local protection for unicast traffic in pure IP
420 and MPLS networks in the event of a single failure, whether link,
421 node, or shared risk link group (SRLG) for both IPv4 and IPv6.
422
423 Gap: None.
424
425 <span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Path Computation Element (PCE)</span>
426
427 The Path Computation Element (PCE) defined in <a href="./rfc4655">RFC 4655</a> [<a href="./rfc4655" title="&quot;A Path Computation Element (PCE)-Based Architecture&quot;">RFC4655</a>] is
428 an entity that is capable of computing a network path or route based
429 on a network graph and applying computational constraints. A Path
430 Computation Client (PCC) may make requests to a PCE for paths to be
431 computed. The PCE Communication Protocol (PCEP) is designed as a
432 communication protocol between PCCs and PCEs for path computations
433 and is defined in <a href="./rfc5440">RFC 5440</a> [<a href="./rfc5440" title="&quot;Path Computation Element (PCE) Communication Protocol (PCEP)&quot;">RFC5440</a>].
434
435 The PCEP specification [<a href="./rfc5440" title="&quot;Path Computation Element (PCE) Communication Protocol (PCEP)&quot;">RFC5440</a>] is defined for both IPv4 and IPv6
436 with support for PCE discovery via an IGP (OSPF [<a href="./rfc5088" title="&quot;OSPF Protocol Extensions for Path Computation Element (PCE) Discovery&quot;">RFC5088</a>] or IS-IS
437 [<a href="./rfc5089" title="&quot;IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery&quot;">RFC5089</a>]) using both IPv4 and IPv6 addresses. Note that PCEP uses
438 identical encoding of subobjects, as in RSVP-TE defined in <a href="./rfc3209">RFC 3209</a>
439 [<a href="./rfc3209" title="&quot;RSVP-TE: Extensions to RSVP for LSP Tunnels&quot;">RFC3209</a>] that supports both IPv4 and IPv6.
440
441
442
443
444 <span class="grey">George &amp; Pignataro Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
447
448
449 The extensions to PCEP to support confidentiality [<a href="./rfc5520" title="&quot;Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism&quot;">RFC5520</a>], route
450 exclusions [<a href="./rfc5521" title="&quot;Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions&quot;">RFC5521</a>], monitoring [<a href="./rfc5886" title="&quot;A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture&quot;">RFC5886</a>], and P2MP TE LSPs
451 [<a href="./rfc6006" title="&quot;Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths&quot;">RFC6006</a>] have support for both IPv4 and IPv6.
452
453 Gap: None.
454
455 <span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a>. Border Gateway Protocol (BGP)</span>
456
457 <a href="./rfc3107">RFC 3107</a> [<a href="./rfc3107" title="&quot;Carrying Label Information in BGP-4&quot;">RFC3107</a>] specifies a set of BGP protocol procedures for
458 distributing the labels (for prefixes corresponding to any address
459 family) between label switch routers so that they can use the labels
460 for forwarding the traffic. <a href="./rfc3107">RFC 3107</a> allows BGP to distribute the
461 label for IPv4 or IPv6 prefix in an IPv6-only network.
462
463 Gap: None.
464
465 <span class="h4"><a class="selflink" id="section-3.2.6" href="#section-3.2.6">3.2.6</a>. Generalized Multi-Protocol Label Switching (GMPLS)</span>
466
467 The Generalized Multi-Protocol Label Switching (GMPLS) specification
468 includes signaling functional extensions [<a href="./rfc3471" title="&quot;Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description&quot;">RFC3471</a>] and RSVP-TE
469 extensions [<a href="./rfc3473" title="&quot;Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions&quot;">RFC3473</a>]. The gap analysis in <a href="#section-3.2.3">Section 3.2.3</a> applies to
470 these.
471
472 <a href="./rfc4558">RFC 4558</a> [<a href="./rfc4558" title="&quot;Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement&quot;">RFC4558</a>] specifies Node-ID Based RSVP Hello Messages with
473 capability for both IPv4 and IPv6. <a href="./rfc4990">RFC 4990</a> [<a href="./rfc4990" title="&quot;Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks&quot;">RFC4990</a>] clarifies the
474 use of IPv6 addresses in GMPLS networks including handling in the MIB
475 modules.
476
477 The second paragraph of <a href="./rfc6370#section-5.3">Section&nbsp;5.3 of RFC 6370</a> [<a href="./rfc6370" title="&quot;MPLS Transport Profile (MPLS-TP) Identifiers&quot;">RFC6370</a>] describes
478 the mapping from an MPLS Transport Profile (MPLS-TP) LSP_ID to RSVP-
479 TE with an assumption that Node_IDs are derived from valid IPv4
480 addresses. This assumption fails in an IPv6-only network, given that
481 there would not be any IPv4 addresses.
482
483 Gap: Minor; <a href="./rfc6370#section-5.3">Section&nbsp;5.3 of RFC 6370</a> [<a href="./rfc6370" title="&quot;MPLS Transport Profile (MPLS-TP) Identifiers&quot;">RFC6370</a>] needs to be updated.
484
485 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. MPLS Applications</span>
486
487 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Layer 2 Virtual Private Network (L2VPN)</span>
488
489 L2VPN [<a href="./rfc4664" title="&quot;Framework for Layer 2 Virtual Private Networks (L2VPNs)&quot;">RFC4664</a>] specifies two fundamentally different kinds of Layer
490 2 VPN services that a service provider could offer to a customer:
491 Virtual Private Wire Service (VPWS) and Virtual Private LAN Service
492 (VPLS). <a href="./rfc4447">RFC 4447</a> [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>] and <a href="./rfc4762">RFC 4762</a> [<a href="./rfc4762" title="&quot;Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling&quot;">RFC4762</a>] specify the LDP
493 protocol changes to instantiate VPWS and VPLS services, respectively,
494 in an MPLS network using LDP as the signaling protocol. This is
495 complemented by <a href="./rfc6074">RFC 6074</a> [<a href="./rfc6074" title="&quot;Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)&quot;">RFC6074</a>], which specifies a set of
496 procedures for instantiating L2VPNs (e.g., VPWS, VPLS) using BGP as a
497
498
499
500 <span class="grey">George &amp; Pignataro Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
503
504
505 discovery protocol and LDP, as well as L2TPv3, as a signaling
506 protocol. <a href="./rfc4761">RFC 4761</a> [<a href="./rfc4761" title="&quot;Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling&quot;">RFC4761</a>] and <a href="./rfc6624">RFC 6624</a> [<a href="./rfc6624" title="&quot;Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling&quot;">RFC6624</a>] specify BGP
507 protocol changes to instantiate VPLS and VPWS services in an MPLS
508 network, using BGP for both discovery and signaling.
509
510 In an IPv6-only MPLS network, use of L2VPN represents a connection of
511 Layer 2 islands over an IPv6 MPLS core, and very few changes are
512 necessary to support operation over an IPv6-only network. The L2VPN
513 signaling protocol is either BGP or LDP in an MPLS network, and both
514 can run directly over IPv6 core infrastructure as well as IPv6 edge
515 devices. <a href="./rfc6074">RFC 6074</a> [<a href="./rfc6074" title="&quot;Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)&quot;">RFC6074</a>] is the only RFC that appears to have a
516 gap for IPv6-only operation. In its discovery procedures (Sections
517 3.2.2 and 6 of <a href="./rfc6074">RFC 6074</a> [<a href="./rfc6074" title="&quot;Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)&quot;">RFC6074</a>]), it suggests encoding PE IP
518 addresses in the Virtual Switching Instance ID (VSI-ID), which is
519 encoded in Network Layer Reachability Information (NLRI) and should
520 not exceed 12 bytes (to differentiate its AFI/SAFI (Subsequent
521 Address Family Identifier) encoding from <a href="./rfc4761">RFC 4761</a>). This means that
522 a PE IP address cannot be an IPv6 address. Also, in its signaling
523 procedures (<a href="./rfc6074#section-3.2.3">Section&nbsp;3.2.3 of RFC 6074</a> [<a href="./rfc6074" title="&quot;Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)&quot;">RFC6074</a>]), it suggests
524 encoding PE_addr in the Source Attachment Individual Identifier
525 (SAII) and the Target Attachment Individual Identifier (TAII), which
526 are limited to 32 bits (AII Type=1) at the moment.
527
528 <a href="./rfc6073">RFC 6073</a> [<a href="./rfc6073" title="&quot;Segmented Pseudowire&quot;">RFC6073</a>] defines the new LDP Pseudowire (PW) Switching
529 Point PE TLV, which supports IPv4 and IPv6.
530
531 Gap: Minor; <a href="./rfc6074">RFC 6074</a> needs to be updated.
532
533 <span class="h5"><a class="selflink" id="section-3.3.1.1" href="#section-3.3.1.1">3.3.1.1</a>. Ethernet VPN (EVPN)</span>
534
535 Ethernet VPN [<a href="#ref-EVPN" title="&quot;BGP MPLS Based Ethernet VPN&quot;">EVPN</a>] defines a method for using BGP MPLS-based
536 Ethernet VPNs. Because it can use functions in LDP and mLDP, as well
537 as Multicast VPLS [<a href="./rfc7117" title="&quot;Multicast in Virtual Private LAN Service (VPLS)&quot;">RFC7117</a>], it inherits LDP gaps previously
538 identified in <a href="#section-3.2.1">Section 3.2.1</a>. Once those gaps are resolved, it should
539 function properly on IPv6-only networks as defined.
540
541 Gap: Major for LDP; update to <a href="./rfc5036">RFC 5036</a> in progress via [<a href="#ref-LDP-IPv6">LDP-IPv6</a>]
542 that should close this gap (see <a href="#section-3.2.1">Section 3.2.1</a>).
543
544 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Layer 3 Virtual Private Network (L3VPN)</span>
545
546 <a href="./rfc4364">RFC 4364</a> [<a href="./rfc4364" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">RFC4364</a>] defines a method by which a Service Provider may
547 use an IP backbone to provide IP VPNs for its customers. The
548 following use cases arise in the context of this gap analysis:
549
550 1. Connecting IPv6 islands over IPv6-only MPLS network
551
552 2. Connecting IPv4 islands over IPv6-only MPLS network
553
554
555
556 <span class="grey">George &amp; Pignataro Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
559
560
561 Both use cases require mapping an IP packet to an IPv6-signaled LSP.
562 <a href="./rfc4364">RFC 4364</a> defines Layer 3 Virtual Private Networks (L3VPNs) for
563 IPv4-only and has references to 32-bit BGP next-hop addresses. <a href="./rfc4659">RFC</a>
564 <a href="./rfc4659">4659</a> [<a href="./rfc4659" title="&quot;BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN&quot;">RFC4659</a>] adds support for IPv6 on L3VPNs, including 128-bit BGP
565 next-hop addresses, and discusses operation whether IPv6 is the
566 payload or the underlying transport address family. However, <a href="./rfc4659">RFC</a>
567 <a href="./rfc4659">4659</a> does not formally update <a href="./rfc4364">RFC 4364</a>, and thus an implementer may
568 miss this additional set of standards unless it is explicitly
569 identified independently of the base functionality defined in <a href="./rfc4364">RFC</a>
570 <a href="./rfc4364">4364</a>. Further, <a href="./rfc4659#section-1">Section&nbsp;1 of RFC 4659</a> explicitly identifies use case
571 2 as out of scope for the document.
572
573 The authors do not believe that there are any additional issues
574 encountered when using L2TPv3, RSVP, or GRE (instead of MPLS) as
575 transport on an IPv6-only network.
576
577 Gap: Major; <a href="./rfc4659">RFC 4659</a> needs to be updated to explicitly cover use case
578 2 (discussed in further detail below)
579
580 <span class="h5"><a class="selflink" id="section-3.3.2.1" href="#section-3.3.2.1">3.3.2.1</a>. IPv6 Provider Edge/IPv4 Provider Edge (6PE/4PE)</span>
581
582 <a href="./rfc4798">RFC 4798</a> [<a href="./rfc4798" title="&quot;Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)&quot;">RFC4798</a>] defines IPv6 Provider Edge (6PE), which defines
583 how to interconnect IPv6 islands over a MPLS-enabled IPv4 cloud.
584 However, use case 2 is doing the opposite, and thus could also be
585 referred to as IPv4 Provider Edge (4PE). The method to support this
586 use case is not defined explicitly. To support it, IPv4 edge devices
587 need to be able to map IPv4 traffic to MPLS IPv6 core LSPs. Also,
588 the core switches may not understand IPv4 at all, but in some cases
589 they may need to be able to exchange Labeled IPv4 routes from one
590 Autonomous System (AS) to a neighboring AS.
591
592 Gap: Major; <a href="./rfc4798">RFC 4798</a> covers only the "6PE" case. Use case 2 is
593 currently not specified in an RFC.
594
595 <span class="h5"><a class="selflink" id="section-3.3.2.2" href="#section-3.3.2.2">3.3.2.2</a>. IPv6 Virtual Private Extension/IPv4 Virtual Private Extension</span>
596 (6VPE/4VPE)
597
598 <a href="./rfc4659">RFC 4659</a> [<a href="./rfc4659" title="&quot;BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN&quot;">RFC4659</a>] defines IPv6 Virtual Private Network Extension
599 (6VPE), a method by which a Service Provider may use its packet-
600 switched backbone to provide Virtual Private Network (VPN) services
601 for its IPv6 customers. It allows the core network to be MPLS IPv4
602 or MPLS IPv6, thus addressing use case 1 above. <a href="./rfc4364">RFC 4364</a> should work
603 as defined for use case 2 above, which could also be referred to as
604 IPv4 Virtual Private Extension (4VPE), but the RFC explicitly does
605 not discuss this use and defines it as out of scope.
606
607 Gap: Minor; <a href="./rfc4659">RFC 4659</a> needs to be updated to explicitly cover use case
608 2.
609
610
611
612 <span class="grey">George &amp; Pignataro Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
615
616
617 <span class="h5"><a class="selflink" id="section-3.3.2.3" href="#section-3.3.2.3">3.3.2.3</a>. BGP Encapsulation Subsequent Address Family Identifier (SAFI)</span>
618
619 <a href="./rfc5512">RFC 5512</a> [<a href="./rfc5512" title="&quot;The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute&quot;">RFC5512</a>] defines the BGP Encapsulation SAFI and the BGP
620 Tunnel Encapsulation Attribute, which can be used to signal tunneling
621 over an IP Core that is using a single address family. This
622 mechanism supports transport of MPLS (and other protocols) over
623 Tunnels in an IP core (including an IPv6-only core). In this
624 context, load balancing can be provided as specified in <a href="./rfc5640">RFC 5640</a>
625 [<a href="./rfc5640" title="&quot;Load- Balancing for Mesh Softwires&quot;">RFC5640</a>].
626
627 Gap: None.
628
629 <span class="h5"><a class="selflink" id="section-3.3.2.4" href="#section-3.3.2.4">3.3.2.4</a>. Multicast in MPLS/BGP IP VPN (MVPN)</span>
630
631 <a href="./rfc6513">RFC 6513</a> [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] defines the procedure to provide multicast service
632 over an MPLS VPN backbone for downstream customers. It is sometimes
633 referred to as Next Generation Multicast VPN (NG-MVPN) The procedure
634 involves the below set of protocols.
635
636 <span class="h6"><a class="selflink" id="section-3.3.2.4.1" href="#section-3.3.2.4.1">3.3.2.4.1</a>. PE-CE Multicast Routing Protocol</span>
637
638 <a href="./rfc6513">RFC 6513</a> [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] explains the use of Protocol Independent Multicast
639 (PIM) as a Provider Edge - Customer Edge (PE-CE) protocol, while
640 <a href="./rfc6514#section-11.1.2">Section&nbsp;11.1.2 of RFC 6514</a> [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] explains the use of mLDP as a
641 PE-CE protocol.
642
643 The MCAST-VPN NLRI route-type format defined in <a href="./rfc6514">RFC 6514</a> [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] is
644 not sufficiently covering all scenarios when mLDP is used as a PE-CE
645 protocol. The issue is explained in Section 2 of [<a href="#ref-mLDP-NLRI">mLDP-NLRI</a>] along
646 with a new route type that encodes the mLDP FEC in NLRI.
647
648 Further, [<a href="#ref-PE-CE" title="&quot;BGP as an MVPN PE-CE Protocol&quot;">PE-CE</a>] defines the use of BGP as a PE-CE protocol.
649
650 Gap: None.
651
652 <span class="h6"><a class="selflink" id="section-3.3.2.4.2" href="#section-3.3.2.4.2">3.3.2.4.2</a>. P-Tunnel Instantiation</span>
653
654 [<a id="ref-RFC6513">RFC6513</a>] explains the use of the below tunnels:
655
656 o RSVP-TE P2MP LSP
657
658 o PIM Tree
659
660 o mLDP P2MP LSP
661
662 o mLDP MP2MP LSP
663
664 o Ingress Replication
665
666
667
668 <span class="grey">George &amp; Pignataro Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
671
672
673 Gap: Gaps in RSVP-TE P2MP LSP (<a href="#section-3.2.3.2">Section 3.2.3.2</a>) and mLDP
674 (<a href="#section-3.2.2">Section 3.2.2</a>) P2MP and MP2MP LSP are covered in previous sections.
675 There are no MPLS-specific gaps for PIM Tree or Ingress Replication,
676 and any protocol-specific gaps not related to MPLS are outside the
677 scope of this document.
678
679 <span class="h6"><a class="selflink" id="section-3.3.2.4.3" href="#section-3.3.2.4.3">3.3.2.4.3</a>. PE-PE Multicast Routing Protocol</span>
680
681 <a href="./rfc6513#section-3.1">Section&nbsp;3.1 of RFC 6513</a> [<a href="./rfc6513" title="&quot;Multicast in MPLS/BGP IP VPNs&quot;">RFC6513</a>] explains the use of PIM as a PE-PE
682 protocol, while <a href="./rfc6514">RFC 6514</a> [<a href="./rfc6514" title="&quot;BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs&quot;">RFC6514</a>] explains the use of BGP as a PE-PE
683 protocol.
684
685 PE-PE multicast routing is not specific to P-tunnels or to MPLS. It
686 can be PIM or BGP with P-tunnels that are label based or PIM tree
687 based. Enabling PIM as a PE-PE multicast protocol is equivalent to
688 running it on a non-MPLS IPv6 network, so there are not any MPLS-
689 specific considerations and any gaps are applicable for non-MPLS
690 networks as well. Similarly, BGP only includes the P-Multicast
691 Service Interface (PMSI) tunnel attribute as a part of the NLRI,
692 which is inherited from P-tunnel instantiation and considered to be
693 an opaque value. Any gaps in the control plane (PIM or BGP) will not
694 be specific to MPLS.
695
696 Gap: Any gaps in PIM or BGP as a PE-PE multicast routing protocol are
697 not unique to MPLS, and therefore are outside the scope of this
698 document. It is included for completeness.
699
700 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. MPLS Transport Profile (MPLS-TP)</span>
701
702 MPLS-TP does not require IP (see <a href="./rfc5921#section-2">Section&nbsp;2 of RFC 5921</a> [<a href="./rfc5921" title="&quot;A Framework for MPLS in Transport Networks&quot;">RFC5921</a>]) and
703 should not be affected by operation on an IPv6-only network.
704 Therefore, this is considered out of scope for this document but is
705 included for completeness.
706
707 Although not required, MPLS-TP can use IP. One such example is
708 included in <a href="#section-3.2.6">Section 3.2.6</a>, where MPLS-TP identifiers can be derived
709 from valid IPv4 addresses.
710
711 Gap: None. MPLS-TP does not require IP.
712
713 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. MPLS Operations, Administration, and Maintenance (MPLS OAM)</span>
714
715 For MPLS LSPs, there are primarily three OAM mechanisms: Extended
716 ICMP [<a href="./rfc4884" title="&quot;Extended ICMP to Support Multi-Part Messages&quot;">RFC4884</a>] [<a href="./rfc4950" title="&quot;ICMP Extensions for Multiprotocol Label Switching&quot;">RFC4950</a>], LSP Ping [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>], and Bidirectional
717 Forwarding Detection (BFD) for MPLS LSPs [<a href="./rfc5884" title="&quot;Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)&quot;">RFC5884</a>]. For MPLS
718 Pseudowires, there is also Virtual Circuit Connectivity Verification
719 (VCCV) [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>] [<a href="./rfc5885" title="&quot;Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)&quot;">RFC5885</a>]. Most of these mechanisms work in pure
720
721
722
723
724 <span class="grey">George &amp; Pignataro Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
727
728
729 IPv6 environments, but there are some problems encountered in mixed
730 environments due to address-family mismatches. The next subsections
731 cover these gaps in detail.
732
733 Gap: Major; <a href="./rfc4379">RFC 4379</a> needs to be updated to better support multipath
734 IPv6. Additionally, there is potential for dropped messages in
735 Extended ICMP and LSP Ping due to IP version mismatches. It is
736 important to note that this is a more generic problem with tunneling
737 when address-family mismatches exist and is not specific to MPLS.
738 While MPLS will be affected, it will be difficult to fix this problem
739 specifically for MPLS, rather than fixing the more generic problem.
740
741 <span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a>. Extended ICMP</span>
742
743 Extended ICMP to support Multi-part messages is defined in <a href="./rfc4884">RFC 4884</a>
744 [<a href="./rfc4884" title="&quot;Extended ICMP to Support Multi-Part Messages&quot;">RFC4884</a>]. This extensibility is defined generally for both ICMPv4
745 and ICMPv6. The specific ICMP extensions for MPLS are defined in <a href="./rfc4950">RFC</a>
746 <a href="./rfc4950">4950</a> [<a href="./rfc4950" title="&quot;ICMP Extensions for Multiprotocol Label Switching&quot;">RFC4950</a>]. ICMP Multi-part with MPLS extensions works for IPv4
747 and IPv6. However, the mechanisms described in <a href="./rfc4884">RFC 4884</a> and 4950 may
748 fail when tunneling IPv4 traffic over an LSP that is supported by an
749 IPv6-only infrastructure.
750
751 Assume the following:
752
753 o The path between two IPv4-only hosts contains an MPLS LSP.
754
755 o The two routers that terminate the LSP run dual stack.
756
757 o The LSP interior routers run IPv6 only.
758
759 o The LSP is signaled over IPv6.
760
761 Now assume that one of the hosts sends an IPv4 packet to the other.
762 However, the packet's TTL expires on an LSP interior router.
763 According to <a href="./rfc3032">RFC 3032</a> [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>], the interior router should examine
764 the IPv4 payload, format an ICMPv4 message, and send it (over the
765 tunnel upon which the original packet arrived) to the egress LSP. In
766 this case, however, the LSP interior router is not IPv4-aware. It
767 cannot parse the original IPv4 datagram, nor can it send an IPv4
768 message. So, no ICMP message is delivered to the source. Some
769 specific ICMP extensions, in particular, ICMP extensions for
770 interface and next-hop identification [<a href="./rfc5837" title="&quot;Extending ICMP for Interface and Next-Hop Identification&quot;">RFC5837</a>], restrict the address
771 family of address information included in an Interface Information
772 Object to the same one as the ICMP (see <a href="./rfc5837#section-4.5">Section&nbsp;4.5 of RFC 5837</a>).
773 While these extensions are not MPLS specific, they can be used with
774 MPLS packets carrying IP datagrams. This has no implications for
775 IPv6-only environments.
776
777
778
779
780 <span class="grey">George &amp; Pignataro Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
783
784
785 Gap: Major; IP version mismatches may cause dropped messages.
786 However, as noted in the previous section, this problem is not
787 specific to MPLS.
788
789 <span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a>. Label Switched Path Ping (LSP Ping)</span>
790
791 The LSP Ping mechanism defined in <a href="./rfc4379">RFC 4379</a> [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>] is specified to
792 work with IPv6. Specifically, the Target FEC Stacks include both
793 IPv4 and IPv6 versions of all FECs (see <a href="./rfc4379#section-3.2">Section&nbsp;3.2 of RFC 4379</a>).
794 The only exceptions are the Pseudowire FECs, which are later
795 specified for IPv6 in <a href="./rfc6829">RFC 6829</a> [<a href="./rfc6829" title="&quot;Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6&quot;">RFC6829</a>]. The multipath information
796 also includes IPv6 encodings (see <a href="./rfc4379#section-3.3.1">Section&nbsp;3.3.1 of RFC 4379</a>).
797
798 LSP Ping packets are UDP packets over either IPv4 or IPv6 (see
799 <a href="./rfc4379#section-4.3">Section&nbsp;4.3 of RFC 4379</a>). However, for IPv6 the destination IP
800 address is a (randomly chosen) IPv6 address from the range
801 0:0:0:0:0:FFFF:127/104; that is, using an IPv4-mapped IPv6 address.
802 This is a transitional mechanism that should not bleed into IPv6-only
803 networks, as [<a href="#ref-IPv4-MAPPED">IPv4-MAPPED</a>] explains. The issue is that the MPLS LSP
804 Ping mechanism needs a range of loopback IP addresses to be used as
805 destination addresses to exercise Equal Cost Multiple Path (ECMP),
806 but the IPv6 address architecture specifies a single address
807 (::1/128) for loopback. A mechanism to achieve this was proposed in
808 [<a href="#ref-LOOPBACK-PREFIX">LOOPBACK-PREFIX</a>].
809
810 Additionally, <a href="./rfc4379">RFC 4379</a> does not define the value to be used in the
811 IPv6 Router Alert option (RAO). For IPv4 RAO, a value of zero is
812 used. However, there is no equivalent value for IPv6 RAO. This gap
813 needs to be fixed to be able to use LSP Ping in IPv6 networks.
814 Further details on this gap are captured, along with a proposed
815 solution, in [<a href="#ref-IPv6-RAO">IPv6-RAO</a>].
816
817 Another gap is that the mechanisms described in <a href="./rfc4379">RFC 4379</a> may fail
818 when tunneling IPv4 traffic over an LSP that is supported by
819 IPv6-only infrastructure.
820
821 Assume the following:
822
823 o LSP Ping is operating in traceroute mode over an MPLS LSP.
824
825 o The two routers that terminate the LSP run dual stack.
826
827 o The LSP interior routers run IPv6 only.
828
829 o The LSP is signaled over IPv6.
830
831
832
833
834
835
836 <span class="grey">George &amp; Pignataro Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
839
840
841 Packets will expire at LSP interior routers. According to <a href="./rfc4379">RFC 4379</a>,
842 the interior router must parse the IPv4 Echo Request and then send an
843 IPv4 Echo Reply. However, the LSP interior router is not IPv4-aware.
844 It cannot parse the IPv4 Echo Request, nor can it send an IPv4 Echo
845 Reply. So, no reply is sent.
846
847 The mechanism described in <a href="./rfc4379">RFC 4379</a> also does not sufficiently
848 explain the behavior in certain IPv6-specific scenarios. For
849 example, <a href="./rfc4379">RFC 4379</a> defines the K value as 28 octets when the Address
850 Family is set to IPv6 Unnumbered, but it doesn't describe how to
851 carry a 32-bit LSR Router ID in the 128-bit Downstream IP Address
852 field.
853
854 Gap: Major; LSP Ping uses IPv4-mapped IPv6 addresses. IP version
855 mismatches may cause dropped messages and unclear mapping from the
856 LSR Router ID to Downstream IP Address.
857
858 <span class="h4"><a class="selflink" id="section-3.4.3" href="#section-3.4.3">3.4.3</a>. Bidirectional Forwarding Detection (BFD)</span>
859
860 The BFD specification for MPLS LSPs [<a href="./rfc5884" title="&quot;Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)&quot;">RFC5884</a>] is defined for IPv4, as
861 well as IPv6, versions of MPLS FECs (see <a href="./rfc5884#section-3.1">Section&nbsp;3.1 of RFC 5884</a>).
862 Additionally, the BFD packet is encapsulated over UDP and specified
863 to run over both IPv4 and IPv6 (see <a href="./rfc5884#section-7">Section&nbsp;7 of RFC 5884</a>).
864
865 Gap: None.
866
867 <span class="h4"><a class="selflink" id="section-3.4.4" href="#section-3.4.4">3.4.4</a>. Pseudowire OAM</span>
868
869 The OAM specifications for MPLS Pseudowires define usage for both
870 IPv4 and IPv6. Specifically, VCCV [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>] can carry IPv4 or IPv6
871 OAM packets (see Sections <a href="#section-5.1.1">5.1.1</a> and <a href="#section-5.2.1">5.2.1</a> of <a href="./rfc5085">RFC 5085</a>), and VCCV for
872 BFD [<a href="./rfc5885" title="&quot;Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)&quot;">RFC5885</a>] also defines an IPv6 encapsulation (see <a href="./rfc5885#section-3.2">Section&nbsp;3.2 of
873 RFC 5885</a>).
874
875 Additionally, for LSP Ping for pseudowires, the Pseudowire FECs are
876 specified for IPv6 in <a href="./rfc6829">RFC 6829</a> [<a href="./rfc6829" title="&quot;Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6&quot;">RFC6829</a>].
877
878 Gap: None.
879
880 <span class="h4"><a class="selflink" id="section-3.4.5" href="#section-3.4.5">3.4.5</a>. MPLS Transport Profile (MPLS-TP) OAM</span>
881
882 As with MPLS-TP, MPLS-TP OAM [<a href="./rfc6371" title="&quot;Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks&quot;">RFC6371</a>] does not require IP or
883 existing MPLS OAM functions and should not be affected by operation
884 on an IPv6-only network. Therefore, this is out of scope for this
885 document but is included for completeness. Although not required,
886 MPLS-TP can use IP.
887
888 Gap: None. MPLS-TP OAM does not require IP.
889
890
891
892 <span class="grey">George &amp; Pignataro Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
895
896
897 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. MIB Modules</span>
898
899 <a href="./rfc3811">RFC 3811</a> [<a href="./rfc3811" title="&quot;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management&quot;">RFC3811</a>] defines the textual conventions for MPLS. These
900 lack support for IPv6 in defining MplsExtendedTunnelId and
901 MplsLsrIdentifier. These textual conventions are used in the MPLS-TE
902 MIB specification [<a href="./rfc3812" title="&quot;Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)&quot;">RFC3812</a>], the GMPLS-TE MIB specification [<a href="./rfc4802" title="&quot;Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base&quot;">RFC4802</a>]
903 and the FRR extension [<a href="./rfc6445" title="&quot;Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute&quot;">RFC6445</a>]. "Definitions of Textual Conventions
904 (TCs) for Multiprotocol Label Switching (MPLS) Management" [<a href="#ref-MPLS-TC" title="&quot;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management&quot;">MPLS-TC</a>]
905 tries to resolve this gap by marking this textual convention as
906 obsolete.
907
908 The other MIB specifications for LSR [<a href="./rfc3813" title="&quot;Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)&quot;">RFC3813</a>], LDP [<a href="./rfc3815" title="&quot;Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)&quot;">RFC3815</a>], and TE
909 [<a href="./rfc4220" title="&quot;Traffic Engineering Link Management Information Base&quot;">RFC4220</a>] have support for both IPv4 and IPv6.
910
911 Lastly, <a href="./rfc4990">RFC 4990</a> [<a href="./rfc4990" title="&quot;Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks&quot;">RFC4990</a>] discusses how to handle IPv6 sources and
912 destinations in the MPLS and GMPLS-TE MIB modules. In particular,
913 <a href="./rfc4990#section-8">Section&nbsp;8 of RFC 4990</a> [<a href="./rfc4990" title="&quot;Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks&quot;">RFC4990</a>] describes a method of defining or
914 monitoring an LSP tunnel using the MPLS-TE and GMPLS-TE MIB modules,
915 working around some of the limitations in <a href="./rfc3811">RFC 3811</a> [<a href="./rfc3811" title="&quot;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management&quot;">RFC3811</a>].
916
917 Gap: Minor; <a href="./rfc4990#section-8">Section&nbsp;8 of RFC 4990</a> [<a href="./rfc4990" title="&quot;Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks&quot;">RFC4990</a>] describes a method to
918 handle IPv6 addresses in the MPLS-TE [<a href="./rfc3812" title="&quot;Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)&quot;">RFC3812</a>] and GMPLS-TE [<a href="./rfc4802" title="&quot;Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base&quot;">RFC4802</a>]
919 MIB modules. Work underway to update <a href="./rfc3811">RFC 3811</a> via [<a href="#ref-MPLS-TC" title="&quot;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management&quot;">MPLS-TC</a>], may
920 also need to update <a href="./rfc3812">RFC 3812</a>, <a href="./rfc4802">RFC 4802</a>, and <a href="./rfc6445">RFC 6445</a>, which depend on
921 it.
922
923 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Gap Summary</span>
924
925 This document has reviewed a wide variety of MPLS features and
926 protocols to determine their suitability for use on IPv6-only or
927 IPv6-primary networks. While some parts of the MPLS suite will
928 function properly without additional changes, gaps have been
929 identified in others that will need to be addressed with follow-on
930 work. This section will summarize those gaps, along with pointers to
931 any work in progress to address them. Note that because the
932 referenced documents are works in progress and do not have consensus
933 at the time of this document's publication, there could be other
934 solutions proposed at a future time, and the pointers in this
935 document should not be considered normative in any way.
936 Additionally, work in progress on new features that use MPLS
937 protocols will need to ensure that those protocols support operation
938 on IPv6-only or IPv6-primary networks, or explicitly identify any
939 dependencies on existing gaps that, once resolved, will allow proper
940 IPv6-only operation.
941
942
943
944
945
946
947
948 <span class="grey">George &amp; Pignataro Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
951
952
953 Identified Gaps in MPLS for IPv6-Only Networks
954
955 +---------+---------------------------------------+-----------------+
956 | Item | Gap | Addressed in |
957 +---------+---------------------------------------+-----------------+
958 | LDP | LSP mapping, LDP identifiers, LDP | [<a href="#ref-LDP-IPv6">LDP-IPv6</a>] |
959 | S.3.2.1 | discovery, LDP session establishment, | |
960 | | next-hop address, and LDP TTL | |
961 | | security | |
962 +---------+---------------------------------------+-----------------+
963 | mLDP | Inherits gaps from LDP, <a href="./rfc6512">RFC 6512</a> | Inherits |
964 | S.3.2.2 | [<a href="./rfc6512" title="&quot;Using Multipoint LDP When the Backbone Has No Route to the Root&quot;">RFC6512</a>] | [<a href="#ref-LDP-IPv6">LDP-IPv6</a>], |
965 | | | additional |
966 | | | fixes TBD |
967 +---------+---------------------------------------+-----------------+
968 | GMPLS | <a href="./rfc6370">RFC 6370</a> [<a href="./rfc6370" title="&quot;MPLS Transport Profile (MPLS-TP) Identifiers&quot;">RFC6370</a>] Node ID derivation | TBD |
969 | S.3.2.6 | | |
970 +---------+---------------------------------------+-----------------+
971 | L2VPN | <a href="./rfc6074">RFC 6074</a> [<a href="./rfc6074" title="&quot;Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)&quot;">RFC6074</a>] discovery, | TBD |
972 | S.3.3.1 | signaling | |
973 +---------+---------------------------------------+-----------------+
974 | L3VPN | <a href="./rfc4659">RFC 4659</a> [<a href="./rfc4659" title="&quot;BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN&quot;">RFC4659</a>] does not define a | TBD |
975 | S.3.3.2 | method for 4PE/4VPE | |
976 +---------+---------------------------------------+-----------------+
977 | OAM | <a href="./rfc4379">RFC 4379</a> [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>] No IPv6 multipath | [<a href="#ref-IPv6-RAO">IPv6-RAO</a>] |
978 | S.3.4 | support, no IPv6 RAO, possible | |
979 | | dropped messages in IP version | |
980 | | mismatch | |
981 +---------+---------------------------------------+-----------------+
982 | MIB | <a href="./rfc3811">RFC 3811</a> [<a href="./rfc3811" title="&quot;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management&quot;">RFC3811</a>] no IPv6 textual | [<a href="#ref-MPLS-TC" title="&quot;Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management&quot;">MPLS-TC</a>] |
983 | Modules | convention | |
984 | S.3.5 | | |
985 +---------+---------------------------------------+-----------------+
986
987 Table 1: IPv6-Only MPLS Gaps
988
989 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
990
991 Changing the address family used for MPLS network operation does not
992 fundamentally alter the security considerations currently extant in
993 any of the specifics of the protocol or its features. However,
994 follow-on work recommended by this gap analysis will need to address
995 any effects that the use of IPv6 in their modifications may have on
996 security.
997
998
999
1000
1001
1002
1003
1004 <span class="grey">George &amp; Pignataro Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
1010
1011 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
1012
1013 [<a id="ref-RFC2460">RFC2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
1014 (IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998,
1015 &lt;<a href="http://www.rfc-editor.org/info/rfc2460">http://www.rfc-editor.org/info/rfc2460</a>&gt;.
1016
1017 [<a id="ref-RFC3032">RFC3032</a>] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
1018 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
1019 Encoding", <a href="./rfc3032">RFC 3032</a>, January 2001,
1020 &lt;<a href="http://www.rfc-editor.org/info/rfc3032">http://www.rfc-editor.org/info/rfc3032</a>&gt;.
1021
1022 [<a id="ref-RFC3107">RFC3107</a>] Rekhter, Y. and E. Rosen, "Carrying Label Information in
1023 BGP-4", <a href="./rfc3107">RFC 3107</a>, May 2001,
1024 &lt;<a href="http://www.rfc-editor.org/info/rfc3107">http://www.rfc-editor.org/info/rfc3107</a>&gt;.
1025
1026 [<a id="ref-RFC3209">RFC3209</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
1027 and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
1028 Tunnels", <a href="./rfc3209">RFC 3209</a>, December 2001,
1029 &lt;<a href="http://www.rfc-editor.org/info/rfc3209">http://www.rfc-editor.org/info/rfc3209</a>&gt;.
1030
1031 [<a id="ref-RFC3471">RFC3471</a>] Berger, L., "Generalized Multi-Protocol Label Switching
1032 (GMPLS) Signaling Functional Description", <a href="./rfc3471">RFC 3471</a>,
1033 January 2003, &lt;<a href="http://www.rfc-editor.org/info/rfc3471">http://www.rfc-editor.org/info/rfc3471</a>&gt;.
1034
1035 [<a id="ref-RFC3473">RFC3473</a>] Berger, L., "Generalized Multi-Protocol Label Switching
1036 (GMPLS) Signaling Resource ReserVation Protocol-Traffic
1037 Engineering (RSVP-TE) Extensions", <a href="./rfc3473">RFC 3473</a>, January 2003,
1038 &lt;<a href="http://www.rfc-editor.org/info/rfc3473">http://www.rfc-editor.org/info/rfc3473</a>&gt;.
1039
1040 [<a id="ref-RFC3811">RFC3811</a>] Nadeau, T. and J. Cucchiara, "Definitions of Textual
1041 Conventions (TCs) for Multiprotocol Label Switching (MPLS)
1042 Management", <a href="./rfc3811">RFC 3811</a>, June 2004,
1043 &lt;<a href="http://www.rfc-editor.org/info/rfc3811">http://www.rfc-editor.org/info/rfc3811</a>&gt;.
1044
1045 [<a id="ref-RFC4023">RFC4023</a>] Worster, T., Rekhter, Y., and E. Rosen, "Encapsulating
1046 MPLS in IP or Generic Routing Encapsulation (GRE)", <a href="./rfc4023">RFC</a>
1047 <a href="./rfc4023">4023</a>, March 2005,
1048 &lt;<a href="http://www.rfc-editor.org/info/rfc4023">http://www.rfc-editor.org/info/rfc4023</a>&gt;.
1049
1050 [<a id="ref-RFC4379">RFC4379</a>] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
1051 Label Switched (MPLS) Data Plane Failures", <a href="./rfc4379">RFC 4379</a>,
1052 February 2006, &lt;<a href="http://www.rfc-editor.org/info/rfc4379">http://www.rfc-editor.org/info/rfc4379</a>&gt;.
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">George &amp; Pignataro Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1063
1064
1065 [<a id="ref-RFC4659">RFC4659</a>] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
1066 "BGP-MPLS IP Virtual Private Network (VPN) Extension for
1067 IPv6 VPN", <a href="./rfc4659">RFC 4659</a>, September 2006,
1068 &lt;<a href="http://www.rfc-editor.org/info/4659">http://www.rfc-editor.org/info/4659</a>&gt;.
1069
1070 [<a id="ref-RFC4817">RFC4817</a>] Townsley, M., Pignataro, C., Wainner, S., Seely, T., and
1071 J. Young, "Encapsulation of MPLS over Layer 2 Tunneling
1072 Protocol Version 3", <a href="./rfc4817">RFC 4817</a>, March 2007,
1073 &lt;<a href="http://www.rfc-editor.org/info/rfc4817">http://www.rfc-editor.org/info/rfc4817</a>&gt;.
1074
1075 [<a id="ref-RFC5036">RFC5036</a>] Andersson, L., Minei, I., and B. Thomas, "LDP
1076 Specification", <a href="./rfc5036">RFC 5036</a>, October 2007,
1077 &lt;<a href="http://www.rfc-editor.org/info/rfc5036">http://www.rfc-editor.org/info/rfc5036</a>&gt;.
1078
1079 [<a id="ref-RFC6074">RFC6074</a>] Rosen, E., Davie, B., Radoaca, V., and W. Luo,
1080 "Provisioning, Auto-Discovery, and Signaling in Layer 2
1081 Virtual Private Networks (L2VPNs)", <a href="./rfc6074">RFC 6074</a>, January
1082 2011, &lt;<a href="http://www.rfc-editor.org/info/rfc6074">http://www.rfc-editor.org/info/rfc6074</a>&gt;.
1083
1084 [<a id="ref-RFC6370">RFC6370</a>] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport
1085 Profile (MPLS-TP) Identifiers", <a href="./rfc6370">RFC 6370</a>, September 2011,
1086 &lt;<a href="http://www.rfc-editor.org/info/rfc6370">http://www.rfc-editor.org/info/rfc6370</a>&gt;.
1087
1088 [<a id="ref-RFC6512">RFC6512</a>] Wijnands, IJ., Rosen, E., Napierala, M., and N. Leymann,
1089 "Using Multipoint LDP When the Backbone Has No Route to
1090 the Root", <a href="./rfc6512">RFC 6512</a>, February 2012,
1091 &lt;<a href="http://www.rfc-editor.org/info/rfc6512">http://www.rfc-editor.org/info/rfc6512</a>&gt;.
1092
1093 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
1094
1095 [<a id="ref-EVPN">EVPN</a>] Sajassi, A., Aggarwal, R., Bitar, N., Isaac, A., and J.
1096 Uttaro, "BGP MPLS Based Ethernet VPN", Work in Progress,
1097 <a href="./draft-ietf-l2vpn-evpn-11">draft-ietf-l2vpn-evpn-11</a>, October 2014.
1098
1099 [<a id="ref-IPv4-MAPPED">IPv4-MAPPED</a>]
1100 Metz, C. and J. Hagino, "IPv4-Mapped Addresses on the Wire
1101 Considered Harmful", Work in Progress, <a href="./draft-itojun-v6ops-v4mapped-harmful-02">draft-itojun-v6ops-</a>
1102 <a href="./draft-itojun-v6ops-v4mapped-harmful-02">v4mapped-harmful-02</a>, October 2003.
1103
1104 [<a id="ref-IPv6-RAO">IPv6-RAO</a>]
1105 Raza, K., Akiya, N., and C. Pignataro, "IPv6 Router Alert
1106 Option for MPLS OAM", Work in Progress, <a href="./draft-raza-mpls-oam-ipv6-rao-02">draft-raza-mpls-</a>
1107 <a href="./draft-raza-mpls-oam-ipv6-rao-02">oam-ipv6-rao-02</a>, September 2014.
1108
1109 [<a id="ref-LDP-IPv6">LDP-IPv6</a>]
1110 Asati, R., Manral, V., Papneja, R., and C. Pignataro,
1111 "Updates to LDP for IPv6", Work in Progress, <a href="./draft-ietf-mpls-ldp-ipv6-14">draft-ietf-</a>
1112 <a href="./draft-ietf-mpls-ldp-ipv6-14">mpls-ldp-ipv6-14</a>, October 2014.
1113
1114
1115
1116 <span class="grey">George &amp; Pignataro Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1119
1120
1121 [<a id="ref-LOOPBACK-PREFIX">LOOPBACK-PREFIX</a>]
1122 Smith, M., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22A+Larger+Loopback+Prefix+for+IPv6%22'>"A Larger Loopback Prefix for IPv6"</a>, Work in
1123 Progress, <a href="./draft-smith-v6ops-larger-ipv6-loopback-prefix-04">draft-smith-v6ops-larger-ipv6-loopback-prefix-</a>
1124 <a href="./draft-smith-v6ops-larger-ipv6-loopback-prefix-04">04</a>, February 2013.
1125
1126 [<a id="ref-mLDP-NLRI">mLDP-NLRI</a>]
1127 Wijnands, I., Rosen, E., and U. Joorde, "Encoding mLDP
1128 FECs in the NLRI of BGP MCAST-VPN Routes", Work in
1129 Progress, <a href="./draft-ietf-l3vpn-mvpn-mldp-nlri-10">draft-ietf-l3vpn-mvpn-mldp-nlri-10</a>, November
1130 2014.
1131
1132 [<a id="ref-MPLS-TC">MPLS-TC</a>] Manral, V., Tsou, T., Will, W., and F. Fondelli,
1133 "Definitions of Textual Conventions (TCs) for
1134 Multiprotocol Label Switching (MPLS) Management", Work in
1135 Progress, <a href="./draft-manral-mpls-rfc3811bis-04">draft-manral-mpls-rfc3811bis-04</a>, September 2014.
1136
1137 [<a id="ref-PE-CE">PE-CE</a>] Patel, K., Rekhter, Y., and E. Rosen, "BGP as an MVPN
1138 PE-CE Protocol", Work in Progress,
1139 <a href="./draft-ietf-l3vpn-mvpn-pe">draft-ietf-l3vpn-mvpn-pe</a>- ce-02, October 2014.
1140
1141 [<a id="ref-RFC1918">RFC1918</a>] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
1142 E. Lear, "Address Allocation for Private Internets",
1143 <a href="https://www.rfc-editor.org/bcp/bcp5">BCP 5</a>, <a href="./rfc1918">RFC 1918</a>, February 1996,
1144 &lt;<a href="http://www.rfc-editor.org/info/rfc1918">http://www.rfc-editor.org/info/rfc1918</a>&gt;.
1145
1146 [<a id="ref-RFC3630">RFC3630</a>] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
1147 (TE) Extensions to OSPF Version 2", <a href="./rfc3630">RFC 3630</a>, September
1148 2003, &lt;<a href="http://www.rfc-editor.org/info/rfc3630">http://www.rfc-editor.org/info/rfc3630</a>&gt;.
1149
1150 [<a id="ref-RFC3812">RFC3812</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau,
1151 "Multiprotocol Label Switching (MPLS) Traffic Engineering
1152 (TE) Management Information Base (MIB)", <a href="./rfc3812">RFC 3812</a>, June
1153 2004, &lt;<a href="http://www.rfc-editor.org/info/rfc3812">http://www.rfc-editor.org/info/rfc3812</a>&gt;.
1154
1155 [<a id="ref-RFC3813">RFC3813</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau,
1156 "Multiprotocol Label Switching (MPLS) Label Switching
1157 Router (LSR) Management Information Base (MIB)", <a href="./rfc3813">RFC 3813</a>,
1158 June 2004, &lt;<a href="http://www.rfc-editor.org/info/rfc3813">http://www.rfc-editor.org/info/rfc3813</a>&gt;.
1159
1160 [<a id="ref-RFC3815">RFC3815</a>] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions
1161 of Managed Objects for the Multiprotocol Label Switching
1162 (MPLS), Label Distribution Protocol (LDP)", <a href="./rfc3815">RFC 3815</a>, June
1163 2004, &lt;<a href="http://www.rfc-editor.org/info/rfc3815">http://www.rfc-editor.org/info/rfc3815</a>&gt;.
1164
1165 [<a id="ref-RFC4090">RFC4090</a>] Pan, P., Swallow, G., and A. Atlas, "Fast Reroute
1166 Extensions to RSVP-TE for LSP Tunnels", <a href="./rfc4090">RFC 4090</a>, May
1167 2005, &lt;<a href="http://www.rfc-editor.org/info/rfc4090">http://www.rfc-editor.org/info/rfc4090</a>&gt;.
1168
1169
1170
1171
1172 <span class="grey">George &amp; Pignataro Informational [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1175
1176
1177 [<a id="ref-RFC4220">RFC4220</a>] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering
1178 Link Management Information Base", <a href="./rfc4220">RFC 4220</a>, November
1179 2005, &lt;<a href="http://www.rfc-editor.org/info/rfc4220">http://www.rfc-editor.org/info/rfc4220</a>&gt;.
1180
1181 [<a id="ref-RFC4364">RFC4364</a>] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
1182 Networks (VPNs)", <a href="./rfc4364">RFC 4364</a>, February 2006,
1183 &lt;<a href="http://www.rfc-editor.org/info/rfc4364">http://www.rfc-editor.org/info/rfc4364</a>&gt;.
1184
1185 [<a id="ref-RFC4447">RFC4447</a>] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
1186 Heron, "Pseudowire Setup and Maintenance Using the Label
1187 Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April 2006,
1188 &lt;<a href="http://www.rfc-editor.org/info/rfc4447">http://www.rfc-editor.org/info/rfc4447</a>&gt;.
1189
1190 [<a id="ref-RFC4558">RFC4558</a>] Ali, Z., Rahman, R., Prairie, D., and D. Papadimitriou,
1191 "Node-ID Based Resource Reservation Protocol (RSVP) Hello:
1192 A Clarification Statement", <a href="./rfc4558">RFC 4558</a>, June 2006,
1193 &lt;<a href="http://www.rfc-editor.org/info/rfc4558">http://www.rfc-editor.org/info/rfc4558</a>&gt;.
1194
1195 [<a id="ref-RFC4655">RFC4655</a>] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
1196 Element (PCE)-Based Architecture", <a href="./rfc4655">RFC 4655</a>, August 2006,
1197 &lt;<a href="http://www.rfc-editor.org/info/rfc4655">http://www.rfc-editor.org/info/rfc4655</a>&gt;.
1198
1199 [<a id="ref-RFC4664">RFC4664</a>] Andersson, L. and E. Rosen, "Framework for Layer 2 Virtual
1200 Private Networks (L2VPNs)", <a href="./rfc4664">RFC 4664</a>, September 2006,
1201 &lt;<a href="http://www.rfc-editor.org/info/rfc4664">http://www.rfc-editor.org/info/rfc4664</a>&gt;.
1202
1203 [<a id="ref-RFC4761">RFC4761</a>] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service
1204 (VPLS) Using BGP for Auto-Discovery and Signaling", <a href="./rfc4761">RFC</a>
1205 <a href="./rfc4761">4761</a>, January 2007,
1206 &lt;<a href="http://www.rfc-editor.org/info/rfc4761">http://www.rfc-editor.org/info/rfc4761</a>&gt;.
1207
1208 [<a id="ref-RFC4762">RFC4762</a>] Lasserre, M. and V. Kompella, "Virtual Private LAN Service
1209 (VPLS) Using Label Distribution Protocol (LDP) Signaling",
1210 <a href="./rfc4762">RFC 4762</a>, January 2007,
1211 &lt;<a href="http://www.rfc-editor.org/info/rfc4762">http://www.rfc-editor.org/info/rfc4762</a>&gt;.
1212
1213 [<a id="ref-RFC4798">RFC4798</a>] De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur,
1214 "Connecting IPv6 Islands over IPv4 MPLS Using IPv6
1215 Provider Edge Routers (6PE)", <a href="./rfc4798">RFC 4798</a>, February 2007,
1216 &lt;<a href="http://www.rfc-editor.org/info/rfc4798">http://www.rfc-editor.org/info/rfc4798</a>&gt;.
1217
1218 [<a id="ref-RFC4802">RFC4802</a>] Nadeau, T. and A. Farrel, "Generalized Multiprotocol Label
1219 Switching (GMPLS) Traffic Engineering Management
1220 Information Base", <a href="./rfc4802">RFC 4802</a>, February 2007,
1221 &lt;<a href="http://www.rfc-editor.org/info/rfc4802">http://www.rfc-editor.org/info/rfc4802</a>&gt;.
1222
1223
1224
1225
1226
1227
1228 <span class="grey">George &amp; Pignataro Informational [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1231
1232
1233 [<a id="ref-RFC4875">RFC4875</a>] Aggarwal, R., Papadimitriou, D., and S. Yasukawa,
1234 "Extensions to Resource Reservation Protocol - Traffic
1235 Engineering (RSVP-TE) for Point-to-Multipoint TE Label
1236 Switched Paths (LSPs)", <a href="./rfc4875">RFC 4875</a>, May 2007,
1237 &lt;<a href="http://www.rfc-editor.org/info/rfc4875">http://www.rfc-editor.org/info/rfc4875</a>&gt;.
1238
1239 [<a id="ref-RFC4884">RFC4884</a>] Bonica, R., Gan, D., Tappan, D., and C. Pignataro,
1240 "Extended ICMP to Support Multi-Part Messages", <a href="./rfc4884">RFC 4884</a>,
1241 April 2007, &lt;<a href="http://www.rfc-editor.org/info/rfc4884">http://www.rfc-editor.org/info/rfc4884</a>&gt;.
1242
1243 [<a id="ref-RFC4950">RFC4950</a>] Bonica, R., Gan, D., Tappan, D., and C. Pignataro, "ICMP
1244 Extensions for Multiprotocol Label Switching", <a href="./rfc4950">RFC 4950</a>,
1245 August 2007, &lt;<a href="http://www.rfc-editor.org/info/rfc4950">http://www.rfc-editor.org/info/rfc4950</a>&gt;.
1246
1247 [<a id="ref-RFC4990">RFC4990</a>] Shiomoto, K., Papneja, R., and R. Rabbat, "Use of
1248 Addresses in Generalized Multiprotocol Label Switching
1249 (GMPLS) Networks", <a href="./rfc4990">RFC 4990</a>, September 2007,
1250 &lt;<a href="http://www.rfc-editor.org/info/rfc4990">http://www.rfc-editor.org/info/rfc4990</a>&gt;.
1251
1252 [<a id="ref-RFC5082">RFC5082</a>] Gill, V., Heasley, J., Meyer, D., Savola, P., and C.
1253 Pignataro, "The Generalized TTL Security Mechanism
1254 (GTSM)", <a href="./rfc5082">RFC 5082</a>, October 2007,
1255 &lt;<a href="http://www.rfc-editor.org/info/rfc5082">http://www.rfc-editor.org/info/rfc5082</a>&gt;.
1256
1257 [<a id="ref-RFC5085">RFC5085</a>] Nadeau, T. and C. Pignataro, "Pseudowire Virtual Circuit
1258 Connectivity Verification (VCCV): A Control Channel for
1259 Pseudowires", <a href="./rfc5085">RFC 5085</a>, December 2007,
1260 &lt;<a href="http://www.rfc-editor.org/info/rfc5085">http://www.rfc-editor.org/info/rfc5085</a>&gt;.
1261
1262 [<a id="ref-RFC5088">RFC5088</a>] Le Roux, JL., Vasseur, JP., Ikejiri, Y., and R. Zhang,
1263 "OSPF Protocol Extensions for Path Computation Element
1264 (PCE) Discovery", <a href="./rfc5088">RFC 5088</a>, January 2008,
1265 &lt;<a href="http://www.rfc-editor.org/info/rfc5088">http://www.rfc-editor.org/info/rfc5088</a>&gt;.
1266
1267 [<a id="ref-RFC5089">RFC5089</a>] Le Roux, JL., Vasseur, JP., Ikejiri, Y., and R. Zhang,
1268 "IS-IS Protocol Extensions for Path Computation Element
1269 (PCE) Discovery", <a href="./rfc5089">RFC 5089</a>, January 2008,
1270 &lt;<a href="http://www.rfc-editor.org/info/rfc5089">http://www.rfc-editor.org/info/rfc5089</a>&gt;.
1271
1272 [<a id="ref-RFC5286">RFC5286</a>] Atlas, A. and A. Zinin, "Basic Specification for IP Fast
1273 Reroute: Loop-Free Alternates", <a href="./rfc5286">RFC 5286</a>, September 2008,
1274 &lt;<a href="http://www.rfc-editor.org/info/rfc5286">http://www.rfc-editor.org/info/rfc5286</a>&gt;.
1275
1276 [<a id="ref-RFC5305">RFC5305</a>] Li, T. and H. Smit, "IS-IS Extensions for Traffic
1277 Engineering", <a href="./rfc5305">RFC 5305</a>, October 2008,
1278 &lt;<a href="http://www.rfc-editor.org/info/rfc5305">http://www.rfc-editor.org/info/rfc5305</a>&gt;.
1279
1280
1281
1282
1283
1284 <span class="grey">George &amp; Pignataro Informational [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1287
1288
1289 [<a id="ref-RFC5329">RFC5329</a>] Ishiguro, K., Manral, V., Davey, A., and A. Lindem,
1290 "Traffic Engineering Extensions to OSPF Version 3", <a href="./rfc5329">RFC</a>
1291 <a href="./rfc5329">5329</a>, September 2008,
1292 &lt;<a href="http://www.rfc-editor.org/info/rfc5329">http://www.rfc-editor.org/info/rfc5329</a>&gt;.
1293
1294 [<a id="ref-RFC5440">RFC5440</a>] Vasseur, JP. and JL. Le Roux, "Path Computation Element
1295 (PCE) Communication Protocol (PCEP)", <a href="./rfc5440">RFC 5440</a>, March
1296 2009, &lt;<a href="http://www.rfc-editor.org/info/rfc5440">http://www.rfc-editor.org/info/rfc5440</a>&gt;.
1297
1298 [<a id="ref-RFC5512">RFC5512</a>] Mohapatra, P. and E. Rosen, "The BGP Encapsulation
1299 Subsequent Address Family Identifier (SAFI) and the BGP
1300 Tunnel Encapsulation Attribute", <a href="./rfc5512">RFC 5512</a>, April 2009,
1301 &lt;<a href="http://www.rfc-editor.org/info/rfc5512">http://www.rfc-editor.org/info/rfc5512</a>&gt;.
1302
1303 [<a id="ref-RFC5520">RFC5520</a>] Bradford, R., Vasseur, JP., and A. Farrel, "Preserving
1304 Topology Confidentiality in Inter-Domain Path Computation
1305 Using a Path-Key-Based Mechanism", <a href="./rfc5520">RFC 5520</a>, April 2009,
1306 &lt;<a href="http://www.rfc-editor.org/info/rfc5520">http://www.rfc-editor.org/info/rfc5520</a>&gt;.
1307
1308 [<a id="ref-RFC5521">RFC5521</a>] Oki, E., Takeda, T., and A. Farrel, "Extensions to the
1309 Path Computation Element Communication Protocol (PCEP) for
1310 Route Exclusions", <a href="./rfc5521">RFC 5521</a>, April 2009,
1311 &lt;<a href="http://www.rfc-editor.org/info/rfc5521">http://www.rfc-editor.org/info/rfc5521</a>&gt;.
1312
1313 [<a id="ref-RFC5640">RFC5640</a>] Filsfils, C., Mohapatra, P., and C. Pignataro, "Load-
1314 Balancing for Mesh Softwires", <a href="./rfc5640">RFC 5640</a>, August 2009,
1315 &lt;<a href="http://www.rfc-editor.org/info/rfc5640">http://www.rfc-editor.org/info/rfc5640</a>&gt;.
1316
1317 [<a id="ref-RFC5837">RFC5837</a>] Atlas, A., Bonica, R., Pignataro, C., Shen, N., and JR.
1318 Rivers, "Extending ICMP for Interface and Next-Hop
1319 Identification", <a href="./rfc5837">RFC 5837</a>, April 2010,
1320 &lt;<a href="http://www.rfc-editor.org/info/rfc5837">http://www.rfc-editor.org/info/rfc5837</a>&gt;.
1321
1322 [<a id="ref-RFC5884">RFC5884</a>] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
1323 "Bidirectional Forwarding Detection (BFD) for MPLS Label
1324 Switched Paths (LSPs)", <a href="./rfc5884">RFC 5884</a>, June 2010,
1325 &lt;<a href="http://www.rfc-editor.org/info/rfc5884">http://www.rfc-editor.org/info/rfc5884</a>&gt;.
1326
1327 [<a id="ref-RFC5885">RFC5885</a>] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding
1328 Detection (BFD) for the Pseudowire Virtual Circuit
1329 Connectivity Verification (VCCV)", <a href="./rfc5885">RFC 5885</a>, June 2010,
1330 &lt;<a href="http://www.rfc-editor.org/info/rfc5885">http://www.rfc-editor.org/info/rfc5885</a>&gt;.
1331
1332 [<a id="ref-RFC5886">RFC5886</a>] Vasseur, JP., Le Roux, JL., and Y. Ikejiri, "A Set of
1333 Monitoring Tools for Path Computation Element (PCE)-Based
1334 Architecture", <a href="./rfc5886">RFC 5886</a>, June 2010,
1335 &lt;<a href="http://www.rfc-editor.org/info/rfc5886">http://www.rfc-editor.org/info/rfc5886</a>&gt;.
1336
1337
1338
1339
1340 <span class="grey">George &amp; Pignataro Informational [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1343
1344
1345 [<a id="ref-RFC5921">RFC5921</a>] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
1346 Berger, "A Framework for MPLS in Transport Networks",
1347 <a href="./rfc5921">RFC 5921</a>, July 2010,
1348 &lt;<a href="http://www.rfc-editor.org/info/rfc5921">http://www.rfc-editor.org/info/rfc5921</a>&gt;.
1349
1350 [<a id="ref-RFC6006">RFC6006</a>] Zhao, Q., King, D., Verhaeghe, F., Takeda, T., Ali, Z.,
1351 and J. Meuric, "Extensions to the Path Computation Element
1352 Communication Protocol (PCEP) for Point-to-Multipoint
1353 Traffic Engineering Label Switched Paths", <a href="./rfc6006">RFC 6006</a>,
1354 September 2010, &lt;<a href="http://www.rfc-editor.org/info/rfc6006">http://www.rfc-editor.org/info/rfc6006</a>&gt;.
1355
1356 [<a id="ref-RFC6073">RFC6073</a>] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M.
1357 Aissaoui, "Segmented Pseudowire", <a href="./rfc6073">RFC 6073</a>, January 2011,
1358 &lt;<a href="http://www.rfc-editor.org/info/rfc6073">http://www.rfc-editor.org/info/rfc6073</a>&gt;.
1359
1360 [<a id="ref-RFC6119">RFC6119</a>] Harrison, J., Berger, J., and M. Bartlett, "IPv6 Traffic
1361 Engineering in IS-IS", <a href="./rfc6119">RFC 6119</a>, February 2011,
1362 &lt;<a href="http://www.rfc-editor.org/info/rfc6119">http://www.rfc-editor.org/info/rfc6119</a>&gt;.
1363
1364 [<a id="ref-RFC6371">RFC6371</a>] Busi, I. and D. Allan, "Operations, Administration, and
1365 Maintenance Framework for MPLS-Based Transport Networks",
1366 <a href="./rfc6371">RFC 6371</a>, September 2011,
1367 &lt;<a href="http://www.rfc-editor.org/info/rfc6371">http://www.rfc-editor.org/info/rfc6371</a>&gt;.
1368
1369 [<a id="ref-RFC6388">RFC6388</a>] Wijnands, IJ., Minei, I., Kompella, K., and B. Thomas,
1370 "Label Distribution Protocol Extensions for Point-to-
1371 Multipoint and Multipoint-to-Multipoint Label Switched
1372 Paths", <a href="./rfc6388">RFC 6388</a>, November 2011,
1373 &lt;<a href="http://www.rfc-editor.org/info/rfc6388">http://www.rfc-editor.org/info/rfc6388</a>&gt;.
1374
1375 [<a id="ref-RFC6445">RFC6445</a>] Nadeau, T., Koushik, A., and R. Cetin, "Multiprotocol
1376 Label Switching (MPLS) Traffic Engineering Management
1377 Information Base for Fast Reroute", <a href="./rfc6445">RFC 6445</a>, November
1378 2011, &lt;<a href="http://www.rfc-editor.org/info/rfc6445">http://www.rfc-editor.org/info/rfc6445</a>&gt;.
1379
1380 [<a id="ref-RFC6513">RFC6513</a>] Rosen, E. and R. Aggarwal, "Multicast in MPLS/BGP IP
1381 VPNs", <a href="./rfc6513">RFC 6513</a>, February 2012,
1382 &lt;<a href="http://www.rfc-editor.org/info/rfc6513">http://www.rfc-editor.org/info/rfc6513</a>&gt;.
1383
1384 [<a id="ref-RFC6514">RFC6514</a>] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
1385 Encodings and Procedures for Multicast in MPLS/BGP IP
1386 VPNs", <a href="./rfc6514">RFC 6514</a>, February 2012,
1387 &lt;<a href="http://rfc-editor.org/info/rfc6514">http://rfc-editor.org/info/rfc6514</a>&gt;.
1388
1389 [<a id="ref-RFC6540">RFC6540</a>] George, W., Donley, C., Liljenstolpe, C., and L. Howard,
1390 "IPv6 Support Required for All IP-Capable Nodes", <a href="https://www.rfc-editor.org/bcp/bcp177">BCP 177</a>,
1391 <a href="./rfc6540">RFC 6540</a>, April 2012,
1392 &lt;<a href="http://www.rfc-editor.org/info/rfc6540">http://www.rfc-editor.org/info/rfc6540</a>&gt;.
1393
1394
1395
1396 <span class="grey">George &amp; Pignataro Informational [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1399
1400
1401 [<a id="ref-RFC6624">RFC6624</a>] Kompella, K., Kothari, B., and R. Cherukuri, "Layer 2
1402 Virtual Private Networks Using BGP for Auto-Discovery and
1403 Signaling", <a href="./rfc6624">RFC 6624</a>, May 2012,
1404 &lt;<a href="http://www.rfc-editor.org/info/rfc6624">http://www.rfc-editor.org/info/rfc6624</a>&gt;.
1405
1406 [<a id="ref-RFC6720">RFC6720</a>] Pignataro, C. and R. Asati, "The Generalized TTL Security
1407 Mechanism (GTSM) for the Label Distribution Protocol
1408 (LDP)", <a href="./rfc6720">RFC 6720</a>, August 2012,
1409 &lt;<a href="http://www.rfc-editor.org/info/rfc6720">http://www.rfc-editor.org/info/rfc6720</a>&gt;.
1410
1411 [<a id="ref-RFC6829">RFC6829</a>] Chen, M., Pan, P., Pignataro, C., and R. Asati, "Label
1412 Switched Path (LSP) Ping for Pseudowire Forwarding
1413 Equivalence Classes (FECs) Advertised over IPv6", <a href="./rfc6829">RFC</a>
1414 <a href="./rfc6829">6829</a>, January 2013,
1415 &lt;<a href="http://www.rfc-editor.org/info/rfc6829">http://www.rfc-editor.org/info/rfc6829</a>&gt;.
1416
1417 [<a id="ref-RFC7117">RFC7117</a>] Aggarwal, R., Kamite, Y., Fang, L., Rekhter, Y., and C.
1418 Kodeboniya, "Multicast in Virtual Private LAN Service
1419 (VPLS)", <a href="./rfc7117">RFC 7117</a>, February 2014,
1420 &lt;<a href="http://www.rfc-editor.org/info/rfc7117">http://www.rfc-editor.org/info/rfc7117</a>&gt;.
1421
1422 Acknowledgements
1423
1424 The authors wish to thank Alvaro Retana, Andrew Yourtchenko, Loa
1425 Andersson, David Allan, Mach Chen, Mustapha Aissaoui, and Mark Tinka
1426 for their detailed reviews, as well as Brian Haberman, Joel Jaeggli,
1427 Adrian Farrel, Nobo Akiya, Francis Dupont, and Tobias Gondrom for
1428 their comments.
1429
1430 Contributors
1431
1432 The following people have contributed text to this document:
1433
1434 Rajiv Asati
1435 Cisco Systems
1436 7025 Kit Creek Road
1437 Research Triangle Park, NC 27709
1438 United States
1439
1440 EMail: [email protected]
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">George &amp; Pignataro Informational [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1455
1456
1457 Kamran Raza
1458 Cisco Systems
1459 2000 Innovation Drive
1460 Ottawa, ON K2K-3E8
1461 Canada
1462
1463 EMail: [email protected]
1464
1465
1466 Ronald Bonica
1467 Juniper Networks
1468 2251 Corporate Park Drive
1469 Herndon, VA 20171
1470 United States
1471
1472 EMail: [email protected]
1473
1474
1475 Rajiv Papneja
1476 Huawei Technologies
1477 2330 Central Expressway
1478 Santa Clara, CA 95050
1479 United States
1480
1481 EMail: [email protected]
1482
1483
1484 Dhruv Dhody
1485 Huawei Technologies
1486 Leela Palace
1487 Bangalore, Karnataka 560008
1488 India
1489
1490 EMail: [email protected]
1491
1492
1493 Vishwas Manral
1494 Ionos Networks
1495 Sunnyvale, CA 94089
1496 United States
1497
1498 EMail: [email protected]
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508 <span class="grey">George &amp; Pignataro Informational [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc7439">RFC 7439</a> IPv6-Only MPLS January 2015</span>
1511
1512
1513 Nagendra Kumar
1514 Cisco Systems, Inc.
1515 7200 Kit Creek Road
1516 Research Triangle Park, NC 27709
1517 United States
1518
1519 EMail: [email protected]
1520
1521 Authors' Addresses
1522
1523 Wesley George (editor)
1524 Time Warner Cable
1525 13820 Sunrise Valley Drive
1526 Herndon, VA 20111
1527 United States
1528
1529 Phone: +1-703-561-2540
1530 EMail: [email protected]
1531
1532
1533 Carlos Pignataro (editor)
1534 Cisco Systems, Inc.
1535 7200-12 Kit Creek Road
1536 Research Triangle Park, NC 27709
1537 United States
1538
1539 Phone: +1-919-392-7428
1540 EMail: [email protected]
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564 George &amp; Pignataro Informational [Page 28]
1565 </pre>