Licklider Transmission
Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle
Protocol IANA Registries
The MITRE Corporation
7515 Colshire Drive
McLean, VA
22102
California
USA
+1-703-983-6547
+1-703-983-7142
kscott@mitre.org
Viagenie
246 Aberdeen
Québec
Québec
G1R 2E1
Canada
+1-418-656-9254
marc.blanchet@viagenie.ca
Internet Research Task Force (IRTF)
Licklider Transmission Protocol
LTP
CBHE
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, RFC5050 defines values for the Bundle 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 actions needed to
be executed by IANA.
The DTNRG research group has defined the Licklider Transmission
Protocol (LTP). 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 needed to be executed by IANA using the Well-Known
IANA Policy Definitions defined in Section 4.1 of .
The Compressed Bundle Header Encoding (CBHE)
specification defines the concepts of Node Number and Service Number in
the 'ipn' URI scheme. In this document we request formation of an IANA
registry for the Node Number field in the 'ipn' scheme.
Because of its association with space communication and the
Consultative Committee on Space Data Systems , a
portion of the CBHE Node Number space and a corresponding portion of the
LTP Engine ID space is delegated by this document to the CCSDS Space
Assigned Numbers Authority . 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 requests the creation of registries managed by IANA.
There are no security issues involved. Refer to the Security
Considerations section of for security issues
with the LTP protocol.
IANA is requested to create registries as described in this
section.
The Licklider Transmission Protocol has fields requiring registries
managed by IANA. This document requests the creation of the three
registries in this section and that they be associated with the other
registries for the Licklider Transmission protocol.
Section 3.2.4 of defines the reason
codes that may be present in Cancel Segments in the LTP
protocol.
The registration policy for this registry is: Specification
Required
The initial values (as defined by RFC5326) for the LTP Cancel
Segment Reason Codes registry shall be:
LTP Cancel Segment Reason Codes Registry
Value
Description
Reference
0
Client service canceled session
1
Unreachable client service
2
Retransmission limit exceeded
3
Miscolored data received
4
System error caused termination
5
Retransmission limit exceeded
0x06-0xFF
Unassigned
This document
The Licklider Transmission Protocol has an LTP Engine ID field
(section 2 of ). An IANA registry shall be
set up as follows.
The registration policy for this registry is:
Expert review required.
Allocated to the Space
Assigned Numbers Authority () for use by
Consultative Committee for Space Data Systems (CCSDS)
missions.
Private or experimental
use.
First-come, First-Served
basis for requests for less than or equal to 2**14 values to a
single entity or organization. Expert review for requests of
more than 2**14 values to a single entity or organization.
The LTP Engine ID is expressed as a Self-Delimiting Numeric Value
(SDNV) in the LTP protocol and no maximum is specified in the
protocol definition. SDNVs are described in Section 4.1 of the
Bundle Protocol in and are also described
in the stand-alone document . The initial
values for the LTP Engine Numbers registry shall be:
LTP Engine Numbers Registry
Value
Description
Reference
0
Reserved
This document
1--(2**14)-1
Unassigned
This document
(2**14)--(2**21)-1
Allocated to CCSDS (SANA)
This document
(2**21)--(2**28)-1
Private/Experimental Use
This document
(2**28)--(2**42)-1
Unassigned
This document
>=(2**42)
Reserved
This document
The Licklider Transmission Protocol has a client service ID
number field (section 3.2.1 of ). An IANA
registry shall be set up as follows.
The registration policy for this registry is:
Allocated to the Space Assigned
Numbers Authority () for use by
Consultative Committee for Space Data Systems (CCSDS)
missions.
Private or experimental use.
Specification required.
The LTP Client Service ID is expressed as a Self-Delimiting
Numeric Value (SDNV) in the LTP protocol and no maximum value is
specified in the protocol definition. The initial values for the LTP
Client Service Identifiers registry shall be:
LTP Client Service Identifiers Registry
Value
Description
Reference
0
Reserved
1
Bundle Protocol
This document
2
LTP Service Data Aggregation
This document
3
CCSDS File Delivery Service
This document
4--(2**14)-1
Allocated to CCSDS (SANA)
This document
(2**14)--32,767
Private / Experimental Use
This document
>=32,768
Unassigned
This document
The CBHE specification defines concepts of
'Node Number' and 'Service Number' that require registries managed by
IANA.
The CBHE specification defines a Node Number (node-nbr) field
(section 2.1 of ). An IANA registry shall be
set up as follows.
The registration policy for this registry is:
Expert review required.
Allocated to the Space
Assigned Numbers Authority () for use by
Consultative Committee for Space Data Systems (CCSDS)
missions.
Private or experimental
use.
First-come, First-Served
basis for requests for less than or equal to 2**14 values to a
single entity or organization. Expert review required for
requests of more than 2**14 values to a single entity or
organization.
Reserved
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:
CBHE Node Number Registry
Value
Description
Reference
0
Reserved
This document
1--(2**14)-1
Unassigned
This document
(2**14)--(2**21)-1
Allocated to CCSDS (SANA)
This document
(2**21)--(2**28)-1
Private/Experimental Use
This document
(2**28)--(2**42)-1
Unassigned
This document
>=(2**42)
Reserved
This document
The Compressed Bundle Header Encoding specification defines a
Service Number (service-nbr) field (section 2.1 of ). An IANA registry shall be set up as
follows.
The registration policy for this registry is:
RFC Required
Allocated to the Space Assigned Numbers
Authority () for use by Consultative
Committee for Space Data Systems (CCSDS) missions.
Specification Required
Private / Experimental Use
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 shall be:
CBHE Service Number Registry
Value
Description
Reference
0
Bundle Protocol Administrative Record
1
CCSDS File Delivery Service
2
Reserved
This document
3-63
Unassigned
This document
64-1023
Allocated to CCSDS (SANA)
This document
1024 - 2**16-1
Unassigned
This document
>=2**16
Private/Experimental Use
This document
Section 6.1 of the Bundle Protocol specification specifies a 4-bit Administrative Record type
code. An IANA registry shall be set up as follows to manage these
record types. This registry, titled 'Bundle Administrative Record
Type,' shall be added to the list of registries associated with the
Bundle Protcol.
The registration policy for this registry is: Specification
required
The initial values for the Bundle Administrative Record Type
registry shall be:
Bundle Protocol Administrative Record Type
Registry
Value
Description
Reference
0
Reserved
This document
1
Bundle status report
2
Custody signal
3-15
Unassigned
This document
The editors would like to thank the following people, in no specific
order: Scott Burleigh, Stephen Farrell, John Buford.
CCSDS File Delivery Protocol Version 4 (CCSDS
727.0-B-4)
Consultative Committee for Space Data Systems
(http://www.ccsds.org)
The Consultative Committee for Space Data Systems at
http://www.ccsds.org
The CCSDS SANA Registry page at
http://sanaregistry.org