[trill] RFC 8377 on Transparent Interconnection of Lots of Links (TRILL): Multi-Topology

rfc-editor@rfc-editor.org Tue, 31 July 2018 23:04 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 16E4B130E8E; Tue, 31 Jul 2018 16:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bXPCdAmKl8mG; Tue, 31 Jul 2018 16:04:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74170130DD1; Tue, 31 Jul 2018 16:04:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 440EBB8122F; Tue, 31 Jul 2018 16:04:20 -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: <20180731230420.440EBB8122F@rfc-editor.org>
Date: Tue, 31 Jul 2018 16:04:20 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/GTRIhLr4V8yKqpiTwFo4k2kARZ4>
Subject: [trill] =?utf-8?q?RFC_8377_on_Transparent_Interconnection_of_Lot?= =?utf-8?q?s_of_Links_=28TRILL=29=3A_Multi-Topology?=
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: Tue, 31 Jul 2018 23:04:34 -0000

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

        RFC 8377

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL): Multi-Topology 
        Author:     D. Eastlake 3rd,
                    M. Zhang,
                    A. Banerjee
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2018
        Mailbox:    d3e3e3@gmail.com, 
        Pages:      20
        Characters: 43177
        Updates:    RFC 6325, RFC 7177

        I-D Tag:    draft-ietf-trill-multi-topology-06.txt

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

        DOI:        10.17487/RFC8377

This document specifies extensions to the IETF TRILL (Transparent
Interconnection of Lots of Links) protocol to support multi-topology
routing of unicast and multi-destination traffic based on IS-IS
(Intermediate System to Intermediate System) multi-topology specified
in RFC 5120.  This document updates RFCs 6325 and 7177.

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

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