Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC Attachments
RFC 7782
Document | Type | RFC - Proposed Standard (February 2016; No errata) | |
---|---|---|---|
Authors | Mingui Zhang , Radia Perlman , Hongjun Zhai , Muhammad Durrani , Sujay Gupta | ||
Last updated | 2018-12-20 | ||
Replaces | draft-zhang-trill-aa-multi-attach | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Donald Eastlake | ||
Shepherd write-up | Show (last changed 2015-08-13) | ||
IESG | IESG state | RFC 7782 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alia Atlas | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) M. Zhang Request for Comments: 7782 Huawei Category: Standards Track R. Perlman ISSN: 2070-1721 EMC H. Zhai Astute Technology M. Durrani Cisco Systems S. Gupta IP Infusion February 2016 Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC Attachments Abstract TRILL (Transparent Interconnection of Lots of Links) active-active service provides end stations with flow-level load balance and resilience against link failures at the edge of TRILL campuses, as described in RFC 7379. This document specifies a method by which member RBridges (also referred to as Routing Bridges or TRILL switches) in an active-active edge RBridge group use their own nicknames as ingress RBridge nicknames to encapsulate frames from attached end systems. Thus, remote edge RBridges (who are not in the group) will see one host Media Access Control (MAC) address being associated with the multiple RBridges in the group. Such remote edge RBridges are required to maintain all those associations (i.e., MAC attachments) and to not flip-flop among them (as would occur prior to the implementation of this specification). The design goals of this specification are discussed herein. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7782. Zhang, et al. Standards Track [Page 1] RFC 7782 Multi-Attach for Active-Active Edge February 2016 Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 2. Acronyms and Terminology ........................................4 3. Overview ........................................................5 4. Incremental Deployable Options ..................................6 4.1. Details of Option B ........................................7 4.1.1. Advertising Data Labels for Active-Active Edge ......7 4.1.2. Discovery of Active-Active Edge Members .............8 4.1.3. Advertising Learned MAC Addresses ...................9 4.2. Extended RBridge Capability Flags APPsub-TLV ..............11 5. Meeting the Design Goals .......................................12 5.1. No MAC Address Flip-Flopping (Normal Unicast Egress) ......12 5.2. Regular Unicast/Multicast Ingress .........................12 5.3. Correct Multicast Egress ..................................12 5.3.1. No Duplication (Single Exit Point) .................12 5.3.2. No Echo (Split Horizon) ............................13 5.4. No Black-Hole or Triangular Forwarding ....................14 5.5. Load Balance towards the AAE ..............................14 5.6. Scalability ...............................................14 6. E-L1FS Backward Compatibility ..................................15 7. Security Considerations ........................................15 8. IANA Considerations ............................................16 8.1. TRILL APPsub-TLVs .........................................16 8.2. Extended RBridge Capabilities Registry ....................16Show full document text