Hierarchical HITs for HIPv2
draft-moskowitz-hip-hierarchical-hit-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Robert Moskowitz , Stuart W. Card , Adam Wiethuechter | ||
Last updated | 2020-11-16 (Latest revision 2020-05-13) | ||
Replaces | draft-moskowitz-hierarchical-hip | ||
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
This document describes using a hierarchical HIT to facilitate large deployments of managed devices. Hierarchical HITs differ from HIPv2 flat HITs by only using 64 bits for mapping the Host Identity, freeing 32 bits to bind in a hierarchy of Registering Entities that provide services to the consumers of hierarchical HITs.
Authors
Robert Moskowitz
Stuart W. Card
Adam Wiethuechter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)