Bundle Protocol Version 7 Administrative Record Types Registry

Introduction An earlier specification defined an IANA registry for administrative record type code points for use with the Bundle Protocol (BP) Version 6 (BPv6) . When Bundle Protocol Version 7 (BPv7) was published in , 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. This document updates BPv7 to explicitly use the IANA "Bundle Administrative Record Types" registry as described in . 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 to avoid collisions with assigned code points.

Scope This document describes updates to the IANA "Bundle Administrative Record Types" registry and how a BPv7 agent is supposed to use that registry to identify administrative record types. This document does not specify how BPv6 and BPv7 can interoperate when both use the same code points or how a specific code point is to be interpreted either similarly or differently by Bundle Protocol versions. The specification for each administrative record type is to define how the administrative record type relates to each BP version.

Terminology 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 when, and only when, they appear in all capitals, as shown here.

Administrative Record Types Registry This document updates the requirements in to specify use of an existing IANA registry and updates that registry as described in . The code point allocated in Annex D of was never added to the IANA registry. To avoid a collision, this document adds that allocation to the registry. Instead of using the list of types in , a BPv7 administrative element SHALL determine which administrative record type code values can be used by the "7" noted in the Bundle Protocol Version column of the IANA "Bundle Administrative Record Types" registry . If an administrative element receives a not-well-formed application data unit (ADU) or an administrative record type code that is not able to be processed by the element, the record SHALL 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 bundle protocol agent processing of (e.g., status reports on) the enveloping bundle.

Security Considerations This document does not define any requirements or structures that introduce new security considerations. The existing security considerations of still apply when using the IANA "Bundle Administrative Record Types" registry.

IANA Considerations This specification modifies a BPv6 registry by extending it for BPv7.

Bundle Administrative Record Types Within the "Bundle Protocol" registry group , 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 include BP versions as in . This document makes no changes to the registration procedures for this registry. Bundle Administrative Record Types

Bundle Protocol Version	Value	Description	Reference
6,7	0	Reserved	RFC 9713
6,7	1	Bundle status report
6	2	Custody signal
	3	Unassigned
6	4	Aggregate Custody Signal
	5 - 15	Unassigned
7	16 - 64383	Unassigned
7	64384 - 64511	Reserved for Experimental Use	RFC 9713
7	64512 - 65535	Reserved for Private Use	RFC 9713