<?xml version="1.0" encoding="UTF-8"?>
<?rfc toc="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" consensus="true" docName="draft-ietf-dtn-bpv7-admin-iana-04" ipr="trust200902" submissionType="IETF" tocInclude="true" updates="9171" version="3">
  <front>
    <title abbrev="BPv7 Admin IANA">
Bundle Protocol Version 7 Administrative Record Types Registry
    </title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-dtn-bpv7-admin-iana-04"/>
    <author fullname="Brian Sipos" initials="B." surname="Sipos">
      <organization abbrev="JHU/APL">The Johns Hopkins University Applied Physics Laboratory</organization>
      <address>
        <postal>
          <street>11100 Johns Hopkins Rd.</street>
          <city>Laurel</city>
          <region>MD</region>
          <code>20723</code>
          <country>United States of America</country>
        </postal>
        <email>brian.sipos+ietf@gmail.com</email>
      </address>
    </author>
    <date/>
    <area>Transport</area>
    <workgroup>Delay-Tolerant Networking</workgroup>
    <keyword>DTN</keyword>
    <abstract>
      <t>
This document updates RFC 9171 to clarify that a Bundle Protocol Version 7 agent is intended to use an IANA registry for Administrative Record types.
It also makes a code point reservations for private and experimental use.
      </t>
    </abstract>
  </front>
  <middle>
    <section anchor="sec-intro">
      <name>Introduction</name>
      <t>
The earlier Bundle Protocol (BP) Version 6 (BPv6) defined an IANA registry for Administrative Record type code points under <xref target="IANA-BP"/>.
When Bundle Protocol Version 7 (BPv7) was published in <xref target="RFC9171"/> it identified the IANA registry for Administrative Record types but did not update the table to be explicit about which entries applied to which Bundle Protocol version(s).
The BPv7 specification also did not discriminate between code point reservations and unassigned ranges for Administrative Record types.
      </t>
      <t>
This document updates BPv7 to explicitly use the IANA Administrative Record type registry in <xref target="sec-bpv7-admin-type"/>.
This document makes a reservation of the zero value for consistency with BPv6.
This document also makes a reservation of high-valued code points for private use and experimental use in accordance with <xref target="RFC8126"/> to avoid collisions with assigned code points.
      </t>
      <section>
        <name>Scope</name>
        <t>
This document describes updates to the IANA Administrative Record type registry and how a BPv7 agent is supposed to use that registry for identifying Administrative Record types.
        </t>
        <t>
This document does not specify how BPv6 and BPv7 can interoperate for overlapping code points or how a specific code point is to be interpreted either similarly or differently between Bundle Protocol versions.
It is up to each individual Administrative Record type specification to define how it relates to each BP version.
        </t>
      </section>
      <section anchor="sec-terminology">
        <name>Terminology</name>
        <t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.
        </t>
      </section>
    </section>
    <section anchor="sec-bpv7-admin-type">
      <name>Administrative Record Types Registry</name>
      <t>
This document updates the requirements in <xref section="6.1" target="RFC9171"/> to use an existing IANA registry and updates that registry in <xref target="sec-iana-bp-admin-type"/>.
      </t>
      <t>
The code point allocated in Annex D of <xref target="CCSDS-BP"/> was never added to the IANA registry.
To avoid a collision, this document adds that allocation to the registry.
      </t>
      <t>
Instead of using the list of types in <xref section="6.1" target="RFC9171"/>, a BPv7 administrative element <bcp14>SHALL</bcp14> interpret administrative record type code values in accordance with the IANA "Bundle Administrative Record Types" registry under <xref target="IANA-BP"/> for entries having a "Bundle Protocol Version" of 7.
      </t>
      <t>
If an administrative element receives a not-well-formed application data unit (ADU) or an administrative record type code which is not able to be processed by the element, the record <bcp14>SHALL</bcp14> be ignored by the element.
The processing of a received administrative record ADU does not affect the fact that the bundle itself was delivered to the administrative element or any related BPA processing of (e.g. status reports on) the enveloping bundle.
      </t>
    </section>
    <section anchor="sec-security">
      <name>Security Considerations</name>
      <t>
This document does not define any requirements or structures which introduce new security considerations.
      </t>
      <t>
The existing security considerations of <xref target="RFC9171"/> still apply when using the IANA Administrative Record Types registry.
      </t>
    </section>
    <section anchor="sec-iana">
      <name>IANA Considerations</name>
      <t>
This specification modifies a BPv6 registry to extend BPv7.
      </t>
      <section anchor="sec-iana-bp-admin-type">
        <name>Bundle Administrative Record Types</name>
        <t>
Within the "Bundle Protocol" registry group <xref target="IANA-BP"/>, the "Bundle Administrative Record Types" registry has been updated to include a leftmost "Bundle Protocol Version" column.
New entries have been added and existing entries have been updated to have BP versions as in the following table.
This document makes no changes to the registration procedures for this registry.
        </t>
        <table>
          <name>Bundle Administrative Record Types</name>
          <thead>
            <tr>
              <th>Bundle Protocol Version</th>
              <th>Value</th>
              <th>Description</th>
              <th>Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td>6,7</td>
              <td>0</td>
              <td>Reserved</td>
              <td>
                <xref target="RFC7116"/>
                [This specification]
              </td>
            </tr>
            <tr>
              <td>6,7</td>
              <td>1</td>
              <td>Bundle status report</td>
              <td>
                <xref target="RFC5050"/>
                <xref target="RFC9171"/>
              </td>
            </tr>
            <tr>
              <td>6</td>
              <td>2</td>
              <td>Custody signal</td>
              <td>
                <xref target="RFC5050"/>
              </td>
            </tr>
            <tr>
              <td>6,7</td>
              <td>3</td>
              <td>Unassigned</td>
              <td/>
            </tr>
            <tr>
              <td>6</td>
              <td>4</td>
              <td>Aggregate Custody Signal</td>
              <td>
                <xref target="CCSDS-BP"/>
              </td>
            </tr>
            <tr>
              <td>6,7</td>
              <td>5 to 15</td>
              <td>Unassigned</td>
              <td/>
            </tr>
            <tr>
              <td>7</td>
              <td>16 to 64383</td>
              <td>Unassigned</td>
              <td/>
            </tr>
            <tr>
              <td>7</td>
              <td>64384 to 64511</td>
              <td>Reserved for experimental use</td>
              <td>[This specification]</td>
            </tr>
            <tr>
              <td>7</td>
              <td>64512 to 65535</td>
              <td>Reserved for private use</td>
              <td>[This specification]</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <reference anchor="IANA-BP" target="https://www.iana.org/assignments/bundle/">
          <front>
            <title>Bundle Protocol</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.9171.xml"/>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="CCSDS-BP" target="https://public.ccsds.org/Pubs/734x2b1.pdf">
          <front>
            <title>CCSDS Bundle Protocol Specification</title>
            <seriesInfo name="CCSDS" value="734.2-B-1"/>
            <author>
              <organization>Consultative Committee for Space Data Systems</organization>
            </author>
            <date month="September" year="2015"/>
          </front>
        </reference>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5050.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.7116.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
      </references>
    </references>
    <section anchor="sec-doc-ack" numbered="false">
      <name>Acknowledgments</name>
      <t>
      </t>
    </section>
  </back>
</rfc>
