Internet DRAFT - draft-blanchet-dtnrg-iana-registries
draft-blanchet-dtnrg-iana-registries
Network Working Group M. Blanchet
Internet-Draft Viagenie
Intended status: Informational March 22, 2010
Expires: September 23, 2010
Delay-Tolerant Networks (DTN) IANA Registries
draft-blanchet-dtnrg-iana-registries-00.txt
Abstract
The DTNRG research group has defined many protocols such as Bundle
Protocol and Licklider. The specifications of these protocols
contain fields that are subject to a registry. For the purpose of
its research work, the group created adhoc registries[DTNRGREG]. As
the specifications are stable and have multiple interoperable
implementations, the group would like to handoff the registries to
IANA for official custidy. This document describes the actions
needed to be executed by IANA.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 23, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
Blanchet Expires September 23, 2010 [Page 1]
Internet-Draft DTN IANA Registries March 2010
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 BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Blanchet Expires September 23, 2010 [Page 2]
Internet-Draft DTN IANA Registries March 2010
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Bundle Protocol . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Bundle Block Types . . . . . . . . . . . . . . . . . . . . 4
2.2. Primary Bundle Protocol Version . . . . . . . . . . . . . 6
2.3. Bundle Processing Control Flags . . . . . . . . . . . . . 6
2.4. Block Processing Control Flags . . . . . . . . . . . . . . 7
2.5. Bundle Status Report Flags . . . . . . . . . . . . . . . . 8
2.6. Bundle Status Report Reason Codes . . . . . . . . . . . . 9
2.7. Bundle Custody Signal Reason Codes . . . . . . . . . . . . 9
3. URI Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. MIME Media Type . . . . . . . . . . . . . . . . . . . . . . . 11
5. LickLider Protocol . . . . . . . . . . . . . . . . . . . . . . 11
5.1. LickLider Protocol Version . . . . . . . . . . . . . . . . 11
5.2. LickLider Cancel Segments Reason Codes . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
9. Normative References . . . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
Blanchet Expires September 23, 2010 [Page 3]
Internet-Draft DTN IANA Registries March 2010
1. Introduction
The DTNRG research group has defined many protocols[RFC4838] such as
Bundle Protocol[RFC5050] and Licklider[RFC5326]. The specifications
of these protocols contain fields that are subject to a registry.
For the purpose of its research work, the group created adhoc
registries[DTNRGREG]. As the specifications are stable and have
multiple interoperable implementations, the group would like to
handoff the registries to IANA for official custidy. This document
describes the actions needed to be executed by IANA.
2. Bundle Protocol
The Bundle Protocol(BP)[RFC5050] has fields requiring a registry
managed by IANA.
2.1. Bundle Block Types
The Bundle Protocol has a Bundle Block Type code field (section
4.5.2) [RFC5050]. An IANA registry shall be setup 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.
Blanchet Expires September 23, 2010 [Page 4]
Internet-Draft DTN IANA Registries March 2010
Bundle Block Type Codes Registry
+--------+--------------+-------------------------------------------+
| Value | Description | Reference |
+--------+--------------+-------------------------------------------+
| 0 | Reserved | This document |
| 1 | Bundle | [RFC5050] |
| | Payload | |
| | Block | |
| 2 | Bundle | [I-D.irtf-dtnrg-bundle-security] |
| | Authenticati | |
| | on Block | |
| 3 | Bundle | [I-D.irtf-dtnrg-bundle-security] |
| | Security | |
| | Block | |
| 4 | Payload | [I-D.irtf-dtnrg-bundle-security] |
| | Confidential | |
| | ity Block | |
| 5 | Previous Hop | [I-D.irtf-dtnrg-bundle-previous-hop-block |
| | Insertion | ] |
| | Block | |
| 6 | Proxy EID | [I-D.symington-dtnrg-bundle-multicast-cus |
| | Extension | todial] |
| | Block | |
| 7 | Retransmissi | [I-D.irtf-dtnrg-bundle-retrans-block] |
| | on Block | |
| 8 | Metadata | [I-D.irtf-dtnrg-bundle-metadata-block] |
| | Extension | |
| | Block | |
| 9 | Extension | [I-D.irtf-dtnrg-bundle-security] |
| | Security | |
| | Block | |
| 10-19 | Unassigned | |
| 20 | Extended | [I-D.irtf-dtnrg-ecos] |
| | Class of | |
| | Service | |
| | Block | |
| TBD | SCHL | [I-D.fall-dtnrg-schl] |
| | Extension | |
| | Block | |
| TBD-19 | Unassigned | |
| 1 | | |
| 192-25 | Private | [RFC5050] |
| 5 | and/or | |
| | experimental | |
| | use | |
+--------+--------------+-------------------------------------------+
Blanchet Expires September 23, 2010 [Page 5]
Internet-Draft DTN IANA Registries March 2010
The value "0" was not defined in any document or in the adhoc
registry. As per concensus by the DNTRG research group, it is
reserved per this document.
RG TBD: decide for value 0. decide registration policy
2.2. Primary Bundle Protocol Version
The Bundle Protocol has a version field (section 4.5.1) [RFC5050].
An IANA registry shall be setup as follows.
The registration policy for this registry is: RFC Required
The Value range is: unsigned 8 bit integer.
Primary Bundle Protocol Version Registry
+-------+-------------+---------------+
| Value | Description | Reference |
+-------+-------------+---------------+
| 0-5 | Reserved | This document |
| 6 | Assigned | [RFC5050] |
| 7-255 | Unassigned | |
+-------+-------------+---------------+
RG TBD: decide registration policy. versions 0-5 are ...
2.3. Bundle Processing Control Flags
The Bundle Protocol has a Bundle Processing Control flags field
(section 4.2) [RFC5050]. An IANA registry shall be setup as follows.
The registration policy for this registry is: Specification Required
The Value range is: Variable length.
Blanchet Expires September 23, 2010 [Page 6]
Internet-Draft DTN IANA Registries March 2010
Bundle Processing Control Flags Registry
+---------------------+---------------------------------+-----------+
| Bit Position (right | Description | Reference |
| to left) | | |
+---------------------+---------------------------------+-----------+
| 0 | Bundle is a fragment | [RFC5050] |
| 1 | Application data unit is an | [RFC5050] |
| | administrative record | |
| 2 | Bundle must not be fragmented | [RFC5050] |
| 3 | Custody transfer is requested | [RFC5050] |
| 4 | Destination endpoint is a | [RFC5050] |
| | singleton | |
| 5 | Acknowledgement by application | [RFC5050] |
| | is requested | |
| 6 | Reserved | [RFC5050] |
| 7-8 | Class of service: priority | [RFC5050] |
| 9-13 | Class of service: reserved | [RFC5050] |
| 14 | Request reporting of bundle | [RFC5050] |
| | reception | |
| 15 | Request reporting of custody | [RFC5050] |
| | acceptance | |
| 16 | Request reporting of bundle | [RFC5050] |
| | forwarding | |
| 17 | Request reporting of bundle | [RFC5050] |
| | delivery | |
| 18 | Request reporting of bundle | [RFC5050] |
| | deletion | |
| 19 | Reserved | [RFC5050] |
| 20 | Reserved | [RFC5050] |
+---------------------+---------------------------------+-----------+
RG TBD: decide registration policy.
2.4. Block Processing Control Flags
The Bundle Protocol has a Block Processing Control flags field
(section 4.2) [RFC5050]. An IANA registry shall be setup as follows.
The registration policy for this registry is: Specification Required
The Value range is: Variable length.
Blanchet Expires September 23, 2010 [Page 7]
Internet-Draft DTN IANA Registries March 2010
Block Processing Control Flags Registry
+--------------------+----------------------------------+-----------+
| Bit Position | Description | Reference |
| (right to left) | | |
+--------------------+----------------------------------+-----------+
| 0 | Block must be replicated in | [RFC5050] |
| | every fragment | |
| 1 | Transmit status report if block | [RFC5050] |
| | can't be processed | |
| 2 | Delete bundle if block can't be | [RFC5050] |
| | processed | |
| 3 | Last block | [RFC5050] |
| 4 | Discard block if it can't be | [RFC5050] |
| | processed | |
| 5 | Block was forwarded without | [RFC5050] |
| | being processed | |
| 0 | Block contains an EID-reference | [RFC5050] |
| | field | |
+--------------------+----------------------------------+-----------+
RG TBD: decide registration policy.
2.5. Bundle Status Report Flags
The Bundle Protocol has a Status Report Status Flag field(section
6.1.1) [RFC5050]. An IANA registry shall be setup as follows.
The registration policy for this registry is: Specification Required
The Value range is: 8 bits.
Bundle Status Report Flags Registry
+----------+----------------------------------------+---------------+
| Value | Description | Reference |
+----------+----------------------------------------+---------------+
| 00000000 | Reserved | This document |
| 00000001 | Reporting node received bundle | [RFC5050] |
| 00000010 | Reporting node accepted custody of | [RFC5050] |
| | bundle | |
| 00000100 | Reporting node forwarded the bundle | [RFC5050] |
| 00001000 | Reporting node delivered the bundle | [RFC5050] |
| 00010000 | Reporting node deleted the bundle | [RFC5050] |
| 00100000 | Unassigned | [RFC5050] |
| 01000000 | Unassigned | [RFC5050] |
| 10000000 | Unassigned | [RFC5050] |
+----------+----------------------------------------+---------------+
Blanchet Expires September 23, 2010 [Page 8]
Internet-Draft DTN IANA Registries March 2010
RG TBD: decide registration policy. value 0 is ...
2.6. Bundle Status Report Reason Codes
The Bundle Protocol has a Bundle Status Report Reason Codes
field(section 6.1.1) [RFC5050]. An IANA registry shall be setup 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 | [RFC5050] |
| 1 | Lifetime expired | [RFC5050] |
| 2 | Forwarded over unidirectional link | [RFC5050] |
| 3 | Transmission canceled | [RFC5050] |
| 4 | Depleted storage | [RFC5050] |
| 5 | Destination endpoint ID unintelligible | [RFC5050] |
| 6 | No known route to destination from here | [RFC5050] |
| 7 | No timely contact with next node on route | [RFC5050] |
| 8 | Block unintelligible | [RFC5050] |
| 9-255 | Unassigned | |
+-------+-------------------------------------------+-----------+
RG TBD: decide registration policy. do we want to reserve a value for
future extensions? 255?
2.7. Bundle Custody Signal Reason Codes
The Bundle Protocol has a Bundle Custody Signal Reason Codes
field(section 6.1.2) [RFC5050]. An IANA registry shall be setup as
follows.
The registration policy for this registry is: Specification Required
The Value range is: unsigned 7 bit integer.
Blanchet Expires September 23, 2010 [Page 9]
Internet-Draft DTN IANA Registries March 2010
Bundle Custody Signal Reason Codes Registry
+-------+---------------+-------------------------------------------+
| Value | Description | Reference |
+-------+---------------+-------------------------------------------+
| 0 | No additional | [RFC5050] |
| | information | |
| 1-2 | Unassigned | |
| 3 | Redundant | [RFC5050] |
| | reception | |
| | (reception by | |
| | a node that | |
| | is a | |
| | custodial | |
| | node for this | |
| | bundle) | |
| 4 | Depleted | [RFC5050] |
| | storage | |
| 5 | Destination | [RFC5050] |
| | endpoint ID | |
| | unintelligibl | |
| | e | |
| 6 | No known | [RFC5050] |
| | route to | |
| | destination | |
| | from here | |
| 7 | No timely | [RFC5050] |
| | contact with | |
| | next node on | |
| | route | |
| 8 | Block | [RFC5050] |
| | unintelligibl | |
| | e | |
| 9 | Bundle | [I-D.symington-dtnrg-bundle-multicast-cus |
| | Forwarded | todial] |
| | Non-custodial | |
| | ly | |
| 10-12 | Unassigned | |
| 7 | | |
+-------+---------------+-------------------------------------------+
RG TBD: decide registration policy. do we want to reserve a value for
future extensions? 255?
3. URI Scheme
IANA has registered the "dtn" URI Scheme
Blanchet Expires September 23, 2010 [Page 10]
Internet-Draft DTN IANA Registries March 2010
[IANAURISCH:http://www.iana.org/assignments/uri-schemes.html] as
provisional. This document requests to change the status of this
assignment from "Provisional" to "Permanent".
RG TBD: request dtn as permanent? has to be "ready" per RFC4395
4. MIME Media Type
RG TBD: do we want application/dtn?
5. LickLider Protocol
5.1. LickLider Protocol Version
The Licklider Protocol has a version field (section 3.1) [RFC5326].
An IANA registry shall be setup as follows.
The registration policy for this registry is: RFC Required
The Value range is: unsigned 4 bit integer.
LickLider Protocol Version Registry
+-------+------------------+-----------+
| Value | Description | Reference |
+-------+------------------+-----------+
| 0 | RFC 5326 version | [RFC5326] |
| 1-15 | Unassigned | |
+-------+------------------+-----------+
RG TBD: decide registration policy.
5.2. LickLider Cancel Segments Reason Codes
The LickLider Protocol has Cancel Segments Reason Codes field(section
3.2.4) [RFC5326]. An IANA registry shall be setup as follows.
The registration policy for this registry is: Specification Required
The Value range is: unsigned 8 bit integer.
Blanchet Expires September 23, 2010 [Page 11]
Internet-Draft DTN IANA Registries March 2010
LickLider Cancel Segments Reason Codes Registry
+-------+------------+----------------------------------+-----------+
| Value | Mnemonic | Description | Reference |
+-------+------------+----------------------------------+-----------+
| 0 | USR_CNCLD | Client service canceled session | [RFC5326] |
| 1 | UNREACH | Unreachable client service | [RFC5326] |
| 2 | RLEXC | Retransmission limit exceeded | [RFC5326] |
| 3 | MISCOLORED | Received either a red-part data | [RFC5326] |
| | | segment at block offset above | |
| | | any green-part data segment | |
| | | offset or a green-part data | |
| | | segment at block offset below | |
| | | any red-part data segment offset | |
| 4 | SYS_CNCLD | A system error condition caused | [RFC5326] |
| | | unexpected session termination | |
| 5 | RXMTCYCEXC | Exceeded the | [RFC5326] |
| | | Retransmission-Cycles limit | |
| 6-255 | Unassigned | | |
+-------+------------+----------------------------------+-----------+
RG TBD: decide registration policy. RFC5326 says 6-255 is
"reserved". does that mean no new assignment, or "unassigned"?
6. Security Considerations
TBD
7. IANA Considerations
TBD. point to all sections requiring IANA Actions.
8. Acknowledgements
The editor would like to thank the following people who have provided
comments and suggestions to this document, in no specific order:
Stephen Farrell.
9. Normative References
[I-D.fall-dtnrg-schl]
Fall, K., "DTN Scope Control using Hop Limits (SCHL)",
draft-fall-dtnrg-schl-00 (work in progress),
February 2010.
Blanchet Expires September 23, 2010 [Page 12]
Internet-Draft DTN IANA Registries March 2010
[I-D.irtf-dtnrg-bundle-metadata-block]
Symington, S., "Delay-Tolerant Networking Metadata
Extension Block",
draft-irtf-dtnrg-bundle-metadata-block-07 (work in
progress), February 2010.
[I-D.irtf-dtnrg-bundle-previous-hop-block]
Symington, S., "Delay-Tolerant Networking Previous Hop
Insertion Block",
draft-irtf-dtnrg-bundle-previous-hop-block-11 (work in
progress), February 2010.
[I-D.irtf-dtnrg-bundle-retrans-block]
Symington, S., "Delay-Tolerant Networking Retransmission
Block", draft-irtf-dtnrg-bundle-retrans-block-06 (work in
progress), October 2009.
[I-D.irtf-dtnrg-bundle-security]
Symington, S., Farrell, S., Weiss, H., and P. Lovell,
"Bundle Security Protocol Specification",
draft-irtf-dtnrg-bundle-security-15 (work in progress),
February 2010.
[I-D.irtf-dtnrg-ecos]
Burleigh, S., "Bundle Protocol Extended Class Of Service
(ECOS)", draft-irtf-dtnrg-ecos-00 (work in progress),
December 2009.
[I-D.symington-dtnrg-bundle-multicast-custodial]
Symington, S., Durst, R., and K. Scott, "Delay-Tolerant
Networking Custodial Multicast Extensions",
draft-symington-dtnrg-bundle-multicast-custodial-06 (work
in progress), August 2009.
[RFC4838] Cerf, V., Burleigh, S., Hooke, A., Torgerson, L., Durst,
R., Scott, K., Fall, K., and H. Weiss, "Delay-Tolerant
Networking Architecture", RFC 4838, April 2007.
[RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol
Specification", RFC 5050, November 2007.
[RFC5326] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider
Transmission Protocol - Specification", RFC 5326,
September 2008.
Blanchet Expires September 23, 2010 [Page 13]
Internet-Draft DTN IANA Registries March 2010
Author's Address
Marc Blanchet
Viagenie
2600 boul. Laurier, suite 625
Quebec, QC G1V 4W1
Canada
Email: Marc.Blanchet@viagenie.ca
URI: http://www.viagenie.ca
Blanchet Expires September 23, 2010 [Page 14]
