<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-rpki-erik-protocol" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rpki-erik-protocol-05">
   <front>
      <title>The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI)</title>
      <author initials="J." surname="Snijders" fullname="Job Snijders">
         <organization>BSD Software Development</organization>
      </author>
      <author initials="T." surname="Bruijnzeels" fullname="Tim Bruijnzeels">
         <organization>RIPE NCC</organization>
      </author>
      <author initials="T." surname="Harrison" fullname="Tom Harrison">
         <organization>APNIC</organization>
      </author>
      <author initials="W." surname="Ohgai" fullname="Wataru Ohgai">
         <organization>JPNIC</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   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&#x27;s design is intended to be efficient, fast, easy to
   implement, and robust in the face of partitions or faults in the
   network.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sidrops-rpki-erik-protocol-05" />
   
</reference>
