Re: [v6ops] Fwd: New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt

Nick Hilliard <nick@foobar.org> Tue, 18 July 2017 14:00 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30BB112785F for <v6ops@ietfa.amsl.com>; Tue, 18 Jul 2017 07:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dwsdbjpY5sM for <v6ops@ietfa.amsl.com>; Tue, 18 Jul 2017 07:00:04 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35D65129B15 for <v6ops@ietf.org>; Tue, 18 Jul 2017 07:00:03 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v6IDxw1K026307 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jul 2017 14:59:58 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <596E145C.8010603@foobar.org>
Date: Tue, 18 Jul 2017 14:59:56 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.15 (Macintosh/20170609)
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
CC: "v6ops-chairs@tools.ietf.org Chairs" <v6ops-chairs@tools.ietf.org>, IPv6 Operations <v6ops@ietf.org>
References: <596CF817.8040900@foobar.org> <CAKD1Yr3VP5u65gjwLNXw+DYkTbx-oy1jLz0JLrOX9kFR_41m+w@mail.gmail.com> <596D2D2D.5080406@foobar.org> <CAKD1Yr04hDJHvg1mvW3L3k6d3=USo8Wgk+Xv4P7hSA8dMGGZyQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr04hDJHvg1mvW3L3k6d3=USo8Wgk+Xv4P7hSA8dMGGZyQ@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Dy8PP_pt3W0mtt7njbbQrMfg59U>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Tue, 18 Jul 2017 14:00:11 -0000

Lorenzo Colitti wrote:
> If you read the discussion threads carefully, you'll see that the main
> issue being raised in that version of the draft (mostly by Philip and
> Gert, as I recall) was not "IA_NA should be used", but "DHCPv6 PD is not
> the only way to assign a prefix, and not a widely adopted way". -05
> addressed that issue by de-emphasizing DHCPv6 PD. As I read it, at the
> time there was pretty broad agreement at the time that IA_NA was not a
> good choice both because it is limited in terms of the number of total
> addresses that can be assigned and because it requires that the client
> send explicit requests, which has the problems listed in section 4.

I don't expect you to agree with the opinions expressed in
draft-hilliard-v6ops-host-addr-update.  To requote Gert:

> I missed that this was intended for BCP, otherwise I would have complained
> earlier.  Haven't seen anyone state that they are deploying DHCPv6-PD to
> hosts except you, so "CP" is really questionable... 
> 
> For an "Lorenzo does not like DHCPv6 IA_NA" draft, Informational sounds 
> about right.

However, there is no basis for you to assert that there was broad
agreement that IA_NA was a bad choice, and less still to codify that
into a statement which, in your opinion, creates an IETF recommendation
not to use DHCPv6 IA_NA.

Nick