[rfc-dist] RFC 8202 on IS-IS Multi-Instance

rfc-editor@rfc-editor.org Fri, 16 June 2017 23:48 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1010E129536 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 16:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zBxd3AFyea9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Jun 2017 16:48:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 889901286D6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Jun 2017 16:48:19 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 670F2B80DBF; Fri, 16 Jun 2017 16:48:02 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id D1AADB80DBE; Fri, 16 Jun 2017 16:48:01 -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
Message-Id: <20170616234801.D1AADB80DBE@rfc-editor.org>
Date: Fri, 16 Jun 2017 16:48:01 -0700
Subject: [rfc-dist] RFC 8202 on IS-IS Multi-Instance
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, isis-wg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8202

        Title:      IS-IS Multi-Instance 
        Author:     L. Ginsberg, 
                    S. Previdi,
                    W. Henderickx
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2017
        Mailbox:    ginsberg@cisco.com, 
                    sprevidi@cisco.com, 
                    wim.henderickx@nokia.com
        Pages:      16
        Characters: 35114
        Obsoletes:  RFC 6822

        I-D Tag:    draft-ietf-isis-mi-bis-03.txt

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

        DOI:        10.17487/RFC8202

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 obsoletes RFC 6822.

This document is a product of the IS-IS for IP Internets 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org