Subject: [Isis-wg] FW: New Version Notification for draft-ginsberg-isis-mi-bis-00.txt

From: "Les Ginsberg (ginsberg)" <[email-masked]>
Date: Fri, 18 Dec 2015 22:55:16 +0000

Folks -

This is a proposed revision of RFC 6822 which introduces a non-backwards compatible change to the specification. It allows the use of RFC 5120 MT support in a non-zero instance with the restriction that this can be done only in ITID #0 and ITID #0 MUST be the only supported ITID for that instance.

For the existing implementations of MI that we are aware of this does not represent a real world compatibility problem. If there are other MI implementations out there for whom these changes will be problematic we need to know about them. If you are not comfortable disclosing this information publicly please feel free to contact the authors directly and/or pass information via the WG chairs.

The draft also addresses the reported Errata (https://www.rfc-editor.org/errata_search.php?rfc=6822 ) for RFC 6822.

Comments welcomed.

   Les

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Friday, December 18, 2015 2:39 PM
To: Les Ginsberg (ginsberg); Stefano Previdi (sprevidi); Wim Henderickx
Subject: New Version Notification for draft-ginsberg-isis-mi-bis-00.txt

A new version of I-D, draft-ginsberg-isis-mi-bis-00.txt has been successfully submitted by Les Ginsberg and posted to the IETF repository.

Name:		draft-ginsberg-isis-mi-bis
Revision:	00
Title:		IS-IS Multi-Instance
Document date:	2015-12-18
Group:		Individual Submission
Pages:		14
URL:            https://www.ietf.org/internet-drafts/draft-ginsberg-isis-mi-bis-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ginsberg-isis-mi-bis/
Htmlized:       https://tools.ietf.org/html/draft-ginsberg-isis-mi-bis-00

Abstract:
   This draft 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(ies) to which the PDU belongs.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat