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

rfc-editor@rfc-editor.org Thu, 12 July 2018 06:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5248A131060; Wed, 11 Jul 2018 23:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-0FidbX6aul; Wed, 11 Jul 2018 23:33:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10245130EBC; Wed, 11 Jul 2018 23:33:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 63771B810D7; Wed, 11 Jul 2018 23:33:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, trill@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180712063353.63771B810D7@rfc-editor.org>
Date: Wed, 11 Jul 2018 23:33:53 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/JSPiCaK8K5oQKBUAJszmUwQZ5Y4>
Subject: [trill] =?utf-8?q?RFC_8384_on_Transparent_Interconnection_of_Lot?= =?utf-8?q?s_of_Links_=28TRILL=29_Smart_Endnodes?=
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 06:33:57 -0000

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