idnits 2.17.1 draft-muks-trill-transport-over-mpls-02.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 : ---------------------------------------------------------------------------- ** There are 26 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 9, 2016) is 2970 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 ---------------------------------------------------------------------------- == Missing Reference: 'RFC1661' is mentioned on line 153, but not defined == Unused Reference: 'RFC3985' is defined on line 583, but no explicit reference was found in the text == Unused Reference: 'RFC4448' is defined on line 593, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 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: September 10, 2016 March 9, 2016 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 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 Internet-Draft is submitted to IETF in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as 34 Internet-Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/1id-abstracts.html 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html 47 Copyright and License Notice 49 Copyright (c) 2016 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2. TRILL Over MPLS Model . . . . . . . . . . . . . . . . . . . . . 5 67 3. VPLS Model . . . . . . . . . . . . . . . . . . . . . . . . . . 6 68 3.1. Entities in the VPLS Model . . . . . . . . . . . . . . . . 7 69 3.3. TRILL Adjacency for VPLS model . . . . . . . . . . . . . . 8 70 3.4. MPLS encapsulation for VPLS model . . . . . . . . . . . . . 8 71 3.5. Loop Free provider PSN/MPLS. . . . . . . . . . . . . . . . 8 72 3.6. Frame processing. . . . . . . . . . . . . . . . . . . . . . 8 73 4. VPTS Model . . . . . . . . . . . . . . . . . . . . . . . . . . 8 74 4.1. Entities in the VPTS Model . . . . . . . . . . . . . . . . 10 75 4.1.1. TRILL Intermediate Routers (TIR) . . . . . . . . . . . 11 76 4.1.2. Virtual TRILL Switch/Service Domain (VTSD) . . . . . . 11 77 4.2. TRILL Adjacency for VPTS model . . . . . . . . . . . . . . 11 78 4.3. MPLS encapsulation for VPTS model . . . . . . . . . . . . . 11 79 4.4. Loop Free provider PSN/MPLS. . . . . . . . . . . . . . . . 12 80 4.5. Frame processing. . . . . . . . . . . . . . . . . . . . . . 12 81 4.5.1. Multi-Destination Frame processing . . . . . . . . . . 12 82 4.5.2. Unicast Frame processing . . . . . . . . . . . . . . . 12 83 5. Extensions to TRILL Over Pseudowires [RFC7173] . . . . . . . . 12 84 6. VPTS Model Versus VPLS Model . . . . . . . . . . . . . . . . . 12 85 7. Packet processing between pseudowires . . . . . . . . . . . . . 13 86 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 14 87 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14 88 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 89 10.1. Normative References . . . . . . . . . . . . . . . . . . . 14 90 10.2. Informative References . . . . . . . . . . . . . . . . . . 15 91 Appendix Z: Change History . . . . . . . . . . . . . . . . . . . . 16 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 94 1. Introduction 96 The IETF Transparent Interconnection of Lots of Links (TRILL) 97 protocol [RFC6325] [RFC7177] [RFC7780] provides transparent 98 forwarding in multi-hop networks with arbitrary topology and link 99 technologies using a header with a hop count and link-state routing. 100 TRILL provides optimal pair-wise forwarding without configuration, 101 safe forwarding even during periods of temporary loops, and support 102 for multipathing of both unicast and multicast traffic. Intermediate 103 Systems (ISs) implementing TRILL are called Routing Bridges(RBridges) 104 or TRILL Switches 106 This draft, in conjunction with [RFC7173] on TRILL Transport using 107 Pseudowires, addresses two problems: 109 1) Providing connection between more than two TRILL sites belongs to 110 a single TRILL network that are separated by an MPLS provider network 111 using [RFC7173]. (Herein also called problem statement 1.) 113 2) Providing a single logical virtualized TRILL network for different 114 tenants that are separated by an MPLS provider network. In short 115 providing connection between TRILL sites belonging to a 116 tenant/tenants over a MPLS provider network. (Herein also called 117 problem statement 2.) 119 A tenant is the administrative entity on whose behalf their 120 associated services are managed. Here tenant refers to a TRILL campus 121 that is segregated from other tenants for security reasons. 123 A key multi-tenancy requirement is traffic isolation so that one 124 tenant's traffic is not visible to any other tenant. This draft also 125 addresses the problem of multi-tenancy by isolating one tenant's 126 traffic from the other. 128 1.1. Terminology 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 132 document are to be interpreted as described in RFC 2119 [RFC2119]. 134 Acronyms used in this document include the following: 136 AC - Attachment Circuit [RFC4664] 138 Data Label - VLAN or FGL 140 ECMP - Equal Cost Multi Path 141 FGL - Fine-Grained Labeling [RFC7172] 143 IS-IS - Intermediate System to Intermediate System [IS-IS] 145 LDP - Label Distribution Protocol 147 LAN - Local Area Network 149 MPLS - Multi-Protocol Label Switching 151 PE - Provider Edge Device 153 PPP - Point-to-Point Protocol [RFC1661] 155 PSN - Packet Switched Network 157 PW - Pseudowire [RFC4664] 159 TIR - TRILL Intermediate Router 160 (Devices that has both IP/MPLS and TRILL 161 functionality) 163 TRILL - Transparent Interconnection of Lots of Links 164 OR Tunneled Routing in the Link Layer 166 TRILL Site - A part of a TRILL campus that contains at 167 least one RBridge. 169 VLAN - Virtual Local Area Network 171 VPLS - Virtual Private LAN Service 173 VPTS - Virtual Private TRILL Service 175 VSI - Virtual Service Instance [RFC4664] 177 VTSD - Virtual TRILL Switch Domain 178 OR Virtual TRILL Service Domain 179 A Virtual RBridge that segregates one tenant's 180 TRILL database as well as traffic from the other. 182 WAN - Wide Area Network 184 2. TRILL Over MPLS Model 186 TRILL Over MPLS can be achieved by two different ways. 188 a) VPLS Model for TRILL 189 b) VPTS Model/TIR Model 191 Both these models can be used to solve the problem statement 1 and 2. 192 Herein the VPLS Model for TRILL is also called Model 1 and the VPTS 193 Model/TIR Model is also called Model 2. 195 3. VPLS Model 197 Figure 1 shows the topological model of TRILL over MPLS using VPLS 198 model. The PE routers in the below topology model should support all 199 the functional Components mentioned in [RFC4664]. 201 +-----+ +-----+ 202 | RBa +---+ ........................... +---| RBb | 203 +-----+ | . . | +-----+ 204 Site 1 | +----+ +----+ | Site 2 205 +----|PE1 | |PE2 |----+ 206 +----+ MPLS Cloud +----+ 207 . . 208 . +----+ . 209 ..........|PE3 |........... 210 +----+ ^ 211 | | 212 | +-- Emulated LAN 213 +-----+ 214 | RBc | 215 +-----+ 216 Site 3 218 Figure 1: Topological Model of TRILL over MPLS 219 connecting three TRILL Sites 221 Figure 2 below shows the topological model of TRILL over MPLS to 222 connect multiple TRILL sites belonging to a tenant (tenant here is a 223 campus, not a Data label). VSI1 and VSI2 are two Virtual Service 224 Instances that segregate Tenant1's traffic from other tenant traffic. 225 VSI1 will maintain its own database for Tenant1, similarly VSI2 will 226 maintain its own database for Tenant2. 228 +-----+ ............................ +-----+ 229 |RBat1+---+ . ++++++++++++++++++++++++ . +---|RBbt1| 230 +-----+ | . + + . | +-----+ 231 Tenant1 Site 1 | +----+ +----+ | Tenant1 Site2 232 +----|VSI1| |VSI1|----+ 233 +----|VSI2| MPLS Cloud |VSI2|----+ 234 | +----+ +----+ | 235 +-----+ | . + + . | +-----+ 236 |RBat2+---+ . +++++++++ +----+ ++++++++ . +---|RBbt2| 237 +-----+ ............|VSI1|........... +-----+ 238 Tenant2 Site 2 +----|VSI2|----+ ^ Tenant2 Site2 239 | +----+ | | 240 | | | 241 +-----+ +-----+ +-----Emulated 242 |RBct2| |RBct1| LAN 243 +-----+ +-----+ 244 Tenant2 Site 3 Tenant1 Site 3 246 .... VSI1 Path 247 ++++ VSI2 Path 249 Figure 2: Topological Model for VPLS Model 250 connecting 2 Tenants with 3 sites each 252 In this model, TRILL sites are connected to VPLS-capable PE devices that 253 provide a logical interconnect, such that TRILL RBridges belonging to a 254 specific tenant connected via an single bridged Ethernet. These devices 255 are the same as PE devices specified in [RFC4026]. The Attachment 256 Circuit ports of PE Routers are layer 2 switch ports that are connected 257 to the RBridges at a TRILL site. Here each VPLS instance looks like an 258 emulated LAN. This model is similar to connecting different RBridges 259 (TRILL sites) by a layer 2 bridge domain (multi access link) as 260 specified in [RFC6325]. This model doesn't requires any changes in PE 261 routers to carry TRILL packets, as TRILL packets will be transferred 262 transparently. 264 3.1. Entities in the VPLS Model 266 The PE (VPLS-PE) and CE devices are defined in [RFC4026]. 268 The Generic L2VPN Transport Functional Components like Attachment 269 Circuits, Pseudowires, VSI etc. are defined in [RFC4664]. 271 The RB (RBridge) and TRILL Sites are defined in [RFC6325] as updated by 272 [RFC7780]. 274 3.3. TRILL Adjacency for VPLS model 276 As specified in section 3 of this document, the MPLS cloud looks like an 277 emulated LAN (also called multi-access link or broadcast link). This 278 results in RBridges at different sites looking like they are connected 279 by a multi-access link. With such interconnection, the TRILL adjacency 280 over the link are automatically discovered and established through TRILL 281 IS-IS control messages [RFC7177]. These IS-IS control messages are 282 transparently forwarded by the VPLS domain, after doing MPLS 283 encapsulation specified in the section 3.4. 285 3.4. MPLS encapsulation for VPLS model 287 MPLS encapsulation over Ethernet pseudowire is specified in [RFC7173] 288 Appendix A, and requires no change in the frame format. 290 3.5. Loop Free provider PSN/MPLS. 292 No explicit handling is required to avoid loop free topology. Split 293 Horizon technique specified in [RFC4664] will take care of avoiding 294 loops in the provider PSN network. 296 3.6. Frame processing. 298 The PE device transparently process the TRILL control and data frames. 299 Procedures to forward the frames are defined in [RFC4664] 301 4. VPTS Model 303 The (Virtual Private TRILL Service) VPTS is a L2 TRILL service, that 304 emulates TRILL service across a Wide Area Network (WAN). VPTS is similar 305 to what VPLS does for bridge domain. VPLS provides "Virtual Private LAN 306 Service" for different customers. VPTS provides "Virtual Private TRILL 307 Service" for different TRILL tenants. 309 Figure 3 shows the topological model of TRILL over MPLS using VPTS. In 310 this model the PE routers are replaced with TIR (TRILL Intermediate 311 Router) and VSI is replaced with VTSD (Virtual TRILL Switch Domain). The 312 TIR devices must be capable of supporting both MPLS and TRILL and is 313 defined in section 4.1.1. The TIR devices are interconnected via PWs and 314 appear as a unified emulated TRILL campus with each VTSD inside a TIR 315 equivalent to a RBridge. 317 Some of the reasons for interconnecting TRILL Sites without isolating 318 TRILL Control plane of one TRILL site with other is as described below. 320 1) Nickname Uniqueness: One of the basic requirements of TRILL is that, 321 RBridge Nicknames should be unique with in the campus. If we segregate 322 control plane of one TRILL site from other TRILL site and provide 323 interconnection between these sites, it may result in Nickname 324 collision. 326 2) Distribution Tree and its pruning: When a TRILL Data packet traverse 327 a Distribution Tree, it will adhere to it even in other TRILL site. If 328 no end-station service is enabled for a particular Data Label in a TRILL 329 site, Distribution Tree may be pruned and TRILL data packets of that 330 particular Data Label might never get to other TRILL sites. RPF check 331 will always be performed on the packets that are received TIR's through 332 pseudowires. 334 3) Hop Count values: When a TRILL data packet is received over a 335 pseudowire by a TIR, the TIR does the processing of Hop Count defined in 336 [RFC6325] and will not perform any resetting of Hop Count. 338 +-----+ +-----+ 339 | RBa +---+ ........................... +---| RBb | 340 +-----+ | . . | +-----+ 341 Site 1 | +----+ +----+ | Site 2 342 +----|TIR1| |TIR2|----+ 343 +----+ MPLS Cloud +----+ 344 . . 345 . +----+ . 346 ..........|TIR3|........... 347 +----+ ^ 348 | | 349 | +-- Emulated TRILL 350 +-----+ 351 | RBc | 352 +-----+ 353 Site 3 355 Figure 3: Topological Model of VPTS/TIR 356 connecting three TRILL Sites 358 In the above figure (Figure 3) Site1, Site2 and Site3 (running TRILL 359 protocol) are connected to TIR Devices. These TIR devices along with 360 the MPLS cloud looks like an unified emulated TRILL campus. Only the PE 361 devices in the MPLS network should be replaced with TIRs so the 362 intermediate P routers are agnostic to the TRILL protocol. 364 Figure 4 below extends the topological model of TRILL over MPLS to 365 connect multiple TRILL sites belonging to a tenant (tenant here is a 366 campus, not a Data label) using VPTS model. VTSD1 and VTSD2 are two 367 Virtual TRILL Switch Domains (Virtual RBridges) that segregate 368 Tenant1's traffic from Tenant2's traffic. VTSD1 will maintain its own 369 TRILL database for Tenant1, similarly VTSD2 will maintain its own TRILL 370 database for Tenant2. 372 +-----+ ............................ +-----+ 373 |RBat1+---+ . ######################## . +---|RBbt1| 374 +-----+ | . # # . | +-----+ 375 Tenant1 Site 1| +-----+ +-----+ | Tenant1 Site 2 376 +----|VTSD1| |VTSD1|----+ 377 +----|VTSD2| MPLS Cloud |VTSD2|----+ 378 | +-----+ +-----+ | 379 +-----+ | . # # . | +-----+ 380 |RBat2+---+ . #########+-----+######### . +---|RBbt2| 381 +-----+ ...........|VTSD1|........... +-----+ 382 Tenant2 Site2 +---|VTSD2|----+ ^ Tenant2 Site 2 383 | +-----+ | | 384 | | | 385 +-----+ +-----+ +-----Emulated 386 |RBct2| |RBct1| TRILL 387 +-----+ +-----+ 388 Tenant2 Site 3 Tenant1 Site 3 390 .... VTSD1 Connectivity 391 #### VTSD2 Connectivity 393 Figure 4: Topological Model of VPTS/TIR 394 connecting 2 tenants with three TRILL Sites 396 4.1. Entities in the VPTS Model 398 The CE devices are defined in [RFC4026]. 400 The Generic L2VPN Transport Functional Components like Attachment 401 Circuits, Pseudowires etc. are defined in [RFC4664]. 403 The RB (RBridge) and TRILL Campus are defined in [RFC6325] as updated by 404 [RFC7780]. 406 This model introduces two new entities called TIR and VTSD. 408 4.1.1. TRILL Intermediate Routers (TIR) 410 The TIRs [TRILL Intermediate Routers] must be capable of running both 411 VPLS and TRILL protocols. TIR devices are a superset of the VPLS-PE 412 devices defined in [RFC4026] with the additional functionality of TRILL. 413 The VSI instance that provides transparent bridging functionality in the 414 PE device is replaced with VTSD in TIR. 416 4.1.2. Virtual TRILL Switch/Service Domain (VTSD) 418 The VTSD [Virtual Trill Switch Domain] is similar to VSI (layer 2 419 bridge) in VPLS model, but this acts as a TRILL RBridge. The VTSD is a 420 superset of VSI and must support all the functionality provided by the 421 VSI as defined in [RFC4026]. Along with VSI functionality, the VTSD must 422 be capable of supporting TRILL protocols and form TRILL adjacencies. The 423 VTSD must be capable of performing all the operations that a standard 424 TRILL Switch can do. 426 One VTSD instance per tenant must be maintained, when multiple tenants 427 are connected to a TIR. The VTSD must maintain all the information 428 maintained by the RBridge on a per tenant basis. The VTSD must also take 429 care of segregating one tenant traffic from other. Each VTSD should have 430 its own nickname, If a TIR supports 10 TRILL tenants, it needs to be 431 assigned with ten TRILL nicknames and run ten copies of TRILL protocols, 432 one for each. 434 4.2. TRILL Adjacency for VPTS model 436 The VTSD must be capable of forming TRILL adjacency with other VTSDs 437 present in its peer VPTS neighbor, and also the neighbor RBridges 438 present in the TRILL sites. The procedure to form TRILL Adjacency is 439 specified in [RFC7173] and [RFC7177]. 441 4.3. MPLS encapsulation for VPTS model 443 MPLS encapsulation over pseudowire is specified in [RFC7173], and 444 requires no changes in the frame format. 446 4.4. Loop Free provider PSN/MPLS. 448 This model isn't required to employ Split Horizon mechanism in the 449 provider PSN network, as TRILL takes care of Loop free topology using 450 Distribution Trees. Any multi-destination packet will traverse a 451 distribution tree path. All distribution trees are calculated based on 452 TRILL base protocol standard [RFC6325] as updated by [RFC7780]. 454 4.5. Frame processing. 456 This section specifies multi-destination and unicast frame processing in 457 VPTS/TIR model. 459 4.5.1. Multi-Destination Frame processing 461 Any multi-destination (unknown unicast, multicast or broadcast) packets 462 inside VTSD should be processed or forwarded through any one of the 463 distribution trees. If any multi-destination packet is received from the 464 wrong pseudowire at a VTSD, the TRILL protocol running in VTSD will 465 perform a RPF check as specified in [RFC7780] and drops the packet. 467 Pruning mechanism in Distribution Trees, as specified in [RFC6325] and 468 [RFC7780] can also be used to avoid forwarding of multi-destination data 469 packets on the branches where there are no potential destinations. 471 4.5.2. Unicast Frame processing 473 Unicast packets must be forwarded in same way they get forwarded in a 474 standard TRILL Campus as specified in [RFC6325]. If multiple equal cost 475 paths are available over pseudowires to reach destination, then VTSD 476 should be capable of doing ECMP for them. 478 5. Extensions to TRILL Over Pseudowires [RFC7173] 480 The [RFC7173] mentions how to interconnect a pair of Transparent 481 Interconnection of Lots of Links (TRILL) switch ports using pseudowires. 482 This document explains, how to connect multiple TRILL sites (not limited 483 to only two sites) using the mechanisms and encapsulations defined in 484 [RFC7173]. 486 6. VPTS Model Versus VPLS Model 487 VPLS Model uses a simpler loop breaking rule: the "split horizon" rule, 488 where a PE must not forward traffic from one PW to another in the same 489 VPLS mesh. 491 An issue with the above rule is that if a pseudowire between PEs fails, 492 frames will not get forwarded between the PEs where pseudowire went 493 down. 495 VPTS solves this problem, as the VPTS Model uses distribution Trees for 496 loop free topology. Hence the frames reach all TIRs even when any one of 497 the pseudowires fails in the mesh. 499 If equal cost paths are available to reach a site over pseudowires, VPTS 500 Model can use ECMP for processing of frames over pseudowires. 502 7. Packet processing between pseudowires 504 Whenever a packet gets received over a pseudowire, VTSD will decapsulate 505 the MPLS headers followed by checking the TRILL header. If the egress 506 nickname in the TRILL header is for a TRILL site located beyond another 507 pseudowire, then VTSD will encapsulate with new MPLS headers and send it 508 across the proper pseudowire. 510 For example in figure 3, consider that the pseudowire between TIR1 and 511 TIR2 fails, Then TIR1 will communicate with TIR2 via TIR3, whenever 512 packets which are destined to TIR3 gets received from pseudowire between 513 TIR1 and TIR3, VTSD inside TIR3 will decapsulate the MPLS headers, then 514 check the TRILL header's egress nickname field. If egress nickname is 515 destained for the RBridge in site3 then the packet will be sent to RBc, 516 if egress nickname is located at site2, VTSD will add MPLS headers for 517 the pseudowire between TIR3 and TIR2 and forward the packet on that 518 pseudowire. 520 8. Security Considerations 522 For general TRILL security considerations, see [RFC6325] 524 For transport of TRILL by Pseudowires security consideration, see 525 [RFC7173]. 527 For general VPLS security considerations, see [RFC4762] 529 Since the VPTS Model uses Distribution trees for processing of multi- 530 destination data packets, it is always advisable to have at least one 531 Distribution tree root to be located in every TRILL site. This will 532 avoid data packets getting received at TRILL sites where end-station 533 service is not enabled for that data packet. 535 9. IANA Considerations 537 This document requires no IANA actions. RFC Editor: Please delete this 538 section before publication 540 10. References 542 10.1. Normative References 544 [IS-IS] "Intermediate system to Intermediate system routeing 545 information exchange protocol for use in conjunction with 546 the Protocol for providing the Connectionless-mode Network 547 Service (ISO 8473)", ISO/IEC 10589:2002, 2002". 549 [RFC6325] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A. 550 Ghanwani, "Routing Bridges (RBridges): Base Protocol 551 Specification", RFC 6325, DOI 10.17487/RFC6325, July 2011, 552 . 554 [RFC4762] Lasserre, M., Ed., and V. Kompella, Ed., "Virtual Private 555 LAN Service (VPLS) Using Label Distribution Protocol (LDP) 556 Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007, 557 . 559 [RFC7173] Yong, L., Eastlake 3rd, D., Aldrin, S., and J. Hudson, 560 "Transparent Interconnection of Lots of Links (TRILL) 561 Transport Using Pseudowires", RFC 7173, DOI 562 10.17487/RFC7173, May 2014, . 565 [RFC7177] Eastlake 3rd, D., Perlman, R., Ghanwani, A., Yang, H., and 566 V. Manral, "Transparent Interconnection of Lots of Links 567 (TRILL): Adjacency", RFC 7177, DOI 10.17487/RFC7177, May 568 2014, . 570 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 571 Requirement Levels", BCP 14, RFC 2119, DOI 572 10.17487/RFC2119, March 1997, . 575 [RFC7780] EEastlake 3rd, D., Zhang, M., Perlman, R., Banerjee, A., 576 Ghanwani, A., and S. Gupta, "Transparent Interconnection 577 of Lots of Links (TRILL): Clarifications, Corrections, and 578 Updates", RFC 7780, DOI 10.17487/RFC7780, February 2016, 579 . 581 10.2. Informative References 583 [RFC3985] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation 584 Edge-to-Edge (PWE3) Architecture", RFC 3985, DOI 585 10.17487/RFC3985, March 2005, . 588 [RFC4026] Andersson, L. and T. Madsen, "Provider Provisioned Virtual 589 Private Network (VPN) Terminology", RFC 4026, DOI 590 10.17487/RFC4026, March 2005, . 593 [RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron, 594 "Encapsulation Methods for Transport of Ethernet over MPLS 595 Networks", RFC 4448, DOI 10.17487/RFC4448, April 2006, 596 . 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 Appendix Z: Change History 611 From -00 to -01 613 1. Did some editorial fixes 615 2. Changed Intended Status from "Proposed Standard" 616 to "Informational" 618 3. Provided reasons for interconnecting TRILL 619 Sites without isolating TRILL Control plane, in section 4. 621 4. Updated section 4.1.2 623 5. Added section for Frame processing between pseudowires. 625 6. Fix references for RFCs, etc. 627 7. Add this Change History Appendix. 629 From -01 to -02 631 Editorial improvements. 633 Authors' Addresses 635 Mohammed Umair 636 IPInfusion 637 RMZ Centennial 638 Mahadevapura Post 639 Bangalore - 560048 India 641 EMail: mohammed.umair2@gmail.com 643 Kingston Smiler Selvaraj 644 IPInfusion 645 RMZ Centennial 646 Mahadevapura Post 647 Bangalore - 560048 India 648 EMail: kingstonsmiler@gmail.com 650 Donald E. Eastlake 3rd 651 Huawei Technologies 652 155 Beaver Street 653 Milford, MA 01757 654 USA 656 Phone: +1-508-333-2270 657 EMail: d3e3e3@gmail.com 659 Lucy Yong 660 Huawei Technologies 661 5340 Legacy Drive 662 Plano, TX 75024 663 USA 665 Phone: +1-469-227-5837 666 EMail: lucy.yong@huawei.com