<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" docName="draft-ietf-sidrops-rpki-erik-protocol-08" ipr="trust200902" xml:lang="en" sortRefs="true" submissionType="IETF" consensus="true" symRefs="true" tocInclude="true" version="3">
  <front>
    <title abbrev="Erik Synchronization Protocol for RPKI">
      The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI)
    </title>
    <author fullname="Job Snijders" initials="J." surname="Snijders">
      <organization abbrev="BSD">BSD Software Development</organization>
      <address>
        <postal>
          <postalLine>Amsterdam</postalLine>
          <postalLine>The Netherlands</postalLine>
        </postal>
        <email>job@bsd.nl</email>
        <uri>https://www.bsd.nl/</uri>
      </address>
    </author>
    <author fullname="Tim Bruijnzeels" initials="T." surname="Bruijnzeels">
      <organization>RIPE NCC</organization>
      <address>
        <postal>
          <postalLine>The Netherlands</postalLine>
        </postal>
        <email>tim@ripe.net</email>
      </address>
    </author>
    <author fullname="Tom Harrison" initials="T." surname="Harrison">
      <organization>APNIC</organization>
      <address>
        <postal>
          <country>AU</country>
        </postal>
        <email>tomh@apnic.net</email>
      </address>
    </author>
    <author fullname="Wataru Ohgai" initials="W." surname="Ohgai">
      <organization>JPNIC</organization>
      <address>
        <postal>
          <country>JP</country>
        </postal>
        <email>alt@nic.ad.jp</email>
      </address>
    </author>
    <date/>
    <area>Operations and Management Area (OPS)</area>
    <workgroup>SIDROPS</workgroup>
    <keyword>Data synchronization</keyword>
    <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.
        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.
      </t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro">
      <name>Introduction</name>
      <t>
        This document specifies the Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI) <xref target="RFC6480"/>.
        Erik Synchronization can be characterized as a data replication system using Merkle trees <xref target="M1987"/>, a content-addressable naming scheme <xref target="RFC6920"/>, concurrency control using monotonically increasing sequence numbers <xref target="RFC0677"/>, and HTTP transport <xref target="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 (<xref target="RFC5781"/> and <xref target="RFC8182"/>).
        The protocol's design is intended to be efficient, fast, easy to implement <xref target="RFC1925"/>, and robust in the face of partitions or faults in the network.
      </t>
      <section>
        <name>Background</name>
        <t>
          The notion of cache-to-cache data replication of unvalidated data was documented in <xref target="RFC7115" section="3"/>.
        </t>
        <blockquote quotedFrom="RFC7115, section 3">
          <t>
             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.
          </t>
        </blockquote>
        <t>
          Historic records show that experiments have been performed in this space using, for example, peer-to-peer file sharing technology (see <xref target="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.
        </t>
      </section>
      <section anchor="reqs-lang">
        <name>Requirements Language</name>
        <t>
          The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
      </section>
      <section anchor="Related">
        <name>Related Work</name>
        <t>
          The reader is assumed to be familiar with the terms and concepts described in
          "<xref target="RFC0677" format="title"/>" <xref target="RFC0677" format="default"/>,
          "<xref target="RFC6480" format="title"/>" <xref target="RFC6480" format="default"/>,
          "<xref target="RFC8182" format="title"/>" <xref target="RFC8182" format="default"/>,
          "<xref target="RFC9286" format="title"/>" <xref target="RFC9286" format="default"/>,
          "<xref target="M1987" format="title"/>" <xref target="M1987" format="default"/>.
        </t>
      </section>
      <section anchor="glossary">
        <name>Glossary</name>
        <t>
          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.
        </t>
        <dl>
          <dt>Erik relay</dt>
          <dd>An intermediate between CA publication repositories and Relying Parties.</dd>
          <dt>FQDN</dt>
          <dd>The fully qualified domain name of an RPKI repository instance referenced by the mandatory rsync URI in an end-entity certificate's Subject Information Access (SIA) extension's id-ad-signedObject accessDescription.</dd>
          <dt>Hash</dt>
          <dd>A message digest calculated for an object using the SHA-256 algorithm.</dd>
          <dt>ErikIndex</dt>
          <dd>The relay's Merkle root for a given FQDN. An ErikIndex is an ordered listing of ErikPartition object hashes.</dd>
          <dt>ErikPartition</dt>
          <dd>An ordered listing of the manifest objects' hashes, manifestNumber values, thisUpdate values, and their certificates' SIA extension values.</dd>
          <dt>ErikSegmentIndex</dt>
          <dd>An ordered listing of the relay's segment buffers and associated ErikIndex objects object hashes.</dd>
        </dl>
      </section>
    </section>
    <section anchor="overview">
      <name>Informal Overview</name>
      <t>
        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.
      </t>
      <t>
        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 <tt>ErikPartition</tt> 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.
      </t>
      <t>
        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 <em>manifestNumber</em> sequence number and <em>thisUpdate</em> for each 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).
      </t>
    </section>
    <section anchor="asn1">
      <name>Erik Synchronization Data Structure Definitions</name>
      <t>
        The messages used in this protocol to construct and determine synchronization states are encoded following Distinguished Encoding Rules (DER) <xref target="X.690"/>.
      </t>
      <t>
        <tt>ErikIndex</tt>, <tt>ErikPartition</tt>, and <tt>ErikSegmentIndex</tt> objects are formally defined as follows:
      </t>
      <sourcecode type="asn.1" markers="false">

&lt;CODE BEGINS&gt;

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.&amp;id({ContentSet}),
  content      [0] EXPLICIT
                   CONTENT-TYPE.&amp;Type({ContentSet}{@contentType}) }

