7116
INFORMATIONAL

Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries

Authors: K. Scott, M. Blanchet
Date: February 2014
Stream: IRTF
Updated by: RFC 9758
View on RFC Editor (HTML) Download PDF View Errata DOI

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.

RFC 7116
Download TXTDownload PDF
RFC 7116: Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries [RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page]

INFORMATIONAL
Updated by: 9758 Errata Exist
Internet Research Task Force (IRTF)                             K. Scott
Request for Comments: 7116                         The MITRE Corporation
Category: Informational                                      M. Blanchet
ISSN: 2070-1721                                                 Viagenie
                                                           February 2014


                 <span class="h1">Licklider Transmission Protocol (LTP),</span>
               <span class="h1">Compressed Bundle Header Encoding (CBHE),</span>
                  <span class="h1">and Bundle Protocol IANA Registries</span>

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, <a href="./rfc5050">RFC 5050</a> 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 <a href="./rfc5741">RFC</a>
   <a href="./rfc5741">5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc7116">http://www.rfc-editor.org/info/rfc7116</a>.










<span class="grey">Scott & Blanchet              Informational                     [Page 1]</span>
<span id="page-2" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


Copyright Notice

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

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.

Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. Security Considerations .........................................<a href="#page-3">3</a>
   <a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-3">3</a>
      <a href="#section-3.1">3.1</a>. Licklider Transmission Protocol ............................<a href="#page-3">3</a>
           <a href="#section-3.1.1">3.1.1</a>. LTP Cancel Segment Reason Codes .....................<a href="#page-3">3</a>
           <a href="#section-3.1.2">3.1.2</a>. LTP Engine ID .......................................<a href="#page-4">4</a>
           <a href="#section-3.1.3">3.1.3</a>. LTP Client Service ID ...............................<a href="#page-5">5</a>
      <a href="#section-3.2">3.2</a>. Compressed Bundle Header Encoding ..........................<a href="#page-6">6</a>
           <a href="#section-3.2.1">3.2.1</a>. CBHE Node Numbers ...................................<a href="#page-6">6</a>
           <a href="#section-3.2.2">3.2.2</a>. CBHE Service Numbers ................................<a href="#page-7">7</a>
      <a href="#section-3.3">3.3</a>. Bundle Administrative Record Types .........................<a href="#page-8">8</a>
   <a href="#section-4">4</a>. Acknowledgements ................................................<a href="#page-8">8</a>
   <a href="#section-5">5</a>. References ......................................................<a href="#page-9">9</a>
      <a href="#section-5.1">5.1</a>. Normative References .......................................<a href="#page-9">9</a>
      <a href="#section-5.2">5.2</a>. Informative References .....................................<a href="#page-9">9</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The DTNRG Research Group has defined the Licklider Transmission
   Protocol (LTP) [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>].  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
   <a href="./rfc5226#section-4.1">Section 4.1 of [RFC5226]</a>.

   The Compressed Bundle Header Encoding (CBHE) [<a href="./rfc6260" title=""Compressed Bundle Header Encoding (CBHE)"">RFC6260</a>] 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.





<span class="grey">Scott & Blanchet              Informational                     [Page 2]</span>
<span id="page-3" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


   Because of its association with space communication and the
   Consultative Committee for Space Data Systems [<a href="#ref-CCSDS" title=""The Consultative Committee for Space Data Systems"">CCSDS</a>], 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 [<a href="#ref-SANA" title=""The CCSDS SANA Registry page"">SANA</a>].  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.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Security Considerations</span>

   This document requests the creation of registries managed by IANA.
   There are no security issues involved.  Refer to the Security
   Considerations section of [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>] for security issues with LTP.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  IANA Considerations</span>

   IANA has created the registries described in this section.

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  Licklider Transmission Protocol</span>

   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.

<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>.  LTP Cancel Segment Reason Codes</span>

   <a href="./rfc5326#section-3.2.4">Section 3.2.4 of [RFC5326]</a> 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 registration policy for this registry is Specification Required.














