Status of This Memo

This is an Internet Standards Track document.¶

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9713.¶

Copyright Notice

Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

The earlier Bundle Protocol (BP) Version 6 (BPv6) defined an IANA registry for Administrative Record type code points under [IANA-BP]. When Bundle Protocol Version 7 (BPv7) was published in [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.¶

This document updates BPv7 to explicitly use the IANA Administrative Record type registry as described in Section 2. 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 [RFC8126] to avoid collisions with assigned code points.¶

2. Administrative Record Types Registry

This document updates the requirements in Section 6.1 of [RFC9171] to specify use of an existing IANA registry and updates that registry as described in Section 4.1.¶

The code point allocated in Annex D of [CCSDS-BP] 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 as described in Section 6.1 of [RFC9171], a BPv7 administrative element SHALL interpret administrative record type code values in accordance with the IANA "Bundle Administrative Record Types" registry [IANA-BP] for entries having a "Bundle Protocol Version" of 7.¶

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 BPA processing of (e.g., status reports on) the enveloping bundle.¶

3. Security Considerations

This document does not define any requirements or structures that introduce new security considerations.¶

The existing security considerations of [RFC9171] still apply when using the IANA "Bundle Administrative Record Types" registry.¶

4. IANA Considerations

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

Acknowledgments

Author's Address