Transparent Interconnection of Lots of Links (TRILL): Adjacency
RFC 7177
Document | Type |
RFC - Proposed Standard
(May 2014; No errata)
Obsoletes RFC 6327
Updates RFC 6325
|
|
---|---|---|---|
Authors | Donald Eastlake , Radia Perlman , Anoop Ghanwani , Howard Yang , Vishwas Manral | ||
Last updated | 2015-10-14 | ||
Replaces | draft-eastlake-trill-rfc6327bis | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jon Hudson | ||
Shepherd write-up | Show (last changed 2013-10-25) | ||
IESG | IESG state | RFC 7177 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Ted Lemon | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) D. Eastlake 3rd Request for Comments: 7177 Huawei Obsoletes: 6327 R. Perlman Updates: 6325 Intel Labs Category: Standards Track A. Ghanwani ISSN: 2070-1721 Dell H. Yang Cisco V. Manral Ionos Corp. May 2014 Transparent Interconnection of Lots of Links (TRILL): Adjacency Abstract The IETF Transparent Interconnection of Lots of Links (TRILL) protocol supports arbitrary link technologies between TRILL switches, including point-to-point links and multi-access Local Area Network (LAN) links that can have multiple TRILL switches and end stations attached. TRILL uses Intermediate System to Intermediate System (IS-IS) routing. This document specifies the establishment, reporting, and termination of IS-IS adjacencies between TRILL switches, also known as RBridges (Routing Bridges). It also concerns four other link-local aspects of TRILL: Designated RBridge (DRB) selection, MTU (Maximum Transmission Unit) testing, pseudonode creation, and BFD (Bidirectional Forwarding Detection) session bootstrapping in connection with adjacency. State diagrams are included where appropriate. This document obsoletes RFC 6327 and updates RFC 6325. 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/rfc7177. Eastlake, et al. Standards Track [Page 1] RFC 7177 TRILL: Adjacency May 2014 Copyright Notice Copyright (c) 2014 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. Eastlake, et al. Standards Track [Page 2] RFC 7177 TRILL: Adjacency May 2014 Table of Contents 1. Introduction ....................................................4 1.1. Content and Precedence .....................................5 1.2. Terminology and Acronyms ...................................5 2. The TRILL Hello Environment and Purposes ........................6 2.1. RBridge Interconnection by Ethernet ........................6 2.2. Handling Native Frames .....................................7 2.3. Zero or Minimal Configuration ..............................8 2.4. MTU Robustness .............................................8 2.5. Purposes of the TRILL Hello Protocol .......................9 3. Adjacency State Machinery ......................................10 3.1. TRILL Hellos, Ports, and VLANs ............................10 3.2. Adjacency Table Entries and States ........................11 3.3. Adjacency and Hello Events ................................12 3.4. Adjacency State Diagram and Table .........................15 3.5. Multiple Parallel Links ...................................17 3.6. Insufficient Space in Adjacency Table .....................17 4. LAN Ports and DRB State ........................................17 4.1. Port Table Entries and DRB Election State .................18 4.2. DRB Election Events .......................................19 4.2.1. DRB Election Details ...............................20 4.2.2. Change in DRB ......................................20 4.2.3. Change in Designated VLAN ..........................21Show full document text