Delay Tolerant Networking WG K. Scott
Internet-Draft The MITRE Corporation
Intended status: Informational S. Farrell
Expires: August 27, 2012 Computer Science Department,
Trinity Collegeex
February 24, 2012
Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding
(CBHE), and Bundle Protocol IANA Registries
draft-dtnrg-ltp-cbhe-registries-02
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.
Finally, RFC5050 [RFC5050] defines values for the Bundle
Administrative Record Type. All of these 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 August 27, 2012.
Scott & Farrell Expires August 27, 2012 [Page 1]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
Copyright Notice
Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Licklider Transmission Protocol . . . . . . . . . . . . . . . 3
2.1. LTP Cancel Segment Reason Codes . . . . . . . . . . . . . 3
2.2. LTP Engine ID . . . . . . . . . . . . . . . . . . . . . . 4
2.3. LTP Client Service ID . . . . . . . . . . . . . . . . . . 5
3. Compressed Bundle Header Encoding . . . . . . . . . . . . . . 6
3.1. CBHE Node Numbers . . . . . . . . . . . . . . . . . . . . 6
3.2. CBHE Service Numbers . . . . . . . . . . . . . . . . . . . 7
4. Bundle Administrative Record Types . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
Scott & Farrell Expires August 27, 2012 [Page 2]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
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
[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 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. 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.
2.1. LTP Cancel Segment Reason Codes
Section 3.2.4 of [RFC5326] defines the reason codes that may be
present in Cancel Segments in the LTP protocol.
The registration policy for this registry is:
0x00--0x05 As defined by RFC5326 and shown in in Table 2-1 below.
0x06 -- 0xFF Allocatable by IANA; RFC Required
The initial values for the LTP Cancel Segment Reason Codes registry
shall be:
Scott & Farrell Expires August 27, 2012 [Page 3]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
Table 2-1: Initial values for the LTP Cancel Segment Reason Codes
Registry:
+-----------+-------------------------------------+---------------+
| Value | Description | Reference |
+-----------+-------------------------------------+---------------+
| 0 | Client service canceled session | RFC5326 |
| 1 | Unreachable client service | RFC5326 |
| 2 | Retransmission limit exceeded. | RFC5326 |
| 3 | Miscolored data received | RFC5326 |
| 4 | System error caused termination | RFC5326 |
| 5 | Retransmission limit exceeded. | RFC5326 |
| 0x06-0xFF | Allocatable by IANA. | This document |
+--------------------+----------------------------+---------------+
2.2. 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; no allocation by IANA
1 -- (2**14)-1 Allocatable by IANA; 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 Allocatable by IANA on a First-come, First-
Served basis 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. SDNVs were first described in relation to the
Scott & Farrell Expires August 27, 2012 [Page 4]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
Bundle Protocol in Section 4.1 of [RFC5050] and are also described in
the stand-alone document [RFC6256]. The initial values for the LTP
Engine Numbers registry shall be:
Table 2-2: 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 | Administered by CCSDS SANA | This document |
| (2**21)--(2**27)-1 | Private/Experimental Use | This document |
| (2**27)--(2**42)-1 | Allocatable by IANA | This document |
| >=(2**42) | Reserved | This document |
+--------------------+----------------------------+---------------+
2.3. 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 -- 3 Initial registry values as shown in table 2-3 below.
4 -- (2**14)-1 Administered by CCSDS SANA
2**14 -- 32,767 Private or experimental use; no assignment by IANA.
>= 32,768 Allocatable by IANA. 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 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:
Scott & Farrell Expires August 27, 2012 [Page 5]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
Table 2-3: LTP Client Service Identifiers Registry:
+----------------+---------------------------------+---------------+
| Value | Description | Reference |
+----------------+---------------------------------+---------------+
| 0 | Reserved | [RFC5326] |
| 1 | Bundle Protocol | This document |
| 2 | LTP Service Data Aggregation | This document |
| 3 | CCSDS File Delivery Service | This document |
| 4--(2**14)-1 | Administered by CCSDS SANA | This document |
|(2**14)--32,767 | Private / Experimental Use | This document |
| >=32,768 | Unassigned (assignable by IANA) | 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 Allocatable by IANA on a First-come, First-
Served basis 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
Scott & Farrell Expires August 27, 2012 [Page 6]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
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. The initial values for the CBHE
Node Number registry shall be:
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 | Allocatable by IANA | This document |
| >=(2**42) | Reserved | This document |
+--------------------+----------------------------+---------------+
3.2. CBHE Service Numbers
The Compressed Bundle Header Enoding specification defnes a Service
Number (service-nbr) field (section 2.1 of [RFC6260]). An IANA
registry shall be set up as follows.
The registration policy for this registry is:
0 -- 4 Initial values defined in table 3-1 below.
5 -- 127 Administered by CCSDS SANA
128 -- 2**16-1 Allocatable by IANA -- document required.
>= 2**16 Private / Experimental Use
The CBHE Service 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:
Scott & Farrell Expires August 27, 2012 [Page 7]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
Table 3-1: Initial values for the CBHE Node Number Registry:
+--------------------+----------------------------+----------------+
| Value | Description | Reference |
+--------------------+----------------------------+----------------+
| 0 | Bundle Protocol | RFC6260 |
| | Administrative Record | |
| 1 | Echo Service | This document |
| 2 | Discard Service | This document |
| 3 | Console Service | This document |
| 4 | CCSDS File Delivery Service| [CFDP] |
| 5--127 | Administered by CCSDS SANA | This document |
| 128 -- 2**16-1 | Allocatable by IANA | This document |
| >=2**16 | Private/Experimental Use | This document |
+--------------------+----------------------------+----------------+
4. Bundle Administrative Record Types
Section 6.1 of the Bundle Protocol specification[RFC5050] specifies a
4-bit Administrative Record type code. An IANA registry shall be set
up as follows to manage these record types. This document requests
the addition of an additional registry titled 'Bundle Administrative
Record Type' be added to the list of registries associated with the
Bundle Protcol.
The registration policy for this registry is:
0 Reserved
1--2 Defined by RFC5050 as shown in table 4-1 below.
3-15 RFC required
The initial values for the Bundle Administrative Record Type registry
shall be:
Table 4-1: Initial values for the Bundle Protocol Administrative
Record Type Registry:
+--------------------+----------------------------+---------------+
| Value | Description | Reference |
+--------------------+----------------------------+---------------+
| 0 | Reserved | This document |
| 1 | Bundle status report | RFC5050 |
| 2 | Custody signal | RFC5050 |
| 3--15 | Allocatable by IANA | RFC5050 |
+--------------------+----------------------------+---------------+
Scott & Farrell Expires August 27, 2012 [Page 8]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
5. 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.
6. IANA Considerations
IANA is requested to create the registries as described in Sections 2
and 3.
7. Acknowledgements
The editor would like to thank the following people, in no specific
order: Marc Blanchet, Scott Burleigh.
8. References
8.1. Normative References
[CFDP] Consultative Committee for Space Data Systems
(http://www.ccsds.org), "CCSDS File Delivery Protocol
Version 4 (CCSDS 727.0-B-4)", January 2007.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol
Specification", RFC 5050, November 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5326] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider
Transmission Protocol - Specification", RFC 5326,
September 2008.
[RFC6256] Eddy, W. and E. Davies, "Using Self-Delimiting Numeric
Values in Protocols", RFC 6256, May 2011.
[RFC6260] Burleigh, S., "Compressed Bundle Header Encoding (CBHE)",
RFC 6260, May 2011.
Scott & Farrell Expires August 27, 2012 [Page 9]
Internet-Draft LTP, CBHE, and BP IANA Registries February 2012
8.2. Informative References
[CCSDS] "The Consultative Committee for Space Data Systems,
http://www.ccsds.org".
[SANA] "The CCSDS SANA Registry page at http://sanaregistry.org".
Authors' Addresses
Keith Scott
The MITRE Corporation
7515 Colshire Drive
McLean, VA, California 22102
USA
Phone: +1-703-983-6547
Fax: ++1-703-983-7142
Email: kscott@mitre.org
Stephen Farrell
Computer Science Department, Trinity Collegeex
Trinity College
Dublin,
Ireland
Phone: +353-1-896-1761
Fax:
Email: stephen.farrell@cs.tcd.ie
URI:
Scott & Farrell Expires August 27, 2012 [Page 10]