Internet DRAFT - draft-dtnrg-ltp-cbhe-registries
draft-dtnrg-ltp-cbhe-registries
Network Working Group K. Scott
Internet-Draft The MITRE Corporation
Intended status: Informational M. Blanchet
Expires: April 11, 2014 Viagenie
October 8, 2013
Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding
(CBHE), and Bundle Protocol IANA Registries
draft-dtnrg-ltp-cbhe-registries-07
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 InterPlanetary
Network (ipn URI scheme). Moreover, RFC5050 [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.
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 April 11, 2014.
Copyright Notice
Copyright (c) 2013 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
Scott & Blanchet Expires April 11, 2014 [Page 1]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
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. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Licklider Transmission Protocol . . . . . . . . . . . . . . 3
3.1.1. LTP Cancel Segment Reason Codes . . . . . . . . . . . . 4
3.1.2. LTP Engine ID . . . . . . . . . . . . . . . . . . . . . 4
3.1.3. LTP Client Service ID . . . . . . . . . . . . . . . . . 5
3.2. Compressed Bundle Header Encoding . . . . . . . . . . . . . 6
3.2.1. CBHE Node Numbers . . . . . . . . . . . . . . . . . . . 6
3.2.2. CBHE Service Numbers . . . . . . . . . . . . . . . . . 7
3.3. Bundle Administrative Record Types . . . . . . . . . . . . 8
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. Normative References . . . . . . . . . . . . . . . . . . . 9
5.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
Scott & Blanchet Expires April 11, 2014 [Page 2]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
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
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 [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.
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 corresponding 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. Security Considerations
This document requests the creation of registries managed by IANA.
There are no security issues involved. Refer to the Security
Considerations section of [RFC5326] for security issues with the LTP
protocol.
3. IANA Considerations
IANA is requested to create registries as described in this section.
3.1. 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.
Scott & Blanchet Expires April 11, 2014 [Page 3]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
3.1.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: 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 | [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 | Unassigned | This document |
+-----------+---------------------------------+---------------+
3.1.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:
1 -- (2**14)-1 Expert review required.
(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**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 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
Scott & Blanchet Expires April 11, 2014 [Page 4]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
Bundle Protocol in [RFC5050] and are also described in the stand-
alone document [RFC6256]. 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 |
+--------------------+---------------------------+---------------+
3.1.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:
4 -- (2**14)-1 Allocated to the Space Assigned Numbers Authority
([SANA]) for use by Consultative Committee for Space Data Systems
(CCSDS) missions.
2**14 -- 32,767 Private or experimental use.
>= 32,768 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:
Scott & Blanchet Expires April 11, 2014 [Page 5]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
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 | Allocated to CCSDS (SANA) | This document |
| (2**14)--32,767 | Private / Experimental Use | This document |
| >=32,768 | Unassigned | This document |
+-----------------+------------------------------+---------------+
3.2. Compressed Bundle Header Encoding
The CBHE specification [RFC6260] defines concepts of 'Node Number'
and 'Service Number' that require registries managed by IANA.
3.2.1. CBHE Node Numbers
The CBHE specification defines 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:
1 -- (2**14)-1 Expert review required.
(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**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 required for requests of more than
2**14 values to a single entity or organization.
>= (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:
Scott & Blanchet Expires April 11, 2014 [Page 6]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
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 |
+--------------------+---------------------------+---------------+
3.2.2. CBHE Service Numbers
The Compressed Bundle Header Encoding specification defines 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-63 RFC Required
64-1023 Allocated to the Space Assigned Numbers Authority ([SANA])
for use by Consultative Committee for Space Data Systems (CCSDS)
missions.
1024 - 2**16-1 Specification 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
Service Number range from 1 -- (2**64)-1. The initial values for the
CBHE Service Number registry shall be:
Scott & Blanchet Expires April 11, 2014 [Page 7]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
CBHE Service Number Registry
+--------------------+--------------------------------+-------------+
| Value | Description | Reference |
+--------------------+--------------------------------+-------------+
| 0 | Bundle Protocol Administrative | [RFC6260] |
| | Record | |
| 1 | CCSDS File Delivery Service | [CFDP] |
| 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 |
+--------------------+--------------------------------+-------------+
3.3. 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 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 | [RFC5050] |
| 2 | Custody signal | [RFC5050] |
| 3-15 | Unassigned | This document |
+-------+----------------------+---------------+
Scott & Blanchet Expires April 11, 2014 [Page 8]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
4. Acknowledgements
The editors would like to thank the following people, in no specific
order: Scott Burleigh, Stephen Farrell, John Buford.
5. References
5.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.
[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.
5.2. Informative References
[CCSDS] "The Consultative Committee for Space Data Systems at
http://www.ccsds.org".
[SANA] "The CCSDS SANA Registry page at http://sanaregistry.org".
Scott & Blanchet Expires April 11, 2014 [Page 9]
Internet-Draft LTP, CBHE, and BP IANA Registries October 2013
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
Marc Blanchet
Viagenie
246 Aberdeen
Quebec, Quebec G1R 2E1
Canada
Phone: +1-418-656-9254
Email: marc.blanchet@viagenie.ca
Scott & Blanchet Expires April 11, 2014 [Page 10]
