IPv6 ND RIO Flags IANA considerations
draft-templin-6man-ndrioiana-01.txt

Abstract

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.

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 https://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 November 11, 2018.

Copyright Notice

Copyright (c) 2018 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 (https://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. RIO Flags
• 3. Updates to RFC4191
• 4. IANA Considerations
• 5. Security Considerations
• 6. Acknowledgements
• 7. References
• 7.1. Normative References
• 7.2. Informative References
• Author's Address

1. Introduction

The Route Information Option (RIO) [RFC4191] in IPv6 Neighbor Discovery (IPv6ND) messages [RFC4861][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.

2. RIO Flags

       0 1 2 3 4 5 6 7
      +-+-+-+-+-+-+-+-+
      |S|Res|Prf|Resvd|
      +-+-+-+-+-+-+-+-+

The IPv6 ND RIO specified in [RFC4191] and as updated by [I-D.templin-6man-rio-redirect] contains the following 8-bit flag field format:[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.

Future use of bits that are currently reserved must be coordinated to avoid conflicts.

3. Updates to RFC4191

This document updates [RFC4191] to include the new IANA Considerations text specified below.

4. IANA Considerations

The IANA is requested to create a new registry for IPv6 ND RIO flags. This should include the following initial values:

       +---------------+---------------------------------+-----------+
       | 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] |
       +---------------+---------------------------------+-----------+

(Where Reference [1] is [I-D.templin-6man-rio-redirect]).

The assignment of new flags in the RIO flags field require Standards Action or IESG Approval [RFC8126].

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

5. Security Considerations

TBD.

6. Acknowledgements

The IANA considerations in this document parallel those discussed for IPv6ND Prefix Information Options (PIOs) in [I-D.troan-6man-ndpioiana].

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

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

This work is aligned with the Boeing Information Technology (BIT) MobileNet program and the Boeing Research & Technology (BR&T) enterprise autonomy program.

7. References

7.1. Normative References

7.2. Informative References

Author's Address