RFC 8384 on Transparent Interconnection of Lots of Links (TRILL) Smart Endnodes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.

        
        RFC 8384

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL) Smart Endnodes 
        Author:     R. Perlman, 
                    F. Hu,
                    D. Eastlake 3rd, 
                    T. Liao
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2018
        Mailbox:    radiaperlman@gmail.com, 
                    hu.fangwei@zte.com.cn, 
                    d3e3e3@gmail.com,
                    liaoting1@huawei.com
        Pages:      17
        Characters: 37374
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-smart-endnodes-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8384

        DOI:        10.17487/RFC8384

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.

This document is a product of the Transparent Interconnection of Lots of Links Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC




[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux