Algorithm Agility Procedure for RPKI.
draft-rgaglian-sidr-algorithm-agility-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Roque Gagliano , Stephen Kent , Sean Turner | ||
| Last updated | 2012-01-25 (Latest revision 2010-10-18) | ||
| Replaced by | draft-ietf-sidr-algorithm-agility | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sidr-algorithm-agility | |
| 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 specifies the process that Certificate Authorities (CAs) and Relying Parties (RP) participating in the Resource Public Key Infrastructure (RPKI) will need to follow to transition to a new (and probably cryptographically stronger) algorithm set. The process is expected to be completed in a time scale of months or years. Consequently, no emergency transition is specified.
Authors
Roque Gagliano
Stephen Kent
Sean Turner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)