Updates to Requirements for IPv6 Options
draft-herbert-ipv6-update-opts-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-14
Replaces draft-herbert-ipv6-update-dest-ops
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                               Tom Herbert
Intended Status: Standard                                     Quantonium
Expires: March 10, 2019                                                 
                                                                        
                                                      September 14, 2018

                Updates to Requirements for IPv6 Options
                   draft-herbert-ipv6-update-opts-00

Abstract

   This document updates requirements for IPv6 Destination and Hop-by-
   Hop Options. The requirements that option type and option length
   cannot change en route, as well as the requirements that options
   cannot be added or removed, are made explicit. The meaning and
   requirements of a Destination Option marked as changeable are
   clarified. Finally, the requirement that all destinations listed in a
   Routing header must process options in a Destination Options header
   preceding the Routing header is relaxed.

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/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors. All rights reserved.

 

Herbert                   Expires March, 2019                   [Page 1]
INTERNET DRAFT     draft-herbert-ipv6-update-opts-00  September 14, 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2  Requirements for adding, removing, or changing options  . . . .  4
   3  Requirements for changeable Destination Options . . . . . . . .  4
   4  Requirements for processing Destination Options . . . . . . . .  5
   5  Detecting that Destination Options precede a Routing header . .  5
   6  Security Considerations . . . . . . . . . . . . . . . . . . . .  6
   7  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  6
   8  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     8.1  Normative References  . . . . . . . . . . . . . . . . . . .  6
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  6

 

Herbert                   Expires March, 2019                   [Page 2]
INTERNET DRAFT     draft-herbert-ipv6-update-opts-00  September 14, 2018

1  Introduction

   [RFC8200] defines Hop-by-Hop and Destination Options. This document
   clarifies requirements for changing, adding, or removing options in a
   packet en route to its final destination. It also relaxes the
   requirement that Destination Options preceding a Routing header must
   be processed by all destinations listed in the Routing header. 

   [RFC8200] specifies that "The third-highest-order bit of the Option
   Type specifies whether or not the Option Data of that option can
   change en route to the packet's final destination." It is implicit in
   this requirement that neither the Option Type nor Option Data Length
   can change en route to the packet's destination. It also follows that
   options cannot be added or removed while a packet is en route. This
   document makes these requirements explicit.

   Per [RFC8200], Destination Options may be marked as changeable (the
   third-highest-order bit of the Option Type for the Destination Option
   is set). [RFC8200] also states that with the exception of Hop-by-Hop
   options, extension headers are not processed except by the
   destination node. It follows that the only possible case that a
   Destination Option may be modified en route is by a node that is one
Show full document text