[trill] RFC 8249 on Transparent Interconnection of Lots of Links (TRILL): MTU Negotiation

rfc-editor@rfc-editor.org Sat, 30 September 2017 22:47 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 C78AA1342DF; Sat, 30 Sep 2017 15:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9f1HsM13F5T3; Sat, 30 Sep 2017 15:47:20 -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 742201342DD; Sat, 30 Sep 2017 15:47:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E5291B80DEB; Sat, 30 Sep 2017 15:47:19 -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
Message-Id: <20170930224719.E5291B80DEB@rfc-editor.org>
Date: Sat, 30 Sep 2017 15:47:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/5ywIXK91qqVJGrqqzLgDx9AzYFM>
Subject: [trill] RFC 8249 on Transparent Interconnection of Lots of Links (TRILL): MTU Negotiation
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 30 Sep 2017 22:47:22 -0000

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

        RFC 8249

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL): MTU Negotiation 
        Author:     M. Zhang, 
                    X. Zhang,
                    D. Eastlake 3rd, 
                    R. Perlman,
                    S. Chatterjee
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2017
        Mailbox:    zhangmingui@huawei.com, 
        Pages:      15
        Characters: 32423
        Updates:    RFC 6325, RFC 7177, RFC 7780

        I-D Tag:    draft-ietf-trill-mtu-negotiation-08.txt

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

        DOI:        10.17487/RFC8249

The base IETF TRILL (Transparent Interconnection of Lots of Links)
protocol has a TRILL campus-wide MTU feature, specified in RFCs 6325
and 7177, that assures that link-state changes can be successfully
flooded throughout the campus while being able to take advantage of a
campus-wide capability to support jumbo packets.  This document
specifies recommended updates to that MTU feature to take advantage,
for appropriate link-local packets, of link-local MTUs that exceed
the TRILL campus MTU.  In addition, it specifies an efficient
algorithm for local MTU testing.  This document updates RFCs 6325,
7177, and 7780.

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