SIDROPS J. Snijders Internet-Draft BSD Intended status: Standards Track T. Bruijnzeels Expires: 20 May 2027 RIPE NCC T. Harrison APNIC W. Ohgai JPNIC 16 November 2026 The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI) draft-ietf-sidrops-rpki-erik-protocol-08 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. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 May 2027. Snijders, et al. Expires 20 May 2027 [Page 1] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.3. Related Work . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Glossary . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Informal Overview . . . . . . . . . . . . . . . . . . . . . . 5 3. Erik Synchronization Data Structure Definitions . . . . . . . 6 3.1. General Syntax . . . . . . . . . . . . . . . . . . . . . 8 3.1.1. contentType . . . . . . . . . . . . . . . . . . . . . 8 3.1.2. content . . . . . . . . . . . . . . . . . . . . . . . 8 3.2. ErikIndex . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2.1. The version field . . . . . . . . . . . . . . . . . . 8 3.2.2. The indexScope field . . . . . . . . . . . . . . . . 9 3.2.3. The indexTime field . . . . . . . . . . . . . . . . . 9 3.2.4. The hashAlg field . . . . . . . . . . . . . . . . . . 9 3.2.5. The partitionList field . . . . . . . . . . . . . . . 9 3.3. ErikPartition . . . . . . . . . . . . . . . . . . . . . . 10 3.3.1. The version field . . . . . . . . . . . . . . . . . . 10 3.3.2. The partitionTime field . . . . . . . . . . . . . . . 10 3.3.3. The hashAlg field . . . . . . . . . . . . . . . . . . 10 3.3.4. The manifestList field . . . . . . . . . . . . . . . 10 3.4. ErikSegmentIndex . . . . . . . . . . . . . . . . . . . . 11 3.4.1. The version field . . . . . . . . . . . . . . . . . . 11 3.4.2. The segmentScope field . . . . . . . . . . . . . . . 11 3.4.3. the segmentIndexTime field . . . . . . . . . . . . . 11 3.4.4. the hashAlg field . . . . . . . . . . . . . . . . . . 12 3.4.5. the segmentList field . . . . . . . . . . . . . . . . 12 4. Client-side Processing . . . . . . . . . . . . . . . . . . . 12 5. Querying an Erik Relay . . . . . . . . . . . . . . . . . . . 13 5.1. Fetching ErikIndex objects . . . . . . . . . . . . . . . 13 5.2. Fetching objects by hash . . . . . . . . . . . . . . . . 14 6. Prefetching Objects in Bulk . . . . . . . . . . . . . . . . . 14 Snijders, et al. Expires 20 May 2027 [Page 2] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 6.1. General Structure of Prefetch Responses . . . . . . . . . 14 6.2. Prefetching Using Snapshot Buffers . . . . . . . . . . . 15 6.3. Prefetching Using Segment Buffers . . . . . . . . . . . . 15 6.3.1. Segment Discovery . . . . . . . . . . . . . . . . . . 15 6.3.2. Segment Buffers . . . . . . . . . . . . . . . . . . . 16 7. Transport Error Detection and Handling . . . . . . . . . . . 16 8. Setting Up an Erik Relay . . . . . . . . . . . . . . . . . . 16 9. Operational Considerations . . . . . . . . . . . . . . . . . 17 9.1. Scaling considerations . . . . . . . . . . . . . . . . . 17 9.2. HTTP Version Recommendations . . . . . . . . . . . . . . 17 9.3. HTTP Compression . . . . . . . . . . . . . . . . . . . . 17 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 11.1. S/MIME Module Identifier . . . . . . . . . . . . . . . . 18 11.2. SMI Security for S/MIME CMS Content Type . . . . . . . . 18 11.3. Well-Known URI . . . . . . . . . . . . . . . . . . . . . 19 11.4. Media Types . . . . . . . . . . . . . . . . . . . . . . 19 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 12.1. Normative References . . . . . . . . . . . . . . . . . . 21 12.2. Informative References . . . . . . . . . . . . . . . . . 22 Appendix A. Implementation status . . . . . . . . . . . . . . . 24 A.1. Experimental Erik Relay Services . . . . . . . . . . . . 24 A.2. Software . . . . . . . . . . . . . . . . . . . . . . . . 24 Appendix B. Example objects . . . . . . . . . . . . . . . . . . 25 B.1. Example ErikIndex . . . . . . . . . . . . . . . . . . . . 25 B.2. Example ErikPartition . . . . . . . . . . . . . . . . . . 29 B.3. Example ErikSegmentIndex . . . . . . . . . . . . . . . . 35 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 1. Introduction This document specifies the Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI) [RFC6480]. Erik Synchronization can be characterized as a data replication system using Merkle trees [M1987], a content-addressable naming scheme [RFC6920], concurrency control using monotonically increasing sequence numbers [RFC0677], and HTTP transport [RFC9110]. 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 ([RFC5781] and [RFC8182]). The protocol's design is intended to be efficient, fast, easy to implement [RFC1925], and robust in the face of partitions or faults in the network. Snijders, et al. Expires 20 May 2027 [Page 3] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 1.1. Background The notion of cache-to-cache data replication of unvalidated data was documented in Section 3 of [RFC7115]. | Validated caches may also be created and maintained from other | validated caches. Network operators SHOULD take maximum advantage | of this feature to minimize load on the global distributed RPKI | database. Of course, the recipient relying parties should re- | validate the data. | | -- RFC7115, section 3 Historic records show that experiments have been performed in this space using, for example, peer-to-peer file sharing technology (see [P2P]), but no standardised and widely-deployed mechanism for cache- to-cache replication emerged since then. The authors hope that the Erik Synchronization protocol might be suitable to fill this gap and improve propagation speed of validly signed repository data as well as help reduce load on the global RPKI. 1.2. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 1.3. Related Work The reader is assumed to be familiar with the terms and concepts described in "Maintenance of duplicate databases" [RFC0677], "An Infrastructure to Support Secure Internet Routing" [RFC6480], "The RPKI Repository Delta Protocol (RRDP)" [RFC8182], "Manifests for the Resource Public Key Infrastructure (RPKI)" [RFC9286], "A Digital Signature Based on a Conventional Encryption Function" [M1987]. 1.4. Glossary This section describes the terminology and abbreviations used in this document. Though the definitions might not be clear on a first read, later on the terms will be introduced with more detail. Erik relay An intermediate between CA publication repositories and Relying Parties. FQDN The fully qualified domain name of an RPKI repository instance Snijders, et al. Expires 20 May 2027 [Page 4] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 referenced by the mandatory rsync URI in an end-entity certificate's Subject Information Access (SIA) extension's id-ad- signedObject accessDescription. Hash A message digest calculated for an object using the SHA-256 algorithm. ErikIndex The relay's Merkle root for a given FQDN. An ErikIndex is an ordered listing of ErikPartition object hashes. ErikPartition An ordered listing of the manifest objects' hashes, manifestNumber values, thisUpdate values, and their certificates' SIA extension values. ErikSegmentIndex An ordered listing of the relay's segment buffers and associated ErikIndex objects object hashes. 2. Informal Overview Erik Synchronisation is an architecture to reliably distribute RPKI repository data from cache to cache using so-called Erik relays. Relays maintain a validated cache themselves and can be clients of other relays. While this property suggests that a group of relays should converge to the exact same state, the distributed nature of the RPKI prevents relays from achieving strict synchronization. In this synchronization protocol, Merkle trees are used to determine whether differences exist between client and relay. Merkle trees are hierarchical data structures: the hash value of each node is computed recursively by hashing the concatenated hash values of the node's children. The hash of the ErikIndex represents the entire dataset related to a given FQDN. If the ErikIndex hash is not the same between two replicas, the relay provides the client with 256 ErikPartition hashes to identify out-of-sync or missing objects referenced in particular partitions. Sequence numbers are then used to determine whether these differences are relevant enough for the client to fetch. All data, except for ErikIndex objects, is fetched using static addresses derived from object hashes. This approach reduces unnecessary data transfer between caches which contain mostly similar data. The client starts by making an inventory of its local state and then querying an Erik relay for the relay's current ErikIndex for a given FQDN. If the ErikIndex is different compared to the previous run (or compared to the ErikIndex derived from locally cached objects). After having acquired the current ErikIndex, clients can determine which ErikPartitions need to be fetched. The client then can compare the _manifestNumber_ sequence number and _thisUpdate_ for each Snijders, et al. Expires 20 May 2027 [Page 5] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 manifest listed in the ErikPartition, and proceed to fetch (purportedly) newer versions of manifests of interest. Whenever a relay has manifests with a lower sequence number on offer, the client can ignore those. The client now has sufficient information to proceed to fetch any missing Certificates, Signed objects, and CRLs. With the information contained within manifests, clients can fetch addressed by content (by hash) and store by name (or some other scheme). 3. Erik Synchronization Data Structure Definitions The messages used in this protocol to construct and determine synchronization states are encoded following Distinguished Encoding Rules (DER) [X.690]. ErikIndex, ErikPartition, and ErikSegmentIndex objects are formally defined as follows: RpkiErikSynchronization-2025 { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) smime(16) mod(0) id-mod-rpkiErikSynchronization-2025(TBD) } DEFINITIONS EXPLICIT TAGS ::= BEGIN -- EXPORTS ALL -- IMPORTS CONTENT-TYPE, ContentSet, Digest, DigestAlgorithmIdentifier FROM CryptographicMessageSyntax-2010 -- in [RFC6268] { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) modules(0) id-mod-cms-2009(58) } AccessDescription, KeyIdentifier FROM PKIX1Implicit-2009 -- in [RFC5912] { iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-mod-pkix1-implicit-02(59) } ; ContentInfo ::= SEQUENCE { contentType CONTENT-TYPE.&id({ContentSet}), content [0] EXPLICIT CONTENT-TYPE.&Type({ContentSet}{@contentType}) } ContentSet CONTENT-TYPE ::= { Snijders, et al. Expires 20 May 2027 [Page 6] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 CryptographicMessageSyntax-2010.ContentSet | ct-rpkiErikIndex | ct-rpkiErikPartition | ct-rpkiErikSegmentIndex, ... } ct-rpkiErikIndex CONTENT-TYPE ::= { TYPE ErikIndex IDENTIFIED BY id-ct-rpkiErikIndex } id-ct-rpkiErikIndex OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) id-smime(16) id-ct(1) erikIndex(55) } ct-rpkiErikPartition CONTENT-TYPE ::= { TYPE ErikPartition IDENTIFIED BY id-ct-rpkiErikPartition } id-ct-rpkiErikPartition OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) id-smime(16) id-ct(1) erikPartition(56) } ct-rpkiErikSegmentIndex CONTENT-TYPE ::= { TYPE ErikSegmentIndex IDENTIFIED BY id-ct-rpkiErikSegmentIndex } id-ct-rpkiErikSegmentIndex OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) id-smime(16) id-ct(1) erikSegmentIndex(59) } ErikIndex ::= SEQUENCE { version [0] INTEGER DEFAULT 0, indexScope IA5String, indexTime GeneralizedTime, hashAlg DigestAlgorithmIdentifier, partitionList SEQUENCE (SIZE(1..ub-Partitions)) OF PartitionRef } ub-Partitions INTEGER ::= 256 PartitionRef ::= SEQUENCE { hash Digest, size INTEGER (100..MAX) } ErikPartition ::= SEQUENCE { version [0] INTEGER DEFAULT 0, partitionTime GeneralizedTime, hashAlg DigestAlgorithmIdentifier, manifestList SEQUENCE (SIZE(1..MAX)) OF ManifestRef } ManifestRef ::= SEQUENCE { hash Digest, size INTEGER (0..MAX), aki KeyIdentifier, Snijders, et al. Expires 20 May 2027 [Page 7] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 manifestNumber INTEGER (0..MAX), thisUpdate GeneralizedTime, locations SEQUENCE (SIZE(1..MAX)) OF AccessDescription } ErikSegmentIndex ::= SEQUENCE { version [0] INTEGER DEFAULT 0, segmentScope IA5String, segmentIndexTime GeneralizedTime, hashAlg DigestAlgorithmIdentifier, segmentList SEQUENCE (SIZE(1..ub-Segments)) OF SegmentRef } ub-Segments INTEGER ::= 36 SegmentRef ::= SEQUENCE { segment GeneralizedTime, index Digest } END 3.1. General Syntax At the top level the content of an Erik object is an instance of ContentInfo. 3.1.1. contentType The contentType is an OID specifying the type of payload in the object, in this profile either id-ct-rpkiErikIndex, id-ct- rpkiErikPartition, or id-ct-rpkiErikSegmentIndex. 3.1.2. content The content field contains an instance of ErikIndex, ErikPartition, or ErikSegmentIndex. 3.2. ErikIndex An ErikIndex represents all current manifest objects available under a given FQDN and thus the complete state of the repository as it is known to the relay. See Appendix B.1 for an example ErikIndex object. 3.2.1. The version field The version number of the ErikIndex object MUST be 0. Snijders, et al. Expires 20 May 2027 [Page 8] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 3.2.2. The indexScope field The indexScope field contains the fully qualified domain name of the Signed Object location of the manifests referenced through this particular ErikIndex. The FQDN MUST be in the "preferred name syntax", as specified by Section 3.5 of [RFC1034] and modified by Section 2.1 of [RFC1123]. 3.2.3. The indexTime field The indexTime is the most recent partitionTime value among the ErikPartitions referenced from the ErikIndex at hand. Use of the most recent partitionTime value (rather than the local system's notion of "now") provides idempotency for distributed system implementations. The field's value is a rough indication when the ErikIndex was generated and can be used for troubleshooting and measurement purposes. For the purposes of this profile, GeneralizedTime values MUST be expressed in UTC (Zulu) and MUST include seconds (i.e., times are YYYYMMDDHHMMSSZ), even where the number of seconds is zero. GeneralizedTime values MUST NOT include fractional seconds. See Section 4.1.2.5.2 of [RFC5280]. 3.2.4. The hashAlg field This field contains the OID of the hash algorithm used to hash the ErikPartitions. The hash algorithm used MUST conform to the RPKI Algorithms and Key Size Profile specification [RFC7935]. 3.2.5. The partitionList field This field is a sequence of PartitionRef instances. There is one PartitionRef for each current ErikPartition. Each PartitionRef is a tuple consisting of the hash of the partition object and the size of the partition object. The fixed maximum size of the partitionList of 256 partitions scales efficiently because partitions track aggregate Manifest objects rather than tracking individual, separate RPKI objects. Information elements are unique with respect to one another and sorted in ascending order of the hash. Snijders, et al. Expires 20 May 2027 [Page 9] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 3.3. ErikPartition An ErikPartition represents the set of manifest objects under a given FQDN which have the same first octet of the Authority Key Identifier (AKI) in common with each other. Each ErikPartition is an ordered listing of ManifestRef instances which contain the manifest objects' hashes, object sizes, AKI, manifestNumber values, thisUpdate values, and their respective end-entity certificates' SIA extension values. Using the first octet of the AKI as the partition key facilitates even and deterministic distribution of ManifestRefs across ErikPartitions. See Appendix B.2 for an example ErikPartition object. 3.3.1. The version field The version number of the ErikPartition object MUST be 0. 3.3.2. The partitionTime field The partitionTime is the most recent thisUpdate value among the manifests referenced from the ErikPartition at hand. Use of the most recent manifest thisUpdate value (rather than the local system's notion of "now") provides idempotency for distributed system implementations. The field's value is a rough indication when the ErikPartition was generated and can be used for troubleshooting and measurement purposes. For the purposes of this profile, GeneralizedTime values MUST be expressed in UTC (Zulu) and MUST include seconds (i.e., times are YYYYMMDDHHMMSSZ), even where the number of seconds is zero. GeneralizedTime values MUST NOT include fractional seconds. See Section 4.1.2.5.2 of [RFC5280]. 3.3.3. The hashAlg field This field contains the OID of the hash algorithm used to hash the manifest objects referenced in this ErikPartition. The hash algorithm used MUST conform to the RPKI Algorithms and Key Size Profile specification [RFC7935]. 3.3.4. The manifestList field This field is a sequence of ManifestRef instances. There is one ManifestRef for each current manifest. A manifest is nominally current until the time specified in nextUpdate or until a manifest is issued with a greater manifestNumber, whichever comes first (see Section 4.2.1 of [RFC9286]). Snijders, et al. Expires 20 May 2027 [Page 10] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 A ManifestRef is a structure consisting of the hash of the manifest object, the size of the manifest object, the manifest issuer's key identifier, the manifestNumber, and the thisUpdate contained within the object, and a sequence of AccessDescription instances from the manifest's End-Entity certificate's Subject Information Access extension. Information elements are unique with respect to one another and sorted in ascending order of the hash. 3.4. ErikSegmentIndex An ErikSegmentIndex represents segments that contain RPKI objects that a relay discovered in a short time window. See Section 6.3 on how these are used and Appendix B.3 for an example ErikSegmentIndex object. 3.4.1. The version field The version number of the ErikSegmentIndex object MUST be 0. 3.4.2. The segmentScope field The segmentScope field contains the fully qualified domain name of the Signed Object locations referenced through this particular ErikSegmentIndex. The FQDN MUST be in the "preferred name syntax", as specified by Section 3.5 of [RFC1034] and modified by Section 2.1 of [RFC1123]. 3.4.3. the segmentIndexTime field The segmentIndexTime is the most recent partitionTime value among the ErikPartitions contained within the segments referenced from the ErikSegmentIndex at hand. The field's value is a rough indication when the last segment was generated and can be used for troubleshooting and measurement purposes. For the purposes of this profile, GeneralizedTime values MUST be expressed in UTC (Zulu) and MUST include seconds (i.e., times are YYYYMMDDHHMMSSZ), even where the number of seconds is zero. GeneralizedTime values MUST NOT include fractional seconds. See Section 4.1.2.5.2 of [RFC5280]. Snijders, et al. Expires 20 May 2027 [Page 11] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 3.4.4. the hashAlg field This field contains the OID of the hash algorithm used to hash latest ErikIndex appended to a given segment. The hash algorithm used MUST conform to the RPKI Algorithms and Key Size Profile specification [RFC7935]. 3.4.5. the segmentList field This field is a sequence of SegmentRef instances. There is one SegmentRef for each current segment. A SegmentRef is a SEQUENCE consisting of a segment identifier and a hash. The segment identifier is expressed as a GeneralizedTime and indicates the moment in time the segment was initialized. The hash in the index field is the message digest calculated over the last ErikIndex associated with the segment. Information elements are unique with respect to one another and sorted in ascending order of the segment identifier. 4. Client-side Processing During top-down RPKI certificate validation, clients recursively determine the FQDNs for which ErikIndex objects need to be acquired. For example, when processing a CA certificate, a client can derive the FQDN from the host component of the rsync URI in the certificate's id-ad-rpkiManifest AccessDescription. If the FQDN has not yet been processed, the client proceeds with Erik synchronization for that FQDN as described below. For each such FQDN, clients acquire and process an ErikIndex, which represents the relay's current Merkle tree head for a given FQDN. A client MUST verify the requested FQDN exactly matches the indexScope value in the ErikIndex, and if not proceed to use a different relay. Then, clients can decide whether or not to fetch ErikPartition objects listed on the ErikIndex, for instance, by checking whether the object associated with the hash was already fetched at some point in the client's past. Before using a ErikPartition, the client MUST verify that all URIs in the accessLocations in the id-ad-signedObject accessMethod instances in the ErikPartition are encompassed in the requested indexScope. A client can then decide whether or not to fetch a given manifest object, by comparing the manifestNumber and thisUpdate with what's locally cached and what's offered by the remote relay. Snijders, et al. Expires 20 May 2027 [Page 12] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 A URI is encompassed by an indexScope if, after URI parsing and DNS name normalization, the URI host component is exactly equal to the indexScope value. Comparisons are case-insensitive. A trailing root label MUST NOT be present in an indexScope. Implementations MUST NOT use substring or suffix matching. A client can compute which products listed in the manifest's fileList need to be fetched from one relay or another in order to achieve a successful fetch. A client MUST verify that the URI in the accessLocation in one of the id-ad-signedObject accessMethod instances in the manifest's Subject Information Access (SIA) is encompassed in the requested indexScope. As there is no concept of 'sessions' (like in RRDP), clients can interchangeably use different Erik relays. When one Erik relay generates a HTTP error, the client can try fetching the requested object from another Erik relay. To improve reliability, clients should alternate among different relays in successive query and fetch attempts. Clients SHOULD use HTTPS, unless the local system is unable to establish TLS connections to any of its configured Erik relays. 5. Querying an Erik Relay Client-side retrieval requires nothing other than the GET request method (Section 9.3.1 of [RFC9110]). 5.1. Fetching ErikIndex objects The URIs to fetch ErikIndex objects can be constructed using the following Well-Known URI template with the relay's hostname as authority, the erik keyword as suffix, the string /index/, followed by a FQDN as parameter, i.e.: https://{relay_hostname}/.well- known/erik/index/{FQDN}. As an example, the URI to fetch an ErikIndex for the rpki.ripe.net FQDN from a relay at relay.example.net would be: https://relay.example.net/.well-known/erik/index/rpki.ripe.net Clients SHOULD use conditional GET requests (Section 13 of [RFC9110]) for fetching ErikIndex objects, because HEAD requests incur a latency penalty due to redundant round-trips. Responses to requests for paths starting with /.well-known/erik/index/ are mutable. Snijders, et al. Expires 20 May 2027 [Page 13] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 5.2. Fetching objects by hash This specification uses "Named Information" identifiers mapped to .well-known HTTP/HTTPS URLs for object retrieval, as described in [RFC6920]. For example, issuance #54 of ripe-ncc-ta.mft has the following SHA256 digest: c2d0427bc5a32c42eea1ab5663d592b1fc29c7d4ef16ab0b5e1d631d039dcc21. The aforementioned digest encoded using base64url encoding is wtBCe8WjLELuoatWY9WSsfwpx9TvFqsLXh1jHQOdzCE. To fetch the aforementioned object from a relay hosted at relay.example.net, a client would access the following HTTP URL: https://relay.example.net/.well-known/ni/sha-256/ wtBCe8WjLELuoatWY9WSsfwpx9TvFqsLXh1jHQOdzCE Responses to requests for paths starting with /.well-known/ni/ are immutable. 6. Prefetching Objects in Bulk Object prefetching is a bulk distribution mechanism useful for efficiently bootstrapping empty caches and for clients to catch up on recently discovered objects through fewer requests. This section outlines the general structure of prefetch request responses and defines various .well-known/erik/ endpoints. 6.1. General Structure of Prefetch Responses In this protocol, a Prefetch Response (PR) is simply a concatenated sequence of zero or more DER-encoded objects. Because DER-encoded objects are self-delimiting, no marker is used between the objects and there is no end-of-sequence indicator. A PR is non-deterministic: objects contained within the PR may appear in arbitrary order or in duplicate. A PR may contain RPKI signed objects, ErikIndex objects, and ErikPartition objects. The set of objects in a PR need not be self-consistent or complete from the perspective of top-down validation. PRs merely serve to reduce network traffic by prefill unvalidated cache areas. Different prefetching strategies have different trade-offs in terms of coverage and accuracy. On the one hand aggressive prefetching might waste bandwidth (i.e. clients download data they might not end up using, or data they had already cached), on the other hand, Snijders, et al. Expires 20 May 2027 [Page 14] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 sending many individual requests for each and every object increases network overhead and latency. As a rule of thumb: FQDN Snapshots (Section 6.2) are useful for clients with no prior state and Segments (Section 6.3) are useful in the steady state (when synchronizing every few minutes). 6.2. Prefetching Using Snapshot Buffers A snapshot buffer contains all signed objects a relay associated with a given FQDN as of the time of the snapshot's production. Snapshot buffers are not necessarily produced in lockstep with updates to the relay's merkle trees, therefore clients MUST perform a tree comparison after fetching a snapshot buffer. To avoid wasting resources, relays SHOULD NOT delay snapshot buffer production by more than one hour. As an example, the URI to fetch a snapshot buffer for the rpki.ripe.net FQDN from a relay at relay.example.net would be: https://relay.example.net/.well-known/erik/snapshot/rpki.ripe.net Responses to requests for paths starting with /.well-known/erik/ snapshot/ are mutable. To avoid wasting resources, relays SHOULD NOT include ErikIndex, ErikPartition, and ErikSegmentIndex objects in snapshot buffers. Clients MUST discard any ErikIndex, ErikPartition, and ErikSegmentIndex objects contained in snapshot buffers. 6.3. Prefetching Using Segment Buffers Segment buffers form an append-only log which contains the signed RPKI objects, ErikIndex objects, and ErikPartition objects a relay discovered in the last few hours for a given FQDN. Relay implementations are RECOMMENDED to start a new segment buffer every 5 minutes. A client starts by fetching the ErikSegmentIndex (Section 3.4) to discover the available segment buffers on the relay. 6.3.1. Segment Discovery The URIs to fetch ErikSegmentIndex objects can be constructed using the following Well-Known URI template with the relay's hostname as authority, the erik keyword as suffix, the string /segmentindex/, followed by a FQDN as parameter, i.e.: Snijders, et al. Expires 20 May 2027 [Page 15] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 https://{relay_hostname}/.well-known/erik/segmentindex/{FQDN} As an example, the URI to fetch an ErikSegmentIndex for the rpki.ripe.net FQDN from a relay at relay.example.net would be: https://relay.example.net/.well-known/erik/segmentindex/rpki.ripe.net Clients SHOULD use conditional GET requests (Section 13 of [RFC9110]) for fetching ErikSegmentIndex objects, because HEAD requests incur a latency penalty due to redundant round-trips. Responses to requests for paths starting with /.well-known/erik/segmentindex/ are mutable. 6.3.2. Segment Buffers The URIs to fetch the segment buffers are constructed by transforming the segmentIndexTime (Section 3.4.3) to integer representation. The integer value is the number of seconds, excluding leap seconds, after midnight UTC, January 1, 1970. Responses to requests for paths starting with /.well-known/erik/segment/ are mutable. As an example, the URI to fetch the segment buffer for rpki.ripe.net starting at Jun 4th, 2026, 15:50:00 UTC from a relay at relay.example.net would be: https://relay.example.net/.well-known/erik/segment/ rpki.ripe.net/1780588200 7. Transport Error Detection and Handling The client MUST calculate the hashes of fetched objects and verify they are the same as the expected hashes (which are embedded in the URIs through which the objects were retrieved). If there is a hash mismatch, the client may try fetching the object from a different Erik relay or treat this as a _failed fetch_ (see Section 6.6 of [RFC9286]) and try again at a later point in time in a next validation run. 8. Setting Up an Erik Relay Erik relays can be operated by any party, without permission from or coordination with publication point operators or CAs. Relays are made accessible via either HTTP or HTTPS or both. Relays generate and make accessible ErikIndexes and ErikPartitions derived from their current validation state, the client then cherry- picks which objects (if any) it wishes to fetch. In turn, relays fetch fresh data from other relays, or from CA-designated publication points accessible via Rsync ([RFC5781]) and RRDP ([RFC8182]). Snijders, et al. Expires 20 May 2027 [Page 16] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 9. Operational Considerations 9.1. Scaling considerations As of July 2025, the global Internet's RPKI churn rate appears to be 2 new objects per second. The ecosystem is estimated to be composed of ~ 5000 RPKI cache instances and ~ 50 repository servers. Assuming 10 minute fetching intervals and 150 metadata requests per synchronization run (for exchange of Merkle tree data), an Erik relay serving all the Internet's RPKI cache instances would probably need to be able to sustain serving an average of at least 11,000 HTTP requests per second. This order of magnitude in terms of scaling requirements can easily be handled by a single commodity server. 9.2. HTTP Version Recommendations In this protocol clients might need to retrieve many individual objects simultaneously from relays. In non-multiplexed transports like HTTP/1.1 ([RFC9112]) concurrent fetching means either establishing many parallel TCP connections or serializing requests over a single connection which might lead to head-of-line blocking, connection exhaustion, and substantial performance degradation. In contrast, HTTP/2 ([RFC9113]) and HTTP/3 ([RFC9114]) natively support stream multiplexing (discussed in Section 4.11 of [RFC9205]) and field/header compression (HPACK [RFC7541], QPACK [RFC9204]). Therefore use of HTTP/2 and HTTP/3 is RECOMMENDED to facilitate high- concurrency, low-latency object retrieval. 9.3. HTTP Compression Using gzip compression on average tends to yield a 20% reduction in size when fetching individual objects and 50% for Prefetch responses. Therefore, clients MUST support gzip content coding (Section 8.4.1.3 of [RFC9110]) and the server MAY assume it without explicit negotiation. Clients SHOULD send an Accept-Encoding header field in the request, which permits the negotiation of other compression schemes as well. Using a previous version of a RPKI object as a compression dictionary for a newer version enables delivery of a delta-compressed version of the changes, usually resulting in significantly smaller responses than what can be achieved by regular compression alone. Clients can facilitate delta compression by sending an Available-Dictionary request header, using a previously fetched version of the RPKI object as the dictionary. It is RECOMMENDED for clients and relays to make use of Compression Dictionary Transport ([RFC9842]). Snijders, et al. Expires 20 May 2027 [Page 17] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 10. Security Considerations This document makes no changes to RPKI certificate validation procedures. Paraphrasing Section 11 of [RFC6810]: The RPKI relies on object, not server or transport, trust. That is, the Regional Internet Registry root trust anchors are distributed through some out-of-band means, and can then be used by each relying party to validate certificate chains and Signed Objects. The inter-cache relationships are based on this object security model; hence, any cache-to-cache transport is assumed to be unreliable at times. See Section 5 of [RFC8182] for more security considerations. To avoid certain forms of attack, clients MUST check whether indexScope, segmentScope, ManifestRef location values, and manifest Subject Information Access (SIA) extensions match the expected FQDN. Byzantine events or faults in relay-to-client communication can be overcome by the client rotating requests for objects among different relays. 11. IANA Considerations 11.1. S/MIME Module Identifier The IANA is requested to add an item to the "SMI Security for S/MIME Module Identifier" registry as follows: Decimal Description References ---------------------------------------------------------- TDB id-mod-rpkiErikSynchronization-2025 [this_document] 11.2. SMI Security for S/MIME CMS Content Type The IANA has allocated for this specification in the "SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1)" registry as follows: Decimal Description References ---------------------------------------------------- 55 id-ct-rpkiErikIndex [this_document] 56 id-ct-rpkiErikPartition [this_document] 59 id-ct-rpkiErikSegmentIndex [this_document] Snijders, et al. Expires 20 May 2027 [Page 18] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Upon publication of this document, IANA is requested to reference the RFC publication instead of this draft. 11.3. Well-Known URI IANA is requested to assign an URI Suffix for Erik Synchronization in the Well-Known URIs registry as follows. URI Suffix erik Reference: [this draft] Status: permanent Change Controller: IETF Related Information - 11.3.1. Protocol Registries Request at Github This section is to be removed before publishing as an RFC. See https://github.com/protocol-registries/well-known-uris/issues/67 for a copy of this request. 11.4. Media Types IANA is requested to register the media types "application/rpki- erikindex", "application/rpki-erikpartition", and "application/rpki- eriksegmentindex" in the "Media Types" registry as follows. 11.4.1. ErikIndex Media Type Type name: application Subtype name: rpki-erikindex Required parameters: N/A Optional parameters: N/A Encoding considerations: binary Security considerations: This media type contains no active content. Interoperability considerations: N/A Published specification: [this_document] Applications that use this media type: Tools for RPKI operators Fragment identifier considerations: N/A Additional information: Content: This media type is a RPKI ErikIndex object, as defined in [this_document]. Magic number(s): N/A File extension(s): N/A Macintosh file type code(s): N/A Person & email address to contact for further information: Job Snijders (job@bsd.nl) Intended usage: COMMON Snijders, et al. Expires 20 May 2027 [Page 19] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Restrictions on usage: N/A Author: Job Snijders (job@bsd.nl) Change controller: IETF 11.4.2. ErikPartition Media Type Type name: application Subtype name: rpki-erikpartition Required parameters: N/A Optional parameters: N/A Encoding considerations: binary Security considerations: This media type contains no active content. Interoperability considerations: N/A Published specification: [this_document] Applications that use this media type: Tools for RPKI operators Fragment identifier considerations: N/A Additional information: Content: This media type is a RPKI ErikPartition object, as defined in [this_document]. Magic number(s): N/A File extension(s): N/A Macintosh file type code(s): N/A Person & email address to contact for further information: Job Snijders (job@bsd.nl) Intended usage: COMMON Restrictions on usage: N/A Author: Job Snijders (job@bsd.nl) Change controller: IETF 11.4.3. ErikSegmentIndex Media Type Type name: application Subtype name: rpki-eriksegmentindex Required parameters: N/A Optional parameters: N/A Encoding considerations: binary Security considerations: This media type contains no active content. Interoperability considerations: N/A Published specification: [this_document] Applications that use this media type: Tools for RPKI operators Fragment identifier considerations: N/A Additional information: Content: This media type is a RPKI ErikSegmentIndex object, as defined in [this_document]. Magic number(s): N/A File extension(s): N/A Macintosh file type code(s): N/A Person & email address to contact for further information: Job Snijders, et al. Expires 20 May 2027 [Page 20] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Snijders (job@bsd.nl) Intended usage: COMMON Restrictions on usage: N/A Author: Job Snijders (job@bsd.nl) Change controller: IETF 12. References 12.1. Normative References [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, . [RFC1123] Braden, R., Ed., "Requirements for Internet Hosts - Application and Support", STD 3, RFC 1123, DOI 10.17487/RFC1123, October 1989, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, . [RFC6810] Bush, R. and R. Austein, "The Resource Public Key Infrastructure (RPKI) to Router Protocol", RFC 6810, DOI 10.17487/RFC6810, January 2013, . [RFC6920] Farrell, S., Kutscher, D., Dannewitz, C., Ohlman, B., Keranen, A., and P. Hallam-Baker, "Naming Things with Hashes", RFC 6920, DOI 10.17487/RFC6920, April 2013, . [RFC7935] Huston, G. and G. Michaelson, Ed., "The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure", RFC 7935, DOI 10.17487/RFC7935, August 2016, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Snijders, et al. Expires 20 May 2027 [Page 21] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 [RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., "HTTP Semantics", STD 97, RFC 9110, DOI 10.17487/RFC9110, June 2022, . [RFC9286] Austein, R., Huston, G., Kent, S., and M. Lepinski, "Manifests for the Resource Public Key Infrastructure (RPKI)", RFC 9286, DOI 10.17487/RFC9286, June 2022, . [X.690] ITU-T, "Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)", ITU-T Recommendation X.690, ISO/IEC 8825-1:2021, February 2021, . 12.2. Informative References [M1987] Merkle, R., "A Digital Signature Based on a Conventional Encryption Function", Advances in Cryptology -- CRYPTO '87 Proceedings, Lecture Notes in Computer Science, Vol. 293, DOI 10.1007/3-540-48184-2_32, 1988, . [P2P] Austein, R., Bush, R., Elkins, M., and L. Johansson, "RPKI Over BitTorrent", March 2012, . [RFC0677] Johnson, P. and R. Thomas, "Maintenance of duplicate databases", RFC 677, DOI 10.17487/RFC677, January 1975, . [RFC1925] Callon, R., "The Twelve Networking Truths", RFC 1925, DOI 10.17487/RFC1925, April 1996, . [RFC5781] Weiler, S., Ward, D., and R. Housley, "The rsync URI Scheme", RFC 5781, DOI 10.17487/RFC5781, February 2010, . [RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support Secure Internet Routing", RFC 6480, DOI 10.17487/RFC6480, February 2012, . Snijders, et al. Expires 20 May 2027 [Page 22] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 [RFC7115] Bush, R., "Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)", BCP 185, RFC 7115, DOI 10.17487/RFC7115, January 2014, . [RFC7541] Peon, R. and H. Ruellan, "HPACK: Header Compression for HTTP/2", RFC 7541, DOI 10.17487/RFC7541, May 2015, . [RFC8182] Bruijnzeels, T., Muravskiy, O., Weber, B., and R. Austein, "The RPKI Repository Delta Protocol (RRDP)", RFC 8182, DOI 10.17487/RFC8182, July 2017, . [RFC9112] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1", STD 99, RFC 9112, DOI 10.17487/RFC9112, June 2022, . [RFC9113] Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", RFC 9113, DOI 10.17487/RFC9113, June 2022, . [RFC9114] Bishop, M., Ed., "HTTP/3", RFC 9114, DOI 10.17487/RFC9114, June 2022, . [RFC9204] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK: Field Compression for HTTP/3", RFC 9204, DOI 10.17487/RFC9204, June 2022, . [RFC9205] Nottingham, M., "Building Protocols with HTTP", BCP 56, RFC 9205, DOI 10.17487/RFC9205, June 2022, . [RFC9842] Meenan, P., Ed. and Y. Weiss, Ed., "Compression Dictionary Transport", RFC 9842, DOI 10.17487/RFC9842, September 2025, . [rpki-erik-demo] Harrison, T., "rpki-erik-demo", March 2026, . [rpkitouch] Snijders, J., "rpkitouch", July 2026, . Snijders, et al. Expires 20 May 2027 [Page 23] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Appendix A. Implementation status This section is to be removed before publishing as an RFC. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". A.1. Experimental Erik Relay Services A few experimental Erik relays are available, each running on slightly different schedules. Client implementers are encouraged to observe results using these instances via round-robin or concurrent access. https://miso.sobornost.net/ Amsterdam, NL, single node http://nyc.rpki-servers.org/ New York, USA, - single node https://pek.rpki-servers.org/ Beijing, China - HTTPS, single node A.2. Software An experimental Erik static content generator was developed by Job Snijders in the form of [rpkitouch] using C. An experimental Erik client and server were developed by Tom Harrison from APNIC in the form of [rpki-erik-demo] using Perl. Snijders, et al. Expires 20 May 2027 [Page 24] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Appendix B. Example objects Included in this section are an ErikIndex for rpki.ripe.net and an ErikPartition referenced from the aforementioned ErikIndex, both Base64 encoded. B.1. Example ErikIndex This object was retrieved from http://miso.sobornost.net/.well- known/erik/index/rpki.ripe.net MIIoRgYLKoZIhvcNAQkQATeggig1MIIoMRYNcnBraS5yaXBlLm5ldBgPMjAyNjEx MTAyMjEyMjRaMAsGCWCGSAFlAwQCATCCKAAwJgQgAVcWB3OC0ubB6kQ++599x44y w1lR/sNKQC+qMez1FKoCAk7nMCYEIAH0ynEgAUN5fEwtrut5vK6ki3a84hyL36Qk CT4yeIh6AgJJ6zAmBCACISFDQNBiMhvUhUhLMQ+xPVJpN5x3PPjssOQLzbQl2wIC RCEwJgQgAix5aOcDpezWga2WvGnHymW1piEw3J+G/skZF67t2AsCAk+4MCYEIAKv iYzxr7rwsf6+ilrGibUeYn6ZPyPmCWQa6n+gSBqLAgJDTTAmBCACt/61lACFSg9y qcWNmHI4c+UNMsyZhmmfeai4ywexVQICUV8wJgQgBI7eEhsKGxk3tPhWyXvIJvUl 27JmCatSlpF4vSxyl5kCAkuVMCYEIAVHYvQmBDGYUSc8Obq76YIl4SzdVaTzzBoW cmgrP0NNAgJRXzAmBCAFR9aoCluiyQfSsfK5EQBq/fAuphYTFSHToma3jWWL8wIC ThMwJgQgBYCh0bMxCqLi5joWUvVtlN7itntPlQ2aKXK1p4Wubf0CAkQeMCYEIAcC mHpUgetXficJaqqEWYPaU1BFRIx4YoHePImHYHxHAgJDTTAmBCAHWBdUjyOtV8X/ roa18ZMW35hGN5EnmXMWTSUVd703AAICThIwJgQgB14NOnoRQRBnrgU7rWNxlKCZ oiVICVF5LDD9M5/RCZ4CAlWEMCYEIAeJAL0TAxoftEBaJtwy3BjCFIrPJ2mEBwym rXzdW4POAgJSNjAmBCALj3pLoYWMZyJDSUpFUFUZ1IEuPERuIQFgKWEo8QysXgIC TT8wJgQgDrZkNxQL3Rlcg3/eNmyNivtkVF71sKMDC7YcoOGTBNYCAlf/MCYEIA9z xJDs4ZtD45H5PXEyG0XB1YVp84qu3MKukbno3B6XAgJFyTAmBCAP80XQFthcHOWO 7EAocQnHOqz2AdZafsM3P4JTLm63awICQaUwJgQgD/mr5+q4YIn5SqdJ0tr0d+a9 +M0pVDVNOf9vbFyllK4CAkJ7MCYEIBE5rV35BntO5Clmmo/XciQVdu6GZfE8yOQx 3N8HCDwpAgJHcDAmBCARrfYWWskkyfagD57cYYhlYuznWNV1/3fG7OxAFoqcrgIC QnkwJgQgFLsHBGc8O/GbMgjrNYy6P6SxUzqBl+lUdjwp/asp9y0CAkntMCYEIBYa GhhAglOavANBvmgfJtU4uFYWhG6ovStBSm1qm+XMAgI//jAmBCAZt3Mt++yzBtff AOGWwhJeQcD4VRyKgADGZaVogMmJCQICSEMwJgQgGdWX4Db9sLhgQhTRtuZi9ZI/ TVcZraV/UlrG5DDFJfgCAkrCMCYEIBqDO7Mysu0hlQDHtBjBx+4rFXDuptslVUAo T61NCEGnAgJEIDAmBCAbadphUt1UDIyy82SOeKrN2dVG+NT2Ux1GjjoEHWVgFwIC U98wJgQgG+U3+ajfL5gCmRYaFrxvZxDvRhIzni1Ft/GeOe5ddToCAlPfMCYEIBwn WP9DwILbx7UR7mw7RqSFwRoqxeCsRL95cNWCtFpLAgJT3jAmBCAdBWXTEtIH6C9I o5C551OZZJ5qhxrYobq8QR0FVp2ZrQICSEQwJgQgHXp3JSAcKYAzS4pUy65wOD09 ksuMSCbANxRLc9kDtKYCAkxrMCYEIB53lO93h/aHczmEVHBXHAEdsmyS1qcdAI06 EmwoPhdUAgJE8zAmBCAfK56xCq+HXhiHotK0WF9HzcJx6CfRdNqaWvxVOimJEQIC TuUwJgQgII6s86chVbp+Qk3srvVFBFEyqOGWH8+yWCLh8L+BkkgCAlFgMCYEICJ4 vqHxn1J7pgC8nSEvAjUk+2qNFx3T+7SLszcKMNBBAgJIRTAmBCAjya6cCQWf0RrB B5rBg2xdrFUuDEeFhryyKdlrsHrEWwICSRkwJgQgJG9erspanISmhcK9FSVOuFP1 rQSDDvpjMvDoC+QS23gCAlmmMCYEICTOZePlPnRzO2J4Ww+dWMvWgiGZ48wxf8v2 3MILITcrAgI/dzAmBCAlFqSFZA4RdxFk0+Wyktv9oUgqMVKX1KyOl4cA/3F5TgIC VlgwJgQgJw0NwDcKD5PBNRj6Jib7pvlzsf5+ykDBtYiVAPi5FeMCAkQhMCYEICh9 eLFcbSuvylmJUA8wmjYngXjYfEPz5Q9qM7xp7LJVAgJTCTAmBCAo8RgVdgPuZniF PFhVtGdZuvY2eJTYmnJlq9PhS+a8CwICSsMwJgQgKeaOTar2T+GTErhlgX8i/3S9 Snijders, et al. Expires 20 May 2027 [Page 25] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 CcK6D+i8elqLaRsEnvICAjvaMCYEICvlRcU1zy+rfRUl3XaWDpR7CFusPw0r5Aaq iY9mmyxAAgJRXzAmBCAsJWShKaqqHphssxYiHcbz6YbSRFIly7TooIGgfolJ8AIC TuYwJgQgLKkfzP6x/ydHOaZDnmEyB3ZRYzxPxSl7tbU7RRq7bZkCAkhDMCYEIC3Y 6dAs1uA3MCsNbaM9QeIQffcgCu0flzflfeGE9aQ1AgJCejAmBCAt7TFjztjXbYfq bLGf8yi33ksi4qvWUGH1+WeHuyBllQICTGcwJgQgLfqGJ1tZMv/mHxllyW9hjZoc ffAxkT+D8cUmkqzR+2ECAlwkMCYEIC6CuOudh8wseJrh5d/dDY9cVB8ITvTo3SnW s6r2Z75iAgJZqDAmBCAu4TVfIjez5RG7qLxPBhRYDGC0mrODKyNSuiBqmXalYQIC SRgwJgQgNDfQFkSFH3dOmCZww98vTggzpirO2uiUy9H/CK7nEaMCAkhHMCYEIDXt x2aXO8Luh2i2yBuT5AVo5J/3PXu+uaHhp0brCJgEAgJPuTAmBCA2NxhbkgFmfXHm DjG598/2s9nNwnWXGHJid5xdojsp7AICWnwwJgQgN7W683BgsIH5TZvrlFxLnzpP GgV0fa/HXfdhDFMGKsECAk7lMCYEIDgAdUvVevKEhH1wNf12ePTAphIuSnagWn5e iGKbCjZfAgJZqjAmBCA5n9PdiRZ8LDRvIcuGU6i2ZMV1K1Uuf/SY4tbfu1EE7AIC RckwJgQgOmB5Pf3aqkRL81XMMl8zWPnLIIKWx9suaB6ccXR+S9sCAlCNMCYEIDqL b3LyYYKHBtRs3iDwQnHUTirMCjdwT1TO9FlZ3O49AgJDTjAmBCA7BlpFmP89U0zj Sws2im8vxSFi9xaj5miJXrooRf91qQICW08wJgQgO+fBxJgCfGQeGXedd0zC94fC cIV+O3ZjFz5cbae5RZMCAknsMCYEIDwSeSG2XVpbzQbtHZ6+MbSN5KmZjgTF9P/o /owsVeyUAgJVgjAmBCA8czApFcpWiRLpD79k1P4ro/2jB4mj7YEuQbSsPL0aYgIC RcswJgQgPMKEr1ciTdrQVUMLRjdXX0lUyOWSK1vbJZP8OYCL8xQCAlWHMCYEID3U I6vTOwB/reAMV3soFHXNIiObAqQRaFJKgI39yu0sAgJLljAmBCA+du2iubQRMaGw XfTzsIBp77qs9YClJgGsbob8YLqlPwICPK8wJgQgP+PNDqaTwF9ZeWnceauYoOXs 5WRUIYoqAFFVxh2iTsgCAk+6MCYEIEIM7+wBWAKsno72gDR7HOFQ6wYvjqyTeLLj 47+L4uOaAgJGmjAmBCBCOrTbFhvmyAXY9V6mZ/l4WZc8y/fMn+8Va6ZiSUK9CwIC Sr8wJgQgQwHe9w88upFFhp4xEPKqnS1dPTEPSqcFQc54h3VLu0sCAkDPMCYEIEQQ oYEd2OYKgJbNz+8JlM8TOH1E8VvA59Vr9U8tUWi3AgJQjDAmBCBEI3u4tdiFckG0 XsWaHd7G+fTaXFYbfJrXdxTvA61U3QICRPUwJgQgRYXaniUdAJYUFDSecPeAAi1k iXugVVojYUS5C5BKHowCAlgBMCYEIEXu94PyU9GjlF0Mbn+EGhTXBLLJmlxOrB5w nZkn4KR9AgJA0jAmBCBLJldcVAzqKcdbWm50OculArvIxY7VhYaplCvSgRrfFQIC SEYwJgQgS/KGVqmXmfr/3MESoBFyBFTsbA8TKnTBPGZ5TSBal4ECAjsGMCYEIEww SFmU9oZS2gB8CNsWh9QkPckbkciGmoo2oZG0fbQsAgJWGDAmBCBMmnSrNzJLswmo UKhOhBlkbArs1DBuIVf7eGGrdATD4AICS5QwJgQgTKhbUZFbtEv39bH58A/nZ5su VUbQhh1elBiKW8Wgft4CAlcsMCYEIE+2ub0hd+53hcS/2/U9MWq7mHb656Y5wf/h R3j/0GqaAgJGHjAmBCBPyJeUvnkL5eWZWKVtPNUOdatkGHaVqgNUBYzUnafG4wIC UIwwJgQgUUR/M2EPXSV/IsYJvbFf05jTJHVMemZo4/CGh0mAaVACAkQhMCYEIFWT hkFNz84amFRnljeaZTh9d8OZlIhwSuGFXD9OUEsWAgJGnDAmBCBVsQgBqSJV76r1 GTl1ZXUjVXrVW+gmhF5Fygr+LdEkcAICTT4wJgQgVuosJrx9USEm3HVjatayXlsw DheWuolDkW7g70swZP0CAkQiMCYEIFcRQvTGTArzjpkAMgAOeufK3lmE5EtXfFlG 45pDzsGpAgJSMzAmBCBZTkPiY1D2AQLSZxZHCXmhma0ktZKVFrCUvuAPioJzvQIC Q0wwJgQgWZOlsDRsGlu/xRCEcEQgAKtGm4AikGPZfvP/6AswS2UCAknuMCYEIFoH WxcSVgzGDrCRNnuFL1M66/iXfX7pLhEOeFLi5+fVAgJHcTAmBCBb6v1+mavf0Jjz jyolWa+gSxu9PVsDLa2LXSwUofxFlgICR28wJgQgXbojs7L/0B/PD3AtdrtxDo1b tV7zaTvC+F8kpf/x9IcCAlCNMCYEIF3dGt7BRj+i1hqy68yyPHk3092kP/IM/fin PYy8W0W6AgJObzAmBCBhK0mxey7lhILodyz0J3/QugtK3RbhNDkRtD/pIwb0XAIC QnkwJgQgYuzdz+L330doFiKfn9fhwQFHviWl88aH+oUepVnvt7ICAk4SMCYEIGMZ T1SE8lyqnzLExThfMDWSDktxLzvd2wnNfQRxgL3BAgI/KTAmBCBj+5kRHOYUH7ln qiWPT1a+J4TbbgV6/OxtWtCNZzP6lQICSsIwJgQgZQuOGXx3MlgXLo8EEvun9/21 wango5pL+Cabigb6EzYCAlcsMCYEIGY1hvIqHEnJj6mFy8pOJXcTZE+x0OWL7c6p +n1WldOEAgJMajAmBCBmVYAvGJhgqWsEKNhef0QvPECgOlkpOMQJwCcqL3wKLAIC RCIwJgQgZoTo32vVBpwDfH95MdxoSeu3vbZienNauMJync8TfkACAkGjMCYEIGb6 Snijders, et al. Expires 20 May 2027 [Page 26] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 2rkPEKhc49gT9ukh3rFcDlbAg/oxox4ax5CiCTV2AgJBHjAmBCBnVhciuTMgGWMP uWGdasUyc9a3vvK+0SMXZESNE3fPuwICPlYwJgQgbZDMdop7jshpQuU2Ux0RYYfr cj5z6KjI7Isa6LraMDcCAk+6MCYEIG2y5UhBztbAEM1QFFHTCgQuX8dJ8MYlCaD6 Xkkb1UoIAgJHcTAmBCBuAuMJR5hDxKRcY3JuOtYIqHQ5tHttkYcXG62KbKT3LQIC TT4wJgQgbqKENHTQd04e33ugTec8t4Gh6rQzvchhoNKYgIs+sRYCAkkaMCYEIHE4 QREBTX+sqmlogzmPIC1WRjKGPYosrpsT2b/7dog5AgJKwzAmBCBxrcrOhYZc9Gqy XKV6ZzRrGys3cox2HaBQ67N/lQaxkAICRPUwJgQgcglZMtjMcegrEf2voGev+tgk ObcNuVfo+nkJ7DuJekcCAkxpMCYEIHKgxqaH36zXzD/40r377FJCI3MjYkQLbS6m yVGAjbwfAgJHcjAmBCBzdb89JFozxjQRtgoO7X8nK8P5gs7tVXBCvgsnam/nUgIC TucwJgQgc4m+LGirgrp/D+7RUA8f5I6LnryG64hG1oMtZhN9ggICAkrCMCYEIHP3 NXcNooLlOiK+SWZZ7/e8G6aJn4bO4qbY5YxF/KgtAgJOETAmBCB0bEYhzDybOUTm 9PbrrsTsT0SLBsANoc/rqxgnSZjNLAICSEQwJgQgdkb/ouPRPLSJwrhf2+3JAJpT OEHWAEs2JQQACd+V0BQCAk4QMCYEIHaxt565LrBNDTINynuDFDBMURuIMrKSREzg XqEfkXb8AgJLlTAmBCB3O3DDYAGAecHr6Lc92NdZz0JV9A5fM1DhHBJRTwQjsAIC TT0wJgQgd/P+utTH7FGplDKhwSWWrp3XKRmVw5vrC4Mvv9cattYCAlwkMCYEIHi1 bbgDmdAsZBdimuj6AFcGAZ9wqoJh1oTYIK1TRMaDAgJLljAmBCB52aRW2ND5UZx4 iLh+Vq5HG/fnl0SQHZAIjsUeabD4awICXPowJgQge5p49bGOS1wv+QFcTjURgprV S0zYeg5lj9G/EI60ZJACAljXMCYEIHz0S9pnw98GSAKNF/4/0hvhGGSTbCxBOEqr y9f9Od1cAgJHczAmBCCAT8WvvLgN004B98l8IpjITHtP8fJXcgOM8dyAYAE3iAIC PyowJgQggHYW17sxfHg+gUgeDQkD675cyTByEJe83PKQLB8Lka8CAkXIMCYEIID6 X0TF+Gbogry1oqZ8HVpJTxp/fAMvtFwEuO1flyLEAgJdzjAmBCCCqjE+tcZEWXh0 GACJOOaMIEo0sJIFWEka6AiZ9xZIWgICR3EwJgQggz3zMzLS5jIYdC9WNYcFSAaU UqKKc25LV0oN7BpXV1cCAk08MCYEIIPzbWk8zReroekmlFA2+AwbygwWxPnl1JJ5 DQ2kl3VYAgJHcDAmBCCEu4B2Hp8LL/8BB+wjh2+qqTpd/5MuWHgg318LOM4R3QIC RCIwJgQghTNdRNeH0d0mL4RcWTPmvfKhjK3rWWEZDHIZJ38HXu4CAkkbMCYEIIdm /iMQ1DckNsY0VwCZ+26THqWWhbFMR234pGnmvnn0AgJHcTAmBCCJE5Zmtm1W4fbh ZpapGZ7dkhFnCuPwhmcoW/zCUhhZuQICOjIwJgQgiVOQ6IIs7OQ6lYJ/cgdFEQTu +PSabCZNrwi4mWXB73UCAkXJMCYEIIrVjdt7meT2Tfo3B8riYtO65v2Sl2TDQavS QoxCGyX0AgJO5DAmBCCLutUiQwcOJaYnQYgyP3PC+R0J2ToC8YJX1paTzklOtwIC QyEwJgQgjvIDd/tDeRLTNTiyin3U7fU4WpAzJDD8vYjTVaxyrKwCAkQgMCYEII+N ejQD4l/Ej7b0CfuVdIzRfO3EEFtNdkMpcmnOoEH3AgJEIjAmBCCQK8SIr3yVMUmt jz4+HQxcuZjZQQm6dkeDHjwbdQGrcwICT7gwJgQgkTg0+tx/J7ukp7Hf05KYmzUg pWx1MfvUWuEfoNw2qEICAj8pMCYEIJFZKX/B+R4MLEqeAAt7E7E2zCVrrnXS6tIj 70sjFUoNAgJQjTAmBCCTDXNPJyjPag341V45SoY2Wn9djXCXSxnHgBgq9dnbcgIC R3IwJgQglKg0ZLoqFYef5rnfgzmqXDMCIoRJZ8tCgIPXiOq23XoCAkXKMCYEIJXl Qzpg0xIJjl4A+F+dO2JkUQxfcnn3he5jJJN4L061AgJJ6zAmBCCWB9DCxRc9r5U/ hNjxi7qq8zBjYc6f2HmxoXx3Jo2PawICS5MwJgQglsAoqfGIiVMybwaWT11JinVG E+qJCMjqDieoywRcEj4CAkuVMCYEIJci1LLb03+SSeGqqd3PDSBTZnI95e5nmLxc ADHTt/qpAgJRYjAmBCCXzELmPMek2pHslNkF/Z5opFCFIsmLzhiK2QTSduB4/wIC SEcwJgQgl9Rzr/rJ8OReDD3VGrkcJmcKyy+++pIXkI9fdI2GsQMCAkXJMCYEIJh4 7FC2lSGTQTM48FhT50GxjtzoumIpDZDyXY24n+JXAgJTCTAmBCCY5iG1GK+q/VQH 7asG6YCsI/hCbmyYmXT9fWjQHAgLOAICRB4wJgQgmrgdI1SeJ+BTrm3/fGGSFHqJ eXHUrJ5Fkbr7PR/U/9oCAkhCMCYEIJq5OiyEyZxNimL7xmBlJDjSLlvHXS4Npdob 6vcPGlXUAgJBpTAmBCCcNg1Y7wt24mlshMHwLM2UDH/a15OjphC/Jg3S9If7VAIC UIwwJgQgnEKhlYxGQhB9pUhU4IbjhtmyNYlMH7owHBVRuE9Wss0CAkntMCYEIJyT Wo60yjMhKTz0PLn9cgv3M2eEAyHTRJk6aVHzbb/jAgJPuDAmBCCc6DNaqbo2iuAi fRocp95Ushs3OFKaEJB8LCEOg0F0JgICSe0wJgQgnOxLk+NeI3SO2UijqTJpzid1 6lzFLwmkBPI5gNq3oNECAk+5MCYEIJ4M5d9zSaFYD8HTB9lBK+oJbQD1KoWiWD4J Snijders, et al. Expires 20 May 2027 [Page 27] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 7y/r6nC0AgJQjjAmBCCeGrj73tzxGcJiOf4DBm5LRsUHlmyj4zNcWV9HBD/LxgIC QnkwJgQgnjBPX46rI/eDDjc/kcY7lQ85tZaLl9eEOQW7OPk9BPoCAkdxMCYEIJ54 kSK3AoYSfhuu+1TqX3D45kCji5WPIHdolc5qrDpPAgJKwDAmBCCf5OB5F6wXAZjV rh/6BFAsXJwlnQStyGno3bTezMSChwICPlYwJgQgoMdH57h6G0VwQgZfMaQilKlv yh1BbPRPgkGqFYkrr6kCAkT3MCYEIKPppU/090gedr9Kt1uGGpaZ95ctuCcZlIWS 7BCFnHqFAgJKwTAmBCCkYb1oilYZjAZK+f03tCcbO0+K+QZ5zI50jpOnzn0tOQIC RCEwJgQgpGRy+QR5VMjIRz695xDSNfKjhc+dRuMTzvKFxPQZKKkCAkGnMCYEIKVf EIEpqmKdm2HIodQ5htiTdAC/Lz3WCmS8PDY1RJgxAgJOEDAmBCClZipifmaJ4lhE Q26YBmb/zzOUl2HPRqx/VU0Ov4j6TgICTuUwJgQgph92XVK9FK3OrgHzeiFkSck9 c0hxjFNNOI0mAa4p3acCAlCMMCYEIKfTRWB4ND24VHtdOMIlblEAWjnUYBGCzUv1 kKTt72egAgJTCTAmBCCn9FiTX6rYPwXKN4R22iofdISoPaz6Ij+R7+szwCunTAIC UI0wJgQgqCnxIvctnvXq9XUNkg50BKtKVY+Rv3WpJcTNVdX0QKoCAk4RMCYEIKnI ozJufeJoDFt9t5PxbARYb10ptf+7Kh9T0p6uVj3FAgI5XjAmBCCqjhX5TVPYS53A Yv9yatyg3VmF4U72G+QwVenJH5NF4wICTg8wJgQgrBQEWSmv/OmSx6CsGtK9Ze+/ s9VYcZTLE88Ig5ZYCQcCAl90MCYEIKyF0S2FklgaDATNfL69wXuyErkbh9gnm95z s02wzpWqAgJJGDAmBCCvTrJFjZHlEvDFcMzrfrGXpKBBHzyvq8dXKeRnITbkhgIC SRkwJgQgsmwPLo1pgT5FL70sTK7G5rzGRato5HD/JW10gSsLjqYCAkDPMCYEILJu pTsdMTP32AeexlgxStGc7jnJoIyCJp9hfRlO35bDAgJKwTAmBCCzjYgec90EVym0 yCnjZh1X7NFsGSKlNd1CQc/6/Bn4bAICUwkwJgQgtTEHq0k0VYq5WAonQPeMHBns a+kVN5RkHTBajnz3DUoCAkXLMCYEILVC8JzmsoHGPEmx7DdtxEOQQyZSt0a4bkcC b4vTxB13AgJHcjAmBCC1fU1QJbbwjeuqfZ066qpqWedWpHzGt/X96efCDbhJ9gIC UjQwJgQgtfc3NFIRwZX2ScMsycZ+SrTgclI+ivbIfILe5GQ3ydACAmHyMCYEILZf Xb0k7h6pZ2ZB/MEdfYC7f4RYkIk9AmHFKxmQBY8mAgJSMjAmBCC3Q0nyJM1L1i5j ivhnrrF+uDsuuU3w8imvS0AtNjJgGwICSEYwJgQgt+o0gnY7fk8q0Bh4DFfzQ8Wc dN/KnKcFesDTolQYxWQCAlFgMCYEILgLf2jJ4XGFaZm+1cqyfIMOMMFWwWPV3YYG VnrYOUM3AgJO5jAmBCC4g1g4LpUkiau+gN6v0AZAwlHOSKrHiWb/lsluU27QSwIC S5cwJgQguQpBIbOgofcqnbkzdIWXt0uExqoDh43yzysbrOInCm4CAkhGMCYEILl6 obA+V3k2WHmn+i80wIJAx1GxvjxLnU4CalWBOVzxAgJIRDAmBCC8e0Ds+3j0m8Ab iWqFmJYx65V5zXmnj/ibEjRTKrl4OAICVlowJgQgvd3Cxe8xWNS0wWZy1nxPcLI6 +TIZiRXr3pZmHhxgY/ACAj8qMCYEIL3sSvL4Po/ALYfl+W8eENx5HpbwqMiYJoPt z6c9LyepAgJUsTAmBCC/oqYkLYBb81OQ9T9ZGXebSuyon5noLM4rKJ5wOgcSvgIC TuQwJgQgv9olCX31tJivXwbH9d5Hm1bX4r4nRC6kKVbyXZ8KJIgCAlgAMCYEIMJ6 dcREb29o/QMLg+RhXMOrb2yqZ/E3QuLb9eBc5yjUAgI+UjAmBCDCm6cRkw+7hmX4 dZRbZ+pBS6IoFm7H3Ki4pgH+lfmJ6gICVYcwJgQgw+OsdqxsQ+0hozG7MpsNYKsY cDmuLQO5XkjHi9OfTgECAjsGMCYEIMQh9oMEe2IYlMQEYqLGJItGtQo70kgfY3NX EOV2ZD9MAgJPuzAmBCDE23KhRvpo0VKii5erVhvrJ15PJYWmcxzXJAabRfKtDAIC QycwJgQgxWqnl1a8gwxfFyuTuNazBwJfGufb+n6VdlO5yJvn8ZYCAlCMMCYEIMYw 3mehCQ6a6MzOLXpOooIegH2qO/tu77Bv9oG3st1iAgJRYTAmBCDGaqSgmjSYb6qw cKM2E31nfhae+j1S2LNmkUV+YIECnwICWacwJgQgxukuJ26oghXYhHpQZQZedGiq GuMwcRH1ISSc7suVN78CAkhCMCYEIMgYgYdvmtH5hP0iJpQWdXp7PwSfroTIo5a2 9qxJ73CTAgJCejAmBCDI598xD1San/KBp+du76ewqBs/KlFvMQwrqcB03fpcZQIC UjYwJgQgyOnGCN6Ik4HVK0EwENzmy4ENoNpOmEOV7vbrS4YAzbwCAkntMCYEIMk1 UyW0OGzW/zwoOcAMLEq9uyrB1o9PFRvA2spK7OyeAgJGmzAmBCDKenxdRPGTM66S C7VspRu0mWh2kuSsrJxtvOfUxP8wcAICRPcwJgQgzbBgLrSpfyVLYAuoeMFgAwmh gS50XKCjy2zFsq4azWkCAl6fMCYEIM3QgrW25QPgCYl+aTzgmzegFw93vcCK+Dzi 2IQYkrijAgJIRjAmBCDOCxUBv4djr6nhnoMKQ3fuAQZnGSVs+pEo0cGm9xF2+QIC SEYwJgQgziT9qqhAro0n0wDUO2iQNKfDVaF6axbGhtc0G7uNQlQCAjsEMCYEINJK F0jolDweEy5pOnpfDjdU2TTiMAZkLCHISiuZIWG0AgJEIzAmBCDUQEgAjLGftKAm Snijders, et al. Expires 20 May 2027 [Page 28] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 5XqH8A6/Rqr6x2Uqjut34PUlZ0H4VQICSe8wJgQg1Uft5YizwCnQ3usGxrEXYqhK +CW1lPTWMX7u2CWyZ00CAknsMCYEINVuOKMYT7d46l7SpGuA9yrxxRsvKYHT3FmB lTBSEhx9AgJO5DAmBCDXCWBdW99oMARKUSW+qBco0jI5nfQu6vgrhcnPtnGCaAIC ThIwJgQg14yiPHYuFIXl8V2RDZCna94TvS32qEGAkP8XHTv/z/oCAjiIMCYEINke VyL+UtwIRYPVaeygrUJ7Zue6kpBnqiKQ6SczvpDiAgJRYjAmBCDaN0WZMunKq0im 23SqJqfzczsFsLDVOvujsrV9yE3wVgICSEYwJgQg2lDVb9Wiu0RbkK2l4ruaUkqt cgFkHGUEcFVPGTmtKtgCAkT3MCYEINxeJowZ6dh4gWXXFnQUNg61jVk1A0E3m48i tqYY7cdgAgJHcDAmBCDdFOSiEO5U1vl8LtgiR5PhakRZ9o/otKtP2TMyIczdjAIC TTswJgQg3aIscAj2EO9N88/YP0PFxNdr/z5W+ZTHFpnVMDRoZocCAkhFMCYEIOAP iME68Al4tPvV19JM7j/VoNcXXSb9tYNmxD4bK0waAgJLlTAmBCDg0LbGobLXWMSJ wYQFXZPtk0cZUuUquJcfWWFr6We5SQICT7swJgQg4SMSQ9arqacEX5VH4iLKFMg/ 24vhV+GxdItwfo1YNdICAkdxMCYEIOL45Al5abjYMNdmRLXcucvOz/WYxnRWLkGF AA171B/7AgI+UzAmBCDkI1wwmKGEMU3vMUhrHYHXQWuZHtqKCd7Hv9WTlO4a+gIC SsAwJgQg5kM3piBGnibSdBKkCm0ybj0YlOmsMPI3kFiYG4WOMzYCAkhGMCYEIOk5 u4GqhNu8h513RPZGtN+RHYWd0zAsM/Yb/n8aqo5zAgJSNjAmBCDpqJupqVfULRSB oO9ek4MtMrine5i/UOD2BNPgVzk2pQICTT4wJgQg6oUgvM1KkZqQdFETRTfLt3Ra yTALItgTFtyg4PJk0boCAkhFMCYEIOvuTINm01ILYmLmWvK+jPBEK1iN1BSXaZin ioL0/aReAgJLljAmBCDr8xUkD494azoHjgxtRe6YQcWFphIAcWTlgb1dtv4BvgIC SewwJgQg7Aup+cMEbDa/gGVZMFCNcafWbnnBq0pcrvdlFgu19DkCAkQfMCYEIOx/ 2eHb44+8W76K89gLc46opkHV3bf/qNVWt7x5Lr3iAgJO5TAmBCDtQYLc1Gmlh1Cv a5pB4IgsgZNrhOY3VVFHQT+scEM8kAICSRowJgQg8RPJYsqXs53ypGs2HvkUExAx r9/GLqeh+cCWwHRgbAECAk0/MCYEIPPWQMHZ9BRWWfLvYTXGImuo+AUjkYGquvKC Sgl6qIWsAgJOEjAmBCD0v2u/LSaNVaemfPUEa4AGU0la3KXq0NOinstfT1FJBAIC RcswJgQg9tyAJHftF6/BOcao72O+Fs+JlbnQSW3pt1QU2m/VgMgCAj//MCYEIPcG OCoOOHYkJAcLWKRqoxGmNujIjmP3ji22VAC4saODAgJJ6zAmBCD3g8zcr97vSYei ShLGTjwfsko/s3ZacYlUqCNoNNngbwICTucwJgQg+SaYORtVtvBz2tSbLt9Q4gO4 4TmuZszEe1JB8gqxtNgCAk09MCYEIPlTfNQaIU/JHkL2RlMCt8iXwgkyZibhJuE+ ct/oXht5AgJLkjAmBCD5VhIimUkDWUDIo1WRcR1IoAjBylvoOorhSvoYjcTUkwIC SsMwJgQg+qUiSWOUhXPmH7bvozXCV/HjGxqOU4dVqllrar090ioCAkJ7MCYEIPu6 TIaAJ3LyQ3ENuP7pjMses0el4uK+NKEWtWGkqdSnAgJIRTAmBCD8etngV89Bjntp KS7UBoFbj7pBk6U+jDMF6Cif9mR2fQICRPYwJgQg/Rk/lKEiJXPHmyBpBtvIQrMR zZSIAyACAOymE2BwBtoCAlFiMCYEIP5G7n1qCXa4U4jrC4JSDtp6vlj5p9fyv39R JCem7O2vAgJGnzAmBCD/kswOUqFM9ShFfXO1M0qiA5FNlLGEFB+O19OF9VyqOwIC SsIwJgQg/9fO1aChz1HasTtud/4b3WpV4Q2iItFFF8p4LfgxnVsCAkQj B.2. Example ErikPartition This object was retrieved from https://miso.sobornost.net/.well- known/ni/sha-256/AZmwyRKvBFv4DPl2g5IAhM8BbDvVWzZvgBLjORCoXqM MIIxEgYLKoZIhvcNAQkQATiggjEBMIIw/RgPMjAyNjAxMDgyMzAyMDhaMAsGCWCG SAFlAwQCATCCMNswgdEEIAFg/0CdwFaUyfP3EyK5RmO+SHjEkYpJ03VcFje02/ua AgIIpQQUfz4LJ7jk15j5K53hV/HaWkPNSeUCAhH4GA8yMDI2MDEwODE5MDA1NVow fjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkv REVGQVVMVC81Zi9hMGM5YWMtM2E0Ny00ZDZjLWFhMTUtYTQyZWM4Nzc2ZmJiLzEv Zno0TEo3amsxNWo1SzUzaFZfSGFXa1BOU2VVLm1mdDCB0QQgBNUfbUn0GcyCLtIB 6SMWn3PzeAvWEckmuoPOieKTqQgCAgilBBR/ytid8b+Zo28pDMPvDx57TQJ1MwIC F5cYDzIwMjYwMTA4MjAwMTExWjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2ku Snijders, et al. Expires 20 May 2027 [Page 29] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 cmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzU1LzlmOGIxNi0yODRmLTQ1MTIt YjNkYy0wMTVkOWYxYjRiNTAvMS9mOHJZbmZHX21hTnZLUXpEN3c4ZWUwMENkVE0u bWZ0MIHRBCAHXXSuVDo4xIJcp05FZytpg4kjD/qhya82XREhZNcQDgICB84EFH9R IoN0dC31RKqTBYxaO9PRZCGZAgIPKxgPMjAyNjAxMDgxODAxMzBaMH4wfAYIKwYB BQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQv MGEvOTM4NWFhLTFiNzktNGEwMi1hMDkyLTAxZWIwMzY4NGYwOS8xL2YxRWlnM1Iw TGZWRXFwTUZqRm83MDlGa0laay5tZnQwgdEEIAfribv7yIvTN0Wj8JLMcqQVV5J/ DDGHUEcOrsmff15rAgIHzgQUf5LfdhDwSPQ79EwzbUHGwRV+8OICAhdPGA8yMDI2 MDEwODIzMDEwMFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0 L3JlcG9zaXRvcnkvREVGQVVMVC8xNy81OGJlMTgtMmYzNS00YzZhLWFhNmEtN2Y3 MmY0NGI4OTgyLzEvZjVMZmRoRHdTUFE3OUV3emJVSEd3UlYtOE9JLm1mdDCB0QQg DIjUjD6duUu0FKQv9y05IBRfVcl4+Kd1b9mDDIns65ICAghgBBR/UAd9Ldimehro tqvWu7NIkCiluwICF8IYDzIwMjYwMTA4MjIwMTMwWjB+MHwGCCsGAQUFBzALhnBy c3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzVjL2MxYzFj ZS1lYTU5LTRkY2YtYmNjYy0zZTdjYWRkODhjNzAvMS9mMUFIZlMzWXBub2E2TGFy MXJ1elNKQW9wYnMubWZ0MIHRBCAaaM1Znthus6ISP96g3JD81Tog+3zOPZGZ8AuZ Hf8H9QICB84EFH/j1jtKW0BLX/g8vysVJaMEd/ZcAgIE/BgPMjAyNjAxMDgyMDAx MDlaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0 b3J5L0RFRkFVTFQvZjYvODFhNjcyLWZlOTgtNGQzZi05YjgzLTJjYjdhM2I2ZTQy Zi8xL2YtUFdPMHBiUUV0Zi1EeV9LeFVsb3dSMzlsdy5tZnQwgdEEIB+2rs4fnNPg lkdC0Oxj3YrmH7gcOCVQjNglyUOdsjI5AgIHzgQUfzP8QNLgMzu8e96rK9hZlUMB wPECAgcFGA8yMDI2MDEwODIzMDExMVowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9y cGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC9iNC82NWJmMWQtZWMxZC00 MGU2LTg0OWQtNzk3OTBkNjZkN2QzLzEvZnpQOFFOTGdNenU4ZTk2cks5aFpsVU1C d1BFLm1mdDCB0QQgI6Umaydl8dJpPFLj+98hCRWwWetbdCBsDVGbXzToe9sCAgfO BBR/KjK6QhloDc3Vj2EB5ceuwVQKcwICF7sYDzIwMjYwMTA4MTYwMjA4WjB+MHwG CCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZB VUxULzU1LzE0M2U5ZS05NmU2LTQ3NGUtYWQyYy0yMmU2ZGY0NTg0YWYvMS9meW95 dWtJWmFBM04xWTloQWVYSHJzRlVDbk0ubWZ0MIHQBCAwH+fHKOlH39wY9R5xHxHm hMnb6GSHhpnVmpCHVeA8FwICB4MEFH8QnrYwNX69ximBGmLmKxhXpxMqAgFQGA8y MDI2MDEwODIzMDE0NFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUu bmV0L3JlcG9zaXRvcnkvREVGQVVMVC8xOC85NTAzMGUtYzVjYi00NWJmLWEzZDkt ZjhiNjNkZWRlNTZjLzEvZnhDZXRqQTFmcjNHS1lFYVl1WXJHRmVuRXlvLm1mdDCB 0QQgMrEX8b0WrGlFZa/aGJQ1O81LoLp9UO84CBaveQjgEJ0CAgfOBBR/VoneSnzn aL86tdn4VG6FbMsZNgICF7sYDzIwMjYwMTA4MTYwMTMwWjB+MHwGCCsGAQUFBzAL hnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzc3LzY0 ZDUwNS0yMjA0LTRkY2EtYTk1ZS04YjUzNzI1ODRhY2QvMS9mMWFKM2twODUyaV9P clhaLUZSdWhXekxHVFkubWZ0MIHRBCAzPSRrimqT6CeNH3o60zUEaMS3WUawEw4O ZIl6p9RoIQICB84EFH8Yitq1tVIIHsrIIcmwkDlIc7MVAgISKxgPMjAyNjAxMDgy MTAxMTdaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBv c2l0b3J5L0RFRkFVTFQvOTAvYTY1NTIyLWY3YzUtNDg3Yi1iN2I4LTJlNDYxNDE0 MWFhNC8xL2Z4aUsyclcxVWdnZXlzZ2h5YkNRT1VoenN4VS5tZnQwgdEEIDZuHlY6 ZmzvFkBtLu2X4/vNQhnzQRDO3eUq5luTSA9lAgIHzgQUf/F65Ue58mQeYFd/5VPd tvdJoIcCAgT7GA8yMDI2MDEwODE2MDE0MVowfjB8BggrBgEFBQcwC4ZwcnN5bmM6 Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC9hNS8xYmMwZjktYmQ3 Yy00ZjdhLWE0MDQtYTQzZmYyNWQ0NDdkLzEvZl9GNjVVZTU4bVFlWUZkXzVWUGR0 dmRKb0ljLm1mdDCB0QQgO/APpgOd1ACqy0+8SO9WRmhqT9DddrWoyeDqQzL7bd8C AghfBBR/VvKJSMgy8tQ0u0TV3g6hImAbBQICF7sYDzIwMjYwMTA4MTUwMTEwWjB+ Snijders, et al. Expires 20 May 2027 [Page 30] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9E RUZBVUxULzNhLzIxZmJjYS04MGUwLTRiOGMtODYyMi00ZTg2YWQ2NGY3NzQvMS9m MWJ5aVVqSU12TFVOTHRFMWQ0T29TSmdHd1UubWZ0MIHRBCBBea4tF3JE2mv6g3bW SBcOn1ws0Gw1yJcVg8WbXTnL3wICB4QEFH83coPXwjWpPce9K4MXsnSPKF/3AgIA rBgPMjAyNjAxMDgyMDAxMTJaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5y aXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvOTIvMGZhZGZjLWY0OWItNDNlOC1i NjIxLTgzMWUyOTQ0ZjhmYS8xL2Z6ZHlnOWZDTmFrOXg3MHJneGV5ZEk4b1hfYy5t ZnQwgdEEIELKBg9HoXTnEUmtGFfoSdAVlwNlZSYG4PMsqnmb19iSAgIHzgQUf/yC WF32m3yUsWphky/8i24zUVYCAhOTGA8yMDI2MDEwODIzMDEwN1owfjB8BggrBgEF BQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC9l NC81MzFkMmItZTE3MC00OWE1LTg0MDQtOTJmNzNmNTZmYzYyLzEvZl95Q1dGMzJt M3lVc1dwaGt5XzhpMjR6VVZZLm1mdDCB0QQgQxrKR0GQ5PFg8dSnJkqQgNXgqJJz OfyMohP7WhCW3Q8CAgqPBBR/a9GmsEYlxXHYMPh4scAjgkdAjAICBl8YDzIwMjYw MTA4MTcwMTAwWjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQv cmVwb3NpdG9yeS9ERUZBVUxULzQ4L2JjNjZkNy01N2FiLTQ3NWQtOTZiYS04OWI2 YzMyMzE1YzIvMS9mMnZScHJCR0pjVngyREQ0ZUxIQUk0SkhRSXcubWZ0MIHRBCBG DFHS/6xyUhCj8Zl1U1kS9wP0gzCFREdGetcG3cLKMgICB84EFH8xKwnR9pDyVwC9 Xc8HyRgMXpZjAgIA5BgPMjAyNjAxMDgyMTAxMzJaMH4wfAYIKwYBBQUHMAuGcHJz eW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvYmMvMjlkYWM5 LTlhMTUtNDY2MS1hZjc4LTE1MjJlMjk2NGZjZS8xL2Z6RXJDZEgya1BKWEFMMWR6 d2ZKR0F4ZWxtTS5tZnQwgdEEIEoZODFpg9QAlydw6JYDtmG9KPMwOH50lZUGXPzo uWz/AgIHzgQUf1i8CGQS9NLFT6BwLZLOJUls5HkCAhU0GA8yMDI2MDEwODIzMDEw NlowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRv cnkvREVGQVVMVC9jYy81MzA5MzMtNTkxNS00ZmYyLWIxZjktNTAxMGQwNWY5OWE4 LzEvZjFpOENHUVM5TkxGVDZCd0xaTE9KVWxzNUhrLm1mdDCB0QQgSpTMk6O4Nitl rWxkqmsUQoq7nb6KWB07+LKbVl4Ywz8CAgfOBBR/HVjWLd1+R68hlv11S7P/JnmJ KgICF7gYDzIwMjYwMTA4MTcwMTA1WjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jw a2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzQ2LzI5MGE2MC03OTJmLTQ0 NzUtYTlmNC1lM2I5ZTBiYWU2YWIvMS9meDFZMWkzZGZrZXZJWmI5ZFV1el95WjVp U28ubWZ0MIHRBCBUQl7ggC2lGraIQxbw+rir1iII4x8LWg5ys/sm6mvySQICB84E FH/WLkLAjhYBxFceDYijSaBQnepeAgITQxgPMjAyNjAxMDgxNzAxMTNaMH4wfAYI KwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFV TFQvNzgvYjkzNGVlLWM0YmEtNDM5MS04MGIwLWU3NWE1ZWE4OWZkMS8xL2Y5WXVR c0NPRmdIRVZ4NE5pS05Kb0ZDZDZsNC5tZnQwgdEEIFoFa8a2/eSlNTOkJE9qPttQ cC6+bFpdBs9LUTO56tvYAgIHzgQUf+aLEiNL1wNDAbyWsTiq4neGCj4CAgYnGA8y MDI2MDEwODIwMDEwN1owfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUu bmV0L3JlcG9zaXRvcnkvREVGQVVMVC84Yi80YTExMTEtOGYzYy00ZWRmLWI3N2Mt MmZhMjYzMWJjMzFjLzEvZi1hTEVpTkwxd05EQWJ5V3NUaXE0bmVHQ2o0Lm1mdDCB 0QQgXnHaL4UZ+iFqZDwh8JKjKcmmeBOmCNz543yoQiwlMn8CAgfOBBR/qBajM40y dBzU//j0ndssyDj9xQICBSsYDzIwMjYwMTA4MTkwMjAxWjB+MHwGCCsGAQUFBzAL hnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzUzL2E0 NTI4YS05MGU2LTRkOTEtYTUyYy1mMDcxN2VhNDg1YzYvMS9mNmdXb3pPTk1uUWMx UF80OUozYkxNZzRfY1UubWZ0MIHRBCBlBtj8cbMdXpx/CKEWYwvo+YZAZmIOEaiK +HcvU9/M3AICCBgEFH8WgCjsDatmimfVv29TWMqr4zeoAgIMKhgPMjAyNjAxMDgy MTAxMjhaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBv c2l0b3J5L0RFRkFVTFQvY2MvYjE1Mjg2LWZkNGQtNDlmZS1hNjllLTdmYWRmNTBh MmUzNy8xL2Z4YUFLT3dOcTJhS1o5V19iMU5ZeXF2ak42Zy5tZnQwgdEEIGd7MqCU /xUEGZqKrH1XkqfN3RqCtG/L1V9L8DQYA1S1AgIHzgQUf7UOfTt/0olM+3DklGCL Snijders, et al. Expires 20 May 2027 [Page 31] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 MgzCFcECAgDQGA8yMDI2MDEwODE3MDEzNFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6 Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC85Ni9hOTE4Y2ItMjA0 NC00ZjFjLTk3MDAtOTM2MDFhMzRmNjJmLzEvZjdVT2ZUdF8wb2xNLTNEa2xHQ0xN Z3pDRmNFLm1mdDCB0QQgbJNFg5mgBHtCC8IDP0ZxfJZsrSOBp8KOJRHb520LtpEC AgfOBBR/dzTf6hIGV0EuqGfdvHuE0TK/eAICEGkYDzIwMjYwMTA4MTcwMTIxWjB+ MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9E RUZBVUxULzdlLzY4MDMyNC1lZTFmLTQwZjItODhkZi0xOTY5MzE5NjJkM2MvMS9m M2MwMy1vU0JsZEJMcWhuM2J4N2hORXl2M2cubWZ0MIHRBCBt7xqIdeziNrWHHxep 3FfwH0OPq5nSVE8fGBb8WLTWAwICB4QEFH8UzoEDt4XzUEvEsy8fTJtwzj9/AgIQ dxgPMjAyNjAxMDgxOTAxMDFaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5y aXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvYjYvZjY5ZGJlLWUwNzUtNDQzOC1i NTNiLWY2MTYwZmExZmIwMi8xL2Z4VE9nUU8zaGZOUVM4U3pMeDlNbTNET1AzOC5t ZnQwgdEEIG6nUCjrFXJF2aB9FoMk5WimDuz4GdU4rL+jK6x7dQe8AgIHzgQUf/sB FcSs3dG0rcQHN4Byas/AGvkCAgzEGA8yMDI2MDEwODE5MDExMVowfjB8BggrBgEF BQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC82 MS81MjY4ZmMtY2ZlZS00YWE4LTk3YmYtY2JlMDIwNjY1ZWZlLzEvZl9zQkZjU3Mz ZEcwcmNRSE40Qnlhc19BR3ZrLm1mdDCB0QQgb+o8m06Q9iU6EnPhdWx7hQf34aX7 u8+BtkN6WDmO8JcCAgfOBBR/tD3iN/0LaihziSMJIdJaLC7RqAICF00YDzIwMjYw MTA4MjAwMTI1WjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQv cmVwb3NpdG9yeS9ERUZBVUxULzA5L2Q0ZDEyYS1hYjRlLTRkYmEtOTVkZS1iYzYz NzEzMGRlNmUvMS9mN1E5NGpmOUMyb29jNGtqQ1NIU1dpd3UwYWcubWZ0MIHRBCBz rSMA19fNkYVSPFrfNwuIQW6pxyA/3xBmt+lL5h5xdAICB84EFH+F6ZA1Q5fjbAyp A6DGIMdwnv3NAgID6hgPMjAyNjAxMDgyMzAyMDhaMH4wfAYIKwYBBQUHMAuGcHJz eW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvNWUvNGFlMTc1 LTU1ZDAtNDg0ZC04ZDExLThjOWQ1ODIzYmFkOS8xL2Y0WHBrRFZEbC1Oc0RLa0Rv TVlneDNDZV9jMC5tZnQwgdEEIHWhirnnIDJ5n+WI2Xvk54oI9JbIb2bvBy3fY7np A/trAgIHzgQUfzE2D/wa/V8dpm2BQE5GY1EtSWcCAhVEGA8yMDI2MDEwODE4MDE1 MVowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRv cnkvREVGQVVMVC8yZC9mZWY1ZGQtMzhlZS00YmM1LTgyZmYtNTg0ZDc4YTI1Zjhj LzEvZnpFMkRfd2FfVjhkcG0yQlFFNUdZMUV0U1djLm1mdDCB0QQge+535dV/T4fB endUeAcDJiibStHT0H8cdANzm3c00sQCAgeEBBR/iyGDWJg6fXolOKnam6HzSU1x qwICAeAYDzIwMjYwMTA4MTYwMTA3WjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jw a2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxUL2Q5Lzc2Y2QwMy1lYWEyLTQ5 NjUtOTRlZi05OGRiYjY0MDJjZGQvMS9mNHNoZzFpWU9uMTZKVGlwMnB1aDgwbE5j YXMubWZ0MIHRBCCASGa4GEb+lTv/4fJr94UgLuaT+ISjkIKKdEKkHovxHwICB84E FH/uPzggc/LD5PzP/KOExbDNgmwmAgIDjBgPMjAyNjAxMDgxNzAxMTdaMH4wfAYI KwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFV TFQvYTcvOGNjZWJmLWY5ZmEtNGM0Ni1hZWU4LWNjYmZhNzM0MjRhNy8xL2YtNF9P Q0J6OHNQa19NXzhvNFRGc00yQ2JDWS5tZnQwgdEEIIEq59M4+de5vhL+AIB9ZhUC n4d3FMAGscEdEk2Nqb90AgIHzgQUfxFBauOSnfN79mpFnNOspjiR6UYCAhe3GA8y MDI2MDEwODIyMDEyOFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUu bmV0L3JlcG9zaXRvcnkvREVGQVVMVC8yZi82YjIyZTgtM2RjZC00NGRkLTk1MTQt Njc1NmY3YjBjMGRiLzEvZnhGQmF1T1NuZk43OW1wRm5OT3NwamlSNlVZLm1mdDCB 0QQgg/TeGB1EpvVQgaiS8VooOlY3CODqmdkfZl+6QeaG9IcCAgeEBBR/F7b5Mjmd WFCT0YczlOv+Gyn5jAICDzsYDzIwMjYwMTA4MTYwMTUzWjB+MHwGCCsGAQUFBzAL hnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzMxL2Nj MDIwMC1iYjJjLTQ1ZjYtYWM3NS04Mjc1NzdkZjhlZGMvMS9meGUyLVRJNW5WaFFr OUdITTVUcl9oc3AtWXcubWZ0MIHRBCCGMyVTGVLFMFffgmebFSD+ivU3zQMIPxNp Snijders, et al. Expires 20 May 2027 [Page 32] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 CZMyZaCMUAICB84EFH8+CHSJ7iOpQk1T+sIW7kuOASgOAgIXThgPMjAyNjAxMDgy MDAxMzRaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBv c2l0b3J5L0RFRkFVTFQvYzYvYzJjOTlkLWNmOTEtNGRmYi05NGRlLWE3YzYzZDU2 MmU1Ni8xL2Z6NElkSW51STZsQ1RWUDZ3aGJ1UzQ0QktBNC5tZnQwgdEEII5DEJkg 54e32y2/B1WOyDyahzCEfaERNpKcSA9PZdtHAgIHzgQUf+/r0V+8ZRSHrK9nQk9H g9Q+tCACAhe3GA8yMDI2MDEwODIxMDIwNFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6 Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC85YS8yNmVmNjMtYjcy Zi00YjNjLThkZmMtMmJjODQ1MTkyMjdhLzEvZi1fcjBWLThaUlNIcks5blFrOUhn OVEtdENBLm1mdDCB0QQgj2n88kmDKSPaKWTt2cg1Pqjq2c7bnts/AV3HJWXqqjkC AgeEBBR/mRjKtvHzXvG15YPLKDnpt0ixWAICFI8YDzIwMjYwMTA4MTkwMTU0WjB+ MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9E RUZBVUxULzI2L2RmODJmYS0xMThkLTQyMTktYmExNi0xYTk2ODNjOWQ2Y2IvMS9m NWtZeXJieDgxN3h0ZVdEeXlnNTZiZElzVmcubWZ0MIHRBCCSkQuN9PCn151nBGBr BmHej5rw8dfvnsEEW+nAvyfMjgICB4QEFH9R3x306IZ+QeXn+S3n+dH6DBVNAgIM oBgPMjAyNjAxMDgyMTAxMTlaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5y aXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvZmEvNWU3MzFmLTUyOGItNGUwMi1h ZDY4LTZkOTAzNWFmMTUzNS8xL2YxSGZIZlRvaG41QjVlZjVMZWY1MGZvTUZVMC5t ZnQwgdEEIJdpko2c2K9OwfCs7d25CWOpQ5QfTp8v4Ini0HEfstxvAgIHhAQUfwdX wzGYHgQrdHE3NSfQ9koTVrQCAhNeGA8yMDI2MDEwODE5MDEzM1owfjB8BggrBgEF BQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC83 OC80Zjk2ZjktNTY5Zi00MzNjLWI5YTgtNmEyNjEyZDQwZjUwLzEvZndkWHd6R1lI Z1FyZEhFM05TZlE5a29UVnJRLm1mdDCB0QQgnbFHY5o1eFI/JXrcZzLyJ1TdH3Z3 csXzRZinE0Y5cCsCAgfOBBR/TVkcI60saUd9f3odTOjrzulZbAICBhQYDzIwMjYw MTA4MTUwMTM1WjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQv cmVwb3NpdG9yeS9ERUZBVUxULzNlLzBkNjdhMi1iYzM2LTRiOTMtYjYwNC1kNGY1 YzkyZDkwOTUvMS9mMDFaSENPdExHbEhmWDk2SFV6bzY4N3BXV3cubWZ0MIHRBCCn jXO+nhFRAnet66plShQY9ijeKIn2Jjn8FzzN7RbFMwICCBgEFH8DofjDNP2/S3je 8MWS/wSQ3fSwAgIXcxgPMjAyNjAxMDgyMTAyMDBaMH4wfAYIKwYBBQUHMAuGcHJz eW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvNjYvM2ZlMWEw LWM2ZmQtNGJjNC1hYWUxLTllZTAwNjk0MmI0Yi8xL2Z3T2gtTU0wX2I5TGVON3d4 WkxfQkpEZDlMQS5tZnQwgdEEILygQ8fZPYY0mQD8zM4wMnIkkXbFYZks+kKXtCav jvupAgIHzgQUf0OdlCQm/Gc7J5zJirNf29fql/UCAhNTGA8yMDI2MDEwODE5MDE1 N1owfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRv cnkvREVGQVVMVC8yYS82OWEwOWYtNTgwOS00NjU2LWIzNTUtMTQ2ZjI1NGFjMTMx LzEvZjBPZGxDUW1fR2M3SjV6SmlyTmYyOWZxbF9VLm1mdDCB0QQgvgX58HkrAY/L uflVMbJZ7LzrWFSoZlhjbgUohc4JjkACAgfOBBR/QtJ8IdqGx+n79Erg5WyY89L4 CwICD1gYDzIwMjYwMTA4MTYwMjAzWjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jw a2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxUL2E5Lzk4YjAyNC05ZDhmLTQ4 NjktYTJhOS0wYWZiN2MzZmJmMzAvMS9mMExTZkNIYWhzZnAtX1JLNE9Wc21QUFMt QXMubWZ0MIHRBCC+S/81Xud1PzUBFp/H1MiaahJK+jQve1DYEWEVia39uAICB84E FH/JVqUrc1BKTx/zRUcZkpen9d6dAgILbhgPMjAyNjAxMDgxNzAxMDlaMH4wfAYI KwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFV TFQvYWEvNzFhYjY5LTY5NjUtNGI3MC05NjhkLWJiNTdhNGVmNzE1My8xL2Y4bFdw U3R6VUVwUEhfTkZSeG1TbDZmMTNwMC5tZnQwgdEEIL9qHDGaKh1R04cdIJLYSjtK eclEypWTBTqgxV51LzV0AgIIpwQUf1FerQle7ZrEyrxatK0LWGfZ8BsCAhfRGA8y MDI2MDEwODIzMDE0OVowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUu bmV0L3JlcG9zaXRvcnkvREVGQVVMVC9hNy81YzJhNTktNjAyNS00MDBlLWFiMjgt ZjBhNjI0ZDQwOTEyLzEvZjFGZXJRbGU3WnJFeXJ4YXRLMExXR2ZaOEJzLm1mdDCB Snijders, et al. Expires 20 May 2027 [Page 33] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 0QQgv39HKTjopic782oac6tVyAIMW0PaCGeYBa2nvVCuDKYCAggYBBR/4OdZNU6D zBkyA4EQneItoPGnAAICF8EYDzIwMjYwMTA4MTgwMTUyWjB+MHwGCCsGAQUFBzAL hnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzRjLzBj NzI0My0xZmZiLTQ5ZDItYjVjMS1iNDAyZThhMWQ5MzQvMS9mLURuV1RWT2c4d1pN Z09CRUozaUxhRHhwd0EubWZ0MIHRBCC/mDUwr8XbN8QR3vi4bpdyNfprvcn9Z/t2 3XZndp12IQICB4QEFH9za4igJATUMEvdrV/1UEpoM+e3AgIXtxgPMjAyNjAxMDgx OTAxMjVaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBv c2l0b3J5L0RFRkFVTFQvOTkvMGYyNWNlLWI5NzctNDg1My05ZWMzLTllNTZjYjU0 ZmVmNy8xL2YzTnJpS0FrQk5Rd1M5MnRYX1ZRU21nejU3Yy5tZnQwgdEEIMzFRfxA eVWe8poS1UkK08BGZ3h9a4zX7Upp1hcBuxHYAgIIXwQUfyuobfeHiI9vhZKoBqb/ 6jBGwHoCAhe/GA8yMDI2MDEwODIwMDExOFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6 Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC82MC81ZTY3ODYtNjM3 Ny00MjI0LWJhMDYtZGM0NzY5ZWZmMWY1LzEvZnl1b2JmZUhpSTl2aFpLb0JxYl82 akJHd0hvLm1mdDCB0QQgzZTr9egKcvXVZQaiAvwJv7MZS6kvoBECP7s1InpsFaIC AgfOBBR/0YpqSZEMwzHckRFK5ZtxhdXzDQICF7wYDzIwMjYwMTA4MTkwMjAzWjB+ MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9E RUZBVUxUL2JhLzA5NDdmMi0yMmNhLTQ3Y2ItODlhZC0zZTUwYTVmMDE5OTgvMS9m OUdLYWttUkRNTXgzSkVSU3VXYmNZWFY4dzAubWZ0MIHRBCDOHee/kR7uuSXgV8NA dqOlT3rD5l6+8gKpPOsQAIockAICB84EFH9K5X7m4KnFEB/BSoelM0FQu6tGAgIH CxgPMjAyNjAxMDgyMTAxNThaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5y aXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvMmIvMTFmYTQ0LTg4NzktNGQxOS1i NDY4LTViNWQ5OGY1MzYxZS8xL2YwcmxmdWJncWNVUUg4RktoNlV6UVZDN3EwWS5t ZnQwgdEEINQB8UTqGOQVuKymbJF9l032P1avGA5HYUZOzZBlJUOpAgIHzgQUf2qO XVXCSYqCY2+Z+PyeMZ4Hdx4CAhC8GA8yMDI2MDEwODIxMDE1NlowfjB8BggrBgEF BQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC83 NC8yN2ZjZTEtMTFjZS00YTMyLWE2NDktZTA3NmI1MTcyMWFkLzEvZjJxT1hWWENT WXFDWTItWi1QeWVNWjRIZHg0Lm1mdDCB0QQg1SElzrrX16Q+poOs2aDApHsXvKrq fpGpM/emj5l2WlUCAgfOBBR/HQ4ymL7Tp/Ofs7JE7ZGL9sTXvwICFZEYDzIwMjYw MTA4MjAwMTMyWjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2kucmlwZS5uZXQv cmVwb3NpdG9yeS9ERUZBVUxUL2Y3L2U2NTA2ZS03Njg1LTQ4ZTctYTU4My0yMWFm M2RlZThlZTkvMS9meDBPTXBpLTA2ZnpuN095Uk8yUmlfYkUxNzgubWZ0MIHRBCDZ 3cCnM1f1TWqRljN/6JJMPxp4i98OoQ/iByRh11U2bAICB84EFH811a5Bf0XuhQXX bOqhs0xFg5SgAgIQlRgPMjAyNjAxMDgxNzAxMDVaMH4wfAYIKwYBBQUHMAuGcHJz eW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvZTYvYzU0Njdi LTM5NjItNGI3NC1hZTBkLTM0NDczYmM5MWQ4MC8xL2Z6WFZya0ZfUmU2RkJkZHM2 cUd6VEVXRGxLQS5tZnQwgdEEINySvZqi93Y/d9zNNx6gq0dxUhmQuVj1t4LKdJ+X tT5eAgIHhAQUf35evW+kacXjcL/BBsTUqtHh25QCAhAjGA8yMDI2MDEwODIxMDEx NFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRv cnkvREVGQVVMVC8yMy9jM2U4ZWQtNTk3YS00ODVhLTk0YTMtOTgyY2ZiMzU5YWVl LzEvZjM1ZXZXLWthY1hqY0xfQkJzVFVxdEhoMjVRLm1mdDCB0QQg4BXwVc2t3CYG ZHmeWUo+F2MGbMmIsMpazuR20W1ttMgCAgfOBBR/m0z9ybDZ48MeDruB5vGxy73J 5AICDZsYDzIwMjYwMTA4MjMwMTAwWjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jw a2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzViLzgyNDZlYi04NDY5LTQy ZGYtYTA4Zi05MGM0MjFmNTVhZGIvMS9mNXRNX2NtdzJlUERIZzY3Z2VieHNjdTl5 ZVEubWZ0MIHRBCDju+/+aQNhL3xABcZCmQwPlJsSt9PVczuiI1LEhh0V9gICB4QE FH8pZlevjQDCX9dfVuzIoos1FQV1AgIQ8BgPMjAyNjAxMDgyMjAxMzJaMH4wfAYI KwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFV TFQvZDAvZTgwYjMzLTNiZWUtNDZlYy1iMzVkLWJhZjk1YTUwNmQxOS8xL2Z5bG1W Snijders, et al. Expires 20 May 2027 [Page 34] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Ni1OQU1KZjExOVc3TWlpaXpVVkJYVS5tZnQwgdEEIOhXNpfSOMASGctVcKbvN/OB 6ql5D1pQacHPcCY/ZHiyAgIIGAQUf/G4HP5quxGOl+AyW2Yur5hPL2oCAg4nGA8y MDI2MDEwODE4MDExNFowfjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUu bmV0L3JlcG9zaXRvcnkvREVGQVVMVC83NS8xODZhMTgtNWQ3Zi00M2VkLWIwNmEt Y2VhN2ViMzUwNTM3LzEvZl9HNEhQNXF1eEdPbC1BeVcyWXVyNWhQTDJvLm1mdDCB 0QQg7ofzO61BsU/Hy5uia4RYPFpIBkpqq5VsbWs8rtg3Ff8CAgfOBBR/F4+vZAHi 83FuMXZFad9zHfWPIgICEi4YDzIwMjYwMTA4MTUwMTA4WjB+MHwGCCsGAQUFBzAL hnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzY2LzFi Nzk2OC1jYTRkLTQ1ZjQtYjY3MS0yZTdmNzg0ODljZDMvMS9meGVQcjJRQjR2Tnhi akYyUlduZmN4MzFqeUkubWZ0MIHRBCDu2djmK3gbyPBqskEsLEV+na+Ot0G2TJur k/7Nc14YQQICB84EFH8km5VEYgaD+Us4inVRpopkk+0SAgID6xgPMjAyNjAxMDgx ODAxNDBaMH4wfAYIKwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBv c2l0b3J5L0RFRkFVTFQvOGIvN2FhMDRlLTQ4MDctNDk4OC05MTAzLTg0MjM5N2Uz MDY0My8xL2Z5U2JsVVJpQm9QNVN6aUtkVkdtaW1TVDdSSS5tZnQ= B.3. Example ErikSegmentIndex This object was retrieved from https://miso.sobornost.net/.well- known/erik/segmentindex/rpki.ripe.net MIGsBgsqhkiG9w0BCRABO6CBnDCBmRYNcnBraS5yaXBlLm5ldBgPMjAyNjA3MjEw NzE5MTRaMAsGCWCGSAFlAwQCATBqMDMYDzIwMjYwNzIxMDcyMDAwWgQguNBbTBoe zZhz2dMs1ZmDiCtE0NEywGnOvc4nrH8ynxUwMxgPMjAyNjA3MjEwNzI1MDBaBCDB doo/n2Nc0xyGtn3PuZhFjpaHHQIffUWi0P34uDag7Q== Acknowledgements This protocol is named after Erik Bais, who passed away in 2024, as a small token of appreciation for his friendship. The authors wish to thank George Michaelson, Theo de Raadt, Bob Beck, Theo Buehler, William McCall, Jasdip Singh, Michael Hollyman, Mike Bishop, Kamiel Braet, Loganaden Velvindron, Lancheng Qin, and Dirk Doesburg for the lovely conversations that led to this proposal. The authors wish to thank Sean Turner and Russ Housley for their review of the ASN.1 notation. Job Snijders is partly funded by the NGI0 Commons Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet under grant agreement No 101135429. Authors' Addresses Job Snijders BSD Software Development Amsterdam The Netherlands Snijders, et al. Expires 20 May 2027 [Page 35] Internet-Draft Erik Synchronization Protocol for RPKI November 2026 Email: job@bsd.nl URI: https://www.bsd.nl/ Tim Bruijnzeels RIPE NCC The Netherlands Email: tim@ripe.net Tom Harrison APNIC Australia Email: tomh@apnic.net Wataru Ohgai JPNIC Japan Email: alt@nic.ad.jp Snijders, et al. Expires 20 May 2027 [Page 36]