The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI)
draft-spaghetti-sidrops-rpki-erik-protocol-04
| Document | Type |
Replaced Internet-Draft
(sidrops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Job Snijders , Tim Bruijnzeels , Tom Harrison , Wataru Ohgai | ||
| Last updated | 2025-12-01 (Latest revision 2025-10-15) | ||
| Replaced by | draft-ietf-sidrops-rpki-erik-protocol | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
Mailing list discussion |
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sidrops-rpki-erik-protocol | |
| 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 specifies the Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI). Erik Synchronization can be characterized as a data replication system using Merkle trees, a content-addressable naming scheme, concurrency control using monotonically increasing sequence numbers, and HTTP transport. Relying Parties can combine information retrieved via Erik Synchronization with other RPKI transport protocols. The protocol's design is intended to be efficient, fast, easy to implement, and robust in the face of partitions or faults in the network.
Authors
Job Snijders
Tim Bruijnzeels
Tom Harrison
Wataru Ohgai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)