One document matched: draft-irtf-dtnrg-iana-bp-registries-02.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY rfc2119 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
]>

<rfc category="info" ipr="trust200902" docName="draft-irtf-dtnrg-iana-bp-registries-02.txt">
  <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
  <?rfc toc="yes" ?>
  <?rfc symrefs="yes" ?>
  <?rfc sortrefs="yes"?>
  <?rfc iprnotified="no" ?>
  <?rfc strict="yes" ?>
  <?rfc compact="yes" ?>
  <front>
    <title abbrev="DTN IANA Registries">Delay-Tolerant Networks (DTN) Bundle Protocol IANA Registries</title>
    <author initials="M." surname="Blanchet" fullname="Marc Blanchet">
      <organization>Viagenie</organization>
      <address>
    <postal>
      <street>2875 boul. Laurier, suite D2-630</street>
      <city>Quebec</city>
      <region>QC</region>
      <code>G1V 2M2</code>
      <country>Canada</country>
    </postal>
    <email>Marc.Blanchet@viagenie.ca</email>
    <uri>http://viagenie.ca</uri>
  </address>
    </author>
    <date month="February" year="2011"/>
    <abstract>
      <t>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 custody.
        This document describes the actions needed to be executed by IANA.
      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction">
      <t>The DTNRG research group has defined many protocols<xref target="RFC4838"/> such as Bundle Protocol<xref target="RFC5050"/> and Licklider<xref target="RFC5326"/>. 
        The specifications of these protocols contain fields that are subject to a registry. 
        For the purpose of its research work, the group created <eref target='http://www.dtnrg.org/wiki/AssignedNamesAndNumbers'>adhoc registries</eref>. 
        As the specifications are stable and have multiple interoperable implementations, 
        the group would like to handoff the registries to IANA for official custody. 
        This document describes the actions needed to be executed by IANA.
