6255
INFORMATIONAL
Delay-Tolerant Networking Bundle Protocol IANA Registries
Authors: M. Blanchet
Date: May 2011
Stream: IRTF
Abstract
The Delay-Tolerant Networking (DTN) Research Group research group has defined many protocols such as the Bundle Protocol and Licklider Transmission Protocol. The specifications of these protocols contain fields that are subject to a registry. For the purpose of its research work, the group 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 executed by IANA. This document is not an Internet Standards Track specification; it is published for informational purposes.
RFC 6255
INFORMATIONAL
Internet Research Task Force (IRTF) M. Blanchet
Request for Comments: 6255 Viagenie
Category: Informational May 2011
ISSN: 2070-1721
<span class="h1">Delay-Tolerant Networking Bundle Protocol IANA Registries</span>
Abstract
The Delay-Tolerant Networking (DTN) Research Group research group has
defined many protocols such as the Bundle Protocol and Licklider
Transmission Protocol. The specifications of these protocols contain
fields that are subject to a registry. For the purpose of its
research work, the group 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
executed by IANA.
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
Network 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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6255">http://www.rfc-editor.org/info/rfc6255</a>.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Blanchet Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Treatment of Flag Fields Encoded Using SDNVs ....................<a href="#page-2">2</a>
<a href="#section-3">3</a>. Bundle Protocol .................................................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Bundle Block Types .........................................<a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. Primary Bundle Protocol Version ............................<a href="#page-3">3</a>
<a href="#section-3.3">3.3</a>. Bundle Processing Control Flags ............................<a href="#page-4">4</a>
<a href="#section-3.4">3.4</a>. Block Processing Control Flags .............................<a href="#page-5">5</a>
<a href="#section-3.5">3.5</a>. Bundle Status Report Flags .................................<a href="#page-6">6</a>
<a href="#section-3.6">3.6</a>. Bundle Status Report Reason Codes ..........................<a href="#page-7">7</a>
<a href="#section-3.7">3.7</a>. Bundle Custody Signal Reason Codes .........................<a href="#page-7">7</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-8">8</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-8">8</a>
<a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-8">8</a>
<a href="#section-7">7</a>. References ......................................................<a href="#page-9">9</a>
<a href="#section-7.1">7.1</a>. Normative References .......................................<a href="#page-9">9</a>
<a href="#section-7.2">7.2</a>. Informative References .....................................<a href="#page-9">9</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The DTNRG research group has defined many protocols relevant to the
DTN architecture [<a href="./rfc4838" title=""Delay-Tolerant Networking Architecture"">RFC4838</a>] such as the Bundle Protocol [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] and
Licklider Transmission Protocol [<a href="./rfc5326" title=""Licklider Transmission Protocol - Specification"">RFC5326</a>]. The specifications of
these protocols contain fields that are subject to a registry. For
the purpose of its research work, the group created ad hoc registries
(<a href="http://www.dtnrg.org/wiki/AssignedNamesAndNumbers">http://www.dtnrg.org/wiki/AssignedNamesAndNumbers</a>). 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
executed by IANA.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Treatment of Flag Fields Encoded Using SDNVs</span>
The DTN protocols use several extensible bit flag fields that are
encoded as Self-Delimiting Numeric Values (SDNVs) as defined in
<a href="./rfc5050#section-4.1">Section 4.1 of [RFC5050]</a>. For these fields, the registry specifies
the allocation and usage of bit positions within the unencoded field.
The SDNV encoding treats the ensemble of bits in the unencoded value
as a numeric value to be encoded on transmission and decoded on
reception as described in [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>].
Processing of SDNV-encoded flags is discussed in [<a href="./rfc6256" title=""Using Self-Delimiting Numeric Values in Protocols"">RFC6256</a>].
<a href="./rfc5050#section-4.1">Section 4.1 of [RFC5050]</a> specifies that implementations are not
required to handle SDNVs with more than 64 bits in their unencoded
value. Accordingly, SDNV-encoded flag fields should be limited to 64
bit positions.
<span class="grey">Blanchet Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
IANA registry policies and wording used in this document are
described in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Bundle Protocol</span>
The Bundle Protocol (BP) [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] has fields requiring a registry
managed by IANA.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Bundle Block Types</span>
The Bundle Protocol has a Bundle Block Type code field (<a href="#section-4.5.2">Section</a>
<a href="#section-4.5.2">4.5.2</a>) [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>]. An IANA registry has been set up as follows.
The registration policy for this registry is:
0-191: Specification Required
192-255: Private or experimental use. No assignment by IANA.
The Value range is: unsigned 8-bit integer.
Bundle Block Type Registry
+--------------+---------------------------------+---------------+
| Value | Description | Reference |
+--------------+---------------------------------+---------------+
| 0 | Reserved | This document |
| 1 | Bundle Payload Block | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 2-191 | Unassigned | |
| 192-255 | Private and/or Experimental Use | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
+--------------+---------------------------------+---------------+
The value "0" was not defined in any document or in the ad hoc
registry. As per consensus by the DTNRG research group, it is
reserved per this document.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Primary Bundle Protocol Version</span>
The Bundle Protocol has a version field (see <a href="./rfc5050#section-4.5.1">Section 4.5.1 of
[RFC5050]</a>). An IANA registry has been set up as follows.
The registration policy for this registry is: RFC Required
The Value range is: unsigned 8-bit integer.
<span class="grey">Blanchet Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
Primary Bundle Protocol Version Registry
+-------+-------------+---------------+
| Value | Description | Reference |
+-------+-------------+---------------+
| 0-5 | Reserved | This document |
| 6 | Assigned | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 7-255 | Unassigned | |
+-------+-------------+---------------+
The value "0-5" was not defined in any document or in the ad hoc
registry. As per consensus by the DTNRG research group, it is
reserved per this document.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Bundle Processing Control Flags</span>
The Bundle Protocol has a Bundle Processing Control Flags field (see
<a href="./rfc5050#section-4.2">Section 4.2 of [RFC5050]</a>) encoded as an SDNV (see <a href="#section-2">Section 2</a>). An
IANA registry has been set up as follows.
The registration policy for this registry is: Specification Required
The Value range is: Variable length. Maximum number of flag bit
positions: 64
<span class="grey">Blanchet Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
Bundle Processing Control Flags Registry
+--------------------+----------------------------------+-----------+
| Bit Position | Description | Reference |
| (right to left) | | |
+--------------------+----------------------------------+-----------+
| 0 | Bundle is a fragment | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 1 | Application data unit is an | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | administrative record | |
| 2 | Bundle must not be fragmented | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 3 | Custody transfer is requested | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 4 | Destination endpoint is a | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | singleton | |
| 5 | Acknowledgement by application | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | is requested | |
| 6 | Reserved | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 7-8 | Class of service: priority | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 9-13 | Class of service: reserved | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 14 | Request reporting of bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | reception | |
| 15 | Request reporting of custody | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | acceptance | |
| 16 | Request reporting of bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | forwarding | |
| 17 | Request reporting of bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | delivery | |
| 18 | Request reporting of bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | deletion | |
| 19 | Reserved | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 20 | Reserved | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 21-63 | Unassigned | |
+--------------------+----------------------------------+-----------+
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Block Processing Control Flags</span>
The Bundle Protocol has a Block Processing Control Flags field (see
<a href="./rfc5050#section-4.3">Section 4.3 of [RFC5050]</a>). An IANA registry has been set up as
follows.
The registration policy for this registry is: Specification Required
The Value range is: Variable length. Maximum number of flag bit
positions: 64
<span class="grey">Blanchet Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
Block Processing Control Flags Registry
+--------------------+----------------------------------+-----------+
| Bit Position | Description | Reference |
| (right to left) | | |
+--------------------+----------------------------------+-----------+
| 0 | Block must be replicated in | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | every fragment | |
| 1 | Transmit status report if block | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | can't be processed | |
| 2 | Delete bundle if block can't be | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | processed | |
| 3 | Last block | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 4 | Discard block if it can't be | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | processed | |
| 5 | Block was forwarded without | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | being processed | |
| 6 | Block contains an EID-reference | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | field | |
| 7-63 | Unassigned | |
+--------------------+----------------------------------+-----------+
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Bundle Status Report Flags</span>
The Bundle Protocol has a Status Report Status Flag field (see
<a href="./rfc5050#section-6.1.1">Section 6.1.1 of [RFC5050]</a>). An IANA registry has been set up as
follows.
The registration policy for this registry is: RFC Required
The Value range is: 8 bits.
Bundle Status Report Flags Registry
+----------+----------------------------------------+---------------+
| Value | Description | Reference |
+----------+----------------------------------------+---------------+
| 00000000 | Reserved | This document |
| 00000001 | Reporting node received bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 00000010 | Reporting node accepted custody of | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | bundle | |
| 00000100 | Reporting node forwarded the bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 00001000 | Reporting node delivered the bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 00010000 | Reporting node deleted the bundle | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 00100000 | Unassigned | |
| 01000000 | Unassigned | |
| 10000000 | Unassigned | |
+----------+----------------------------------------+---------------+
<span class="grey">Blanchet Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
The value "00000000" was not defined in any document or in the ad hoc
registry. As per consensus by the DTNRG research group, it is
reserved per this document.
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Bundle Status Report Reason Codes</span>
The Bundle Protocol has a Bundle Status Report Reason Codes field
(see <a href="./rfc5050#section-6.1.1">Section 6.1.1 of [RFC5050]</a>). An IANA registry has been set up
as follows.
The registration policy for this registry is: Specification Required
The Value range is: unsigned 8-bit integer.
Bundle Status Report Reason Codes Registry
+-------+-------------------------------------------+---------------+
| Value | Description | Reference |
+-------+-------------------------------------------+---------------+
| 0 | No additional information | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 1 | Lifetime expired | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 2 | Forwarded over unidirectional link | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 3 | Transmission canceled | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 4 | Depleted storage | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 5 | Destination endpoint ID unintelligible | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 6 | No known route to destination from here | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 7 | No timely contact with next node on route | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 8 | Block unintelligible | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 9-254 | Unassigned | |
| 255 | Reserved | This document |
+-------+-------------------------------------------+---------------+
The value "255" was not defined in any document or in the ad hoc
registry. As per consensus by the DTNRG research group, it is
reserved per this document.
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Bundle Custody Signal Reason Codes</span>
The Bundle Protocol has a Bundle Custody Signal Reason Codes field
(see <a href="./rfc5050#section-6.1.2">Section 6.1.2 of [RFC5050]</a>). An IANA registry has been set up
as follows.
The registration policy for this registry is: Specification Required
The Value range is: unsigned 7-bit integer.
<span class="grey">Blanchet Informational [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
Bundle Custody Signal Reason Codes Registry
+--------------+--------------------------------------+-------------+
| Value | Description | Reference |
+--------------+--------------------------------------+-------------+
| 0 | No additional information | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 1-2 | Unassigned | |
| 3 | Redundant reception (reception by a | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | node that is a custodial node for | |
| | this bundle) | |
| 4 | Depleted storage | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 5 | Destination endpoint ID | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | unintelligible | |
| 6 | No known route to destination from | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | here | |
| 7 | No timely contact with next node on | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| | route | |
| 8 | Block unintelligible | [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>] |
| 9-126 | Unassigned | |
| 127 | Reserved | This |
| | | document |
+--------------+--------------------------------------+-------------+
The value "127" was not defined in any document or in the ad hoc
registry. As per consensus by the DTNRG research group, it is
reserved per this document.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document requests the creation of registries managed by IANA.
There are no security issues involved. Refer to the Security
Considerations section of the referenced protocols.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has created the registries as described in the previous
sections.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The editor would like to thank the following people who have provided
comments and suggestions to this document, in no specific order:
Stephen Farrell, Daniel Ellard, Scott Burleigh, Keith Scott, and
Elwyn Davies.
<span class="grey">Blanchet Informational [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc6255">RFC 6255</a> DTN IANA Registries May 2011</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC5050">RFC5050</a>] Scott, K. and S. Burleigh, "Bundle Protocol
Specification", <a href="./rfc5050">RFC 5050</a>, November 2007.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-RFC4838">RFC4838</a>] Cerf, V., Burleigh, S., Hooke, A., Torgerson, L., Durst,
R., Scott, K., Fall, K., and H. Weiss, "Delay-Tolerant
Networking Architecture", <a href="./rfc4838">RFC 4838</a>, April 2007.
[<a id="ref-RFC5326">RFC5326</a>] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider
Transmission Protocol - Specification", <a href="./rfc5326">RFC 5326</a>,
September 2008.
[<a id="ref-RFC6256">RFC6256</a>] Eddy, W. and E. Davies, "Using Self-Delimiting Numeric
Values in Protocols", <a href="./rfc6256">RFC 6256</a>, May 2011.
Author's Address
Marc Blanchet
Viagenie
2875 boul. Laurier, suite D2-630
Quebec, QC G1V 2M2
Canada
EMail: [email protected]
URI: <a href="http://viagenie.ca">http://viagenie.ca</a>
Blanchet Informational [Page 9]
Annotations
Select text to annotate