Using DHCP to Manage Node and Ring SID Assignment
draft-kompella-spring-dhcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kireeti Kompella , Ron Bonica | ||
| Last updated | 2020-01-08 (Latest revision 2019-07-07) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Node and ring segment identifiers (SIDs) assignements in a particular domain (such as an IGP area) must follow certain rules: they must be allocated from a configured set of SID blocks; they must be unique; and the values should be sticky, i.e., the same value(s) should be assigned to a node should its assignment expire (as might happen if the node resets). This memo suggests the use of the Dynamic Host Configuration Protocol to handle such assignments.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)