<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc [
 <!ENTITY nbsp    "&#160;">
 <!ENTITY zwsp   "&#8203;">
 <!ENTITY nbhy   "&#8209;">
 <!ENTITY wj     "&#8288;">
]>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" xml:lang="en" category="std" docName="draft-ietf-grow-nrtm-v4-11" number="10063" submissionType="IETF" consensus="true" ipr="trust200902" symRefs="true" sortRefs="true" tocInclude="true" tocDepth="3" updates="" obsoletes="">

<front>
  <title abbrev="NRTM v4">Near Real Time Mirroring (NRTM) Version 4</title>
  <seriesInfo name="RFC" value="10063"/>
  <author fullname="Sasha Romijn" initials="S." surname="Romijn">
    <organization>Reliably Coded</organization>
    <address>
      <postal>
        <city>Amsterdam</city>
        <country>Netherlands</country>
      </postal>
      <email>sasha@reliablycoded.nl</email>
      <uri>https://www.reliablycoded.nl/</uri>
    </address>
  </author>

  <author fullname="Job Snijders" initials="J." surname="Snijders">
    <organization abbrev="BSD">BSD Software Development</organization>
    <address>
      <postal>
        <city>Amsterdam</city>
        <country>Netherlands</country>
      </postal>
      <email>job@bsd.nl</email>
      <uri>https://www.bsd.nl/</uri>
    </address>
  </author>

  <author fullname="Edward Shryane" initials="E." surname="Shryane">
    <organization>RIPE NCC</organization>
    <address>
      <postal>
        <city>Amsterdam</city>
        <country>Netherlands</country>
      </postal>
      <email>eshryane@ripe.net</email>
    </address>
  </author>

  <author fullname="Stavros Konstantaras" initials="S." surname="Konstantaras">
    <organization>AMS-IX</organization>
    <address>
      <postal>
        <city>Amsterdam</city>
        <country>Netherlands</country>
      </postal>
      <email>stavros.konstantaras@ams-ix.net</email>
    </address>
  </author>
  <date month="November" year="2026"/>

  <area>OPS</area>
  <workgroup>grow</workgroup>

  <keyword>NRTM</keyword>
  <keyword>RPSL</keyword>
  <keyword>IRR</keyword>

  <abstract>
    <t>
      This document specifies Near Real Time Mirroring version 4 (NRTMv4): a one-way synchronization protocol for Internet Routing Registry (IRR) records. NRTMv4 is based on files that are distributed over HTTPS.
      The protocol allows instances of IRR Database servers to mirror IRR records, specified in the Routing Policy Specification Language (RPSL), between each other.
    </t>
  </abstract>

</front>

