Host Identifier Revocation in HIP
draft-irtf-hiprg-revocation-05
| Document | Type |
Expired Internet-Draft
(hiprg RG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dacheng Zhang , Dmitriy Kuptsov , Sean Shen | ||
| Last updated | 2012-09-10 (Latest revision 2012-03-09) | ||
| RFC stream | Internet Research Task Force (IRTF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | IRTF state | (None) | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (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 mainly analyzes the key revocation issue with host identifiers (HIs) in the Host Identity Protocol (HIP). Generally, key revocation is an important functionality of key management systems; it is concerned with the issues of removing cryptographic keys from operational use when they are not secure or not secure enough any more. This functionality is particularly important for the security systems expected to execute for long periods. This document also attempts to investigate several issues that a designer of HI revocation mechanisms need to carefully consider.
Authors
Dacheng Zhang
Dmitriy Kuptsov
Sean Shen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)