Transparent Interconnection of Lots of Links (TRILL): Multi-Topology
RFC 8377
|
| Document |
Type |
|
RFC - Proposed Standard
(July 2018; No errata)
|
|
Last updated |
|
2018-07-31
|
|
Replaces |
|
draft-eastlake-trill-multi-topology
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Susan Hares
|
|
Shepherd write-up |
|
Show
(last changed 2018-02-19)
|
| IESG |
IESG state |
|
RFC 8377 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alia Atlas
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
IANA OK - Actions Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) D. Eastlake 3rd
Request for Comments: 8377 M. Zhang
Updates: 6325, 7177 Huawei
Category: Standards Track A. Banerjee
ISSN: 2070-1721 Cisco
July 2018
Transparent Interconnection of Lots of Links (TRILL):
Multi-Topology
Abstract
This document specifies extensions to the IETF TRILL (Transparent
Interconnection of Lots of Links) protocol to support multi-topology
routing of unicast and multi-destination traffic based on IS-IS
(Intermediate System to Intermediate System) multi-topology specified
in RFC 5120. This document updates RFCs 6325 and 7177.
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
https://www.rfc-editor.org/info/rfc8377.
Copyright Notice
Copyright (c) 2018 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
(https://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 1]
RFC 8377 TRILL: Multi-Topology July 2018
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................4
2. Topologies ......................................................5
2.2. Links and Multi-Topology ...................................5
2.3. TRILL Switches and Multi-Topology ..........................6
2.4. TRILL Data Packets and Multi-Topology ......................6
2.4.1. Explicit Topology Labeling Support ..................7
2.4.2. The Explicit Topology Label .........................8
2.4.3. TRILL Use of the MT Label ...........................8
3. TRILL Multi-Topology Adjacency and Routing .....................10
3.1. Adjacency .................................................10
3.2. TRILL Switch Nicknames ....................................10
3.3. TRILL Unicast Routing .....................................11
3.4. TRILL Multi-Destination Routing ...........................11
3.4.1. Distribution Trees .................................11
3.4.2. Multi-Access Links .................................13
4. Mixed Links ....................................................13
5. Other Multi-Topology Considerations ............................14
5.1. Address Learning ..........................................14
5.1.1. Data Plane Learning ................................14
5.1.2. Multi-Topology ESADI ...............................14
5.2. Legacy Stubs ..............................................14
5.3. RBridge Channel Messages ..................................14
5.4. Implementations Considerations ............................15
6. Allocation Considerations ......................................15
6.1. IEEE Registration Authority Considerations ................15
6.2. IANA Considerations .......................................15
7. Security Considerations ........................................16
8. References .....................................................17
8.1. Normative References ......................................17
8.2. Informative References ....................................18
Appendix A. Differences from RFC 5120 .............................19
Acknowledgements ..................................................19
Authors' Addresses ................................................20
1. Introduction
This document specifies extensions to the IETF TRILL (Transparent
Interconnection of Lots of Links) protocol [RFC6325] [RFC7177]
[RFC7780] to support multi-topology routing for both unicast and
Show full document text