IPv6 Router Advertisement Prefix Information Option eXclusive Flag
draft-pioxfolks-6man-pio-exclusive-bit-02

Document Type Active Internet-Draft (individual)
Last updated 2017-03-28
Stream (None)
Intended RFC status (None)
Formats plain text xml 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 Engineering Task Force                                 E. Kline
Internet-Draft                                           Google Japan KK
Updates: 4861,6275 (if approved)                          M. Abrahamsson
Intended status: Experimental                           T-Systems Nordic
Expires: September 28, 2017                               March 27, 2017

   IPv6 Router Advertisement Prefix Information Option eXclusive Flag
               draft-pioxfolks-6man-pio-exclusive-bit-02

Abstract

   This document defines a new control bit in the IPv6 RA PIO flags
   octet that indicates that the node receiving this RA is the exclusive
   receiver of all traffic destined to any address within that prefix.

   Termed the eXclusive flag (or "X flag"), nodes that recognize this
   can perform some optimizations to save time and traffic (e.g. disable
   ND and DAD for addresses within this prefix) and more immediately
   pursue the benefits of being provided multiple addresses (vis.
   [RFC7934] section 3).  Additionally, network infrastructure nodes
   (routers, switches) can benefit by minimizing the number of {link
   layer, IP} address pairs required to offer network connectivity (vis.
   [RFC7934] section 9.3).

   Use of the X flag is backward compatible with existing IPv6 standards
   compliant implementations.

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 September 28, 2017.

Copyright Notice

Kline & Abrahamsson    Expires September 28, 2017               [Page 1]
Internet-Draft         IPv6 RA PIO eXclusive Flag             March 2017

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Efficiency improvements . . . . . . . . . . . . . . . . .   4
     2.2.  New architectural possibilities . . . . . . . . . . . . .   4
   3.  Applicability statement . . . . . . . . . . . . . . . . . . .   5
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Requirements Language . . . . . . . . . . . . . . . . . .   6
     4.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.1.  PIO-X . . . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.2.  PIO-X RA  . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.3.  Host  . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Updated Prefix Information Option . . . . . . . . . . . . . .   6
     5.1.  Updated format description  . . . . . . . . . . . . . . .   6
     5.2.  Receiver processing . . . . . . . . . . . . . . . . . . .   7
       5.2.1.  PIO R flag  . . . . . . . . . . . . . . . . . . . . .   7
       5.2.2.  (Re)Interpretation of other flags . . . . . . . . . .   7
         5.2.2.1.  PIO L flag  . . . . . . . . . . . . . . . . . . .   8
         5.2.2.2.  PIO A flag  . . . . . . . . . . . . . . . . . . .   8
     5.3.  Sender requirements . . . . . . . . . . . . . . . . . . .   8
     5.4.  Comparison with DHCPv6 PD . . . . . . . . . . . . . . . .   9
   6.  Host behavior . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  PIO-X processing  . . . . . . . . . . . . . . . . . . . .   9
     6.2.  Neighbor Discovery implications . . . . . . . . . . . . .   9
       6.2.1.  Duplicate Address Detection (DAD) . . . . . . . . . .   9
       6.2.2.  Router Solicitations (RSes) . . . . . . . . . . . . .  10
     6.3.  Link-local address behavior . . . . . . . . . . . . . . .  10
Show full document text