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
|
<pre>Internet Engineering Task Force (IETF) H. Li
Request for Comments: 6423 China Mobile
Updates: <a href="./rfc5586">5586</a> L. Martini
Category: Standards Track Cisco System
ISSN: 2070-1721 J. He
Huawei
F. Huang
Alcatel-Lucent
November 2011
<span class="h1">Using the Generic Associated Channel Label for Pseudowire in</span>
<span class="h1">the MPLS Transport Profile (MPLS-TP)</span>
Abstract
This document describes the requirements for using the Generic
Associated Channel Label (GAL) in pseudowires (PWs) in MPLS Transport
Profile (MPLS-TP) networks, and provides an update to the description
of GAL usage in <a href="./rfc5586">RFC 5586</a> by removing the restriction that is imposed
on using GAL for PWs, especially in MPLS-TP environments.
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/rfc6423">http://www.rfc-editor.org/info/rfc6423</a>.
<span class="grey">Li, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6423">RFC 6423</a> Using GAL in MPLS-TP PW November 2011</span>
Copyright Notice
Copyright (c) 2011 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.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-2">2</a>
<a href="#section-2.1">2.1</a>. Terminology ................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. GAL Usage for MPLS-TP PW ........................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. Acknowledgments .................................................<a href="#page-4">4</a>
<a href="#section-6">6</a>. References ......................................................<a href="#page-5">5</a>
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-5">5</a>
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a id="ref-RFC5586">RFC5586</a>] generalizes the Associated Channel mechanism of [<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>]
to be used for Sections, Label Switched Paths (LSPs), and Pseudowires
(PWs) in MPLS networks. [<a href="./rfc5085" title=""Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires"">RFC5085</a>] defines the Associated Channel
Header (ACH), and [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>] generalizes this for use as the Generic
Associated Channel (G-ACh).
[<a id="ref-RFC5586">RFC5586</a>] defines a generalized label-based exception mechanism using
the Generic Associated Channel Label (GAL) to work together with the
ACH for use with LSPs but prohibits GAL usage with PWs.
This document removes the restriction imposed by [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD 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="grey">Li, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6423">RFC 6423</a> Using GAL in MPLS-TP PW November 2011</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Terminology</span>
ACH Associated Channel Header
CW Control Word
G-ACh Generic Associated Channel
GAL Generic Associated Channel Label
MPLS-TP MPLS Transport Profile
OAM Operation, Administration, and Maintenance
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. GAL Usage for MPLS-TP PW</span>
According to the MPLS-TP requirements document [<a href="./rfc5654" title=""Requirements of an MPLS Transport Profile"">RFC5654</a>], it is
necessary that MPLS-TP mechanisms and capabilities be able to
interoperate with the existing IETF MPLS [<a href="./rfc3031" title=""Multiprotocol Label Switching Architecture"">RFC3031</a>] and IETF PWE3
[<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>] architectures as appropriate. [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>] differentiates
between the usage of the GAL with PWs in MPLS and MPLS-TP
environments in <a href="#section-4.2">Section 4.2</a> as follows:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
Concatenated Segments of LSPs, and with Sections, and MUST NOT be
used with PWs.
This indicates that the GAL can be used for MPLS-TP LSPs and
Sections, but not for PWs in an MPLS-TP network.
However, there is no restriction imposed on the usage of the GAL in
MPLS PWs, which is described immediately afterwards in the same
section (<a href="#section-4.2">Section 4.2</a>) of [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>]:
However, in other MPLS environments, this document places no
restrictions on where the GAL may appear within the label stack or
its use with PWs.
The inconsistency between the usage of the GAL with MPLS PWs and
MPLS-TP PWs may cause unnecessary implementation differences and is
in disagreement with the MPLS-TP requirements.
Therefore, this document specifies that the GAL can be used with
packets on a G-ACh on LSPs, Concatenated Segments of LSPs, Sections,
and PWs in both MPLS and MPLS-TP environments without discrimination.
<span class="grey">Li, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6423">RFC 6423</a> Using GAL in MPLS-TP PW November 2011</span>
[<a id="ref-RFC5586">RFC5586</a>] is updated by removing the restrictions on using GAL for PW
as follows:
- <a href="#section-1">Section 1</a> (Introduction) in [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>], the original text:
The GAL mechanism is defined to work together with the ACH for
LSPs and MPLS Sections.
is replaced by:
The GAL mechanism is defined to work together with the ACH for
LSPs and MPLS Sections, and for PWs.
- <a href="#section-4.2">Section 4.2</a>. (GAL Applicability and Usage) in [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>], the
original text:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
LSPs, Concatenated Segments of LSPs, and with Sections, and
MUST NOT be used with PWs. It MUST always be at the bottom of
the label stack (i.e., S bit set to 1). However, in other MPLS
environments, this document places no restrictions on where the
GAL may appear within the label stack or its use with PWs.
is replaced by:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
LSPs, Concatenated Segments of LSPs, and with Sections, and MAY
be used with PWs. The presence of a GAL indicates that an ACH
immediately follows the MPLS label stack.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
There are no further security considerations than those in [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
The authors would like to thank Luyuan Fang, Adrian Farrel, Haiyan
Zhang, Guanghui Sun, Italo Busi, and Matthew Bocci for their
contributions to this work.
The authors would also like to thank the authors of [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>] and
people who were involved in the development of [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>].
<span class="grey">Li, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6423">RFC 6423</a> Using GAL in MPLS-TP PW November 2011</span>
<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-RFC3031">RFC3031</a>] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", <a href="./rfc3031">RFC 3031</a>, January 2001.
[<a id="ref-RFC3985">RFC3985</a>] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation
Edge-to-Edge (PWE3) Architecture", <a href="./rfc3985">RFC 3985</a>, March 2005.
[<a id="ref-RFC5586">RFC5586</a>] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,
"MPLS Generic Associated Channel", <a href="./rfc5586">RFC 5586</a>, June 2009.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC5085">RFC5085</a>] Nadeau, T., Ed., and C. Pignataro, Ed., "Pseudowire Virtual
Circuit Connectivity Verification (VCCV): A Control Channel
for Pseudowires", <a href="./rfc5085">RFC 5085</a>, December 2007.
[<a id="ref-RFC5654">RFC5654</a>] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
Sprecher, N.,and S. Ueno, "Requirements of an MPLS
Transport Profile", <a href="./rfc5654">RFC 5654</a>, September 2009.
Authors' Addresses
Han Li
China Mobile Communications Corporation
EMail: lihan@chinamobile.com
Luca Martini
Cisco Systems, Inc.
EMail: lmartini@cisco.com
Jia He
Huawei Technologies Co., Ltd.
EMail: hejia@huawei.com
Feng Huang
Alcatel-Lucent shanghai Bell
EMail: feng.f.huang@alcatel-sbell.com.cn
Li, et al. Standards Track [Page 5]
</pre>
|
