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.

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.

Table of Contents

1.  Introduction
2.  Bundle Protocol
    2.1.  Bundle Block Types
    2.2.  Primary Bundle Protocol Version
    2.3.  Bundle Processing Control Flags
    2.4.  Block Processing Control Flags
    2.5.  Bundle Status Report Flags
    2.6.  Bundle Status Report Reason Codes
    2.7.  Bundle Custody Signal Reason Codes
3.  URI Scheme
4.  MIME Media Type
5.  LickLider Protocol
    5.1.  LickLider Protocol Version
    5.2.  LickLider Cancel Segments Reason Codes
6.  Security Considerations
7.  IANA Considerations
8.  Acknowledgements
9.  Normative References
§  Author's Address

1.  Introduction

The DTNRG research group has defined many protocols[RFC4838] (Cerf, V., Burleigh, S., Hooke, A., Torgerson, L., Durst, R., Scott, K., Fall, K., and H. Weiss, “Delay-Tolerant Networking Architecture,” April 2007.) such as Bundle Protocol[RFC5050] (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) and Licklider[RFC5326] (Ramadas, M., Burleigh, S., and S. Farrell, “Licklider Transmission Protocol - Specification,” September 2008.). 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] (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) 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) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [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.

Bundle Block Type Codes Registry

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) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [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

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) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [RFC5050]. An IANA registry shall be setup as follows.

The registration policy for this registry is: Specification Required

The Value range is: Variable length.

Bundle Processing Control Flags Registry

RG TBD: decide registration policy.

2.4.  Block Processing Control Flags

The Bundle Protocol has a Block Processing Control flags field (section 4.2) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [RFC5050]. An IANA registry shall be setup as follows.

The registration policy for this registry is: Specification Required

The Value range is: Variable length.

Block Processing Control Flags Registry

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) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [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

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) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [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

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) (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.) [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.

Bundle Custody Signal Reason Codes Registry

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 [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) (Ramadas, M., Burleigh, S., and S. Farrell, “Licklider Transmission Protocol - Specification,” September 2008.) [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

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) (Ramadas, M., Burleigh, S., and S. Farrell, “Licklider Transmission Protocol - Specification,” September 2008.) [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.

LickLider Cancel Segments Reason Codes Registry

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

Author's Address