ContentSet CONTENT-TYPE ::= {
  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,
  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
&lt;CODE ENDS&gt;

</sourcecode>
      <section anchor="genstructure">
        <name>General Syntax</name>
        <t>
          At the top level the content of an Erik object is an instance of <tt>ContentInfo</tt>.
        </t>
        <section>
          <name>contentType</name>
          <t>
            The <tt>contentType</tt> is an OID specifying the type of payload in the object, in this profile either <tt>id-ct-rpkiErikIndex</tt>, <tt>id-ct-rpkiErikPartition</tt>, or <tt>id-ct-rpkiErikSegmentIndex</tt>.
          </t>
        </section>
        <section>
          <name>content</name>
          <t>
            The <tt>content</tt> field contains an instance of <tt>ErikIndex</tt>, <tt>ErikPartition</tt>, or <tt>ErikSegmentIndex</tt>.
          </t>
        </section>
      </section>
      <section anchor="asn1-index">
        <name>ErikIndex</name>
        <t>
          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.
        </t>
        <t>
          See <xref target="ex_index"/> for an example <tt>ErikIndex</tt> object.
        </t>
        <section title="The version field">
          <t>
            The version number of the ErikIndex object <bcp14>MUST</bcp14> be 0.
          </t>
        </section>
        <section title="The indexScope field">
          <t>
            The <tt>indexScope</tt> 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 <xref target="RFC1034" section="3.5"/> and modified by <xref target="RFC1123" section="2.1"/>.
          </t>
        </section>
        <section title="The indexTime field">
          <t>
            The <tt>indexTime</tt> is the most recent <tt>partitionTime</tt> value among the ErikPartitions referenced from the ErikIndex at hand.
            Use of the most recent <tt>partitionTime</tt> 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.
          </t>
          <t>
            For the purposes of this profile, <tt>GeneralizedTime</tt> 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 <xref target="RFC5280" section="4.1.2.5.2"/>.
          </t>
        </section>
        <section title="The hashAlg field">
          <t>
            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 <xref target="RFC7935"/>.
          </t>
        </section>
        <section title="The partitionList field">
          <t>
            This field is a sequence of <tt>PartitionRef</tt> instances.
            There is one <tt>PartitionRef</tt> for each current ErikPartition.
            Each <tt>PartitionRef</tt> is a tuple consisting of the hash of the partition object and the size of the partition object.
            The fixed maximum size of the <tt>partitionList</tt> of 256 partitions scales efficiently because partitions track aggregate Manifest objects rather than tracking individual, separate RPKI objects.
          </t>
          <t>
            Information elements are unique with respect to one another and sorted in ascending order of the hash.
          </t>
        </section>
      </section>
      <section anchor="asn1-partition">
        <name>ErikPartition</name>
        <t>
          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 <tt>ManifestRef</tt> 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.
        </t>
        <t>
          See <xref target="ex_part"/> for an example <tt>ErikPartition</tt> object.
        </t>
        <section title="The version field">
          <t>
            The version number of the ErikPartition object <bcp14>MUST</bcp14> be 0.
          </t>
        </section>
        <section title="The partitionTime field">
          <t>
            The <tt>partitionTime</tt> is the most recent <tt>thisUpdate</tt> value among the manifests referenced from the ErikPartition at hand.
            Use of the most recent manifest <tt>thisUpdate</tt> 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.
          </t>
          <t>
            For the purposes of this profile, <tt>GeneralizedTime</tt> 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 <xref target="RFC5280" section="4.1.2.5.2"/>.
          </t>
        </section>
        <section title="The hashAlg field">
          <t>
            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 <xref target="RFC7935"/>.
          </t>
        </section>
        <section title="The manifestList field">
          <t>
            This field is a sequence of <tt>ManifestRef</tt> instances.
            There is one <tt>ManifestRef</tt> 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 <xref target="RFC9286" section="4.2.1"/>).
          </t>
          <t>
            A <tt>ManifestRef</tt> 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 <tt>AccessDescription</tt> instances from the manifest's End-Entity certificate's Subject Information Access extension.
          </t>
          <t>
            Information elements are unique with respect to one another and sorted in ascending order of the hash.
          </t>
        </section>
      </section>
      <section anchor="asn1-segmentindex">
        <name>ErikSegmentIndex</name>
        <t>
          An <tt>ErikSegmentIndex</tt> represents segments that contain RPKI objects that a relay discovered in a short time window.
        </t>
        <t>
          See <xref target="segmentpf"/> on how these are used and <xref target="ex_segidx"/> for an example <tt>ErikSegmentIndex</tt> object.
        </t>
        <section title="The version field">
          <t>
            The version number of the <tt>ErikSegmentIndex</tt> object <bcp14>MUST</bcp14> be 0.
          </t>
        </section>
        <section title="The segmentScope field">
          <t>
            The <tt>segmentScope</tt> field contains the fully qualified domain name of the Signed Object locations referenced through this particular <tt>ErikSegmentIndex</tt>.
            The FQDN <bcp14>MUST</bcp14> be in the "preferred name syntax", as specified by <xref target="RFC1034" section="3.5"/> and modified by <xref target="RFC1123" section="2.1"/>.
          </t>
        </section>
        <section title="the segmentIndexTime field" anchor="segmentIndexTime">
          <t>
            The <tt>segmentIndexTime</tt> is the most recent <tt>partitionTime</tt> value among the <tt>ErikPartitions</tt> contained within the segments referenced from the <tt>ErikSegmentIndex</tt> 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.
          </t>
          <t>
            For the purposes of this profile, <tt>GeneralizedTime</tt> 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 <xref target="RFC5280" section="4.1.2.5.2"/>.
          </t>
        </section>
        <section title="the hashAlg field">
          <t>
            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 <xref target="RFC7935"/>.
          </t>
        </section>
        <section title="the segmentList field">
          <t>
            This field is a sequence of <tt>SegmentRef</tt> instances.
            There is one <tt>SegmentRef</tt> for each current segment.
          </t>
          <t>
            A <tt>SegmentRef</tt> is a SEQUENCE consisting of a segment identifier and a hash.
            The segment identifier is expressed as a <tt>GeneralizedTime</tt> and indicates the moment in time the segment was initialized.
            The hash in the <tt>index</tt> field is the message digest calculated over the last <tt>ErikIndex</tt> associated with the segment.
          </t>
          <t>
            Information elements are unique with respect to one another and sorted in ascending order of the <tt>segment</tt> identifier.
          </t>
        </section>
      </section>
    </section>
    <section anchor="rp">
      <name>Client-side Processing</name>
      <t>
        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 <tt>id-ad-rpkiManifest</tt> <tt>AccessDescription</tt>.
        If the FQDN has not yet been processed, the client proceeds with Erik synchronization for that FQDN as described below.
      </t>
      <t>
        For each such FQDN, clients acquire and process an <tt>ErikIndex</tt>, which represents the relay's current Merkle tree head for a given FQDN.
        A client <bcp14>MUST</bcp14> verify the requested FQDN exactly matches the <tt>indexScope</tt> value in the <tt>ErikIndex</tt>, and if not proceed to use a different relay.
      </t>
      <t>
        Then, clients can decide whether or not to fetch <tt>ErikPartition</tt> objects listed on the <tt>ErikIndex</tt>, for instance, by checking whether the object associated with the hash was already fetched at some point in the client's past.
      </t>
      <t>
        Before using a <tt>ErikPartition</tt>, the client <bcp14>MUST</bcp14> verify that all URIs in the accessLocations in the id-ad-signedObject accessMethod instances in the <tt>ErikPartition</tt> are encompassed in the requested <tt>indexScope</tt>.
        A client can then decide whether or not to fetch a given manifest object, by comparing the <tt>manifestNumber</tt> and <tt>thisUpdate</tt> with what's locally cached and what's offered by the remote relay.
      </t>
      <t>
      A URI is encompassed by an <tt>indexScope</tt> if, after URI parsing and DNS name normalization, the URI host component is exactly equal to the <tt>indexScope</tt> value.
      Comparisons are case-insensitive. 
      A trailing root label MUST NOT be present in an <tt>indexScope</tt>. 
      Implementations MUST NOT use substring or suffix matching.
      </t>
      <t>
        A client can compute which products listed in the manifest's <tt>fileList</tt> need to be fetched from one relay or another in order to achieve a successful fetch.
        A client <bcp14>MUST</bcp14> 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 <tt>indexScope</tt>.
      </t>
      <t>
        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.
      </t>
      <t>
        Clients <bcp14>SHOULD</bcp14> use HTTPS, unless the local system is unable to establish TLS connections to any of its configured Erik relays.
      </t>
    </section>
    <section anchor="querying">
      <name>Querying an Erik Relay</name>
      <t>
        Client-side retrieval requires nothing other than the <tt>GET</tt> request method (<xref target="RFC9110" section="9.3.1"/>).
      </t>
      <section title="Fetching ErikIndex objects">
        <t>
          The URIs to fetch ErikIndex objects can be constructed using the following Well-Known URI template with the relay's hostname as authority, the <tt>erik</tt> keyword as suffix, the string <tt>/index/</tt>, followed by a FQDN as parameter, i.e.: <tt>https://{relay_hostname}/.well-known/erik/index/{FQDN}</tt>.
        </t>
        <t>
          As an example, the URI to fetch an <tt>ErikIndex</tt> for the <tt>rpki.ripe.net</tt> FQDN from a relay at <tt>relay.example.net</tt> would be:
        </t>
        <t>
          <tt>https://relay.example.net/.well-known/erik/index/rpki.ripe.net</tt>
        </t>
        <t>
          Clients <bcp14>SHOULD</bcp14> use conditional <tt>GET</tt> requests (<xref target="RFC9110" section="13"/>) for fetching <tt>ErikIndex</tt> objects, because <tt>HEAD</tt> requests incur a latency penalty due to redundant round-trips.
          Responses to requests for paths starting with <tt>/.well-known/erik/index/</tt> are mutable.
        </t>
      </section>
      <section title="Fetching objects by hash">
        <t>
          This specification uses "Named Information" identifiers mapped to <tt>.well-known</tt> HTTP/HTTPS URLs for object retrieval, as described in <xref target="RFC6920"/>.
        </t>
        <t>
          For example, issuance <tt>#54</tt> of <tt>ripe-ncc-ta.mft</tt> has the following SHA256 digest: <tt>c2d0427bc5a32c42eea1ab5663d592b1fc29c7d4ef16ab0b5e1d631d039dcc21</tt>.
          The aforementioned digest encoded using base64url encoding is <tt>wtBCe8WjLELuoatWY9WSsfwpx9TvFqsLXh1jHQOdzCE</tt>.
        </t>
        <t>
          To fetch the aforementioned object from a relay hosted at <tt>relay.example.net</tt>, a client would access the following HTTP URL:
        </t>
        <t>
          <tt>https://relay.example.net/.well-known/ni/sha-256/wtBCe8WjLELuoatWY9WSsfwpx9TvFqsLXh1jHQOdzCE</tt>
        </t>
        <t>
          Responses to requests for paths starting with <tt>/.well-known/ni/</tt> are immutable.
        </t>
      </section>
    </section>
    <section anchor="prefetching">
      <name>Prefetching Objects in Bulk</name>
      <t>
        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.
      </t>
      <t>
        This section outlines the general structure of prefetch request responses and defines various <tt>.well-known/erik/</tt> endpoints.
      </t>
      <section>
        <name>General Structure of Prefetch Responses</name>
        <t>
          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.
          <!-- FYI - I don't consider this a problem, but this also means that if any objects in the prefetching stream are not well-formed, it may not be possible to reliably decode the rest of the stream. -->
        </t>
        <t>
          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, <tt>ErikIndex</tt> objects, and <tt>ErikPartition</tt> 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.
        </t>
        <t>
          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, sending many individual requests for each and every object increases network overhead and latency.
          As a rule of thumb: <xref target="snappf">FQDN Snapshots</xref> are useful for clients with no prior state and <xref target="segmentpf">Segments</xref> are useful in the steady state (when synchronizing every few minutes).
        </t>
      </section>
      <section anchor="snappf">
        <name>Prefetching Using Snapshot Buffers</name>
        <t>
          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 <bcp14>MUST</bcp14> perform a tree comparison after fetching a snapshot buffer.
        </t>
        <t>
          To avoid wasting resources, relays <bcp14>SHOULD NOT</bcp14> delay snapshot buffer production by more than one hour.
        </t>
        <t>
          As an example, the URI to fetch a snapshot buffer for the <tt>rpki.ripe.net</tt> FQDN from a relay at <tt>relay.example.net</tt> would be:
        </t>
        <t>
	  <tt>https://relay.example.net/.well-known/erik/snapshot/rpki.ripe.net</tt>
        </t>
        <t>
          Responses to requests for paths starting with <tt>/.well-known/erik/snapshot/</tt> are mutable.
        </t>
        <t>
          To avoid wasting resources, relays <bcp14>SHOULD NOT</bcp14> include <tt>ErikIndex</tt>, <tt>ErikPartition</tt>, and <tt>ErikSegmentIndex</tt> objects in snapshot buffers.
          Clients <bcp14>MUST</bcp14> discard any <tt>ErikIndex</tt>, <tt>ErikPartition</tt>, and <tt>ErikSegmentIndex</tt> objects contained in snapshot buffers.
        </t>
      </section>
      <section anchor="segmentpf">
        <name>Prefetching Using Segment Buffers</name>
        <t>
          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.
        </t>
        <t>
          Relay implementations are <bcp14>RECOMMENDED</bcp14> to start a new segment buffer every 5 minutes.
        </t>
        <t>
          A client starts by fetching the <tt>ErikSegmentIndex</tt> (<xref target="asn1-segmentindex"/>) to discover the available segment buffers on the relay.
        </t>
        <section title="Segment Discovery">
          <t>
            The URIs to fetch <tt>ErikSegmentIndex</tt> objects can be constructed using the following Well-Known URI template with the relay's hostname as authority, the <tt>erik</tt> keyword as suffix, the string <tt>/segmentindex/</tt>, followed by a FQDN as parameter, i.e.:
          </t>
          <t>
            <tt>https://{relay_hostname}/.well-known/erik/segmentindex/{FQDN}</tt>
          </t>
          <t>
            As an example, the URI to fetch an <tt>ErikSegmentIndex</tt> for the <tt>rpki.ripe.net</tt> FQDN from a relay at <tt>relay.example.net</tt> would be:
          </t>
          <t>
            <tt>https://relay.example.net/.well-known/erik/segmentindex/rpki.ripe.net</tt>
          </t>
          <t>
            Clients <bcp14>SHOULD</bcp14> use conditional <tt>GET</tt> requests (<xref target="RFC9110" section="13"/>) for fetching <tt>ErikSegmentIndex</tt> objects, because <tt>HEAD</tt> requests incur a latency penalty due to redundant round-trips.
            Responses to requests for paths starting with <tt>/.well-known/erik/segmentindex/</tt> are mutable.
          </t>
        </section>
        <section title="Segment Buffers">
          <t>
            The URIs to fetch the segment buffers are constructed by transforming the <tt>segmentIndexTime</tt> (<xref target="segmentIndexTime"/>) 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 <tt>/.well-known/erik/segment/</tt> are mutable.
          </t>
          <t>
            As an example, the URI to fetch the segment buffer for <tt>rpki.ripe.net</tt> starting at Jun 4th, 2026, 15:50:00 UTC from a relay at <tt>relay.example.net</tt> would be:
          </t>
          <t>
            <tt>https://relay.example.net/.well-known/erik/segment/rpki.ripe.net/1780588200</tt>
          </t>
        </section>
      </section>
    </section>
    <section anchor="error">
      <name>Transport Error Detection and Handling</name>
      <t>
        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 <em>failed fetch</em> (see <xref target="RFC9286" section="6.6"/>) and try again at a later point in time in a next validation run.
      </t>
    </section>
    <section anchor="relay">
      <name>Setting Up an Erik Relay</name>
      <t>
        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.
      </t>
      <t>
        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 (<xref target="RFC5781"/>) and RRDP (<xref target="RFC8182"/>).
      </t>
    </section>
    <section anchor="operational">
      <name>Operational Considerations</name>
      <section>
        <name>Scaling considerations</name>
        <t>
          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.
        </t>
      </section>
      <section>
        <name>HTTP Version Recommendations</name>
        <t>
          In this protocol clients might need to retrieve many individual objects simultaneously from relays.
          In non-multiplexed transports like HTTP/1.1 (<xref target="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 (<xref target="RFC9113"/>) and HTTP/3 (<xref target="RFC9114"/>) natively support stream multiplexing (discussed in <xref target="RFC9205" section="4.11"/>) and field/header compression (HPACK <xref target="RFC7541"/>, QPACK <xref target="RFC9204"/>).
          Therefore use of HTTP/2 and HTTP/3 is <bcp14>RECOMMENDED</bcp14> to facilitate high-concurrency, low-latency object retrieval.
        </t>
      </section>
      <section>
        <name>HTTP Compression</name>
        <t>
          Using gzip compression on average tends to yield a 20% reduction in size when fetching individual objects and 50% for Prefetch responses.
          Therefore, clients <bcp14>MUST</bcp14> support gzip content coding (<xref target="RFC9110" section="8.4.1.3"/>) and the server <bcp14>MAY</bcp14> assume it without explicit negotiation.
          Clients <bcp14>SHOULD</bcp14> send an <tt>Accept-Encoding</tt> header field in the request, which permits the negotiation of other compression schemes as well.
        </t>
        <t>
          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 <tt>Available-Dictionary</tt> request header, using a previously fetched version of the RPKI object as the dictionary.
          It is <bcp14>RECOMMENDED</bcp14> for clients and relays to make use of Compression Dictionary Transport (<xref target="RFC9842"/>).
        </t>
      </section>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>
        This document makes no changes to RPKI certificate validation procedures.
      </t>
      <t>
        Paraphrasing <xref target="RFC6810" section="11"/>:
        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 <xref target="RFC8182" section="5"/> for more security considerations.
      </t>
      <t>
        To avoid certain forms of attack, clients <bcp14>MUST</bcp14> check whether <tt>indexScope</tt>, <tt>segmentScope</tt>, <tt>ManifestRef</tt> location values, and manifest Subject Information Access (SIA) extensions match the expected FQDN.
      </t>
      <t>
        Byzantine events or faults in relay-to-client communication can be overcome by the client rotating requests for objects among different relays.
      </t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <section title="S/MIME Module Identifier">
        <t>
          The IANA is requested to add an item to the "SMI Security for S/MIME Module Identifier" registry as follows:
        </t>
        <artwork>
<![CDATA[
Decimal  Description                          References
----------------------------------------------------------
  TDB    id-mod-rpkiErikSynchronization-2025  [this_document]
]]>
        </artwork>
      </section>
      <section title="SMI Security for S/MIME CMS Content Type">
        <t>
          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:
        </t>
        <artwork>
<![CDATA[
Decimal  Description                 References
----------------------------------------------------
   55    id-ct-rpkiErikIndex         [this_document]
   56    id-ct-rpkiErikPartition     [this_document]
   59    id-ct-rpkiErikSegmentIndex  [this_document]
]]>
        </artwork>
        <t>
          Upon publication of this document, IANA is requested to reference the RFC publication instead of this draft.
        </t>
      </section>
      <section title="Well-Known URI">
        <t>
          IANA is requested to assign an URI Suffix for Erik Synchronization in the Well-Known URIs registry as follows.
        </t>
        <dl spacing="compact">
          <dt>URI Suffix</dt>
          <dd>
            <tt>erik</tt></dd>
          <dt>Reference:</dt>
          <dd>[this draft]</dd>
          <dt>Status:</dt>
          <dd>permanent</dd>
          <dt>Change Controller:</dt>
          <dd>IETF</dd>
          <dt>Related Information</dt>
          <dd>-</dd>
        </dl>
        <section removeInRFC="true" toc="exclude">
          <name>Protocol Registries Request at Github</name>
          <t>
            See https://github.com/protocol-registries/well-known-uris/issues/67 for a copy of this request.
          </t>
        </section>
      </section>
      <section>
        <name>Media Types</name>
        <t>
          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.
        </t>
        <section toc="exclude">
          <name>ErikIndex Media Type</name>
          <dl spacing="compact">
            <dt>Type name:</dt>
            <dd>application</dd>
            <dt>Subtype name:</dt>
            <dd>rpki-erikindex</dd>
            <dt>Required parameters:</dt>
            <dd>N/A</dd>
            <dt>Optional parameters:</dt>
            <dd>N/A</dd>
            <dt>Encoding considerations:</dt>
            <dd>binary</dd>
            <dt>Security considerations:</dt>
            <dd>This media type contains no active content.</dd>
            <dt>Interoperability considerations:</dt>
            <dd>N/A</dd>
            <dt>Published specification:</dt>
            <dd>[this_document]</dd>
            <dt>Applications that use this media type:</dt>
            <dd>Tools for RPKI operators</dd>
            <dt>Fragment identifier considerations:</dt>
            <dd>N/A</dd>
            <dt>Additional information:</dt>
            <dd>
              <dl spacing="compact">
                <dt><br/></dt>
                <dd/>
                <dt>Content:</dt>
                <dd>This media type is a RPKI ErikIndex object, as defined in [this_document].</dd>
                <dt>Magic number(s):</dt>
                <dd>N/A</dd>
                <dt>File extension(s):</dt>
                <dd>N/A</dd>
                <dt>Macintosh file type code(s):</dt>
                <dd>N/A</dd>
              </dl>
            </dd>
            <dt>Person &amp; email address to contact for further information:</dt>
            <dd>Job Snijders (job@bsd.nl)</dd>
            <dt>Intended usage:</dt>
            <dd>COMMON</dd>
            <dt>Restrictions on usage:</dt>
            <dd>N/A</dd>
            <dt>Author:</dt>
            <dd>Job Snijders (job@bsd.nl)</dd>
            <dt>Change controller:</dt>
            <dd>IETF</dd>
          </dl>
        </section>
        <section toc="exclude">
          <name>ErikPartition Media Type</name>
          <dl spacing="compact">
            <dt>Type name:</dt>
            <dd>application</dd>
            <dt>Subtype name:</dt>
            <dd>rpki-erikpartition</dd>
            <dt>Required parameters:</dt>
            <dd>N/A</dd>
            <dt>Optional parameters:</dt>
            <dd>N/A</dd>
            <dt>Encoding considerations:</dt>
            <dd>binary</dd>
            <dt>Security considerations:</dt>
            <dd>This media type contains no active content.</dd>
            <dt>Interoperability considerations:</dt>
            <dd>N/A</dd>
            <dt>Published specification:</dt>
            <dd>[this_document]</dd>
            <dt>Applications that use this media type:</dt>
            <dd>Tools for RPKI operators</dd>
            <dt>Fragment identifier considerations:</dt>
            <dd>N/A</dd>
            <dt>Additional information:</dt>
            <dd>
              <dl spacing="compact">
                <dt><br/></dt>
                <dd/>
                <dt>Content:</dt>
                <dd>This media type is a RPKI ErikPartition object, as defined in [this_document].</dd>
                <dt>Magic number(s):</dt>
                <dd>N/A</dd>
                <dt>File extension(s):</dt>
                <dd>N/A</dd>
                <dt>Macintosh file type code(s):</dt>
                <dd>N/A</dd>
              </dl>
            </dd>
            <dt>Person &amp; email address to contact for further information:</dt>
            <dd>Job Snijders (job@bsd.nl)</dd>
            <dt>Intended usage:</dt>
            <dd>COMMON</dd>
            <dt>Restrictions on usage:</dt>
            <dd>N/A</dd>
            <dt>Author:</dt>
            <dd>Job Snijders (job@bsd.nl)</dd>
            <dt>Change controller:</dt>
            <dd>IETF</dd>
          </dl>
        </section>
        <section toc="exclude">
          <name>ErikSegmentIndex Media Type</name>
          <dl spacing="compact">
            <dt>Type name:</dt>
            <dd>application</dd>
            <dt>Subtype name:</dt>
            <dd>rpki-eriksegmentindex</dd>
            <dt>Required parameters:</dt>
            <dd>N/A</dd>
            <dt>Optional parameters:</dt>
            <dd>N/A</dd>
            <dt>Encoding considerations:</dt>
            <dd>binary</dd>
            <dt>Security considerations:</dt>
            <dd>This media type contains no active content.</dd>
            <dt>Interoperability considerations:</dt>
            <dd>N/A</dd>
            <dt>Published specification:</dt>
            <dd>[this_document]</dd>
            <dt>Applications that use this media type:</dt>
            <dd>Tools for RPKI operators</dd>
            <dt>Fragment identifier considerations:</dt>
            <dd>N/A</dd>
            <dt>Additional information:</dt>
            <dd>
              <dl spacing="compact">
                <dt><br/></dt>
                <dd/>
                <dt>Content:</dt>
                <dd>This media type is a RPKI ErikSegmentIndex object, as defined in [this_document].</dd>
                <dt>Magic number(s):</dt>
                <dd>N/A</dd>
                <dt>File extension(s):</dt>
                <dd>N/A</dd>
                <dt>Macintosh file type code(s):</dt>
                <dd>N/A</dd>
              </dl>
            </dd>
            <dt>Person &amp; email address to contact for further information:</dt>
            <dd>Job Snijders (job@bsd.nl)</dd>
            <dt>Intended usage:</dt>
            <dd>COMMON</dd>
            <dt>Restrictions on usage:</dt>
            <dd>N/A</dd>
            <dt>Author:</dt>
            <dd>Job Snijders (job@bsd.nl)</dd>
            <dt>Change controller:</dt>
            <dd>IETF</dd>
          </dl>
        </section>
      </section>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <reference anchor="RFC1034" target="https://www.rfc-editor.org/info/rfc1034" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1034.xml">
          <front>
            <title>Domain names - concepts and facilities</title>
            <author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/>
            <date month="November" year="1987"/>
            <abstract>
              <t>This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="13"/>
          <seriesInfo name="RFC" value="1034"/>
          <seriesInfo name="DOI" value="10.17487/RFC1034"/>
        </reference>
        <reference anchor="RFC1123" target="https://www.rfc-editor.org/info/rfc1123" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1123.xml">
          <front>
            <title>Requirements for Internet Hosts - Application and Support</title>
            <author fullname="R. Braden" initials="R." role="editor" surname="Braden"/>
            <date month="October" year="1989"/>
            <abstract>
              <t>This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="3"/>
          <seriesInfo name="RFC" value="1123"/>
          <seriesInfo name="DOI" value="10.17487/RFC1123"/>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC5280" target="https://www.rfc-editor.org/info/rfc5280" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5280.xml">
          <front>
            <title>Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</title>
            <author fullname="D. Cooper" initials="D." surname="Cooper"/>
            <author fullname="S. Santesson" initials="S." surname="Santesson"/>
            <author fullname="S. Farrell" initials="S." surname="Farrell"/>
            <author fullname="S. Boeyen" initials="S." surname="Boeyen"/>
            <author fullname="R. Housley" initials="R." surname="Housley"/>
            <author fullname="W. Polk" initials="W." surname="Polk"/>
            <date month="May" year="2008"/>
            <abstract>
              <t>This memo profiles the X.509 v3 certificate and X.509 v2 certificate revocation list (CRL) for use in the Internet. An overview of this approach and model is provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail along with standard and Internet-specific extensions. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5280"/>
          <seriesInfo name="DOI" value="10.17487/RFC5280"/>
        </reference>
        <reference anchor="RFC6810" target="https://www.rfc-editor.org/info/rfc6810" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6810.xml">
          <front>
            <title>The Resource Public Key Infrastructure (RPKI) to Router Protocol</title>
            <author fullname="R. Bush" initials="R." surname="Bush"/>
            <author fullname="R. Austein" initials="R." surname="Austein"/>
            <date month="January" year="2013"/>
            <abstract>
              <t>In order to verifiably validate the origin Autonomous Systems of BGP announcements, routers need a simple but reliable mechanism to receive Resource Public Key Infrastructure (RFC 6480) prefix origin data from a trusted cache. This document describes a protocol to deliver validated prefix origin data to routers. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6810"/>
          <seriesInfo name="DOI" value="10.17487/RFC6810"/>
        </reference>
        <reference anchor="RFC6920" target="https://www.rfc-editor.org/info/rfc6920" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6920.xml">
          <front>
            <title>Naming Things with Hashes</title>
            <author fullname="S. Farrell" initials="S." surname="Farrell"/>
            <author fullname="D. Kutscher" initials="D." surname="Kutscher"/>
            <author fullname="C. Dannewitz" initials="C." surname="Dannewitz"/>
            <author fullname="B. Ohlman" initials="B." surname="Ohlman"/>
            <author fullname="A. Keranen" initials="A." surname="Keranen"/>
            <author fullname="P. Hallam-Baker" initials="P." surname="Hallam-Baker"/>
            <date month="April" year="2013"/>
            <abstract>
              <t>This document defines a set of ways to identify a thing (a digital object in this case) using the output from a hash function. It specifies a new URI scheme for this purpose, a way to map these to HTTP URLs, and binary and human-speakable formats for these names. The various formats are designed to support, but not require, a strong link to the referenced object, such that the referenced object may be authenticated to the same degree as the reference to it. The reason for this work is to standardise current uses of hash outputs in URLs and to support new information-centric applications and other uses of hash outputs in protocols.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6920"/>
          <seriesInfo name="DOI" value="10.17487/RFC6920"/>
        </reference>
        <reference anchor="RFC7935" target="https://www.rfc-editor.org/info/rfc7935" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7935.xml">
          <front>
            <title>The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure</title>
            <author fullname="G. Huston" initials="G." surname="Huston"/>
            <author fullname="G. Michaelson" initials="G." role="editor" surname="Michaelson"/>
            <date month="August" year="2016"/>
            <abstract>
              <t>This document specifies the algorithms, algorithms' parameters, asymmetric key formats, asymmetric key size, and signature format for the Resource Public Key Infrastructure (RPKI) subscribers that generate digital signatures on certificates, Certificate Revocation Lists (CRLs), Cryptographic Message Syntax (CMS) signed objects and certification requests as well as for the relying parties (RPs) that verify these digital signatures.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7935"/>
          <seriesInfo name="DOI" value="10.17487/RFC7935"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC9110" target="https://www.rfc-editor.org/info/rfc9110" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC9286" target="https://www.rfc-editor.org/info/rfc9286" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9286.xml">
          <front>
            <title>Manifests for the Resource Public Key Infrastructure (RPKI)</title>
            <author fullname="R. Austein" initials="R." surname="Austein"/>
            <author fullname="G. Huston" initials="G." surname="Huston"/>
            <author fullname="S. Kent" initials="S." surname="Kent"/>
            <author fullname="M. Lepinski" initials="M." surname="Lepinski"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>This document defines a "manifest" for use in the Resource Public Key Infrastructure (RPKI). A manifest is a signed object (file) that contains a listing of all the signed objects (files) in the repository publication point (directory) associated with an authority responsible for publishing in the repository. For each certificate, Certificate Revocation List (CRL), or other type of signed objects issued by the authority that are published at this repository publication point, the manifest contains both the name of the file containing the object and a hash of the file content. Manifests are intended to enable a relying party (RP) to detect certain forms of attacks against a repository. Specifically, if an RP checks a manifest's contents against the signed objects retrieved from a repository publication point, then the RP can detect replay attacks, and unauthorized in-flight modification or deletion of signed objects. This document obsoletes RFC 6486.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9286"/>
          <seriesInfo name="DOI" value="10.17487/RFC9286"/>
        </reference>
        <reference anchor="X.690" target="https://www.itu.int/rec/T-REC-X.690-202102-I/en" quoteTitle="true" derivedAnchor="X.690">
          <front>
            <title>Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="February" year="2021"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="X.690"/>
          <seriesInfo name="ISO/IEC" value="8825-1:2021"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="RFC7541" target="https://www.rfc-editor.org/info/rfc7541" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7541.xml">
          <front>
            <title>HPACK: Header Compression for HTTP/2</title>
            <author fullname="R. Peon" initials="R." surname="Peon"/>
            <author fullname="H. Ruellan" initials="H." surname="Ruellan"/>
            <date month="May" year="2015"/>
            <abstract>
              <t>This specification defines HPACK, a compression format for efficiently representing HTTP header fields, to be used in HTTP/2.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7541"/>
          <seriesInfo name="DOI" value="10.17487/RFC7541"/>
        </reference>
        <reference anchor="RFC9204" target="https://www.rfc-editor.org/info/rfc9204" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9204.xml">
          <front>
            <title>QPACK: Field Compression for HTTP/3</title>
            <author fullname="C. Krasic" initials="C." surname="Krasic"/>
            <author fullname="M. Bishop" initials="M." surname="Bishop"/>
            <author fullname="A. Frindell" initials="A." role="editor" surname="Frindell"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>This specification defines QPACK: a compression format for efficiently representing HTTP fields that is to be used in HTTP/3. This is a variation of HPACK compression that seeks to reduce head-of-line blocking.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9204"/>
          <seriesInfo name="DOI" value="10.17487/RFC9204"/>
        </reference>
        <reference anchor="RFC9205" target="https://www.rfc-editor.org/info/rfc9205" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9205.xml">
          <front>
            <title>Building Protocols with HTTP</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet but might be applicable in other situations.</t>
              <t>This document obsoletes RFC 3205.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="56"/>
          <seriesInfo name="RFC" value="9205"/>
          <seriesInfo name="DOI" value="10.17487/RFC9205"/>
        </reference>
        <reference anchor="RFC9112" target="https://www.rfc-editor.org/info/rfc9112" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9112.xml">
          <front>
            <title>HTTP/1.1</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document specifies the HTTP/1.1 message syntax, message parsing, connection management, and related security concerns.</t>
              <t>This document obsoletes portions of RFC 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="99"/>
          <seriesInfo name="RFC" value="9112"/>
          <seriesInfo name="DOI" value="10.17487/RFC9112"/>
        </reference>
        <reference anchor="RFC9113" target="https://www.rfc-editor.org/info/rfc9113" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9113.xml">
          <front>
            <title>HTTP/2</title>
            <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
            <author fullname="C. Benfield" initials="C." role="editor" surname="Benfield"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced latency by introducing field compression and allowing multiple concurrent exchanges on the same connection.</t>
              <t>This document obsoletes RFCs 7540 and 8740.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9113"/>
          <seriesInfo name="DOI" value="10.17487/RFC9113"/>
        </reference>
        <reference anchor="RFC9114" target="https://www.rfc-editor.org/info/rfc9114" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9114.xml">
          <front>
            <title>HTTP/3</title>
            <author fullname="M. Bishop" initials="M." role="editor" surname="Bishop"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9114"/>
          <seriesInfo name="DOI" value="10.17487/RFC9114"/>
        </reference>
        <reference anchor="M1987" quoteTitle="true" target="https://doi.org/10.1007/3-540-48184-2_32" derivedAnchor="M1987">
          <front>
            <title>A Digital Signature Based on a Conventional Encryption Function</title>
            <author fullname="R. Merkle" initials="R." surname="Merkle"/>
            <date year="1988"/>
          </front>
          <refcontent>Advances in Cryptology -- CRYPTO '87 Proceedings</refcontent>
          <refcontent>Lecture Notes in Computer Science, Vol. 293</refcontent>
          <seriesInfo name="DOI" value="10.1007/3-540-48184-2_32"/>
        </reference>
        <reference anchor="P2P" target="https://www.ietf.org/proceedings/83/slides/slides-83-sidr-9.pdf">
          <front>
            <title>RPKI Over BitTorrent</title>
            <author fullname="Rob Austein" initials="R." surname="Austein"/>
            <author fullname="Randy Bush" initials="R." surname="Bush"/>
            <author fullname="Michael Elkins" initials="M." surname="Elkins"/>
            <author fullname="Leif Johansson" initials="L." surname="Johansson"/>
            <date year="2012" month="March"/>
          </front>
        </reference>
        <!--
        <reference anchor="ustar" target="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/pax.html#tag_20_94_13_06">
          <front>
            <title>ustar Interchange Format</title>
            <author>
              <organization>IEEE/Open Group</organization>
            </author>
            <date year="2024" month="June"/>
          </front>
          <seriesInfo name="IEEE Std" value="1003.1-2024"/>
          <seriesInfo name="DOI" value="10.1109/IEEESTD.2018.8423794"/>
        </reference>
-->

        <reference anchor="RFC0677" target="https://www.rfc-editor.org/info/rfc677" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.0677.xml">
          <front>
            <title>Maintenance of duplicate databases</title>
            <author fullname="P.R. Johnson" initials="P.R." surname="Johnson"/>
            <author fullname="R. Thomas" initials="R." surname="Thomas"/>
            <date month="January" year="1975"/>
          </front>
          <seriesInfo name="RFC" value="677"/>
          <seriesInfo name="DOI" value="10.17487/RFC677"/>
        </reference>
        <reference anchor="RFC1925" target="https://www.rfc-editor.org/info/rfc1925" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1925.xml">
          <front>
            <title>The Twelve Networking Truths</title>
            <author fullname="R. Callon" initials="R." surname="Callon"/>
            <date month="April" year="1996"/>
            <abstract>
              <t>This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1925"/>
          <seriesInfo name="DOI" value="10.17487/RFC1925"/>
        </reference>
        <reference anchor="RFC5781" target="https://www.rfc-editor.org/info/rfc5781" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5781.xml">
          <front>
            <title>The rsync URI Scheme</title>
            <author fullname="S. Weiler" initials="S." surname="Weiler"/>
            <author fullname="D. Ward" initials="D." surname="Ward"/>
            <author fullname="R. Housley" initials="R." surname="Housley"/>
            <date month="February" year="2010"/>
            <abstract>
              <t>This document specifies the rsync Uniform Resource Identifier (URI) scheme. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5781"/>
          <seriesInfo name="DOI" value="10.17487/RFC5781"/>
        </reference>
        <reference anchor="RFC6480" target="https://www.rfc-editor.org/info/rfc6480" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6480.xml">
          <front>
            <title>An Infrastructure to Support Secure Internet Routing</title>
            <author fullname="M. Lepinski" initials="M." surname="Lepinski"/>
            <author fullname="S. Kent" initials="S." surname="Kent"/>
            <date month="February" year="2012"/>
            <abstract>
              <t>This document describes an architecture for an infrastructure to support improved security of Internet routing. The foundation of this architecture is a Resource Public Key Infrastructure (RPKI) that represents the allocation hierarchy of IP address space and Autonomous System (AS) numbers; and a distributed repository system for storing and disseminating the data objects that comprise the RPKI, as well as other signed objects necessary for improved routing security. As an initial application of this architecture, the document describes how a legitimate holder of IP address space can explicitly and verifiably authorize one or more ASes to originate routes to that address space. Such verifiable authorizations could be used, for example, to more securely construct BGP route filters. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6480"/>
          <seriesInfo name="DOI" value="10.17487/RFC6480"/>
        </reference>
        <reference anchor="RFC7115" target="https://www.rfc-editor.org/info/rfc7115" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7115.xml">
          <front>
            <title>Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)</title>
            <author fullname="R. Bush" initials="R." surname="Bush"/>
            <date month="January" year="2014"/>
            <abstract>
              <t>Deployment of BGP origin validation that is based on the Resource Public Key Infrastructure (RPKI) has many operational considerations. This document attempts to collect and present those that are most critical. It is expected to evolve as RPKI-based origin validation continues to be deployed and the dynamics are better understood.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="185"/>
          <seriesInfo name="RFC" value="7115"/>
          <seriesInfo name="DOI" value="10.17487/RFC7115"/>
        </reference>
        <reference anchor="RFC8182" target="https://www.rfc-editor.org/info/rfc8182" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8182.xml">
          <front>
            <title>The RPKI Repository Delta Protocol (RRDP)</title>
            <author fullname="T. Bruijnzeels" initials="T." surname="Bruijnzeels"/>
            <author fullname="O. Muravskiy" initials="O." surname="Muravskiy"/>
            <author fullname="B. Weber" initials="B." surname="Weber"/>
            <author fullname="R. Austein" initials="R." surname="Austein"/>
            <date month="July" year="2017"/>
            <abstract>
              <t>In the Resource Public Key Infrastructure (RPKI), Certificate Authorities (CAs) publish certificates, including end-entity certificates, Certificate Revocation Lists (CRLs), and RPKI signed objects to repositories. Relying Parties retrieve the published information from those repositories. This document specifies a new RPKI Repository Delta Protocol (RRDP) for this purpose. RRDP was specifically designed for scaling. It relies on an Update Notification File which lists the current Snapshot and Delta Files that can be retrieved using HTTPS (HTTP over Transport Layer Security (TLS)), and it enables the use of Content Distribution Networks (CDNs) or other caching infrastructures for the retrieval of these files.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8182"/>
          <seriesInfo name="DOI" value="10.17487/RFC8182"/>
        </reference>
        <reference anchor="RFC9842" target="https://www.rfc-editor.org/info/rfc9842" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9842.xml">
          <front>
            <title>Compression Dictionary Transport</title>
            <author fullname="P. Meenan" initials="P." role="editor" surname="Meenan"/>
            <author fullname="Y. Weiss" initials="Y." role="editor" surname="Weiss"/>
            <date month="September" year="2025"/>
            <abstract>
              <t>This document specifies a mechanism for dictionary-based compression in the Hypertext Transfer Protocol (HTTP). By utilizing this technique, clients and servers can reduce the size of transmitted data, leading to improved performance and reduced bandwidth consumption. This document extends existing HTTP compression methods and provides guidelines for the delivery and use of compression dictionaries within the HTTP protocol.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9842"/>
          <seriesInfo name="DOI" value="10.17487/RFC9842"/>
        </reference>
        <reference anchor="rpkitouch" target="https://www.github.com/job/rpkitouch">
          <front>
            <title>rpkitouch</title>
            <author fullname="Job Snijders"/>
            <date month="July" year="2026"/>
          </front>
        </reference>
        <!--
        <reference anchor="rpki-client" target="https://www.rpki-client.org/">
          <front>
            <title>rpki-client</title>
            <author fullname="Claudio Jeker"/>
            <author fullname="Job Snijders"/>
            <author fullname="Kristaps Dzonsons"/>
            <author fullname="Theo Buehler"/>
            <date month="June" year="2024" />
          </front>
        </reference>
