[Isis-wg] RFC 6822 on IS-IS Multi-Instance

rfc-editor@rfc-editor.org Sat, 22 December 2012 01:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA1721E8084; Fri, 21 Dec 2012 17:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.915
X-Spam-Level:
X-Spam-Status: No, score=-101.915 tagged_above=-999 required=5 tests=[AWL=0.085, 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 n40Zf6LJFGmF; Fri, 21 Dec 2012 17:40:33 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 0586521E8083; Fri, 21 Dec 2012 17:40:33 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 80EB1B1E00A; Fri, 21 Dec 2012 17:31:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121222013115.80EB1B1E00A@rfc-editor.org>
Date: Fri, 21 Dec 2012 17:31:15 -0800
Cc: isis-wg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Isis-wg] RFC 6822 on IS-IS Multi-Instance
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Dec 2012 01:40:33 -0000

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

        
        RFC 6822

        Title:      IS-IS Multi-Instance 
        Author:     S. Previdi, Ed.,
                    L. Ginsberg, M. Shand,
                    A. Roy, D. Ward
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2012
        Mailbox:    sprevidi@cisco.com, 
                    ginsberg@cisco.com, 
                    imc.shand@gmail.com,
                    akr@cisco.com, 
                    wardd@cisco.com
        Pages:      14
        Characters: 30254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-mi-08.txt

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

This document describes a mechanism that allows a single router to
share one or more circuits among multiple Intermediate System to
Intermediate System (IS-IS) routing protocol instances.

Multiple instances allow the isolation of resources associated with
each instance.  Routers will form instance-specific adjacencies.
Each instance can support multiple topologies.  Each topology has a
unique Link State Database (LSDB).  Each Protocol Data Unit (PDU)
will contain a new Type-Length-Value (TLV) identifying the instance
and the topology (or topologies) to which the PDU belongs.

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