Change Publication Server used by an RPKI CA
draft-timbru-sidrops-change-pubserver-01
| Document | Type |
Replaced Internet-Draft
(sidrops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tim Bruijnzeels , Martin Hoffmann , Koen van Hove | ||
| Last updated | 2025-11-02 (Latest revision 2025-09-18) | ||
| Replaced by | draft-ietf-sidrops-change-pubserver | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sidrops-change-pubserver | |
| Consensus boilerplate | Unknown | ||
| 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 outlines how an RPKI CA can migrate from one RFC 8181 Publication Server to another. The process is similar to the RPKI CA Key Rollover process defined in RFC 6489, except that in this case a new location is used for the new key.
Authors
Tim Bruijnzeels
Martin Hoffmann
Koen van Hove
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)