RPKI Publication Protocol Version 2
draft-timbru-sidrops-rpki-publication-v2-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tim Bruijnzeels | ||
| Last updated | 2023-04-27 (Latest revision 2022-10-24) | ||
| 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
The RPKI Publication Protocol first described in RFC 8181 has worked very well. That said, as it turns out, there are a number of requirements emerging from operational experience which cannot be supported by the current protocol. In particular, identity key roll overs, support for publication quota and stricter verification of content by the server. This document is an early write-up with the following goals: (1) support discussions about requirements for additional work and (2) explore a possible version 2 with solutions to meet those requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)