RFC 6822: IS-IS Multi-Instance
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8202.
Current version: RFC 8202 — IS-IS Multi-Instance
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6822
- Published
- December 2012
- Authors
- S. Previdi; L. Ginsberg; M. Shand; A. Roy; D. Ward
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Obsoleted by:
- RFC 8202
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6823Advertising Generic Information in IS-ISCurrent
December 2012
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 6165Extensions to IS-IS for Layer-2 SystemsCurrent
April 2011
- RFC 5308Routing IPv6 with IS-ISUpdated
October 2008
- RFC 5307IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2008
- RFC 5306Restart Signaling for IS-ISObsoleted
October 2008
- RFC 5305IS-IS Extensions for Traffic EngineeringUpdated
October 2008
- RFC 5304IS-IS Cryptographic AuthenticationUpdated
October 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?