<span class="grey">Scott & Blanchet              Informational                     [Page 3]</span>
<span id="page-4" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


   The initial values (as defined by <a href="./rfc5326">RFC 5326</a>) for the "LTP Cancel
   Segment Reason Codes" are:

      +-------+---------------------------------+---------------+
      | Value | Description                     | Reference     |
      +-------+---------------------------------+---------------+
      |   0   | Client service canceled session | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
      |   1   | Unreachable client service      | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
      |   2   | Retransmission limit exceeded   | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
      |   3   | Miscolored data received        | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
      |   4   | System error caused termination | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
      |   5   | Retransmission limit exceeded   | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
      | 6-255 | Unassigned                      | This document |
      +-------+---------------------------------+---------------+

<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>.  LTP Engine ID</span>

   The Licklider Transmission Protocol has an LTP Engine ID field
   (<a href="./rfc5326#section-2">Section 2 of [RFC5326]</a>).  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.

   The registration policy for this registry is:

   1 -- (2**14)-1  Expert Review required.

   (2**14) -- (2**21)-1  Allocated to the Space Assigned Numbers
      Authority ([<a href="#ref-SANA" title=""The CCSDS SANA Registry page"">SANA</a>]) for use by Consultative Committee for Space
      Data Systems (CCSDS) missions.

   (2**21) -- (2**28)-1  Private or Experimental Use.

   (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.














<span class="grey">Scott & Blanchet              Informational                     [Page 4]</span>
<span id="page-5" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


   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 <a href="#section-4.1">Section 4.1</a> of the Bundle
   Protocol specification [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] and in [<a href="./rfc6256" title=""Using Self-Delimiting Numeric Values in Protocols"">RFC6256</a>].  The initial
   values for the "LTP Engine Numbers" registry are:

    +--------------------+---------------------------+---------------+
    |              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 |
    +--------------------+---------------------------+---------------+

<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>.  LTP Client Service ID</span>

   The Licklider Transmission Protocol has a client service ID number
   field (<a href="./rfc5326#section-3.2.1">Section 3.2.1 of [RFC5326]</a>).  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 registration policy for this registry is:

   4 -- (2**14)-1  Allocated to the Space Assigned Numbers Authority
      ([<a href="#ref-SANA" title=""The CCSDS SANA Registry page"">SANA</a>]) for use by Consultative Committee for Space Data Systems
      (CCSDS) missions.

   2**14 -- 32,767  Private or Experimental Use.

   >= 32,768  Specification Required.

















<span class="grey">Scott & Blanchet              Informational                     [Page 5]</span>
<span id="page-6" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


   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:

    +-----------------+------------------------------+---------------+
    |           Value | Description                  | Reference     |
    +-----------------+------------------------------+---------------+
    |               0 | Reserved                     | [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]     |
    |               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 |
    +-----------------+------------------------------+---------------+

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Compressed Bundle Header Encoding</span>

   The CBHE specification [<a href="./rfc6260" title=""Compressed Bundle Header Encoding (CBHE)"">RFC6260</a>] defines concepts of 'Node Number'
   and 'Service Number' that require registries managed by IANA.

<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>.  CBHE Node Numbers</span>

   The CBHE specification defines a Node Number (node-nbr) field
   (<a href="./rfc6260#section-2.1">Section 2.1 of [RFC6260]</a>).  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.

   The registration policy for this registry is:

   1 -- (2**14)-1  Expert Review required.

   (2**14) -- (2**21)-1  Allocated to the Space Assigned Numbers
      Authority ([<a href="#ref-SANA" title=""The CCSDS SANA Registry page"">SANA</a>]) for use by Consultative Committee for Space
      Data Systems (CCSDS) missions.

   (2**21) -- (2**28)-1  Private or Experimental Use.

   (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.





<span class="grey">Scott & Blanchet              Informational                     [Page 6]</span>
<span id="page-7" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


   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:

    +--------------------+---------------------------+---------------+
    |              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 |
    +--------------------+---------------------------+---------------+

<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>.  CBHE Service Numbers</span>

   The Compressed Bundle Header Encoding specification defines a Service
   Number (service-nbr) field (<a href="./rfc6260#section-2.1">Section 2.1 of [RFC6260]</a>).  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 ([<a href="#ref-SANA" title=""The CCSDS SANA Registry page"">SANA</a>])
      for use by Consultative Committee for Space Data Systems (CCSDS)
      missions.

   1024 - 2**16-1  Specification Required.

   >= 2**16  Private/Experimental Use.
















<span class="grey">Scott & Blanchet              Informational                     [Page 7]</span>
<span id="page-8" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


   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:

   +----------------+--------------------------------+---------------+
   |          Value | Description                    | Reference     |
   +----------------+--------------------------------+---------------+
   |              0 | Bundle Protocol Administrative | [<a href="./rfc6260" title=""Compressed Bundle Header Encoding (CBHE)"">RFC6260</a>]     |
   |                |   Record                       |               |
   |              1 | CCSDS File Delivery Service    | [<a href="#ref-CFDP" title=""CCSDS File Delivery Protocol Version 4 (CCSDS 727.0-B-4)"">CFDP</a>]        |
   |              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 |
   +----------------+--------------------------------+---------------+

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  Bundle Administrative Record Types</span>

   <a href="#section-6.1">Section 6.1</a> of the Bundle Protocol specification [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] 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:

           +-------+----------------------+---------------+
           | Value | Description          | Reference     |
           +-------+----------------------+---------------+
           |     0 | Reserved             | This document |
           |     1 | Bundle status report | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>]     |
           |     2 | Custody signal       | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>]     |
           |  3-15 | Unassigned           | This document |
           +-------+----------------------+---------------+

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Acknowledgements</span>

   The authors would like to thank the following people, in no specific
   order: Scott Burleigh, Stephen Farrell, and John Buford.







