idnits 2.17.1 draft-ietf-trill-transport-over-mpls-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 3, 2017) is 2519 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Mohammed Umair 3 Intended Status: Informational Kingston Smiler Selvaraj 4 IPInfusion 5 Donald Eastlake 3rd 6 Lucy Yong 7 Huawei Technologies 8 Expires: December 5, 2017 June 3, 2017 10 TRILL Transparent Transport over MPLS 11 13 Abstract 15 This document specifies how to interconnect multiple Transparent 16 Interconnection of Lots of links (TRILL) sites with an intervening 17 MPLS network using existing TRILL and VPLS standards. This draft 18 addresses two problems as follows: 20 1) Providing connection between more than two TRILL sites that 21 are separated by an MPLS provider network. 23 2) Providing a single logical virtualized TRILL network for 24 different tenants that are separated by an MPLS provider network. 26 Status of this Memo 28 This document is not an Internet Standards Track specification; it is 29 published for informational purposes. 31 This Internet-Draft is submitted to IETF in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF), its areas, and its working groups. Note that 36 other groups may also distribute working documents as 37 Internet-Drafts. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 43 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/1id-abstracts.html 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html 49 Copyright and License Notice 51 Copyright (c) 2017 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. TRILL Over MPLS Model . . . . . . . . . . . . . . . . . . . . . 5 69 3. VPLS Model . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 3.1. Entities in the VPLS Model . . . . . . . . . . . . . . . . 7 71 3.3. TRILL Adjacency for VPLS model . . . . . . . . . . . . . . 8 72 3.4. MPLS encapsulation for VPLS model . . . . . . . . . . . . . 8 73 3.5. Loop Free provider PSN/MPLS. . . . . . . . . . . . . . . . 8 74 3.6. Frame processing. . . . . . . . . . . . . . . . . . . . . . 8 75 4. VPTS Model . . . . . . . . . . . . . . . . . . . . . . . . . . 8 76 4.1. Entities in the VPTS Model . . . . . . . . . . . . . . . . 10 77 4.1.1. TRILL Intermediate Routers (TIR) . . . . . . . . . . . 11 78 4.1.2. Virtual TRILL Switch/Service Domain (VTSD) . . . . . . 11 79 4.2. TRILL Adjacency for VPTS model . . . . . . . . . . . . . . 11 80 4.3. MPLS encapsulation for VPTS model . . . . . . . . . . . . . 12 81 4.4. Loop Free provider PSN/MPLS. . . . . . . . . . . . . . . . 12 82 4.5. Frame processing. . . . . . . . . . . . . . . . . . . . . . 12 83 4.5.1. Multi-Destination Frame processing . . . . . . . . . . 12 84 4.5.2. Unicast Frame processing . . . . . . . . . . . . . . . 12 85 5. Extensions to TRILL Over Pseudowires [RFC7173] . . . . . . . . 12 86 6. VPTS Model Versus VPLS Model . . . . . . . . . . . . . . . . . 13 87 7. Packet processing between pseudowires . . . . . . . . . . . . . 13 88 8. Efficiency Considerations . . . . . . . . . . . . . . . . . . . 14 89 9. Security Considerations . . . . . . . . . . . . . . . . . . . . 15 90 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 91 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 92 11.1. Normative References . . . . . . . . . . . . . . . . . . . 15 93 11.2. Informative References . . . . . . . . . . . . . . . . . . 16 94 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 16 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 97 1. Introduction 99 The IETF Transparent Interconnection of Lots of Links (TRILL) 100 protocol [RFC6325] [RFC7177] [RFC7780] provides transparent 101 forwarding in multi-hop networks with arbitrary topology and link 102 technologies using a header with a hop count and link-state routing. 103 TRILL provides optimal pair-wise forwarding without configuration, 104 safe forwarding even during periods of temporary loops, and support 105 for multipathing of both unicast and multicast traffic. Intermediate 106 Systems (ISs) implementing TRILL are called Routing Bridges 107 (RBridges) or TRILL Switches 109 This draft, in conjunction with [RFC7173] on TRILL Transport using 110 Pseudowires, addresses two problems: 112 1) Providing connection between more than two TRILL sites belongs to 113 a single TRILL network that are separated by an MPLS provider network 114 using [RFC7173]. (Herein also called problem statement 1.) 116 2) Providing a single logical virtualized TRILL network for different 117 tenants that are separated by an MPLS provider network. In short 118 providing connection between TRILL sites belonging to a 119 tenant/tenants over a MPLS provider network. (Herein also called 120 problem statement 2.) 122 A tenant is the administrative entity on whose behalf their 123 associated services are managed. Here tenant refers to a TRILL campus 124 that is segregated from other tenants for security reasons. 126 A key multi-tenancy requirement is traffic isolation so that one 127 tenant's traffic is not visible to any other tenant. This draft also 128 addresses the problem of multi-tenancy by isolating one tenant's 129 traffic from the other. 131 1.1. Terminology 133 Acronyms used in this document include the following: 135 AC - Attachment Circuit [RFC4664] 137 Data Label - VLAN or FGL 139 ECMP - Equal Cost Multi Path 141 FGL - Fine-Grained Labeling [RFC7172] 143 IS-IS - Intermediate System to Intermediate 144 System [IS-IS] 146 LDP - Label Distribution Protocol 148 LAN - Local Area Network 150 MPLS - Multi-Protocol Label Switching 152 PBB - Provider Backbone Bridging 154 PE - Provider Edge Device 156 PSN - Packet Switched Network 158 PW - Pseudowire [RFC4664] 160 TIR - TRILL Intermediate Router 161 (Devices that has both IP/MPLS and TRILL 162 functionality) 164 TRILL - Transparent Interconnection of Lots of 165 Links OR Tunneled Routing in the Link Layer 167 TRILL Site - A part of a TRILL campus that contains at 168 least one RBridge. 170 VLAN - Virtual Local Area Network 172 VPLS - Virtual Private LAN Service 174 VPTS - Virtual Private TRILL Service 176 VSI - Virtual Service Instance [RFC4664] 178 VTSD - Virtual TRILL Switch Domain 179 OR Virtual TRILL Service Domain 180 A Virtual RBridge that segregates one 181 tenant's TRILL database as well as 182 traffic from the other. 184 WAN - Wide Area Network 186 2. TRILL Over MPLS Model 188 TRILL Over MPLS can be achieved in two different ways. 190 a) VPLS Model for TRILL 191 b) VPTS Model/TIR Model 193 Both these models can be used to solve the problem statement 1 and 2. 194 Herein the VPLS Model for TRILL is also called Model 1 and the VPTS 195 Model/TIR Model is also called Model 2. 197 3. VPLS Model 199 Figure 1 shows the topological model of TRILL over MPLS using VPLS 200 model. The PE routers in the below topology model should support all 201 the functional Components mentioned in [RFC4664]. 203 +-----+ +-----+ 204 | RBa +---+ ........................... +---| RBb | 205 +-----+ | . . | +-----+ 206 Site 1 | +----+ +----+ | Site 2 207 +----|PE1 | |PE2 |----+ 208 +----+ MPLS Cloud +----+ 209 . . 210 . +----+ . 211 ..........|PE3 |........... 212 +----+ ^ 213 | | 214 | +-- Emulated LAN 215 +-----+ 216 | RBc | 217 +-----+ 218 Site 3 220 Figure 1: Topological Model of TRILL over MPLS 221 connecting three TRILL Sites 223 Figure 2 below shows the topological model of TRILL over MPLS to 224 connect multiple TRILL sites belonging to a tenant (tenant here is a 225 TRILL campus, not a specific Data label). VSI1 and VSI2 are two Virtual 226 Service Instances that segregate Tenant1's traffic from other tenant 227 traffic. VSI1 will maintain its own database for Tenant1, similarly 228 VSI2 will maintain its own database for Tenant2. 230 +-----+ ............................ +-----+ 231 |RBat1+---+ . ++++++++++++++++++++++++ . +---|RBbt1| 232 +-----+ | . + + . | +-----+ 233 Tenant1 Site 1 | +----+ +----+ | Tenant1 Site2 234 +----|VSI1| |VSI1|----+ 235 +----|VSI2| MPLS Cloud |VSI2|----+ 236 | +----+ +----+ | 237 +-----+ | . + + . | +-----+ 238 |RBat2+---+ . +++++++++ +----+ ++++++++ . +---|RBbt2| 239 +-----+ ............|VSI1|........... +-----+ 240 Tenant2 Site 2 |VSI2| ^ Tenant2 Site2 241 +----+ | 242 | | 243 +-----+ +-----Emulated 244 |RBct2| LAN 245 +-----+ 246 Tenant2 Site 3 248 .... VSI1 Path 249 ++++ VSI2 Path 251 Figure 2: Topological Model for VPLS Model 252 connecting 2 Tenants with 3 sites each 254 In this model, TRILL sites are connected to VPLS-capable PE devices that 255 provide a logical interconnect, such that TRILL RBridges belonging to a 256 specific tenant connected via an single bridged Ethernet. These devices 257 are the same as PE devices specified in [RFC4026]. The Attachment 258 Circuit ports of PE Routers are layer 2 switch ports that are connected 259 to the RBridges at a TRILL site. Here each VPLS instance looks like an 260 emulated LAN. This model is similar to connecting different RBridges 261 (TRILL sites) by a layer 2 bridge domain (multi access link) as 262 specified in [RFC6325]. This model doesn't requires any changes in PE 263 routers to carry TRILL packets, as TRILL packets will be transferred 264 transparently. 266 3.1. Entities in the VPLS Model 268 The PE (VPLS-PE) and CE devices are defined in [RFC4026]. 270 The Generic L2VPN Transport Functional Components like Attachment 271 Circuits, Pseudowires, VSI etc. are defined in [RFC4664]. 273 The RB (RBridge) and TRILL Sites are defined in [RFC6325] as updated by 274 [RFC7780]. 276 3.3. TRILL Adjacency for VPLS model 278 As specified in section 3 of this document, the MPLS cloud looks like an 279 emulated LAN (also called multi-access link or broadcast link). This 280 results in RBridges at different sites looking like they are connected 281 by a multi-access link. With such interconnection, the TRILL adjacency 282 over the link are automatically discovered and established through TRILL 283 IS-IS control messages [RFC7177]. These IS-IS control messages are 284 transparently forwarded by the VPLS domain, after doing MPLS 285 encapsulation specified in the section 3.4. 287 3.4. MPLS encapsulation for VPLS model 289 Use of VPLS [RFC4762] [RFC4761] to interconnect TRILL sites requires no 290 changes to a VPLS implementation, in particular the use of Ethernet 291 pseudowires between VPLS PEs. A VPLS PE receives normal Ethernet frames 292 from an RBridge (i.e., CE) and is not aware that the CE is an RBridge 293 device. As an example, an MPLS-encapsulated TRILL packet within the MPLS 294 network can use the format illustrated in Appendix A of [RFC7173] for 295 the non-PBB case. For the PBB case, additional header fields illustrated 296 in [RFC7041] can be added by entry PE and removed by the exit PE. 298 3.5. Loop Free provider PSN/MPLS. 300 No explicit handling is required to avoid loop free topology. Split 301 Horizon technique specified in [RFC4664] will take care of avoiding 302 loops in the provider PSN network. 304 3.6. Frame processing. 306 The PE devices transparently process the TRILL control and data frames. 307 Procedures to forward the frames are defined in [RFC4664] 309 4. VPTS Model 311 The (Virtual Private TRILL Service) VPTS is a L2 TRILL service, that 312 emulates TRILL service across a Wide Area Network (WAN). VPTS is similar 313 to what VPLS does for bridge core but provides a TRILL core. VPLS 314 provides "Virtual Private LAN Service" for different customers. VPTS 315 provides "Virtual Private TRILL Service" for different TRILL tenants. 317 Figure 3 shows the topological model of TRILL over MPLS using VPTS. In 318 this model the PE routers are replaced with TIR (TRILL Intermediate 319 Router) and VSI is replaced with VTSD (Virtual TRILL Switch Domain). The 320 TIR devices must be capable of supporting both MPLS and TRILL as 321 specified in section 4.1.1. The TIR devices are interconnected via PWs 322 and appear as a unified emulated TRILL campus with each VTSD inside a 323 TIR equivalent to a RBridge. 325 Some of the reasons for interconnecting TRILL Sites without isolating 326 the TRILL Control plane of one TRILL site from other sites are as 327 described below. 329 1) Nickname Uniqueness: One of the basic requirements of TRILL is that, 330 RBridge Nicknames are unique within the campus [RFC6325]. If we 331 segregate control plane of one TRILL site from other TRILL site and 332 provide interconnection between these sites, it may result in Nickname 333 collision. 335 2) Distribution Tree and its pruning: When a TRILL Data packet 336 traverses a Distribution Tree, it will stay on it even in other TRILL 337 site. If no end-station service is enabled for a particular Data Label 338 in a TRILL site, the Distribution Tree may be pruned and TRILL data 339 packets of that particular Data Label might never get to other TRILL 340 sites. The TRILL RPF check will always be performed on the packets that 341 are received by TIRs through pseudowires. 343 3) Hop Count values: When a TRILL data packet is received over a 344 pseudowire by a TIR, the TIR does the processing of Hop Count defined in 345 [RFC6325] and will not perform any resetting of Hop Count. 347 +-----+ +-----+ 348 | RBa +---+ ........................... +---| RBb | 349 +-----+ | . . | +-----+ 350 Site 1 | +----+ +----+ | Site 2 351 +----|TIR1| |TIR2|----+ 352 +----+ MPLS Cloud +----+ 353 . . 354 . +----+ . 355 ..........|TIR3|........... 356 +----+ ^ 357 | | 358 | +-- Emulated TRILL 359 +-----+ 360 | RBc | 361 +-----+ 362 Site 3 364 Figure 3: Topological Model of VPTS/TIR 365 connecting three TRILL Sites 367 In the above figure (Figure 3) Site1, Site2 and Site3 (running the 368 TRILL protocol) are connected to TIR Devices. These TIR devices, along 369 with the MPLS cloud, look like an unified emulated TRILL network. Only 370 the PE devices in the MPLS network should be replaced with TIRs so the 371 intermediate Provider routers are agnostic to the TRILL protocol. 373 Figure 4 below extends the topological model of TRILL over MPLS to 374 connect multiple TRILL sites belonging to a tenant (tenant here is a 375 campus, not a Data label) using VPTS model. VTSD1 and VTSD2 are two 376 Virtual TRILL Switch Domains (Virtual RBridges) that segregate 377 Tenant1's traffic from Tenant2's traffic. VTSD1 will maintain its own 378 TRILL database for Tenant1, similarly VTSD2 will maintain its own TRILL 379 database for Tenant2. 381 +-----+ ............................ +-----+ 382 |RBat1+---+ . ######################## . +---|RBbt1| 383 +-----+ | . # # . | +-----+ 384 Tenant1 Site 1| +-----+ +-----+ | Tenant1 Site 2 385 +----|VTSD1| |VTSD1|----+ 386 +----|VTSD2| MPLS Cloud |VTSD2|----+ 387 | +-----+ +-----+ | 388 +-----+ | . # # . | +-----+ 389 |RBat2+---+ . #########+-----+######### . +---|RBbt2| 390 +-----+ ...........|VTSD1|........... +-----+ 391 Tenant2 Site2 |VTSD2| ^ Tenant2 Site 2 392 +-----+ | 393 | | 394 +-----+ +-----Emulated 395 |RBct2| TRILL 396 +-----+ 397 Tenant2 Site 3 399 .... VTSD1 Connectivity 400 #### VTSD2 Connectivity 402 Figure 4: Topological Model of VPTS/TIR 403 connecting 2 tenants with three TRILL Sites 405 4.1. Entities in the VPTS Model 406 The CE devices are defined in [RFC4026]. 408 The Generic L2VPN Transport Functional Components like Attachment 409 Circuits, Pseudowires etc. are defined in [RFC4664]. 411 The RB (RBridge) and TRILL Campus are defined in [RFC6325] as updated by 412 [RFC7780]. 414 This model introduces two new entities called TIR and VTSD. 416 4.1.1. TRILL Intermediate Routers (TIR) 418 The TIRs [TRILL Intermediate Routers] must be capable of running both 419 VPLS and TRILL protocols. TIR devices are a superset of the VPLS-PE 420 devices defined in [RFC4026] with the additional functionality of TRILL. 421 The VSI instance that provides transparent bridging functionality in the 422 PE device is replaced with VTSD in a TIR. 424 4.1.2. Virtual TRILL Switch/Service Domain (VTSD) 426 The VTSD [Virtual Trill Switch Domain] is similar to VSI (layer 2 427 bridge) in the VPLS model, but the VTSD acts as a TRILL RBridge. The 428 VTSD is a superset of VSI and must support all the functionality 429 provided by the VSI as defined in [RFC4026]. Along with VSI 430 functionality, the VTSD must be capable of supporting TRILL protocols 431 and forming TRILL adjacencies. The VTSD must be capable of performing 432 all the operations that a standard TRILL Switch can do. 434 One VTSD instance per tenant must be maintained, when multiple tenants 435 are connected to a TIR. The VTSD must maintain all the information 436 maintained by the RBridge on a per tenant basis. The VTSD must also take 437 care of segregating one tenant traffic from other. Each VTSD should have 438 its own nickname, If a TIR supports 10 TRILL tenants, it needs to be 439 assigned with ten TRILL nicknames, one for the nickname space of each of 440 its tenants, and run ten copies of TRILL protocols, one for each tenant. 442 4.2. TRILL Adjacency for VPTS model 444 The VTSD must be capable of forming TRILL adjacency with other VTSDs 445 present in its peer VPTS neighbor, and also the neighbor RBridges 446 present in the TRILL sites. The procedure to form TRILL Adjacency is 447 specified in [RFC7173] and [RFC7177]. 449 4.3. MPLS encapsulation for VPTS model 451 The VPTS model uses PPP or Ethernet pseudowires for MPLS encapsulation 452 as specified in [RFC7173], and requires no changes in the packet format 453 in that RFC. 455 4.4. Loop Free provider PSN/MPLS. 457 This model isn't required to employ Split Horizon mechanism in the 458 provider PSN network, as TRILL takes care of Loop free topology using 459 Distribution Trees. Any multi-destination packet will traverse a 460 distribution tree path. All distribution trees are calculated based on 461 TRILL base protocol standard [RFC6325] as updated by [RFC7780]. 463 4.5. Frame processing. 465 This section specifies multi-destination and unicast frame processing in 466 VPTS/TIR model. 468 4.5.1. Multi-Destination Frame processing 470 Any multi-destination (unknown unicast, multicast or broadcast, as 471 indicated by multi-destination bit in the TRILL Header) packets inside 472 VTSD will be processed or forwarded through the distribution tree for 473 which they were encapsulated on TRILL ingress. If any multi-destination 474 packet is received from the wrong pseudowire at a VTSD, the TRILL 475 protocol running in the VTSD will perform an RPF check as specified in 476 [RFC7780] and drop the packet. 478 The Pruning mechanism in Distribution Trees, as specified in [RFC6325] 479 and [RFC7780], can also be used to avoid forwarding of multi-destination 480 data packets on the branches where there are no potential destinations. 482 4.5.2. Unicast Frame processing 484 Unicast packets must be forwarded in same way they get forwarded in a 485 standard TRILL Campus as specified in [RFC6325]. If multiple equal cost 486 paths are available over pseudowires to reach destination, then VTSD 487 should be capable of doing ECMP for them. 489 5. Extensions to TRILL Over Pseudowires [RFC7173] 491 The [RFC7173] mentions how to interconnect a pair of Transparent 492 Interconnection of Lots of Links (TRILL) switch ports using pseudowires. 493 This document explains, how to connect multiple TRILL sites (not limited 494 to only two sites) using the mechanisms and encapsulations defined in 495 [RFC7173]. 497 6. VPTS Model Versus VPLS Model 499 VPLS Model uses a simpler loop-breaking rule: the "split horizon" rule, 500 where a PE must not forward traffic from one PW to another in the same 501 VPLS mesh, whereas the VPTS Model uses distribution Trees for loop free 502 topology. 504 7. Packet processing between pseudowires 506 Whenever a packet gets received over a pseudowire, a VTSD will 507 decapsulate the MPLS headers followed by checking the TRILL header. If 508 the egress nickname in the TRILL header is for a TRILL site located 509 beyond another pseudowire, then VTSD will encapsulate with new MPLS 510 headers and send it across the proper pseudowire. 512 For example in figure 3, consider that the pseudowire between TIR1 and 513 TIR2 fails, Then TIR1 will communicate with TIR2 via TIR3, whenever 514 packets which are destined to TIR3 gets received from pseudowire between 515 TIR1 and TIR3, VTSD inside TIR3 will decapsulate the MPLS headers, then 516 check the TRILL header's egress nickname field. If the egress nickname 517 indicate it is destained for the RBridge in site3 then the packet will 518 be sent to RBc, if the egress nickname is located at site2, VTSD will 519 add MPLS headers for the pseudowire between TIR3 and TIR2 and forward 520 the packet on that pseudowire. 522 8. Efficiency Considerations 524 Since the VPTS Model uses Distribution trees for processing of multi- 525 destination data packets, it is always advisable to have at least one 526 Distribution tree root to be located in every TRILL site. This will 527 avoid data packets getting received at TRILL sites where end-station 528 service is not enabled for that data packet. 530 9. Security Considerations 532 For general TRILL security considerations, see [RFC6325] 534 For transport of TRILL by Pseudowires security consideration, see 535 [RFC7173]. 537 For general VPLS security considerations, see [RFC4761] and [RFC4762] 539 10. IANA Considerations 541 This document requires no IANA actions. RFC Editor: Please delete this 542 section before publication 544 11. References 546 11.1. Normative References 548 [IS-IS] "Intermediate system to Intermediate system routeing 549 information exchange protocol for use in conjunction with 550 the Protocol for providing the Connectionless-mode Network 551 Service (ISO 8473)", ISO/IEC 10589:2002, 2002". 553 [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A. 554 Ghanwani, "Routing Bridges (RBridges): Base Protocol 555 Specification", RFC 6325, DOI 10.17487/RFC6325, July 2011, 556 . 558 [RFC4761] Kompella, K., Ed., and Y. Rekhter, Ed., "Virtual Private 559 LAN Service (VPLS) Using BGP for Auto-Discovery and 560 Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007, 561 . 563 [RFC4762] Lasserre, M., Ed., and V. Kompella, Ed., "Virtual Private 564 LAN Service (VPLS) Using Label Distribution Protocol (LDP) 565 Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007, 566 . 568 [RFC7041] Balus, F., Ed., Sajassi, A., Ed., and N. Bitar, Ed., 569 "Extensions to the Virtual Private LAN Service (VPLS) 570 Provider Edge (PE) Model for Provider Backbone Bridging", 571 RFC 7041, DOI 10.17487/RFC7041, November 2013, 572 . 574 [RFC7173] Yong, L., Eastlake 3rd, D., Aldrin, S., and J. Hudson, 575 "Transparent Interconnection of Lots of Links (TRILL) 576 Transport Using Pseudowires", RFC 7173, DOI 577 10.17487/RFC7173, May 2014, . 580 [RFC7177] Eastlake 3rd, D., Perlman, R., Ghanwani, A., Yang, H., and 581 V. Manral, "Transparent Interconnection of Lots of Links 582 (TRILL): Adjacency", RFC 7177, DOI 10.17487/RFC7177, May 583 2014, . 585 [RFC7780] Eastlake 3rd, D., Zhang, M., Perlman, R., Banerjee, A., 586 Ghanwani, A., and S. Gupta, "Transparent Interconnection 587 of Lots of Links (TRILL): Clarifications, Corrections, and 588 Updates", RFC 7780, DOI 10.17487/RFC7780, February 2016, 589 . 591 11.2. Informative References 593 [RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual 594 Private Network (VPN) Terminology", RFC 4026, DOI 595 10.17487/RFC4026, March 2005, . 598 [RFC4664] Andersson, L., Ed., and E. Rosen, Ed., "Framework for 599 Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, DOI 600 10.17487/RFC4664, September 2006, . 603 [RFC7172] Eastlake 3rd, D., Zhang, M., Agarwal, P., Perlman, R., and 604 D. Dutt, "Transparent Interconnection of Lots of Links 605 (TRILL): Fine-Grained Labeling", RFC 7172, DOI 606 10.17487/RFC7172, May 2014, . 609 Acknowledgements 611 The contributions of Andrew G. Malis is gratefully acknowledged in 612 improving the quality of this document. 614 Authors' Addresses 616 Mohammed Umair 617 IPInfusion 618 RMZ Centennial 619 Mahadevapura Post 620 Bangalore - 560048 India 622 EMail: mohammed.umair2@gmail.com 624 Kingston Smiler Selvaraj 625 IPInfusion 626 RMZ Centennial 627 Mahadevapura Post 628 Bangalore - 560048 India 630 EMail: kingstonsmiler@gmail.com 632 Donald E. Eastlake 3rd 633 Huawei Technologies 634 155 Beaver Street 635 Milford, MA 01757 636 USA 638 Phone: +1-508-333-2270 639 EMail: d3e3e3@gmail.com 641 Lucy Yong 642 Huawei Technologies 643 5340 Legacy Drive 644 Plano, TX 75024 645 USA 647 Phone: +1-469-227-5837 648 EMail: lucy.yong@huawei.com