RFC 6326 on Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS

rfc-editor@rfc-editor.org Fri, 22 July 2011 16:17 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 776A721F86B9; Fri, 22 Jul 2011 09:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.177
X-Spam-Level:
X-Spam-Status: No, score=-102.177 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVycq6ll+4jG; Fri, 22 Jul 2011 09:17:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id E479D21F8519; Fri, 22 Jul 2011 09:17:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 56CB498C535; Fri, 22 Jul 2011 09:06:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6326 on Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
From: rfc-editor@rfc-editor.org
Message-Id: <20110722160625.56CB498C535@rfc-editor.org>
Date: Fri, 22 Jul 2011 09:06:25 -0700
Cc: isis-wg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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, 22 Jul 2011 16:17:25 -0000

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

        
        RFC 6326

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL) Use of IS-IS 
        Author:     D. Eastlake, A. Banerjee,
                    D. Dutt, R. Perlman,
                    A. Ghanwani
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2011
        Mailbox:    d3e3e3@gmail.com, 
                    ayabaner@cisco.com, 
                    ddutt@cisco.com,  Radia@alum.mit.edu, 
                    anoop@alumni.duke.edu
        Pages:      25
        Characters: 51059
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-trill-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6326.txt

The IETF has standardized the Transparent Interconnection of Lots of Links
(TRILL) protocol, which provides transparent Layer 2 forwarding using
encapsulation with a hop count and IS-IS link state routing. This document
specifies the data formats and code points for the IS-IS extensions to
support TRILL.  [STANDARDS-TRACK]

This document is a product of the IS-IS for IP Internets Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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