Transparent Interconnection of Lots of Links (TRILL) Smart Endnodes
RFC 8384
|
| Document |
Type |
|
RFC - Proposed Standard
(July 2018; No errata)
|
|
Last updated |
|
2018-07-11
|
|
Replaces |
|
draft-perlman-trill-smart-endnodes
|
|
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 8384 (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) R. Perlman
Request for Comments: 8384 Dell EMC
Category: Standards Track F. Hu
ISSN: 2070-1721 ZTE Corporation
D. Eastlake 3rd
T. Liao
Huawei Technologies
July 2018
Transparent Interconnection of Lots of Links (TRILL) Smart Endnodes
Abstract
This document addresses the problem of the size and freshness of the
endnode learning table in edge Routing Bridges (RBridges), by
allowing endnodes to volunteer for endnode learning and
encapsulation/decapsulation. Such an endnode is known as a "Smart
Endnode". Only the attached edge RBridge can distinguish a "Smart
Endnode" from a "normal endnode". The Smart Endnode uses the
nickname of the attached edge RBridge, so this solution does not
consume extra nicknames. The solution also enables endnodes that are
Fine-Grained Label (FGL) aware.
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/rfc8384.
Perlman, et al. Standards Track [Page 1]
RFC 8384 TRILL Smart Endnodes July 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. Conventions Used in This Document . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 4
4. Smart-Hello Mechanism between Smart Endnode and RBridge . . . 6
4.1. Smart-Hello Encapsulation . . . . . . . . . . . . . . . . 6
4.2. Edge RBridge's Smart-Hello . . . . . . . . . . . . . . . 8
4.3. Smart Endnode's Smart-Hello . . . . . . . . . . . . . . . 8
5. Processing Data Packets . . . . . . . . . . . . . . . . . . . 10
5.1. Data-Packet Processing for Smart Endnodes . . . . . . . . 10
5.2. Data-Packet Processing for Edge RBridge . . . . . . . . . 11
6. Multihoming Scenario . . . . . . . . . . . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 16
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
Perlman, et al. Standards Track [Page 2]
RFC 8384 TRILL Smart Endnodes July 2018
1. Introduction
The IETF TRILL (Transparent Interconnection of Lots of Links)
protocol [RFC6325] [RFC7780] provides optimal pair-wise data frame
forwarding without configuration, safe forwarding even during periods
of temporary loops, and support for multipathing of both unicast and
multicast traffic. TRILL accomplishes this by using IS-IS [IS-IS]
[RFC7176] link state routing and encapsulating traffic using a header
that includes a hop count. Devices that implement TRILL are called
"RBridges" (Routing Bridges) or "TRILL Switches".
An RBridge that attaches to endnodes is called an "edge RBridge" or
"edge TRILL Switch", whereas one that exclusively forwards
Show full document text