@techreport{ietf-sidrops-rpki-erik-protocol-07,
    number =    {draft-ietf-sidrops-rpki-erik-protocol-07},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpki-erik-protocol/07/},
    author =    {Job Snijders and Tim Bruijnzeels and Tom Harrison and Wataru Ohgai},
    title =     {{The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI)}},
    pagetotal = 36,
    year =      2026,
    month =     aug,
    day =       16,
    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. The protocol is used to interact with Erik Relays, a new intermediary layer in the RPKI supply chain that exists between the Repository Publication Point and Relying Parties, enabling better scalability. 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.},
}