RFC 7978 on Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header Extension

rfc-editor@rfc-editor.org Fri, 30 September 2016 21:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0A83E127058; Fri, 30 Sep 2016 14:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id en7ehrQxMdTa; Fri, 30 Sep 2016 14:47:53 -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 C6509126B6D; Fri, 30 Sep 2016 14:38:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C10EAB803D2; Fri, 30 Sep 2016 14:38:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7978 on Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header Extension
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160930213819.C10EAB803D2@rfc-editor.org>
Date: Fri, 30 Sep 2016 14:38:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MtRQT_y8bb37RjXF7ZC5M335X1s>
Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 21:47:55 -0000

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

        RFC 7978

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL): RBridge Channel Header Extension 
        Author:     D. Eastlake 3rd, M. Umair, Y. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    d3e3e3@gmail.com, 
        Pages:      25
        Characters: 54617
        Updates:    RFC 7178

        I-D Tag:    draft-ietf-trill-channel-tunnel-11.txt

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

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

The IETF TRILL (Transparent Interconnection of Lots of Links) protocol
includes an optional mechanism (specified in RFC 7178) called RBridge
Channel for the transmission of typed messages between TRILL switches
in the same campus and the transmission of such messages between TRILL
switches and end stations on the same link.  This document specifies
extensions to the RBridge Channel protocol header to support two
features as follows: (1) a standard method to tunnel payloads whose
type can be indicated by Ethertype through encapsulation in RBridge
Channel messages; and (2) a method to support security facilities for
RBridge Channel messages.  This document updates RFC 7178.

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