1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Internet Engineering Task Force (IETF) G. Mirsky
Request for Comments: 7189 Ericsson
Category: Standards Track March 2014
ISSN: 2070-1721
<span class="h1">Virtual Circuit Connectivity Verification (VCCV)</span>
<span class="h1">Capability Advertisement for MPLS Transport Profile (MPLS-TP)</span>
Abstract
This document specifies how signaling and selection processes for
Pseudowire (PW) Virtual Circuit Connectivity Verification (VCCV) are
modified to ensure backward compatibility and allow use of proactive
Connectivity Verification (CV), Continuity Check (CC), and Remote
Defect Indication (RDI) over MPLS Transport Profile (MPLS-TP) PWs.
This document introduces four new CV types and, to accommodate them,
a new VCCV Extended CV parameter for PW Interface Parameters Sub-TLV
is defined.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7189">http://www.rfc-editor.org/info/rfc7189</a>.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Mirsky Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7189">RFC 7189</a> VCCV for MPLS-TP March 2014</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Conventions Used in This Document . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1.1">1.1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1.2">1.1.2</a>. Requirements Language . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. MPLS-TP CC-CV on Pseudowires . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. VCCV Extended CV Advertisement Sub-TLV . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. MPLS-TP CC-CV Types . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. MPLS-TP CC-CV Type Operation . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.4">2.4</a>. CV Type Selection . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. VCCV Extended CV Types . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Proactive Connectivity Verification (CV), Continuity Check (CC), and
Remote Defect Indication (RDI) for the MPLS Transport Profile
[<a href="./rfc6428" title=""Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile"">RFC6428</a>] are applicable to all constructs of the MPLS-TP, including
pseudowires (PWs). If the control plane is used to operate and
manage PWs then the procedures defined in [<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>] and [<a href="./rfc5885" title=""Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)"">RFC5885</a>]
should be used to select the proper type of Control Channel and the
corresponding type of Connectivity Verification. This document
specifies how signaling and selection processes are modified to
ensure backward compatibility and allow use of proactive CV-CC-RDI
over MPLS-TP PWs.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
<span class="h4"><a class="selflink" id="section-1.1.1" href="#section-1.1.1">1.1.1</a>. Terminology</span>
BFD: Bidirectional Forwarding Detection
CC: Continuity Check
CV: Connectivity Verification
PE: Provider Edge
VCCV: Virtual Circuit Connectivity Verification
<span class="grey">Mirsky Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7189">RFC 7189</a> VCCV for MPLS-TP March 2014</span>
<span class="h4"><a class="selflink" id="section-1.1.2" href="#section-1.1.2">1.1.2</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. MPLS-TP CC-CV on Pseudowires</span>
PW VCCV can support several CV Types, and it can support an arbitrary
combination of CV modes advertised in the CV Types field of the VCCV
Interface Parameter sub-TLV [<a href="./rfc4446" title=""IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)"">RFC4446</a>] [<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>]. Currently, six
types of CV have been defined for PW VCCV. This document introduces
four new CV types and, to accommodate them, a new VCCV Extended CV
parameter for the PW Interface Parameters Sub-TLV is defined.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. VCCV Extended CV Advertisement Sub-TLV</span>
The format of the VCCV Extended CV Advertisement is a TLV where the
format is as follows:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x19 | Length | CV Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: VCCV Extended CV Parameter Format
The Length field is the length of the sub-TLV, including type and the
Length field itself. The minimum length is 4. It is recommended
that extensions to the sub-TLV be done in 4-byte increments.
The Reserved field MUST be set to zeroes on transmit and ignored on
receive.
The CV Type field is a bitmask that lists types of CV monitoring that
a PE is capable of supporting. The VCCV Extended CV parameter sub-
TLV MUST appear in combination with the VCCV parameter sub-TLV. If
the VCCV parameter sub-TLV is missing, then the VCCV Extended CV
parameter sub-TLV SHOULD be ignored.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. MPLS-TP CC-CV Types</span>
[<a id="ref-RFC6428">RFC6428</a>] defines coordinated and independent modes of monitoring
point-to-point bidirectional connection that can be applied to
monitoring PWs. At the same time, [<a href="./rfc6310" title=""Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message Mapping"">RFC6310</a>] defines how BFD-based
<span class="grey">Mirsky Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7189">RFC 7189</a> VCCV for MPLS-TP March 2014</span>
Operations, Administration, and Maintenance (OAM) can map to the
status of an Attachment Circuit. Thus, there could be four MPLS-TP
CV types for each combination of mode and functionality:
+----------------+-------------------+------------------------------+
| Modes | Fault Detection | Fault Detection and Status |
| | Only | Signaling |
+----------------+-------------------+------------------------------+
| Independent | 0x01 | 0x02 |
| Mode | | |
| Coordinated | 0x04 | 0x08 |
| Mode | | |
+----------------+-------------------+------------------------------+
Table 1: Bitmask Values for MPLS-TP CV Types
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. MPLS-TP CC-CV Type Operation</span>
According to [<a href="./rfc6428" title=""Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile"">RFC6428</a>], connectivity verification is part of MPLS-TP
CC/CV operation that can be used with VCCV Control Channel Type 1
[<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>]. If VCCV Control Channel Type 1 is selected, then PEs MAY
select one of the MPLS-TP CC-CV types as the VCCV CV mechanism to be
used for this PW.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. CV Type Selection</span>
CV selection rules that have been defined in <a href="./rfc5085#section-7">Section 7 of [RFC5085]</a>
and updated in <a href="./rfc5885#section-4">Section 4 of [RFC5885]</a> are augmented in this document.
If VCCV Control Channel Type 1 is chosen according to <a href="./rfc5085#section-7">Section 7 of
[RFC5085]</a> and a common set of proactive CV types that are advertised
by both PEs includes MPLS-TP CC-CV types and some BFD CV types, then
MPLS-TP CC-CV takes precedence over any type of BFD CV. If multiple
MPLS-TP CV types are advertised by both PEs, then the following list
(ordered by descending priority) is used:
1. 0x08 - Coordinated mode for PW Fault Detection and AC/PW Fault
Status Signaling
2. 0x04 - Coordinated mode for PW Fault Detection only
3. 0x02 - Independent mode for PW Fault Detection and AC/PW Fault
Status Signaling
4. 0x01 - Independent mode for PW Fault Detection only
<span class="grey">Mirsky Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7189">RFC 7189</a> VCCV for MPLS-TP March 2014</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
The PW Interface Parameters Sub-TLV registry is defined in [<a href="./rfc4446" title=""IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)"">RFC4446</a>].
IANA has reserved a new PW Interface Parameters Sub-TLV type as
follows:
+-----------+----------+----------------------------+---------------+
| Parameter | Length | Description | Reference |
| ID | | | |
+-----------+----------+----------------------------+---------------+
| 0x19 | variable | VCCV Extended CV Parameter | This document |
+-----------+----------+----------------------------+---------------+
Table 2: New PW Interface Parameters Sub-TLV
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. VCCV Extended CV Types</span>
IANA has set up a registry of VCCV Extended CV Types. These are
8-bit values. Extended CV Type values 0x01, 0x02, 0x04, and 0x08 are
specified in <a href="#section-2.2">Section 2.2</a> of this document. The remaining values
(0x10 through 0x80) are to be assigned by IANA using the "IETF
Review" policy defined in [<a href="./rfc5226" title="">RFC5226</a>]. A VCCV Extended Connectivity
Verification Type description and a reference to an RFC approved by
the IESG are required for any assignment from this registry.
+--------------+----------------------------------------------------+
| Bit(Value) | Description |
+--------------+----------------------------------------------------+
| Bit 0 (0x01) | Independent mode for PW Fault Detection only |
| Bit 1 (0x02) | Independent mode for PW Fault Detection and AC/PW |
| | Fault Status Signaling |
| Bit 2 (0x04) | Coordinated mode for PW Fault Detection only |
| Bit 3 (0x08) | Coordinated mode for PW Fault Detection and AC/PW |
| | Fault Status Signaling |
| Bit 4 (0x10) | Unassigned |
| Bit 5 (0x20) | Unassigned |
| Bit 6 (0x40) | Unassigned |
| Bit 7 (0x80) | Unassigned |
+--------------+----------------------------------------------------+
Table 3: VCCV Extended Connectivity Verification (CV) Types
<span class="grey">Mirsky Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7189">RFC 7189</a> VCCV for MPLS-TP March 2014</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
Routers that implement the additional CV Type defined herein are
subject to the same security considerations as defined in [<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>],
[<a href="./rfc5880" title=""Bidirectional Forwarding Detection (BFD)"">RFC5880</a>], [<a href="./rfc5881" title=""Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)"">RFC5881</a>], and [<a href="./rfc6428" title=""Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile"">RFC6428</a>]. This specification does not
raise any additional security issues beyond those.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
The author gratefully acknowledges the thoughtful review, comments,
and explanations provided by Dave Allan and Carlos Pignataro.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC4446">RFC4446</a>] Martini, L., "IANA Allocations for Pseudowire Edge to Edge
Emulation (PWE3)", <a href="https://www.rfc-editor.org/bcp/bcp116">BCP 116</a>, <a href="./rfc4446">RFC 4446</a>, April 2006.
[<a id="ref-RFC4447">RFC4447</a>] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
Heron, "Pseudowire Setup and Maintenance Using the Label
Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April 2006.
[<a id="ref-RFC5085">RFC5085</a>] Nadeau, T. and C. Pignataro, "Pseudowire Virtual Circuit
Connectivity Verification (VCCV): A Control Channel for
Pseudowires", <a href="./rfc5085">RFC 5085</a>, December 2007.
[<a id="ref-RFC5880">RFC5880</a>] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", <a href="./rfc5880">RFC 5880</a>, June 2010.
[<a id="ref-RFC5881">RFC5881</a>] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", <a href="./rfc5881">RFC 5881</a>, June
2010.
[<a id="ref-RFC5885">RFC5885</a>] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding
Detection (BFD) for the Pseudowire Virtual Circuit
Connectivity Verification (VCCV)", <a href="./rfc5885">RFC 5885</a>, June 2010.
[<a id="ref-RFC6310">RFC6310</a>] Aissaoui, M., Busschbach, P., Martini, L., Morrow, M.,
Nadeau, T., and Y(J). Stein, "Pseudowire (PW) Operations,
Administration, and Maintenance (OAM) Message Mapping",
<a href="./rfc6310">RFC 6310</a>, July 2011.
<span class="grey">Mirsky Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7189">RFC 7189</a> VCCV for MPLS-TP March 2014</span>
[<a id="ref-RFC6428">RFC6428</a>] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
Connectivity Verification, Continuity Check, and Remote
Defect Indication for the MPLS Transport Profile", <a href="./rfc6428">RFC</a>
<a href="./rfc6428">6428</a>, November 2011.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
Author's Address
Greg Mirsky
Ericsson
EMail: gregory.mirsky@ericsson.com
Mirsky Standards Track [Page 7]
</pre>
|
