Generation of Unique IS-IS System Identifiers
draft-simpson-isis-ppp-unique-02
Document | Type |
Expired Internet-Draft
(rtg)
Expired & archived
|
|
---|---|---|---|
Author | William A. Simpson | ||
Last updated | 2015-10-14 (Latest revision 2011-08-08) | ||
RFC stream | Independent Submission | ||
Intended RFC status | Experimental | ||
Formats | |||
Stream | ISE state | (None) | |
Consensus boilerplate | Unknown | ||
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Telechat date | (None) | ||
Responsible AD | Stewart Bryant | ||
IESG note | |||
Send notices to | rfc-ise@rfc-editor.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)