<middle>

  <section><name>Introduction</name>
    <t>
      The Internet Routing Registry (IRR) consists of several IRR Databases, each representing objects in the Routing Policy Specification Language (RPSL) <xref target="RFC2622"/>.
      About a dozen larger IRR Databases are well known and widely used, operated by different organizations such as Regional Internet Registries and some large network operators.
      IRR objects serve many purposes ranging from manual research by operators to automated network configuration and filtering.
    </t>

    <t>
      Most of these well-known IRR Databases mirror IRR objects from some others so that queries run against these instances provide a comprehensive view.
      Some parties also mirror IRR Databases to private IRR server instances to reduce latency when replying to queries, analyze IRR objects, or other purposes.
    </t>

    <t>
      NRTM version 4 (NRTMv4) is a protocol for IRR mirroring and is designed to address issues in existing IRR Database mirroring protocols.
      In NRTMv4, IRR Databases publish their records on an HTTPS <xref target="STD97"/> endpoint with periodic Snapshot Files and regular Delta Files.
      Signing allows integrity checks.
      By only generating files once and publishing them over HTTPS, scalability is improved.
      NRTMv4 borrows some concepts from the Resource Public Key Infrastructure (RPKI) Repository Delta Protocol <xref target="RFC8182"/>, as there are overlaps between the two protocols.
    </t>

    <t>
      Reliable and secure distribution of IRR data is important for global routing operations since network operators depend on IRR objects for route filtering and network configuration.
      Prior mirroring protocols lack integrity verification, have no formal specification, and scale poorly.
      NRTMv4 addresses these shortcomings by providing a formally specified, scalable, and integrity-protected mirroring protocol.
      Of earlier NRTM versions, none were formally specified, but NRTMv3 <xref target="NRTMv3"/> was widely deployed.
      Some comparisons are made in <xref target="security_considerations" />.
    </t>

  </section>

  <section><name>Overview</name>
    <t>
      In NRTMv4, a mirror server is an instance of IRR Database software that has a database of IRR objects and makes them available on an HTTPS endpoint to allow mirroring by others.
      These objects can be retrieved by mirror clients, which then load them into their local storage.
    </t>
    <figure>
      <name>NRTMv4 Protocol Overview</name>
      <artwork align="center"><![CDATA[
                    Mirror Server
                   +--------------+
                   | IRR Database |
                   +------+-------+
                          |
      +-------------------+-------------------+
      |                   |                   |
  periodic                |               on change
      |                   |                   |
      v                   v                   v
+------------+      +-----------+      +------------+
|  Snapshot  |      |  Update   |      |   Delta    |
|    File    | refs |   Notif.  | refs |  File(s)   |
|   (all     |<-----|   File    |----->| (changes   |
|  objects)  |      |  (index)  |      |   only)    |
+-----+------+      +-----------+      +-----+------+
      |                   |                  |
      |          +--------+--------+         |
      +--------->+  Mirror Client  +<--------+
        initial  | Local Database  |   update
                 +-----------------+]]></artwork>
    </figure>
    <t>
      Publication consists of three different files:     
    </t>
    <ul>
      <li>
        A single Update Notification File.
        This specifies the current IRR Database version and locations of the Snapshot File and Delta Files.
        It is signed to allow verification of the authenticity of the Update Notification File.
      </li>
      <li>
        A single active Snapshot File.
        This contains all published IRR objects at a particular version.
        The mirror server periodically generates a new snapshot.
      </li>
      <li>
        Zero or more Delta Files.
        These contain the changes between two Database versions.
      </li>
     </ul>
     <t>
       The Update Notification File <bcp14>MUST</bcp14> be in the JSON Web Signature <xref target="RFC7515" /> format, where the payload is in JSON format <xref target="RFC8259" />.
       The Snapshot File and Delta Files <bcp14>MUST</bcp14> be in the JSON Text Sequences <xref target="RFC7464" /> format so that each object in large files can be parsed independently.
       Files <bcp14>MAY</bcp14> be compressed with GZIP <xref target="RFC1952" />.
     </t>
     <t>
       Mirror clients initially retrieve the small Update Notification File and a Snapshot File from which they initialize their local copy of the Database.
       After that, mirror clients only retrieve the Update Notification File periodically, typically every minute, to determine whether there are any changes, and then retrieve only the relevant Delta Files, if any.
       This minimizes data transfer.
       Deltas have sequential versions.
     </t>
     <t>
       Mirror clients are configured with the URL of an Update Notification File, the name of the IRR Database, and a public signing key. This public key is used to verify the Update Notification File, which, in turn, contains hashes of all the Snapshot and Delta Files.
     </t>
     <t>
       Upon initialization, the mirror server generates a session identifier (session_id) for the Database (<xref target="mirror_server_snapshot_initialization" />).
       This allows long-term caching and is used by the client to determine that the Delta Files continue to form a full set of changes allowing an update to the latest version.
       If the mirror server loses partial history or the mirror client starts mirroring from a different server, the session_id change will force a full reload from the latest Snapshot File, ensuring there are no accidental mirroring gaps.
     </t>
     <t>
       Mirror servers can use caching to reduce their load, particularly because snapshots and deltas are immutable for a given session_id and version number.
       These are also the largest files. Update Notification Files may not be cached for longer than one minute, but are fairly small.
     </t>
     <t>
       Note that in NRTMv4, contiguous version numbers are used for the Database version and Delta Files.
       This is different and unrelated to the serial in NRTMv3.
       NRTMv3 serials refer to a single change to a single object, whereas an NRTMv4 version refers to one delta, possibly containing multiple changes to multiple objects.
       NRTMv3 serials can also contain gaps, NRTMv4 versions do not.

      </t>
    </section>
  <section><name>Terminology</name>
    <dl spacing="normal" newline="false">
      <dt>IRR Database:</dt>
      <dd>A logical collection of IRR objects represented in RPSL, grouped by the value in their "source" attribute. That value is the name of the IRR Database. No particular storage technology is implied.</dd>
      <dt>Snapshot File:</dt>
      <dd>A file that reflects the complete contents of the IRR objects in an IRR Database at a particular point in time.</dd>
      <dt>Delta File:</dt>
      <dd>A file that contains all changes for exactly one incremental update of the IRR Database.</dd>
      <dt>Update Notification File:</dt>
      <dd>A file generated by the mirror server and used by mirror clients to discover which changes exist between the state of the IRR mirror server and of the mirror client.</dd>
      <dt>Mirror Server:</dt>
      <dd>An instance of IRR Database software that has a database of IRR objects and makes them available for retrieval on an HTTPS endpoint, to allow mirroring by others.</dd>
      <dt>Mirror Client:</dt>
      <dd>An instance of IRR Database software that retrieves IRR objects from a mirror server and loads them into its local storage.</dd>
      <dt>Version:</dt>
      <dd>A monotonically increasing positive integer, scoped to a session_id, that identifies a particular state of the IRR Database.</dd>
    </dl>
    <section>
      <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>
  <section><name>Mirror Server Use</name>
    <section><name>Key Configuration</name>
      <t>
        When enabling NRTMv4 publication for an IRR Database, the operator <bcp14>MUST</bcp14> generate a JSON Web Key <xref target="RFC7517"/> pair and configure the private key in the mirror server.
        The operator then provides the corresponding public key, the name of the IRR Database, and publication URL of the Update Notification File to any operators of mirror clients.
        The published public key <bcp14>MUST</bcp14> be encapsulated following Textual Encoding of Subject Public Key Info <xref target="RFC7468" section="13"/>, sometimes referred to as "PEM encoding".
        The process for providing this is not in the scope of this protocol, but a typical case is publication on the operator's known website.
        Key rotation is described in <xref target="public_key_rotation" />.
      </t>
      <t>
        It is <bcp14>RECOMMENDED</bcp14> that implementations provide easily accessible tools for operators to generate new signing keys to enter into their configuration and assist with key rotation.
        All configuration options <bcp14>SHOULD</bcp14> be clearly named to indicate that they are private keys. Clear naming reduces the risk of operator error causing accidental exposure.
      </t>
    </section>
    <section anchor="mirror_server_snapshot_initialization"><name>Snapshot Initialization</name>
      <t>
        A mirror server <bcp14>MUST</bcp14> follow the initialization steps upon the first export for an IRR Database by that mirror server, or if the server lost history and can not reliably produce a continuous set of deltas from a previous state.
      </t>
      <t>
        In other words, either the mirror server guarantees that clients following the deltas have a correct and complete view, or the mirror server must reinitialize, which will force clients to reinitialize as well.
      </t>
      <t>
        Initialization consists of these actions:
      </t>
      <ul>
        <li>
          The mirror server <bcp14>MUST</bcp14> generate a new session_id.
          This <bcp14>MUST</bcp14> be a Universally Unique Identifier version 4 (UUIDv4) (<xref target="RFC9562" section="5.4"/>) and <bcp14>MUST</bcp14> be the same across all client sessions.
          The session_id is unique to the IRR Database, so an instance that serves multiple IRR Databases will create a separate session_id for each.
        </li>
        <li>
          The server <bcp14>MUST</bcp14> generate a snapshot for version number one.
          This may contain an empty array of objects if the IRR Database is currently empty.
        </li>
        <li>
          The server <bcp14>MUST</bcp14> generate a new Update Notification File with the new session_id, a reference to the new snapshot, and no deltas.
        </li>
      </ul>
      <t>
        Note that a publication, and its associated session_ids and versions, always relates to a single specific IRR Database, even if multiple databases are published from one instance.
        For example, a mirror server that serves two IRR Databases named EXAMPLE and EXAMPLE-NONAUTH will generate two Update Notification Files, referring to two Snapshot Files and two sets of Delta Files. Each set of Delta Files has contiguous version numbers. The two publications are completely independent of each other, with different session IDs, and may be published at different times.
        This applies even if the same IRR server instance produces both.
      </t>
    </section>

    <section><name>Publishing Updates</name>
      <t>
        After creating the initialization files, the mirror server processes updates by generating Delta Files and, periodically, a new Snapshot File, and placing them on the HTTPS endpoint.
      </t>
      <section><name>Delta Files</name>
        <t>
          Changes to IRR objects <bcp14>MUST</bcp14> be recorded in Delta Files. One Delta File can contain multiple changes.
        </t>
        <t>
          Updates are generated as follows:
        </t>
        <ul>
          <li>
            A mirror server <bcp14>MUST</bcp14> publish a Delta File approximately every minute if there have been changes to IRR objects in that time frame.
          </li>
          <li>
            If a mirror server is lagging in production of Delta Files, such as after an initialization or server downtime, it <bcp14>MUST</bcp14> generate one larger "catch up" Delta File rather than individual Delta Files for every one-minute window.
          </li>
          <li>
            A new Delta File <bcp14>MUST</bcp14> be generated with a new version, one greater than the last Delta File version, or one greater than the last Snapshot File version if there were no prior deltas at all.
          </li>
          <li>
            The Delta File <bcp14>MUST</bcp14> include all changes that happened during the time frame in the order in which they occurred.
            If multiple changes have occurred within the time frame that would cancel each other out, like an addition and immediate deletion of the same object, the mirror server <bcp14>MUST</bcp14> still include all these changes.
          </li>
          <li>
            The URL where the Delta File is published <bcp14>MUST</bcp14> contain the session ID and version number so that the content at a given URL is immutable and can be cached indefinitely by HTTP intermediaries.
            It <bcp14>MUST</bcp14> also contain a random value that can not be predicted before publication to counter negative caching issues.
          </li>
          <li>
            The Update Notification File <bcp14>MUST</bcp14> be updated to include the new Delta File.
          </li>
          <li>
            References to Delta Files older than 24 hours <bcp14>SHOULD</bcp14> be removed from the Update Notification File.
            This limits the potential length of the Delta chain that clients must process, where a Snapshot refresh may be more efficient, while also preventing overly frequent Snapshot reloads.
            However, a mirror server <bcp14>MUST NOT</bcp14> remove references to Delta Files with a version higher than the current Snapshot File version, as this would leave clients with no path from the snapshot to the current state.
            Refer also to <xref target="storage" />.
          </li>
          <li>
            Note that, as Delta Files always contain changes compared to a previous state, there can never be a Delta File with version 1.
          </li>
        </ul>
        <t>
          Mirror servers with high object churn are <bcp14>RECOMMENDED</bcp14> to generate new Snapshot Files more frequently than the required minimum to limit the length of the Delta chain that clients must traverse on initialization or after a gap.
          Long Delta chains increase initialization time and resource consumption for mirror clients.
        </t>
      </section>
      <section><name>Snapshot Files</name>
        <t>
          Snapshot Files after initialization are generated as follows:
        </t>
        <ul>
          <li>
            If there have been no changes to the IRR objects since the last snapshot, the mirror server <bcp14>MUST NOT</bcp14> generate a new snapshot.
          </li>
          <li>
            The mirror server <bcp14>MUST</bcp14> generate a new Snapshot File at least once per day if there have been changes to the IRR objects.
            Mirror servers should not generate new Snapshot Files more than once per hour, as snapshot generation can be resource-intensive.
          </li>
          <li>
            The version number of the new snapshot <bcp14>MUST</bcp14> be equal to the last Delta File version at the time the server begins generating the snapshot.
          </li>
          <li>
            The URL where the Snapshot File is published <bcp14>MUST</bcp14> contain the session ID and version number so that the content at a given URL is immutable and can be cached indefinitely by HTTP intermediaries.
            It <bcp14>MUST</bcp14> also contain a random value that can not be predicted before publication to counter negative caching issues.
          </li>
          <li>
            The Update Notification File <bcp14>MUST</bcp14> be updated to include the new snapshot if one was generated.
          </li>
          <li>
            Snapshot generation may take some time, and in that time, newer changes may occur that are not part of the snapshot in progress.
            The mirror server <bcp14>MUST</bcp14> continue to produce Delta Files during this window.
            This means that the server may publish a Snapshot File with a version number older than the most recent Delta File at the time of publication.
          </li>
        </ul>
      </section>
      <section><name>Update Notification File</name>
        <t>
          The Update Notification File <bcp14>MUST</bcp14> be updated when a new Delta or Snapshot File is published and at least every 24 hours, even if there have been no changes.
          The full format and validation rules are specified in <xref target="update_notification_file" />.
        </t>
      </section>
      <section><name>Publication Policy Restrictions</name>
        <t>
          A mirror server <bcp14>MAY</bcp14> have a policy that restricts the publication of certain IRR objects or attributes, or modifies these before publication.
          Typical scenarios for this include preventing the distribution of certain personal data or password hashes, or excluding objects which do not meet validation rules like RPKI consistency.
          If objects are modified, it is <bcp14>RECOMMENDED</bcp14> that the mirror server makes it evident to humans reading the object text that the object was modified, for example, by adding remark lines or comments.
        </t>
        <t>
          Mirror servers are <bcp14>RECOMMENDED</bcp14> to remove password hashes from the auth lines in mntner objects, as they have little use beyond the authoritative server and their publication may be a security risk.
        </t>
        <t>
          If a mirror server has a policy that restricts or modifies object publication, this <bcp14>MUST</bcp14> be applied consistently to Snapshot Files and Delta Files from the moment the policy is enacted or modified.
        </t>
      </section>
    </section>
  </section>

  <section><name>Mirror Client Use</name>
    <section><name>Client Configuration</name>
      <t>
        Mirror clients are configured with the name of the IRR Database, the URL of the Update Notification File, and the public key currently used for signing the Update Notification File.
        Key rotation is described in <xref target="public_key_rotation" />.
      </t>
    </section>

    <section><name>Update Notification File Retrieval</name>
      <t>
        Mirror clients may retrieve the Update Notification File to check for changes every minute.
        Mirror clients <bcp14>MUST NOT</bcp14> check more than once per minute.
      </t>
    </section>

    <section><name>Initialization from Snapshot</name>
      <t>
        Clients <bcp14>MUST</bcp14> initialize from a Snapshot File when initially configured, or if they are not able to update their local data from the provided Delta Files:
      </t>
      <ul>
        <li>
          The client <bcp14>MUST</bcp14> retrieve the Update Notification File.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> verify that the source attribute in the Update Notification File matches the configured IRR Database name.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> retrieve the Snapshot File and load the objects into its local storage.
        </li>
        <li>
          The mirror client <bcp14>MUST</bcp14> verify that the calculated SHA-256 <xref target="SHS"/> hash of the Snapshot File matches the hash in the Update Notification File that referenced it.
          If the Snapshot File was compressed with GZIP, the hash <bcp14>MUST</bcp14> match the compressed data.
          As the Update Notification File is signed, this hash verification proves the integrity and authenticity for the Snapshot File.
          In case of a mismatch of this hash, the file <bcp14>MUST</bcp14> be rejected.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> record the session_id and version of the loaded Snapshot File.
        </li>
        <li>
          The file <bcp14>MUST</bcp14> be rejected if an Update Notification File or a Snapshot File has an invalid syntax (e.g., missing mandatory parameters).
          For validating the IRR objects contained in the files, see <xref target="irr_object_validation" />.
        </li>
      </ul>
    </section>
    <section><name>Processing Delta Files</name>
      <t>
        If a mirror client has previously initialized from a snapshot:
      </t>
      <ul>
        <li>
          The client <bcp14>MUST</bcp14> retrieve the Update Notification File.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> verify that the source attribute in the Update Notification File matches the configured IRR Database name.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> verify that the session_id matches the previously known session_id.
          If this does not match, the client <bcp14>MUST</bcp14> reinitialize from the snapshot.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> verify that the Update Notification File version is the same or higher than the client's current most recent version.
          If not, the Update Notification File <bcp14>MUST</bcp14> be rejected.
          It is <bcp14>RECOMMENDED</bcp14> for the client to distinguish between an Update Notification File that is a single version older, and a much older version, in any status messages.
          The former can occur from time to time in synchronization issues and the latter is more likely a faulty implementation.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> verify that the Update Notification File contains one contiguous set of Delta File versions after the client's current most recent version up to the latest version in the Update Notification File.
          If the Delta File versions are not contiguous, the Update Notification File <bcp14>MUST</bcp14> be rejected.
          If the available Delta File versions do not range from the client's most recent version plus one, the client <bcp14>MUST</bcp14> reinitialize from the snapshot.
        </li>
        <li>
          The mirror client <bcp14>MUST</bcp14> verify that the hashes of each Delta and Snapshot File have not changed compared to the previous valid Update Notification File for the same file type and version.
          If a newer Update Notification File contains a different hash for a specific file, this indicates a misconfiguration in the server and the client <bcp14>MUST</bcp14> reject the Update Notification File.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> retrieve all Delta Files for versions since the client's last known version, if there are any.
        </li>
        <li>
          The mirror client <bcp14>MUST</bcp14> verify that the calculated SHA-256 hash of each newly downloaded Delta File matches the hash in the Update Notification File that referenced it.
          If the Delta File was compressed with GZIP, the hash <bcp14>MUST</bcp14> match the compressed file.
          As the Update Notification File is signed, this hash verification proves the integrity and authenticity for the Delta File.
          In case of a mismatch of this hash, the Delta File <bcp14>MUST</bcp14> be rejected.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> process all changes in the Delta Files in order: lowest Delta File version number first, and in the order of the changes list in the Delta File.
        </li>
        <li>
          The client <bcp14>MUST</bcp14> update its records of the most recent version to the version of the Update Notification File.
        </li>
        <li>
          If an Update Notification File or a Delta File has an invalid syntax (including missing mandatory parameters), the file <bcp14>MUST</bcp14> be rejected.
          For validating the IRR objects contained in the files, see <xref target="irr_object_validation" />.
        </li>
      </ul>
      <t>
        If the Update Notification File or one of the Delta Files is rejected, the mirror client <bcp14>MUST NOT</bcp14> process any newer Deltas than those that are valid and have been successfully verified.
        If some Delta Files are rejected, it <bcp14>MAY</bcp14> process the valid Delta Files, but <bcp14>MUST NOT</bcp14> skip over any rejected Delta Files while doing so.
        Additionally, the changes in a specific Delta File <bcp14>MUST</bcp14> be processed either completely, or not at all, i.e., a Delta File must never be partially processed.
      </t>
    </section>
    <section><name>Error Recovery</name>
      <t>
        When a mirror client fails to retrieve any file due to a transient error, such as a network failure or an HTTP 5xx response, the client <bcp14>SHOULD</bcp14> retry before concluding the retrieval has failed.
        It is <bcp14>RECOMMENDED</bcp14> that implementations use a bounded exponential backoff strategy, starting from a short initial interval (e.g., a few seconds) up to a capped maximum interval (e.g., several minutes), with a bounded total retry duration.
        This prevents unnecessary Snapshot imports on clients and can prevent clients overwhelming a server on transient failures.
        Mirror clients <bcp14>SHOULD</bcp14> log retry and recovery events, including the reason, to assist operators in diagnosing mirroring failures.
      </t>
      <t>
        If a file is rejected, the mirror client <bcp14>MUST NOT</bcp14> load any data from it.
        If the error may be transient, the mirror client <bcp14>SHOULD</bcp14> retry.
        After exhausting retries, if the required Delta Files remain unavailable or are still rejected, the mirror client <bcp14>SHOULD</bcp14> reinitialize from the Snapshot File to prevent using stale data.
        If the Snapshot File itself cannot be retrieved or is rejected after retries, as there is no further fallback, the client <bcp14>SHOULD</bcp14> alert the operator and stop until the issue is resolved.
      </t>
    </section>
    <section><name>Signature and Staleness Verification</name>
      <t>
        Every time a mirror client retrieves a new version of the Update Notification File, it <bcp14>MUST</bcp14> verify the included signature.
        The signature <bcp14>MUST</bcp14> be valid for the configured public key for the contents of the Update Notification File.
        If the signature does not match, the mirror client <bcp14>MUST</bcp14> reject the Update Notification File unless a key rotation is in progress as described in <xref target="public_key_rotation" />.
      </t>
      <t>
        A mirror client can use the generation timestamp in the Update Notification File to check whether the file is stale, as the mirror server must update this file at least every 24 hours.
        If the generation timestamp is more than 24 hours ago, the file is stale and the mirror client <bcp14>SHOULD</bcp14> warn the operator in log messages or other alerting, but <bcp14>MAY</bcp14> continue to process it otherwise.
      </t>
    </section>
    <section><name>Policy Restrictions</name>
      <t>
        A mirror client <bcp14>MAY</bcp14> have a policy that restricts the processing of objects to certain object classes, or other limitations on which objects it processes.
      </t>
      <t>
        If a mirror client has a policy that restricts object processing, this <bcp14>MUST</bcp14> be applied consistently to Snapshot Files and Delta Files from the moment the policy is enacted or modified.
      </t>
    </section>
  </section>


  <section anchor="update_notification_file"><name>Update Notification File</name>
    <section><name>Purpose</name>
      <t>
        The Update Notification File is generated by the mirror server and used by mirror clients to discover whether any changes exist between the state of the IRR mirror server and of the mirror client.
        It also describes the location of the Snapshot File and incremental Delta Files.
        Finally, the generation timestamp can be used to detect whether the file is stale.
      </t>
      <t>
        The mirror server <bcp14>MUST</bcp14> generate a new Update Notification File every time there are new deltas or snapshots and at least every 24 hours, even if there have been no changes.
      </t>
    </section>

    <section><name>Cache Concerns</name>
      <t>
        A mirror server may use caching infrastructure to cache the Update Notification File and reduce the load of HTTPS requests.
      </t>
      <t>
        However, since this file is used by mirror clients to determine whether any updates are available, the mirror server <bcp14>SHOULD</bcp14> ensure that this file is not cached for longer than one minute.
        An exception to this rule is that it is better to serve a stale Update Notification File rather than no Update Notification File.
      </t>
      <t>
        Mirror servers <bcp14>SHOULD</bcp14> set the HTTP <tt>Cache-Control</tt> response header on the Update Notification File to <tt>no-cache</tt> or <tt>max-age=60</tt>, consistent with the one-minute caching limit.
        Mirror servers <bcp14>SHOULD</bcp14> set <tt>Cache-Control: immutable</tt> on responses for Snapshot Files and Delta Files, as these are immutable for a given session_id and version.
        Otherwise, clients and intermediaries may unnecessarily refetch large files.
        Mirror clients <bcp14>MAY</bcp14> use HTTP conditional requests (e.g., using <tt>If-None-Match</tt> with ETags or <tt>If-Modified-Since</tt>) when polling the Update Notification File to reduce bandwidth consumption when no changes have occurred.
      </t>
    </section>

    <section><name>Payload Format and Validation</name>
      <t>
        An example payload of an Update Notification File is provided below:
      </t>