-->

        <reference anchor="rpki-erik-demo" target="https://github.com/APNIC-net/rpki-erik-demo">
          <front>
            <title>rpki-erik-demo</title>
            <author fullname="Tom Harrison">
              <organization>APNIC</organization>
            </author>
            <date month="March" year="2026"/>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="running_code" title="Implementation status" removeInRFC="true">
      <t>
        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.
      </t>
      <t>
        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".
      </t>
      <section>
        <name>Experimental Erik Relay Services</name>
        <t>
          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.
        </t>
        <dl>
          <!--
          <dt><tt>http://relay.rpki-servers.org/</tt></dt>
          <dd>Dublin, Osaka, Sydney - anycasted distributed computing cluster</dd>
 
          <dt><tt>http://dub.rpki-servers.org/</tt></dt>
          <dd>Dublin, Ireland, - distributed computing cluster (6 machines, NFS backend)</dd>
 
          <dt><tt>http://atl.rpki-servers.org/</tt></dt>
          <dd>Atlanta, USA, - distributed computing cluster (2 machines, NFS backend)</dd>
-->
          <dt><tt>https://miso.sobornost.net/</tt></dt>
          <dd>Amsterdam, NL, single node</dd>
          <dt><tt>http://nyc.rpki-servers.org/</tt></dt>
          <dd>New York, USA, - single node</dd>
          <dt><tt>https://pek.rpki-servers.org/</tt></dt>
          <dd>Beijing, China - HTTPS, single node</dd>
          <!-- 
          <dt><tt>http://fnllwqoupfrhso6643whm6lpkgsftjtc6crpehmyz2o7pffirnqy7rad.onion/</tt></dt>
          <dd>Erik relay service via Tor</dd>
