Re: New Version Notification for draft-pioxfolks-6man-pio-exclusive-bit-00.txt

Which specific network is this draft planning to be deployed in and how
many hosts does the network have?

It's a stretch to say traffic is saved if ND and DAD are disabled.
Usually, a DAD probe is sent once by an interface.  ND performs NUD at the
rate of one NS message per sec.   MLD reports are sent every few secs or
thereabouts.

I am also not convinced of the scan attack in section 9.3 or RFC7934 since
RPF can catch if the attack packet source fails RPF.  Routers have a robust
punt path to which too many address resolutions are rate limited.  I agree
the rate limit is not fair, but at least the router does not crash,  Also,
one can use DHCPv6 Leasequery to validate an DHCPv6-assigned address or an
IPv6 PD.   A DAD Proxy on the router can also validate a specific
destination.

I will read rest of the draft and get back.

Regards,

Hemant

On Fri, Sep 16, 2016 at 5:29 AM, Erik Kline <ek@google.com> wrote:

> A new version of I-D, draft-pioxfolks-6man-pio-exclusive-bit-00.txt
> has been successfully submitted by Erik Kline and posted to the
> IETF repository.
>
> Name:           draft-pioxfolks-6man-pio-exclusive-bit
> Revision:       00
> Title:          IPv6 Router Advertisement Prefix Information Option
> Exclusive Bit
> Document date:  2016-09-16
> Group:          Individual Submission
> Pages:          13
> URL:
> https://www.ietf.org/internet-drafts/draft-pioxfolks-6man-
> pio-exclusive-bit-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-pioxfolks-6man-pio-exclusive-bit/
> Htmlized:
> https://tools.ietf.org/html/draft-pioxfolks-6man-pio-exclusive-bit-00
>
>
> 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 bit (or "X bit"), nodes that recognize this can
>    perform some traffic-saving optimizations (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 bit is backward compatible with existing IPv6 standards
>    compliant implementations.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>