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

神明達哉 <jinmei@wide.ad.jp> Wed, 09 July 2014 16:38 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 C2D4D1A020B for <dhcwg@ietfa.amsl.com>; Wed, 9 Jul 2014 09:38:54 -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 sIotVBFMjaym for <dhcwg@ietfa.amsl.com>; Wed, 9 Jul 2014 09:38:53 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DB2A1A0067 for <dhcwg@ietf.org>; Wed, 9 Jul 2014 09:38:53 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id cc10so3108446wib.12 for <dhcwg@ietf.org>; Wed, 09 Jul 2014 09:38:52 -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:content-transfer-encoding; bh=2AP4LQj0innJuMRtseUSxu7mNW9LB/EYDeGq0j4ZJNQ=; b=cvmewkU23v4Me3x7aM60iFFPLkWhi7OL/etEidLmASaA8DDqugh7XoIkblgts7Gb2v AjLKdXDx7dgYNX9dxZdVMdMfk1mm6GEJNGWW/AXSCvSwQSchFbL3G0lhY0oPcD8kg5qO TWN0sAxKLhFzzwFjxwQseP9psLmi7S6dFgTaw1Ov2q1C+pzvYoSTDMK2TdST6yFL73G5 vc6zEUvcwBQBRMbfvErKOwI0T/nfe+MaOuPFR+4aYCD/8OUmTlUvBXDFeImqAm6eciFa QfF/Rd1jd7CHl2v93IOQaI81ml5d11+EclKcJHENqxVdq+AIkx9smW8UICwt1IvuetZ0 DHVA==
MIME-Version: 1.0
X-Received: by 10.180.80.70 with SMTP id p6mr13042737wix.22.1404923932312; Wed, 09 Jul 2014 09:38:52 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.63.211 with HTTP; Wed, 9 Jul 2014 09:38:52 -0700 (PDT)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B5E170B@xmb-rcd-x04.cisco.com>
References: <20140630163351.4191.69719.idtracker@ietfa.amsl.com> <489D13FBFA9B3E41812EA89F188F018E1B5E03D1@xmb-rcd-x04.cisco.com> <CAJE_bqfZV+BCFR4u3W8O6X4oamZbeNQLSOJotyhbB2gBbXh03Q@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B5E170B@xmb-rcd-x04.cisco.com>
Date: Wed, 09 Jul 2014 09:38:52 -0700
X-Google-Sender-Auth: LyZXQ3HP4uhYGK5K7e-EzITLsZ0
Message-ID: <CAJE_bqdqj1MauRQ5m1s7wkv-6hqusdFg+vZe8n9FvsVDEeeDdQ@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/Jx7gLF5KiP-4AFYIoLUHR_yiHGA
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: Wed, 09 Jul 2014 16:38:54 -0000

At Mon, 30 Jun 2014 18:19:37 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> But because we're making changes to the specifications (i.e., revised sections of 3315, 3633, and even in some cases providing text for possible use in the 3315bis work), we are indeed trying to cover all IA_* options (while we hope it includes future possible IA_* options, that is more difficult to achieve as we don't know what those might be).
>
> >Can I assume that this draft tries to provide a generalized specification for all current and possible IA_xx
[...]
> Bottom line is that yes we are trying to accommodate all (existing) IA_* types. And, in general we've assumed that 3315 has handled IA_NA/IA_TA co-existence sufficiently, so the revised text focuses on included IA_PD handling.

The nuance is subtle here, so please let me be sure: which one is
(more) correct?
1. this draft excludes the applicability to future possible IA_XXs
   (i.e., it only covers IA_NA, IA_TA, and IA_PD, and the main
   motivation is the concurrent use of IA_NA and IA_PD).
2. this draft intends to be applicable to future possible IA_XXs,
   even if this is currently just a hope (since we don't know the
   future possibilities right now) and may turn out to be infeasible.

My initial interpretation was #2.  Am I correct?

--
JINMEI, Tatuya