-->
        </dl>
      </section>
      <section>
        <name>Software</name>
        <t>
          An experimental Erik static content generator was developed by Job Snijders in the form of <xref target="rpkitouch"/> using <tt>C</tt>.
        </t>
        <t>
          An experimental Erik client and server were developed by Tom Harrison from APNIC in the form of <xref target="rpki-erik-demo"/> using <tt>Perl</tt>.
        </t>
      </section>
    </section>
    <section anchor="example_payloads">
      <name>Example objects</name>
      <t>
        Included in this section are an <tt>ErikIndex</tt> for <tt>rpki.ripe.net</tt> and an <tt>ErikPartition</tt> referenced from the aforementioned ErikIndex, both Base64 encoded.
      </t>
      <section>
        <name>Example ErikIndex</name>
        <t>
          This object was retrieved from <tt>http://miso.sobornost.net/.well-known/erik/index/rpki.ripe.net</tt>
        </t>
        <sourcecode anchor="ex_index" type="base64" originalSrc="rpki.ripe.net.b64">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
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
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
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
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
</sourcecode>
      </section>
      <section>
        <name>Example ErikPartition</name>
        <t>
          This object was retrieved from <tt>https://miso.sobornost.net/.well-known/ni/sha-256/AZmwyRKvBFv4DPl2g5IAhM8BbDvVWzZvgBLjORCoXqM</tt>
        </t>
        <sourcecode anchor="ex_part" type="base64" originalSrc="AZmwyRKvBFv4DPl2g5IAhM8BbDvVWzZvgBLjORCoXqM.b64">MIIxEgYLKoZIhvcNAQkQATiggjEBMIIw/RgPMjAyNjAxMDgyMzAyMDhaMAsGCWCG
