<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict='yes'?>
<?rfc iprnotified='no'?>
<rfc category="std" docName="draft-templin-6man-ndrioiana-01.txt"
     ipr="trust200902" updates="RFC4191">
  <front>
    <title abbrev="Prefix Delegation for Hosts">IPv6 ND RIO Flags IANA
    considerations</title>

    <author fullname="Fred L. Templin" initials="F. L." role="editor"
            surname="Templin">
      <organization>Boeing Research &amp; Technology</organization>

      <address>
        <postal>
          <street>P.O. Box 3707</street>

          <city>Seattle</city>

          <region>WA</region>

          <code>98124</code>

          <country>USA</country>
        </postal>

        <email>fltemplin@acm.org</email>
      </address>
    </author>

    <date day="10" month="May" year="2018"/>

    <keyword>I-D</keyword>

    <keyword>Internet-Draft</keyword>

    <abstract>
      <t>The IPv6 Neighbor Discovery (IPv6ND) Route Information Option (RIO)
      defines an 8-bit flags field. This document requests IANA to create a
      new registry for managing RIO flag assignments.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>The Route Information Option (RIO) <xref target="RFC4191"/> in IPv6
      Neighbor Discovery (IPv6ND) messages <xref target="RFC4861"/><xref
      target="RFC8200"/> defines an 8-bit flag field, but there are currently
      no guidelines for assignments. The purpose of this document is to
      request IANA to create a new registry for the RIO flags to avoid
      potential conflicts.</t>
    </section>

    <section anchor="rio" title="RIO Flags">
      <t>The IPv6 ND RIO specified in <xref target="RFC4191"/> and as updated
      by <xref target="I-D.templin-6man-rio-redirect"/> contains the following
      8-bit flag field format:<figure>
          <artwork><![CDATA[       0 1 2 3 4 5 6 7
      +-+-+-+-+-+-+-+-+
      |S|Res|Prf|Resvd|
      +-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>In this field, bit 0 is the "Solicited (S)" flag <xref
      target="I-D.templin-6man-rio-redirect"/>, bits 3-4 encode a 2-bit Route
      Preference codepoint, and the remaining bits are reserved for future
      use.</t>

      <t>Future use of bits that are currently reserved must be coordinated to
      avoid conflicts.</t>
    </section>

    <section anchor="updates" title="Updates to RFC4191">
      <t>This document updates <xref target="RFC4191"/> to include the new
      IANA Considerations text specified below.</t>
    </section>

    <section anchor="iana" title="IANA Considerations">
      <t>The IANA is requested to create a new registry for IPv6 ND RIO flags.
      This should include the following initial values:</t>

      <t><figure>
          <artwork><![CDATA[
       +---------------+---------------------------------+-----------+
       | RIO Flag Bits | Description                     | Reference |
       +---------------+---------------------------------+-----------+
       | 0             | S - Solicited Flag              | [1]       |
       | 1-2           | Reserved                        | [RFC4191] |
       | 3-4           | Prf - a 2-bit Route Preference  | [RFC4191] |
       | 5-7           | Reserved                        | [RFC4191] |
       +---------------+---------------------------------+-----------+
]]></artwork>
        </figure></t>

      <t>(Where Reference [1] is <xref
      target="I-D.templin-6man-rio-redirect"/>).</t>

      <t>The assignment of new flags in the RIO flags field require Standards
      Action or IESG Approval <xref target="RFC8126"/>.</t>

      <t>The registry for these flags should be added to:
      http://www.iana.org/assignments/icmpv6-parameters</t>
    </section>

    <section anchor="secure" title="Security Considerations">
      <t>TBD.</t>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t>The IANA considerations in this document parallel those discussed for
      IPv6ND Prefix Information Options (PIOs) in <xref
      target="I-D.troan-6man-ndpioiana"/>.</t>

      <t>This work is aligned with the NASA Safe Autonomous Systems Operation
      (SASO) program under NASA contract number NNA16BD84C.</t>

      <t>This work is aligned with the FAA as per the SE2025 contract number
      DTFAWA-15-D-00030.</t>

      <t>This work is aligned with the Boeing Information Technology (BIT)
      MobileNet program and the Boeing Research &amp; Technology (BR&amp;T)
      enterprise autonomy program.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc ?>

      <?rfc include="reference.RFC.8200"?>

      <?rfc include="reference.RFC.8126"?>

      <?rfc ?>

      <?rfc ?>

      <?rfc include="reference.RFC.4191"?>

      <?rfc include="reference.RFC.4861"?>

      <?rfc ?>
    </references>

    <references title="Informative References">
      <?rfc include="reference.I-D.templin-6man-rio-redirect"?>

      <?rfc include="reference.I-D.troan-6man-ndpioiana"?>
    </references>
  </back>
</rfc>
