IS-IS Multi-Instance
draft-ietf-isis-mi-bis-03

Document Type Active Internet-Draft (isis WG)
Last updated 2017-05-05 (latest revision 2017-04-17)
Replaces draft-ginsberg-isis-mi-bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Christian Hopps
Shepherd write-up Show (last changed 2017-03-01)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to "Christian Hopps" <chopps@chopps.org>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Networking Working Group                                     L. Ginsberg
Internet-Draft                                                S. Previdi
Obsoletes: 6822 (if approved)                              Cisco Systems
Intended status: Standards Track                           W. Henderickx
Expires: October 19, 2017                                          Nokia
                                                          April 17, 2017

                          IS-IS Multi-Instance
                     draft-ietf-isis-mi-bis-03.txt

Abstract

   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 if approved.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 19, 2017.

Ginsberg, et al.        Expires October 19, 2017                [Page 1]
Internet-Draft         draft-iietf-isis-mi-bis.txt            April 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Elements Of Procedure . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Instance Identifier TLV . . . . . . . . . . . . . . . . .   4
     2.2.  Instance Membership . . . . . . . . . . . . . . . . . . .   6
     2.3.  Use of Authentication . . . . . . . . . . . . . . . . . .   6
     2.4.  Adjacency Establishment . . . . . . . . . . . . . . . . .   6
       2.4.1.  Point-to-Point Adjacencies  . . . . . . . . . . . . .   6
       2.4.2.  Multi-Access Adjacencies  . . . . . . . . . . . . . .   6
     2.5.  Update Process Operation  . . . . . . . . . . . . . . . .   7
       2.5.1.  Update Process Operation on Point-to-Point Circuits .   7
       2.5.2.  Update Process Operation on Broadcast Circuits  . . .   7
     2.6.  Interoperability Considerations . . . . . . . . . . . . .   7
       2.6.1.  Interoperability Issues on Broadcast Circuits . . . .   7
       2.6.2.  Interoperability Using Point-to-Point Circuits  . . .   8
   3.  Usage Guidelines  . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  One-to-One Mapping between Topologies and Instances . . .   9
     3.2.  Many-to-One Mapping between Topologies and Instances  . .  10
     3.3.  Considerations for the Number of Instances  . . . . . . .  10
   4.  Relationship to M-ISIS  . . . . . . . . . . . . . . . . . . .  11
   5.  Graceful Restart Interactions . . . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text