[trill] RFC 8385 on Transparent Interconnection of Lots of Links (TRILL) Transparent Transport over MPLS

rfc-editor@rfc-editor.org Mon, 11 June 2018 17:27 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 06914126CB6; Mon, 11 Jun 2018 10:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WKmcSpz8Z4VD; Mon, 11 Jun 2018 10:27:13 -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 663EC130FF1; Mon, 11 Jun 2018 10:27:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7EE48B80EB4; Mon, 11 Jun 2018 10:27:12 -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: <20180611172712.7EE48B80EB4@rfc-editor.org>
Date: Mon, 11 Jun 2018 10:27:12 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/biZpk46q86pG-TZlpd7spsZ6ytU>
Subject: [trill] =?utf-8?q?RFC_8385_on_Transparent_Interconnection_of_Lot?= =?utf-8?q?s_of_Links_=28TRILL=29_Transparent_Transport_over_MPLS?=
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 11 Jun 2018 17:27:16 -0000

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

        RFC 8385

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL) Transparent Transport over MPLS 
        Author:     M. Umair, 
                    S. Kingston Smiler,
                    D. Eastlake 3rd, 
                    L. Yong
        Status:     Informational
        Stream:     IETF
        Date:       June 2018
        Mailbox:    mohammed.umair2@gmail.com, 
        Pages:      16
        Characters: 34248
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-transport-over-mpls-08.txt

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

        DOI:        10.17487/RFC8385

This document specifies methods to interconnect multiple TRILL
(Transparent Interconnection of Lots of Links) sites with an
intervening MPLS network using existing TRILL and VPLS (Virtual
Private LAN Service) standards.  This document addresses two problems:
1) providing connection between more than two TRILL sites that are
separated by an MPLS provider network and 2) providing a single
logical virtualized TRILL network for different tenants that are
separated by an MPLS provider network.

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

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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