SAFlAwQCATCCMNswgdEEIAFg/0CdwFaUyfP3EyK5RmO+SHjEkYpJ03VcFje02/ua
AgIIpQQUfz4LJ7jk15j5K53hV/HaWkPNSeUCAhH4GA8yMDI2MDEwODE5MDA1NVow
fjB8BggrBgEFBQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkv
REVGQVVMVC81Zi9hMGM5YWMtM2E0Ny00ZDZjLWFhMTUtYTQyZWM4Nzc2ZmJiLzEv
Zno0TEo3amsxNWo1SzUzaFZfSGFXa1BOU2VVLm1mdDCB0QQgBNUfbUn0GcyCLtIB
6SMWn3PzeAvWEckmuoPOieKTqQgCAgilBBR/ytid8b+Zo28pDMPvDx57TQJ1MwIC
F5cYDzIwMjYwMTA4MjAwMTExWjB+MHwGCCsGAQUFBzALhnByc3luYzovL3Jwa2ku
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+
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
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
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
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
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=
</sourcecode>
      </section>
      <section>
        <name>Example ErikSegmentIndex</name>
        <t>
          This object was retrieved from <tt>https://miso.sobornost.net/.well-known/erik/segmentindex/rpki.ripe.net</tt>
        </t>
        <sourcecode anchor="ex_segidx" type="base64" originalSrc="segmentindex.example.b64">MIGsBgsqhkiG9w0BCRABO6CBnDCBmRYNcnBraS5yaXBlLm5ldBgPMjAyNjA3MjEw