<span class="grey">Scott & Blanchet              Informational                     [Page 8]</span>
<span id="page-9" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  References</span>

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  Normative References</span>

   [<a id="ref-CFDP">CFDP</a>]     Consultative Committee for Space Data Systems, "CCSDS File
              Delivery Protocol Version 4 (CCSDS 727.0-B-4)",
              January 2007, <<a href="http://www.ccsds.org">http://www.ccsds.org</a>>.

   [<a id="ref-RFC5050">RFC5050</a>]  Scott, K. and S. Burleigh, "Bundle Protocol
              Specification", <a href="./rfc5050">RFC 5050</a>, November 2007.

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              May 2008.

   [<a id="ref-RFC5326">RFC5326</a>]  Ramadas, M., Burleigh, S., and S. Farrell, "Licklider
              Transmission Protocol - Specification", <a href="./rfc5326">RFC 5326</a>,
              September 2008.

   [<a id="ref-RFC6256">RFC6256</a>]  Eddy, W. and E. Davies, "Using Self-Delimiting Numeric
              Values in Protocols", <a href="./rfc6256">RFC 6256</a>, May 2011.

   [<a id="ref-RFC6260">RFC6260</a>]  Burleigh, S., "Compressed Bundle Header Encoding (CBHE)",
              <a href="./rfc6260">RFC 6260</a>, May 2011.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  Informative References</span>

   [<a id="ref-CCSDS">CCSDS</a>]    CCSDS, "The Consultative Committee for Space Data
              Systems", <<a href="http://www.ccsds.org">http://www.ccsds.org</a>>.

   [<a id="ref-SANA">SANA</a>]     SANA, "The CCSDS SANA Registry page",
              <<a href="http://sanaregistry.org">http://sanaregistry.org</a>>.



















<span class="grey">Scott & Blanchet              Informational                     [Page 9]</span>
<span id="page-10" ></span>
<span class="grey"><a href="./rfc7116">RFC 7116</a>            LTP, CBHE, and BP IANA Registries      February 2014</span>


Authors' Addresses

   Keith Scott
   The MITRE Corporation
   7515 Colshire Drive
   McLean, VA  22102
   USA

   Phone: +1-703-983-6547
   Fax:   +1-703-983-7142
   EMail: [email protected]


   Marc Blanchet
   Viagenie
   246 Aberdeen
   Quebec  G1R 2E1
   Canada

   Phone: +1-418-656-9254
   EMail: [email protected]






























Scott & Blanchet              Informational                    [Page 10]

Additional Resources