Deployment of Reconsidered Validation in the Resource Public Key Infrastructure (RPKI)
draft-va-sidrops-deploy-reconsidered-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | George G. Michaelson , Tim Bruijnzeels | ||
| Last updated | 2019-09-08 (Latest revision 2019-03-07) | ||
| 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 defines a deployment model for reconsidered validation [RFC8360] in the Resource Public Key Infrastructure (RPKI). It stipulates that Relying Parties in the RPKI MUST support reconsidered validation by 1 July TBD-Year, and that Certificate Authorities MAY use the reconsidered validation OIDs in CA certificates that they issue from this date. Furthermore Certificate Authorities should monitor whether the set of resources in CA certificate they receive has shrunk, and make adjustments in the CA certificates and/or other RPKI objects when appropriate.
Authors
George G. Michaelson
Tim Bruijnzeels
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)