<sourcecode type="json"><![CDATA[
{
  "nrtm_version": 4,
  "timestamp": "2025-12-01T15:00:00Z",
  "type": "notification",
  "next_signing_key": "bnJ0..bXY0",
  "source": "EXAMPLE",
  "session_id": "ca128382-78d9-41d1-8927-1ecef15275be",
  "version": 4,
  "snapshot": {
    "version": 3,
    "url":
"ca128382-78d9-41d1-8927-1ecef15275be/nrtm-snapshot.3.04759.json.gz",
    "hash": "9a..86"
  },
  "deltas": [
    {
      "version": 2,
      "url":
"ca128382-78d9-41d1-8927-1ecef15275be/nrtm-delta.2.784a2a6.json",
      "hash": "62..a2"
    },
    {
      "version": 3,
      "url":
"ca128382-78d9-41d1-8927-1ecef15275be/nrtm-delta.3.0f681f0.json",
      "hash": "25..9a"
    },
    {
      "version": 4,
      "url":
"ca128382-78d9-41d1-8927-1ecef15275be/nrtm-delta.4.d9c194a.json",
      "hash": "b4..13"
    }
  ],
  "metadata": {}
}]]></sourcecode>
     <aside>
      <t>
        Note: Hash and key values in this example are shortened because of formatting.
      </t>
     </aside>
      <t>
        In this example, the overall version is 4, the snapshot is at version 3, and deltas are listed for versions 2, 3, and 4.
        The deltas at versions 2 and 3 predate the snapshot, but are still within the 24-hour retention window.
        A new client would initialize from the snapshot at version 3 and then apply only delta 4.
        An existing client already at version 1 can instead apply deltas 2, 3, and 4 without reinitializing from the snapshot.
      </t>
      <t>
        The following validation rules <bcp14>MUST</bcp14> be observed when creating or parsing Update Notification Files:
      </t>
      <ul>
        <li>
          The nrtm_version <bcp14>MUST</bcp14> be 4.
        </li>
        <li>
          The timestamp <bcp14>MUST</bcp14> be in the format specified in <xref target="RFC3339"/> with the time-offset set to "Z".
        </li>
        <li>
          The type <bcp14>MUST</bcp14> be "notification".
        </li>
        <li>
          The optional field next_signing_key is used for in-band key rotation.
          If present, it <bcp14>MUST</bcp14> be a JWK <xref target="RFC7517"/> public key encoded in PEM, which matches the private key the mirror server will start using to sign the Update Notification File in the near future.
          Key rotation is described in <xref target="public_key_rotation" />.
          If there is no next signing key, this key <bcp14>MUST</bcp14> be omitted.
        </li>
        <li>
          The source <bcp14>MUST</bcp14> be a valid IRR object name <xref target="RFC2622"/>.
        </li>
        <li>
          The session_id attribute <bcp14>MUST</bcp14> be a UUIDv4 (<xref section="5.4" target="RFC9562"/>) unique to this session for this source.
        </li>
        <li>
          The version <bcp14>MUST</bcp14> be an unsigned positive integer and be equal to the highest version of the deltas and snapshot.
        </li>
        <li>
          The file <bcp14>MUST</bcp14> contain exactly one snapshot.
        </li>
        <li>
          The file <bcp14>MAY</bcp14> contain one or more deltas.
        </li>
        <li>
          The deltas <bcp14>MUST</bcp14> have a sequential contiguous set of version numbers.
        </li>
        <li>
          Each snapshot and delta element <bcp14>MUST</bcp14> have a version, URL, and hash attribute.
          The URL must be relative to the path of the Update Notification File.
          For example, if the Update Notification File example above is published on https://example.com/nrtm/update-notification-file.jose, the full URL for the referred snapshot is https://example.com/nrtm/ca128382-78d9-41d1-8927-1ecef15275be/nrtm-snapshot.3.04759.json.gz.
          If the snapshot or delta file was compressed with GZIP, the filename <bcp14>MUST</bcp14> end in ".gz", and the hash <bcp14>MUST</bcp14> match the compressed data.
        </li>
        <li>
          The hash attribute in snapshot and delta elements <bcp14>MUST</bcp14> be the hexadecimal encoding of the SHA-256 hash of the referenced file.
          This hash algorithm, used to verify the integrity of the Snapshot and Delta Files, is fixed and independent of the JWS signing algorithm used for the Update Notification File.
          The mirror client <bcp14>MUST</bcp14> verify this hash when the file is retrieved and reject the file if the hash does not match.
        </li>
        <li>
          The metadata key <bcp14>MAY</bcp14> be present and is used for metadata produced by the server to aid in tracing and debugging.
          This can contain information like the name of the host on which the file was generated or the name and version of the software used.
          Each mirror server may choose which fields to include or choose to not include any metadata.
          The mirror server <bcp14>SHOULD NOT</bcp14> cause excessive size increases by adding extensive metadata in the Update Notification File, as it is the most frequently retrieved file.
        </li>
      </ul>
    </section>
    <section anchor="encoding_and_signature"><name>Encoding and Signature</name>
      <ul>
        <li>
          The actual Update Notification File content is a JSON Web Signature <xref target="RFC7515"/> using JWS Compact Serialization.
        </li>
        <li>
          The JWS Payload is the JSON <xref target="RFC8259"/> serialization of the structure described in the previous section.
        </li>
        <li>
          The filename of the serialized data <bcp14>MUST</bcp14> be "update-notification-file.jose".
        </li>

        <li>
          Mirror clients <bcp14>MUST</bcp14> implement ES256.
          Mirror servers <bcp14>MAY</bcp14> use ES256 or other digital signature algorithms from the IANA "JSON Web Signature and Encryption Algorithms" registry <xref target="IANA_jose"/>; the algorithm <bcp14>MUST NOT</bcp14> be "none", a MAC algorithm, or <tt>Deprecated</tt> or <tt>Prohibited</tt>.
          It is <bcp14>RECOMMENDED</bcp14> to use ES256 or other Recommended or Recommended+ algorithms.
          If a server uses an algorithm other than ES256, it is the server operator's responsibility to ensure their mirror clients support that algorithm.
        </li>
      </ul>
    </section>
  </section>


  <section><name>Snapshot File</name>

    <section><name>Purpose</name>
      <t>
        The Snapshot File reflects the complete and current contents of all IRR objects in an IRR Database.
        Mirror clients <bcp14>MUST</bcp14> use this to initialize their local copy of the IRR Database.
        Snapshot Files are not individually signed.
        Their integrity is verified by comparing the calculated SHA-256 hash with the hash listed in the signed Update Notification File (see <xref target="encoding_and_signature"/>).
      </t>
    </section>

    <section><name>Cache Concerns</name>
      <t>
        A snapshot reflects the content of the IRR Database at a specific point in time; for that reason, it can be considered immutable data.
        Snapshot Files are published at a URL that is unique to the specific session and version.
        The URL also contains a random value that can not be predicted before publication to counter negative caching issues.
      </t>
      <t>
        Because these files never change, they can be cached.
        However, as snapshots are large and old snapshots will no longer be referred by newer Update Notification Files, it is <bcp14>RECOMMENDED</bcp14> that a limited cache interval is used.
      </t>
    </section>

    <section><name>File Format and Validation</name>
      <t>
        Example Snapshot File, where ␞ (U+241E) represents the record separator control character (U+001E) as specified in <xref target="RFC7464"/>:
      </t>
