Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-06.txt

神明達哉 <jinmei@wide.ad.jp> Mon, 30 June 2014 18:04 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F06B1A03D0 for <dhcwg@ietfa.amsl.com>; Mon, 30 Jun 2014 11:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 6U_L_m2ZxV7d for <dhcwg@ietfa.amsl.com>; Mon, 30 Jun 2014 11:04:21 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 080111A03E5 for <dhcwg@ietf.org>; Mon, 30 Jun 2014 11:04:18 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b13so8472097wgh.23 for <dhcwg@ietf.org>; Mon, 30 Jun 2014 11:04:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=peQOc+Byk+DvvdJo+5pXt6KFrVcw6C7Mmxcn29Gm+Gg=; b=0BQ+Nel6S5hWha4Ubn4nVaplSmbCDy82Moc0OHu4wwpDoO+ZXxY0UJ4SNnNPnJBh2g FrJ6iXEUEaN/FDWBIkZ0QZVH32mfY/Hja5PkrXXqSPNXFDBOkqghzhSdUXTT9lyovFSM mj16BKuVdzbbGyTd+RfWc1TVtmn0o+X85JtEsvNhK1bF3MN4jV5H7wh38XK4LEj+dtkX ChXmWSfmO275xeEywhwHYOb9T5A34oKT8lwjEPVuNgTQ4YehoRdnTwvyt9DhcccVBrVJ NuG2SyAAcLQoFxrwEifBR1J5mJ+A5+XmD/O3C2reXyIRLWzLLGB1plm6bG0M0QAre0pZ PF5Q==
MIME-Version: 1.0
X-Received: by 10.194.89.138 with SMTP id bo10mr6391212wjb.22.1404151457472; Mon, 30 Jun 2014 11:04:17 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.222.7 with HTTP; Mon, 30 Jun 2014 11:04:17 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B5E03D1@xmb-rcd-x04.cisco.com>
References: <20140630163351.4191.69719.idtracker@ietfa.amsl.com> <489D13FBFA9B3E41812EA89F188F018E1B5E03D1@xmb-rcd-x04.cisco.com>
Date: Mon, 30 Jun 2014 11:04:17 -0700
X-Google-Sender-Auth: pTsJihUD47Zqg3-TnHmsXDSKVKk
Message-ID: <CAJE_bqfZV+BCFR4u3W8O6X4oamZbeNQLSOJotyhbB2gBbXh03Q@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/4os387fT50jLJs7fsb3-AI_mrCc
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 18:04:27 -0000

At Mon, 30 Jun 2014 16:55:59 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> A new version of this document has been posted. Sorry for the long
> delay but there were some significant changes to make and thanks to
> Marcin for joining the authors to make some of those changes.

I've just made a quick scan of the 06 version.  I'm going to take a
closer look at it later, but please let me check one high level thing
first, based on my own comments on the previous version:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15284.html

Can I assume that this draft tries to provide a generalized specification
for all current and possible IA_xx, even if the original motivation
was (in my understanding from the previous discussion) to clarify the
usage of IA_NA and IA_PA in the same DHCPv6 session?  And, if so, does
it try to provide a well-defined specification for the usage with
IA_TA and other IA_xx's?

The overall tone of the new version from a quick read seemed to
suggest that the answer is "yes" to both questions, but in some
specific cases the draft still seems to focus on /assume specific
usage (not just as an example).  Also, as for IA_TA, the 4th paragraph
of Section 1, especially its second sentence, could read as if IA_TA
is an out of scope of this specification:

   [...] IA_TA also has limited value when DHCPv6 is used for address
   assignment, as the privacy issues identified for IPv6 stateless
   address assignment ([RFC4941]) do not apply to DHCPv6 assignments.

If the intent is to also cover the usage of IA_TA, I don't see the
need for this sentence in the context of this document.

I'd like to be sure about the author's intent of these, as that would
affect how I should read the draft and possibly make comments on it.

--
JINMEI, Tatuya