Browse Prior Art Database

Transparent Interconnection of Lots of Links (TRILL) Smart Endnodes (RFC8384)

IP.com Disclosure Number: IPCOM000254571D
Original Publication Date: 2018-Jul-01
Included in the Prior Art Database: 2018-Jul-12
Document File: 34 page(s) / 37K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Perlman: AUTHOR [+3]

Abstract

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".

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

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 t...