NzE5MTRaMAsGCWCGSAFlAwQCATBqMDMYDzIwMjYwNzIxMDcyMDAwWgQguNBbTBoe
zZhz2dMs1ZmDiCtE0NEywGnOvc4nrH8ynxUwMxgPMjAyNjA3MjEwNzI1MDBaBCDB
doo/n2Nc0xyGtn3PuZhFjpaHHQIffUWi0P34uDag7Q==
</sourcecode>
      </section>
    </section>
    <section anchor="acknowledgements" numbered="false">
      <name>Acknowledgements</name>
      <t>
        This protocol is named after Erik Bais, who passed away in 2024, as a small token of appreciation for his friendship.
      </t>
      <t>
        The authors wish to thank
          <contact fullname="George Michaelson"/>,
          <contact fullname="Theo de Raadt"/>,
          <contact fullname="Bob Beck"/>,
          <contact fullname="Theo Buehler"/>,
          <contact fullname="William McCall"/>,
          <contact fullname="Jasdip Singh"/>,
          <contact fullname="Michael Hollyman"/>,
          <contact fullname="Mike Bishop"/>,
          <contact fullname="Kamiel Braet"/>,
          <contact fullname="Loganaden Velvindron"/>,
          <contact fullname="Lancheng Qin"/>,
          and
          <contact fullname="Dirk Doesburg"/>
        for the lovely conversations that led to this proposal.
        The authors wish to thank <contact fullname="Sean Turner"/> and <contact fullname="Russ Housley"/> for their review of the ASN.1 notation.
      </t>
      <t>
        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.
      </t>
    </section>
  </back>
</rfc>
