Generation of Unique IS-IS System Identifiers
draft-simpson-isis-ppp-unique-02
| Document | Type | Expired Internet-Draft | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2011-08-08) | ||
| Stream | ISE | ||
| Intended RFC status | Experimental | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | ISE state | (None) | |
| Consensus Boilerplate | Unknown | ||
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Telechat date | |||
| Responsible AD | Stewart Bryant | ||
| IESG note | ISE Submission | ||
| Send notices to | rfc-ise@rfc-editor.org | ||
https://www.ietf.org/archive/id/draft-simpson-isis-ppp-unique-02.txt
Abstract
The IS-IS routing protocol (Intermediate System to Intermediate System, ISO 10589) requires unique System Identifiers at the link layer. A common practice has been to use an existing IEEE 802 MAC link-layer interface identifier. When no unique MAC is available, this document specifies automatic generation of identifiers. It is fully interoperable with systems that do not support this extension. Additionally, the extension automatically resolves conflicts between System Identifiers.
Authors
William Simpson (William.Allen.Simpson@Gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)