rfc9713.original   rfc9713.txt 
Delay-Tolerant Networking B. Sipos Internet Engineering Task Force (IETF) B. Sipos
Internet-Draft JHU/APL Request for Comments: 9713 JHU/APL
Updates: 9171 (if approved) 3 October 2024 Updates: 9171 January 2025
Intended status: Standards Track Category: Standards Track
Expires: 6 April 2025 ISSN: 2070-1721
Bundle Protocol Version 7 Administrative Record Types Registry Bundle Protocol Version 7 Administrative Record Types Registry
draft-ietf-dtn-bpv7-admin-iana-04
Abstract Abstract
This document updates RFC 9171 to clarify that a Bundle Protocol This document updates RFC 9171 to clarify that Bundle Protocol
Version 7 agent is intended to use an IANA registry for Version 7 agents are expected to use the IANA "Bundle Administrative
Administrative Record types. It also makes a code point reservations Record Types" registry to identify and document administrative record
for private and experimental use. types. This document also designates code points for Private and
Experimental Use.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 6 April 2025. 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 Notice
Copyright (c) 2024 IETF Trust and the persons identified as the Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Scope
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology
2. Administrative Record Types Registry . . . . . . . . . . . . 3 2. Administrative Record Types Registry
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations
4.1. Bundle Administrative Record Types . . . . . . . . . . . 4 4.1. Bundle Administrative Record Types
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. References
5.1. Normative References . . . . . . . . . . . . . . . . . . 4 5.1. Normative References
5.2. Informative References . . . . . . . . . . . . . . . . . 5 5.2. Informative References
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
The earlier Bundle Protocol (BP) Version 6 (BPv6) defined an IANA An earlier specification [RFC7116] defined an IANA registry for
registry for Administrative Record type code points under [IANA-BP]. administrative record type code points [IANA-BP] for use with the
When Bundle Protocol Version 7 (BPv7) was published in [RFC9171] it Bundle Protocol (BP) Version 6 (BPv6) [RFC5050]. When Bundle
identified the IANA registry for Administrative Record types but did Protocol Version 7 (BPv7) was published in [RFC9171], it identified
not update the table to be explicit about which entries applied to the IANA registry for administrative record types but did not update
which Bundle Protocol version(s). The BPv7 specification also did the table to be explicit about which entries applied to which Bundle
not discriminate between code point reservations and unassigned Protocol version(s). The BPv7 specification also did not
ranges for Administrative Record types. discriminate between code point reservations and unassigned ranges
for administrative record types.
This document updates BPv7 to explicitly use the IANA Administrative This document updates BPv7 to explicitly use the IANA "Bundle
Record type registry in Section 2. This document makes a reservation Administrative Record Types" registry as described in Section 2.
of the zero value for consistency with BPv6. This document also This document makes a reservation of the zero value for consistency
makes a reservation of high-valued code points for private use and with BPv6. This document also makes a reservation of high-valued
experimental use in accordance with [RFC8126] to avoid collisions code points for Private Use and Experimental Use in accordance with
with assigned code points. [RFC8126] to avoid collisions with assigned code points.
1.1. Scope 1.1. Scope
This document describes updates to the IANA Administrative Record This document describes updates to the IANA "Bundle Administrative
type registry and how a BPv7 agent is supposed to use that registry Record Types" registry and how a BPv7 agent is supposed to use that
for identifying Administrative Record types. registry to identify administrative record types.
This document does not specify how BPv6 and BPv7 can interoperate for This document does not specify how BPv6 and BPv7 can interoperate
overlapping code points or how a specific code point is to be when both use the same code points or how a specific code point is to
interpreted either similarly or differently between Bundle Protocol be interpreted either similarly or differently by Bundle Protocol
versions. It is up to each individual Administrative Record type versions. The specification for each administrative record type is
specification to define how it relates to each BP version. to define how the administrative record type relates to each BP
version.
1.2. Terminology 1.2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. Administrative Record Types Registry 2. Administrative Record Types Registry
This document updates the requirements in Section 6.1 of [RFC9171] to This document updates the requirements in Section 6.1 of [RFC9171] to
use an existing IANA registry and updates that registry in specify use of an existing IANA registry and updates that registry as
Section 4.1. described in Section 4.1.
The code point allocated in Annex D of [CCSDS-BP] was never added to 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 the IANA registry. To avoid a collision, this document adds that
allocation to the registry. allocation to the registry.
Instead of using the list of types in Section 6.1 of [RFC9171], a Instead of using the list of types in Section 6.1 of [RFC9171], a
BPv7 administrative element SHALL interpret administrative record BPv7 administrative element SHALL determine which administrative
type code values in accordance with the IANA "Bundle Administrative record type code values can be used by the "7" noted in the Bundle
Record Types" registry under [IANA-BP] for entries having a "Bundle Protocol Version column of the IANA "Bundle Administrative Record
Protocol Version" of 7. Types" registry [IANA-BP].
If an administrative element receives a not-well-formed application If an administrative element receives a not-well-formed application
data unit (ADU) or an administrative record type code which is not 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 able to be processed by the element, the record SHALL be ignored by
the element. The processing of a received administrative record ADU the element. The processing of a received administrative record ADU
does not affect the fact that the bundle itself was delivered to the does not affect the fact that the bundle itself was delivered to the
administrative element or any related BPA processing of (e.g. status administrative element or any related bundle protocol agent
reports on) the enveloping bundle. processing of (e.g., status reports on) the enveloping bundle.
3. Security Considerations 3. Security Considerations
This document does not define any requirements or structures which This document does not define any requirements or structures that
introduce new security considerations. introduce new security considerations.
The existing security considerations of [RFC9171] still apply when The existing security considerations of [RFC9171] still apply when
using the IANA Administrative Record Types registry. using the IANA "Bundle Administrative Record Types" registry.
4. IANA Considerations 4. IANA Considerations
This specification modifies a BPv6 registry to extend BPv7. This specification modifies a BPv6 registry by extending it for BPv7.
4.1. Bundle Administrative Record Types 4.1. Bundle Administrative Record Types
Within the "Bundle Protocol" registry group [IANA-BP], the "Bundle Within the "Bundle Protocol" registry group [IANA-BP], the "Bundle
Administrative Record Types" registry has been updated to include a Administrative Record Types" registry has been updated to include a
leftmost "Bundle Protocol Version" column. New entries have been leftmost "Bundle Protocol Version" column. New entries have been
added and existing entries have been updated to have BP versions as added and existing entries have been updated to include BP versions
in the following table. This document makes no changes to the as in Table 1. This document makes no changes to the registration
registration procedures for this registry. procedures for this registry.
+=================+==========+==================+=================+ +=========================+=========+==================+============+
| Bundle Protocol | Value | Description | Reference | | Bundle Protocol | Value | Description | Reference |
| Version | | | | | Version | | | |
+=================+==========+==================+=================+ +=========================+=========+==================+============+
| 6,7 | 0 | Reserved | [RFC7116] [This | | 6,7 | 0 | Reserved | [RFC7116] |
| | | | specification] | | | | | RFC 9713 |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 6,7 | 1 | Bundle status | [RFC5050] | | 6,7 | 1 | Bundle status | [RFC5050] |
| | | report | [RFC9171] | | | | report | [RFC9171] |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 6 | 2 | Custody signal | [RFC5050] | | 6 | 2 | Custody signal | [RFC5050] |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 6,7 | 3 | Unassigned | | | | 3 | Unassigned | |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 6 | 4 | Aggregate | [CCSDS-BP] | | 6 | 4 | Aggregate | [CCSDS-BP] |
| | | Custody Signal | | | | | Custody Signal | |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 6,7 | 5 to 15 | Unassigned | | | | 5 - 15 | Unassigned |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+-------------------------------+
| 7 | 16 to | Unassigned | | | 7 | 16 - | Unassigned |
| | 64383 | | | | | 64383 | |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 7 | 64384 to | Reserved for | [This | | 7 | 64384 - | Reserved for | RFC 9713 |
| | 64511 | experimental use | specification] | | | 64511 | Experimental Use | |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
| 7 | 64512 to | Reserved for | [This | | 7 | 64512 - | Reserved for | RFC 9713 |
| | 65535 | private use | specification] | | | 65535 | Private Use | |
+-----------------+----------+------------------+-----------------+ +-------------------------+---------+------------------+------------+
Table 1: Bundle Administrative Record Types Table 1: Bundle Administrative Record Types
5. References 5. References
5.1. Normative References 5.1. Normative References
[IANA-BP] IANA, "Bundle Protocol", [IANA-BP] IANA, "Bundle Protocol",
<https://www.iana.org/assignments/bundle/>. <https://www.iana.org/assignments/bundle/>.
skipping to change at page 5, line 21 skipping to change at line 200
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC9171] Burleigh, S., Fall, K., and E. Birrane, III, "Bundle [RFC9171] Burleigh, S., Fall, K., and E. Birrane, III, "Bundle
Protocol Version 7", RFC 9171, DOI 10.17487/RFC9171, Protocol Version 7", RFC 9171, DOI 10.17487/RFC9171,
January 2022, <https://www.rfc-editor.org/info/rfc9171>. January 2022, <https://www.rfc-editor.org/info/rfc9171>.
5.2. Informative References 5.2. Informative References
[CCSDS-BP] Consultative Committee for Space Data Systems, "CCSDS [CCSDS-BP] Consultative Committee for Space Data Systems, "CCSDS
Bundle Protocol Specification", CCSDS 734.2-B-1, September Bundle Protocol Specification", CCSDS Recommended
2015, <https://public.ccsds.org/Pubs/734x2b1.pdf>. Standard, CCSDS 734.2-B-1, September 2015,
<https://public.ccsds.org/Pubs/734x2b1.pdf>.
[RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol [RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol
Specification", RFC 5050, DOI 10.17487/RFC5050, November Specification", RFC 5050, DOI 10.17487/RFC5050, November
2007, <https://www.rfc-editor.org/info/rfc5050>. 2007, <https://www.rfc-editor.org/info/rfc5050>.
[RFC7116] Scott, K. and M. Blanchet, "Licklider Transmission [RFC7116] Scott, K. and M. Blanchet, "Licklider Transmission
Protocol (LTP), Compressed Bundle Header Encoding (CBHE), Protocol (LTP), Compressed Bundle Header Encoding (CBHE),
and Bundle Protocol IANA Registries", RFC 7116, and Bundle Protocol IANA Registries", RFC 7116,
DOI 10.17487/RFC7116, February 2014, DOI 10.17487/RFC7116, February 2014,
<https://www.rfc-editor.org/info/rfc7116>. <https://www.rfc-editor.org/info/rfc7116>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
Acknowledgments
Author's Address Author's Address
Brian Sipos Brian Sipos
The Johns Hopkins University Applied Physics Laboratory The Johns Hopkins University Applied Physics Laboratory
11100 Johns Hopkins Rd. 11100 Johns Hopkins Rd.
Laurel, MD 20723 Laurel, MD 20723
United States of America United States of America
Email: brian.sipos+ietf@gmail.com Email: brian.sipos+ietf@gmail.com
 End of changes. 25 change blocks. 
113 lines changed or deleted 111 lines changed or added

This html diff was produced by rfcdiff 1.48.