Licklider Transmission Protocol (LTP) and Compressed Bundle Header Encoding (CBHE) IANA Registries
draft-dtnrg-ltp-cbhe-registries-00

Abstract

The DTNRG research group has defined the experimental Licklider Transmission Protocol (LTP) [RFC5326] and the Compressed Bundle Header Encoding (CBHE) [RFC6260] mechanism for the 'ipn' URI scheme. Both documents describe 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 custody. This document describes the actions needed to be executed by IANA.

Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

Status of this Memo

This Internet-Draft is submitted in full conformance with the 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 http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on May 18, 2012.

Copyright Notice

Copyright (c) 2011 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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Licklider Transmission Protocol
• 2.1. LTP Engine ID
• 2.2. LTP Client Service ID
• 3. Compressed Bundle Header Encoding
• 3.1. CBHE Node Numbers
• 4. Security Considerations
• 5. IANA Considerations
• 6. Acknowledgements
• 7. References
• 7.1. Normative References
• 7.2. Informative References
• Authors' Addresses

1. Introduction

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 custody. This document describes the actions needed to be executed by IANA.

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 an IANA registry for the Node Number field in the 'ipn' scheme. There is a separate Internet Draft that will (if approved) establish a registry for the service-nbr portion and relate entries there to a corresponding registry for the 'dtn' URI scheme.

Because of its association with space communication and the Consultative Committee on Space Data Systems [CCSDS], a portion of the CBHE Node Number space and a portion of the LTP Engine ID space is 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.

2. Licklider Transmission Protocol

The Licklider Transmission Protocol has fields requiring registries managed by IANA.

2.1. LTP Engine ID

The Licklider Transmission Protocol has an LTP Engine ID field (section 2 of [RFC5326]). An IANA registry shall be set up as follows.

The registration policy for this registry is:

0

Reserved

1 -- (2**14)-1

Expert review required. The designated experts for the review are the chairs of the IRTF DTN Research Group (dtnrg) if the dtnrg is extant, or as determined by the IRSG.

(2**14) -- (2**21)-1

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

(2**21) -- (2**27)-1

Private or experimental use. No assignment by IANA.

(2**27) -- (2**42)-1

First-come, First-Served for requests for less than or equal to 2**14 values. Expert review for requests of more than 2**14 values. The designated experts for the review are the chairs of the IRTF DTN Research Group (dtnrg) if the dtnrg is extant, or as determined by the IRSG.

>= (2**42)

Reserved

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.

Initial values for the LTP Engine Numbers Registry:

    +--------------------+----------------------------+---------------+
    |        Value       | Description                | Reference     |
    +--------------------+----------------------------+---------------+
    |                  0 | Reserved                   | This document |
    |       1--(2**14)-1 | Unassigned                 | This document |
    | (2**14)--(2**21)-1 | Managed by CCSDS SANA      | This document |
    | (2**21)--(2**27)-1 | Private/Experimental Use   | This document |
    | (2**27)--(2**42)-1 | Unassigned                 | This document |
    |          >=(2**42) | Reserved                   | This document |
    +--------------------+----------------------------+---------------+

2.2. LTP Client Service ID

The Licklider Transmission Protocol has a client service ID number field (section 3.2.1 of [RFC5326]). An IANA registry shall be set up as follows.

The registration policy for this registry is:

0

Reserved

1 -- 127

Expert review required. The designated experts for the review are the chairs of the IRTF DTN Research Group (dtnrg) if the dtnrg is extant, or as determined by the IRSG.

128 -- 255

Private or experimental use. No assignment by IANA.

>= 256

Expert review required. The designated experts for the review are the chairs of the IRTF DTN Research Group (dtnrg) if the dtnrg is extant, or as determined by the IRSG.

The LTP Engine ID is expressed as a Self-Delimiting Numeric Value (SDNV) in the LTP protocol and no maximum value is specified in the protocol definition.

LTP Client Service Identifiers Registry:

    +---------------+---------------------------------+---------------+
    |        Value  | Description                     | Reference     |
    +---------------+---------------------------------+---------------+
    |             0 | Reserved                        | [RFC5326]     |
    |             1 | Bundle Protocol                 | This document |
    |        2--127 | Unassigned                      | This document |
    |      128--255 | Private / Experimental User     | This document |
    |         >=256 | Unassigned                      | This document |
    +---------------+---------------------------------+---------------+

3. Compressed Bundle Header Encoding

The Compressed Bundle Header Encoding specification defines concepts of Node Number' and 'Service Number' that require registries managed by IANA. This document addresses the 'Node Number' registry; a separate document addresses the formation and management of the 'Service Number' registry.

3.1. CBHE Node Numbers

The Compressed Bundle Header Enoding specification defnes a Node Number (node-nbr) field (section 2.1 of [RFC6260]). An IANA registry shall be set up as follows.

The registration policy for this registry is:

0

Reserved

1 -- (2**14)-1

Expert review required. The designated experts for the review are the chairs of the IRTF DTN Research Group (dtnrg) if the dtnrg is extant, or as determined by the IRSG.

(2**14) -- (2**21)-1

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

(2**21) -- (2**27)-1

Private or experimental use. No assignment by IANA.

(2**27) -- (2**42)-1

First-come, First-Served for requests for less than or equal to 2**14 values. Expert review for requests of more than 2**14 values. The designated experts for the review are the chairs of the IRTF DTN Research Group (dtnrg) if the dtnrg is extant, or as determined by the IRSG.

>= (2**42)

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.

Initial values for the CBHE Node Number Registry:

    +--------------------+----------------------------+---------------+
    |        Value       | Description                | Reference     |
    +--------------------+----------------------------+---------------+
    |                  0 | Reserved                   | This document |
    |       1--(2**14)-1 | Unassigned                 | This document |
    | (2**14)--(2**21)-1 | Managed by CCSDS SANA      | This document |
    | (2**21)--(2**27)-1 | Private/Experimental Use   | This document |
    | (2**27)--(2**42)-1 | Unassigned                 | This document |
    |          >=(2**42) | Reserved                   | This document |
    +--------------------+----------------------------+---------------+

4. Security Considerations

This document requests the creation of registries managed by IANA. Thera are no security issues involved. Refer to the Security Considerations section of [RFC5326] for security issues with the LTP protocol.

5. IANA Considerations

IANA is requested to create the registries as described in Sections 2 and 3.

6. Acknowledgements

The editor would like to thank the following people, in no specific order: Marc Blanchet, Scott Burleigh.

7. References

7.1. Normative References

7.2. Informative References

Authors' Addresses