IS-IS Multi-Instance
RFC 6822
| Document | Type |
RFC - Proposed Standard
(December 2012; Errata)
Was draft-ietf-isis-mi (isis WG)
|
|
|---|---|---|---|
| Last updated | 2015-11-02 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6822 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Adrian Farrel | ||
| IESG note | Chris Hopps (chopps@rawdofmt.org) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) S. Previdi, Ed.
Request for Comments: 6822 L. Ginsberg
Category: Standards Track Cisco Systems
ISSN: 2070-1721 M. Shand
A. Roy
D. Ward
Cisco Systems
December 2012
IS-IS Multi-Instance
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6822.
Previdi, et al. Standards Track [Page 1]
RFC 6822 IS-IS Multi-Instance December 2012
Copyright Notice
Copyright (c) 2012 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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Previdi, et al. Standards Track [Page 2]
RFC 6822 IS-IS Multi-Instance December 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Elements Of Procedure . . . . . . . . . . . . . . . . . . . . 4
2.1. Instance Identifier TLV . . . . . . . . . . . . . . . . . 5
2.2. Instance Membership . . . . . . . . . . . . . . . . . . . 6
2.3. Use of Authentication . . . . . . . . . . . . . . . . . . 6
2.4. Adjacency Establishment . . . . . . . . . . . . . . . . . 6
2.4.1. Point-to-Point Adjacencies . . . . . . . . . . . . . . 7
2.4.2. Multi-Access Adjacencies . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . 8
2.6.1. Interoperability Issues on Broadcast Circuits . . . . 8
2.6.2. Interoperability Using Point-to-Point Circuits . . . . 9
3. Usage Guidelines . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. One-to-One Mapping between Topologies and Instances . . . 10
Show full document text