<sourcecode type="json"><![CDATA[
␞{
  "nrtm_version": 4,
  "type": "snapshot",
  "source": "EXAMPLE",
  "session_id": "ca128382-78d9-41d1-8927-1ecef15275be",
  "version": 3
}
␞{"object": "route: 192.0.2.0/24\norigin: AS64500\nsource: EXAMPLE"}
␞{"object": "route6: 2001:db8::/32\norigin: AS64500\nsource: EXAMPLE"}
]]></sourcecode>
<aside>
      <t>
        Note: IRR object texts in this example are shortened because of formatting.
      </t>
</aside>
      <t>
        The file is in JSON Text Sequences <xref target="RFC7464" /> format and <bcp14>MUST</bcp14> contain one or more records (it must contain at least the header).
        The first record is the file header and the following validation rules <bcp14>MUST</bcp14> be observed when creating or parsing a Snapshot File header:
      </t>
      <ul>
        <li>
          The nrtm_version <bcp14>MUST</bcp14> be 4.
        </li>
        <li>
          The type <bcp14>MUST</bcp14> be "snapshot".
        </li>
        <li>
          The source <bcp14>MUST</bcp14> match the source in the Update Notification File.
        </li>
        <li>
          The session_id attribute <bcp14>MUST</bcp14> match the session_id in the Update Notification File.
        </li>
        <li>
          The version <bcp14>MUST</bcp14> be an unsigned positive integer, matching the Update Notification File entry for this snapshot.
        </li>
      </ul>
      <t>
        The remaining records (zero or more) <bcp14>MUST</bcp14> each contain a string representation of an IRR object.
        The source attribute in the IRR object texts <bcp14>MUST</bcp14> match the source attribute of the Snapshot File.
      </t>
    </section>
  </section>

  <section><name>Delta File</name>

    <section><name>Purpose</name>
      <t>
        A Delta File contains all changes for exactly one incremental update of the IRR Database.
        It may include new, modified, and deleted objects. Delta Files can contain multiple alterations to multiple objects.
        Delta Files are not individually signed.
        Their integrity is verified by comparing the calculated SHA-256 hash with the hash listed in the signed Update Notification File (see <xref target="encoding_and_signature"/>).
      </t>
    </section>

    <section><name>Cache Concerns</name>
      <t>
        Deltas reflect the difference in content of the IRR Database from one version to another; for that reason, it can be considered immutable data.
        Delta Files are published at a URL that is unique to the specific session and version.
        The URL also contains a random value that can not be predicted before publication to counter negative caching issues.
      </t>
      <t>
        To avoid race conditions where a mirror client retrieves an Update Notification File moments before it's updated, mirror servers <bcp14>SHOULD</bcp14> retain old Delta Files for at least 5 minutes after a new Update Notification File is published that no longer contains these Delta Files.
      </t>
    </section>

    <section><name>File Format and Validation</name>
      <t>
        Example Delta File, where ␞ (U+241E) represents the record separator control character (U+001E) as   
