Delay Tolerant Networking WG K. Scott
Internet-Draft The MITRE Corporation
Intended status: Informational S. Farrell
Expires: May 18, 2012 Computer Science Department
November 15, 2011
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
Scott & Farrell Expires May 18, 2012 [Page 1]
Internet-Draft LTP IANA Registries November 2011
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Licklider Transmission Protocol . . . . . . . . . . . . . . . . 3
2.1. LTP Engine ID . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. LTP Client Service ID . . . . . . . . . . . . . . . . . . . 4
3. Compressed Bundle Header Encoding . . . . . . . . . . . . . . . 5
3.1. CBHE Node Numbers . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Scott & Farrell Expires May 18, 2012 [Page 2]
Internet-Draft LTP IANA Registries November 2011
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.
Scott & Farrell Expires May 18, 2012 [Page 3]
Internet-Draft LTP IANA Registries November 2011
(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.
Scott & Farrell Expires May 18, 2012 [Page 4]
Internet-Draft LTP IANA Registries November 2011
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.
Scott & Farrell Expires May 18, 2012 [Page 5]
Internet-Draft LTP IANA Registries November 2011
(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.
Scott & Farrell Expires May 18, 2012 [Page 6]
Internet-Draft LTP IANA Registries November 2011
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5326] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider
Transmission Protocol - Specification", RFC 5326,
September 2008.
[RFC6260] Burleigh, S., "Compressed Bundle Header Encoding (CBHE)",
RFC 6260, May 2011.
7.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 College
Dublin,
Ireland
Phone: +353-1-896-1761
Fax:
Email: stephen.farrell@cs.tcd.ie
URI:
Scott & Farrell Expires May 18, 2012 [Page 7]
