Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 Gateway
RFC 7956
Document | Type |
RFC - Proposed Standard
(September 2016; No errata)
Was draft-ietf-trill-irb (trill WG)
|
|
---|---|---|---|
Authors | Hao Weiguo , Li Yizhou , Andrew Qu , Muhammad Durrani , Ponkarthick Sivamurugan | ||
Last updated | 2018-12-20 | ||
Replaces | draft-hao-trill-irb | ||
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 2016-02-08) | ||
IESG | IESG state | RFC 7956 (Proposed Standard) | |
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) W. Hao Request for Comments: 7956 Y. Li Category: Standards Track Huawei ISSN: 2070-1721 A. Qu MediaTec M. Durrani Equinix Inc. P. Sivamurugan IP Infusion September 2016 Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 Gateway Abstract The base TRILL (Transparent Interconnection of Lots of Links) protocol provides optimal pair-wise data frame forwarding for Layer 2 intra-subnet traffic but not for Layer 3 inter-subnet traffic. A centralized gateway solution is typically used for Layer 3 inter- subnet traffic forwarding but has the following issues: 1. Sub-optimum forwarding paths for inter-subnet traffic. 2. A centralized gateway that may need to support a very large number of gateway interfaces in a Data Center, one per tenant per Data Label used by that tenant, to provide interconnect functionality for all the Layer 2 Virtual Networks in a TRILL campus. 3. A traffic bottleneck at the gateway. This document specifies an optional TRILL distributed gateway solution that resolves these centralized gateway issues. 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 7841. 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/rfc7956. Hao, et al. Standards Track [Page 1] RFC 7956 TRILL Distributed Layer 3 Gateway September 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 1.1. Document Organization ......................................3 2. Conventions Used in This Document ...............................4 3. Simplified Example and Problem Statement ........................5 3.1. Simplified Example .........................................6 3.2. Problem Statement Summary ..................................8 4. Layer 3 Traffic Forwarding Model ................................9 5. Distributed Gateway Solution Details ...........................10 5.1. Local Routing Information .................................11 5.2. Local Routing Information Synchronization .................12 5.3. Active-Active Access ......................................14 5.4. Data Traffic Forwarding Process ...........................15 6. Distributed Layer 3 Gateway Process Example ....................16 6.1. Control-Plane Process .....................................17 6.2. Data-Plane Process ........................................19 7. TRILL Protocol Extensions ......................................20 7.1. The Tenant Label and Gateway MAC APPsub-TLV ...............20 7.2. The SE Flag in the NickFlags APPsub-TLV ...................21 7.3. The IPv4 Prefix APPsub-TLV ................................22 7.4. The IPv6 Prefix APPsub-TLV ................................23 8. Security Considerations ........................................24 9. Management Considerations ......................................24 10. IANA Considerations ...........................................24 11. References ....................................................25 11.1. Normative References .....................................25 11.2. Informative References ...................................26Show full document text