specified in <xref target="RFC7464"/>:
      </t>
<sourcecode type="json"><![CDATA[
␞{
  "nrtm_version": 4,
  "type": "delta",
  "source": "EXAMPLE",
  "session_id": "ca128382-78d9-41d1-8927-1ecef15275be",
  "version": 3
}
␞{
  "action": "delete",
  "object_class": "person",
  "primary_key": "PRSN1-EXAMPLE"
}
␞{
  "action": "delete",
  "object_class": "route",
  "primary_key": "192.0.2.0/24AS64500"
}
␞{
  "action": "add_modify",
  "object": "route6: 2001:db8::/32\norigin: AS64500\nsource: EXAMPLE"
}]]></sourcecode>
<aside>
      <t>
        Note: IRR object texts in this example are shortened because of formatting.
      </t>
</aside>
      <t>
        The file is in JSON Text Sequences <xref target="RFC7464" /> format and <bcp14>MUST</bcp14> contain two or more records (at least the header and one change).
        The first record is the file header and the following validation rules <bcp14>MUST</bcp14> be observed when creating or parsing a Delta File header:
      </t>
      <ul>
        <li>
          The nrtm_version <bcp14>MUST</bcp14> be 4.
        </li>
        <li>
          The type <bcp14>MUST</bcp14> be "delta".
        </li>
        <li>
          The source <bcp14>MUST</bcp14> match the source in the Update Notification File.
        </li>
        <li>
          The session_id attribute <bcp14>MUST</bcp14> match the session_id in the Update Notification File.
        </li>
        <li>
          The version <bcp14>MUST</bcp14> be an unsigned positive integer, matching the Update Notification File entry for this delta.
        </li>
      </ul>

      <t>
        The remaining records (one or more) <bcp14>MUST</bcp14> each contain a JSON object that represents a change. The JSON object <bcp14>MUST</bcp14> meet the following rules: 
      </t>
      <ul>
        <li>
          It has an "action" attribute, which is either "delete" for object deletions or "add_modify" for additions or modifications.
        </li>
        <li>
          If action is "delete": It has an "object_class" attribute with the RPSL object class name, and a "primary_key" attribute with the primary key of the deleted object.
          For objects that are listed in <xref target="RFC2622"/> and <xref target="RFC4012"/>, the primary key is the value of the RPSL field defined as "class key".
          For object classes that define a pair of attributes as class key, e.g. route, the values of the individual attributes are appended together without separators.
          For any other objects, the primary key is the value of the RPSL field with the same name as the object class name.
          The primary key and object class name are not case-sensitive. Therefore, mirror clients <bcp14>MUST</bcp14> use case-insensitive matching against their local database.
        </li>
        <li>
          If action is "add_modify": It has an "object" attribute with the RPSL text of the new version of the object.
      </li>
      </ul>

    </section>
  </section>

  <section><name>Operational Considerations</name>

    <section><name>Time</name>
      <t>
        IRR clients and servers are <bcp14>RECOMMENDED</bcp14> to use <xref target="RFC5905">NTP</xref> synchronization to avoid timing discrepancies.
      </t>
    </section>

    <section anchor="irr_object_validation"><name>IRR Object Validation</name>
      <t>
        Throughout the years, various implementations of IRR servers have taken liberties with the various RFCs regarding RPSL.
        Implementations have introduced different new object classes, attributes, and validation rules.
        Current IRR Databases also contain legacy objects that were created under different validation rules.
        In practice, there is no uniformly implemented standard for RPSL, but merely rough outlines partially documented in different places.
      </t>
      <t>
        This has the potential to create interoperability issues.
        Some are addressed by NRTMv4, like having a consistent character set when mirroring data between implementations.
        However, some issues can not be addressed in this way, such as one implementation introducing a new object class that is entirely unknown to another implementation.
      </t>
      <t>
        A mirror client <bcp14>SHOULD</bcp14> be able to handle unknown object classes and objects that are invalid according to its own validation rules, which may mean simply discarding them without rejecting remaining objects or preventing future updates.
      </t>
      <t>
        It is <bcp14>RECOMMENDED</bcp14> for mirror clients to log these cases, particularly those where an object was discarded due to violating validation rules.
        These cases create an inconsistency between the IRR objects of the server and client, and logs facilitate later analysis.
      </t>
      <t>
        It is recommended for mirror clients to be flexible where possible and reasonable when applying their own validation rules to IRR objects retrieved from mirror servers.
        For example, a route object with an origin attribute that is not a valid AS number can't be usefully interpreted.
        There is no way for an IRR server to correctly parse and index such an object.
        However, a route-set object whose name does not start with "RS-" <xref target="RFC2622"/>, or an inetnum with an unknown extra "org" attribute, still allows the mirror client to interpret it unambiguously even if it does not meet the mirror client's own validation rules for authoritative records.
      </t>
    </section>
    <section><name>Intermediate Mirror Instances</name>
      <t>
        An IRR Database generally has a single authoritative source.
        In some cases, an instance run by a third party will function as a kind of intermediate: both being a mirror client, mirroring IRR objects from the authoritative source, and simultaneously functioning as a mirror server to yet another mirror client.
      </t>
      <t>
        There are various operational reasons for such a setup, such as the intermediate filtering certain records.
        Regardless of the reason, the mirror client and server function of an IRR server must be treated as separate processes.
        In particular, this means they <bcp14>MUST</bcp14> have separate session IDs.
        The intermediate server <bcp14>MUST NOT</bcp14> republish the same files it retrieved from the authoritative source with the same session ID.
      </t>
    </section>

    <section><name>Reading from Local Files</name>
      <t>
        In the typical use case for NRTMv4, a mirror client retrieves files from an HTTPS endpoint.
        However, implementations <bcp14>MAY</bcp14> also support reading from files on the local filesystem instead for when operators want to use a different method to retrieve or distribute the files.
        When reading from local files, mirror clients <bcp14>SHOULD</bcp14> still follow all validation rules, including the validation of the signature and hashes, to prevent corrupted or tampered data from being loaded.
      </t>
    </section>

    <section anchor="storage"><name>Storage Considerations</name>
      <t>
        After publishing a new Update Notification File and absent local policy, a mirror server <bcp14>SHOULD</bcp14> remove any Snapshot and Delta Files that are no longer referenced, as unreferenced files consume storage unnecessarily.
        To avoid race conditions where a mirror client retrieves an Update Notification File moments before it is updated, mirror servers <bcp14>SHOULD</bcp14> retain unreferenced files for at least 5 minutes after a new Update Notification File is published.
      </t>
    </section>
    <section anchor="public_key_rotation"><name>Public Key Rotation</name>
      <t>
        It is recommended that the IRR Database operators rotate the signing key on their mirror server with a frequency that is not disruptive to operations but preserves the familiarity of the practices to accomplish key rotation.
        Many organizations have settled on annual cycles.
        The next_signing_key field in the Update Notification File supports in-band key rotation using the following process:
      </t>
        <ul>
          <li>
            The server operator generates a new key and configures this in the mirror server implementation as the upcoming new signing key.
          </li>
          <li>
            The mirror server <bcp14>MUST</bcp14> include this key in the next_signing_key field in any Update Notification File generated while the new signing key is configured.
            Hence, the new signing key will start being propagated to the mirror clients with the next publication of the Notification File, which will take at most 24 hours.
            Mirror server implementations <bcp14>MAY</bcp14> offer a method to cause the Update Notification File to be refreshed earlier, with the next_signing_key included, and thus start the propagation earlier.
          </li>
          <li>
            When mirror clients retrieve the Update Notification File next, they <bcp14>MUST</bcp14> detect the next_signing_key field and store the key in their configuration.
          </li>
          <li>
            After allowing mirror clients time to have seen the new Update Notification File with the next_signing_key field, the mirror server operator configures the new key as the currently active key and removes the old key.
            Any Update Notification File generated after this point <bcp14>MUST</bcp14> be signed with this new key and will not contain a next_signing_key field.
          </li>
          <li>
            The <bcp14>RECOMMENDED</bcp14> period between publication of the upcoming key in the next_signing_key field and removal of the old key is one week. This offers all active clients a reasonable chance to follow the rotation process.
          </li>
          <li>
            When mirror clients retrieve an Update Notification File and find that the signature does not match, they <bcp14>MUST</bcp14> attempt to verify against a next_signing_key encountered in a previous (valid) file.
            If the signature matches for this new key, the client <bcp14>MUST</bcp14> update its configuration to use the new key for validation.
            After this, the client <bcp14>MUST NOT</bcp14> use the old key for validation at any time; a mirror server cannot switch back to an old key.
          </li>
        </ul>
      <t>
        If a mirror client never retrieves an Update Notification file at any point during the rotation process, it will no longer be able to verify the signature.
        In that scenario manual recovery is required, similar to a first time configuration of a new mirror client.
      </t>
    </section>

    <section><name>Scalability</name>
      <t>
        As NRTMv4 uses HTTPS for all file retrieval, mirror servers can use standard HTTP caching infrastructure, horizontal scaling, and CDN integration to handle load.
        Caching considerations for each file type are discussed in the respective Cache Concerns sections.
      </t>
      <t>
        Delta Files are typically small, as they only contain changes since the previous version.
        Snapshot Files can be larger, but all files may be compressed with GZIP to reduce storage and bandwidth requirements.
      </t>
    </section>

    <section><name>NRTMv3 Compatibility</name>
      <t>
        NRTMv4 is a new protocol that is not backwards compatible with NRTMv3.
        There is no migration path between the two protocols; operators wishing to support both can run them in parallel.
      </t>
    </section>
  </section>

  <section anchor="IANA"><name>IANA Considerations</name>
    <t>
      This document has no IANA actions.
    </t>
  </section>

  <section anchor="security_considerations"><name>Security Considerations</name>
    <t>
      IRR objects serve many purposes, including automated network configuration and filtering.
      Manipulation of IRR objects can therefore have a significant security impact.
      However, security in existing protocols is mostly absent.
    </t>
    <t>
      Before NRTMv4, the most common protocols for IRR Database mirroring are FTP for retrieving full snapshots and NRTM version 3 for retrieving later changes.
      There are no provisions for integrity or authenticity and there are various scenarios where mirroring may not be reliable.
    </t>
    <t>
      NRTMv4 requires integrity verification.
      The Update Notification File is signed and clients must verify its signature.
      The signed Update Notification File contains SHA-256 hashes of all Delta and Snapshot Files, which clients must verify through calculating and comparing hashes on retrieval.
      Together, the signature and hash verification form a chain of trust from the signing key to each individual file.
      Additionally, the channel security offered by HTTPS further limits security risks.
    </t>
    <t>
      By allowing publication on any HTTPS endpoint, NRTMv4 allows for extensive scaling and there are many existing techniques and services to protect against denial-of-service attacks.
      In contrast, NRTMv3 required mirror clients to directly query the IRR server instance with special WHOIS queries.
      This scales poorly and there are no standard protections against denial-of-service available.
    </t>
    <t>
      Since Snapshot and Delta Files may be compressed with GZIP, a maliciously crafted compressed file could expand to a much larger size than expected, potentially exhausting memory or disk resources.
      Implementations <bcp14>SHOULD</bcp14> enforce limits on the decompressed size of files relative to the compressed size or the expected data volume for the IRR Database.
      See also the security considerations of <xref target="RFC6713"/>.
    </t>
    <t>
      The HTTPS endpoint used for NRTMv4 <bcp14>MUST</bcp14> be configured according to the best practices in <xref target="BCP195"/>.
      Mirror clients <bcp14>MUST NOT</bcp14> use other protocols than HTTPS, such as HTTP or FTP.
    </t>
  </section>

