Extensions of Host Identity Protocol (HIP) with Hierarchical Information
draft-zhang-hip-hierarchical-parameter-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dacheng Zhang , Xiaohu Xu | ||
| Last updated | 2009-05-27 | ||
| 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 briefly introduces the benefits brought by extending the Host Identity Protocol (HIP) with hierarchical information. In addition, two hierarchical extensions of HIP are introduced. The first one aims to transport hierarchical information in a parameter of the HIP header, while the second one extends DNS resource records in order to contain hierarchical information. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)