Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries
RFC 7116
| Document | Type |
RFC - Informational
(February 2014; No errata)
Was draft-dtnrg-ltp-cbhe-registries (individual)
|
|
|---|---|---|---|
| Last updated | 2014-02-12 | ||
| Stream | IRTF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| IETF conflict review | conflict-review-dtnrg-ltp-cbhe-registries | ||
| Stream | IRTF state | Published RFC | |
| Consensus Boilerplate | Unknown | ||
| Document shepherd | Joerg Ott | ||
| IESG | IESG state | RFC 7116 (Informational) | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
Internet Research Task Force (IRTF) K. Scott
Request for Comments: 7116 The MITRE Corporation
Category: Informational M. Blanchet
ISSN: 2070-1721 Viagenie
February 2014
Licklider Transmission Protocol (LTP),
Compressed Bundle Header Encoding (CBHE),
and Bundle Protocol IANA Registries
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.
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 RFC
5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7116.
Scott & Blanchet Informational [Page 1]
RFC 7116 LTP, CBHE, and BP IANA Registries February 2014
Copyright Notice
Copyright (c) 2014 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.
Table of Contents
1. Introduction ....................................................2
2. Security Considerations .........................................3
3. IANA Considerations .............................................3
3.1. Licklider Transmission Protocol ............................3
3.1.1. LTP Cancel Segment Reason Codes .....................3
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 ................................................8
5. References ......................................................9
5.1. Normative References .......................................9
5.2. Informative References .....................................9
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 that IANA needs to
take and uses the well-known IANA policy definitions as described 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 IANA
registries for these fields.
Scott & Blanchet Informational [Page 2]
RFC 7116 LTP, CBHE, and BP IANA Registries February 2014
Because of its association with space communication and the
Consultative Committee for Space Data Systems [CCSDS], portions of
the "CBHE Node Numbers", "CBHE Service Numbers", and "LTP Engine
Numbers" spaces are delegated by this document to the CCSDS Space
Show full document text