</middle>

<back>

  <references><name>References</name>
  <references><name>Normative References</name>

    <xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.STD.97.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.1952.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2622.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9562.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4012.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7464.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7468.xml"/>    
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7515.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7517.xml"/>

    <xi:include href="https://bib.ietf.org/public/rfc/bibxml-iana/reference.IANA.jose.xml"/>

    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/>

    <xi:include href="https://bib.ietf.org/public/rfc/bibxml9/reference.BCP.195.xml"/>

    <reference anchor="SHS" target="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">
      <front>
        <title>Secure Hash Standard (SHS)</title>
        <author>
          <organization abbrev="NIST">National Institute of Standards and Technology</organization>
        </author>
        <date month="August" year="2015"/>
      </front>
      <seriesInfo name="NIST FIPS" value="180-4"/>
      <seriesInfo name="DOI" value="10.6028/NIST.FIPS.180-4"/>
    </reference>
    
  </references>

  <references><name>Informative References</name>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5905.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6713.xml"/>
    <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8182.xml"/>

    <reference anchor="NRTMv3" target="https://docs.db.ripe.net/RIPE-Database-Mirror/Access-to-NRTM/">
      <front>
        <title>Access to NRTM</title>
        <author>
        <organization>RIPE NCC</organization>
        </author>
        <date month="March" year="2026" />
      </front>
    </reference>

  </references>
  </references>

  <section numbered="false"><name>Acknowledgments</name>
    <t>
      The authors would like to thank
        <contact fullname="George Michaelson"/>, <contact fullname="Shon Huang"/>, <contact fullname="Tim Bruijnzeels"/>, <contact fullname="Mahesh Aggarwal"/>, <contact fullname="Fedor Vompe"/>, <contact fullname="Paul Etchells"/>,
        and <contact fullname="Mohamed Boucadair"/>
      for their helpful review of this document and/or work on implementations.
      The authors would also like to thank
        <contact fullname="Daniele Ceccarelli"/>, <contact fullname="Claudio Allocchio"/>, <contact fullname="Menachem Dodge"/>, <contact fullname="Julian Reschke"/>, <contact fullname="Watson Ladd"/>, and <contact fullname="Paul Kyzivat"/>
      for their reviews during IETF Last Call.
      The authors thank <contact fullname="Gorry Fairhurst"/>, <contact fullname="Andy Newton"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Mike Bishop"/>, <contact fullname="Deb Cooley"/>, <contact fullname="Roman Danyliw"/>, <contact fullname="Mahesh Jethanandani"/>, <contact fullname="Ketan Talaulikar"/>, <contact fullname="Gunter Van de Velde"/>, <contact fullname="Christopher Inacio"/>, <contact fullname="Jim Guichard"/>, and <contact fullname="Tommy Jensen"/> for the reviews and feedback.
    </t>
  </section>

</back>

</rfc>