</t>
</section>
<section anchor="sdnv" title="Treatment of Flag Fields Encoded using SDNVs">
<t>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 <xref target="RFC5050"/>. 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 <xref target="RFC5050"/>.</t>
<t>Processing of SDNV-encoded flags is discussed in <xref target="I-D.irtf-dtnrg-sdnv"/>.</t>
<t>Section 4.1 of <xref target="RFC5050"/> 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.</t>
<t>IANA Registry policies and wording used in this document are described in <xref target="RFC5226"/>.</t>
</section>
<section title="Bundle Protocol">
  <t>The Bundle Protocol(BP)<xref target="RFC5050"/> has fields requiring a registry managed by IANA.</t>
  <section title="Bundle Block Types">
  <t>The Bundle Protocol has a Bundle Block Type code field <xref target="RFC5050">(section 4.5.2)</xref>. An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is:
    <list>
      <t>0-191: Specification Required</t>
      <t>192-255: Private or experimental use. No assignment by IANA.</t>
    </list>
    </t>
    <t>The Value range is: unsigned 8 bit integer.</t>
      <texttable>
        <preamble>Bundle Block Type Codes Registry</preamble>
      <ttcol align='right' width="20%">Value</ttcol>
      <ttcol align='left' width="50%">Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>0</c><c>Reserved</c><c>This document</c>
      <c>1</c><c>Bundle Payload Block</c><c><xref target="RFC5050"/></c>
      <c>2-191</c><c>Unassigned</c><c></c>
      <c>192-255</c><c>Private and/or experimental use</c><c><xref target="RFC5050"/></c>
    </texttable>
    <t>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.</t>
 </section>
  <section title="Primary Bundle Protocol Version">
  <t>The Bundle Protocol has a version field <xref target="RFC5050">(section 4.5.1)</xref>. An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is: RFC Required</t>
    <t>The Value range is: unsigned 8 bit integer.</t>
      <texttable>
        <preamble>Primary Bundle Protocol Version Registry</preamble>
      <ttcol align='right'>Value</ttcol>
      <ttcol align='left'>Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>0-5</c><c>Reserved</c><c>This document</c>
      <c>6</c><c>Assigned</c><c><xref target="RFC5050"/></c>
      <c>7-255</c><c>Unassigned</c><c></c>
    </texttable>
    <t>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.</t>
  </section>
 <section title="Bundle Processing Control Flags">
  <t>The Bundle Protocol has a Bundle Processing Control flags field <xref target="RFC5050">(section 4.2)</xref> encoded as an SDNV(<xref target="sdnv">see section </xref>). An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is: Specification Required</t>
    <t>The Value range is: Variable length. Maximum number of flag bit positions: 64</t>
      <texttable>
        <preamble>Bundle Processing Control Flags Registry</preamble>
      <ttcol align='right' width="20%">Bit Position (right to left)</ttcol>
      <ttcol align='left' width="50%">Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>0</c><c>Bundle is a fragment</c><c><xref target="RFC5050"/></c>
      <c>1</c><c>Application data unit is an administrative record</c><c><xref target="RFC5050"/></c>
      <c>2</c><c>Bundle must not be fragmented</c><c><xref target="RFC5050"/></c>
      <c>3</c><c>Custody transfer is requested</c><c><xref target="RFC5050"/></c>
      <c>4</c><c>Destination endpoint is a singleton</c><c><xref target="RFC5050"/></c>
      <c>5</c><c>Acknowledgement by application is requested</c><c><xref target="RFC5050"/></c>
      <c>6</c><c>Reserved</c><c><xref target="RFC5050"/></c>
      <c>7-8</c><c>Class of service: priority</c><c><xref target="RFC5050"/></c>
      <c>9-13</c><c>Class of service: reserved</c><c><xref target="RFC5050"/></c>
      <c>14</c><c>Request reporting of bundle reception</c><c><xref target="RFC5050"/></c>
      <c>15</c><c>Request reporting of custody acceptance</c><c><xref target="RFC5050"/></c>
      <c>16</c><c>Request reporting of bundle forwarding</c><c><xref target="RFC5050"/></c>
      <c>17</c><c>Request reporting of bundle delivery</c><c><xref target="RFC5050"/></c>
      <c>18</c><c>Request reporting of bundle deletion</c><c><xref target="RFC5050"/></c>
      <c>19</c><c>Reserved</c><c><xref target="RFC5050"/></c>
      <c>20</c><c>Reserved</c><c><xref target="RFC5050"/></c>
   </texttable>
  </section>
 <section title="Block Processing Control Flags">
  <t>The Bundle Protocol has a Block Processing Control flags field <xref target="RFC5050">(section 4.3)</xref>. An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is: Specification Required</t>
    <t>The Value range is: Variable length. Maximum number of flag bit positions: 64</t>
      <texttable>
        <preamble>Block Processing Control Flags Registry</preamble>
      <ttcol align='right'>Bit Position (right to left)</ttcol>
      <ttcol align='left'>Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>0</c><c>Block must be replicated in every fragment</c><c><xref target="RFC5050"/></c>
      <c>1</c><c>Transmit status report if block can't be processed</c><c><xref target="RFC5050"/></c>
      <c>2</c><c>Delete bundle if block can't be processed</c><c><xref target="RFC5050"/></c>
      <c>3</c><c>Last block</c><c><xref target="RFC5050"/></c>
      <c>4</c><c>Discard block if it can't be processed</c><c><xref target="RFC5050"/></c>
      <c>5</c><c>Block was forwarded without being processed</c><c><xref target="RFC5050"/></c>
      <c>6</c><c>Block contains an EID-reference field</c><c><xref target="RFC5050"/></c>
   </texttable>
  </section>
  <section title="Bundle Status Report Flags">
  <t>The Bundle Protocol has a Status Report Status Flag field<xref target="RFC5050">(section 6.1.1)</xref>. An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is: RFC Required</t>
    <t>The Value range is: 8 bits.</t>
     <texttable>
        <preamble>Bundle Status Report Flags Registry</preamble>
      <ttcol align='right'>Value</ttcol>
      <ttcol align='left'>Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>00000000</c><c>Reserved</c><c>This document</c>
      <c>00000001</c><c>Reporting node received bundle</c><c><xref target="RFC5050"/></c>
      <c>00000010</c><c>Reporting node accepted custody of bundle</c><c><xref target="RFC5050"/></c>
      <c>00000100</c><c>Reporting node forwarded the bundle</c><c><xref target="RFC5050"/></c>
      <c>00001000</c><c>Reporting node delivered the bundle</c><c><xref target="RFC5050"/></c>
      <c>00010000</c><c>Reporting node deleted the bundle</c><c><xref target="RFC5050"/></c>
      <c>00100000</c><c>Unassigned</c><c></c>
      <c>01000000</c><c>Unassigned</c><c></c>
      <c>10000000</c><c>Unassigned</c><c></c>
    </texttable>
    <t>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.</t>
  </section>
  <section title="Bundle Status Report Reason Codes">
  <t>The Bundle Protocol has a Bundle Status Report Reason Codes field<xref target="RFC5050">(section 6.1.1)</xref>. An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is: Specification Required</t>
    <t>The Value range is: unsigned 8 bit integer.</t>
     <texttable>
        <preamble>Bundle Status Report Reason Codes Registry</preamble>
      <ttcol align='right'>Value</ttcol>
      <ttcol align='left'>Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>0</c><c>No additional information</c><c><xref target="RFC5050"/></c>
      <c>1</c><c>Lifetime expired</c><c><xref target="RFC5050"/></c>
      <c>2</c><c>Forwarded over unidirectional link</c><c><xref target="RFC5050"/></c>
      <c>3</c><c>Transmission canceled</c><c><xref target="RFC5050"/></c>
      <c>4</c><c>Depleted storage</c><c><xref target="RFC5050"/></c>
      <c>5</c><c>Destination endpoint ID unintelligible</c><c><xref target="RFC5050"/></c>
      <c>6</c><c>No known route to destination from here</c><c><xref target="RFC5050"/></c>
      <c>7</c><c>No timely contact with next node on route</c><c><xref target="RFC5050"/></c>
      <c>8</c><c>Block unintelligible</c><c><xref target="RFC5050"/></c>
      <c>9-254</c><c>Unassigned</c><c></c>
      <c>255</c><c>Reserved</c><c>This document</c>
    </texttable>
    <t>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.</t>
  </section>
  <section title="Bundle Custody Signal Reason Codes">
  <t>The Bundle Protocol has a Bundle Custody Signal Reason Codes field<xref target="RFC5050">(section 6.1.2)</xref>. An IANA registry shall be setup as follows.</t>
    <t>The registration policy for this registry is: Specification Required</t>
    <t>The Value range is: unsigned 7 bit integer.</t>
     <texttable>
        <preamble>Bundle Custody Signal Reason Codes Registry</preamble>
      <ttcol align='right' width="20%">Value</ttcol>
      <ttcol align='left' width="60%">Description</ttcol>
      <ttcol align='left'>Reference</ttcol>
      <c>0</c><c>No additional information</c><c><xref target="RFC5050"/></c>
      <c>1-2</c><c>Unassigned</c><c></c>
      <c>3</c><c>Redundant reception (reception by a node that is a custodial node for this bundle)</c><c><xref target="RFC5050"/></c>
      <c>4</c><c>Depleted storage</c><c><xref target="RFC5050"/></c>
      <c>5</c><c>Destination endpoint ID unintelligible</c><c><xref target="RFC5050"/></c>
      <c>6</c><c>No known route to destination from here</c><c><xref target="RFC5050"/></c>
      <c>7</c><c>No timely contact with next node on route</c><c><xref target="RFC5050"/></c>
      <c>8</c><c>Block unintelligible</c><c><xref target="RFC5050"/></c>
      <c>9-126</c><c>Unassigned</c><c></c>
      <c>127</c><c>Reserved</c><c>This document</c>
    </texttable>
    <t>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.</t>
  </section>
</section>
<section title="Security Considerations">
<t>This document requests the creation of registries managed by IANA. There is no security issues involved. Refer to Security Considerations of the referenced protocols.</t>
</section>
<section title="IANA Considerations">
      <t>
IANA is requested to create the registries as described in the previous sections.  </t>
</section>
<section title="Acknowledgements">
 <t>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.</t>
</section>
  </middle>
  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.4838" ?>
      <?rfc include="reference.RFC.5050" ?>
      <?rfc include="reference.RFC.5226" ?>
      <?rfc include="reference.RFC.5326" ?>
    </references>
    <references title="Informative References">
      <?rfc include="reference.I-D.irtf-dtnrg-sdnv" ?>
    </references>
  </back>
</rfc>