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

"Bernie Volz (volz)" <volz@cisco.com> Wed, 09 July 2014 17:07 UTC

Return-Path: <volz@cisco.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 4673F1A0174 for <dhcwg@ietfa.amsl.com>; Wed, 9 Jul 2014 10:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.852
X-Spam-Level:
X-Spam-Status: No, score=-14.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 QMdzF8VxkU5p for <dhcwg@ietfa.amsl.com>; Wed, 9 Jul 2014 10:07:42 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C081E1A020B for <dhcwg@ietf.org>; Wed, 9 Jul 2014 10:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3450; q=dns/txt; s=iport; t=1404925684; x=1406135284; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=idCti/pBjXLA3XQvwtxsSbXz1U/fg5iscFLZzRYQnAY=; b=UEGFwxvMKOjECfXN/+PRzRw+y8mvQ7VjhisuGbBmCLGglFFtXUF7qdEb 2Fds+cNLDV2SuvoXhx2ywkXtYgRTyIknfuPgvRoHF+wwBXxfPY9cNMKMO X/Pd/eKNxsKqYWCflcoZbpt0x6OCACEab0jOc1iKwObijgT/Y8TCtk+Qd k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAJd1vVOtJA2B/2dsb2JhbABZgw6BLIJvw3IBGXcWdYQDAQEBAwEjEUUFBwQCAQgRBAEBAwIGHQMCAgIfERQBCAgCBA4FCIgmAwkIrnmSdQ2HAReBLItsgXkWEAsHBoJxNoEWBZh2j3iGFINDgjA
X-IronPort-AV: E=Sophos;i="5.01,632,1400025600"; d="scan'208";a="59496928"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-3.cisco.com with ESMTP; 09 Jul 2014 17:08:03 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s69H7fJA022424 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Jul 2014 17:07:41 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.176]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Wed, 9 Jul 2014 12:07:40 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: 神明達哉 <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-06.txt
Thread-Index: AQHPlIEus6CA5H78HkuHLmw+Sv8Eh5uJ3xfAgABnIoD//6zhMIAOYD0A//+yLrA=
Date: Wed, 09 Jul 2014 17:07:40 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B5EE425@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> <CAJE_bqdqj1MauRQ5m1s7wkv-6hqusdFg+vZe8n9FvsVDEeeDdQ@mail.gmail.com>
In-Reply-To: <CAJE_bqdqj1MauRQ5m1s7wkv-6hqusdFg+vZe8n9FvsVDEeeDdQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.44.70.117]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ZoMkL05Pk5CO2Z-E2TcAv-xLlrA
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 17:07:43 -0000

Hi Jinmei:

Yes, #2 is our hope.

--

It occurs to me that if this as this is the intent, we might want to discuss whether to add a new "OPTION_T1T2" (or some other name). Reasons would be:
1. It would be a good way for servers to know if the client has been uplifted as including this option code in the ORO would tell the server that.
2. Servers would return the T1/T2 for all (renewable) bindings in this option (as well as setting these values in the existing IA_NA/IA_PD options - servers COULD set these fields to 0 in the IA_NA/IA_PD option if returning the option as requested by the client).
3. Clients would know if the server was uplifted (if it returned this option).
4. It would remove the need for these fields in any future IA_* type options.

I think this idea was raised by someone else (Marcin?) at one time (though that may not have been on the list).

- Bernie

-----Original Message-----
From: jinmei.tatuya@gmail.com [mailto:jinmei.tatuya@gmail.com] On Behalf Of ????
Sent: Wednesday, July 09, 2014 12:39 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-06.txt

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