RPKI Key Management Issues
draft-vegoda-manderson-sidr-key-management-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Leo Vegoda , Terry Manderson | ||
| Last updated | 2015-04-04 (Latest revision 2014-10-01) | ||
| 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
Strong key management is central to the security of any hierarchy of cryptographic certificates. Well-defined architectural objectives will be important guides to the detailed design work needed to support the deployment of a Global Trust Anchor for the RPKI. This document identifies some of the questions that need to be addressed in the architectural guidelines for key management.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)