Debian Codegraph @

rfc6073.html

raw
1 <pre>Internet Engineering Task Force (IETF) L. Martini
2 Request for Comments: 6073 C. Metz
3 Category: Standards Track Cisco Systems, Inc.
4 ISSN: 2070-1721 T. Nadeau
5 LucidVision
6 M. Bocci
7 M. Aissaoui
8 Alcatel-Lucent
9 January 2011
10
11
12 <span class="h1">Segmented Pseudowire</span>
13
14 Abstract
15
16 This document describes how to connect pseudowires (PWs) between
17 different Packet Switched Network (PSN) domains or between two or
18 more distinct PW control plane domains, where a control plane domain
19 uses a common control plane protocol or instance of that protocol for
20 a given PW. The different PW control plane domains may belong to
21 independent autonomous systems, or the PSN technology is
22 heterogeneous, or a PW might need to be aggregated at a specific PSN
23 point. The PW packet data units are simply switched from one PW to
24 another without changing the PW payload.
25
26 Status of This Memo
27
28 This is an Internet Standards Track document.
29
30 This document is a product of the Internet Engineering Task Force
31 (IETF). It represents the consensus of the IETF community. It has
32 received public review and has been approved for publication by the
33 Internet Engineering Steering Group (IESG). Further information on
34 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
35
36 Information about the current status of this document, any errata,
37 and how to provide feedback on it may be obtained at
38 <a href="http://www.rfc-editor.org/info/rfc6073">http://www.rfc-editor.org/info/rfc6073</a>.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Martini, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2011 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 This document may contain material from IETF Documents or IETF
73 Contributions published or made publicly available before November
74 10, 2008. The person(s) controlling the copyright in some of this
75 material may not have granted the IETF Trust the right to allow
76 modifications of such material outside the IETF Standards Process.
77 Without obtaining an adequate license from the person(s) controlling
78 the copyright in such materials, this document may not be modified
79 outside the IETF Standards Process, and derivative works of it may
80 not be created outside the IETF Standards Process, except to format
81 it for publication as an RFC or to translate it into languages other
82 than English.
83
84 Table of Contents
85
86 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
87 <a href="#section-2">2</a>. Specification of Requirements ...................................<a href="#page-5">5</a>
88 <a href="#section-3">3</a>. Terminology .....................................................<a href="#page-5">5</a>
89 <a href="#section-4">4</a>. General Description .............................................<a href="#page-6">6</a>
90 <a href="#section-5">5</a>. PW Switching and Attachment Circuit Type ........................<a href="#page-9">9</a>
91 <a href="#section-6">6</a>. Applicability ...................................................<a href="#page-9">9</a>
92 <a href="#section-7">7</a>. MPLS-PW to MPLS-PW Switching ...................................<a href="#page-10">10</a>
93 <a href="#section-7.1">7.1</a>. Static Control Plane Switching ............................<a href="#page-10">10</a>
94 <a href="#section-7.2">7.2</a>. Two LDP Control Planes Using the Same FEC Type ............<a href="#page-11">11</a>
95 <a href="#section-7.2.1">7.2.1</a>. FEC 129 Active/Passive T-PE Election Procedure .....<a href="#page-11">11</a>
96 <a href="#section-7.3">7.3</a>. LDP Using FEC 128 to LDP Using the Generalized FEC 129 ....<a href="#page-12">12</a>
97 <a href="#section-7.4">7.4</a>. LDP SP-PE TLV .............................................<a href="#page-12">12</a>
98 <a href="#section-7.4.1">7.4.1</a>. PW Switching Point PE Sub-TLVs .....................<a href="#page-14">14</a>
99 <a href="#section-7.4.2">7.4.2</a>. Adaptation of Interface Parameters .................<a href="#page-15">15</a>
100 <a href="#section-7.5">7.5</a>. Group ID ..................................................<a href="#page-16">16</a>
101 <a href="#section-7.6">7.6</a>. PW Loop Detection .........................................<a href="#page-16">16</a>
102 <a href="#section-8">8</a>. MPLS-PW to L2TPv3-PW Control Plane Switching ...................<a href="#page-16">16</a>
103 <a href="#section-8.1">8.1</a>. Static MPLS and L2TPv3 PWs ................................<a href="#page-17">17</a>
104 <a href="#section-8.2">8.2</a>. Static MPLS PW and Dynamic L2TPv3 PW ......................<a href="#page-17">17</a>
105
106
107
108 <span class="grey">Martini, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
111
112
113 <a href="#section-8.3">8.3</a>. Static L2TPv3 PW and Dynamic LDP/MPLS PW ..................<a href="#page-17">17</a>
114 <a href="#section-8.4">8.4</a>. Dynamic LDP/MPLS and L2TPv3 PWs ...........................<a href="#page-17">17</a>
115 <a href="#section-8.4.1">8.4.1</a>. Session Establishment ..............................<a href="#page-18">18</a>
116 <a href="#section-8.4.2">8.4.2</a>. Adaptation of PW Status message ....................<a href="#page-18">18</a>
117 <a href="#section-8.4.3">8.4.3</a>. Session Tear Down ..................................<a href="#page-18">18</a>
118 <a href="#section-8.5">8.5</a>. Adaptation of L2TPv3 AVPs to Interface Parameters .........<a href="#page-19">19</a>
119 <a href="#section-8.6">8.6</a>. Switching Point TLV in L2TPv3 .............................<a href="#page-20">20</a>
120 <a href="#section-8.7">8.7</a>. L2TPv3 and MPLS PW Data Plane .............................<a href="#page-20">20</a>
121 <a href="#section-8.7.1">8.7.1</a>. Mapping the MPLS Control Word to L2TP ..............<a href="#page-21">21</a>
122 <a href="#section-9">9</a>. Operations, Administration, and Maintenance (OAM) ..............<a href="#page-22">22</a>
123 <a href="#section-9.1">9.1</a>. Extensions to VCCV to Support MS-PWs ......................<a href="#page-22">22</a>
124 <a href="#section-9.2">9.2</a>. OAM from MPLS PW to L2TPv3 PW .............................<a href="#page-22">22</a>
125 <a href="#section-9.3">9.3</a>. OAM Data Plane Indication from MPLS PW to MPLS PW .........<a href="#page-22">22</a>
126 <a href="#section-9.4">9.4</a>. Signaling OAM Capabilities for Switched Pseudowires .......<a href="#page-23">23</a>
127 <a href="#section-9.5">9.5</a>. OAM Capability for MS-PWs Demultiplexed Using MPLS ........<a href="#page-23">23</a>
128 <a href="#section-9.5.1">9.5.1</a>. MS-PW and VCCV CC Type 1 ...........................<a href="#page-24">24</a>
129 <a href="#section-9.5.2">9.5.2</a>. MS-PW and VCCV CC Type 2 ...........................<a href="#page-24">24</a>
130 <a href="#section-9.5.3">9.5.3</a>. MS-PW and VCCV CC Type 3 ...........................<a href="#page-24">24</a>
131 <a href="#section-9.6">9.6</a>. MS-PW VCCV Operations .....................................<a href="#page-24">24</a>
132 <a href="#section-9.6.1">9.6.1</a>. VCCV Echo Message Processing .......................<a href="#page-25">25</a>
133 <a href="#section-9.6.2">9.6.2</a>. Detailed VCCV Procedures ...........................<a href="#page-27">27</a>
134 <a href="#section-10">10</a>. Mapping Switched Pseudowire Status ............................<a href="#page-31">31</a>
135 <a href="#section-10.1">10.1</a>. PW Status Messages Initiated by the S-PE .................<a href="#page-32">32</a>
136 <a href="#section-10.1.1">10.1.1</a>. Local PW2 Transmit Direction Fault ................<a href="#page-33">33</a>
137 <a href="#section-10.1.2">10.1.2</a>. Local PW1 Transmit Direction Fault ................<a href="#page-34">34</a>
138 <a href="#section-10.1.3">10.1.3</a>. Local PW2 Receive Direction Fault .................<a href="#page-34">34</a>
139 <a href="#section-10.1.4">10.1.4</a>. Local PW1 Receive Direction Fault .................<a href="#page-34">34</a>
140 <a href="#section-10.1.5">10.1.5</a>. Clearing Faults ...................................<a href="#page-34">34</a>
141 <a href="#section-10.2">10.2</a>. PW Status Messages and SP-PE TLV Processing ..............<a href="#page-35">35</a>
142 <a href="#section-10.3">10.3</a>. T-PE Processing of PW Status Messages ....................<a href="#page-35">35</a>
143 <a href="#section-10.4">10.4</a>. Pseudowire Status Negotiation Procedures .................<a href="#page-35">35</a>
144 <a href="#section-10.5">10.5</a>. Status Dampening .........................................<a href="#page-35">35</a>
145 <a href="#section-11">11</a>. Peering between Autonomous Systems ............................<a href="#page-35">35</a>
146 <a href="#section-12">12</a>. Congestion Considerations .....................................<a href="#page-36">36</a>
147 <a href="#section-13">13</a>. Security Considerations .......................................<a href="#page-36">36</a>
148 <a href="#section-13.1">13.1</a>. Data Plane Security ......................................<a href="#page-36">36</a>
149 <a href="#section-13.1.1">13.1.1</a>. VCCV Security Considerations ......................<a href="#page-36">36</a>
150 <a href="#section-13.2">13.2</a>. Control Protocol Security ................................<a href="#page-37">37</a>
151 <a href="#section-14">14</a>. IANA Considerations ...........................................<a href="#page-38">38</a>
152 <a href="#section-14.1">14.1</a>. L2TPv3 AVP ...............................................<a href="#page-38">38</a>
153 <a href="#section-14.2">14.2</a>. LDP TLV TYPE .............................................<a href="#page-38">38</a>
154 <a href="#section-14.3">14.3</a>. LDP Status Codes .........................................<a href="#page-38">38</a>
155 <a href="#section-14.4">14.4</a>. L2TPv3 Result Codes ......................................<a href="#page-38">38</a>
156 <a href="#section-14.5">14.5</a>. New IANA Registries ......................................<a href="#page-39">39</a>
157 <a href="#section-15">15</a>. Normative References ..........................................<a href="#page-39">39</a>
158 <a href="#section-16">16</a>. Informative References ........................................<a href="#page-40">40</a>
159 <a href="#section-17">17</a>. Acknowledgments ...............................................<a href="#page-42">42</a>
160 <a href="#section-18">18</a>. Contributors ..................................................<a href="#page-42">42</a>
161
162
163
164 <span class="grey">Martini, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
170
171 The PWE3 Architecture [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>] defines the signaling and
172 encapsulation techniques for establishing Single-Segment Pseudowires
173 (SS-PWs) between a pair of terminating PEs. Multi-Segment
174 Pseudowires (MS-PWs) are most useful in two general cases:
175
176 -i. In some cases it is not possible, desirable, or feasible to
177 establish a PW control channel between the terminating source
178 and destination PEs. At a minimum, PW control channel
179 establishment requires knowledge of and reachability to the
180 remote (terminating) PE IP address. The local (terminating)
181 PE may not have access to this information because of
182 topology, operational, or security constraints.
183
184 An example is the inter-AS L2VPN scenario where the
185 terminating PEs reside in different provider networks (ASes)
186 and it is the practice to cryptographically sign all control
187 traffic exchanged between two networks. Technically, an
188 SS-PW could be used but this would require cryptographic
189 signatures on ALL terminating source and destination PE
190 nodes. An MS-PW allows the providers to confine key
191 administration to just the PW switching points connecting the
192 two domains.
193
194 A second example might involve a single AS where the PW setup
195 path between the terminating PEs is computed by an external
196 entity. Assume that a full mesh of PWE3 control channels is
197 established between PE-A, PE-B, and PE-C. A client-layer L2
198 connection tunneled through a PW is required between
199 terminating PE-A and PE-C. The external entity computes a PW
200 setup path that passes through PE-B. This results in two
201 discrete PW segments being built: one between PE-A and PE-B
202 and one between PE-B and PE-C. The successful client-layer
203 L2 connection between terminating PE-A and terminating PE-C
204 requires that PE-B performs the PWE3 switching process.
205
206 A third example involves the use of PWs in hierarchical
207 IP/MPLS networks. Access networks connected to a backbone
208 use PWs to transport customer payloads between customer sites
209 serviced by the same access network and up to the edge of the
210 backbone where they can be terminated or switched onto a
211 succeeding PW segment crossing the backbone. The use of PWE3
212 switching between the access and backbone networks can
213 potentially reduce the PWE3 control channels and routing
214 information processed by the access network T-PEs.
215
216
217
218
219
220 <span class="grey">Martini, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
223
224
225 It should be noted that PWE3 switching does not help in any
226 way to reduce the amount of PW state supported by each access
227 network T-PE.
228
229 -ii. In some applications, the signaling protocol and
230 encapsulation on each segment of the PW are different. The
231 terminating PEs are connected to networks employing different
232 PW signaling and encapsulation protocols. In this case, it
233 is not possible to use an SS-PW. An MS-PW with the
234 appropriate signaling protocol interworking performed at the
235 PW switching points can enable PW connectivity between the
236 terminating PEs in this scenario.
237
238 A more detailed discussion of the requirements pertaining to MS-PWs
239 can be found in [<a href="./rfc5254" title="&quot;Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)&quot;">RFC5254</a>].
240
241 There are four different mechanisms to establish PWs:
242
243 -i. Static configuration of the PW (MPLS or Layer 2 Tunneling
244 Protocol version 3 (L2TPv3))
245 -ii. LDP using FEC 128 (PWid FEC Element)
246 -iii. LDP using FEC 129 (Generalized PWid FEC Element)
247 -iv. L2TPv3
248
249 While MS-PWs are composed of PW segments, each PW segment cannot
250 function independently, as the PW service is always instantiated
251 across the complete MS-PW. Hence, no PW segments can be signaled or
252 be operational without the complete MS-PW being signaled at once.
253
254 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification of Requirements</span>
255
256 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
257 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
258 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
259
260 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span>
261
262 - PW Terminating Provider Edge (T-PE). A PE where the customer-
263 facing attachment circuits (ACs) are bound to a PW forwarder. A
264 Terminating PE is present in the first and last segments of a
265 MS-PW. This incorporates the functionality of a PE as defined in
266 [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>].
267
268 - Single-Segment Pseudowire (SS-PW). A PW set up directly between
269 two T-PE devices. The PW label is unchanged between the
270 originating and terminating T-PEs.
271
272
273
274
275
276 <span class="grey">Martini, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
279
280
281 - Multi-Segment Pseudowire (MS-PW). A static or dynamically
282 configured set of two or more contiguous PW segments that behave
283 and function as a single point-to-point PW. Each end of an MS-PW
284 by definition MUST terminate on a T-PE.
285
286 - PW Segment. A part of a single-segment or multi-segment PW, which
287 traverses one PSN tunnel in each direction between two PE devices,
288 T-PEs and/or S-PEs (switching PE).
289
290 - PW Switching Provider Edge (S-PE). A PE capable of switching the
291 control and data planes of the preceding and succeeding PW segments
292 in an MS-PW. The S-PE terminates the PSN tunnels of the preceding
293 and succeeding segments of the MS-PW. It therefore includes a PW
294 switching point for an MS-PW. A PW switching point is never the
295 S-PE and the T-PE for the same MS-PW. A PW switching point runs
296 necessary protocols to set up and manage PW segments with other PW
297 switching points and terminating PEs. An S-PE can exist anywhere a
298 PW must be processed or policy applied. It is therefore not
299 limited to the edge of a provider network.
300
301 - MS-PW path. The set of S-PEs that will be traversed in sequence to
302 form the MS-PW.
303
304 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. General Description</span>
305
306 A pseudowire (PW) is a mechanism that carries the essential elements
307 of an emulated service from one PE to one or more other PEs over a
308 PSN as described in Figure 1 and in [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>]. Many providers have
309 deployed PWs as a means of migrating existing (or building new) L2VPN
310 services (e.g., Frame Relay, ATM, or Ethernet) onto a PSN.
311
312 PWs may span multiple domains of the same or different provider
313 networks. In these scenarios, PW control channels (i.e., targeted
314 LDP, L2TPv3) and PWs will cross AS boundaries.
315
316 Inter-AS L2VPN functionality is currently supported, and several
317 techniques employing MPLS encapsulation and LDP signaling have been
318 documented [<a href="./rfc4364" title="&quot;BGP/MPLS IP Virtual Private Networks (VPNs)&quot;">RFC4364</a>]. It is also straightforward to support the same
319 inter-AS L2VPN functionality employing L2TPv3. In this document, we
320 define a methodology to switch a PW between different Packet Switched
321 Network (PSN) domains or between two or more distinct PW control
322 plane domains.
323
324
325
326
327
328
329
330
331
332 <span class="grey">Martini, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
335
336
337 |&lt;-------------- Emulated Service ----------------&gt;|
338 | |
339 | |&lt;-------- Pseudowire ------&gt;| |
340 | | | |
341 | | |&lt;-- PSN Tunnel --&gt;| | |
342 | V V V V |
343 V AC +----+ +----+ AC V
344 +-----+ | | PE1|==================| PE2| | +-----+
345 | |----------|............PW1.............|----------| |
346 | CE1 | | | | | | | | CE2 |
347 | |----------|............PW2.............|----------| |
348 +-----+ ^ | | |==================| | | ^ +-----+
349 ^ | +----+ +----+ | | ^
350 | | Provider Edge 1 Provider Edge 2 | |
351 | | | |
352 Customer | | Customer
353 Edge 1 | | Edge 2
354 | |
355 native service native service
356
357 Figure 1: PWE3 Reference Model
358
359 There are two methods for switching a PW between two PW domains. In
360 the first method (Figure 2), the two separate control plane domains
361 terminate on different PEs.
362
363 |&lt;-------Multi-Segment Pseudowire-------&gt;|
364 | PSN PSN |
365 AC | |&lt;-1-&gt;| |&lt;-2-&gt;| | AC
366 | V V V V V V |
367 | +----+ +-----+ +----+ +----+ |
368 +----+ | | |=====| | | |=====| | | +----+
369 | |-------|......PW1.......|--AC1--|......PW2......|-------| |
370 | CE1| | | | | | | | | | | |CE2 |
371 | |-------|......PW3.......|--AC2--|......PW4......|-------| |
372 +----+ | | |=====| | | |=====| | | +----+
373 ^ +----+ +-----+ +----+ +----+ ^
374 | PE1 PE2 PE3 PE4 |
375 | ^ ^ |
376 | | | |
377 | PW switching points |
378 | |
379 | |
380 |&lt;-------------------- Emulated Service ----------------&gt;|
381
382 Figure 2: PW Switching Using AC Reference Model
383
384
385
386
387
388 <span class="grey">Martini, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
391
392
393 In Figure 2, pseudowires in two separate PSNs are stitched together
394 using native service attachment circuits. PE2 and PE3 only run the
395 control plane for the PSN to which they are directly attached. At
396 PE2 and PE3, PW1 and PW2 are connected using attachment circuit AC1,
397 while PW3 and PW4 are connected using attachment circuit AC2.
398
399 Native |&lt;-----Multi-Segment Pseudowire------&gt;| Native
400 Service | PSN PSN | Service
401 (AC) | |&lt;-Tunnel-&gt;| |&lt;-Tunnel-&gt;| | (AC)
402 | V V 1 V V 2 V V |
403 | +----+ +-----+ +----+ |
404 +----+ | |TPE1|==========|SPE1 |==========|TPE2| | +----+
405 | |------|.....PW.Seg't1....X....PW.Seg't3.....|-------| |
406 | CE1| | | | | | | | | |CE2 |
407 | |------|.....PW.Seg't2....X....PW.Seg't4.....|-------| |
408 +----+ | | |==========| |==========| | | +----+
409 ^ +----+ +-----+ +----+ ^
410 | Provider Edge 1 ^ Provider Edge 2 |
411 | | |
412 | | |
413 | PW switching point |
414 | |
415 |&lt;----------------- Emulated Service ---------------&gt;|
416
417 Figure 3: MS-PW Reference Model
418
419 In Figure 3, SPE1 runs two separate control planes: one toward TPE1,
420 and one toward TPE2. The PW switching point (S-PE) is configured to
421 connect PW Segment 1 and PW Segment 3 together to complete the multi-
422 segment PW between TPE1 and TPE2. PW Segment 1 and PW Segment 3 MUST
423 be of the same PW type, but PSN Tunnel 1 and PSN Tunnel 2 need not be
424 the same technology. In the latter case, if the PW is switched to a
425 different technology, the PEs must adapt the PDU encapsulation
426 between the different PSN technologies. In the case where PSN Tunnel
427 1 and PSN Tunnel 2 are the same technology, the PW PDU does not need
428 to be modified, and PDUs are then switched between the pseudowires at
429 the PW label level.
430
431 It should be noted that it is possible to adapt one PSN technology to
432 a different one, for example, MPLS over an IP encapsulation or
433 Generic Routing Encapsulation (GRE) [<a href="./rfc4023" title="&quot;Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)&quot;">RFC4023</a>], but this is outside
434 the scope of this document. Further, one could perform an
435 interworking function on the PWs themselves at the S-PE, allowing
436 conversion from one PW type to another, but this is also outside the
437 scope of this document.
438
439 This document describes procedures for building multi-segment
440 pseudowires using manual configuration of the switching point PE1.
441
442
443
444 <span class="grey">Martini, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
447
448
449 Other documents may build on this base specification to automate the
450 configuration and selection of S-PE1. All elements of the
451 establishment of end-to-end MS-PWs including routing and signaling
452 are out of scope of this document, and any discussion in this
453 document serves purely as examples. It should also be noted that a
454 PW can traverse multiple PW switching points along it's path, and the
455 edge PEs will not require any specific knowledge of how many S-PEs
456 the PW has traversed (though this may be reported for troubleshooting
457 purposes).
458
459 The general approach taken for MS-PWs is to connect the individual
460 control planes by passing along any signaling information immediately
461 upon reception. First, the S-PE is configured to switch a PW segment
462 from a specific peer to another PW segment destined for a different
463 peer. No control messages are exchanged yet, as the S-PE does not
464 have enough information to actually initiate the PW setup messages.
465 However, if a session does not already exist, a control protocol
466 (LDP/L2TP) session MAY be setup. In this model, the MS-PW setup is
467 starting from the T-PE devices. Once the T-PE is configured, it
468 sends the PW control setup messages. These messages are received by
469 the S-PE, and immediately used to form the PW setup messages for the
470 next SS-PW of the MS-PW.
471
472 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. PW Switching and Attachment Circuit Type</span>
473
474 The PWs in each PSN are established independently, with each PSN
475 being treated as a separate PW domain. For example, in Figure 2 for
476 the case of MPLS PSNs, PW1 is setup between PE1 and PE2 using the LDP
477 targeted session as described in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>], and at the same time a
478 separate pseudowire, PW2, is setup between PE3 and PE4. The ACs for
479 PW1 and PW2 at PE2 and PE3 MUST be configured such that they are the
480 same PW type, e.g., ATM Virtual Channel Connection (VCC), Ethernet
481 VLAN, etc.
482
483 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Applicability</span>
484
485 The general applicability of MS-PWs and their relationship to L2VPNs
486 are described in [<a href="./rfc5659" title="&quot;An Architecture for Multi- Segment Pseudowire Emulation Edge-to-Edge&quot;">RFC5659</a>]. The applicability of a PW type, as
487 specified in the relevant RFC for that encapsulation (e.g., [<a href="./rfc4717" title="&quot;Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks&quot;">RFC4717</a>]
488 for ATM), applies to each segment. This section describes further
489 applicability considerations.
490
491 As with SS-PWs, the performance of any segment will be limited by the
492 performance of the underlying PSN. The performance may be further
493 degraded by the emulation process, and performance degradation may be
494 further increased by traversing multiple PW segments. Furthermore,
495 the overall performance of an MS-PW is no better than the worst-
496 performing segment of that MS-PW.
497
498
499
500 <span class="grey">Martini, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
503
504
505 Since different PSN types may be able to achieve different maximum
506 performance objectives, it is necessary to carefully consider which
507 PSN types are used along the path of an MS-PW.
508
509 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. MPLS-PW to MPLS-PW Switching</span>
510
511 Referencing Figure 3, T-PE1 set up PW Segment 1 using the LDP
512 targeted session as described in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>], at the same time a
513 separate pseudowire, PW Segment 3, is setup to T-PE2. Each PW is
514 configured independently on the PEs, but on S-PE1, PW Segment 1 is
515 connected to PW Segment 3. PDUs are then switched between the
516 pseudowires at the PW label level. Hence, the data plane does not
517 need any special knowledge of the specific pseudowire type. A simple
518 standard MPLS label swap operation is sufficient to connect the two
519 PWs, and in this case the PW adaptation function cannot be used.
520 However, when pushing a new PSN label, the Time to Live (TTL) SHOULD
521 be set to 255, or some other locally configured fixed value.
522
523 This process can be repeated as many times as necessary; the only
524 limitation to the number of S-PEs traversed is imposed by the TTL
525 field of the PW MPLS label. The setting of the TTL of the PW MPLS
526 label is a matter of local policy on the originating PE, but SHOULD
527 be set to 255. However, if the PW PDU contains an Operations,
528 Administration, and Maintenance (OAM) packet, then the TTL can be set
529 to the required value as explained later in this document.
530
531 There are three different mechanisms for MPLS-to-MPLS PW setup:
532
533 -i. Static configuration of the PW
534 -ii. LDP using FEC 128
535 -iii. LDP using the generalized FEC 129
536
537 This results in four distinct PW switching situations that are
538 significantly different and must be considered in detail:
539
540 -i. Switching between two static control planes
541 -ii. Switching between a static and a dynamic LDP control plane
542 -iii. Switching between two LDP control planes using the same FEC
543 type
544 -iv. Switching between LDP using FEC 128 and LDP using the
545 generalized FEC 129
546
547 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Static Control Plane Switching</span>
548
549 In the case of two static control planes, the S-PE MUST be configured
550 to direct the MPLS packets from one PW into the other. There is no
551 control protocol involved in this case. When one of the control
552 planes is a simple static PW configuration and the other control
553
554
555
556 <span class="grey">Martini, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
559
560
561 plane is a dynamic LDP FEC 128 or generalized PW FEC, then the static
562 control plane should be considered similar to an attachment circuit
563 (AC) in the reference model of Figure 1. The switching point PE
564 SHOULD signal the appropriate PW status if it detects a failure in
565 sending or receiving packets over the static PW segment. In the
566 absence of a PW status communication mechanism when the PW is
567 statically configured, the status communicated to the dynamic LDP PW
568 will be limited to local interface failures. In this case, the S-PE
569 PE behaves in a very similar manner to a T-PE, assuming an active
570 signaling role. This means that the S-PE will immediately send the
571 LDP Label Mapping message if the static PW is deemed to be UP.
572
573 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Two LDP Control Planes Using the Same FEC Type</span>
574
575 The S-PE SHOULD assume an initial passive role. This means that when
576 independent PWs are configured on the switching point, the Label
577 Switching Router (LSR) does not advertise the LDP PW FEC mapping
578 until it has received at least one of the two PW LDP FECs from a
579 remote PE. This is necessary because the switching point LSR does
580 not know a priori what the interface parameter field in the initial
581 FEC advertisement will contain.
582
583 If one of the S-PEs doesn't accept an LDP Label Mapping message, then
584 a Label Release message may be sent back to the originator T-PE
585 depending on the cause of the error. LDP liberal label retention
586 mode still applies; hence, if a PE is simply not configured yet, the
587 label mapping is stored for future use. An MS-PW is declared UP only
588 when all the constituent SS-PWs are UP.
589
590 The Pseudowire Identifier (PWid), as defined in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>], is a
591 unique number between each pair of PEs. Hence, each SS-PW that forms
592 an MS-PW may have a different PWid. In the case of the generalized
593 PW FEC, the Attachment Group Identifier (AGI) / Source Attachment
594 Identifier (SAI) / Target Attachment Identifier (TAI) may have to
595 also be different for some, or sometimes all, SS-PWs.
596
597 <span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. FEC 129 Active/Passive T-PE Election Procedure</span>
598
599 When an MS-PW is signaled using FEC 129, each T-PE might
600 independently start signaling the MS-PW. If the MS-PW path is not
601 statically configured, in certain cases the signaling procedure could
602 result in an attempt to set up each direction of the MS-PW through
603 different S-PEs. If an operator wishes to avoid this situation, one
604 of the T-PEs MUST start the PW signaling (active role), while the
605 other waits to receive the LDP label mapping before sending the
606 respective PW LDP Label Mapping message (passive role). When the
607 MS-PW path is not statically configured, the active T-PE (the Source
608
609
610
611
612 <span class="grey">Martini, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
615
616
617 T-PE) and the passive T-PE (the Target T-PE) MUST be identified
618 before signaling is initiated for a given MS-PW.
619
620 The determination of which T-PE assumes the active role SHOULD be
621 done as follows:
622
623 The SAII and TAII are compared as unsigned integers; if the SAII is
624 larger, then the T-PE assumes the active role.
625
626 The selection process to determine which T-PE assumes the active role
627 MAY be superseded by manual provisioning. In this case, one of the
628 T-PEs MUST be set to the active role, and the other one MUST be set
629 to the passive role.
630
631 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. LDP Using FEC 128 to LDP Using the Generalized FEC 129</span>
632
633 When a PE is using the generalized FEC 129, there are two distinct
634 roles that a PE can assume: active and passive. A PE that assumes
635 the active role will send the LDP PW setup message, while a passive
636 role PE will simply reply to an incoming LDP PW setup message. The
637 S-PE will always remain passive until a PWid FEC 128 LDP message is
638 received, which will cause the corresponding generalized PW FEC LDP
639 message to be formed and sent. If a generalized FEC PW LDP message
640 is received while the switching point PE is in a passive role, the
641 corresponding PW FEC 128 LDP message will be formed and sent.
642
643 PWids need to be mapped to the corresponding AGI/TAI/SAI and vice
644 versa. This can be accomplished by local S-PE configuration, or by
645 some other means, such as some form of auto discovery. Such other
646 means are outside the scope of this document.
647
648 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. LDP SP-PE TLV</span>
649
650 The edge-to-edge PW might traverse several switching points, in
651 separate administrative domains. For management and troubleshooting
652 reasons, it is useful to record information about the switching
653 points at the S-PEs that the PW traverses. This is accomplished by
654 using a PW Switching Point PE TLV (SP-PE TLV).
655
656 Sending the SP-PE TLV is OPTIONAL; however, the PE or S-PE MUST
657 process the TLV upon reception. The "U" bit MUST be set for backward
658 compatibility with T-PEs that do not support the MS-PW extensions
659 described in the document. The SP-PE TLV MAY appear only once for
660 each switching point traversed, and it cannot be of length zero. The
661 SP-PE TLV is appended to the PW FEC at each S-PE, and the order of
662 the SP-PE TLVs in the LDP message MUST be preserved. The SP-PE TLV
663
664
665
666
667
668 <span class="grey">Martini, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
671
672
673 is necessary to support some of the Virtual Circuit Connectivity
674 Verification (VCCV) functions for MS-PWs. See <a href="#section-9.5">Section 9.5</a> for more
675 details. The SP-PE TLV is encoded as follows:
676
677 0 1 2 3
678 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
680 |1|0| SP-PE TLV (0x096D) | SP-PE TLV Length |
681 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
682 | Sub-TLV Type | Length | Variable Length Value |
683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
684 | Variable Length Value |
685 | " " " |
686 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
687
688 - SP-PE TLV Length
689
690 Specifies the total length of all the following SP-PE TLV fields
691 in octets.
692
693 - Sub-TLV Type
694
695 Encodes how the Value field is to be interpreted.
696
697 - Length
698
699 Specifies the length of the Value field in octets.
700
701 - Value
702
703 Octet string of Length octets that encodes information to be
704 interpreted as specified by the Type field.
705
706 PW Switching Point PE sub-TLV Types are assigned by IANA according to
707 the process defined in <a href="#section-14">Section 14</a> (IANA Considerations) below.
708
709 For local policy reasons, a particular S-PE can filter out all
710 SP-PE TLVs in a Label Mapping message that traverses it and not
711 include its own SP-PE TLV. In this case, from any upstream PE,
712 it will appear as if this particular S-PE is the T-PE. This
713 might be necessary, depending on local policy, if the S-PE is at
714 the service provider administrative boundary. It should also be
715 noted that because there are no SP-PE TLVs describing the path
716 beyond the S-PE that removed them, VCCV will only work as far as
717 that S-PE.
718
719
720
721
722
723
724 <span class="grey">Martini, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
727
728
729 <span class="h4"><a class="selflink" id="section-7.4.1" href="#section-7.4.1">7.4.1</a>. PW Switching Point PE Sub-TLVs</span>
730
731 The SP-PE TLV contains sub-TLVs that describe various characteristics
732 of the S-PE traversed. The SP-PE TLV MUST contain the appropriate
733 mandatory sub-TLVs specified below. The definitions of the PW
734 Switching Point PE sub-TLVs are as follows:
735
736 - PWid of last PW segment traversed.
737
738 This is only applicable if the last PW segment traversed used
739 LDP FEC 128 to signal the PW. This sub-TLV type contains a PWid
740 in the format of the PWid described in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>]. This is just
741 a 32-bit unsigned integer number.
742
743 - PW Switching Point description string.
744
745 An OPTIONAL description string of text up to 80 characters long.
746 Human-readable text MUST be provided in the UTF-8 character set
747 using the Default Language [<a href="./rfc2277" title="&quot;IETF Policy on Character Sets and Languages&quot;">RFC2277</a>].
748
749 - Local IP address of PW Switching Point.
750
751 The local IPv4 or IPv6 address of the PW Switching Point. This
752 is an OPTIONAL Sub-TLV. In most cases, this will be the local
753 LDP session IP address of the S-PE.
754
755 - Remote IP address of the last PW Switching Point traversed or of
756 the T-PE.
757
758 The IPv4 or IPv6 address of the last PW Switching Point
759 traversed or of the T-PE. This is an OPTIONAL Sub-TLV. In most
760 cases, this will be the remote IP address of the LDP session.
761 This Sub-TLV SHOULD only be included if there are no other SP-PE
762 TLVs present from other S-PEs, or if the remote IP address of
763 the LDP session does not correspond to the "Local IP address of
764 PW Switching Point" TLV value contained in the last SP-PE TLV.
765
766 - The FEC element of last PW segment traversed.
767
768 This is only applicable if the last PW segment traversed used
769 LDP FEC 129 to signal the PW.
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Martini, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
783
784
785 The FEC element of the last PW segment traversed. This is encoded in
786 the following format:
787
788 0 1 2 3
789 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
791 | AGI Type | Length | Value |
792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
793 ~ AGI Value (contd.) ~
794 | |
795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
796 | AII Type | Length | Value |
797 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
798 ~ SAII Value (contd.) ~
799 | |
800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
801 | AII Type | Length | Value |
802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
803 ~ TAII Value (contd.) ~
804 | |
805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
806
807 - L2 PW address of the PW Switching Point (recommended format).
808
809 This sub-TLV type contains an L2 PW address of PW Switching
810 Point in the format described in <a href="./rfc5003#section-3.2">Section&nbsp;3.2 of [RFC5003]</a>. This
811 includes the AII type field and length, as well as the L2 PW
812 address with the AC ID field set to zero.
813
814 <span class="h4"><a class="selflink" id="section-7.4.2" href="#section-7.4.2">7.4.2</a>. Adaptation of Interface Parameters</span>
815
816 [<a id="ref-RFC4447">RFC4447</a>] defines several interface parameters, which are used by the
817 Network Service Processing (NSP) to adapt the PW to the attachment
818 circuit (AC). The interface parameters are only used at the
819 endpoints, and MUST be passed unchanged across the S-PE. However,
820 the following interface parameters MAY be modified as follows:
821
822 - 0x03 Optional Interface Description string
823 This Interface parameter MAY be modified or altogether removed
824 from the FEC element depending on local configuration policies.
825
826 - 0x09 Fragmentation indicator
827 This parameter MAY be inserted in the FEC by the switching point
828 if it is capable of re-assembly of fragmented PW frames
829 according to [<a href="./rfc4623" title="&quot;Pseudowire Emulation Edge- to-Edge (PWE3) Fragmentation and Reassembly&quot;">RFC4623</a>].
830
831
832
833
834
835
836 <span class="grey">Martini, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
839
840
841 - 0x0C VCCV parameter
842 This Parameter contains the Control Channel (CC) type and
843 Connectivity Verification (CV) type bit fields. The CV type bit
844 field MUST be reset to reflect the CV type supported by the
845 S-PE. The CC type bit field MUST have bit 1 "Type 2: MPLS
846 Router Alert Label" set to 0. The other bit fields MUST be
847 reset to reflect the CC type supported by the S-PE.
848
849 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Group ID</span>
850
851 The Group ID (GR ID) is used to reduce the number of status messages
852 that need to be sent by the PE advertising the PW FEC. The GR ID has
853 local significance only, and therefore MUST be mapped to a unique GR
854 ID allocated by the S-PE.
855
856 <span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a>. PW Loop Detection</span>
857
858 A switching point PE SHOULD inspect the PW Switching Point PE TLV, to
859 verify that its own IP address does not appear in it. If the PE's IP
860 address appears in a received PW Switching Point PE TLV, the PE
861 SHOULD break the loop and send a label release message with the
862 following error code:
863
864 Value E Description
865 0x0000003A 0 PW Loop Detected
866
867 If an S-PE along the MS-PW removed all SP-PE TLVs, as mentioned
868 above, this loop detection method will fail.
869
870 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. MPLS-PW to L2TPv3-PW Control Plane Switching</span>
871
872 Both MPLS and L2TPv3 PWs may be static or dynamic. This results in
873 four possibilities when switching between L2TPv3 and MPLS.
874
875 -i. Switching between static MPLS and L2TPv3 PWs
876 -ii. Switching between a static MPLS PW and a dynamic L2TPv3 PW
877 -iii. Switching between a static L2TPv3 PW and a dynamic LDP/MPLS
878 PW
879 -iv. Switching between a dynamic LDP/MPLS PW and a dynamic L2TPv3
880 PW
881
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Martini, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
895
896
897 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Static MPLS and L2TPv3 PWs</span>
898
899 In the case of two static control planes, the S-PE MUST be configured
900 to direct packets from one PW into the other. There is no control
901 protocol involved in this case. The configuration MUST include which
902 MPLS PW Label maps to which L2TPv3 Session ID (and associated Cookie,
903 if present) as well as which MPLS Tunnel Label maps to which PE
904 destination IP address.
905
906 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Static MPLS PW and Dynamic L2TPv3 PW</span>
907
908 When a statically configured MPLS PW is switched to a dynamic L2TPv3
909 PW, the static control plane should be considered identical to an
910 attachment circuit (AC) in the reference model of Figure 1. The
911 switching point PE SHOULD signal the appropriate PW status if it
912 detects a failure in sending or receiving packets over the static PW.
913 Because the PW is statically configured, the status communicated to
914 the dynamic L2TPv3 PW will be limited to local interface failures.
915 In this case, the S-PE behaves in a very similar manner to a T-PE,
916 assuming an active role.
917
918 <span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Static L2TPv3 PW and Dynamic LDP/MPLS PW</span>
919
920 When a statically configured L2TPv3 PW is switched to a dynamic
921 LDP/MPLS PW, then the static control plane should be considered
922 identical to an attachment circuit (AC) in the reference model of
923 Figure 1. The switching point PE SHOULD signal the appropriate PW
924 status (via an L2TPv3 Set-Link-Info (SLI) message) if it detects a
925 failure in sending or receiving packets over the static PW. Because
926 the PW is statically configured, the status communicated to the
927 dynamic LDP/MPLS PW will be limited to local interface failures. In
928 this case, the S-PE behaves in a very similar manner to a T-PE,
929 assuming an active role.
930
931 <span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Dynamic LDP/MPLS and L2TPv3 PWs</span>
932
933 When switching between dynamic PWs, the switching point always
934 assumes an initial passive role. Thus, it does not initiate an
935 LDP/MPLS or L2TPv3 PW until it has received a connection request
936 (Label Mapping or Incoming-Call-Request (ICRQ)) from one side of the
937 node. Note that while MPLS PWs are made up of two unidirectional
938 Label Switched Paths (LSPs) bonded together by FEC identifiers,
939 L2TPv3 PWs are bidirectional in nature, setup via a three-message
940 exchange (ICRQ, Incoming-Call-Reply (ICRP), and Incoming-Call-
941 Connected (ICCN)). Details of Session Establishment, Tear Down, and
942 PW Status signaling are detailed below.
943
944
945
946
947
948 <span class="grey">Martini, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
951
952
953 <span class="h4"><a class="selflink" id="section-8.4.1" href="#section-8.4.1">8.4.1</a>. Session Establishment</span>
954
955 When the S-PE receives an L2TPv3 ICRQ message, the identifying AVPs
956 included in the message are mapped to FEC identifiers and sent in an
957 LDP Label Mapping message. Conversely, if an LDP Label Mapping
958 message is received, it is either mapped to an ICRP message or causes
959 an L2TPv3 session to be initiated by sending an ICRQ.
960
961 Following are two example exchanges of messages between LDP and
962 L2TPv3. The first is a case where an L2TPv3 T-PE initiates an MS-PW;
963 the second is a case where an MPLS T-PE initiates an MS-PW.
964
965 PE 1 (L2TPv3) PW Switching Node PE3 (MPLS/LDP)
966
967 AC "Up"
968 L2TPv3 ICRQ ---&gt;
969 LDP Label Mapping ---&gt;
970 AC "Up"
971 &lt;--- LDP Label Mapping
972 &lt;--- L2TPv3 ICRP
973 L2TPv3 ICCN ---&gt;
974 &lt;-------------------- MS-PW Established ------------------&gt;
975 PE 1 (MPLS/LDP) PW Switching Node PE3 (L2TPv3)
976
977 AC "Up"
978 LDP Label Mapping ---&gt;
979 L2TPv3 ICRQ ---&gt;
980 &lt;--- L2TPv3 ICRP
981 &lt;--- LDP Label Mapping
982 L2TPv3 ICCN ---&gt;
983 AC "Up"
984 &lt;-------------------- MS-PW Established ------------------&gt;
985
986 <span class="h4"><a class="selflink" id="section-8.4.2" href="#section-8.4.2">8.4.2</a>. Adaptation of PW Status Message</span>
987
988 L2TPv3 uses the SLI message to indicate an interface status change
989 (such as the interface transitioning from "Up" or "Down"). MPLS/LDP
990 PWs either signal this via an LDP Label Withdraw or the PW Status
991 Notification message defined in <a href="./rfc4447#section-4.4">Section&nbsp;4.4 of [RFC4447]</a>. The LDP
992 status TLV bit SHOULD be mapped to the L2TPv3 equivalent Extended
993 Circuit Status Values TLV specified in [<a href="./rfc5641" title="&quot;Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status Values&quot;">RFC5641</a>].
994
995 <span class="h4"><a class="selflink" id="section-8.4.3" href="#section-8.4.3">8.4.3</a>. Session Tear Down</span>
996
997 L2TPv3 uses a single message, Call-Disconnect-Notify (CDN), to tear
998 down a pseudowire. The CDN message translates to a Label Withdraw
999 message in LDP. Following are two example exchanges of messages
1000
1001
1002
1003
1004 <span class="grey">Martini, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1007
1008
1009 between LDP and L2TPv3. The first is a case where an L2TPv3 T-PE
1010 initiates the termination of an MS-PW; the second is a case where an
1011 MPLS T-PE initiates the termination of an MS-PW.
1012
1013 PE 1 (L2TPv3) PW Switching Node PE3 (MPLS/LDP)
1014
1015 AC "Down"
1016 L2TPv3 CDN ---&gt;
1017 LDP Label Withdraw ---&gt;
1018 AC "Down"
1019 &lt;-- LDP Label Release
1020
1021 &lt;--------------- MS-PW Data Path Down ------------------&gt;
1022 PE 1 (MPLS LDP) PW Switching Node PE3 (L2TPv3)
1023
1024 AC "Down"
1025 LDP Label Withdraw ---&gt;
1026 L2TPv3 CDN --&gt;
1027 &lt;-- LDP Label Release
1028 AC "Down"
1029
1030 &lt;---------------- MS-PW Data Path Down ------------------&gt;
1031
1032 <span class="h3"><a class="selflink" id="section-8.5" href="#section-8.5">8.5</a>. Adaptation of L2TPv3 AVPs to Interface Parameters</span>
1033
1034 [<a id="ref-RFC4447">RFC4447</a>] defines several interface parameters that MUST be mapped to
1035 the equivalent AVPs in L2TPv3 setup messages.
1036
1037 * Interface MTU
1038
1039 The Interface MTU parameter is mapped directly to the L2TP
1040 "Interface Maximum Transmission Unit" AVP defined in [<a href="./rfc4667" title="&quot;Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)&quot;">RFC4667</a>].
1041
1042 * Max Number of Concatenated ATM cells
1043
1044 This interface parameter is mapped directly to the L2TP "ATM
1045 Maximum Concatenated Cells AVP" described in <a href="./rfc4454#section-6">Section&nbsp;6 of
1046 [RFC4454]</a>.
1047
1048 * PW Type
1049
1050 The PW Type defined in [<a href="./rfc4446" title="&quot;IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)&quot;">RFC4446</a>] is mapped to the L2TPv3
1051 "Pseudowire Type" AVP defined in [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>].
1052
1053 * PWid (FEC 128)
1054
1055 For FEC 128, the PWid is mapped directly to the L2TPv3 "Remote
1056 End ID" AVP defined in [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>].
1057
1058
1059
1060 <span class="grey">Martini, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1063
1064
1065 * Generalized FEC 129 SAI/TAI
1066
1067 <a href="./rfc4667#section-4.3">Section&nbsp;4.3 of [RFC4667]</a> defines how to encode the SAI and TAI
1068 parameters. These can be mapped directly.
1069
1070 Other interface parameter mappings are unsupported when switching
1071 between LDP/MPLS and L2TPv3 PWs.
1072
1073 <span class="h3"><a class="selflink" id="section-8.6" href="#section-8.6">8.6</a>. PW Switching Point PE TLV in L2TPv3</span>
1074
1075 When translating between LDP and L2TPv3 control messages, the PW
1076 Switching Point PE TLV described earlier in this document is carried
1077 in a single variable-length L2TP AVP present in the ICRQ and ICRP
1078 messages, and optionally in the ICCN message.
1079
1080 The L2TP "PW Switching Point AVP" is Attribute Type 101. The AVP MAY
1081 be hidden (the L2TP AVP H-bit may be 0 or 1), the length of the AVP
1082 is 6 plus the length of the series of Switching Point PE sub-TLVs
1083 included in the AVP, and the AVP MUST NOT be marked Mandatory (the
1084 L2TP AVP M-bit MUST be 0).
1085
1086 <span class="h3"><a class="selflink" id="section-8.7" href="#section-8.7">8.7</a>. L2TPv3 and MPLS PW Data Plane</span>
1087
1088 When switching between an MPLS and L2TP PW, packets are sent in their
1089 entirety from one PW to the other, replacing the MPLS label stack
1090 with the L2TPv3 and IP header or vice versa.
1091
1092 <a href="./rfc3985#section-5.4">Section&nbsp;5.4 of [RFC3985]</a> discusses the purpose of the various shim
1093 headers necessary for enabling a pseudowire over an IP or MPLS PSN.
1094 For L2TPv3, the Payload Convergence and Sequencing function is
1095 carried out via the Default L2-Specific Sublayer defined in
1096 [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>]. For MPLS, these two functions (together with PSN
1097 Convergence) are carried out via the MPLS Control Word. Since these
1098 functions are different between MPLS and L2TPv3, interworking between
1099 the two may be necessary.
1100
1101 The L2TP L2-Specific Sublayer and MPLS Control Word are shim headers,
1102 which in some cases are not necessary to be present at all. For
1103 example, an Ethernet PW with sequencing disabled will generally not
1104 require an MPLS Control Word or L2TP Default L2-Specific Sublayer to
1105 be present at all. In this case, Ethernet frames are simply sent
1106 from one PW to the other without any modification beyond the MPLS and
1107 L2TP/IP encapsulation and decapsulation.
1108
1109 The following section offers guidelines for how to interwork between
1110 L2TP and MPLS for those cases where the Payload Convergence,
1111 Sequencing, or PSN Convergence functions are necessary on one or both
1112 sides of the switching node.
1113
1114
1115
1116 <span class="grey">Martini, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1119
1120
1121 <span class="h4"><a class="selflink" id="section-8.7.1" href="#section-8.7.1">8.7.1</a>. Mapping the MPLS Control Word to L2TP</span>
1122
1123 The MPLS Control Word consists of (from left to right):
1124
1125 0 1 2 3
1126 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1128 |0 0 0 0| Reserved | Length | Sequence Number |
1129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1130
1131 -i. These bits are always zero in an MPLS PW PDU. It is not
1132 necessary to map them to L2TP.
1133
1134 -ii. These six bits may be used for Payload Convergence depending
1135 on the PW type. For ATM, the first four of these bits are
1136 defined in [<a href="./rfc4717" title="&quot;Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks&quot;">RFC4717</a>]. These map directly to the bits
1137 defined in [<a href="./rfc4454" title="&quot;Asynchronous Transfer Mode (ATM) over Layer 2 Tunneling Protocol Version 3 (L2TPv3)&quot;">RFC4454</a>]. For Frame Relay, these bits indicate
1138 how to set the bits in the Frame Relay header that must be
1139 regenerated for L2TP as it carries the Frame Relay header
1140 intact.
1141
1142 -iii. L2TP determines its payload length from IP. Thus, this
1143 Length field need not be carried directly to L2TP. This
1144 Length field will have to be calculated and inserted for
1145 MPLS when necessary.
1146
1147 -iv. The Default L2-Specific Sublayer has a sequence number with
1148 different semantics than that of the MPLS Control Word.
1149 This difference eliminates the possibility of supporting
1150 sequencing across the MS-PW by simply carrying the sequence
1151 number through the switching point transparently. As such,
1152 sequence numbers MAY be supported by checking the sequence
1153 numbers of packets arriving at the switching point and
1154 regenerating a new sequence number in the appropriate format
1155 for the PW on egress. If this type of sequence interworking
1156 at the switching node is not supported, and a T-PE requests
1157 sequencing of all packets via the L2TP control channel
1158 during session setup, the switching node SHOULD NOT allow
1159 the session to be established by sending a CDN message with
1160 Result Code set to 31 "Sequencing not supported".
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Martini, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Operations, Administration, and Maintenance (OAM)</span>
1178
1179 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Extensions to VCCV to Support MS-PWs</span>
1180
1181 Single-segment pseudowires are signaled using the Virtual Circuit
1182 Connectivity Verification (VCCV) parameter included in the interface
1183 parameter field of the PWid FEC TLV or the interface parameter sub-
1184 TLV of the Generalized PWid FEC TLV as described in [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>]. When
1185 a switching point exists between PE nodes, it is required to be able
1186 to continue operating VCCV end-to-end across a switching point and to
1187 provide the ability to trace the path of the MS-PW over any number of
1188 segments.
1189
1190 This document provides a method for achieving these two objectives.
1191 This method is based on reusing the existing VCCV Control Word (CW)
1192 and decrementing the TTL of the PW label at each S-PE in the path of
1193 the MS-PW.
1194
1195 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. OAM from MPLS PW to L2TPv3 PW</span>
1196
1197 When an MS-PW includes SS-PWs that use the L2TPv3, the MPLS PW OAM
1198 MUST be terminated at the S-PE connecting the L2TPv3 and MPLS
1199 segments. Status information received in a particular PW segment can
1200 then be used to generate the appropriate status messages on the
1201 following PW segment. In the case of L2TPV3, the status bits in the
1202 circuit status AVP defined in <a href="./rfc3931#section-5.4.5">Section&nbsp;5.4.5 of [RFC3931]</a> and Extended
1203 Circuit Status Values defined in [<a href="./rfc5641" title="&quot;Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status Values&quot;">RFC5641</a>] can be mapped directly to
1204 the PW status bits defined in <a href="./rfc4447#section-5.4.3">Section&nbsp;5.4.3 of [RFC4447]</a>.
1205
1206 VCCV messages are specific to the MPLS data plane and cannot be used
1207 for an L2TPv3 PW segment. Therefore, the S-PE MUST NOT send the VCCV
1208 parameter included in the interface parameter field of the PWid FEC
1209 TLV or the sub-TLV interface parameter of the Generalized PWid FEC
1210 TLV. It might be possible to translate VCCV messages from L2TPv3 PW
1211 segments to MPLS PW segments and vice versa; however, this topic is
1212 left for further study.
1213
1214 <span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. OAM Data Plane Indication from MPLS PW to MPLS PW</span>
1215
1216 As stated above, the S-PE MUST perform a standard MPLS label swap
1217 operation on the MPLS PW label. By the rules defined in [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>],
1218 the PW label TTL MUST be decreased at every S-PE. Once the PW label
1219 TTL reaches the value of 0, the packet is sent to the control plane
1220 to be processed. Hence, by controlling the PW TTL value of the PW
1221 label, it is possible to select exactly which S-PE will respond to
1222 the VCCV packet.
1223
1224
1225
1226
1227
1228 <span class="grey">Martini, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1231
1232
1233 <span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a>. Signaling OAM Capabilities for Switched Pseudowires</span>
1234
1235 Similarly to SS-PW, MS-PW VCCV capabilities are signaled using the
1236 VCCV parameter included in the interface parameter field of the PWid
1237 FEC TLV or the sub-TLV interface parameter of the Generalized PWid
1238 FEC TLV as described in [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>].
1239
1240 In Figure 3, T-PE1 uses the VCCV parameter included in the interface
1241 parameter field of the PWid FEC TLV or the sub-TLV interface
1242 parameter of the Generalized PWid FEC TLV to indicate to the far-end
1243 T-PE2 what VCCV capabilities T-PE1 supports. This is the same VCCV
1244 parameter as would be used if T-PE1 and T-PE2 were connected
1245 directly. S-PE2, which is a PW switching point, as part of the
1246 adaptation function for interface parameters, processes locally the
1247 VCCV parameter then passes it to T-PE2. If there were multiple S-PEs
1248 on the path between T-PE1 and T-PE2, each would carry out the same
1249 processing, passing along the VCCV parameter. The local processing
1250 of the VCCV parameter removes CC Types specified by the originating
1251 T-PE that are not supported on the S-PE. For example, if T-PE1
1252 indicates that it supports CC Types 1, 2, and 3, then the S-PE
1253 removes the Router Alert CC Type 2, leaving the rest of the TLV
1254 unchanged, and passes the modified VCCV parameter to the next S-PE
1255 along the path.
1256
1257 The far end T-PE (T-PE2) receives the VCCV parameter indicating only
1258 the CC Types that are supported by the initial T-PE (T-PE1) and all
1259 S-PEs along the PW path.
1260
1261 <span class="h3"><a class="selflink" id="section-9.5" href="#section-9.5">9.5</a>. OAM Capability for MS-PWs Demultiplexed Using MPLS</span>
1262
1263 The VCCV parameter ID is defined as follows in [<a href="./rfc4446" title="&quot;IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)&quot;">RFC4446</a>]:
1264
1265 Parameter ID Length Description
1266 0x0c 4 VCCV
1267
1268 The format of the VCCV parameter field is as follows:
1269
1270 0 1 2 3
1271 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1273 | 0x0c | 0x04 | CC Types | CV Types |
1274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1275
1276 Bit 0 (0x01) - Type 1: PWE3 Control Word with 0001b as
1277 first nibble as defined in [<a href="./rfc4385" title="&quot;Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN&quot;">RFC4385</a>]
1278 Bit 1 (0x02) - Type 2: MPLS Router Alert Label
1279 Bit 2 (0x04) - Type 3: MPLS Demultiplexor PW Label with
1280 TTL == 1 (Type 3).
1281
1282
1283
1284 <span class="grey">Martini, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1287
1288
1289 <span class="h4"><a class="selflink" id="section-9.5.1" href="#section-9.5.1">9.5.1</a>. MS-PW and VCCV CC Type 1</span>
1290
1291 VCCV CC Type 1 can be used for MS-PWs. However, if the CW is enabled
1292 on user packets, VCCV CC Type 1 MUST be used according to the rules
1293 in [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>]. When using CC Type 1 for MS-PWs, the PE transmitting
1294 the VCCV packet MUST set the TTL to the appropriate value to reach
1295 the destination S-PE. However, if the packet is destined for the
1296 T-PE, the TTL can be set to any value that is sufficient for the
1297 packet to reach the T-PE.
1298
1299 <span class="h4"><a class="selflink" id="section-9.5.2" href="#section-9.5.2">9.5.2</a>. MS-PW and VCCV CC Type 2</span>
1300
1301 VCCV CC Type 2 is not supported for MS-PWs and MUST be removed from a
1302 VCCV parameter field by the S-PE.
1303
1304 <span class="h4"><a class="selflink" id="section-9.5.3" href="#section-9.5.3">9.5.3</a>. MS-PW and VCCV CC Type 3</span>
1305
1306 VCCV CC Type 3 can be used for MS-PWs; however, if the CW is enabled,
1307 VCCV Type 1 is preferred according to the rules in [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>]. Note
1308 that for using the VCCV Type 3, TTL method, the PE will set the PW
1309 label TTL to the appropriate value necessary to reach the target PE;
1310 otherwise, the VCCV packet might be forwarded over the AC to the
1311 Customer Premise Equipment (CPE).
1312
1313 <span class="h3"><a class="selflink" id="section-9.6" href="#section-9.6">9.6</a>. MS-PW VCCV Operations</span>
1314
1315 This document specifies four VCCV operations:
1316
1317 -i. End-to-end MS-PW connectivity verification. This operation
1318 enables the connectivity of the MS-PW to be tested from
1319 source T-PE to destination T-PE. In order to do this, the
1320 sending T-PE must include the FEC used in the last segment
1321 of the MS-PW to the destination T-PE in the VCCV-Ping echo
1322 request. This information is either configured at the
1323 sending T-PE or is obtained by processing the corresponding
1324 sub-TLVs of the optional SP-PE TLV, as described below.
1325
1326 -ii. Partial MS-PW connectivity verification. This operation
1327 enables the connectivity of any contiguous subset of the
1328 segments of an MS-PW to be tested from the source T-PE or a
1329 source S-PE to a destination S-PE or T-PE. Again, the FEC
1330 used on the last segment to be tested must be included in
1331 the VCCV-Ping echo request message. This information is
1332 determined by the sending T-PE or S-PE as in (i) above.
1333
1334 -iii. MS-PW path verification. This operation verifies the path
1335 of the MS-PW, as returned by the SP-PE TLV, against the
1336 actual data path of the MS-PW. The sending T-PE or S-PE
1337
1338
1339
1340 <span class="grey">Martini, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1343
1344
1345 iteratively sends a VCCV echo request to each S-PE along the
1346 MS-PW path, using the FEC for the corresponding MS-PW
1347 segment in the SP-PE TLV. If the SP-PE TLV information is
1348 correct, then a VCCV echo reply showing that this is a valid
1349 router for the FEC will be received. However, if the SP-PE
1350 TLV information is incorrect, then this operation enables
1351 the first incorrect switching point to be determined, but
1352 not the actual path of the MS-PW beyond that. This
1353 operation cannot be used when the MS-PW is statically
1354 configured or when the SP-PE TLV is not supported. The
1355 processing of the PW Switching Point PE TLV used for this
1356 operation is described below. This operation is OPTIONAL.
1357
1358 -iv. MS-PW path trace. This operation traces the data path of
1359 the MS-PW using FECs included in the Target FEC stack TLV
1360 [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>] returned by S-PEs or T-PEs in an echo reply
1361 message. The sending T-PE or S-PE uses this information to
1362 recursively test each S-PE along the path of the MS-PW in a
1363 single operation in a similar manner to LSP trace. This
1364 operation is able to determine the actual data path of the
1365 MS-PW, and can be used for both statically configured and
1366 signaled MS-PWs. Support for this operation is OPTIONAL.
1367
1368 Note that the above operations rely on intermediate S-PEs and/or the
1369 destination T-PE to include the PW Switching Point PE TLV as a part
1370 of the MS-PW setup process, or to include the Target FEC stack TLV in
1371 the VCCV echo reply message. For various reasons, e.g., privacy or
1372 security of the S-PE/T-PE, this information may not be available to
1373 the source T-PE. In these cases, manual configuration of the FEC MAY
1374 still be used.
1375
1376 <span class="h4"><a class="selflink" id="section-9.6.1" href="#section-9.6.1">9.6.1</a>. VCCV Echo Message Processing</span>
1377
1378 The challenge for the control plane is to be able to build the VCCV
1379 echo request packet with the necessary information to reach the
1380 desired S-PE or T-PE, for example, the target FEC 128 PW sub-TLV of
1381 the downstream PW segment that the packet is destined for. This
1382 could be even more difficult in situations in which the MS-PW spans
1383 different providers and Autonomous Systems.
1384
1385 For example, in Figure 3, T-PE1 has the FEC 128 of the segment (PW
1386 segment 1), but it does not readily have the information required to
1387 compose the FEC 128 of the following segment (PW segment 3), if a
1388 VCCV echo request is to be sent to T-PE2. This can be achieved by
1389 the methods described in the following subsections.
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Martini, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1399
1400
1401 <span class="h5"><a class="selflink" id="section-9.6.1.1" href="#section-9.6.1.1">9.6.1.1</a>. Sending a VCCV Echo Request</span>
1402
1403 When performing a partial or end-to-end connectivity or path
1404 verification, the sender of the echo request message requires the FEC
1405 of the last segment to the target S-PE/T-PE node. This information
1406 can either be configured manually or be obtained by inspecting the
1407 corresponding sub-TLVs of the PW Switching Point PE TLV.
1408
1409 The necessary SP-PE sub-TLVs are:
1410
1411 Type Description
1412 0x01 PWid of last PW segment traversed
1413 0x03 Local IP address of PW Switching Point
1414 0x04 Remote IP address of last PW Switching Point traversed or
1415 of the T-PE
1416
1417 When performing an OPTIONAL MS-PW path trace operation, the T-PE will
1418 automatically learn the target FEC by probing, one by one, the S-PEs
1419 of the MS-PW path, using the FEC returned in the Target FEC stack of
1420 the previous VCCV echo reply.
1421
1422 <span class="h5"><a class="selflink" id="section-9.6.1.2" href="#section-9.6.1.2">9.6.1.2</a>. Receiving a VCCV Echo Request</span>
1423
1424 Upon receiving a VCCV echo request, the control plane on S-PEs (or
1425 the target node of each segment of the MS-PW) validates the request
1426 and responds to the request with an echo reply consisting of a return
1427 code of 8 (label switched at stack depth) indicating that it is an
1428 S-PE and not the egress router for the MS-PW.
1429
1430 S-PEs that wish to reveal their downstream next-hop in a trace
1431 operation should include the FEC of the downstream PW segment in the
1432 Target FEC stack (as per Sections <a href="#section-3.2">3.2</a> and <a href="#section-4.5">4.5</a> of [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>]) of the
1433 echo reply message. FEC 128 PWs MUST use the format shown in <a href="./rfc4379#section-3.2.9">Section</a>
1434 <a href="./rfc4379#section-3.2.9">3.2.9 of [RFC4379]</a> for the sub-TLV in the Target FEC stack, while FEC
1435 129 PWs MUST use the format shown in <a href="./rfc4379#section-3.2.10">Section&nbsp;3.2.10 of [RFC4379]</a> for
1436 the sub-TLV in the Target FEC stack. Note that an S-PE MUST NOT
1437 include this FEC information in the reply if it has been configured
1438 not to do so for administrative reasons or for reasons explained
1439 previously.
1440
1441 If the node is the T-PE or the egress node of the MS-PW, it responds
1442 to the echo request with an echo reply with a return code of 3
1443 (Egress Router).
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Martini, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1455
1456
1457 <span class="h5"><a class="selflink" id="section-9.6.1.3" href="#section-9.6.1.3">9.6.1.3</a>. Receiving a VCCV Echo Reply</span>
1458
1459 The operation to be taken by the node receiving the echo reply in
1460 response to an echo request depends on the VCCV mode of operation
1461 described above. See <a href="#section-9.5.2">Section 9.5.2</a> for detailed procedures.
1462
1463 <span class="h4"><a class="selflink" id="section-9.6.2" href="#section-9.6.2">9.6.2</a>. Detailed VCCV Procedures</span>
1464
1465 There are two similar methods of verifying the MS-PW path: Path Trace
1466 and Path Verification. Path Trace does not use the LDP control plane
1467 to obtain information on the path to verify, so this method is well
1468 suited if portions of the MS-PW are statically configured SS-PWs.
1469 The Path Verification method relies on information obtained from the
1470 LDP control plane, and hence offers better verification of the
1471 current forwarding behavior compared to the LDP signaled forwarding
1472 information of the MS-PW path. However, in the case where there are
1473 statically signaled SS-PWs in the MS-PW path, the path information is
1474 unavailable and must be programmed manually.
1475
1476 <span class="h5"><a class="selflink" id="section-9.6.2.1" href="#section-9.6.2.1">9.6.2.1</a>. End-to-End Connectivity Verification between T-PEs</span>
1477
1478 In Figure 3, if T-PE1, S-PE, and T-PE2 support Control Word, the PW
1479 control plane will automatically negotiate the use of the CW. VCCV
1480 CC Type 3 will function correctly whether or not the CW is enabled on
1481 the PW. However, VCCV Type 1 (which can be use for end-to-end
1482 verification only) is only supported if the CW is enabled.
1483
1484 At the S-PE, the data path operations include an outer label pop,
1485 inner label swap, and new outer label push. Note that there is no
1486 requirement for the S-PE to inspect the CW. Thus, the end-to-end
1487 connectivity of the multi-segment pseudowire can be verified by
1488 performing all of the following steps:
1489
1490 -i. The T-PE forms a VCCV-Ping echo request message with the FEC
1491 matching that of the last PW segment to the destination
1492 T-PE.
1493
1494 -ii. The T-PE sets the inner PW label TTL to the exact value to
1495 allow the packet to reach the far-end T-PE. (The value is
1496 determined by counting the number of S-PEs from the control
1497 plane information.) Alternatively, if CC Type 1 is
1498 supported, the packet can be encapsulated according to CC
1499 Type 1 in [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>].
1500
1501 -iii. The T-PE sends a VCCV packet that will follow the exact same
1502 data path at each S-PE as that taken by data packets.
1503
1504
1505
1506
1507
1508 <span class="grey">Martini, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1511
1512
1513 -iv. The S-PE may perform an outer label pop, if Penultimate Hop
1514 Popping (PHP) is disabled, and will perform an inner label
1515 swap with TTL decrement and a new outer label push.
1516
1517 -v. There is no requirement for the S-PE to inspect the CW.
1518
1519 -vi. The VCCV packet is diverted to VCCV control processing at
1520 the destination T-PE.
1521
1522 -vii. The destination T-PE replies using the specified reply mode,
1523 i.e., reverse PW path or IP path.
1524
1525 <span class="h5"><a class="selflink" id="section-9.6.2.2" href="#section-9.6.2.2">9.6.2.2</a>. Partial Connectivity Verification from T-PE</span>
1526
1527 In order to trace part of the multi-segment pseudowire, the TTL of
1528 the PW label may be used to force the VCCV message to 'pop out' at an
1529 intermediate node. When the TTL expires, the S-PE can determine that
1530 the packet is a VCCV packet either by checking the CW or (if the CW
1531 is not in use) by checking for a valid IP header with UDP destination
1532 port 3503. The packet should then be diverted to VCCV processing.
1533
1534 In Figure 3, if T-PE1 sends a VCCV message with the TTL of the PW
1535 label equal to 1, the TTL will expire at the S-PE. T-PE1 can thus
1536 verify the first segment of the pseudowire.
1537
1538 The VCCV packet is built according to <a href="./rfc4379#section-3.2.9">[RFC4379], Section&nbsp;3.2.9</a> for
1539 FEC 128, or <a href="#section-3.2.10">Section 3.2.10</a> for FEC 129. All the information
1540 necessary to build the VCCV LSP ping packet is collected by
1541 inspecting the S-PE TLVs.
1542
1543 Note that this use of the TTL is subject to the caution expressed in
1544 [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>]. If a penultimate LSR between S-PEs or between an S-PE and
1545 a T-PE manipulates the PW label TTL, the VCCV message may not emerge
1546 from the MS-PW at the correct S-PE.
1547
1548 <span class="h5"><a class="selflink" id="section-9.6.2.3" href="#section-9.6.2.3">9.6.2.3</a>. Partial Connectivity Verification between S-PEs</span>
1549
1550 Assuming that all nodes along an MS-PW support the Control Word CC
1551 Type 3, VCCV between S-PEs may be accomplished using the PW label TTL
1552 as described above. In Figure 3, the S-PE may verify the path
1553 between it and T-PE2 by sending a VCCV message with the PW label TTL
1554 set to 1. Given a more complex network with multiple S-PEs, an S-PE
1555 may verify the connectivity between it and an S-PE two segments away
1556 by sending a VCCV message with the PW label TTL set to 2. Thus, an
1557 S-PE can diagnose connectivity problems by successively increasing
1558 the TTL. All the information needed to build the proper VCCV echo
1559
1560
1561
1562
1563
1564 <span class="grey">Martini, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1567
1568
1569 request packet (as described in [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>], Sections <a href="#section-3.2.9">3.2.9</a> or <a href="#section-3.2.10">3.2.10</a>)
1570 is obtained automatically from the LDP label mapping that contains
1571 S-PE TLVs.
1572
1573 <span class="h5"><a class="selflink" id="section-9.6.2.4" href="#section-9.6.2.4">9.6.2.4</a>. MS-PW Path Verification</span>
1574
1575 As an example, in Figure 3, VCCV trace can be performed on the MS-PW
1576 originating from T-PE1 by a single operational command. The
1577 following process ensues:
1578
1579 -i. T-PE1 sends a VCCV echo request with TTL set to 1 and a FEC
1580 containing the pseudowire information of the first segment
1581 (PW1 between T-PE1 and S-PE) to S-PE for validation. If FEC
1582 Stack Validation is enabled, the request may also include an
1583 additional sub-TLV such as LDP Prefix and/or RSVP LSP,
1584 dependent on the type of transport tunnel the segmented PW
1585 is riding on.
1586
1587 -ii. S-PE validates the echo request with the FEC. Since it is a
1588 switching point between the first and second segment, it
1589 builds an echo reply with a return code of 8 and sends the
1590 echo reply back to T-PE1.
1591
1592 -iii. T-PE1 builds a second VCCV echo request based on the
1593 information obtained from the control plane (SP-PE TLV). It
1594 then increments the TTL and sends it out to T-PE2. Note
1595 that the VCCV echo request packet is switched at the S-PE
1596 data path and forwarded to the next downstream segment
1597 without any involvement from the control plane.
1598
1599 -iv. T-PE2 receives and validates the echo request with the FEC.
1600 Since T-PE2 is the destination node or the egress node of
1601 the MS-PW, it replies to T-PE1 with an echo reply with a
1602 return code of 3 (Egress Router).
1603
1604 -v. T-PE1 receives the echo reply from T-PE2. T-PE1 is made
1605 aware that T-PE2 is the destination of the MS-PW because the
1606 echo reply has a return code of 3. The trace process is
1607 completed.
1608
1609 If no echo reply is received, or an error code is received from a
1610 particular PE, the trace process MUST stop immediately, and packets
1611 MUST NOT be sent further along the MS-PW.
1612
1613 For more detail on the format of the VCCV echo packet, refer to
1614 [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>] and [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>]. The TTL here refers to that of the inner
1615 (PW) label TTL.
1616
1617
1618
1619
1620 <span class="grey">Martini, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1623
1624
1625 <span class="h5"><a class="selflink" id="section-9.6.2.5" href="#section-9.6.2.5">9.6.2.5</a>. MS-PW Path Trace</span>
1626
1627 As an example, in Figure 3, VCCV trace can be performed on the MS-PW
1628 originating from T-PE1 by a single operational command. The
1629 following OPTIONAL process ensues:
1630
1631 -i. T-PE1 sends a VCCV echo request with TTL set to 1 and a FEC
1632 containing the pseudowire information of the first segment
1633 (PW1 between T-PE1 and S-PE) to S-PE for validation. If FEC
1634 Stack Validation is enabled, the request may also include an
1635 additional sub-TLV such as LDP Prefix and/or RSVP LSP,
1636 dependent on the type of transport tunnel the segmented PW
1637 is riding on.
1638
1639 -ii. The S-PE validates the echo request with the FEC.
1640
1641 -iii. The S-PE builds an echo reply with a return code of 8 and
1642 sends the echo reply back to T-PE1, appending the FEC 128
1643 information for the next segment along the MS-PW to the VCCV
1644 echo reply packet using the Target FEC stack TLV (as per
1645 Sections <a href="#section-3.2">3.2</a> and <a href="#section-4.5">4.5</a> of [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>]).
1646
1647 -iv. T-PE1 builds a second VCCV echo request based on the
1648 information obtained from the FEC stack TLV received in the
1649 previous VCCV echo reply. It then increments the TTL and
1650 sends it out to T-PE2. Note that the VCCV echo request
1651 packet is switched at the S-PE data path and forwarded to
1652 the next downstream segment without any involvement from the
1653 control plane.
1654
1655 -v. T-PE2 receives and validates the echo request with the FEC.
1656 Since T-PE2 is the destination node or the egress node of
1657 the MS-PW, it replies to T-PE1 with an echo reply with a
1658 return code of 3 (Egress Router).
1659
1660 -vi. T-PE1 receives the echo reply from T-PE2. T-PE1 is made
1661 aware that T-PE2 is the destination of the MS-PW because the
1662 echo reply has a return code of 3. The trace process is
1663 completed.
1664
1665 If no echo reply is received, or an error code is received from a
1666 particular PE, the trace process MUST stop immediately, and packets
1667 MUST NOT be sent further along the MS-PW.
1668
1669 For more detail on the format of the VCCV echo packet, refer to
1670 [<a href="./rfc5085" title="&quot;Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires&quot;">RFC5085</a>] and [<a href="./rfc4379" title="&quot;Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures&quot;">RFC4379</a>]. The TTL here refers to that of the inner
1671 (PW) label TTL.
1672
1673
1674
1675
1676 <span class="grey">Martini, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1679
1680
1681 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Mapping Switched Pseudowire Status</span>
1682
1683 In the PW switching with attachment circuits case (Figure 2), PW
1684 status messages indicating PW or attachment circuit faults MUST be
1685 mapped to fault indications or OAM messages on the connecting AC as
1686 defined in [<a href="#ref-PW-MSG-MAP" title="&quot;Pseudowire (PW) OAM Message Mapping&quot;">PW-MSG-MAP</a>].
1687
1688 In the PW control plane switching case (Figure 3), there is no
1689 attachment circuit at the S-PE, but the two PWs are connected
1690 together. Similarly, the status of the PWs is forwarded unchanged
1691 from one PW to the other by the control plane switching function.
1692 However, it may sometimes be necessary to communicate fault status of
1693 one of the locally attached PW segments at an S-PE. For LDP, this
1694 can be accomplished by sending an LDP notification message containing
1695 the PW status TLV, as well as an OPTIONAL PW Switching Point PE TLV
1696 as follows:
1697
1698 0 1 2 3
1699 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1701 |0| Notification (0x0001) | Message Length |
1702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1703 | Message ID |
1704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1705 |0|1| Status (0x0300) | Length |
1706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1707 |0|1| Status Code=0x00000028 |
1708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1709 | Message ID=0 |
1710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1711 | Message Type=0 | PW Status TLV |
1712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1713 | PW Status TLV |
1714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1715 | PW Status TLV | PWid FEC or Generalized ID FEC|
1716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1717 ~ ~
1718 | PWid FEC or Generalized ID FEC (contd.) |
1719 | |
1720 | |
1721 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1722 |1|0| SP-PE TLV (0x096D) | SP-PE TLV Length |
1723 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1724 | Type | Length | Variable Length Value |
1725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Martini, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1735
1736
1737 Only one SP-PE TLV can be present in this message. This message is
1738 then relayed by each S-PE unchanged. The T-PE decodes the status
1739 message and the included SP-PE TLV to detect exactly where the fault
1740 occurred. At the T-PE, if there is no SP-PE TLV included in the LDP
1741 status notification, then the status message can be assumed to have
1742 originated at the remote T-PE.
1743
1744 The merging of the received LDP status and the local status for the
1745 PW segments at an S-PE can be summarized as follows:
1746
1747 -i. When the local status for both PW segments is UP, the S-PE
1748 passes any received AC or PW status bits unchanged, i.e.,
1749 the status notification TLV is unchanged, but the PWid in
1750 the case of a FEC 128 TLV is set to the value of the PW
1751 segment of the next hop.
1752
1753 -ii. When the local status for any of the PW segments is at
1754 fault, the S-PE always sends the local status bits
1755 regardless of whether the received status bits from the
1756 remote node indicated that an upstream fault has cleared.
1757 AC status bits are passed along unchanged.
1758
1759 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. PW Status Messages Initiated by the S-PE</span>
1760
1761 The PW fault directions are defined as follows:
1762
1763 +-------+
1764 ---PW1 Receive----&gt;| |-----PW2 Transmit----&gt;
1765 S-PE1 | S-PE2 | S-PE3
1766 &lt;--PW1 Transmit----| |&lt;----PW2 Receive------
1767 +-------+
1768
1769 Figure 4: S-PE and PW Transmission/Reception Directions
1770
1771 When a local fault is detected by the S-PE, a PW status message is
1772 sent in both directions along the PW. Since there are no attachment
1773 circuits on an S-PE, only the following status messages are relevant:
1774
1775 0x00000008 - Local PSN-facing PW (ingress) Receive Fault
1776 0x00000010 - Local PSN-facing PW (egress) Transmit Fault
1777
1778 Each S-PE needs to store only two 32-bit PW status words for each PW
1779 segment: one for local failures and one for remote failures (normally
1780 received from another PE). The first failure will set the
1781 appropriate bit in the 32-bit status word, and each subsequent
1782 failure will be ORed to the appropriate PW status word. In the case
1783
1784
1785
1786
1787
1788 <span class="grey">Martini, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1791
1792
1793 that the PW status word stores remote failures, this rule has the
1794 effect of a logical OR operation with the first failure received on
1795 the particular PW segment.
1796
1797 It should be noted that remote failures received on an S-PE are just
1798 passed along the MS-PW unchanged, while local failures detected an
1799 S-PE are signaled on both PW segments.
1800
1801 A T-PE can receive multiple failures from S-PEs along the MS-PW;
1802 however, only the failure from the remote closest S-PE will be stored
1803 (last PW status message received). The PW status word received is
1804 just ORed to any existing remote PW status already stored on the
1805 T-PE.
1806
1807 Given that there are two PW segments at a particular S-PE for a
1808 particular MS-PW (referring to Figure 4), there are four possible
1809 failure cases as follows:
1810
1811 -i. PW2 Transmit direction fault
1812 -ii. PW1 Transmit direction fault
1813 -iii. PW2 Receive direction fault
1814 -iv. PW1 Receive direction fault
1815
1816 Once a PW status notification message is initiated at an S-PE for a
1817 particular PW status bit, any further status message for the same
1818 status bit (and received from an upstream neighbor) is processed
1819 locally and not forwarded until the S-PE original status error state
1820 is cleared.
1821
1822 Each S-PE along the MS-PW MUST store any PW status messages
1823 transiting it. If more than one status message with the same PW
1824 status bit set is received by a T-PE or S-PE, only the last PW status
1825 message is stored.
1826
1827 <span class="h4"><a class="selflink" id="section-10.1.1" href="#section-10.1.1">10.1.1</a>. Local PW2 Transmit Direction Fault</span>
1828
1829 When this failure occurs, the S-PE will take the following actions:
1830
1831 * Send a PW status message to S-PE3 containing "0x00000010 - Local
1832 PSN-facing PW (egress) Transmit Fault".
1833
1834 * Send a PW status message to S-PE1 containing "0x00000008 - Local
1835 PSN-facing PW (ingress) Receive Fault".
1836
1837 * Store 0x00000010 in the local PW status word for the PW segment
1838 toward S-PE3.
1839
1840
1841
1842
1843
1844 <span class="grey">Martini, et al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1847
1848
1849 <span class="h4"><a class="selflink" id="section-10.1.2" href="#section-10.1.2">10.1.2</a>. Local PW1 Transmit Direction Fault</span>
1850
1851 When this failure occurs, the S-PE will take the following actions:
1852
1853 * Send a PW status message to S-PE1 containing "0x00000010 - Local
1854 PSN-facing PW (egress) Transmit Fault".
1855
1856 * Send a PW status message to S-PE3 containing "0x00000008 - Local
1857 PSN-facing PW (ingress) Receive Fault".
1858
1859 * Store 0x00000010 in the local PW status word for the PW segment
1860 toward S-PE1.
1861
1862 <span class="h4"><a class="selflink" id="section-10.1.3" href="#section-10.1.3">10.1.3</a>. Local PW2 Receive Direction Fault</span>
1863
1864 When this failure occurs, the S-PE will take the following actions:
1865
1866 * Send a PW status message to S-PE3 containing "0x00000008 - Local
1867 PSN-facing PW (ingress) Receive Fault".
1868
1869 * Send a PW status message to S-PE1 containing "0x00000010 - Local
1870 PSN-facing PW (egress) Transmit Fault".
1871
1872 * Store 0x00000008 in the local PW status word for the PW segment
1873 toward S-PE3.
1874
1875 <span class="h4"><a class="selflink" id="section-10.1.4" href="#section-10.1.4">10.1.4</a>. Local PW1 Receive Direction Fault</span>
1876
1877 When this failure occurs, the S-PE will take the following actions:
1878
1879 * Send a PW status message to S-PE1 containing "0x00000008 - Local
1880 PSN-facing PW (ingress) Receive Fault".
1881
1882 * Send a PW status message to S-PE3 containing "0x00000010 - Local
1883 PSN-facing PW (egress) Transmit Fault".
1884
1885 * Store 0x00000008 in the local PW status word for the PW segment
1886 toward S-PE1.
1887
1888 <span class="h4"><a class="selflink" id="section-10.1.5" href="#section-10.1.5">10.1.5</a>. Clearing Faults</span>
1889
1890 Remote PW status fault clearing messages received by an S-PE will
1891 only be forwarded if there are no corresponding local faults on the
1892 S-PE. (Local faults always supersede remote faults.)
1893
1894 Once the local fault has cleared, and there is no corresponding (same
1895 PW status bit set) remote fault, a PW status message is sent out to
1896 the adjacent PEs, clearing the fault.
1897
1898
1899
1900 <span class="grey">Martini, et al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1903
1904
1905 When a PW status fault clearing message is forwarded, the S-PE will
1906 always send the SP-PE TLV associated with the PE that cleared the
1907 fault.
1908
1909 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. PW Status Messages and SP-PE TLV Processing</span>
1910
1911 When a PW status message is received that includes an SP-PE TLV, the
1912 SP-PE TLV information MAY be stored, along with the contents of the
1913 PW status Word according to the procedures described above. The
1914 SP-PE TLV stored is always the SP-PE TLV that is associated with the
1915 PE that set that particular last fault. If subsequent PW status
1916 messages for the same PW status bit are received, the SP-PE TLV will
1917 overwrite the previously stored SP-PE TLV.
1918
1919 <span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a>. T-PE Processing of PW Status Messages</span>
1920
1921 The PW switching architecture is based on the concept that the T-PE
1922 should process the PW LDP messages in the same manner as if it were
1923 participating in the setup of a PW segment. However, a T-PE
1924 participating in an MS-PW SHOULD be able to process the SP-PE TLV.
1925 Otherwise, the processing of PW status messages and other PW setup
1926 messages is exactly as described in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>].
1927
1928 <span class="h3"><a class="selflink" id="section-10.4" href="#section-10.4">10.4</a>. Pseudowire Status Negotiation Procedures</span>
1929
1930 Pseudowire status signaling methodology, defined in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>], SHOULD
1931 be transparent to the switching point.
1932
1933 <span class="h3"><a class="selflink" id="section-10.5" href="#section-10.5">10.5</a>. Status Dampening</span>
1934
1935 When the PW control plane switching methodology is used to cross an
1936 administrative boundary, it might be necessary to prevent excessive
1937 status signaling changes from being propagated across the
1938 administrative boundary. This can be achieved by using a similar
1939 method as commonly employed for the BGP route advertisement
1940 dampening. The details of this OPTIONAL algorithm are a matter of
1941 implementation and are outside the scope of this document.
1942
1943 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Peering between Autonomous Systems</span>
1944
1945 The procedures outlined in this document can be employed to provision
1946 and manage MS-PWs crossing AS boundaries. The use of more advanced
1947 mechanisms involving auto-discovery and ordered PWE3 MS-PW signaling
1948 will be covered in a separate document.
1949
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Martini, et al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
1959
1960
1961 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Congestion Considerations</span>
1962
1963 Each PSN carrying the PW may be subject to congestion. The
1964 congestion considerations in [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>] apply to PW segments as well.
1965 Each PW segment will handle any congestion experienced by the PW
1966 traffic independently of the other MS-PW segments. It is possible
1967 that passing knowledge of congestion between segments and to the
1968 T-PEs can result in more efficient edge-to-edge congestion mitigation
1969 systems. However, any specific methods of congestion mitigation are
1970 outside the scope of this document and left for further study.
1971
1972 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Security Considerations</span>
1973
1974 This document specifies the LDP, L2TPv3, and VCCV extensions that are
1975 needed for setting up and maintaining pseudowires. The purpose of
1976 setting up pseudowires is to enable Layer 2 frames to be encapsulated
1977 and transmitted from one end of a pseudowire to the other.
1978 Therefore, we discuss the security considerations for both the data
1979 plane and the control plane in the following sections. The
1980 guidelines and security considerations specified in [<a href="./rfc5920" title="&quot;Security Framework for MPLS and GMPLS Networks&quot;">RFC5920</a>] also
1981 apply to MS-PW when the PSN is MPLS.
1982
1983 <span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. Data Plane Security</span>
1984
1985 Data plane security considerations as discussed in [<a href="./rfc4447" title="&quot;Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)&quot;">RFC4447</a>],
1986 [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>], and [<a href="./rfc3985" title="&quot;Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture&quot;">RFC3985</a>] apply to this extension without any changes.
1987
1988 <span class="h4"><a class="selflink" id="section-13.1.1" href="#section-13.1.1">13.1.1</a>. VCCV Security Considerations</span>
1989
1990 The VCCV technology for MS-PW offers a method for the service
1991 provider to verify the data path of a specific PW. This involves
1992 sending a packet to a specific PE and receiving an answer that either
1993 confirms the information contained in the packet or indicates that it
1994 is incorrect. This is a very similar process to the commonly used IP
1995 ICMP ping and TTL expired methods for IP networks. It should be
1996 noted that when using VCCV Type 3 for PW when the CW is not enabled,
1997 if a packet is crafted with a TTL greater than the number of hops
1998 along the MS-PW path, or an S-PE along the path mis-processes the
1999 TTL, the packet could mistakenly be forwarded out of the attachment
2000 circuit as a native PW packet. This packet would most likely be
2001 treated as an error packet by the CE. However, if this possibility
2002 is not acceptable, the CW should be enabled to guarantee that a VCCV
2003 packet will never be mistakenly forwarded to the AC.
2004
2005
2006
2007
2008
2009
2010
2011
2012 <span class="grey">Martini, et al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2015
2016
2017 <span class="h3"><a class="selflink" id="section-13.2" href="#section-13.2">13.2</a>. Control Protocol Security</span>
2018
2019 General security considerations with regard to the use of LDP are
2020 specified in <a href="./rfc5036#section-5">Section&nbsp;5 of RFC 5036</a>. Security considerations with
2021 regard to the L2TPv3 control plane are specified in [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>]. These
2022 considerations apply as well to the case where LDP or L2TPv3 is used
2023 to set up PWs.
2024
2025 A pseudowire connects two attachment circuits. It is important to
2026 make sure that LDP connections are not arbitrarily accepted from
2027 anywhere, or else a local attachment circuit might get connected to
2028 an arbitrary remote attachment circuit. Therefore, an incoming
2029 session request MUST NOT be accepted unless its IP source address is
2030 known to be the source of an "eligible" peer. The set of eligible
2031 peers could be pre-configured (either as a list of IP addresses or as
2032 a list of address/mask combinations), or it could be discovered
2033 dynamically via an auto-discovery protocol that is itself trusted.
2034 (Note that if the auto-discovery protocol were not trusted, the set
2035 of "eligible peers" it produces could not be trusted.)
2036
2037 Even if a connection request appears to come from an eligible peer,
2038 its source address may have been spoofed. So some means of
2039 preventing source address spoofing must be in place. For example, if
2040 all the eligible peers are in the same network, source address
2041 filtering at the border routers of that network could eliminate the
2042 possibility of source address spoofing.
2043
2044 For a greater degree of security, the LDP authentication option, as
2045 described in <a href="./rfc5036#section-2.9">Section&nbsp;2.9 of [RFC5036]</a>, or the Control Message
2046 Authentication option of [<a href="./rfc3931" title="&quot;Layer Two Tunneling Protocol - Version 3 (L2TPv3)&quot;">RFC3931</a>], MAY be used. This provides
2047 integrity and authentication for the control messages, and eliminates
2048 the possibility of source address spoofing. Use of the message
2049 authentication option does not provide privacy, but privacy of
2050 control messages is not usually considered to be highly important.
2051 Both the LDP and L2TPv3 message authentication options rely on the
2052 configuration of pre-shared keys, making it difficult to deploy when
2053 the set of eligible neighbors is determined by an auto-configuration
2054 protocol.
2055
2056 The protocol described in this document relies on the LDP MD5
2057 authentication key option, as described in <a href="./rfc5036#section-2.9">Section&nbsp;2.9 of [RFC5036]</a>,
2058 to provide integrity and authentication for the LDP messages and
2059 protect against source address spoofing. This mechanism relies on
2060 the configuration of pre-shared keys, which typically introduces some
2061 fragility. In the specific case of MS-PW, the number of links that
2062 leave an organization will be limited in practice, so the reliance on
2063 pre-shared keys should be manageable.
2064
2065
2066
2067
2068 <span class="grey">Martini, et al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2071
2072
2073 When the Generalized PWid FEC Element is used, it is possible that a
2074 particular peer may be one of the eligible peers, but may not be the
2075 right one to connect to the particular attachment circuit identified
2076 by the particular instance of the Generalized ID FEC element.
2077 However, given that the peer is known to be one of the eligible peers
2078 (as discussed above), this would be the result of a configuration
2079 error, rather than a security problem. Nevertheless, it may be
2080 advisable for a PE to associate each of its local attachment circuits
2081 with a set of eligible peers, rather than have just a single set of
2082 eligible peers associated with the PE as a whole.
2083
2084 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. IANA Considerations</span>
2085
2086 <span class="h3"><a class="selflink" id="section-14.1" href="#section-14.1">14.1</a>. L2TPv3 AVP</span>
2087
2088 This document uses a new L2TP parameter; IANA already maintains the
2089 registry "Control Message Attribute Value Pairs" defined by
2090 [<a href="./rfc3438" title="&quot;Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update&quot;">RFC3438</a>]. The following new value has been assigned:
2091
2092 101 PW Switching Point AVP
2093
2094 <span class="h3"><a class="selflink" id="section-14.2" href="#section-14.2">14.2</a>. LDP TLV TYPE</span>
2095
2096 This document uses a new LDP TLV type; IANA already maintains the
2097 registry "TLV TYPE NAME SPACE" defined by <a href="./rfc5036">RFC 5036</a>. The following
2098 value has been assigned:
2099
2100 TLV type Description
2101 0x096D Pseudowire Switching Point PE TLV
2102
2103 <span class="h3"><a class="selflink" id="section-14.3" href="#section-14.3">14.3</a>. LDP Status Codes</span>
2104
2105 This document uses a new LDP status code; IANA already maintains the
2106 registry "STATUS CODE NAME SPACE" defined by <a href="./rfc5036">RFC 5036</a>. The following
2107 value has been assigned:
2108
2109 Assignment E Description
2110 0x0000003A 0 PW Loop Detected
2111
2112 <span class="h3"><a class="selflink" id="section-14.4" href="#section-14.4">14.4</a>. L2TPv3 Result Codes</span>
2113
2114 This document uses a new L2TPv3 Result Code for the CDN message, as
2115 assigned by IANA in the "Result Code AVP (Attribute Type 1) Values"
2116 registry.
2117
2118
2119
2120
2121
2122
2123
2124 <span class="grey">Martini, et al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2127
2128
2129 Registry Name: Result Code AVP (Attribute Type 1) Values Defined
2130 Result Code values for the CDN message are:
2131
2132 Assignment Description
2133 31 Sequencing not supported
2134
2135 <span class="h3"><a class="selflink" id="section-14.5" href="#section-14.5">14.5</a>. New IANA Registries</span>
2136
2137 IANA has set up a registry named "Pseudowire Switching Point PE sub-
2138 TLV Type". These are 8-bit values. Type values 1 through 6 are
2139 defined in this document. Type values 7 through 64 are to be
2140 assigned by IANA using the "Expert Review" policy defined in
2141 [<a href="./rfc5226" title="">RFC5226</a>]. Type values 65 through 127, as well as 0 and 255, are to
2142 be allocated using the IETF consensus policy defined in <a href="./rfc5226">RFC 5226</a>.
2143 Type values 128 through 254 are reserved for vendor proprietary
2144 extensions and are to be assigned by IANA, using the "First Come
2145 First Served" policy defined in <a href="./rfc5226">RFC 5226</a>.
2146
2147 The Type Values are assigned as follows:
2148
2149 Type Length Description
2150
2151 0x01 4 PWid of last PW segment traversed
2152 0x02 variable PW Switching Point description string
2153 0x03 4/16 Local IP address of PW Switching Point
2154 0x04 4/16 Remote IP address of last PW Switching Point
2155 traversed or of the T-PE
2156 0x05 variable FEC Element of last PW segment traversed
2157 0x06 12 L2 PW address of PW Switching Point
2158
2159 <span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Normative References</span>
2160
2161 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
2162 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
2163
2164 [<a id="ref-RFC2277">RFC2277</a>] Alvestrand, H., "IETF Policy on Character Sets and
2165 Languages", <a href="https://www.rfc-editor.org/bcp/bcp18">BCP 18</a>, <a href="./rfc2277">RFC 2277</a>, January 1998.
2166
2167 [<a id="ref-RFC3931">RFC3931</a>] Lau, J., Ed., Townsley, M., Ed., and I. Goyret, Ed.,
2168 "Layer Two Tunneling Protocol - Version 3 (L2TPv3)", <a href="./rfc3931">RFC</a>
2169 <a href="./rfc3931">3931</a>, March 2005.
2170
2171 [<a id="ref-RFC4364">RFC4364</a>] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
2172 Networks (VPNs)", <a href="./rfc4364">RFC 4364</a>, February 2006.
2173
2174 [<a id="ref-RFC4379">RFC4379</a>] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
2175 Label Switched (MPLS) Data Plane Failures", <a href="./rfc4379">RFC 4379</a>,
2176 February 2006.
2177
2178
2179
2180 <span class="grey">Martini, et al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2183
2184
2185 [<a id="ref-RFC4385">RFC4385</a>] Bryant, S., Swallow, G., Martini, L., and D. McPherson,
2186 "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word
2187 for Use over an MPLS PSN", <a href="./rfc4385">RFC 4385</a>, February 2006.
2188
2189 [<a id="ref-RFC4446">RFC4446</a>] Martini, L., "IANA Allocations for Pseudowire Edge to
2190 Edge Emulation (PWE3)", <a href="https://www.rfc-editor.org/bcp/bcp116">BCP 116</a>, <a href="./rfc4446">RFC 4446</a>, April 2006.
2191
2192 [<a id="ref-RFC4447">RFC4447</a>] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T.,
2193 and G. Heron, "Pseudowire Setup and Maintenance Using
2194 the Label Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April
2195 2006.
2196
2197 [<a id="ref-RFC5003">RFC5003</a>] Metz, C., Martini, L., Balus, F., and J. Sugimoto,
2198 "Attachment Individual Identifier (AII) Types for
2199 Aggregation", <a href="./rfc5003">RFC 5003</a>, September 2007.
2200
2201 [<a id="ref-RFC5036">RFC5036</a>] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed.,
2202 "LDP Specification", <a href="./rfc5036">RFC 5036</a>, October 2007.
2203
2204 [<a id="ref-RFC5085">RFC5085</a>] Nadeau, T., Ed., and C. Pignataro, Ed., "Pseudowire
2205 Virtual Circuit Connectivity Verification (VCCV): A
2206 Control Channel for Pseudowires", <a href="./rfc5085">RFC 5085</a>, December
2207 2007.
2208
2209 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
2210 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
2211 May 2008.
2212
2213 [<a id="ref-RFC5641">RFC5641</a>] McGill, N. and C. Pignataro, "Layer 2 Tunneling Protocol
2214 Version 3 (L2TPv3) Extended Circuit Status Values", <a href="./rfc5641">RFC</a>
2215 <a href="./rfc5641">5641</a>, August 2009.
2216
2217 <span class="h2"><a class="selflink" id="section-16" href="#section-16">16</a>. Informative References</span>
2218
2219 [<a id="ref-PW-MSG-MAP">PW-MSG-MAP</a>] Aissaoui, M., Busschbach, P., Morrow, M., Martini, L.,
2220 Stein, Y(J)., Allan, D., and T. Nadeau, "Pseudowire (PW)
2221 OAM Message Mapping", Work in Progress, October 2010.
2222
2223 [<a id="ref-RFC3032">RFC3032</a>] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
2224 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
2225 Encoding", <a href="./rfc3032">RFC 3032</a>, January 2001.
2226
2227 [<a id="ref-RFC3438">RFC3438</a>] Townsley, W., "Layer Two Tunneling Protocol (L2TP)
2228 Internet Assigned Numbers Authority (IANA)
2229 Considerations Update", <a href="https://www.rfc-editor.org/bcp/bcp68">BCP 68</a>, <a href="./rfc3438">RFC 3438</a>, December 2002.
2230
2231
2232
2233
2234
2235
2236 <span class="grey">Martini, et al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2239
2240
2241 [<a id="ref-RFC3985">RFC3985</a>] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire
2242 Emulation Edge-to-Edge (PWE3) Architecture", <a href="./rfc3985">RFC 3985</a>,
2243 March 2005.
2244
2245 [<a id="ref-RFC4023">RFC4023</a>] Worster, T., Rekhter, Y., and E. Rosen, Ed.,
2246 "Encapsulating MPLS in IP or Generic Routing
2247 Encapsulation (GRE)", <a href="./rfc4023">RFC 4023</a>, March 2005.
2248
2249 [<a id="ref-RFC4454">RFC4454</a>] Singh, S., Townsley, M., and C. Pignataro, "Asynchronous
2250 Transfer Mode (ATM) over Layer 2 Tunneling Protocol
2251 Version 3 (L2TPv3)", <a href="./rfc4454">RFC 4454</a>, May 2006.
2252
2253 [<a id="ref-RFC4623">RFC4623</a>] Malis, A. and M. Townsley, "Pseudowire Emulation Edge-
2254 to-Edge (PWE3) Fragmentation and Reassembly", <a href="./rfc4623">RFC 4623</a>,
2255 August 2006.
2256
2257 [<a id="ref-RFC4667">RFC4667</a>] Luo, W., "Layer 2 Virtual Private Network (L2VPN)
2258 Extensions for Layer 2 Tunneling Protocol (L2TP)", <a href="./rfc4667">RFC</a>
2259 <a href="./rfc4667">4667</a>, September 2006.
2260
2261 [<a id="ref-RFC4717">RFC4717</a>] Martini, L., Jayakumar, J., Bocci, M., El-Aawar, N.,
2262 Brayley, J., and G. Koleyni, "Encapsulation Methods for
2263 Transport of Asynchronous Transfer Mode (ATM) over MPLS
2264 Networks", <a href="./rfc4717">RFC 4717</a>, December 2006.
2265
2266 [<a id="ref-RFC5254">RFC5254</a>] Bitar, N., Ed., Bocci, M., Ed., and L. Martini, Ed.,
2267 "Requirements for Multi-Segment Pseudowire Emulation
2268 Edge-to-Edge (PWE3)", <a href="./rfc5254">RFC 5254</a>, October 2008.
2269
2270 [<a id="ref-RFC5659">RFC5659</a>] Bocci, M. and S. Bryant, "An Architecture for Multi-
2271 Segment Pseudowire Emulation Edge-to-Edge", <a href="./rfc5659">RFC 5659</a>,
2272 October 2009.
2273
2274 [<a id="ref-RFC5920">RFC5920</a>] Fang, L., Ed., "Security Framework for MPLS and GMPLS
2275 Networks", <a href="./rfc5920">RFC 5920</a>, July 2010.
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292 <span class="grey">Martini, et al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2295
2296
2297 <span class="h2"><a class="selflink" id="section-17" href="#section-17">17</a>. Acknowledgments</span>
2298
2299 The authors wish to acknowledge the contributions of Satoru
2300 Matsushima, Wei Luo, Neil Mcgill, Skip Booth, Neil Hart, Michael Hua,
2301 and Tiberiu Grigoriu.
2302
2303 <span class="h2"><a class="selflink" id="section-18" href="#section-18">18</a>. Contributors</span>
2304
2305 The following people also contributed text to this document:
2306
2307 Florin Balus
2308 Alcatel-Lucent
2309 701 East Middlefield Rd.
2310 Mountain View, CA 94043
2311 US
2312 EMail: [email protected]
2313
2314
2315 Mike Duckett
2316 Bellsouth
2317 Lindbergh Center, D481
2318 575 Morosgo Dr
2319 Atlanta, GA 30324
2320 US
2321 EMail: [email protected]
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348 <span class="grey">Martini, et al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc6073">RFC 6073</a> Segmented Pseudowire January 2011</span>
2351
2352
2353 Authors' Addresses
2354
2355 Luca Martini
2356 Cisco Systems, Inc.
2357 9155 East Nichols Avenue, Suite 400
2358 Englewood, CO 80112
2359 US
2360 EMail: [email protected]
2361
2362
2363 Chris Metz
2364 Cisco Systems, Inc.
2365 EMail: [email protected]
2366
2367
2368 Thomas D. Nadeau
2369 EMail: [email protected]
2370
2371
2372 Matthew Bocci
2373 Alcatel-Lucent
2374 Grove House, Waltham Road Rd
2375 White Waltham, Berks SL6 3TN
2376 UK
2377 EMail: [email protected]
2378
2379
2380 Mustapha Aissaoui
2381 Alcatel-Lucent
2382 600, March Road,
2383 Kanata, ON
2384 Canada
2385 EMail: [email protected]
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404 Martini, et al. Standards Track [Page 43]
2405 </pre>