IS-IS Multi-Instance
draft-ginsberg-isis-mi-bis-01
| Document | Type |
Replaced Internet-Draft
(isis WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Les Ginsberg , Stefano Previdi , Wim Henderickx | ||
| Last updated | 2016-04-22 (Latest revision 2016-04-20) | ||
| Replaced by | draft-ietf-isis-mi-bis | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-isis-mi-bis | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | "Christian Hopps" <chopps@chopps.org> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Les Ginsberg
Stefano Previdi
Wim Henderickx
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)