Abstract

The DTNRG Research Group has defined the experimental Licklider Transmission Protocol (LTP) and the Compressed Bundle Header Encoding (CBHE) mechanism for the InterPlanetary Network ('ipn' URI scheme). Moreover, RFC 5050 defines values for the Bundle Protocol administrative record type. All of these fields are subject to a registry. For the purpose of its research work, the group has created ad hoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to hand off the registries to IANA for official management. This document describes the necessary IANA actions.

Status of This Memo

This document is not an Internet Standards Track specification; it is published for informational purposes.

This document is a product of the Internet Research Task Force (IRTF). The IRTF publishes the results of Internet-related research and development activities. These results might not be suitable for deployment. This RFC represents the consensus of the Delay-Tolerant Networking (DTNRG) Research Group of the Internet Research Task Force (IRTF). Documents approved for publication by the IRSG are not a candidate for any level of Internet Standard; see Section 2 of RFC5741.

Copyright Notice

Copyright (c) 2014 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 (http://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.

The DTNRG Research Group has defined the Licklider Transmission Protocol (LTP) [RFC5326]. LTP contains certain fields that are subject to a registry. For the purpose of its research work, the group has created ad hoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to hand off the registries to IANA for official management. This document describes the actions that IANA needs to take and uses the well-known IANA policy definitions as described in Section 4.1 of [RFC5226].

The Compressed Bundle Header Encoding (CBHE) [RFC6260] specification defines the concepts of 'Node Number' and 'Service Number' in the 'ipn' URI scheme. In this document, we request formation of IANA registries for these fields.

Scott & Blanchet Informational [Page 2]

RFC 7116 LTP, CBHE, and BP IANA Registries February 2014

Because of its association with space communication and the Consultative Committee for Space Data Systems [CCSDS], portions of the "CBHE Node Numbers", "CBHE Service Numbers", and "LTP Engine Numbers" spaces are delegated by this document to the CCSDS Space Assigned Numbers Authority [SANA]. SANA functions similarly to IANA in that it maintains registries of managed values, with a focus on values used by protocols used by CCSDS member agencies.

This document represents the consensus of the DTNRG. It has been discussed and reviewed by the research group and interested parties.

The Licklider Transmission Protocol has fields requiring registries managed by IANA. This document requests the creation of the three registries in this section and requests that they be associated with the other LTP registries.

Section 3.2.4 of [RFC5326] defines the reason codes that may be present in Cancel Segments in LTP. IANA has set up a registry to manage the cancel reason codes. This registry, titled "LTP Cancel Segment Reason Codes", has been added to the list of registries associated with the Licklider Transmission Protocol.

The Licklider Transmission Protocol has an LTP Engine ID field (Section 2 of [RFC5326]). IANA has set up a registry to manage the Engine IDs. This registry, titled "LTP Engine Numbers", has been added to the list of registries associated with the Licklider Transmission Protocol.

(2**28) -- (2**42)-1 First Come First Served basis for requests for less than or equal to 2**14 values to a single entity or organization. Expert Review is required for requests of more than 2**14 values to a single entity or organization.

Scott & Blanchet Informational [Page 4]

RFC 7116 LTP, CBHE, and BP IANA Registries February 2014

The LTP Engine ID is expressed as a Self-Delimiting Numeric Value (SDNV) in LTP, and no maximum is specified in the protocol definition. SDNVs are described in Section 4.1 of the Bundle Protocol specification [RFC5050] and in [RFC6256]. The initial values for the "LTP Engine Numbers" registry are:

The Licklider Transmission Protocol has a client service ID number field (Section 3.2.1 of [RFC5326]). IANA has set up a registry to manage LTP Client Service IDs. This registry, titled "LTP Client Service Identifiers", has been added to the list of registries associated with the Licklider Transmission Protocol.

The LTP Client Service ID is expressed as a Self-Delimiting Numeric Value (SDNV) in LTP, and no maximum value is specified in the protocol definition. The initial values for the "LTP Client Service Identifiers" are:

The CBHE specification defines a Node Number (node-nbr) field (Section 2.1 of [RFC6260]). IANA has set up a registry to manage CBHE Node Numbers. This registry, titled "CBHE Node Numbers", has been added to the list of registries associated with the Bundle Protocol.

(2**28) -- (2**42)-1 First Come First Served basis for requests for less than or equal to 2**14 values to a single entity or organization. Expert Review is required for requests of more than 2**14 values to a single entity or organization.

>= (2**42) Reserved.

Scott & Blanchet Informational [Page 6]

RFC 7116 LTP, CBHE, and BP IANA Registries February 2014

The CBHE Node Number is expressed as a Self-Delimiting Numeric Value (SDNV) in the CBHE specification. Allowable values for the Node Number range from 1 -- (2**64)-1. The initial values for the "CBHE Node Number" registry shall be:

The Compressed Bundle Header Encoding specification defines a Service Number (service-nbr) field (Section 2.1 of [RFC6260]). IANA has set up a registry to manage CBHE Service Numbers. This registry, titled "CBHE Service Numbers", has been added to the list of registries associated with the Bundle Protocol.

The registration policy for this registry is:

0-63 Specification Required.

64-1023 Allocated to the Space Assigned Numbers Authority ([SANA]) for use by Consultative Committee for Space Data Systems (CCSDS) missions.

The CBHE Service Number is expressed as a Self-Delimiting Numeric Value (SDNV) in the CBHE specification. Allowable values for the Service Number range from 1 -- (2**64)-1. The initial values for the "CBHE Service Number" registry are:

Section 6.1 of the Bundle Protocol specification [RFC5050] specifies a 4-bit Administrative Record type code. IANA has set up a registry to manage these record types. This registry, titled "Bundle Administrative Record Types", has been added to the list of registries associated with the Bundle Protocol.

The registration policy for this registry is Specification Required.

The initial values for the "Bundle Administrative Record Type" registry are: