Using DHCP to Manage Node and Ring SID Assignment
draft-kompella-spring-dhcp-00

Document Type Expired Internet-Draft (individual)
Authors Kireeti Kompella  , Ron Bonica 
Last updated 2020-01-08 (latest revision 2019-07-07)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kompella-spring-dhcp-00.txt

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

Kireeti Kompella (kireeti.kompella@gmail.com)
Ron Bonica (rbonica@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)