RFC 6165 on Extensions to IS-IS for Layer-2 Systems

rfc-editor@rfc-editor.org Thu, 14 April 2011 18:25 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfc.amsl.com
Delivered-To: ietf-announce@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 76F9DE0865; Thu, 14 Apr 2011 11:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.054
X-Spam-Level:
X-Spam-Status: No, score=-102.054 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OX4G-xEXwCb1; Thu, 14 Apr 2011 11:25:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfc.amsl.com (Postfix) with ESMTP id BB1BDE0864; Thu, 14 Apr 2011 11:25:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3F3CAE0770; Thu, 14 Apr 2011 11:25:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6165 on Extensions to IS-IS for Layer-2 Systems
From: rfc-editor@rfc-editor.org
Message-Id: <20110414182523.3F3CAE0770@rfc-editor.org>
Date: Thu, 14 Apr 2011 11:25:23 -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: Thu, 14 Apr 2011 18:25:24 -0000

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

        
        RFC 6165

        Title:      Extensions to IS-IS for Layer-2 
                    Systems 
        Author:     A. Banerjee, D. Ward
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2011
        Mailbox:    ayabaner@cisco.com, 
                    dward@juniper.net
        Pages:      7
        Characters: 12266
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-layer2-11.txt

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

This document specifies the Intermediate System to Intermediate
System (IS-IS) extensions necessary to support link state routing for
any protocols running directly over Layer-2.  While supporting this
concept involves several pieces, this document only describes
extensions to IS-IS.  Furthermore, the Type, Length, Value pairs
(TLVs) described in this document are generic Layer-2 additions, and
specific ones as needed are defined in the IS-IS technology-specific
extensions.  We leave it to the systems using these IS-IS extensions
to explain how the information carried in IS-IS is used.  [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