| 1 |
<pre>Internet Engineering Task Force (IETF) P. Dutta |
| 2 |
Request for Comments: 7361 F. Balus |
| 3 |
Category: Standards Track Alcatel-Lucent |
| 4 |
ISSN: 2070-1721 O. Stokes |
| 5 |
Extreme Networks |
| 6 |
G. Calvignac |
| 7 |
Orange |
| 8 |
D. Fedyk |
| 9 |
Hewlett-Packard |
| 10 |
September 2014 |
| 11 |
|
| 12 |
|
| 13 |
<span class="h1">LDP Extensions for Optimized MAC Address Withdrawal</span> |
| 14 |
<span class="h1">in a Hierarchical Virtual Private LAN Service (H-VPLS)</span> |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
<a href="./rfc4762">RFC 4762</a> describes a mechanism to remove or unlearn Media Access |
| 19 |
Control (MAC) addresses that have been dynamically learned in a |
| 20 |
Virtual Private LAN Service (VPLS) instance for faster convergence on |
| 21 |
topology changes. The procedure also removes MAC addresses in the |
| 22 |
VPLS that do not require relearning due to such topology changes. |
| 23 |
This document defines an enhancement to the MAC address withdraw |
| 24 |
procedure with an empty MAC list (<a href="./rfc4762">RFC 4762</a>); this enhancement enables |
| 25 |
a Provider Edge (PE) device to remove only the MAC addresses that |
| 26 |
need to be relearned. Additional extensions to <a href="./rfc4762">RFC 4762</a> MAC withdraw |
| 27 |
procedures are specified to provide an optimized MAC flushing for the |
| 28 |
Provider Backbone Bridging (PBB) VPLS specified in <a href="./rfc7041">RFC 7041</a>. |
| 29 |
|
| 30 |
Status of This Memo |
| 31 |
|
| 32 |
This is an Internet Standards Track document. |
| 33 |
|
| 34 |
This document is a product of the Internet Engineering Task Force |
| 35 |
(IETF). It represents the consensus of the IETF community. It has |
| 36 |
received public review and has been approved for publication by the |
| 37 |
Internet Engineering Steering Group (IESG). Further information on |
| 38 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 39 |
|
| 40 |
Information about the current status of this document, any errata, |
| 41 |
and how to provide feedback on it may be obtained at |
| 42 |
<a href="http://www.rfc-editor.org/info/rfc7361">http://www.rfc-editor.org/info/rfc7361</a>. |
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2014 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
|
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-6">6</a> |
| 117 |
<a href="#section-2.1">2.1</a>. Requirements Language ......................................<a href="#page-6">6</a> |
| 118 |
<a href="#section-3">3</a>. Overview ........................................................<a href="#page-6">6</a> |
| 119 |
<a href="#section-3.1">3.1</a>. MAC Flushing on Activation of Backup Spoke PW ..............<a href="#page-8">8</a> |
| 120 |
<a href="#section-3.1.1">3.1.1</a>. MAC Flushing Initiated by PE-rs .....................<a href="#page-8">8</a> |
| 121 |
<a href="#section-3.1.2">3.1.2</a>. MAC Flushing Initiated by MTU-s .....................<a href="#page-8">8</a> |
| 122 |
<a href="#section-3.2">3.2</a>. MAC Flushing on Failure ....................................<a href="#page-9">9</a> |
| 123 |
<a href="#section-3.3">3.3</a>. MAC Flushing in PBB-VPLS ..................................<a href="#page-10">10</a> |
| 124 |
<a href="#section-4">4</a>. Problem Description ............................................<a href="#page-10">10</a> |
| 125 |
<a href="#section-4.1">4.1</a>. MAC Flushing Optimization in VPLS Resiliency ..............<a href="#page-10">10</a> |
| 126 |
<a href="#section-4.1.1">4.1.1</a>. MAC Flushing Optimization for Regular H-VPLS .......<a href="#page-11">11</a> |
| 127 |
4.1.2. MAC Flushing Optimization for Native Ethernet |
| 128 |
Access .............................................<a href="#page-13">13</a> |
| 129 |
<a href="#section-4.2">4.2</a>. Black-Holing Issue in PBB-VPLS ............................<a href="#page-13">13</a> |
| 130 |
<a href="#section-5">5</a>. Solution Description ...........................................<a href="#page-14">14</a> |
| 131 |
<a href="#section-5.1">5.1</a>. MAC Flushing Optimization for VPLS Resiliency .............<a href="#page-14">14</a> |
| 132 |
<a href="#section-5.1.1">5.1.1</a>. MAC Flush Parameters TLV ...........................<a href="#page-15">15</a> |
| 133 |
5.1.2. Application of the MAC Flush TLV in |
| 134 |
Optimized MAC Flushing .............................<a href="#page-16">16</a> |
| 135 |
<a href="#section-5.1.3">5.1.3</a>. MAC Flush TLV Processing Rules for Regular VPLS ....<a href="#page-17">17</a> |
| 136 |
<a href="#section-5.1.4">5.1.4</a>. Optimized MAC Flush Procedures .....................<a href="#page-18">18</a> |
| 137 |
<a href="#section-5.2">5.2</a>. LDP MAC Flush Extensions for PBB-VPLS .....................<a href="#page-19">19</a> |
| 138 |
<a href="#section-5.2.1">5.2.1</a>. MAC Flush TLV Processing Rules for PBB-VPLS ........<a href="#page-20">20</a> |
| 139 |
<a href="#section-5.2.2">5.2.2</a>. Applicability of the MAC Flush Parameters TLV ......<a href="#page-22">22</a> |
| 140 |
<a href="#section-6">6</a>. Operational Considerations .....................................<a href="#page-23">23</a> |
| 141 |
<a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-24">24</a> |
| 142 |
<a href="#section-7.1">7.1</a>. New LDP TLV ...............................................<a href="#page-24">24</a> |
| 143 |
<a href="#section-7.2">7.2</a>. New Registry for MAC Flush Flags ..........................<a href="#page-24">24</a> |
| 144 |
<a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-24">24</a> |
| 145 |
<a href="#section-9">9</a>. Contributing Author ............................................<a href="#page-25">25</a> |
| 146 |
<a href="#section-10">10</a>. Acknowledgements ..............................................<a href="#page-25">25</a> |
| 147 |
<a href="#section-11">11</a>. References ....................................................<a href="#page-25">25</a> |
| 148 |
<a href="#section-11.1">11.1</a>. Normative References .....................................<a href="#page-25">25</a> |
| 149 |
<a href="#section-11.2">11.2</a>. Informative References ...................................<a href="#page-25">25</a> |
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
A method of Virtual Private LAN Service (VPLS), also known as |
| 172 |
Transparent LAN Services (TLS), is described in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. A VPLS is |
| 173 |
created using a collection of one or more point-to-point pseudowires |
| 174 |
(PWs) [<a href="./rfc4664" title=""Framework for Layer 2 Virtual Private Networks (L2VPNs)"">RFC4664</a>] configured in a flat, full-mesh topology. The mesh |
| 175 |
topology provides a LAN segment or broadcast domain that is fully |
| 176 |
capable of learning and forwarding on Ethernet Media Access Control |
| 177 |
(MAC) addresses at the Provider Edge (PE) devices. |
| 178 |
|
| 179 |
This VPLS full-mesh core configuration can be augmented with |
| 180 |
additional non-meshed spoke nodes to provide a Hierarchical VPLS |
| 181 |
(H-VPLS) service [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. Throughout this document, this |
| 182 |
configuration is referred to as "regular" H-VPLS. |
| 183 |
|
| 184 |
[<a id="ref-RFC7041">RFC7041</a>] describes how Provider Backbone Bridging (PBB) can be |
| 185 |
integrated with VPLS to allow for useful PBB capabilities while |
| 186 |
continuing to avoid the use of the Multiple Spanning Tree Protocol |
| 187 |
(MSTP) in the backbone. The combined solution, referred to as |
| 188 |
"PBB-VPLS", results in better scalability in terms of number of |
| 189 |
service instances, PWs, and C-MAC (Customer MAC) addresses that need |
| 190 |
to be handled in the VPLS PEs, depending on the location of the |
| 191 |
I-component in the PBB-VPLS topology. |
| 192 |
|
| 193 |
A MAC address withdrawal mechanism for VPLS is described in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] |
| 194 |
to remove or unlearn MAC addresses for faster convergence on topology |
| 195 |
changes in resilient H-VPLS topologies. Note that the H-VPLS |
| 196 |
topology discussed in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] describes the two-tier hierarchy in |
| 197 |
VPLS as the basic building block of H-VPLS, but it is possible to |
| 198 |
have a multi-tier hierarchy in an H-VPLS. |
| 199 |
|
| 200 |
|
| 201 |
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 |
|
| 206 |
|
| 207 |
|
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 223 |
|
| 224 |
|
| 225 |
Figure 1 is reproduced from [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] and illustrates dual-homing |
| 226 |
in H-VPLS. |
| 227 |
|
| 228 |
PE2-rs |
| 229 |
+--------+ |
| 230 |
| | |
| 231 |
| -- | |
| 232 |
| / \ | |
| 233 |
CE-1 | \S / | |
| 234 |
\ | -- | |
| 235 |
\ +--------+ |
| 236 |
\ MTU-s PE1-rs / | |
| 237 |
+--------+ +--------+ / | |
| 238 |
| | | | / | |
| 239 |
| -- | Primary PW | -- |---/ | |
| 240 |
| / \ |- - - - - - - - - - - | / \ | | |
| 241 |
| \S / | | \S / | | |
| 242 |
| -- | | -- |---\ | |
| 243 |
+--------+ +--------+ \ | |
| 244 |
/ \ \ | |
| 245 |
/ \ +--------+ |
| 246 |
/ \ | | |
| 247 |
CE-2 \ | -- | |
| 248 |
\ Secondary PW | / \ | |
| 249 |
- - - - - - - - - - - - - - - - - | \S / | |
| 250 |
| -- | |
| 251 |
+--------+ |
| 252 |
PE3-rs |
| 253 |
|
| 254 |
Figure 1: An Example of a Dual-Homed MTU-s |
| 255 |
|
| 256 |
An example usage of the MAC flushing mechanism is the dual-homed |
| 257 |
H-VPLS where an edge device called the Multi-Tenant Unit switch |
| 258 |
(MTU-s) [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] is connected to two PE devices via a primary spoke |
| 259 |
PW and backup spoke PW, respectively. Such redundancy is designed to |
| 260 |
protect against the failure of the primary spoke PW or primary PE |
| 261 |
device. There could be multiple methods of dual-homing in H-VPLS |
| 262 |
that are not described in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. For example, note the following |
| 263 |
statement from <a href="./rfc4762#section-10.2.1">Section 10.2.1 of [RFC4762]</a>. |
| 264 |
|
| 265 |
How a spoke is designated primary or secondary is outside the |
| 266 |
scope of this document. For example, a spanning tree instance |
| 267 |
running between only the MTU-s and the two PE-rs nodes is one |
| 268 |
possible method. Another method could be configuration. |
| 269 |
|
| 270 |
This document intends to clarify several H-VPLS dual-homing models |
| 271 |
that are deployed in practice and various use cases of LDP-based MAC |
| 272 |
flushing in these models. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 282 |
|
| 283 |
This document uses the terminology defined in [<a href="./rfc7041" title=""Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone Bridging"">RFC7041</a>], [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>], |
| 284 |
[<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>], and [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. |
| 285 |
|
| 286 |
Throughout this document, "Virtual Private LAN Service" (VPLS) refers |
| 287 |
to the emulated bridged LAN service offered to a customer. "H-VPLS" |
| 288 |
refers to the hierarchical connectivity or layout of the MTU-s and |
| 289 |
the Provider Edge routing- and switching-capable (PE-rs) devices |
| 290 |
offering the VPLS [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. |
| 291 |
|
| 292 |
The terms "spoke node" and "MTU-s" in H-VPLS are used |
| 293 |
interchangeably. |
| 294 |
|
| 295 |
"Spoke PW" refers to the Pseudowire (PW) that provides connectivity |
| 296 |
between MTU-s and PE-rs nodes. |
| 297 |
|
| 298 |
"Mesh PW" refers to the PW that provides connectivity between PE-rs |
| 299 |
nodes in a VPLS full-mesh core. |
| 300 |
|
| 301 |
"MAC flush message" refers to a Label Distribution Protocol (LDP) |
| 302 |
address withdraw message without a MAC List TLV. |
| 303 |
|
| 304 |
A MAC flush message "in the context of a PW" refers to the message |
| 305 |
that has been received over the LDP session that is used to set up |
| 306 |
the PW used to provide connectivity in VPLS. The MAC flush message |
| 307 |
carries the context of the PW in terms of the Forwarding Equivalence |
| 308 |
Class (FEC) TLV associated with the PW [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] [<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>]. |
| 309 |
|
| 310 |
In general, "MAC flushing" refers to the method of initiating and |
| 311 |
processing MAC flush messages across a VPLS instance. |
| 312 |
|
| 313 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Requirements Language</span> |
| 314 |
|
| 315 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 316 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 317 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 318 |
|
| 319 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span> |
| 320 |
|
| 321 |
When the MTU-s switches over to the backup PW, the requirement is to |
| 322 |
flush the MAC addresses learned in the corresponding Virtual Switch |
| 323 |
Instance (VSI) in peer PE devices participating in the full mesh, to |
| 324 |
avoid the black-holing of frames to those addresses. This is |
| 325 |
accomplished by sending an LDP address withdraw message -- a new |
| 326 |
message defined in this document -- from the PE that is no longer |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 335 |
|
| 336 |
|
| 337 |
connected to the MTU-s with the primary PW. The new message contains |
| 338 |
a list of MAC addresses to be removed and is sent to all other PEs |
| 339 |
over the corresponding LDP sessions. |
| 340 |
|
| 341 |
In order to minimize the impact on LDP convergence time and |
| 342 |
scalability when a MAC List TLV contains a large number of MAC |
| 343 |
addresses, many implementations use an LDP address withdraw message |
| 344 |
with an empty MAC list. When a PE-rs switch in the full mesh of |
| 345 |
H-VPLS receives this message, it also flushes MAC addresses that are |
| 346 |
not affected due to the topology change, thus leading to unnecessary |
| 347 |
flooding and relearning. Throughout this document, the term "MAC |
| 348 |
flush message" is used to specify an LDP address withdraw message |
| 349 |
with an empty MAC list as described in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. The solutions |
| 350 |
described in this document are applicable only to LDP address |
| 351 |
withdraw messages with empty MAC lists. |
| 352 |
|
| 353 |
In a VPLS topology, the core PWs remain active and learning happens |
| 354 |
on the PE-rs nodes. However, when the VPLS topology changes, the |
| 355 |
PE-rs must relearn using MAC address withdrawal or flushing. As per |
| 356 |
the MAC address withdrawal processing rules in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>], a PE |
| 357 |
device, on receiving a MAC flush message, removes all MAC addresses |
| 358 |
associated with the specified VPLS instance (as indicated in the FEC |
| 359 |
TLV) except the MAC addresses learned over the PW associated with |
| 360 |
this signaling session over which the message was received. |
| 361 |
Throughout this document, we use the terminology "positive" MAC |
| 362 |
flushing or "flush-all-but-mine" for this type of MAC flush message |
| 363 |
and its actions. |
| 364 |
|
| 365 |
This document introduces an optimized "negative" MAC flush message, |
| 366 |
described in <a href="#section-3.2">Section 3.2</a>, that can be configured to improve the |
| 367 |
response to topology changes in a number of Ethernet topologies where |
| 368 |
the Service Level Agreement (SLA) is dependent on minimal disruption |
| 369 |
and fast restoration of affected traffic. This new message is used |
| 370 |
in the case of Provider Backbone Bridging (PBB) topologies to |
| 371 |
restrict the flushing to a set of service instances (I-SIDs). It is |
| 372 |
also important to note that the MAC flush message described in |
| 373 |
[<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>], which is called "a positive MAC flush message" in this |
| 374 |
document, MUST always be handled for Backbone MACs (B-MACs) in cases |
| 375 |
where the core nodes change or fail. In dual-homed or multi-homed |
| 376 |
edge topologies, the procedures in this document augment [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] |
| 377 |
messages and provide less disruption for those cases. |
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. MAC Flushing on Activation of Backup Spoke PW</span> |
| 394 |
|
| 395 |
This section describes scenarios where MAC flush withdrawal is |
| 396 |
initiated on activation of a backup PW in H-VPLS. |
| 397 |
|
| 398 |
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. MAC Flushing Initiated by PE-rs</span> |
| 399 |
|
| 400 |
[<a id="ref-RFC4762">RFC4762</a>] specifies that on failure of the primary PW it is PE3-rs |
| 401 |
(Figure 1) that initiates MAC flushing towards the core. However, |
| 402 |
note that PE3-rs can initiate MAC flushing only when PE3-rs is |
| 403 |
dual-homing "aware" -- that is, there is some redundancy management |
| 404 |
protocol running between the MTU-s and its host PE-rs devices. The |
| 405 |
scope of this document is applicable to several dual-homing or |
| 406 |
multi-homing protocols. This document illustrates that multi-homing |
| 407 |
can be improved with negative MAC flushing. One example is BGP-based |
| 408 |
multi-homing in LDP-based VPLS, which uses the procedures defined in |
| 409 |
[<a href="#ref-VPLS-MH" title=""BGP based Multi-homing in Virtual Private LAN Service"">VPLS-MH</a>]. In this method of dual-homing, PE3-rs would neither |
| 410 |
forward any traffic to the MTU-s nor receive any traffic from the |
| 411 |
MTU-s while PE1-rs is acting as a primary (or designated forwarder). |
| 412 |
|
| 413 |
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. MAC Flushing Initiated by MTU-s</span> |
| 414 |
|
| 415 |
When dual-homing is achieved by manual configuration in the MTU-s, |
| 416 |
the hosting PE-rs devices are dual-homing "agnostic", and PE3-rs |
| 417 |
cannot initiate MAC flush messages. PE3-rs can send or receive |
| 418 |
traffic over the backup PW, since the dual-homing control is with the |
| 419 |
MTU-s only. When the backup PW is made active by the MTU-s, the |
| 420 |
MTU-s triggers a MAC flush message. The message is sent over the LDP |
| 421 |
session associated with the newly activated PW. On receiving the MAC |
| 422 |
flush message from the MTU-s, PE3-rs (the PE-rs device with a |
| 423 |
now-active PW) would flush all the MAC addresses it has learned, |
| 424 |
except the ones learned over the newly activated spoke PW. PE3-rs |
| 425 |
further initiates a MAC flush message to all other PE devices in the |
| 426 |
core. Note that a forced switchover to the backup PW can also be |
| 427 |
invoked by the MTU-s due to maintenance or administrative activities |
| 428 |
on the former primary spoke PW. |
| 429 |
|
| 430 |
The method of MAC flushing initiated by the MTU-s is modeled after |
| 431 |
Topology Change Notification (TCN) in the Rapid Spanning Tree |
| 432 |
Protocol (RSTP) [<a href="#ref-IEEE.802.1Q-2011">IEEE.802.1Q-2011</a>]. When a bridge switches from a |
| 433 |
failed link to the backup link, the bridge sends out a TCN message |
| 434 |
over the newly activated link. Upon receiving this message, the |
| 435 |
upstream bridge flushes its entire list of MAC addresses, except the |
| 436 |
ones received over this link. The upstream bridge then sends the TCN |
| 437 |
message out of its other ports in that spanning tree instance. The |
| 438 |
message is further relayed along the spanning tree by the other |
| 439 |
bridges. |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 447 |
|
| 448 |
|
| 449 |
The MAC flushing information is propagated in the control plane. The |
| 450 |
control-plane message propagation is associated with the data path |
| 451 |
and hence follows propagation rules similar to those used for |
| 452 |
forwarding in the LDP data plane. For example, PE-rs nodes follow |
| 453 |
the data-plane "split-horizon" forwarding rules in H-VPLS (refer to |
| 454 |
<a href="./rfc4762#section-4.4">Section 4.4 of [RFC4762]</a>). Therefore, a MAC flush message is |
| 455 |
propagated in the context of mesh PW(s) when it is received in the |
| 456 |
context of a spoke PW. When a PE-rs node receives a MAC flush |
| 457 |
message in the context of a mesh PW, then it is not propagated to |
| 458 |
other mesh PWs. |
| 459 |
|
| 460 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. MAC Flushing on Failure</span> |
| 461 |
|
| 462 |
MAC flushing on failure, or "negative" MAC flushing, is introduced in |
| 463 |
this document. Negative MAC flushing is an improvement on the |
| 464 |
current practice of sending a MAC flush message with an empty MAC |
| 465 |
list as described in <a href="#section-3.1.1">Section 3.1.1</a>. We use the term "negative" MAC |
| 466 |
flushing or "flush-all-from-me" for this kind of flushing action as |
| 467 |
opposed to the "positive" MAC flush action in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. In negative |
| 468 |
MAC flushing, the MAC flushing is initiated by PE1-rs (Figure 1) on |
| 469 |
detection of failure of the primary spoke PW. The MAC flush message |
| 470 |
is sent to all participating PE-rs devices in the VPLS full mesh. |
| 471 |
PE1-rs should initiate MAC flushing only if PE1-rs is dual-homing |
| 472 |
aware. (If PE1-rs is dual-homing agnostic, the policy is to not |
| 473 |
initiate MAC flushing on failure, since that could cause unnecessary |
| 474 |
flushing in the case of a single-homed MTU-s.) The specific dual- |
| 475 |
homing protocols for this scenario are outside the scope of this |
| 476 |
document, but the operator can choose to use the optimized MAC |
| 477 |
flushing described in this document or the [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] procedures. |
| 478 |
|
| 479 |
The procedure for negative MAC flushing is beneficial and results in |
| 480 |
less disruption than the [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] procedures, including when the |
| 481 |
MTU-s is dual-homed with a variety of Ethernet technologies, not just |
| 482 |
LDP. The negative MAC flush message is a more targeted MAC flush, |
| 483 |
and the other PE-rs nodes will flush only the specified MACs. This |
| 484 |
targeted MAC flush cannot be achieved with the MAC address withdraw |
| 485 |
message defined in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. Negative MAC flushing typically |
| 486 |
results in a smaller set of MACs to be flushed and results in less |
| 487 |
disruption for these topologies. |
| 488 |
|
| 489 |
Note that in the case of negative MAC flushing the list SHOULD be |
| 490 |
only the MACs for the affected MTU-s. If the list is empty, then the |
| 491 |
negative MAC flush procedures will result in flushing and relearning |
| 492 |
all attached MTU-s devices for the originating PE-rs. |
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. MAC Flushing in PBB-VPLS</span> |
| 506 |
|
| 507 |
[<a id="ref-RFC7041">RFC7041</a>] describes how PBB can be integrated with VPLS to allow for |
| 508 |
useful PBB capabilities while continuing to avoid the use of MSTP in |
| 509 |
the backbone. The combined solution, referred to as "PBB-VPLS", |
| 510 |
results in better scalability in terms of the number of service |
| 511 |
instances, PWs, and C-MACs that need to be handled in the VPLS PE-rs |
| 512 |
devices. This document describes extensions to LDP MAC flushing |
| 513 |
procedures described in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] that are required to build |
| 514 |
desirable capabilities for the PBB-VPLS solution. |
| 515 |
|
| 516 |
The solution proposed in this document is generic and is applicable |
| 517 |
when Multi-Segment Pseudowires (MS-PWs) [<a href="./rfc6073" title=""Segmented Pseudowire"">RFC6073</a>] are used in |
| 518 |
interconnecting PE devices in H-VPLS. There could be other H-VPLS |
| 519 |
models not defined in this document where the solution may be |
| 520 |
applicable. |
| 521 |
|
| 522 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Problem Description</span> |
| 523 |
|
| 524 |
This section describes the problems in detail with respect to various |
| 525 |
MAC flushing actions described in <a href="#section-3">Section 3</a>. |
| 526 |
|
| 527 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. MAC Flushing Optimization in VPLS Resiliency</span> |
| 528 |
|
| 529 |
This section describes the optimizations required in MAC flushing |
| 530 |
procedures when H-VPLS resiliency is provided by primary and backup |
| 531 |
spoke PWs. |
| 532 |
|
| 533 |
|
| 534 |
|
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. MAC Flushing Optimization for Regular H-VPLS</span> |
| 562 |
|
| 563 |
Figure 2 shows a dual-homed H-VPLS scenario for a VPLS instance, |
| 564 |
where the problem with the existing MAC flushing method is as |
| 565 |
explained in <a href="#section-3">Section 3</a>. |
| 566 |
|
| 567 |
PE1-rs PE3-rs |
| 568 |
+--------+ +--------+ |
| 569 |
| | | | |
| 570 |
| -- | | -- | |
| 571 |
Customer Site 1 | / \ |------------------| / \ |->Z |
| 572 |
X->CE-1 /-----| \s / | | \s / | |
| 573 |
\ primary spoke PW | -- | /------| -- | |
| 574 |
\ / +--------+ / +--------+ |
| 575 |
\ (MTU-s)/ | \ / | |
| 576 |
+--------+/ | \ / | |
| 577 |
| | | \ / | |
| 578 |
| -- | | \ / | |
| 579 |
| / \ | | H-VPLS Full-Mesh Core| |
| 580 |
| \s / | | / \ | |
| 581 |
| -- | | / \ | |
| 582 |
/+--------+\ | / \ | |
| 583 |
/ backup spoke PW | / \ | |
| 584 |
/ \ +--------+ \--------+--------+ |
| 585 |
Y->CE-2 \ | | | | |
| 586 |
Customer Site 2 \------| -- | | -- | |
| 587 |
| / \ |------------------| / \ |-> |
| 588 |
| \s / | | \s / | |
| 589 |
| -- | | -- | |
| 590 |
+--------+ +--------+ |
| 591 |
PE2-rs PE4-rs |
| 592 |
|
| 593 |
Figure 2: Dual-Homed MTU-s in Two-Tier Hierarchy H-VPLS |
| 594 |
|
| 595 |
In Figure 2, the MTU-s is dual-homed to PE1-rs and PE2-rs. Only the |
| 596 |
primary spoke PW is active at the MTU-s; thus, PE1-rs is acting as |
| 597 |
the active device (designated forwarder) to reach the full mesh in |
| 598 |
the VPLS instance. The MAC addresses of nodes located at access |
| 599 |
sites (behind CE-1 and CE-2) are learned at PE1-rs over the primary |
| 600 |
spoke PW. Let's say X represents a set of such MAC addresses located |
| 601 |
behind CE-1. MAC Z represents one of a possible set of other |
| 602 |
destination MACs. As packets flow from X to other MACs in the VPLS |
| 603 |
network, PE2-rs, PE3-rs, and PE4-rs learn about X on their respective |
| 604 |
mesh PWs terminating at PE1-rs. When the MTU-s switches to the |
| 605 |
backup spoke PW and activates it, PE2-rs becomes the active device |
| 606 |
(designated forwarder) to reach the full-mesh core for the MTU-s. |
| 607 |
Traffic entering the H-VPLS from CE-1 and CE-2 is diverted by the |
| 608 |
MTU-s to the spoke PW to PE2-rs. Traffic destined from PE2-rs, |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 615 |
|
| 616 |
|
| 617 |
PE3-rs, and PE4-rs to X will be black-holed until the MAC address |
| 618 |
aging timer expires (the default is 5 minutes) or a packet flows from |
| 619 |
X to other addresses through PE2-rs. |
| 620 |
|
| 621 |
For example, if a packet flows from MAC Z to MAC X after the backup |
| 622 |
spoke PW is active, packets from MAC Z travel from PE3-rs to PE1-rs |
| 623 |
and are dropped. However, if a packet with MAC X as source and MAC Z |
| 624 |
as destination arrives at PE2-rs, PE2-rs will now learn that MAC X is |
| 625 |
on the backup spoke PW and will forward to MAC Z. At this point, |
| 626 |
traffic from PE3-rs to MAC X will go to PE2-rs, since PE3-rs has also |
| 627 |
learned about MAC X. Therefore, a mechanism is required to make this |
| 628 |
learning more timely in cases where traffic is not bidirectional. |
| 629 |
|
| 630 |
To avoid traffic black-holing, the MAC addresses that have been |
| 631 |
learned in the upstream VPLS full mesh through PE1-rs must be |
| 632 |
relearned or removed from the MAC Forwarding Information Bases (FIBs) |
| 633 |
in the VSIs at PE2-rs, PE3-rs, and PE4-rs. If PE1-rs and PE2-rs are |
| 634 |
dual-homing agnostic, then on activation of the standby PW from the |
| 635 |
MTU-s, a MAC flush message will be sent by the MTU-s to PE2-rs that |
| 636 |
will flush all the MAC addresses learned in the VPLS instance at |
| 637 |
PE2-rs from all other PWs except the PW connected to the MTU-s. |
| 638 |
|
| 639 |
PE2-rs further relays the MAC flush messages to all other PE-rs |
| 640 |
devices in the full mesh. The same processing rule applies for all |
| 641 |
those PE-rs devices: all the MAC addresses are flushed except the |
| 642 |
ones learned on the PW connected to PE2-rs. For example, at PE3-rs |
| 643 |
all of the MAC addresses learned from the PWs connected to PE1-rs and |
| 644 |
PE4-rs are flushed and relearned subsequently. Before the relearning |
| 645 |
happens, flooding of unknown destination MAC addresses takes place |
| 646 |
throughout the network. As the number of PE-rs devices in the full |
| 647 |
mesh increases, the number of unaffected MAC addresses flushed in a |
| 648 |
VPLS instance also increases, thus leading to unnecessary flooding |
| 649 |
and relearning. With a large number of VPLS instances provisioned in |
| 650 |
the H-VPLS network topology, the amount of unnecessary flooding and |
| 651 |
relearning increases. An optimization, described below, is required |
| 652 |
that will flush only the MAC addresses learned from the respective |
| 653 |
PWs between PE1-rs and other PE devices in the full mesh, to minimize |
| 654 |
the relearning and flooding in the network. In the example above, |
| 655 |
only the MAC addresses in sets X and Y (shown in Figure 2) need to be |
| 656 |
flushed across the core. |
| 657 |
|
| 658 |
The same case is applicable when PE1-rs and PE2-rs are dual-homing |
| 659 |
aware and participate in a designated forwarder election. When |
| 660 |
PE2-rs becomes the active device for the MTU-s, then PE2-rs MAY |
| 661 |
initiate MAC flushing towards the core. The receiving action of the |
| 662 |
MAC flush message in other PE-rs devices is the same as in MAC |
| 663 |
flushing initiated by the MTU-s. This is the behavior specified in |
| 664 |
[<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. MAC Flushing Optimization for Native Ethernet Access</span> |
| 674 |
|
| 675 |
The analysis in <a href="#section-4.1.1">Section 4.1.1</a> applies also to the native Ethernet |
| 676 |
access into a VPLS. In such a scenario, one active endpoint and one |
| 677 |
or more standby endpoints terminate into two or more VPLS or H-VPLS |
| 678 |
PE-rs devices. Examples of this dual-homed access are ITU-T |
| 679 |
[<a href="#ref-ITU.G8032" title=""Ethernet ring protection switching"">ITU.G8032</a>] access rings or any proprietary multi-chassis Link |
| 680 |
Aggregation Group (LAG) emulations. Upon failure of the active |
| 681 |
native Ethernet endpoint on PE1-rs, an optimized MAC flush message is |
| 682 |
required to be initiated by PE1-rs to ensure that on PE2-rs, PE3-rs, |
| 683 |
and PE4-rs only the MAC addresses learned from the respective PWs |
| 684 |
connected to PE1-rs are being flushed. |
| 685 |
|
| 686 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Black-Holing Issue in PBB-VPLS</span> |
| 687 |
|
| 688 |
In a PBB-VPLS deployment, a B-component VPLS (B-VPLS) may be used as |
| 689 |
infrastructure to support one or more I-component instances. The |
| 690 |
B-VPLS control plane (LDP Signaling) and learning of Backbone MACs |
| 691 |
(B-MACs) replace the I-component control plane and learning of |
| 692 |
Customer MACs (C-MACs) throughout the MPLS core. This raises an |
| 693 |
additional challenge related to black-hole avoidance in the |
| 694 |
I-component domain as described in this section. Figure 3 describes |
| 695 |
the case of a Customer Edge (CE) device (node A) dual-homed to two |
| 696 |
I-component instances located on two PBB-VPLS PEs (PE1-rs and |
| 697 |
PE2-rs). |
| 698 |
|
| 699 |
IP/MPLS Core |
| 700 |
+--------------+ |
| 701 |
|PE2-rs | |
| 702 |
+----+ | |
| 703 |
|PBB | | |
| 704 |
|VPLS| +-+ | |
| 705 |
|(B2)|---|P| | |
| 706 |
Stby/+----+ /+-+\ |PE3-rs |
| 707 |
/ +----+ / \+----+ |
| 708 |
+---+/ |PBB |/ +-+ |PBB | +---+ |
| 709 |
C-MAC X--|CE |---|VPLS|---|P|--|VPLS|---|CE |--C-MAC Y |
| 710 |
| |Act|(B1)| +-+ | | | | |
| 711 |
+---+ +----+ +----+ +---+ |
| 712 |
A |PE1-rs | B |
| 713 |
| | |
| 714 |
+--------------+ |
| 715 |
|
| 716 |
Figure 3: PBB Black-Holing Issue - CE Dual-Homing Use Case |
| 717 |
|
| 718 |
The link between PE1-rs and CE-A is active (marked with A), while the |
| 719 |
link between CE-A and PE2-rs is in standby/blocked status. In the |
| 720 |
network diagram, C-MAC X is one of the MAC addresses located behind |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 727 |
|
| 728 |
|
| 729 |
CE-A in the customer domain, C-MAC Y is behind CE-B, and the B-VPLS |
| 730 |
instances on PE1-rs are associated with B-MAC B1 and PE2-rs with |
| 731 |
B-MAC B2. |
| 732 |
|
| 733 |
As the packets flow from C-MAC X to C-MAC Y through PE1-rs with |
| 734 |
B-MAC B1, the remote PE-rs devices participating in the B-VPLS with |
| 735 |
the same I-SID (for example, PE3-rs) will learn the C-MAC X |
| 736 |
associated with B-MAC B1 on PE1-rs. Under a failure condition of the |
| 737 |
link between CE-A and PE1-rs and on activation of the link to PE2-rs, |
| 738 |
the remote PE-rs devices (for example, PE3-rs) will forward the |
| 739 |
traffic destined for C-MAC X to B-MAC B1, resulting in PE1-rs black- |
| 740 |
holing that traffic until the aging timer expires or a packet flows |
| 741 |
from X to Y through PE2-rs (B-MAC B2). This may take a long time |
| 742 |
(the default aging timer is 5 minutes) and may affect a large number |
| 743 |
of flows across multiple I-components. |
| 744 |
|
| 745 |
A possible solution to this issue is to use the existing LDP MAC |
| 746 |
flushing method as specified in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] to flush the B-MAC |
| 747 |
associated with the PE-rs in the B-VPLS domain where the failure |
| 748 |
occurred. This will automatically flush the C-MAC-to-B-MAC |
| 749 |
association in the remote PE-rs devices. This solution has the |
| 750 |
disadvantage of producing a lot of unnecessary MAC flushing in the |
| 751 |
B-VPLS domain as there was no failure or topology change affecting |
| 752 |
the Backbone domain. |
| 753 |
|
| 754 |
A better solution -- one that would propagate the I-component events |
| 755 |
through the backbone infrastructure (B-VPLS) -- is required in order |
| 756 |
to flush only the C-MAC-to-B-MAC associations in the remote PBB-VPLS- |
| 757 |
capable PE-rs devices. Since there are no I-component control-plane |
| 758 |
exchanges across the PBB backbone, extensions to the B-VPLS control |
| 759 |
plane are required to propagate the I-component MAC flushing events |
| 760 |
across the B-VPLS. |
| 761 |
|
| 762 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Solution Description</span> |
| 763 |
|
| 764 |
This section describes the solution for the problem space described |
| 765 |
in <a href="#section-4">Section 4</a>. |
| 766 |
|
| 767 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. MAC Flushing Optimization for VPLS Resiliency</span> |
| 768 |
|
| 769 |
The basic principle of the optimized MAC flush mechanism is explained |
| 770 |
with reference to Figure 2. The optimization is achieved by |
| 771 |
initiating MAC flushing on failure as described in <a href="#section-3.2">Section 3.2</a>. |
| 772 |
|
| 773 |
PE1-rs would initiate MAC flushing towards the core on detection of |
| 774 |
failure of the primary spoke PW between the MTU-s and PE1-rs (or |
| 775 |
status change from active to standby [<a href="./rfc6718" title=""Pseudowire Redundancy"">RFC6718</a>]). This method is |
| 776 |
referred to as "MAC flushing on failure" throughout this document. |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 783 |
|
| 784 |
|
| 785 |
The MAC flush message would indicate to receiving PE-rs devices to |
| 786 |
flush all MACs learned over the PW in the context of the VPLS for |
| 787 |
which the MAC flush message is received. Each PE-rs device in the |
| 788 |
full mesh that receives the message identifies the VPLS instance and |
| 789 |
its respective PW that terminates in PE1-rs from the FEC TLV received |
| 790 |
in the message and/or LDP session. Thus, the PE-rs device flushes |
| 791 |
only the MAC addresses learned from that PW connected to PE1-rs, |
| 792 |
minimizing the required relearning and the flooding throughout the |
| 793 |
VPLS domain. |
| 794 |
|
| 795 |
This section defines a generic MAC Flush Parameters TLV for LDP |
| 796 |
[<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>]. Throughout this document, the MAC Flush Parameters TLV is |
| 797 |
also referred to as the "MAC Flush TLV". A MAC Flush TLV carries |
| 798 |
information on the desired action at the PE-rs device receiving the |
| 799 |
message and is used for optimized MAC flushing in VPLS. The MAC |
| 800 |
Flush TLV can also be used for the [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] style of MAC flushing as |
| 801 |
explained in <a href="#section-3">Section 3</a>. |
| 802 |
|
| 803 |
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. MAC Flush Parameters TLV</span> |
| 804 |
|
| 805 |
The MAC Flush Parameters TLV is described below: |
| 806 |
|
| 807 |
0 1 2 3 |
| 808 |
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 |
| 809 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 810 |
|1|1| MAC Flush TLV (0x0406) | Length | |
| 811 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 812 |
| Flags | Sub-TLV Type | Sub-TLV Length | |
| 813 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 814 |
| Sub-TLV Variable-Length Value | |
| 815 |
| " | |
| 816 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 817 |
|
| 818 |
The U-bit and F-bit [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>] are set to forward if unknown so that |
| 819 |
potential intermediate VPLS PE-rs devices unaware of the new TLV can |
| 820 |
just propagate it transparently. In the case of a B-VPLS network |
| 821 |
that has PBB-VPLS in the core with no I-components attached, this |
| 822 |
message can still be useful to edge B-VPLS devices that do have the |
| 823 |
I-components with the I-SIDs and understand the message. The MAC |
| 824 |
Flush Parameters TLV type is 0x0406, as assigned by IANA. The |
| 825 |
encoding of the TLV follows the standard LDP TLV encoding described |
| 826 |
in [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>]. |
| 827 |
|
| 828 |
The TLV value field contains a 1-byte Flag field used as described |
| 829 |
below. Further, the TLV value MAY carry one or more sub-TLVs. Any |
| 830 |
sub-TLV definition for the above TLV MUST address the actions in |
| 831 |
combination with other existing sub-TLVs. |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 839 |
|
| 840 |
|
| 841 |
The detailed format for the Flags bit vector is described below: |
| 842 |
|
| 843 |
0 1 2 3 4 5 6 7 |
| 844 |
+-+-+-+-+-+-+-+-+ |
| 845 |
|C|N| MBZ | (MBZ = MUST Be Zero) |
| 846 |
+-+-+-+-+-+-+-+-+ |
| 847 |
|
| 848 |
The 1-byte Flag field is mandatory. The following flags are |
| 849 |
defined: |
| 850 |
|
| 851 |
C-flag: Used to indicate the context of the PBB-VPLS component in |
| 852 |
which MAC flushing is required. For PBB-VPLS, there are two |
| 853 |
contexts of MAC flushing -- the Backbone VPLS (B-component |
| 854 |
VPLS) and the Customer VPLS (I-component VPLS). The C-flag |
| 855 |
MUST be ZERO (C = 0) when a MAC flush action for the B-VPLS is |
| 856 |
required and MUST be set (C = 1) when the MAC flush action for |
| 857 |
the I-component is required. In the regular H-VPLS case, the |
| 858 |
C-flag MUST be ZERO (C = 0) to indicate that the flush applies |
| 859 |
to the current VPLS context. |
| 860 |
|
| 861 |
N-flag: Used to indicate whether a positive (N = 0, |
| 862 |
flush-all-but-mine) or negative (N = 1, flush-all-from-me) MAC |
| 863 |
flush action is required. The source (mine/me) is defined as |
| 864 |
the PW associated with either the LDP session on which the LDP |
| 865 |
MAC withdraw was received or the B-MAC(s) listed in the B-MAC |
| 866 |
Sub-TLV. For the optimized MAC flush procedure described in |
| 867 |
this section, the flag MUST be set (N = 1). |
| 868 |
|
| 869 |
Detailed usage in the context of PBB-VPLS is explained in |
| 870 |
<a href="#section-5.2">Section 5.2</a>. |
| 871 |
|
| 872 |
MBZ flags: The rest of the flags SHOULD be set to zero on |
| 873 |
transmission and ignored on reception. |
| 874 |
|
| 875 |
The MAC Flush TLV SHOULD be placed after the existing TLVs in the |
| 876 |
[<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] MAC flush message. |
| 877 |
|
| 878 |
<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. Application of the MAC Flush TLV in Optimized MAC Flushing</span> |
| 879 |
|
| 880 |
When optimized MAC flushing is supported, the MAC Flush TLV MUST be |
| 881 |
sent in an existing LDP address withdraw message with an empty MAC |
| 882 |
list but from the core PE-rs on detection of failure of its |
| 883 |
local/primary spoke PW. The N-bit in the TLV MUST be set to 1 to |
| 884 |
indicate flush-all-from-me. If the optimized MAC flush procedure is |
| 885 |
used in a Backbone VPLS or regular VPLS/H-VPLS context, the C-bit |
| 886 |
MUST be ZERO (C = 0). If it is used in an I-component context, the |
| 887 |
C-bit MUST be set (C = 1). See <a href="#section-5.2">Section 5.2</a> for details of its usage |
| 888 |
in the context of PBB-VPLS. |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 895 |
|
| 896 |
|
| 897 |
Note that the assumption is that the MAC Flush TLV is understood by |
| 898 |
all devices before it is turned on in any network. See <a href="#section-6">Section 6</a> |
| 899 |
("Operational Considerations"). |
| 900 |
|
| 901 |
When optimized MAC flushing is not supported, the MAC withdraw |
| 902 |
procedures defined in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>], where either the MTU-s or PE2-rs |
| 903 |
sends the MAC withdraw message, SHOULD be used. This includes the |
| 904 |
case where the network is being changed to support optimized MAC |
| 905 |
flushing but not all devices are capable of understanding optimized |
| 906 |
MAC flush messages. |
| 907 |
|
| 908 |
In the case of B-VPLS devices, the optimized MAC flush message SHOULD |
| 909 |
be supported. |
| 910 |
|
| 911 |
<span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a>. MAC Flush TLV Processing Rules for Regular VPLS</span> |
| 912 |
|
| 913 |
This section describes the processing rules of the MAC Flush TLV that |
| 914 |
MUST be followed in the context of optimized MAC flush procedures |
| 915 |
in VPLS. |
| 916 |
|
| 917 |
When optimized MAC flushing is supported, a multi-homing PE-rs |
| 918 |
initiates a MAC flush message towards the other related VPLS PE-rs |
| 919 |
devices when it detects a transition (failure or a change to standby) |
| 920 |
in its active spoke PW. In such a case the MAC Flush TLV MUST be |
| 921 |
sent with N = 1. A PE-rs device receiving the MAC Flush TLV SHOULD |
| 922 |
follow the same processing rules as those described in this section. |
| 923 |
|
| 924 |
Note that if a Multi-Segment Pseudowire (MS-PW) is used in VPLS, then |
| 925 |
a MAC flush message is processed only at the PW Terminating Provider |
| 926 |
Edge (T-PE) nodes, since PW Switching Provider Edge S-PE(s) traversed |
| 927 |
by the MS-PW propagates the MAC flush messages without any action. |
| 928 |
In this section, a PE-rs device signifies only a T-PE in the MS-PW |
| 929 |
case. |
| 930 |
|
| 931 |
When a PE-rs device receives a MAC Flush TLV with N = 1, it SHOULD |
| 932 |
flush all the MAC addresses learned from the PW in the VPLS in the |
| 933 |
context on which the MAC flush message is received. It is assumed |
| 934 |
that when these procedures are used all nodes support the MAC flush |
| 935 |
message. See <a href="#section-6">Section 6</a> ("Operational Considerations") for details. |
| 936 |
|
| 937 |
When optimized MAC flushing is not supported, a MAC Flush TLV is |
| 938 |
received with N = 0 in the MAC flush message; in such a case, the |
| 939 |
receiving PE-rs SHOULD flush the MAC addresses learned from all PWs |
| 940 |
in the VPLS instance, except the ones learned over the PW on which |
| 941 |
the message is received. |
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 951 |
|
| 952 |
|
| 953 |
Regardless of whether optimized MAC flushing is supported, if a PE-rs |
| 954 |
device receives a MAC flush message with a MAC Flush TLV option |
| 955 |
(N = 0 or N = 1) and a valid MAC address list, it SHOULD ignore the |
| 956 |
option and deal with MAC addresses explicitly as per [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. |
| 957 |
|
| 958 |
<span class="h4"><a class="selflink" id="section-5.1.4" href="#section-5.1.4">5.1.4</a>. Optimized MAC Flush Procedures</span> |
| 959 |
|
| 960 |
This section expands on the optimized MAC flush procedure in the |
| 961 |
scenario shown in Figure 2. |
| 962 |
|
| 963 |
When optimized MAC flushing is being used, a PE-rs that is dual- |
| 964 |
homing aware SHOULD send MAC address messages with a MAC Flush TLV |
| 965 |
and N = 1, provided the other PEs understand the new messages. Upon |
| 966 |
receipt of the MAC flush message, PE2-rs identifies the VPLS instance |
| 967 |
that requires MAC flushing from the FEC element in the FEC TLV. On |
| 968 |
receiving N = 1, PE2-rs removes all MAC addresses learned from that |
| 969 |
PW over which the message is received. The same action is performed |
| 970 |
by PE3-rs and PE4-rs. |
| 971 |
|
| 972 |
Figure 4 shows another redundant H-VPLS topology to protect against |
| 973 |
failure of the MTU-s device. In this case, since there is more than |
| 974 |
a single MTU-S, a protocol such as provider RSTP [<a href="#ref-IEEE.802.1Q-2011">IEEE.802.1Q-2011</a>] |
| 975 |
may be used as the selection algorithm for active and backup PWs in |
| 976 |
order to maintain the connectivity between MTU-s devices and PE-rs |
| 977 |
devices at the edge. It is assumed that PE-rs devices can detect |
| 978 |
failure on PWs in either direction through OAM mechanisms (for |
| 979 |
instance, Virtual Circuit Connectivity Verification (VCCV) |
| 980 |
procedures). |
| 981 |
|
| 982 |
MTU-1================PE1-rs==============PE3-rs |
| 983 |
|| || \ /|| |
| 984 |
|| Redundancy || \ / || |
| 985 |
|| Provider RSTP || Full Mesh . || |
| 986 |
|| || / \ || |
| 987 |
|| || / \|| |
| 988 |
MTU-2----------------PE2-rs==============PE4-rs |
| 989 |
Backup PW |
| 990 |
|
| 991 |
Figure 4: Redundancy with Provider RSTP |
| 992 |
|
| 993 |
MTU-1, MTU-2, PE1-rs, and PE2-rs participate in provider RSTP. |
| 994 |
Configuration using RSTP ensures that the PW between MTU-1 and PE1-rs |
| 995 |
is active and the PW between MTU-2 and PE2-rs is blocked (made |
| 996 |
backup) at the MTU-2 end. When the active PW failure is detected by |
| 997 |
RSTP, it activates the PW between MTU-2 and PE2-rs. When PE1-rs |
| 998 |
detects the failing PW to MTU-1, it MAY trigger MAC flushing into the |
| 999 |
full mesh with a MAC Flush TLV that carries N = 1. Other PE-rs |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
devices in the full mesh that receive the MAC flush message identify |
| 1010 |
their respective PWs terminating on PE1-rs and flush all the MAC |
| 1011 |
addresses learned from it. |
| 1012 |
|
| 1013 |
[<a id="ref-RFC4762">RFC4762</a>] describes a multi-domain VPLS service where fully meshed |
| 1014 |
VPLS networks (domains) are connected together by a single spoke PW |
| 1015 |
per VPLS service between the VPLS "border" PE-rs devices. To provide |
| 1016 |
redundancy against failure of the inter-domain spoke, full mesh of |
| 1017 |
inter-domain spokes can be set up between border PE-rs devices, and |
| 1018 |
provider RSTP may be used for selection of the active inter-domain |
| 1019 |
spoke. In the case of inter-domain spoke PW failure, MAC withdrawal |
| 1020 |
initiated by PE-rs MAY be used for optimized MAC flush procedures |
| 1021 |
within individual domains. |
| 1022 |
|
| 1023 |
Further, the procedures are applicable to any native Ethernet access |
| 1024 |
topologies multi-homed to two or more VPLS PE-rs devices. The text |
| 1025 |
in this section applies for the native Ethernet case where |
| 1026 |
active/standby PWs are replaced with the active/standby Ethernet |
| 1027 |
endpoints. An optimized MAC flush message can be generated by the |
| 1028 |
VPLS PE-rs that detects the failure in the primary Ethernet access. |
| 1029 |
|
| 1030 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. LDP MAC Flush Extensions for PBB-VPLS</span> |
| 1031 |
|
| 1032 |
The use of an address withdraw message with a MAC List TLV is |
| 1033 |
proposed in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] as a way to expedite removal of MAC addresses |
| 1034 |
as the result of a topology change (e.g., failure of a primary link |
| 1035 |
of a VPLS PE-rs device and, implicitly, the activation of an |
| 1036 |
alternate link in a dual-homing use case). These existing procedures |
| 1037 |
apply individually to B-VPLS and I-component domains. |
| 1038 |
|
| 1039 |
When it comes to reflecting topology changes in access networks |
| 1040 |
connected to I-components across the B-VPLS domain, certain additions |
| 1041 |
should be considered, as described below. |
| 1042 |
|
| 1043 |
MAC switching in PBB is based on the mapping of Customer MACs |
| 1044 |
(C-MACs) to one or more Backbone MACs (B-MACs). A topology change in |
| 1045 |
the access (I-component domain) should just invoke the flushing of |
| 1046 |
C-MAC entries in the PBB PEs' FIB(s) associated with the |
| 1047 |
I-component(s) impacted by the failure. There is a need to indicate |
| 1048 |
the PBB PE (B-MAC source) that originated the MAC flush message to |
| 1049 |
selectively flush only the MACs that are affected. |
| 1050 |
|
| 1051 |
These goals can be achieved by including the MAC Flush Parameters TLV |
| 1052 |
in the LDP address withdraw message to indicate the particular |
| 1053 |
domain(s) requiring MAC flushing. On the other end, the receiving |
| 1054 |
PEs SHOULD use the information from the new TLV to flush only the |
| 1055 |
related FIB entry/entries in the I-component instance(s). |
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
At least one of the following sub-TLVs MUST be included in the MAC |
| 1066 |
Flush Parameters TLV if the C-flag is set to 1: |
| 1067 |
|
| 1068 |
o PBB B-MAC List Sub-TLV: |
| 1069 |
|
| 1070 |
Type: 0x0407 |
| 1071 |
|
| 1072 |
Length: Value length in octets. At least one B-MAC address MUST |
| 1073 |
be present in the list. |
| 1074 |
|
| 1075 |
Value: One or a list of 48-bit B-MAC addresses. These are the |
| 1076 |
source B-MAC addresses associated with the B-VPLS instance that |
| 1077 |
originated the MAC withdraw message. It will be used to identify |
| 1078 |
the C-MAC(s) mapped to the B-MAC(s) listed in the sub-TLV. |
| 1079 |
|
| 1080 |
o PBB I-SID List Sub-TLV: |
| 1081 |
|
| 1082 |
Type: 0x0408 |
| 1083 |
|
| 1084 |
Length: Value length in octets. Zero indicates an empty I-SID |
| 1085 |
list. An empty I-SID list means that the flushing applies to all |
| 1086 |
the I-SIDs mapped to the B-VPLS indicated by the FEC TLV. |
| 1087 |
|
| 1088 |
Value: One or a list of 24-bit I-SIDs that represent the |
| 1089 |
I-component FIB(s) where the MAC flushing needs to take place. |
| 1090 |
|
| 1091 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. MAC Flush TLV Processing Rules for PBB-VPLS</span> |
| 1092 |
|
| 1093 |
The following steps describe the details of the processing rules for |
| 1094 |
the MAC Flush TLV in the context of PBB-VPLS. In general, these |
| 1095 |
procedures are similar to the VPLS case but are tailored to PBB, |
| 1096 |
which may have a large number of MAC addresses. In PBB, there are |
| 1097 |
two sets of MAC addresses: Backbone (outer) MACs (B-MACs) and |
| 1098 |
Customer (inner) MACs (C-MACs). C-MACs are associated to remote |
| 1099 |
B-MACs by learning. There are also I-SIDs in PBB; I-SIDs are similar |
| 1100 |
to VLANs for the purposes of the discussion in this section. In |
| 1101 |
order to achieve behavior that is similar to the Regular VPLS case, |
| 1102 |
there are some differences in the interpretation of the optimized MAC |
| 1103 |
flush message. |
| 1104 |
|
| 1105 |
1. Positive flush of C-MACs. This is equivalent to [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] MAC |
| 1106 |
flushing in a PBB context. In this case, the N-bit is set to 0; |
| 1107 |
the C-bit is set to 1, and C-MACs are to be flushed. However, |
| 1108 |
since C-MACs are related to B-MACs in an I-SID context, further |
| 1109 |
refinement of the flushing scope is possible. |
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
- If an I-SID needs to be flushed (all C-MACs within that I-SID), |
| 1122 |
then I-SIDs are listed in the appropriate TLV. If all I-SIDs |
| 1123 |
are to have the C-MACs flushed, then the I-SID TLV can be empty. |
| 1124 |
It is typical to flush a single I-SID only, since each I-SID is |
| 1125 |
associated with one or more interfaces (typically one, in the |
| 1126 |
case of dual-homing). In the PBB case, flushing the I-SID is |
| 1127 |
equivalent to the empty MAC list discussed in [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. |
| 1128 |
|
| 1129 |
- If only a set of B-MAC-to-C-MAC associations needs to be |
| 1130 |
flushed, then a B-MAC list can be included to further refine the |
| 1131 |
list. This can be the case if an I-SID component has more than |
| 1132 |
one interface and a B-MAC is used to refine the granularity. |
| 1133 |
Since this is a positive MAC flush message, the intended |
| 1134 |
behavior is to flush all C-MACs except those that are associated |
| 1135 |
with B-MACs in the list. |
| 1136 |
|
| 1137 |
Positive flush of B-MACs is also useful for propagating flush |
| 1138 |
from other protocols such as RSTP. |
| 1139 |
|
| 1140 |
2. Negative flush of C-MACs. This is equivalent to optimized MAC |
| 1141 |
flushing. In this case, the N-bit is set to 1; the C-bit is set |
| 1142 |
to 1, and a list of B-MACs is provided so that the respective |
| 1143 |
C-MACs can be flushed. |
| 1144 |
|
| 1145 |
- The I-SID list SHOULD be specified. If it is absent, then all |
| 1146 |
I-SIDs require that the C-MACs be flushed. |
| 1147 |
|
| 1148 |
- A set of B-MACs SHOULD be listed, since B-MAC-to-C-MAC |
| 1149 |
associations need to be flushed and listing B-MACs scopes the |
| 1150 |
flush to just those B-MACs. Again, this is typical usage, |
| 1151 |
because a PBB VPLS I-component interface will have one |
| 1152 |
associated I-SID and typically one (but possibly more than one) |
| 1153 |
B-MAC, each with multiple remotely learned C-MACs. The B-MAC |
| 1154 |
list is included to further refine the list for the remote |
| 1155 |
receiver. Since this is a negative MAC flush message, the |
| 1156 |
intended behavior is to flush all remote C-MACs that are |
| 1157 |
associated with any B-MACs in the list (in other words, from the |
| 1158 |
affected interface). |
| 1159 |
|
| 1160 |
The processing rules on reception of the MAC flush message are: |
| 1161 |
|
| 1162 |
- On Backbone Core Bridges (BCBs), if the C-bit is set to 1, then the |
| 1163 |
PBB-VPLS SHOULD NOT flush their B-MAC FIBs. The B-VPLS control |
| 1164 |
plane SHOULD propagate the MAC flush message following the data- |
| 1165 |
plane split-horizon rules to the established B-VPLS topology. |
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
- On Backbone Edge Bridges (BEBs), the following actions apply: |
| 1178 |
|
| 1179 |
- The PBB I-SID list is used to determine the particular I-SID |
| 1180 |
FIBs (I-component) that need to be considered for flushing |
| 1181 |
action. If the PBB I-SID List Sub-TLV is not included in a |
| 1182 |
received message, then all the I-SID FIBs associated with the |
| 1183 |
receiving B-VPLS SHOULD be considered for flushing action. |
| 1184 |
|
| 1185 |
- The PBB B-MAC list is used to identify from the I-SID FIBs in |
| 1186 |
the previous step to selectively flush B-MAC-to-C-MAC |
| 1187 |
associations, depending on the N-flag specified below. If the |
| 1188 |
PBB B-MAC List Sub-TLV is not included in a received message, |
| 1189 |
then all B-MAC-to-C-MAC associations in all I-SID FIBs |
| 1190 |
(I-component) as specified by the I-SID List are considered for |
| 1191 |
required flushing action, again depending on the N-flag |
| 1192 |
specified below. |
| 1193 |
|
| 1194 |
- Next, depending on the N-flag value, the following actions |
| 1195 |
apply: |
| 1196 |
|
| 1197 |
- N = 0: all the C-MACs in the selected I-SID FIBs SHOULD be |
| 1198 |
flushed, with the exception of the resultant C-MAC list from |
| 1199 |
the B-MAC list mentioned in the message ("flush all but the |
| 1200 |
C-MACs associated with the B-MAC(s) in the B-MAC List Sub-TLV |
| 1201 |
from the FIBs associated with the I-SID list"). |
| 1202 |
|
| 1203 |
- N = 1: all the resultant C-MACs SHOULD be flushed ("flush all |
| 1204 |
the C-MACs associated with the B-MAC(s) in the B-MAC List |
| 1205 |
Sub-TLV from the FIBs associated with the I-SID list"). |
| 1206 |
|
| 1207 |
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Applicability of the MAC Flush Parameters TLV</span> |
| 1208 |
|
| 1209 |
If the MAC Flush Parameters TLV is received by a Backbone Edge Bridge |
| 1210 |
(BEB) in a PBB-VPLS that does not understand the TLV, then an |
| 1211 |
undesirable MAC flushing action may result. It is RECOMMENDED that |
| 1212 |
all PE-rs devices participating in PBB-VPLS support the MAC Flush |
| 1213 |
Parameters TLV. If this is not possible, the MAC Flush Parameters |
| 1214 |
TLV SHOULD be disabled, as mentioned in <a href="#section-6">Section 6</a> ("Operational |
| 1215 |
Considerations"). |
| 1216 |
|
| 1217 |
"Mac Flush TLV" and its formal name -- "MAC Flush Parameters TLV" -- |
| 1218 |
are synonymous. The MAC Flush TLV is applicable to the regular VPLS |
| 1219 |
context as well, as explained in <a href="#section-3.1.1">Section 3.1.1</a>. To achieve negative |
| 1220 |
MAC flushing (flush-all-from-me) in a regular VPLS context, the MAC |
| 1221 |
Flush Parameters TLV SHOULD be encoded with C = 0 and N = 1 without |
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
inclusion of any Sub-TLVs. A negative MAC flush message is highly |
| 1234 |
desirable in scenarios where VPLS access redundancy is provided by |
| 1235 |
Ethernet ring protection as specified in the ITU-T G.8032 [<a href="#ref-ITU.G8032" title=""Ethernet ring protection switching"">ITU.G8032</a>] |
| 1236 |
specification. |
| 1237 |
|
| 1238 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Operational Considerations</span> |
| 1239 |
|
| 1240 |
As mentioned earlier, if the MAC Flush Parameters TLV is not |
| 1241 |
understood by a receiver, then an undesirable MAC flushing action |
| 1242 |
would result. To avoid this, one possible solution is to develop an |
| 1243 |
LDP-based capability negotiation mechanism to negotiate support of |
| 1244 |
various MAC flushing capabilities between PE-rs devices in a VPLS |
| 1245 |
instance. A negotiation mechanism was discussed previously and was |
| 1246 |
considered outside the scope of this document. Negotiation is not |
| 1247 |
required to deploy this optimized MAC flushing as described in this |
| 1248 |
document. |
| 1249 |
|
| 1250 |
VPLS may be used with or without the optimization. If an operator |
| 1251 |
wants the optimization for VPLS, it is the operator's responsibility |
| 1252 |
to make sure that the VPLS devices that are capable of supporting the |
| 1253 |
optimization are properly configured. From an operational |
| 1254 |
standpoint, it is RECOMMENDED that implementations of the solution |
| 1255 |
provide administrative control to select the desired MAC flushing |
| 1256 |
action towards a PE-rs device in the VPLS. Thus, in the topology |
| 1257 |
described in Figure 2, an implementation could support PE1-rs, |
| 1258 |
sending optimized MAC flush messages towards the PE-rs devices that |
| 1259 |
support the solution and the PE2-rs device initiating the [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] |
| 1260 |
style of MAC flush messages towards the PE-rs devices that do not |
| 1261 |
support the optimized solution during upgrades. The PE-rs that |
| 1262 |
supports the MAC Flush Parameters TLV MUST support the <a href="./rfc4762">RFC 4762</a> MAC |
| 1263 |
flushing procedures, since this document only augments them. |
| 1264 |
|
| 1265 |
In the case of PBB-VPLS, this operation is the only method supported |
| 1266 |
for specifying I-SIDs, and the optimization is assumed to be |
| 1267 |
supported or should be turned off, reverting to flushing using |
| 1268 |
[<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>] at the Backbone MAC level. |
| 1269 |
|
| 1270 |
|
| 1271 |
|
| 1272 |
|
| 1273 |
|
| 1274 |
|
| 1275 |
|
| 1276 |
|
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 1290 |
|
| 1291 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. New LDP TLV</span> |
| 1292 |
|
| 1293 |
IANA maintains a registry called "Label Distribution Protocol (LDP) |
| 1294 |
Parameters" with a sub-registry called "TLV Type Name Space". |
| 1295 |
|
| 1296 |
IANA has allocated three new code points as follows: |
| 1297 |
|
| 1298 |
Value | Description | Reference | Notes |
| 1299 |
-------+---------------------------+------------+----------- |
| 1300 |
0x0406 | MAC Flush Parameters TLV | [<a href="./rfc7361">RFC7361</a>] | |
| 1301 |
0x0407 | PBB B-MAC List Sub-TLV | [<a href="./rfc7361">RFC7361</a>] | |
| 1302 |
0x0408 | PBB I-SID List Sub-TLV | [<a href="./rfc7361">RFC7361</a>] | |
| 1303 |
|
| 1304 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. New Registry for MAC Flush Flags</span> |
| 1305 |
|
| 1306 |
IANA has created a new sub-registry under "Label Distribution |
| 1307 |
Protocol (LDP) Parameters" called "MAC Flush Flags". |
| 1308 |
|
| 1309 |
IANA has populated the registry as follows: |
| 1310 |
|
| 1311 |
Bit Number | Hex | Abbreviation | Description | Reference |
| 1312 |
-----------+------+--------------+-----------------------+----------- |
| 1313 |
0 | 0x80 | C | Context | [<a href="./rfc7361">RFC7361</a>] |
| 1314 |
1 | 0x40 | N | Negative MAC flushing | [<a href="./rfc7361">RFC7361</a>] |
| 1315 |
2-7 | | | Unassigned | |
| 1316 |
|
| 1317 |
Other new bits are to be assigned by Standards Action [<a href="./rfc5226" title="">RFC5226</a>]. |
| 1318 |
|
| 1319 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 1320 |
|
| 1321 |
Control-plane aspects: |
| 1322 |
|
| 1323 |
LDP security (authentication) methods as described in [<a href="./rfc5036" title=""LDP Specification"">RFC5036</a>] |
| 1324 |
are applicable here. Further, this document implements security |
| 1325 |
considerations as discussed in [<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>] and [<a href="./rfc4762" title=""Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"">RFC4762</a>]. The |
| 1326 |
extensions defined here optimize the MAC flushing action, and so |
| 1327 |
the risk of security attacks is reduced. However, in the event |
| 1328 |
that the configuration of support for the new TLV can be spoofed, |
| 1329 |
sub-optimal behavior will be seen. |
| 1330 |
|
| 1331 |
Data-plane aspects: |
| 1332 |
|
| 1333 |
This specification does not have any impact on the VPLS forwarding |
| 1334 |
plane but can improve MAC flushing behavior. |
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Contributing Author</span> |
| 1346 |
|
| 1347 |
The authors would like to thank Marc Lasserre, who made a major |
| 1348 |
contribution to the development of this document. |
| 1349 |
|
| 1350 |
Marc Lasserre |
| 1351 |
Alcatel-Lucent |
| 1352 |
EMail: [email protected] |
| 1353 |
|
| 1354 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span> |
| 1355 |
|
| 1356 |
The authors would like to thank the following people who have |
| 1357 |
provided valuable comments, feedback, and review on the topics |
| 1358 |
discussed in this document: Dimitri Papadimitriou, Jorge Rabadan, |
| 1359 |
Prashanth Ishwar, Vipin Jain, John Rigby, Ali Sajassi, Wim |
| 1360 |
Henderickx, Paul Kwok, Maarten Vissers, Daniel Cohn, Nabil Bitar, |
| 1361 |
Giles Heron, Adrian Farrel, Ben Niven-Jenkins, Robert Sparks, Susan |
| 1362 |
Hares, and Stephen Farrell. |
| 1363 |
|
| 1364 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span> |
| 1365 |
|
| 1366 |
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span> |
| 1367 |
|
| 1368 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1369 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1370 |
|
| 1371 |
[<a id="ref-RFC4447">RFC4447</a>] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and |
| 1372 |
G. Heron, "Pseudowire Setup and Maintenance Using the |
| 1373 |
Label Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April 2006. |
| 1374 |
|
| 1375 |
[<a id="ref-RFC4762">RFC4762</a>] Lasserre, M., Ed., and V. Kompella, Ed., "Virtual Private |
| 1376 |
LAN Service (VPLS) Using Label Distribution Protocol |
| 1377 |
(LDP) Signaling", <a href="./rfc4762">RFC 4762</a>, January 2007. |
| 1378 |
|
| 1379 |
[<a id="ref-RFC5036">RFC5036</a>] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., |
| 1380 |
"LDP Specification", <a href="./rfc5036">RFC 5036</a>, October 2007. |
| 1381 |
|
| 1382 |
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span> |
| 1383 |
|
| 1384 |
[<a id="ref-IEEE.802.1Q-2011">IEEE.802.1Q-2011</a>] |
| 1385 |
IEEE, "IEEE Standard for Local and metropolitan area |
| 1386 |
networks -- Media Access Control (MAC) Bridges and |
| 1387 |
Virtual Bridged Local Area Networks", IEEE Std 802.1Q, |
| 1388 |
2011. |
| 1389 |
|
| 1390 |
[<a id="ref-ITU.G8032">ITU.G8032</a>] International Telecommunication Union, "Ethernet ring |
| 1391 |
protection switching", ITU-T Recommendation G.8032, |
| 1392 |
February 2012. |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
[<a id="ref-RFC4664">RFC4664</a>] Andersson, L., Ed., and E. Rosen, Ed., "Framework for |
| 1402 |
Layer 2 Virtual Private Networks (L2VPNs)", <a href="./rfc4664">RFC 4664</a>, |
| 1403 |
September 2006. |
| 1404 |
|
| 1405 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 1406 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 1407 |
May 2008. |
| 1408 |
|
| 1409 |
[<a id="ref-RFC6073">RFC6073</a>] Martini, L., Metz, C., Nadeau, T., Bocci, M., and M. |
| 1410 |
Aissaoui, "Segmented Pseudowire", <a href="./rfc6073">RFC 6073</a>, January 2011. |
| 1411 |
|
| 1412 |
[<a id="ref-RFC6718">RFC6718</a>] Muley, P., Aissaoui, M., and M. Bocci, "Pseudowire |
| 1413 |
Redundancy", <a href="./rfc6718">RFC 6718</a>, August 2012. |
| 1414 |
|
| 1415 |
[<a id="ref-RFC7041">RFC7041</a>] Balus, F., Ed., Sajassi, A., Ed., and N. Bitar, Ed., |
| 1416 |
"Extensions to the Virtual Private LAN Service (VPLS) |
| 1417 |
Provider Edge (PE) Model for Provider Backbone Bridging", |
| 1418 |
<a href="./rfc7041">RFC 7041</a>, November 2013. |
| 1419 |
|
| 1420 |
[<a id="ref-VPLS-MH">VPLS-MH</a>] Kothari, B., Kompella, K., Henderickx, W., Balus, F., |
| 1421 |
Uttaro, J., Palislamovic, S., and W. Lin, "BGP based |
| 1422 |
Multi-homing in Virtual Private LAN Service", Work in |
| 1423 |
Progress, July 2014. |
| 1424 |
|
| 1425 |
|
| 1426 |
|
| 1427 |
|
| 1428 |
|
| 1429 |
|
| 1430 |
|
| 1431 |
|
| 1432 |
|
| 1433 |
|
| 1434 |
|
| 1435 |
|
| 1436 |
|
| 1437 |
|
| 1438 |
|
| 1439 |
|
| 1440 |
|
| 1441 |
|
| 1442 |
|
| 1443 |
|
| 1444 |
|
| 1445 |
|
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Dutta, 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="./rfc7361">RFC 7361</a> Optimized MAC Withdrawal in H-VPLS September 2014</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
Authors' Addresses |
| 1458 |
|
| 1459 |
Pranjal Kumar Dutta |
| 1460 |
Alcatel-Lucent |
| 1461 |
701 E Middlefield Road |
| 1462 |
Mountain View, CA 94043 |
| 1463 |
USA |
| 1464 |
|
| 1465 |
EMail: [email protected] |
| 1466 |
|
| 1467 |
|
| 1468 |
Florin Balus |
| 1469 |
Alcatel-Lucent |
| 1470 |
701 E Middlefield Road |
| 1471 |
Mountain View, CA 94043 |
| 1472 |
USA |
| 1473 |
|
| 1474 |
EMail: [email protected] |
| 1475 |
|
| 1476 |
|
| 1477 |
Olen Stokes |
| 1478 |
Extreme Networks |
| 1479 |
2121 RDU Center Drive |
| 1480 |
Suite 300 |
| 1481 |
Morrisville, NC 27650 |
| 1482 |
USA |
| 1483 |
|
| 1484 |
EMail: [email protected] |
| 1485 |
|
| 1486 |
|
| 1487 |
Geraldine Calvignac |
| 1488 |
Orange |
| 1489 |
2, avenue Pierre-Marzin |
| 1490 |
Lannion Cedex, 22307 |
| 1491 |
France |
| 1492 |
|
| 1493 |
EMail: [email protected] |
| 1494 |
|
| 1495 |
|
| 1496 |
Don Fedyk |
| 1497 |
Hewlett-Packard Company |
| 1498 |
USA |
| 1499 |
|
| 1500 |
EMail: [email protected] |
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
Dutta, et al. Standards Track [Page 27] |
| 1509 |
</pre> |