Delay-Tolerant Networks (DTN) Bundle Protocol IANA Registries
draft-irtf-dtnrg-iana-bp-registries-01.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. 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 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 28, 2011.

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 Simplified BSD License.

Table of Contents

1.  Introduction
2.  Treatment of Flag Fields Encoded using SDNVs
3.  Bundle Protocol
    3.1.  Bundle Block Types
    3.2.  Primary Bundle Protocol Version
    3.3.  Bundle Processing Control Flags
    3.4.  Block Processing Control Flags
    3.5.  Bundle Status Report Flags
    3.6.  Bundle Status Report Reason Codes
    3.7.  Bundle Custody Signal Reason Codes
4.  Security Considerations
5.  IANA Considerations
6.  Acknowledgements
7.  References
    7.1.  Normative References
    7.2.  Informative 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. 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.  Treatment of Flag Fields Encoded using SDNVs

The DTN protocols use several extensible bit flag fields that are encoded as Self-Delimiting Numeric Values (SDNVs) as defined in Section 4.1 of [RFC5050] (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.). 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 [RFC5050] (Scott, K. and S. Burleigh, “Bundle Protocol Specification,” November 2007.).

Processing of SDNV-encoded flags is discussed in [I‑D.irtf‑dtnrg‑sdnv] (Eddy, W. and E. Davies, “Using Self-Delimiting Numeric Values in Protocols,” October 2010.).

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

3.  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.

3.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.

3.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

The value "0-5" 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.

3.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] encoded as an SDNV(see section (Treatment of Flag Fields Encoded using SDNVs)). An IANA registry shall be setup as follows.

The registration policy for this registry is: Specification Required

The Value range is: Variable length. Maximum number of flag bit positions: 64

Bundle Processing Control Flags Registry

3.4.  Block Processing Control Flags

The Bundle Protocol has a Block Processing Control flags field (section 4.3) (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. Maximum number of flag bit positions: 64

Block Processing Control Flags Registry

3.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: RFC Required

The Value range is: 8 bits.

Bundle Status Report Flags Registry

The value "00000000" 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.

3.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

The value "255" 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.

3.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

The value "127" 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.

4.  Security Considerations

This document requests the creation of registries managed by IANA. There is no security issues involved. Refer to Security Considerations of the referenced protocols.

5.  IANA Considerations

IANA is requested to create the registries as described in the previous sections.

6.  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, Daniel Ellard, Scott Burleigh, Keith Scott, Elwyn Davies.

7.  References

7.1. Normative References

7.2. Informative References

Author's Address