Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames
RFC 8397
| Document | Type | RFC - Proposed Standard (May 2018; No errata) | |
|---|---|---|---|
| Authors | Mingui Zhang , Donald Eastlake , Radia Perlman , Hongjun Zhai , Dongxin Liu | ||
| Last updated | 2018-05-31 | ||
| Replaces | draft-zhang-trill-multilevel-unique-nickname | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Susan Hares | ||
| Shepherd write-up | Show (last changed 2018-02-20) | ||
| IESG | IESG state | RFC 8397 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alia Atlas | ||
| Send notices to | Susan Hares <shares@ndzh.com> | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Zhang
Request for Comments: 8397 D. Eastlake 3rd
Category: Standards Track Huawei
ISSN: 2070-1721 R. Perlman
Dell EMC
H. Zhai
JIT
D. Liu
China Telecom Co., Ltd
May 2018
Transparent Interconnection of Lots of Links (TRILL) Multilevel
Using Unique Nicknames
Abstract
TRILL (Transparent Interconnection of Lots of Links) routing can be
extended to support multiple levels by building on the multilevel
feature of IS-IS routing. Depending on how nicknames are managed,
there are two primary alternatives to realize TRILL multilevel: the
unique nickname approach and the aggregated nickname approach as
discussed in RFC 8243. This document specifies a unique nickname
approach. This approach gives unique nicknames to all TRILL switches
across the multilevel TRILL campus.
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/rfc8397.
Zhang, et al. Standards Track [Page 1]
RFC 8397 TRILL Multilevel Unique Nickname May 2018
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.
Table of Contents
1. Introduction ....................................................3
2. Acronyms and Terminology ........................................4
3. Data Routing ....................................................4
3.1. Unicast Routing ............................................4
3.2. Multi-destination Routing ..................................5
3.2.1. Local Distribution Trees ............................6
3.2.2. Global Distribution Trees ...........................6
4. Protocol Basics and Extensions ..................................8
4.1. Multilevel TRILL Basics ....................................8
4.2. Nickname Allocation ........................................9
4.3. Nickname Announcements .....................................9
4.4. Capability Indication .....................................11
5. Mix with Aggregated Nickname Areas .............................11
6. Security Considerations ........................................12
7. IANA Considerations ............................................13
8. References .....................................................13
8.1. Normative References ......................................13
8.2. Informative References ....................................14
Contributors ......................................................15
Authors' Addresses ................................................15
Zhang, et al. Standards Track [Page 2]
RFC 8397 TRILL Multilevel Unique Nickname May 2018
1. Introduction
The multiple-level feature of [IS-IS] can increase the scalability of
TRILL as discussed in [RFC8243]. However, multilevel IS-IS needs
some extensions to support the TRILL multilevel feature. The two
most significant extensions are how TRILL switch nicknames are
managed and how distribution trees are handled [RFC8243].
There are two primary alternatives to realize TRILL multilevel
[RFC8243]. One approach, which is referred to as the "aggregated
nickname" approach, involves assigning nicknames to the areas, and
Show full document text