[v6ops] Suresh Krishnan's Discuss on draft-ietf-v6ops-unique-ipv6-prefix-per-host-07: (with DISCUSS and COMMENT)

Suresh Krishnan <suresh.krishnan@gmail.com> Wed, 16 August 2017 22:54 UTC

Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 20ACA126DD9; Wed, 16 Aug 2017 15:54:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh.krishnan@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-unique-ipv6-prefix-per-host@ietf.org, Ron Bonica <rbonica@juniper.net>, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org, v6ops-chairs@ietf.org, rbonica@juniper.net, v6ops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150292405512.12308.10034157849517158179.idtracker@ietfa.amsl.com>
Date: Wed, 16 Aug 2017 15:54:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9MMK7S5b7v90XtmszxWS5SS_TTs>
Subject: [v6ops] Suresh Krishnan's Discuss on draft-ietf-v6ops-unique-ipv6-prefix-per-host-07: (with DISCUSS and COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Aug 2017 22:54:15 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-v6ops-unique-ipv6-prefix-per-host-07: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

* Section 4

It is not clear what you intend here

"IPv6 Router Advertisement Interval = 300s"

The router advertisement interval is not configured as an absolute value but as
minimum and maximum bounds (MinRtrAdvInterval and MaxRtrAdvInterval) which are
used to calculate the actual advertisement interval. When the RA is sent from
an interface, the actual interval is an uniformly distributed random value
between the MinRtrAdvInterval and MaxRtrAdvInterval. At the very minimum you
need to clarify if you would like to have this as a lower bound or as an upper
bound.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

* Section 4

-> I think text is needed here to handle the case where the DNS server is
provided in the RA itself  (RFC8106)

"In addition it will use stateless DHCPv6 to get the IPv6 address of the DNS
server"

-> I am not sure what is the motivation for this text.

"however it SHOULD NOT use stateful DHCPv6 to receive a service provider
managed IPv6 address"

-> This text seems incorrect

"due to the L-bit set, it SHOULD send this traffic to the First Hop Provider
Router"

I think it should be the exact opposite. i.e. say *unset* instead of set

"due to the L-bit being unset, it SHOULD send this traffic to the First Hop
Provider Router"