rfc-9713

Bundle Protocol Version 7 Administrative Record Types Registry

B. Sipos
date2025-01 streamIETF areaint wgdtn statusPROPOSED STANDARD pages5 canonicalhttps://www.rfc-editor.org/rfc/rfc9713 doi10.17487/RFC9713
This document updates RFC 9171 to clarify that Bundle Protocol Version 7 agents are expected to use the IANA "Bundle Administrative Record Types" registry to identify and document administrative record types. This document also designates code points for Private and Experimental Use.

updates

Extracted elements (9)

design-rationale §1

High-valued code points (64384-65535) are reserved for Private and Experimental Use in accordance with RFC 8126 to avoid collisions with assigned code points. This prevents implementations using private or experimental record types from inadvertently conflicting with future IANA-assigned types.

registry

design-rationale §2

The CCSDS-BP code point allocation (value 4, Aggregate Custody Signal) was never added to the IANA registry when BPv7 was published. RFC 9713 adds it explicitly to avoid future collision with new assignments.

registry

design-rationale §1

The zero value is reserved for consistency with BPv6, which had previously reserved it. This maintains alignment between BPv6 and BPv7 code point allocations.

registry

interoperability-note §1.1

This document does not specify how BPv6 and BPv7 interoperate when both use the same code points, nor how a specific code point is to be interpreted similarly or differently between BP versions. Each administrative record type specification is responsible for defining its relationship to each BP version.

registry

normative-requirement §2 REQUIRED

A BPv7 administrative element SHALL determine which administrative record type code values can be used by consulting the 'Bundle Protocol Version' column of the IANA 'Bundle Administrative Record Types' registry, using entries marked '7'.

registry

normative-requirement §2 REQUIRED

If an administrative element receives a not-well-formed ADU or an administrative record type code that cannot be processed, the record SHALL be ignored by the element. This does not affect bundle delivery or related bundle protocol agent processing.

registry

protocol-element §4.1

Bundle Administrative Record Types code point table: value 0 is Reserved (BPv6,7); value 1 is Bundle Status Report (BPv6,7); value 2 is Custody Signal (BPv6 only); value 4 is Aggregate Custody Signal (BPv6 only, from CCSDS-BP); values 16-64383 are Unassigned for BPv7; values 64384-64511 are Experimental Use for BPv7; values 64512-65535 are Private Use for BPv7.

registry

registry §4.1

The IANA 'Bundle Administrative Record Types' registry has been updated to add a 'Bundle Protocol Version' column, add new entries, and update existing entries to indicate which BP version(s) each record type applies to. Code points 64384-64511 are reserved for Experimental Use and 64512-65535 for Private Use under BPv7.

registry

security-consideration §3

RFC 9713 does not define any requirements or structures that introduce new security considerations. The existing security considerations of RFC 9171 continue to apply when using the IANA 'Bundle Administrative Record Types' registry.

security