[trill] RFC 7956 on Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 Gateway

rfc-editor@rfc-editor.org Wed, 07 September 2016 20:02 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 293F612B3F8; Wed, 7 Sep 2016 13:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.13
X-Spam-Status: No, score=-104.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bUqb04gT0aoT; Wed, 7 Sep 2016 13:01:56 -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 977F712B427; Wed, 7 Sep 2016 13:01:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6698EB80B9B; Wed, 7 Sep 2016 13:01: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
Message-Id: <20160907200153.6698EB80B9B@rfc-editor.org>
Date: Wed, 7 Sep 2016 13:01:53 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/GaAe4hleuxwwsobvf03n7KelPCU>
Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org
Subject: [trill] RFC 7956 on Transparent Interconnection of Lots of Links (TRILL) Distributed Layer 3 Gateway
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 07 Sep 2016 20:02:04 -0000

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

        RFC 7956

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL) Distributed Layer 3 Gateway 
        Author:     W. Hao, Y. Li,
                    A. Qu, M. Durrani,
                    P. Sivamurugan
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    haoweiguo@huawei.com, 
        Pages:      28
        Characters: 62104
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-irb-14.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7956

The base TRILL (Transparent Interconnection of Lots of Links)
protocol provides optimal pair-wise data frame forwarding for Layer 2
intra-subnet traffic but not for Layer 3 inter-subnet traffic.  A
centralized gateway solution is typically used for Layer 3
inter-subnet traffic forwarding but has the following issues:

1. Sub-optimum forwarding paths for inter-subnet traffic.

2. A centralized gateway that may need to support a very large
number of gateway interfaces in a Data Center, one per tenant per
Data Label used by that tenant, to provide interconnect functionality
for all the Layer 2 Virtual Networks in a TRILL campus.

3. A traffic bottleneck at the gateway.

This document specifies an optional TRILL distributed gateway
solution that resolves these centralized gateway issues.

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