
From nobody Mon Feb  2 09:48:46 2015
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 5D0281A8828 for <dhcwg@ietfa.amsl.com>; Mon,  2 Feb 2015 09:48:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.921
X-Spam-Level: 
X-Spam-Status: No, score=0.921 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 wa4fneJkR-gf for <dhcwg@ietfa.amsl.com>; Mon,  2 Feb 2015 09:48:41 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 038CE1A87EC for <dhcwg@ietf.org>; Mon,  2 Feb 2015 09:48:41 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id w55so35143449wes.5 for <dhcwg@ietf.org>; Mon, 02 Feb 2015 09:48:39 -0800 (PST)
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=88QJ793Epwu2KqbGfKloh9vRmDg9qrG/ZLBUKYzludU=; b=PRQPPE9lUqph3wR7ZR6cpNP9K8RtlJbC+VHGPTxey144DcZ+z/gVOvSAgMpeOZyQen 6VuyEBd1aSMB4mN1gfuwMCG3IYsOA5VtRpvFzxxCciAgK3Xuv8/REdKqheZZkRRx3v14 Qr4gQWnmTqKuoXi6VJXsskl8ty/eH8/NJmQR+44RfYl7I65wGz3KV/lMxFGnvMbD0JIn BDbj8V4sJNm/8jUUbr21WSxzbs2/EMgM4M7DSsg0kV/E4om3pPP9wwAKlx2SR1QoDSZH EadQyNRYm8IzjvI32G40VAXz3KKpDDpZz1szbAJ2dqW74boxPpX5IOcoKKFBHQV4rVDW ACxA==
MIME-Version: 1.0
X-Received: by 10.194.242.6 with SMTP id wm6mr46888950wjc.7.1422899319772; Mon, 02 Feb 2015 09:48:39 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.44.66 with HTTP; Mon, 2 Feb 2015 09:48:39 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com>
Date: Mon, 2 Feb 2015 09:48:39 -0800
X-Google-Sender-Auth: L3U291oRaSUsGyfs3GwHXis9_MA
Message-ID: <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <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/zm0EFDX2ENTikoS-7Jz4G_8_gOk>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 02 Feb 2015 17:48:42 -0000

At Fri, 30 Jan 2015 20:03:28 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> For those that are interested in the issues raised and resolution, please=
 see the attached PDF (of the Google docs spreadsheet Marcin and I used to =
record the issues and determine our actions). Note: If the PDF fails to mak=
e it through, I will send an update with a URL (once I find a good place to=
 put it).
>
> Please review this updated version to assure you are happy with it.

(resnding the same content that I sent to the authors offlist)

I've only checked the updates related to my previous comments; I've
not read the entire text.

#53: it's not clear why my comment was rejected, and the revised
     abstract still seems to be awkward/not so helpful for first time
     or potential readers.  But it looks like I've been failing to
     persuading the authors on this point, so I won't insist on it
     anymore.
#54: likewise.  the justification still looks weak to me (note that
     I'm not opposed to the choice itself, even if it's just a matter
     of preference).  But I won't insist.
#55: it's not clear why it's rejected.
#56 and #57: does this mean we defer the fix to dhcpv6bis even if the
     points are deemed to be an issue?  If so, I don't think it a good
     idea especially now that I understand the intent of this work is
     to publish it as a standalone RFC.

--
JINMEI, Tatuya


From nobody Wed Feb  4 07:26:04 2015
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 EDB5F1A8A90 for <dhcwg@ietfa.amsl.com>; Wed,  4 Feb 2015 07:26:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 gwXqWj8_5CMZ for <dhcwg@ietfa.amsl.com>; Wed,  4 Feb 2015 07:26:00 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F5FB1A8A99 for <dhcwg@ietf.org>; Wed,  4 Feb 2015 07:25:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4134; q=dns/txt; s=iport; t=1423063561; x=1424273161; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tjWs5cm8CC9WgrYyYIWE/RziNiY4AUy/Dh8LI5o8q5o=; b=P+CTTU16N6ukhlSHjU14T2bVJ3Y+c5tvDSum7upkV9XxLQO8bX0X2mf5 yf55tYjnLGfYbl8+RB6T0R1eSpF9Kf75kfps4gt/ZxETKkk7smWYQelv7 WkSdayGPz9udqVrSzwHZNxgrsfkziBFSUD+Jq7TgkCv8oHW7RtHUj16cl M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqwFANs50lStJA2E/2dsb2JhbABagwaBKwSCfcUtAhx8QwEBAQEBfYQMAQEBAwEjEUUFBwQCAQgRBAEBAwIGHQMCAgIfERQBCAgBAQQBDQUIiBEDCQjAL5BiDYVrAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EhjC2BRzIWEAsHBoJiLoETAQSEFop6hzAzgl2DA4JGhUk9hX0iggIcgVBvgUR+AQEB
X-IronPort-AV: E=Sophos;i="5.09,518,1418083200"; d="scan'208";a="390257263"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-1.cisco.com with ESMTP; 04 Feb 2015 15:25:42 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t14FPea5002044 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Feb 2015 15:25:40 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.220]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Wed, 4 Feb 2015 09:25:40 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Ted Lemon (Ted.Lemon@nominum.com)" <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikA=
Date: Wed, 4 Feb 2015 15:25:40 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com>
In-Reply-To: <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.243.76]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/mcb6xiNhb6XT_wvxej98Z79HzK0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 04 Feb 2015 15:26:03 -0000

SmlubWVpOg0KDQpSZWdhcmRpbmcgIzUzLCB3ZSB0b29rIFRlZCdzIHN1Z2dlc3RlZCByZS13cml0
ZSBvZiB0aGUgQWJzdHJhY3QsIHNvIHBlcmhhcHMgaWYgeW91IHdhbnQgdG8gaGF2ZSB0aGlzIGNo
YW5nZWQsIHlvdSBjYW4gd29yayBzb21ldGhpbmcgb3V0IHdpdGggVGVkICh5b3UgZGlkIHNheSB5
b3Ugd29uJ3QgaW5zaXN0LCBzbyB3ZSB3aWxsIGxlYXZlIGl0IHRvIHlvdSB0byBmb2xsb3cgdXAg
d2l0aCBUZWQgaWYgeW91IHdhbnQgdG8pLiBUaGlzIGlzIG9uZSBpc3N1ZSB3aXRoIG11bHRpcGxl
IHJldmlld2VycyBwcm92aWRpbmcgY29uZmxpY3RpbmcgY2hhbmdlcy4NCg0KUmVnYXJkaW5nICM1
NCwgd2UgZmVlbCB0aGF0IHRoZSB0ZXh0IGlzIE9LIGFzIGlzLiBJZiB5b3Ugd2FudCB0byBmb2xs
b3cgdXAsIHBsZWFzZSBzdWdnZXN0IGV4cGxpY2l0bHkgd2hhdCB5b3Ugd2FudCB0aGUgdGV4dCB0
byByZWFkIGFuZCB3ZSBjYW4gcmVjb25zaWRlci4NCg0KUmVnYXJkaW5nICM1NSwgYWdhaW4sIHdl
IGZlZWwgdGhhdCB0aGUgY2hhbmdlcyBpbiB0b3RhbCBhcmUgc3VmZmljaWVudCByZWdhcmRpbmcg
dGhpcyBhbmQgZnVydGhlciBjbGFyaWZpY2F0aW9uIGlzIG5vdCByZXF1aXJlZC4NCg0KUmVnYXJk
aW5nICM1NiAmIDU3IC0gV2hpbGUgdGhlIGRyYWZ0IGlzIHRpdGxlZCAic3RhdGVmdWwgaXNzdWVz
IiwgaXQgaXMgbm90IGRlc2lnbmVkIHRvIGNvdmVyIGFsbCBzdGF0ZWZ1bCBpc3N1ZXMgKHRoaXMg
aXMganVzdCBhIHNob3J0IG5hbWUgYW5kIGdpdmVuIGV2ZXJ5dGhpbmcgd2Uga25vdyB0b2RheSwg
YSBkaWZmZXJlbnQgdGl0bGUgd291bGQgbGlrZWx5IGhhdmUgYmVlbiBiZXR0ZXIpLiBJbiB0aGlz
IHdvcmssIHdlIGFyZSBqdXN0IHRyeWluZyB0byBhZGRyZXNzIHRoZSBDUEUgSUFfTkEvSUFfUEQg
aXNzdWVzLiBTbywgaWYgdGhlIHByb2JsZW0gaXNuJ3Qgc3BlY2lmaWMgdG8gdGhhdCBjYXNlLCB3
ZSB3YW50IHRvIGRlZmVyIGFsbCBvdGhlciBpc3N1ZXMgdG8gdGhlIERIQ1B2NmJpcyB3b3JrLiBX
ZSBuZWVkIHRvIGRyYXcgdGhlIGxpbmUgc29tZXdoZXJlLCBvdGhlcndpc2Ugd2UgY291bGQgY29u
dGludWUgdGhpcyBwYXJ0aWN1bGFyIGRyYWZ0ICJmb3JldmVyIi4gSWYgeW91IGRvIGZlZWwgc3Ry
b25nbHkgdGhhdCB0aGVzZSBpc3N1ZXMgZGVzZXJ2ZSBtb3JlIHByb21wdCBhdHRlbnRpb24gdGhh
biB0aGUgREhDUHY2YmlzIGVmZm9ydCwgcGVyaGFwcyB5b3UgYXJlIHdpbGxpbmcgdG8gc3RhcnQg
YW5vdGhlciBkb2N1bWVudCB0byBhZGRyZXNzIHRoZXNlIChhbmQgcGVyaGFwcykgb3RoZXIgaXNz
dWVzLg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogamlu
bWVpLnRhdHV5YUBnbWFpbC5jb20gW21haWx0bzpqaW5tZWkudGF0dXlhQGdtYWlsLmNvbV0gT24g
QmVoYWxmIE9mID8/Pz8NClNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMDIsIDIwMTUgMTI6NDkgUE0N
ClRvOiBCZXJuaWUgVm9seiAodm9seikNCkNjOiBkaGN3Z0BpZXRmLm9yZw0KU3ViamVjdDogUmU6
IFtkaGN3Z10gZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXN0YXRlZnVsLWlzc3Vlcy0xMC50eHQNCg0K
QXQgRnJpLCAzMCBKYW4gMjAxNSAyMDowMzoyOCArMDAwMCwNCiJCZXJuaWUgVm9seiAodm9seiki
IDx2b2x6QGNpc2NvLmNvbT4gd3JvdGU6DQoNCj4gRm9yIHRob3NlIHRoYXQgYXJlIGludGVyZXN0
ZWQgaW4gdGhlIGlzc3VlcyByYWlzZWQgYW5kIHJlc29sdXRpb24sIHBsZWFzZSBzZWUgdGhlIGF0
dGFjaGVkIFBERiAob2YgdGhlIEdvb2dsZSBkb2NzIHNwcmVhZHNoZWV0IE1hcmNpbiBhbmQgSSB1
c2VkIHRvIHJlY29yZCB0aGUgaXNzdWVzIGFuZCBkZXRlcm1pbmUgb3VyIGFjdGlvbnMpLiBOb3Rl
OiBJZiB0aGUgUERGIGZhaWxzIHRvIG1ha2UgaXQgdGhyb3VnaCwgSSB3aWxsIHNlbmQgYW4gdXBk
YXRlIHdpdGggYSBVUkwgKG9uY2UgSSBmaW5kIGEgZ29vZCBwbGFjZSB0byBwdXQgaXQpLg0KPg0K
PiBQbGVhc2UgcmV2aWV3IHRoaXMgdXBkYXRlZCB2ZXJzaW9uIHRvIGFzc3VyZSB5b3UgYXJlIGhh
cHB5IHdpdGggaXQuDQoNCihyZXNuZGluZyB0aGUgc2FtZSBjb250ZW50IHRoYXQgSSBzZW50IHRv
IHRoZSBhdXRob3JzIG9mZmxpc3QpDQoNCkkndmUgb25seSBjaGVja2VkIHRoZSB1cGRhdGVzIHJl
bGF0ZWQgdG8gbXkgcHJldmlvdXMgY29tbWVudHM7IEkndmUgbm90IHJlYWQgdGhlIGVudGlyZSB0
ZXh0Lg0KDQojNTM6IGl0J3Mgbm90IGNsZWFyIHdoeSBteSBjb21tZW50IHdhcyByZWplY3RlZCwg
YW5kIHRoZSByZXZpc2VkDQogICAgIGFic3RyYWN0IHN0aWxsIHNlZW1zIHRvIGJlIGF3a3dhcmQv
bm90IHNvIGhlbHBmdWwgZm9yIGZpcnN0IHRpbWUNCiAgICAgb3IgcG90ZW50aWFsIHJlYWRlcnMu
ICBCdXQgaXQgbG9va3MgbGlrZSBJJ3ZlIGJlZW4gZmFpbGluZyB0bw0KICAgICBwZXJzdWFkaW5n
IHRoZSBhdXRob3JzIG9uIHRoaXMgcG9pbnQsIHNvIEkgd29uJ3QgaW5zaXN0IG9uIGl0DQogICAg
IGFueW1vcmUuDQojNTQ6IGxpa2V3aXNlLiAgdGhlIGp1c3RpZmljYXRpb24gc3RpbGwgbG9va3Mg
d2VhayB0byBtZSAobm90ZSB0aGF0DQogICAgIEknbSBub3Qgb3Bwb3NlZCB0byB0aGUgY2hvaWNl
IGl0c2VsZiwgZXZlbiBpZiBpdCdzIGp1c3QgYSBtYXR0ZXINCiAgICAgb2YgcHJlZmVyZW5jZSku
ICBCdXQgSSB3b24ndCBpbnNpc3QuDQojNTU6IGl0J3Mgbm90IGNsZWFyIHdoeSBpdCdzIHJlamVj
dGVkLg0KIzU2IGFuZCAjNTc6IGRvZXMgdGhpcyBtZWFuIHdlIGRlZmVyIHRoZSBmaXggdG8gZGhj
cHY2YmlzIGV2ZW4gaWYgdGhlDQogICAgIHBvaW50cyBhcmUgZGVlbWVkIHRvIGJlIGFuIGlzc3Vl
PyAgSWYgc28sIEkgZG9uJ3QgdGhpbmsgaXQgYSBnb29kDQogICAgIGlkZWEgZXNwZWNpYWxseSBu
b3cgdGhhdCBJIHVuZGVyc3RhbmQgdGhlIGludGVudCBvZiB0aGlzIHdvcmsgaXMNCiAgICAgdG8g
cHVibGlzaCBpdCBhcyBhIHN0YW5kYWxvbmUgUkZDLg0KDQotLQ0KSklOTUVJLCBUYXR1eWENCg==


From nobody Wed Feb  4 10:42:52 2015
Return-Path: <tomasz.mrugalski@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 DB2311A1AE3 for <dhcwg@ietfa.amsl.com>; Wed,  4 Feb 2015 10:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 kB2o7ML7t-Wj for <dhcwg@ietfa.amsl.com>; Wed,  4 Feb 2015 10:42:48 -0800 (PST)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC78F1A1A64 for <dhcwg@ietf.org>; Wed,  4 Feb 2015 10:42:47 -0800 (PST)
Received: by mail-wi0-f181.google.com with SMTP id fb4so5710028wid.2 for <dhcwg@ietf.org>; Wed, 04 Feb 2015 10:42:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=OgQknUtTYPeCR7ocAZ5USnhHMUP0OX5vqTYhYoDjtn0=; b=WnGAddwLs6K2/+5hPjV5sp5uxX+cE1xpMNCnqdqlvE9GAMZNNJvL3eXoqWEJ9y39/F NsTsXqcQEDpJnkDIdq0CuEg8B9Aa7YS8WMlVCtuSz5B3bCYg3fg9z0tEw8G5AjGFYrBi hWuIw/2kaWA5VqYnGVFRcNVsKnx2DRLeRwVtQWe/ABjL2cK4F8QeCRBgpN+KAkp8PKSh 6EbD5mmNYQTKjItqWerxdvkYacCA0b7kMgKbiPqezxd1FPOYH6NSiSzSQJLzHswSdnSL E6sAESzYTREjun8fmWfvoywvxPPDo5t8INj5dliU3tBN2OeVhQEY1kor/WsxBBREAghU MgKw==
X-Received: by 10.180.221.38 with SMTP id qb6mr7210325wic.73.1423075366456; Wed, 04 Feb 2015 10:42:46 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id fa3sm2212960wib.17.2015.02.04.10.42.45 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 10:42:45 -0800 (PST)
Message-ID: <54D26821.8010807@gmail.com>
Date: Wed, 04 Feb 2015 19:42:41 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1B7A8322@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B7A8322@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20150204194241543
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/TCSGOxF9FdJhY8cFzHroEdhWQgM>
Subject: Re: [dhcwg] IMPORTANT - IETF-92 (Dallas) DHC WG Session & Agenda Items
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, 04 Feb 2015 18:42:50 -0000

On 09.01.2015 16:46, Bernie Volz (volz) wrote:
Name of session: DHCP privacy update

Name of draft(s):
- draft-jiang-dhc-dhcp-privacy-00
- draft-krishnan-dhc-dhcpv6-privacy-00
- 2 additional mitigation drafts that will be published before Dallas

Time requested: 15-30mins
(depending on how much time we get, we may present only the major points
or go into more details, if time permits).

Presenter name(s): To be determined

> Brief description of what issues need discussing and what you hope to
> accomplish by presenting (please focus on open issues, rather than a
> status update):
Go through the issues identified in the privacy drafts, present
considered solutions and get feedback.

Tomek


From nobody Wed Feb  4 11:20:38 2015
Return-Path: <tomasz.mrugalski@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 2C70F1A1B72 for <dhcwg@ietfa.amsl.com>; Wed,  4 Feb 2015 11:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 JenxFVeJhHXq for <dhcwg@ietfa.amsl.com>; Wed,  4 Feb 2015 11:20:31 -0800 (PST)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84AB41A1B61 for <dhcwg@ietf.org>; Wed,  4 Feb 2015 11:20:31 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id h11so5934795wiw.1 for <dhcwg@ietf.org>; Wed, 04 Feb 2015 11:20:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rdu/sAVnmk6sV5WktZCjOj0Aq0ukZQM5cgbaThdkNDQ=; b=C8NUzaT5O6UQdEWiqnaOnVp27PoC9kcTkKSRAADxhoVnbVI1NcIZDqK3dpbqN+Z+Dd 6SFetbaKimFxlEi93eD5b79TuHDde/rBkkSYXieEAzWz34XlPfoj2f8ipHMrGKQLwA3y 4xroZMpu7mGLrYQR3TIUOncBNhIdsTfF7ynrvr190ZNltbzrtemdUKrDp+7Gcm3C9RRG edt4tFCcRNZ53ulyrfngMUqYSSPYDJykysgFrustyB2B8prxMzpSOkijhFUHOg8JYAgD LeymHPwIZMLUvgzsYoUJsbT5EdlLVWtYQYVllyBG3LLNbYvgasyWOF/Eg4hlKw96LKre 43Qg==
X-Received: by 10.180.184.132 with SMTP id eu4mr7374778wic.49.1423077630136; Wed, 04 Feb 2015 11:20:30 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id ev7sm3976953wjb.47.2015.02.04.11.20.28 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 11:20:29 -0800 (PST)
Message-ID: <54D270F8.4090300@gmail.com>
Date: Wed, 04 Feb 2015 20:20:24 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
References: <54932112.3080008@gmail.com>
In-Reply-To: <54932112.3080008@gmail.com>
X-TagToolbar-Keys: D20150204202024928
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/7yP7ZtQw652DcjI4oDcsaBDMObA>
Subject: [dhcwg] WGLC for draft-ietf-dhc-access-network-identifier-05 - Passed with issues
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, 04 Feb 2015 19:20:37 -0000

I just realized that the WGLC summary was discussed among chairs, but
never sent to the ML. Sorry about the delay.

The chairs have reviewed the feedback received for the
draft-ietf-dhc-access-network-identifier-05. The explicit feedback
received during the WGLC was disappointing. First and foremost, this
draft defines options that have nothing to do with DHCP. DHCP is merely
a delivery channel. Had there been another WG in IETF that could take
this work, it should have been done there. Unfortunately, there's no
appropriate group in IETF, so DHC had to take up this task. From this
perspective, it is understandable that there is minor interest, as the
DHCP community is not the primary user of those options.

Furthermore, this draft was presented in DHC meetings several times, it
never received any opposition and a small number of people expressed
support for it.

Finally, both chairs and the shepherd (Sheng agreed to take this role,
thanks!) reviewed this draft and didn't find anything particularly wrong
with it. A number of improvements are needed, but that is something that
can be easily fixed. Therefore we decided to consider this WGLC to pass
with issues. An updated revision addressing raised comments is needed.
We'll have another short WGLC for it, just to confirm that the issues
are indeed addressed.

Bernie volunteered to help addressing the issues. Thanks for doing this
effort!

Bernie & Tomek


From nobody Thu Feb  5 02:39:31 2015
Return-Path: <leaf.yeh.sdo@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 55D321A1AF1 for <dhcwg@ietfa.amsl.com>; Thu,  5 Feb 2015 02:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 dXA4ByE8fW9i for <dhcwg@ietfa.amsl.com>; Thu,  5 Feb 2015 02:39:14 -0800 (PST)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4D5D1A1AF8 for <dhcwg@ietf.org>; Thu,  5 Feb 2015 02:39:13 -0800 (PST)
Received: by mail-ie0-f178.google.com with SMTP id rd18so9050446iec.9 for <dhcwg@ietf.org>; Thu, 05 Feb 2015 02:39:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:thread-index:content-language; bh=AR51JN3RYKJBvZT+J3aYWIAOhPAwDQHMHItUkaspBkM=; b=kKJFt1K9WTRc37MmNtKmh+guyNP2JTv8mB3nWH8hzt1SoAXR28AlLICDaXbY91UzKQ vUbkdQEeQupON97Gnn7jD/CVZdElvMeffy/9MHSlZQNVWszb2i0jN5AsFX6iGL3i7eOe mdwjC0A7BJ3QCc3vjp6YS0MMB+Fa64qskvs4D8+/5/yweGooOMj7gbOCM1uoKY9QxYjM cJcKvd0Oolp124r5jbx9XybkErrHbvYVx25wWRiuvm2VjSBa2X5t7syN32SNh1yg8L8l +SRoMvLvipMOuQ4B1q3DytiOGGpckcCrBanuqCMCyV+thynCL4hfOexqDlN5yZPJHHwd r5Gw==
X-Received: by 10.42.33.66 with SMTP id h2mr6310512icd.7.1423132752964; Thu, 05 Feb 2015 02:39:12 -0800 (PST)
Received: from PC ([218.241.109.163]) by mx.google.com with ESMTPSA id s76sm2306924ioi.7.2015.02.05.02.39.10 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 05 Feb 2015 02:39:12 -0800 (PST)
Message-ID: <54d34850.cf886b0a.2b7a.7f16@mx.google.com>
X-Google-Original-Message-ID: <000c01d04130$11126c00$33374400$@yeh.sdo@gmail.com>
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7BE04B@xmb-rcd-x04.cisco.com> <54c1d125.431b6b0a.6596.0dac@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B7C05D4@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B7C05D4@xmb-rcd-x04.cisco.com>
Date: Thu, 5 Feb 2015 18:39:46 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01D04173.1F35AC00"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdA2cQ5NVqtoN7eTR0euEuM71YWMFgAUjJwAAAEt2rACl9FSgA==
Content-Language: zh-cn
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/lRpi44xMbwE_F0s9sOj0-Ldm2iY>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draft-krishnan-dhc-dhcpv6-privacy
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: Thu, 05 Feb 2015 10:39:20 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01D04173.1F35AC00
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Bernie - I believe these would be Informational as they will not propose
anything to implement. =A1=AD Other drafts being worked on will document =
how one
might mitigate some or all of these privacy concerns.

=20

I=A1=AEve read draft-krishnan-dhc-dhcpv6-privacy. Have we got any output =
on the
requirement for the DHCPv6 client implementation? Do we believe the DUID =
of
DHCPv6 client (or even IAID) should not be a permanent =
=A1=AEstable=A1=AF
identifier? and they should have no relation with the MAC address of the
client?

=20

=20

Best Regards,

Leaf

=20

=20

=20

From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: Friday, January 23, 2015 12:52 PM
To: Leaf Yeh; dhcwg@ietf.org
Subject: RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &
draft-krishnan-dhc-dhcpv6-privacy

=20

I believe these would be Informational as they will not propose anything =
to
implement.

=20

They presently are specified as being Standards Track =A8C we would =
probably
want to make sure they are adopted as Informational.

=20

Other drafts being worked on will document how one might mitigate some =
or
all of these privacy concerns.

=20

-          Bernie

=20

From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]=20
Sent: Thursday, January 22, 2015 11:43 PM
To: Bernie Volz (volz); dhcwg@ietf.org
Subject: RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &
draft-krishnan-dhc-dhcpv6-privacy

=20

Q: Will these 2 drafts be put into standard track?

=20

=20

Best Regards,

Leaf

=20

=20

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz =
(volz)
Sent: Friday, January 23, 2015 2:38 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &
draft-krishnan-dhc-dhcpv6-privacy

=20

Hello:

=20

During the Honolulu IETF-91 meeting, there was consensus to adopt the
following documents as working group items:

draft-jiang-dhc-dhcp-privacy-00  Privacy considerations for DHCP

draft-krishnan-dhc-dhcpv6-privacy-00      Privacy considerations for =
DHCPv6

=20

If you do NOT favor the adoption of one or both, please reply to this =
mail
and also state your objections. This adoption call will end on Feb 4, =
2015,
and unless we hear objections, these documents will be adopted.

=20

You may also indicate your support for adopting them, but because of the =
WG
meeting consensus, this is not necessary.

=20

The HTML version of the documents can be viewed at
http://tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00 and =
http://tools.
ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00.

=20

Thanks!

=20

- Tomek & Bernie

=20


------=_NextPart_000_000D_01D04173.1F35AC00
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"=B4=BF=CE=C4=B1=BE Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=C5=FA=D7=A2=BF=F2=CE=C4=B1=BE Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"=B4=BF=CE=C4=B1=BE Char";
	mso-style-priority:99;
	mso-style-link:=B4=BF=CE=C4=B1=BE;
	font-family:=CB=CE=CC=E5;}
span.Char0
	{mso-style-name:"=C5=FA=D7=A2=BF=F2=CE=C4=B1=BE Char";
	mso-style-priority:99;
	mso-style-link:=C5=FA=D7=A2=BF=F2=CE=C4=B1=BE;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:232813922;
	mso-list-type:hybrid;
	mso-list-template-ids:-586226994 -1403359754 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3633;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Bernie - I believe these would be =
Informational as they will not propose anything to implement. =A1=AD =
Other drafts being worked on will document how one might mitigate some =
or all of these privacy concerns.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>I=A1=AEve read =
draft-krishnan-dhc-dhcpv6-privacy. Have we got any output on the =
requirement for the DHCPv6 client implementation? Do we believe the DUID =
of DHCPv6 client (or even IAID) should not be a permanent =
=A1=AEstable=A1=AF identifier? and they should have no relation with the =
MAC address of the client?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bernie =
Volz (volz) [mailto:volz@cisco.com] <br><b>Sent:</b> Friday, January 23, =
2015 12:52 PM<br><b>To:</b> Leaf Yeh; dhcwg@ietf.org<br><b>Subject:</b> =
RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &amp; =
draft-krishnan-dhc-dhcpv6-privacy<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I believe =
these would be Informational as they will not propose anything to =
implement.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>They =
presently are specified as being Standards Track =A8C we would probably =
want to make sure they are adopted as =
Informational.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Other =
drafts being worked on will document how one might mitigate some or all =
of these privacy concerns.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Bernie<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Leaf Yeh =
[<a =
href=3D"mailto:leaf.yeh.sdo@gmail.com">mailto:leaf.yeh.sdo@gmail.com</a>]=
 <br><b>Sent:</b> Thursday, January 22, 2015 11:43 PM<br><b>To:</b> =
Bernie Volz (volz); <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br><b>Subject:</b> RE: =
[dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &amp; =
draft-krishnan-dhc-dhcpv6-privacy<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Q: Will these 2 drafts be put =
into standard track?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Best =
Regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'>Leaf<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:#1F497D'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> dhcwg [<a =
href=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Bernie Volz (volz)<br><b>Sent:</b> Friday, January =
23, 2015 2:38 AM<br><b>To:</b> <a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br><b>Subject:</b> =
[dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &amp; =
draft-krishnan-dhc-dhcpv6-privacy<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Hello:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>During the Honolulu IETF-91 =
meeting, there was consensus to adopt the following documents as working =
group items:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'text-indent:36.0pt'><span =
lang=3DEN-US>draft-jiang-dhc-dhcp-privacy-00&nbsp; Privacy =
considerations for DHCP<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'text-indent:36.0pt'><span =
lang=3DEN-US>draft-krishnan-dhc-dhcpv6-privacy-00&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Privacy considerations for DHCPv6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>If you do NOT favor the adoption =
of one or both, please reply to this mail and also state your =
objections. This adoption call will end on Feb 4, 2015, and unless we =
hear objections, these documents will be =
adopted.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>You may also indicate your support for adopting them, but =
because of the WG meeting consensus, this is not =
necessary.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>The HTML version of the documents can be viewed at <a =
href=3D"http://tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00">http:=
//tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00</a> and <a =
href=3D"http://tools.ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00">=
http://tools.ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00</a>.<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Thanks!<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>- Tomek &amp; Bernie<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_000D_01D04173.1F35AC00--


From nobody Thu Feb  5 04:03:09 2015
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 4D4EB1A1BA0 for <dhcwg@ietfa.amsl.com>; Thu,  5 Feb 2015 04:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 2-QWKUqafPS0 for <dhcwg@ietfa.amsl.com>; Thu,  5 Feb 2015 04:03:06 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C7A31A1B93 for <dhcwg@ietf.org>; Thu,  5 Feb 2015 04:03:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17965; q=dns/txt; s=iport; t=1423137787; x=1424347387; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XlGWkB5VFp+VKxELbC1GC+L54KM8WTEWJrXxGiGdsiE=; b=V5Tk+1bfczaCBTfgJnGTFeWtIGPLd4AItaE3zFyd7auR8bGeb4AmuQ83 0aZVygGYze4G2MEJ9F65oQunHSrotWN/4OJVn2h9zndEqVBK7Mbky9Xih X93CAvv1xvX4inkNJ5QIp6sz+eu8iV0cnB9x5oFqAPEBE5bkK9m03MR74 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAGANZa01StJA2E/2dsb2JhbABagkNDUlnAYoFqhXECgSVDAQEBAQF9hAwBAQEELUUHEAIBCBEEAQEoByERFAkIAQEEDgWIGQMRDdAJDYVWAQEBAQEBAQEBAQEBAQEBAQEBAQEBF41OgVkBAU8GAYMWgRMFjTGBY4NQhBSBRoEXNoJNgkaGCoJCgz4iggIcFIE8bwGBCoE3AQEB
X-IronPort-AV: E=Sophos;i="5.09,523,1418083200";  d="scan'208,217";a="390548003"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-9.cisco.com with ESMTP; 05 Feb 2015 12:03:06 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t15C355F026939 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Feb 2015 12:03:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.220]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Thu, 5 Feb 2015 06:03:05 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Thread-Topic: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draft-krishnan-dhc-dhcpv6-privacy
Thread-Index: AdA2cQ5NVqtoN7eTR0euEuM71YWMFgAUjJwAAAEt2rACl9FSgAAFHTSJ
Date: Thu, 5 Feb 2015 12:03:04 +0000
Message-ID: <2E9867AA-37F8-44B9-AA48-61F720D67C06@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7BE04B@xmb-rcd-x04.cisco.com> <54c1d125.431b6b0a.6596.0dac@mx.google.com> <489D13FBFA9B3E41812EA89F188F018E1B7C05D4@xmb-rcd-x04.cisco.com>, <54d34850.cf886b0a.2b7a.7f16@mx.google.com>
In-Reply-To: <54d34850.cf886b0a.2b7a.7f16@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_2E9867AA37F844B9AA4861F720D67C06ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/g8JhvuWpW1QvjW1YIE6sXowVRPE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draft-krishnan-dhc-dhcpv6-privacy
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: Thu, 05 Feb 2015 12:03:08 -0000

--_000_2E9867AA37F844B9AA4861F720D67C06ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Yes, these documents will most likely end up as informational - this can be=
 fixed when published as wg docs.

- Bernie (from iPad)

On Feb 5, 2015, at 5:39 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com<mailto:leaf.ye=
h.sdo@gmail.com>> wrote:

Bernie - I believe these would be Informational as they will not propose an=
ything to implement. =85 Other drafts being worked on will document how one=
 might mitigate some or all of these privacy concerns.

I=91ve read draft-krishnan-dhc-dhcpv6-privacy. Have we got any output on th=
e requirement for the DHCPv6 client implementation? Do we believe the DUID =
of DHCPv6 client (or even IAID) should not be a permanent =91stable=92 iden=
tifier? and they should have no relation with the MAC address of the client=
?


Best Regards,
Leaf



From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, January 23, 2015 12:52 PM
To: Leaf Yeh; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draf=
t-krishnan-dhc-dhcpv6-privacy

I believe these would be Informational as they will not propose anything to=
 implement.

They presently are specified as being Standards Track =96 we would probably=
 want to make sure they are adopted as Informational.

Other drafts being worked on will document how one might mitigate some or a=
ll of these privacy concerns.


-          Bernie

From: Leaf Yeh [mailto:leaf.yeh.sdo@gmail.com]
Sent: Thursday, January 22, 2015 11:43 PM
To: Bernie Volz (volz); dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draf=
t-krishnan-dhc-dhcpv6-privacy

Q: Will these 2 drafts be put into standard track?


Best Regards,
Leaf


From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Friday, January 23, 2015 2:38 AM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draft-kr=
ishnan-dhc-dhcpv6-privacy


Hello:



During the Honolulu IETF-91 meeting, there was consensus to adopt the follo=
wing documents as working group items:

draft-jiang-dhc-dhcp-privacy-00  Privacy considerations for DHCP

draft-krishnan-dhc-dhcpv6-privacy-00      Privacy considerations for DHCPv6



If you do NOT favor the adoption of one or both, please reply to this mail =
and also state your objections. This adoption call will end on Feb 4, 2015,=
 and unless we hear objections, these documents will be adopted.



You may also indicate your support for adopting them, but because of the WG=
 meeting consensus, this is not necessary.



The HTML version of the documents can be viewed at http://tools.ietf.org/ht=
ml/draft-jiang-dhc-dhcp-privacy-00 and http://tools.ietf.org/html/draft-kri=
shnan-dhc-dhcpv6-privacy-00.



Thanks!



- Tomek & Bernie


--_000_2E9867AA37F844B9AA4861F720D67C06ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body dir=3D"auto">
<div>Yes, these documents will most likely end up as informational - this c=
an be fixed when published as wg docs.<br>
<br>
- Bernie (from iPad)</div>
<div><br>
On Feb 5, 2015, at 5:39 AM, Leaf Yeh &lt;<a href=3D"mailto:leaf.yeh.sdo@gma=
il.com">leaf.yeh.sdo@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:??;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@??";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"??? Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"????? Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"??? Char";
	mso-style-priority:99;
	mso-style-link:???;
	font-family:??;}
span.Char0
	{mso-style-name:"????? Char";
	mso-style-priority:99;
	mso-style-link:?????;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:232813922;
	mso-list-type:hybrid;
	mso-list-template-ids:-586226994 -1403359754 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3633;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Bernie =
- I believe these would be Informational as they will not propose anything =
to implement. =85 Other drafts being worked on will document how one might =
mitigate some or all of these privacy concerns.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">I=91ve read draft-krishnan-dhc-dhcpv6-privacy. Have we got any ou=
tput on the requirement for the DHCPv6 client implementation? Do we believe=
 the DUID of DHCPv6 client (or even IAID)
 should not be a permanent =91stable=92 identifier? and they should have no=
 relation with the MAC address of the client?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Best Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Leaf<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Bernie Volz (volz) [<a href=3D"mailto:volz@cisco.com"=
>mailto:volz@cisco.com</a>]
<br>
<b>Sent:</b> Friday, January 23, 2015 12:52 PM<br>
<b>To:</b> Leaf Yeh; <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><b=
r>
<b>Subject:</b> RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy=
 &amp; draft-krishnan-dhc-dhcpv6-privacy<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I belie=
ve these would be Informational as they will not propose anything to implem=
ent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">They pr=
esently are specified as being Standards Track =96 we would probably want t=
o make sure they are adopted as Informational.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Other d=
rafts being worked on will document how one might mitigate some or all of t=
hese privacy concerns.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><!--[if !supportLists]--><span lang=3D"EN-US" style=3D"color:#1F49=
7D"><span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times =
New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><!--[endif]--><span lang=3D"EN-US" style=3D"color:#1F4=
97D">Bernie<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Leaf Yeh [<a href=3D"mailto:leaf.yeh.sdo@gmail.com">m=
ailto:leaf.yeh.sdo@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, January 22, 2015 11:43 PM<br>
<b>To:</b> Bernie Volz (volz); <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf=
.org</a><br>
<b>Subject:</b> RE: [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy=
 &amp; draft-krishnan-dhc-dhcpv6-privacy<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Q: Will these 2 drafts be put into standard track?<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Best Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Leaf<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> dhcwg [<a href=3D"mailto:dhcwg-bounces@ietf.org">mail=
to:dhcwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Friday, January 23, 2015 2:38 AM<br>
<b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<b>Subject:</b> [dhcwg] WG Adoption Call - draft-jiang-dhc-dhcp-privacy &am=
p; draft-krishnan-dhc-dhcpv6-privacy<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Hello:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">During the Honolulu IETF-91 =
meeting, there was consensus to adopt the following documents as working gr=
oup items:<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"text-indent:36.0pt"><span lang=3D"EN-US"=
>draft-jiang-dhc-dhcp-privacy-00&nbsp; Privacy considerations for DHCP<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"text-indent:36.0pt"><span lang=3D"EN-US"=
>draft-krishnan-dhc-dhcpv6-privacy-00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Privacy=
 considerations for DHCPv6<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">If you do NOT favor the adop=
tion of one or both, please reply to this mail and also state your objectio=
ns. This adoption call will end on Feb 4, 2015, and unless we hear objectio=
ns, these documents will be adopted.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">You may also indicate your s=
upport for adopting them, but because of the WG meeting consensus, this is =
not necessary.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">The HTML version of the docu=
ments can be viewed at
<a href=3D"http://tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00">http=
://tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00</a> and
<a href=3D"http://tools.ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00"=
>http://tools.ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00</a>.<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Thanks!<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">- Tomek &amp; Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</blockquote>
</body>
</html>

--_000_2E9867AA37F844B9AA4861F720D67C06ciscocom_--


From nobody Thu Feb  5 04:18:55 2015
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 08BD81A8724 for <dhcwg@ietfa.amsl.com>; Thu,  5 Feb 2015 04:18:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 Ml1YIrcO31zj for <dhcwg@ietfa.amsl.com>; Thu,  5 Feb 2015 04:18:52 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28A0B1A8722 for <dhcwg@ietf.org>; Thu,  5 Feb 2015 04:18:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5568; q=dns/txt; s=iport; t=1423138732; x=1424348332; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=VbGFuHlB+n0akH6pOXV3TE606bwZ62liwdHt/fjeLIs=; b=TFiW235UKv5DDe4KYha4BuVVVBRe7QnXIDhvuC/3Tm9xqX2txWtvlDEy irJTxm+eD8LgVc33filDdVNy+Yf6ozntgqbJJvMYd2b1687l3pphZ0xPb JLVP4aCWLr1/DTwM/QnXlAOS7VIi21gI5gpTlbPPblyvyfukbfyE4mXe6 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AvBgCVXtNU/5ldJa1agkNDUlnAYoFqhXECgSVDAQEBAQF9hA0BAQQtXAIBRwcyFBECBBOILQ3VcwEBAQEBAQEBAQEBAQEBAQEBAQEBGI8nAQFWgxaBEwWNMYFjg1CFWoEXNoJNixKDPiKCMoE8b4ELgTcBAQE
X-IronPort-AV: E=Sophos;i="5.09,523,1418083200";  d="scan'208,217";a="120807785"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP; 05 Feb 2015 12:18:52 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t15CIpR6028870 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 5 Feb 2015 12:18:51 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.220]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Thu, 5 Feb 2015 06:18:51 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Results for WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draft-krishnan-dhc-dhcpv6-privacy
Thread-Index: AQHQQT3m7QQZzYo2ik+Cv/tvTv/CPg==
Date: Thu, 5 Feb 2015 12:18:50 +0000
Message-ID: <6D3AE30B-3681-4D06-ADE4-FBC0F6B4A3FF@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7BE04B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B7BE04B@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_6D3AE30B36814D06ADE4FBC0F6B4A3FFciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/AjdpvJtEd7qBdLLYUYsXGipMw7o>
Subject: [dhcwg] Results for WG Adoption Call - draft-jiang-dhc-dhcp-privacy & draft-krishnan-dhc-dhcpv6-privacy
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: Thu, 05 Feb 2015 12:18:54 -0000

--_000_6D3AE30B36814D06ADE4FBC0F6B4A3FFciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

The chairs have decided there is consenus to adopt this work.

The authors are requested to publish WG versions of these documents - pleas=
e also assure they are Informational and not Standards Track documents.

Thanks.

- Bernie (from iPad)

On Jan 22, 2015, at 1:37 PM, Bernie Volz (volz) <volz@cisco.com<mailto:volz=
@cisco.com>> wrote:


Hello:



During the Honolulu IETF-91 meeting, there was consensus to adopt the follo=
wing documents as working group items:

draft-jiang-dhc-dhcp-privacy-00  Privacy considerations for DHCP

draft-krishnan-dhc-dhcpv6-privacy-00      Privacy considerations for DHCPv6



If you do NOT favor the adoption of one or both, please reply to this mail =
and also state your objections. This adoption call will end on Feb 4, 2015,=
 and unless we hear objections, these documents will be adopted.



You may also indicate your support for adopting them, but because of the WG=
 meeting consensus, this is not necessary.



The HTML version of the documents can be viewed at http://tools.ietf.org/ht=
ml/draft-jiang-dhc-dhcp-privacy-00 and http://tools.ietf.org/html/draft-kri=
shnan-dhc-dhcpv6-privacy-00.



Thanks!



- Tomek & Bernie


--_000_6D3AE30B36814D06ADE4FBC0F6B4A3FFciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Hi:</div>
<div><br>
</div>
<div>The chairs have decided there is consenus to adopt this work.</div>
<div><br>
</div>
<div>The authors are requested to publish WG versions of these documents - =
please also assure they are Informational and not Standards Track documents=
.</div>
<div><br>
</div>
<div>Thanks.<br>
<br>
- Bernie (from iPad)</div>
<div><br>
On Jan 22, 2015, at 1:37 PM, Bernie Volz (volz) &lt;<a href=3D"mailto:volz@=
cisco.com">volz@cisco.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hello:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">During the Honolulu IETF-91 meeting, there was co=
nsensus to adopt the following documents as working group items:<o:p></o:p>=
</p>
<p class=3D"MsoPlainText" style=3D"text-indent:.5in">draft-jiang-dhc-dhcp-p=
rivacy-00&nbsp; Privacy considerations for DHCP<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"text-indent:.5in">draft-krishnan-dhc-dhc=
pv6-privacy-00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Privacy considerations for DHC=
Pv6<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">If you do NOT favor the adoption of one or both, =
please reply to this mail and also state your objections. This adoption cal=
l will end on Feb 4, 2015, and unless we hear objections, these documents w=
ill be adopted.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">You may also indicate your support for adopting t=
hem, but because of the WG meeting consensus, this is not necessary.<o:p></=
o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The HTML version of the documents can be viewed a=
t <a href=3D"http://tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00">
http://tools.ietf.org/html/draft-jiang-dhc-dhcp-privacy-00</a> and <a href=
=3D"http://tools.ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00">
http://tools.ietf.org/html/draft-krishnan-dhc-dhcpv6-privacy-00</a>.<o:p></=
o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks!<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</blockquote>
</body>
</html>

--_000_6D3AE30B36814D06ADE4FBC0F6B4A3FFciscocom_--


From nobody Thu Feb  5 19:16:22 2015
Return-Path: <internet-drafts@ietf.org>
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 856E31A040B; Thu,  5 Feb 2015 19:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 yb_bcshMd3_Z; Thu,  5 Feb 2015 19:16:10 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BD7481A0210; Thu,  5 Feb 2015 19:16:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150206031609.2019.69944.idtracker@ietfa.amsl.com>
Date: Thu, 05 Feb 2015 19:16:09 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/yc39VILzMl_2SgyBgkmGlTI46WU>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-access-network-identifier-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 06 Feb 2015 03:16:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Access Network Identifier Option in DHCP
        Authors         : Shwetha Bhandari
                          Sri Gundavelli
                          Mark Grayson
                          Bernie Volz
                          Jouni Korhonen
	Filename        : draft-ietf-dhc-access-network-identifier-06.txt
	Pages           : 19
	Date            : 2015-02-05

Abstract:
   This document specifies the format and mechanism that is to be used
   for encoding access network identifiers in DHCPv4 and DHCPv6 messages
   by defining new access network identifier options and sub-options.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-access-network-identifier/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-access-network-identifier-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-access-network-identifier-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Feb  6 10:35:17 2015
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 55B621A19E3 for <dhcwg@ietfa.amsl.com>; Fri,  6 Feb 2015 10:35:08 -0800 (PST)
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 Sk5VqrWP-Rpl for <dhcwg@ietfa.amsl.com>; Fri,  6 Feb 2015 10:35:07 -0800 (PST)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB01B1A1A3C for <dhcwg@ietf.org>; Fri,  6 Feb 2015 10:35:03 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id z12so15237599wgg.3 for <dhcwg@ietf.org>; Fri, 06 Feb 2015 10:35:02 -0800 (PST)
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=yI2oTByVUD+ac1GiaNlQ1G0tOyO/zpai8+tXddywpig=; b=qWOtFTxcF2MKnrfO84+g6xpJMAvZVXcqL3X/McJWQ73aQWAAL5jNsCdo0egmJgLsm1 Rrt2zdUJ031Zn+xLmjrdjTk56PO7WRJzxHHq+DwieVRYiMqPCuqt/755XSS9aDYVOrEB hGjalaTZL9i3tDJPUVuBgJzTswKlepNYIM+cJf7W9EUpBAyoVI6LjfMmHrzJ7f0tuBZB 8ciu2nRREi732DYUTnu2iuAbU2QSDSzXRe/zpxngH1WxgqYHUpLD0384266AHdDPMg7o GAzno9VSg47Ofo4ozsGcwhJ0w8l/C8nRdJEjX/Y9JFpj5lqNc0TM9pB3vePn513FGPEB exMQ==
MIME-Version: 1.0
X-Received: by 10.180.149.197 with SMTP id uc5mr6016520wib.80.1423247702682; Fri, 06 Feb 2015 10:35:02 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Fri, 6 Feb 2015 10:35:02 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com>
Date: Fri, 6 Feb 2015 10:35:02 -0800
X-Google-Sender-Auth: zOd3LijrqMeqlC8L6vydVEL0bIA
Message-ID: <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <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/vxZ_c7Q8ytBLKpI1kYDE9aUm5Uk>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Fri, 06 Feb 2015 18:35:08 -0000

At Wed, 4 Feb 2015 15:25:40 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> Regarding #56 & 57 - While the draft is titled "stateful issues", it
> is not designed to cover all stateful issues (this is just a short
> name and given everything we know today, a different title would
> likely have been better). In this work, we are just trying to
> address the CPE IA_NA/IA_PD issues. So, if the problem isn't
> specific to that case, we want to defer all other issues to the
> DHCPv6bis work.

Depending on the rationale for deferring specific points, I can live
with that.  But I'd at least like to understand why it's okay to
defer.  Regarding #56, or more specifically, on the following text of
stateful-issues-10:

     When the client receives a NotOnLink status from the server in
     response to a Request, the client can either re-issue the Request
     without specifying any addresses or restart the DHCP server
     discovery process (see section 17).

Specifically why is it okay to defer it?  Because a CPE-type client
isn't supposed to be a mobile device and is unlikely to get NotOnLink
(or for that matter it's even unlikely for the client to send Confirm
in the first place)?

What about #57?  I guess the relevant text in stateful-issues-10 is
now this one:

     If the client cannot operate without the addresses for the IAs for
     which it received the NoAddrsAvail status code, the client may try
     another server (perhaps by restarting the DHCP server discovery
     process).

Why can we dismiss it (in terms of #57)?  Perhaps because it's assumed
to be unlikely that the client (= CPE) gets a prefix but not an
address?

BTW: as for the title, I guess I previously suggested to rename it so
it matches what's actually described better, e.g, "Clarification on
Mixed Use of DHCPv6 Address Assignment and Prefix Delegation".  For
people discussing this drafts here (like you and me), this doesn't
matter much since we know all the history of how this document has
evolved into the current form.  But if we publish it as an RFC, it
will be more important to make it clearer and less confusing for
future readers who don't have the background context.  In that sense I
personally it's worth doing if we can find a better title, and I don't
think it's too late yet.

--
JINMEI, Tatuya


From nobody Fri Feb  6 12:13:32 2015
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 4CC501A1B25 for <dhcwg@ietfa.amsl.com>; Fri,  6 Feb 2015 12:13:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 ORBNhzFUrzu7 for <dhcwg@ietfa.amsl.com>; Fri,  6 Feb 2015 12:13:27 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FCBD1A0377 for <dhcwg@ietf.org>; Fri,  6 Feb 2015 12:13:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10360; q=dns/txt; s=iport; t=1423253607; x=1424463207; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=o4YP6MztVmdBIn48QV9i3lzWdHJZfP76gp4zS47aB0g=; b=ZP2/Ie6Fw6UVkz8aw76/VY1dU4DFgW6TX0yESNeL6vAN1Rv/NB+tOvKM KCvSYJ3d9PZaDm1B54x5IKFFj9fDOQAhnCW7yRgKPy+Lj14GJq30+IYFJ n3wh65/gcdTjDGcnTel2EZARMHgZbw8pKLyt6zYTN6Tl/jcpnZllaIUvt s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AgCACgH9VU/5hdJa1agwZSWoMBvX+BaoVxAoEZQwEBAQEBfYQNAQEEIQFXEAIBCCcYAgMCMhQRAQEEDgWILQ2iNZxnAZYYAQEBAQEBAQEBAQEBAQEBAQEBAQEBF494B4JlMYETBY03gWODUIVcgU2RHyKDbm+CQgEBAQ
X-IronPort-AV: E=Sophos;i="5.09,530,1418083200";  d="scan'208,217";a="121247523"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-8.cisco.com with ESMTP; 06 Feb 2015 20:13:26 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t16KDPeH028486 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Feb 2015 20:13:26 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.220]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Fri, 6 Feb 2015 14:13:25 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikAAeCiTAP//tueg
Date: Fri, 6 Feb 2015 20:13:25 +0000
Message-ID: <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com>, <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com>
In-Reply-To: <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_B57385A8AAAB46D9BE079B3BC4EC1129ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Nf24O1ROwsHGZz97C341XTiBP3Y>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Fri, 06 Feb 2015 20:13:30 -0000

--_000_B57385A8AAAB46D9BE079B3BC4EC1129ciscocom_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

Jinmei:

For #56, how is this text much different from what is in RFC 3315:

"When the client receives a NotOnLink status from the server in response to=
 a Request, the client can either re-issue the Request without specifying a=
ny addresses or restart the DHCP server discovery process (see section 17<h=
ttp://tools.ietf.org/html/rfc3315#section-17>)."

For #57, from 3315:


"When the client receives a NotOnLink status from the server in
   response to a Request, the client can either re-issue the Request
   without specifying any addresses or restart the DHCP server discovery
   process (see section 17<http://tools.ietf.org/html/rfc3315#section-17>).=
"



How is what we are saying any different? That is why this is a general RFC =
3315 issue and we drew the line not to address it in stateful issues. Again=
, this draft is to address a subset of the entire set of issues.


Feel free to start a new draft if you wish to start work on discussing thes=
e issues; we are planning to request adoption of the 3315bis work shortly, =
so that is another venue.


We will rediscuss title change.

- Bernie (from iPad)

On Feb 6, 2015, at 1:35 PM, =1B$B?@L@C#:H=1B(B <jinmei@wide.ad.jp<mailto:ji=
nmei@wide.ad.jp>> wrote:

At Wed, 4 Feb 2015 15:25:40 +0000,
"Bernie Volz (volz)" <volz@cisco.com<mailto:volz@cisco.com>> wrote:

Regarding #56 & 57 - While the draft is titled "stateful issues", it
is not designed to cover all stateful issues (this is just a short
name and given everything we know today, a different title would
likely have been better). In this work, we are just trying to
address the CPE IA_NA/IA_PD issues. So, if the problem isn't
specific to that case, we want to defer all other issues to the
DHCPv6bis work.

Depending on the rationale for deferring specific points, I can live
with that.  But I'd at least like to understand why it's okay to
defer.  Regarding #56, or more specifically, on the following text of
stateful-issues-10:

    When the client receives a NotOnLink status from the server in
    response to a Request, the client can either re-issue the Request
    without specifying any addresses or restart the DHCP server
    discovery process (see section 17).

Specifically why is it okay to defer it?  Because a CPE-type client
isn't supposed to be a mobile device and is unlikely to get NotOnLink
(or for that matter it's even unlikely for the client to send Confirm
in the first place)?

What about #57?  I guess the relevant text in stateful-issues-10 is
now this one:

    If the client cannot operate without the addresses for the IAs for
    which it received the NoAddrsAvail status code, the client may try
    another server (perhaps by restarting the DHCP server discovery
    process).

Why can we dismiss it (in terms of #57)?  Perhaps because it's assumed
to be unlikely that the client (=3D CPE) gets a prefix but not an
address?

BTW: as for the title, I guess I previously suggested to rename it so
it matches what's actually described better, e.g, "Clarification on
Mixed Use of DHCPv6 Address Assignment and Prefix Delegation".  For
people discussing this drafts here (like you and me), this doesn't
matter much since we know all the history of how this document has
evolved into the current form.  But if we publish it as an RFC, it
will be more important to make it clearer and less confusing for
future readers who don't have the background context.  In that sense I
personally it's worth doing if we can find a better title, and I don't
think it's too late yet.

--
JINMEI, Tatuya

--_000_B57385A8AAAB46D9BE079B3BC4EC1129ciscocom_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-2022-=
jp">
</head>
<body dir=3D"auto">
<div>Jinmei:</div>
<div><br>
</div>
<div>For #56, how is this text much different from what is in RFC 3315:</di=
v>
<div><span style=3D"background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
<div><span style=3D"background-color: rgba(255, 255, 255, 0);">&quot;When t=
he client receives a NotOnLink status from the server in response to a Requ=
est, the client can either re-issue the Request without specifying any addr=
esses or restart the DHCP server discovery
 process (see </span><a href=3D"http://tools.ietf.org/html/rfc3315#section-=
17" style=3D"background-color: rgba(255, 255, 255, 0);">section 17</a><span=
 style=3D"background-color: rgba(255, 255, 255, 0);">).&quot;</span></div>
<div><span style=3D"background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
<div>For #57, from 3315:</div>
<div><br>
</div>
<div>
<pre class=3D"newpage" style=3D"margin-top: 0px; margin-bottom: 0px; page-b=
reak-before: always;"><font color=3D"#000000" face=3D"UICTFontTextStyleBody=
"><span style=3D"white-space: normal; background-color: rgba(255, 255, 255,=
 0);">&quot;When the client receives a NotOnLink status from the server in
   response to a Request, the client can either re-issue the Request
   without specifying any addresses or restart the DHCP server discovery
   process (see <a href=3D"http://tools.ietf.org/html/rfc3315#section-17">s=
ection 17</a>).&quot;</span></font><span style=3D"font-size: 1em; -webkit-t=
ext-size-adjust: auto;">
</span></pre>
</div>
<div><br>
</div>
<div><br>
</div>
<div>How is what we are saying any different? That is why this is a general=
 RFC 3315 issue and we drew the line not to address it in stateful issues. =
Again, this draft is to address a subset of the entire set of issues.</div>
<div><br>
</div>
<div><br>
</div>
<div>Feel free to start a new draft if you wish to start work on discussing=
 these issues; we are planning to request adoption of the 3315bis work shor=
tly, so that is another venue.</div>
<div><br>
</div>
<div><br>
</div>
<div>We will rediscuss title change.</div>
<div><br>
- Bernie (from iPad)</div>
<div><br>
On Feb 6, 2015, at 1:35 PM, =1B$B?@L@C#:H=1B(B &lt;<a href=3D"mailto:jinmei=
@wide.ad.jp">jinmei@wide.ad.jp</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><span>At Wed, 4 Feb 2015 15:25:40 &#43;0000,</span><br>
<span>&quot;Bernie Volz (volz)&quot; &lt;<a href=3D"mailto:volz@cisco.com">=
volz@cisco.com</a>&gt; wrote:</span><br>
<span></span><br>
<blockquote type=3D"cite"><span>Regarding #56 &amp; 57 - While the draft is=
 titled &quot;stateful issues&quot;, it</span><br>
</blockquote>
<blockquote type=3D"cite"><span>is not designed to cover all stateful issue=
s (this is just a short</span><br>
</blockquote>
<blockquote type=3D"cite"><span>name and given everything we know today, a =
different title would</span><br>
</blockquote>
<blockquote type=3D"cite"><span>likely have been better). In this work, we =
are just trying to</span><br>
</blockquote>
<blockquote type=3D"cite"><span>address the CPE IA_NA/IA_PD issues. So, if =
the problem isn't</span><br>
</blockquote>
<blockquote type=3D"cite"><span>specific to that case, we want to defer all=
 other issues to the</span><br>
</blockquote>
<blockquote type=3D"cite"><span>DHCPv6bis work.</span><br>
</blockquote>
<span></span><br>
<span>Depending on the rationale for deferring specific points, I can live<=
/span><br>
<span>with that. &nbsp;But I'd at least like to understand why it's okay to=
</span><br>
<span>defer. &nbsp;Regarding #56, or more specifically, on the following te=
xt of</span><br>
<span>stateful-issues-10:</span><br>
<span></span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;When the client receives a NotOnLink status f=
rom the server in</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;response to a Request, the client can either =
re-issue the Request</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;without specifying any addresses or restart t=
he DHCP server</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;discovery process (see section 17).</span><br=
>
<span></span><br>
<span>Specifically why is it okay to defer it? &nbsp;Because a CPE-type cli=
ent</span><br>
<span>isn't supposed to be a mobile device and is unlikely to get NotOnLink=
</span><br>
<span>(or for that matter it's even unlikely for the client to send Confirm=
</span><br>
<span>in the first place)?</span><br>
<span></span><br>
<span>What about #57? &nbsp;I guess the relevant text in stateful-issues-10=
 is</span><br>
<span>now this one:</span><br>
<span></span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;If the client cannot operate without the addr=
esses for the IAs for</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;which it received the NoAddrsAvail status cod=
e, the client may try</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;another server (perhaps by restarting the DHC=
P server discovery</span><br>
<span>&nbsp;&nbsp;&nbsp;&nbsp;process).</span><br>
<span></span><br>
<span>Why can we dismiss it (in terms of #57)? &nbsp;Perhaps because it's a=
ssumed</span><br>
<span>to be unlikely that the client (=3D CPE) gets a prefix but not an</sp=
an><br>
<span>address?</span><br>
<span></span><br>
<span>BTW: as for the title, I guess I previously suggested to rename it so=
</span><br>
<span>it matches what's actually described better, e.g, &quot;Clarification=
 on</span><br>
<span>Mixed Use of DHCPv6 Address Assignment and Prefix Delegation&quot;. &=
nbsp;For</span><br>
<span>people discussing this drafts here (like you and me), this doesn't</s=
pan><br>
<span>matter much since we know all the history of how this document has</s=
pan><br>
<span>evolved into the current form. &nbsp;But if we publish it as an RFC, =
it</span><br>
<span>will be more important to make it clearer and less confusing for</spa=
n><br>
<span>future readers who don't have the background context. &nbsp;In that s=
ense I</span><br>
<span>personally it's worth doing if we can find a better title, and I don'=
t</span><br>
<span>think it's too late yet.</span><br>
<span></span><br>
<span>--</span><br>
<span>JINMEI, Tatuya</span><br>
</div>
</blockquote>
</body>
</html>

--_000_B57385A8AAAB46D9BE079B3BC4EC1129ciscocom_--


From nobody Sat Feb  7 13:32:08 2015
Return-Path: <mellon@fugue.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 2A8971A897D for <dhcwg@ietfa.amsl.com>; Sat,  7 Feb 2015 13:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level: 
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] 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 RclUFtCbrHAV for <dhcwg@ietfa.amsl.com>; Sat,  7 Feb 2015 13:32:04 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id E96051A8965 for <dhcwg@ietf.org>; Sat,  7 Feb 2015 13:32:03 -0800 (PST)
Received: from [172.19.131.139] (unknown [12.130.116.26]) by toccata.fugue.com (Postfix) with ESMTPSA id 3CDF52380CAC for <dhcwg@ietf.org>; Sat,  7 Feb 2015 16:32:00 -0500 (EST)
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com>
Date: Sat, 7 Feb 2015 15:31:47 -0600
To: dhcwg <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Oz1wlLVdIUpQ8WcE_g1-9Tfh4g4>
Subject: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Sat, 07 Feb 2015 21:32:07 -0000

The mechanisms defined in this draft seem okay, modulo the secdir review =
which may turn up things I would miss.   However, the use model =
described is completely wrong, and I can't publish the document until =
that's fixed.

The problem is that there are a number of statements in section 7 that =
are simply not factual, and are going to cause massive pushback if we =
submit it without fixing them.   I'll go through these in order.

>    Because         =20
>    the client may have to validate the authentication in the condition =
        =20
>    of without connectivity wider than link-local, authentication with  =
        =20
>    certificates may not always be feasible.

This statement doesn't make sense as written.   PKI certificate =
revocation can't be checked without network connectivity, but PKI =
certificates certainly can, if the DHCP client has a list of acceptable =
root certs and the server-supplied cert has a signature chain that =
validates.   And the client could check for certificate revocation =
before making the information received from the DHCP server available =
for general use.

So if there is a point to be made here, it must be something other than =
what the text actually says.   If the text can just be deleted, that =
would be fine, but if it can't, the WG needs to figure out what it's =
supposed to say.   It definitely doesn't make sense for it to say what =
it says.

>    So, this document only            =20
>    sticks on Leaf of Faith model, to make sure the client talks to the =
        =20
>    same previous server.

I realize that I am a repeat offender in the use of the term =
"leap-of-faith authentication," but the generally accepted term these =
days is Trust On First Use (TOFU).

>    Message integrity is provided.  But there is a chance for the =
client        =20
>    to incorrectly trust a malicious server at the beginning of the =
first       =20
>    session with the server (and therefore keep trusting it =
thereafter).        =20
>    But the leap of faith mechanim guarantees the subsequent messages =
are       =20
>    sent by the same previous server, and therefore narrows the attack  =
        =20
>    scope.

This is all fine.

>    This may make sense if the network can be reasonably                =
=20
>    considered secure and requesting pre-configuration is deemed to be  =
        =20
>    infeasible.  A small home network would be an example of such =
cases.=20

This is not.   The DHCP client has no way of knowing what kind of =
network it's connecting to on first use.   I think what you mean to say =
here is something like this:

    TOFU is a good model for connecting to networks the client does not =
recognize: if the network connection turns out to work, then remembering =
the successful authentication of the DHCP server for future uses of the =
network can prevent future attempts to attack clients on that network.

    When connecting to known networks, it may be desirable for the =
client to be pre-configured with a cert for DHCP servers on that =
network.   This can prevent attacks on first use of the network.   =
Examples of such networks can include the device owner's home network =
and networks operated by the device owner's employer.   However, in both =
cases the TOFU model still provides substantial protection from future =
attacks, as long as the validation occurs when no attack is in progress.

>                                                                        =
        =20
>    For environments that are neither controlled nor really =
trustworthy,        =20
>    such as a network in a cafeteria, while the leap of faith model,    =
        =20
>    i.e., silently trusting the server at the first time, would be too  =
        =20
>    insecure.  But some middle ground might be justified, such as       =
        =20
>    requiring human intervention at the point of the leap of faith.

This statement doesn't make any sense, again because the client has no =
way of knowing that it is attaching to such a network.

The real use model has to be one of the following:

- Automatic TOFU
- TOFU only when confirmed by the end user
- Pre-configured cert

I think of these three, automatic TOFU actually provides a great deal of =
security in all three scenarios and it is okay to say so.   TOFU =
confirmed by the end user may or may not be better: the risk you might =
be trying to mitigate here is connecting to an entirely untrustworthy =
network.   But it's not at all clear to me that asking the user to help =
in this case is a good strategy, because users are notoriously =
uneducated about security, and may make exactly the wrong decision when =
asked to confirm a cert.

The third model, pre-installed certs, makes sense in a number of cases: =
the corporate case, the large Wifi provider case (e.g., Boingo) and the =
secure homenet case (although the UI issues there could be ... =
interesting).

In the case of Boingo and the corporate use case, a PKI cert that could =
be trusted as a signer would actually be a really great idea.   =
Otherwise every DHCP server has to have the same cert, and that creates =
a bit of a security vulnerability: an attack on an unattended server in =
some cafe that provides, e.g., Boingo hotspot service, would compromise =
the entire network, not just the network in that cafe.   Very short key =
valid lifetimes could render stolen certs less useful.

I do not think the draft actually needs to go through all these use =
cases in detail, because they are purely speculative.   But I mention =
them here because I think there is a lack of clarity in this section =
which needs to be addressed, and talking about the possible use cases is =
a good way to address that problem.

>    As for authentication on a server, there are several different      =
        =20
>    scenarios to consider, each of which has different applicability    =
        =20
>    issues.  If the server allows the leap of faith model, any =
malicious        =20
>    user can pretend to be a new legitimate client.  While the server =
can       =20
>    always be considered to have connectivity to validate certificate, =
it       =20
>    is feasible to check client certificates.

This doesn't make any sense to me.   What's the threat model that makes =
TOFU useful?   I can't think of one.   It doesn't help against DoS =
attacks.   I suppose it prevents one client from taking another client's =
address, but I'm not sure that's worth the effort.   And why install a =
cert on a client?   What's the use case?

>    Network administrators may wish to constrain the allocation of      =
        =20
>    addresses to authorized hosts to avoid denial of service attacks in =
        =20
>    "hostile" environments where the network medium is not physically   =
        =20
>    secured, such as wireless networks or college residence halls.  A   =
        =20
>    server may have to selectively serve a specific client or deny      =
        =20
>    specific clients depending on the identity of the client in a       =
        =20
>    controlled environment, like a corporate intranet.  But the support =
        =20
>    from skilled staff or administrator may be required to set up the   =
        =20
>    clients.

This is not true.   The use model I would expect to see here is that the =
client generates a key, possibly one key per server for privacy reasons, =
and then just uses that.   If the client has to register somehow to use =
the key, then you'd send it to a captive portal for registration, and =
that would be how the key would get into the server's database.   =
Requiring the network administrator to install a key on the laptop is =
not only too much work, it's actually potentially dangerous, because the =
network administrator may not be trustworthy with respect to the =
contents of the device's memory.

If it were up to me, I would simply delete section 7, and all the =
references to it elsewhere in the document, and simply provide the =
mechanism without saying how to use it.   I know Jinmei wanted to talk =
about use cases, but I think it harms the draft to do so when we haven't =
really seen how people will choose to use it.

In section 8, there are further problems, but I don't think there's much =
point in talking about them until we've talked about this.


From nobody Sun Feb  8 17:57:50 2015
Return-Path: <jiangsheng@huawei.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 321E21A6F22 for <dhcwg@ietfa.amsl.com>; Sun,  8 Feb 2015 17:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 wC5wV6WLoWaG for <dhcwg@ietfa.amsl.com>; Sun,  8 Feb 2015 17:57:46 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFBAF1A1AFA for <dhcwg@ietf.org>; Sun,  8 Feb 2015 17:57:44 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPA76514; Mon, 09 Feb 2015 01:57:43 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Feb 2015 01:57:42 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.106]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Mon, 9 Feb 2015 09:57:36 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <mellon@fugue.com>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
Thread-Index: AQHQQx2McUj9f9+oTEe7lmci6/QZ1ZznjnZA
Date: Mon, 9 Feb 2015 01:57:34 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923B049397@nkgeml512-mbx.china.huawei.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com>
In-Reply-To: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/uZQe6ltW4QdD3-CVQDyrc_GfqqE>
Cc: "draft-ietf-dhc-sedhcpv6@tools.ietf.org" <draft-ietf-dhc-sedhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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, 09 Feb 2015 01:57:48 -0000

SGksIFRlZCwNCg0KVHdvIHF1aWNrIHJlc3BvbnNlcyBiZWxvdy4gSSB3aWxsIHRyeSB0byBnaXZl
IGFuIHVwZGF0ZSB0aGlzIHdlZWsgYWZ0ZXIgZGlzY3Vzc2lvbiB3aXRoIHlvdSBhbmQgY28tYXV0
aG9ycy4NCg0KPkkgcmVhbGl6ZSB0aGF0IEkgYW0gYSByZXBlYXQgb2ZmZW5kZXIgaW4gdGhlIHVz
ZSBvZiB0aGUgdGVybSAibGVhcC1vZi1mYWl0aA0KPmF1dGhlbnRpY2F0aW9uLCIgYnV0IHRoZSBn
ZW5lcmFsbHkgYWNjZXB0ZWQgdGVybSB0aGVzZSBkYXlzIGlzIFRydXN0IE9uIEZpcnN0DQo+VXNl
IChUT0ZVKS4NCg0KU28sIHNoYWxsIEkgcmVwbGFjZSAibGVhcCBvZiBmYWl0aCIgYnkgIlRydXN0
IE9uIEZpcnN0IFVzZSAoVE9GVSkiPyBJIGFtIGZpbmUgd2l0aCBpdC4gSnVzdCBuZWVkIGEgZG91
YmxlIGNvbmZpcm1hdGlvbi4NCg0KPklmIGl0IHdlcmUgdXAgdG8gbWUsIEkgd291bGQgc2ltcGx5
IGRlbGV0ZSBzZWN0aW9uIDcsIGFuZCBhbGwgdGhlIHJlZmVyZW5jZXMgdG8gaXQNCj5lbHNld2hl
cmUgaW4gdGhlIGRvY3VtZW50LCBhbmQgc2ltcGx5IHByb3ZpZGUgdGhlIG1lY2hhbmlzbSB3aXRo
b3V0IHNheWluZw0KPmhvdyB0byB1c2UgaXQuICAgSSBrbm93IEppbm1laSB3YW50ZWQgdG8gdGFs
ayBhYm91dCB1c2UgY2FzZXMsIGJ1dCBJIHRoaW5rIGl0DQo+aGFybXMgdGhlIGRyYWZ0IHRvIGRv
IHNvIHdoZW4gd2UgaGF2ZW4ndCByZWFsbHkgc2VlbiBob3cgcGVvcGxlIHdpbGwgY2hvb3NlDQo+
dG8gdXNlIGl0Lg0KDQpUaGUgc2VjdGlvbiA3IHdhcyBtYWlubHkgY29udHJpYnV0ZWQgYnkgSmlu
bWVpLiBTbyBJIHdpbGwgbGVhdmUgaXQgdG8gSmlubWVpJ3MgZGVjaXNpb24sIGVpdGhlciBkZWxl
dGluZyB0aGlzIHNlY3Rpb24gb3IgZml4aW5nIFRlZCdzIGNvbmNlcm4gc29vbi4gSmlubWVpLCBp
ZiB5b3UgZGVjaWRlIHRvIGtlZXAgdGhlIHNlc3Npb24sIEkgbmVlZCB0aGUgbmV3IHRleHQgYnkg
VGh1cnNkYXkgKEZlYi4gMTIpLCBpZGVhbGx5IGFmdGVyIGNvbmZpcm1hdGlvbiBmcm9tIFRlZC4N
Cg0KPkluIHNlY3Rpb24gOCwgdGhlcmUgYXJlIGZ1cnRoZXIgcHJvYmxlbXMsIGJ1dCBJIGRvbid0
IHRoaW5rIHRoZXJlJ3MgbXVjaCBwb2ludCBpbg0KPnRhbGtpbmcgYWJvdXQgdGhlbSB1bnRpbCB3
ZSd2ZSB0YWxrZWQgYWJvdXQgdGhpcy4NCg0KTGV0J3MgYXNzdW1lIHNlY3Rpb24gNyBoYXMgYmVl
biBwcm9wZXJseSBhZGRyZXNzZWQsIEkgbmVlZCB0byB3b3JrIG9uIHNlY3Rpb24gOCBwYXJyYWxs
ZWwgaW4gb3JkZXIgdG8gcHJvZHVjZSBhbiB1cGRhdGUgYnkgRnJpZGF5LiBUZWQsIGNvdWxkIHlv
dSBnaXZlIHRoZSBkZXRhaWxzIGVpdGhlciBwdWJsaWMgb3IgcHJpdmF0ZSBlbWFpbD8NCg0KTWFu
eSB0aGFua3MgYW5kIGJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KPl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ZGhjd2cgbWFpbGluZyBsaXN0DQo+ZGhj
d2dAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dn
DQo=


From nobody Mon Feb  9 10:24:46 2015
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 4398E1A1B5E for <dhcwg@ietfa.amsl.com>; Mon,  9 Feb 2015 10:18:35 -0800 (PST)
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 EYBHu1F11rpq for <dhcwg@ietfa.amsl.com>; Mon,  9 Feb 2015 10:18:33 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6C531A6EFE for <dhcwg@ietf.org>; Mon,  9 Feb 2015 10:18:21 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id em10so3051546wid.1 for <dhcwg@ietf.org>; Mon, 09 Feb 2015 10:18:20 -0800 (PST)
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=DMhp2+fVVIQo4vDo9/mWKy03SRqV4idxItBQmaicdeI=; b=wGd8S89EAbInpu6DPfYr3o6XROyXGbwxkC0xjZb/fIIlHSPBDahbRsVAEpDViJURZf HTdpWa5tXZWSqQzmcQH7wss7KZNonDmU/TaP6PfzRs5ib12m7xGc0Q9NMKLVZVKvWi+H JiFSymjt+Eoz0RohEXopqyXaYAVBXJGO21+TtKMai98oXYKqgmniq+28f0kTD2umfrkp WATZzdRpP1OcgtTubfwIZA2PEsPEn564y/yepvauRpP7domvcYU2BNjRNIBnF2TtEIZ2 60iLGnCo+8+lapQWK6pTz+NOsVerOtTkpE1P/XBvbSyJFLJVAIyDZmlMULuMP/I1hpSb Tmxg==
MIME-Version: 1.0
X-Received: by 10.180.88.33 with SMTP id bd1mr38019036wib.10.1423505900572; Mon, 09 Feb 2015 10:18:20 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Mon, 9 Feb 2015 10:18:20 -0800 (PST)
In-Reply-To: <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com>
Date: Mon, 9 Feb 2015 10:18:20 -0800
X-Google-Sender-Auth: 2bEqufhJdqJb2q8e4tHUcci6wdg
Message-ID: <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <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/ano2hsU8oT_oRUK7pqCmDo7ByfU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 09 Feb 2015 18:18:35 -0000

At Fri, 6 Feb 2015 20:13:25 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> For #56, how is this text much different from what is in RFC 3315:
>
> "When the client receives a NotOnLink status from the server in response =
to a Request, the client can either re-issue the Request without specifying=
 any addresses or restart the DHCP server discovery process (see section 17=
<http://tools.ietf.org/html/rfc3315#section-17>)."
>
> For #57, from 3315:
>
>
> "When the client receives a NotOnLink status from the server in
>    response to a Request, the client can either re-issue the Request
>    without specifying any addresses or restart the DHCP server discovery
>    process (see section 17<http://tools.ietf.org/html/rfc3315#section-17>=
)."
>
> How is what we are saying any different?

The main difference is that dhcpv6-stateful-issues now specifies that
clients use a single DHCPv6 session for all IA options, and not
clarifying these can break the integrity of the specification.  See,
e.g., the very last paragraph of
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15934.html

On the other hand, in RFC3315 it's simply unclear and (implicitly)
left to the implementation.   To me, these two are very different
kinds of issues.  I can leave the latter open, but not the former.

> Feel free to start a new draft if you wish to start work on discussing th=
ese issues; we are planning to request adoption of the 3315bis work shortly=
, so that is another venue.

I'm fine with deferring the resolution to 3315bis (also, I don't think
it's worth a separate draft).  But I'd at least like dhcpv6-stateful-issues
to clearly state these points are open issues and will be handled in
later document(s).  Otherwise it will confuse implementors of this
specification.  If you don't mind adding such text, I'm willing to
volunteer to propose a possible small subsection for that.  But to do
so, I first wanted to understand why these are minor enough and we can
safely defer the solution.  Hence these questions:

> Depending on the rationale for deferring specific points, I can live
> with that.  But I'd at least like to understand why it's okay to
> defer.  Regarding #56, or more specifically, on the following text of
> stateful-issues-10:
>
>     When the client receives a NotOnLink status from the server in
>     response to a Request, the client can either re-issue the Request
>     without specifying any addresses or restart the DHCP server
>     discovery process (see section 17).
>
> Specifically why is it okay to defer it?  Because a CPE-type client
> isn't supposed to be a mobile device and is unlikely to get NotOnLink
> (or for that matter it's even unlikely for the client to send Confirm
> in the first place)?
>
> What about #57?  I guess the relevant text in stateful-issues-10 is
> now this one:
>
>     If the client cannot operate without the addresses for the IAs for
>     which it received the NoAddrsAvail status code, the client may try
>     another server (perhaps by restarting the DHCP server discovery
>     process).
>
> Why can we dismiss it (in terms of #57)?  Perhaps because it's assumed
> to be unlikely that the client (=3D CPE) gets a prefix but not an
> address?

--
JINMEI, Tatuya


From nobody Mon Feb  9 11:20:50 2015
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 6FF761A1BF9 for <dhcwg@ietfa.amsl.com>; Mon,  9 Feb 2015 10:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.722
X-Spam-Level: *
X-Spam-Status: No, score=1.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 HwIwKVFqoAbw for <dhcwg@ietfa.amsl.com>; Mon,  9 Feb 2015 10:58:19 -0800 (PST)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6A41A1B8D for <dhcwg@ietf.org>; Mon,  9 Feb 2015 10:58:18 -0800 (PST)
Received: by mail-wg0-f45.google.com with SMTP id x12so28674558wgg.4 for <dhcwg@ietf.org>; Mon, 09 Feb 2015 10:58:17 -0800 (PST)
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=XJKmTGq9Ga6lJSv6f4nTcbAwMiX0FY+xt8HgYl7Wpw8=; b=kj1xBnx8/N9JGUO23AL63QrCvuCrY4YWALPdFoCgXPrTyid+0o2t+Tb/HTuErV7E53 YqaFqNSrnfHVqohDM68lxKbIoKy/HAxy1nuo2R6C5gkiPC/8JS5p4VlPx1AbF0RVqKHb CxMJXctBOy1hJATBnySJdJeqT0Rn4TH601EM0OUvy33PtoeF2FQFikNebm2ClZcCm7DM gkoj+tdJrGZ7CSZyw3XaFRrtZKdFqaHcvYMcj6r7Yq+3R05v8aO0mIghVDHuu5kF1qwf l2yTx8TtVK1UYQaTSWq1EL4XgNh3ijAt3ZVuN03x1U+QxT69FxyAVqO+Oyc4uA49h3i7 GBCw==
MIME-Version: 1.0
X-Received: by 10.180.198.101 with SMTP id jb5mr1943305wic.92.1423508288826; Mon, 09 Feb 2015 10:58:08 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Mon, 9 Feb 2015 10:58:08 -0800 (PST)
In-Reply-To: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com>
Date: Mon, 9 Feb 2015 10:58:08 -0800
X-Google-Sender-Auth: FN_eUzM3TOeWYCnx905tiQ0X9_E
Message-ID: <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/y7n17bIk9CemqgBvGSLgy6ljeZ8>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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, 09 Feb 2015 18:58:20 -0000

At Sat, 7 Feb 2015 15:31:47 -0600,
Ted Lemon <mellon@fugue.com> wrote:

> If it were up to me, I would simply delete section 7, and all the
> references to it elsewhere in the document, and simply provide the
> mechanism without saying how to use it.   I know Jinmei wanted to
> talk about use cases, but I think it harms the draft to do so when
> we haven't really seen how people will choose to use it.

What I wanted to see was an explanation of "why we need this
mechanism".  It doesn't have to be use cases; actually, a more formal
"threat analysis" documentation might be better.  In the previous
discussion on this fundamental point, (IIRC) no one showed persuading
explanation beyond "someone previously said they wanted to have it".
The idea of publishing "threat analysis" was rejected because it was
considered too time consuming.  So, as a compromise, we chose to add a
"use cases" section in this document.  That's also why the section is
largely speculative as you said in a different paragraph.

If this section raises concerns, we should certainly address them.
But totally removing the section will bring us to the very fundamental
discussion: we're providing a new protocol with on one
understanding/explaining why it's necessary.  And, whether it's a "use
cases" section or a formal analysis document, I believe there was a
pretty clear sense of the wg that we shouldn't publish the protocol
with completely ignoring the "why".

So, I guess we should probably reconfirm the sense of the wg again:
whether it's okay to publish the protocol part without explaining why
we need it.  If the mood of the wg has now changed and they say it's
okay, we should probably just drop this section and move forward.

I, for one, still believe it doesn't make sense to just publish the
protocol if no one understands why we need it.  Like before, however,
I'm fine with dropping the use case section from the protocol document
and publish a formal threat analysis first.

--
JINMEI, Tatuya


From nobody Mon Feb  9 12:04:22 2015
Return-Path: <mellon@fugue.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 666EA1A87C1 for <dhcwg@ietfa.amsl.com>; Mon,  9 Feb 2015 11:30:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.611
X-Spam-Level: 
X-Spam-Status: No, score=-1.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UwtM53gIVTnS for <dhcwg@ietfa.amsl.com>; Mon,  9 Feb 2015 11:30:53 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id A77E31A87D2 for <dhcwg@ietf.org>; Mon,  9 Feb 2015 11:30:07 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id D10DC2380847; Mon,  9 Feb 2015 14:30:06 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com>
Date: Mon, 9 Feb 2015 14:30:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Agfl2iqGZ00_pI-k1tJ4wS_Ccao>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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, 09 Feb 2015 19:30:55 -0000

On Feb 9, 2015, at 1:58 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> What I wanted to see was an explanation of "why we need this
> mechanism".

In my mind, the answer to this is that at present no mechanism exists =
for security DHCP messages between servers and clients that does not =
have a serious key distribution problem.   By using public-key-based =
authentication, we provide a mechanism for securing such messages that =
can be reasonably deployed without the key distribution problems =
inherent in the shared-secret-based authentication mechanism specified =
in RFC 3315, either using some form of PKI or else Trust-on-first-use =
(TOFU).

Why do we need to say more than this?


From nobody Mon Feb  9 19:24:17 2015
Return-Path: <internet-drafts@ietf.org>
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 311821A8A6C; Mon,  9 Feb 2015 19:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 YbuR3goVhA8U; Mon,  9 Feb 2015 19:24:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 64FE71A8830; Mon,  9 Feb 2015 19:24:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150210032400.21374.37461.idtracker@ietfa.amsl.com>
Date: Mon, 09 Feb 2015 19:24:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/HA1xmHrtw9AXSuUH7YbiOZzcULs>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcp-privacy-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 10 Feb 2015 03:24:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Privacy considerations for DHCP
        Authors         : Sheng Jiang
                          Suresh Krishnan
                          Tomek Mrugalski
	Filename        : draft-ietf-dhc-dhcp-privacy-00.txt
	Pages           : 13
	Date            : 2015-02-09

Abstract:
   DHCP is a protocol that is used to provide addressing and
   configuration information to IPv4 hosts.  This document discusses the
   various identifiers used by DHCP and the potential privacy issues.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcp-privacy/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcp-privacy-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 10 12:27:41 2015
Return-Path: <tomasz.mrugalski@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 45E091A1BFB for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 12:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 TljFFKxyGm_R for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 12:27:35 -0800 (PST)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 134D51A1BEF for <dhcwg@ietf.org>; Tue, 10 Feb 2015 12:27:35 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id z2so15826847wiv.0 for <dhcwg@ietf.org>; Tue, 10 Feb 2015 12:27:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xb5Wv/JZacAC4yaNs+v0k11zSjdje6MNTtidp8dJaiw=; b=CW3e5MTbPkBQHimygB48GP5vc0uUY/5UDrVIcvh03bDZ+kbasOBD0s3ObYmpX3eIxC EghYYnoBsPVkJ4A0vDRr3nnDoHdqJ3DwjYo80RFjeEShm0orRlXzcnEkLaQehpQFk4qa ybZXOi6JYxV+1DG8/R+UMT9U6nAa0YzSsnQLq6bMR+eJKA1b/A0Xjb0E97LENgrDdYFo s6XqeCG39PeRPMnCWa2RuFbThuTEOiq81A1QUfIlnam61s7C6kgG9cwjRPcerXEz045U GtgzIHO3oJGDde8wIMkBhxF/NR2pmQQphW/FbEFwxISzQ6jweQYqyB5/fsCgnUm0ODzo ctPw==
X-Received: by 10.180.21.162 with SMTP id w2mr49124005wie.42.1423600053860; Tue, 10 Feb 2015 12:27:33 -0800 (PST)
Received: from [10.0.0.100] (109107011157.gdansk.vectranet.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id o7sm20290480wix.12.2015.02.10.12.27.31 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Feb 2015 12:27:32 -0800 (PST)
Message-ID: <54DA69B2.7030102@gmail.com>
Date: Tue, 10 Feb 2015 21:27:30 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>,  "Bernie Volz (volz)" <volz@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com>
In-Reply-To: <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com>
X-TagToolbar-Keys: D20150210212730086
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/bja5GUL8HelK4wVD-SDusJQwmZc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Tue, 10 Feb 2015 20:27:37 -0000

On 09.02.2015 19:18, 神明達哉 wrote:
> At Fri, 6 Feb 2015 20:13:25 +0000,
> "Bernie Volz (volz)" <volz@cisco.com> wrote:
> 
>> For #56, how is this text much different from what is in RFC 3315:
>>
>> "When the client receives a NotOnLink status from the server in response to a Request, the client can either re-issue the Request without specifying any addresses or restart the DHCP server discovery process (see section 17<http://tools.ietf.org/html/rfc3315#section-17>)."
>>
>> For #57, from 3315:
>>
>>
>> "When the client receives a NotOnLink status from the server in
>>    response to a Request, the client can either re-issue the Request
>>    without specifying any addresses or restart the DHCP server discovery
>>    process (see section 17<http://tools.ietf.org/html/rfc3315#section-17>)."
>>
>> How is what we are saying any different?
> 
> The main difference is that dhcpv6-stateful-issues now specifies that
> clients use a single DHCPv6 session for all IA options, and not
> clarifying these can break the integrity of the specification.  See,
> e.g., the very last paragraph of
> http://www.ietf.org/mail-archive/web/dhcwg/current/msg15934.html
> 
> On the other hand, in RFC3315 it's simply unclear and (implicitly)
> left to the implementation.   To me, these two are very different
> kinds of issues.  I can leave the latter open, but not the former.
How about adding this sentence at the end of the 4.3 section:
"This change effectively will cause clients to make all renewals in a
single exchange." Would that be sufficient?

>> Feel free to start a new draft if you wish to start work on discussing these issues; we are planning to request adoption of the 3315bis work shortly, so that is another venue.
> 
> I'm fine with deferring the resolution to 3315bis (also, I don't think
> it's worth a separate draft).  But I'd at least like dhcpv6-stateful-issues
> to clearly state these points are open issues and will be handled in
> later document(s).
Personally, I think it's a bit redundant (no RFC could make a promise of
never being updated in the future), but for the sake of moving forward
we can consider adding the following at the end of the section:

OLD:
  The changes described in this document are intended to be
  incorporated in a new revision of the DHCPv6 protocol specification
  ([I-D.dhcwg-dhc-rfc3315bis]).
NEW:
  The changes described in this document are intended to be
  incorporated in a new revision of the DHCPv6 protocol specification
  ([I-D.dhcwg-dhc-rfc3315bis]), which will also address additional open
  issues.

Would that be sufficiently clear? I'd really like this document to move
forward sooner rather than later.

On a related note, we plan to start adoption call for 3315bis in a bit
over a week from now. To have it adopted by Dallas, we'll need to start
it around Feb. 18th.

I have minor comments about the draft, both are related to idnits:
1. idnits reports one mis-capitalisation: "MUST not" => "MUST NOT"

2. You're proposing updates to several sections of RFCs that were
published prior to RFC5378 and I think you haven't obtained approvals
from all original authors to move to the BCP78 rights. Therefore you
should use pre-RFC5378 boilerplate. Don't worry, it's easy to do.
Changing in the xml ipr="Trust200902" to ipr="pre5378Trust200902" should
do the trick.

3. Reference update is required draft-ietf-mif-mpvd-arch-09 => -10.

Tomek


From nobody Tue Feb 10 14:04:00 2015
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 5C7581A870F for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 14:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 0ItDS6FFsOOo for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 14:03:55 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C8221A86F7 for <dhcwg@ietf.org>; Tue, 10 Feb 2015 14:03:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6176; q=dns/txt; s=iport; t=1423605824; x=1424815424; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Wg5hHJGt0dafOkVQC8RPB1OaTdV7u6TYwtaM+qldmLA=; b=TiTb7FjSt+NAqlm+6ccU4HSD9KTDGqlbE0w7Cvnv3YgqJtcFIcRU+hwy Tdw6j91KkFwCEk0O9NHIMhbOdQBtsJC7PdFguCz47hQKMgbEGwNF9Q9eD Ytaa7oOtCxJW9xeIbNtnxynbKsd1zVMn1Kop7zGbmoN1XxHzLdqGq7scm 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0COBQDPf9pU/5RdJa1bgwZSWgSCfcAVhXECHIEDQwEBAQEBAXyEDAEBAQMBHQYRRQwEAgEGAg4DBAEBAQICBh0DAgICHxEUAQgIAgQBDQUIAYgQAwkIDZ0znGyRBg2FQwEBAQEBAQEBAQEBAQEBAQEBAQEBAReBIYwsgVkBAR4WGwcGgmIugRQFjyCDUYQXgl42imc+hgMig25vAYEKOX8BAQE
X-IronPort-AV: E=Sophos;i="5.09,553,1418083200"; d="scan'208";a="122380453"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-2.cisco.com with ESMTP; 10 Feb 2015 22:03:43 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t1AM3hSR008852 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Feb 2015 22:03:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-rcd-x04.cisco.com ([::1]) with mapi id 14.03.0195.001; Tue, 10 Feb 2015 16:03:43 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikAAeCiTAP//tueggAT7bQCAAbZrAIAASymg
Date: Tue, 10 Feb 2015 22:03:43 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C998073@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com>
In-Reply-To: <54DA69B2.7030102@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/jL1eFd1cRCzrqSI9O9b_FGBFons>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Ted Lemon \(Ted.Lemon@nominum.com\)" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Tue, 10 Feb 2015 22:03:58 -0000

SSd2ZSBkb25lIHRoZSBuaXRzIChzbyB4bWwgaXMgLTExLCBmaXhlZCBNVVNUIG5vdCwgYW5kIGNo
YW5nZWQgdG8gcHJlNTM3OFRydXN0MjAwOTAyKS4NCg0KSSd2ZSBub3QgdG91Y2hlZCB0aGUgb3Ro
ZXIgaXNzdWVzLg0KDQpJJ20gdGhpbmtpbmcgdGhhdCB3ZSByZWFsbHkgbmVlZCB0byBiZSBjYXJl
ZnVsIGFib3V0IGhpbnRpbmcgYXQgb3RoZXIgaXNzdWVzIGFzIElFU0cgbWF5IGFzayB3aHkgbm90
IGZpeCB0aG9zZSB0b28uIEJ1dCBwZXJoYXBzIFRlZCBoYXMgc29tZSBhZHZpY2UgaGVyZT8NCg0K
QW5kLCB3ZSBzdGlsbCBoYXZlIHRoZSBkcmFmdCB0aXRsZSB0byByZXNvbHZlLg0KDQpPbmNlIEpp
bm1laSBvciBvdGhlcnMgY29tbWVudCBvbiB0aGUgcHJvcG9zZSBmb3IgNC4zIHRleHQgLi4uDQoN
Ckl0IHdvdWxkIGJlIGdvb2QgdG8gZ2V0IHRoaXMgZG9uZSBub3cgc28gdGhhdCBUZWQgY2FuIHJh
aXNlIGFuZCBkaXNjdXNzIGF0IElFU0csIGJ1dCBhbGFzIHBlcmhhcHMgdGhhdCB3aWxsIG5vdCBi
ZSBwb3NzaWJsZSBhbmQgd2UnbGwganVzdCBoYXZlIHRvIGxldCB0aGluZ3MgZGV2ZWxvcCBhcyB0
aGV5IHdpbGwuIChJIHN1cmUgd291bGQgbGlrZSB0byBnZXQgdGhpcyBlZmZvcnQgb3ZlciBhbmQg
ZG9uZSB3aXRoIHRvbyAuLi4gaXQgaGFzIGJlZW4gYSBsb25nIHNsb3cgcHJvY2VzcyAtIGl0IGlz
IG5ldmVyIGVhc3kgcHV0dGluZyB0aGluZ3MgaW4gd29yZHMuKQ0KDQotIEJlcm5pZQ0KDQotLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogVG9tZWsgTXJ1Z2Fsc2tpIFttYWlsdG86dG9t
YXN6Lm1ydWdhbHNraUBnbWFpbC5jb21dIA0KU2VudDogVHVlc2RheSwgRmVicnVhcnkgMTAsIDIw
MTUgMzoyNyBQTQ0KVG86IOelnuaYjumBlOWTiTsgQmVybmllIFZvbHogKHZvbHopDQpDYzogZGhj
d2dAaWV0Zi5vcmc7IFRlZCBMZW1vbiAoVGVkLkxlbW9uQG5vbWludW0uY29tKQ0KU3ViamVjdDog
UmU6IFtkaGN3Z10gZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXN0YXRlZnVsLWlzc3Vlcy0xMC50eHQN
Cg0KT24gMDkuMDIuMjAxNSAxOToxOCwg56We5piO6YGU5ZOJIHdyb3RlOg0KPiBBdCBGcmksIDYg
RmViIDIwMTUgMjA6MTM6MjUgKzAwMDAsDQo+ICJCZXJuaWUgVm9seiAodm9seikiIDx2b2x6QGNp
c2NvLmNvbT4gd3JvdGU6DQo+IA0KPj4gRm9yICM1NiwgaG93IGlzIHRoaXMgdGV4dCBtdWNoIGRp
ZmZlcmVudCBmcm9tIHdoYXQgaXMgaW4gUkZDIDMzMTU6DQo+Pg0KPj4gIldoZW4gdGhlIGNsaWVu
dCByZWNlaXZlcyBhIE5vdE9uTGluayBzdGF0dXMgZnJvbSB0aGUgc2VydmVyIGluIHJlc3BvbnNl
IHRvIGEgUmVxdWVzdCwgdGhlIGNsaWVudCBjYW4gZWl0aGVyIHJlLWlzc3VlIHRoZSBSZXF1ZXN0
IHdpdGhvdXQgc3BlY2lmeWluZyBhbnkgYWRkcmVzc2VzIG9yIHJlc3RhcnQgdGhlIERIQ1Agc2Vy
dmVyIGRpc2NvdmVyeSBwcm9jZXNzIChzZWUgc2VjdGlvbiAxNzxodHRwOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9yZmMzMzE1I3NlY3Rpb24tMTc+KS4iDQo+Pg0KPj4gRm9yICM1NywgZnJvbSAzMzE1
Og0KPj4NCj4+DQo+PiAiV2hlbiB0aGUgY2xpZW50IHJlY2VpdmVzIGEgTm90T25MaW5rIHN0YXR1
cyBmcm9tIHRoZSBzZXJ2ZXIgaW4NCj4+ICAgIHJlc3BvbnNlIHRvIGEgUmVxdWVzdCwgdGhlIGNs
aWVudCBjYW4gZWl0aGVyIHJlLWlzc3VlIHRoZSBSZXF1ZXN0DQo+PiAgICB3aXRob3V0IHNwZWNp
ZnlpbmcgYW55IGFkZHJlc3NlcyBvciByZXN0YXJ0IHRoZSBESENQIHNlcnZlciBkaXNjb3ZlcnkN
Cj4+ICAgIHByb2Nlc3MgKHNlZSBzZWN0aW9uIDE3PGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1s
L3JmYzMzMTUjc2VjdGlvbi0xNz4pLiINCj4+DQo+PiBIb3cgaXMgd2hhdCB3ZSBhcmUgc2F5aW5n
IGFueSBkaWZmZXJlbnQ/DQo+IA0KPiBUaGUgbWFpbiBkaWZmZXJlbmNlIGlzIHRoYXQgZGhjcHY2
LXN0YXRlZnVsLWlzc3VlcyBub3cgc3BlY2lmaWVzIHRoYXQgDQo+IGNsaWVudHMgdXNlIGEgc2lu
Z2xlIERIQ1B2NiBzZXNzaW9uIGZvciBhbGwgSUEgb3B0aW9ucywgYW5kIG5vdCANCj4gY2xhcmlm
eWluZyB0aGVzZSBjYW4gYnJlYWsgdGhlIGludGVncml0eSBvZiB0aGUgc3BlY2lmaWNhdGlvbi4g
IFNlZSwgDQo+IGUuZy4sIHRoZSB2ZXJ5IGxhc3QgcGFyYWdyYXBoIG9mIA0KPiBodHRwOi8vd3d3
LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvZGhjd2cvY3VycmVudC9tc2cxNTkzNC5odG1sDQo+
IA0KPiBPbiB0aGUgb3RoZXIgaGFuZCwgaW4gUkZDMzMxNSBpdCdzIHNpbXBseSB1bmNsZWFyIGFu
ZCAoaW1wbGljaXRseSkNCj4gbGVmdCB0byB0aGUgaW1wbGVtZW50YXRpb24uICAgVG8gbWUsIHRo
ZXNlIHR3byBhcmUgdmVyeSBkaWZmZXJlbnQNCj4ga2luZHMgb2YgaXNzdWVzLiAgSSBjYW4gbGVh
dmUgdGhlIGxhdHRlciBvcGVuLCBidXQgbm90IHRoZSBmb3JtZXIuDQpIb3cgYWJvdXQgYWRkaW5n
IHRoaXMgc2VudGVuY2UgYXQgdGhlIGVuZCBvZiB0aGUgNC4zIHNlY3Rpb246DQoiVGhpcyBjaGFu
Z2UgZWZmZWN0aXZlbHkgd2lsbCBjYXVzZSBjbGllbnRzIHRvIG1ha2UgYWxsIHJlbmV3YWxzIGlu
IGEgc2luZ2xlIGV4Y2hhbmdlLiIgV291bGQgdGhhdCBiZSBzdWZmaWNpZW50Pw0KDQo+PiBGZWVs
IGZyZWUgdG8gc3RhcnQgYSBuZXcgZHJhZnQgaWYgeW91IHdpc2ggdG8gc3RhcnQgd29yayBvbiBk
aXNjdXNzaW5nIHRoZXNlIGlzc3Vlczsgd2UgYXJlIHBsYW5uaW5nIHRvIHJlcXVlc3QgYWRvcHRp
b24gb2YgdGhlIDMzMTViaXMgd29yayBzaG9ydGx5LCBzbyB0aGF0IGlzIGFub3RoZXIgdmVudWUu
DQo+IA0KPiBJJ20gZmluZSB3aXRoIGRlZmVycmluZyB0aGUgcmVzb2x1dGlvbiB0byAzMzE1Ymlz
IChhbHNvLCBJIGRvbid0IHRoaW5rIA0KPiBpdCdzIHdvcnRoIGEgc2VwYXJhdGUgZHJhZnQpLiAg
QnV0IEknZCBhdCBsZWFzdCBsaWtlIA0KPiBkaGNwdjYtc3RhdGVmdWwtaXNzdWVzIHRvIGNsZWFy
bHkgc3RhdGUgdGhlc2UgcG9pbnRzIGFyZSBvcGVuIGlzc3VlcyANCj4gYW5kIHdpbGwgYmUgaGFu
ZGxlZCBpbiBsYXRlciBkb2N1bWVudChzKS4NClBlcnNvbmFsbHksIEkgdGhpbmsgaXQncyBhIGJp
dCByZWR1bmRhbnQgKG5vIFJGQyBjb3VsZCBtYWtlIGEgcHJvbWlzZSBvZiBuZXZlciBiZWluZyB1
cGRhdGVkIGluIHRoZSBmdXR1cmUpLCBidXQgZm9yIHRoZSBzYWtlIG9mIG1vdmluZyBmb3J3YXJk
IHdlIGNhbiBjb25zaWRlciBhZGRpbmcgdGhlIGZvbGxvd2luZyBhdCB0aGUgZW5kIG9mIHRoZSBz
ZWN0aW9uOg0KDQpPTEQ6DQogIFRoZSBjaGFuZ2VzIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50
IGFyZSBpbnRlbmRlZCB0byBiZQ0KICBpbmNvcnBvcmF0ZWQgaW4gYSBuZXcgcmV2aXNpb24gb2Yg
dGhlIERIQ1B2NiBwcm90b2NvbCBzcGVjaWZpY2F0aW9uDQogIChbSS1ELmRoY3dnLWRoYy1yZmMz
MzE1YmlzXSkuDQpORVc6DQogIFRoZSBjaGFuZ2VzIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50
IGFyZSBpbnRlbmRlZCB0byBiZQ0KICBpbmNvcnBvcmF0ZWQgaW4gYSBuZXcgcmV2aXNpb24gb2Yg
dGhlIERIQ1B2NiBwcm90b2NvbCBzcGVjaWZpY2F0aW9uDQogIChbSS1ELmRoY3dnLWRoYy1yZmMz
MzE1YmlzXSksIHdoaWNoIHdpbGwgYWxzbyBhZGRyZXNzIGFkZGl0aW9uYWwgb3Blbg0KICBpc3N1
ZXMuDQoNCldvdWxkIHRoYXQgYmUgc3VmZmljaWVudGx5IGNsZWFyPyBJJ2QgcmVhbGx5IGxpa2Ug
dGhpcyBkb2N1bWVudCB0byBtb3ZlIGZvcndhcmQgc29vbmVyIHJhdGhlciB0aGFuIGxhdGVyLg0K
DQpPbiBhIHJlbGF0ZWQgbm90ZSwgd2UgcGxhbiB0byBzdGFydCBhZG9wdGlvbiBjYWxsIGZvciAz
MzE1YmlzIGluIGEgYml0IG92ZXIgYSB3ZWVrIGZyb20gbm93LiBUbyBoYXZlIGl0IGFkb3B0ZWQg
YnkgRGFsbGFzLCB3ZSdsbCBuZWVkIHRvIHN0YXJ0IGl0IGFyb3VuZCBGZWIuIDE4dGguDQoNCkkg
aGF2ZSBtaW5vciBjb21tZW50cyBhYm91dCB0aGUgZHJhZnQsIGJvdGggYXJlIHJlbGF0ZWQgdG8g
aWRuaXRzOg0KMS4gaWRuaXRzIHJlcG9ydHMgb25lIG1pcy1jYXBpdGFsaXNhdGlvbjogIk1VU1Qg
bm90IiA9PiAiTVVTVCBOT1QiDQoNCjIuIFlvdSdyZSBwcm9wb3NpbmcgdXBkYXRlcyB0byBzZXZl
cmFsIHNlY3Rpb25zIG9mIFJGQ3MgdGhhdCB3ZXJlIHB1Ymxpc2hlZCBwcmlvciB0byBSRkM1Mzc4
IGFuZCBJIHRoaW5rIHlvdSBoYXZlbid0IG9idGFpbmVkIGFwcHJvdmFscyBmcm9tIGFsbCBvcmln
aW5hbCBhdXRob3JzIHRvIG1vdmUgdG8gdGhlIEJDUDc4IHJpZ2h0cy4gVGhlcmVmb3JlIHlvdSBz
aG91bGQgdXNlIHByZS1SRkM1Mzc4IGJvaWxlcnBsYXRlLiBEb24ndCB3b3JyeSwgaXQncyBlYXN5
IHRvIGRvLg0KQ2hhbmdpbmcgaW4gdGhlIHhtbCBpcHI9IlRydXN0MjAwOTAyIiB0byBpcHI9InBy
ZTUzNzhUcnVzdDIwMDkwMiIgc2hvdWxkIGRvIHRoZSB0cmljay4NCg0KMy4gUmVmZXJlbmNlIHVw
ZGF0ZSBpcyByZXF1aXJlZCBkcmFmdC1pZXRmLW1pZi1tcHZkLWFyY2gtMDkgPT4gLTEwLg0KDQpU
b21law0KDQo=


From nobody Tue Feb 10 15:32:34 2015
Return-Path: <Ted.Lemon@nominum.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 745381A872B for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 15:32:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 R6xb6QK5Qq92 for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 15:32:30 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 058C71A03A5 for <dhcwg@ietf.org>; Tue, 10 Feb 2015 15:32:30 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id E17AFDA029A for <dhcwg@ietf.org>; Tue, 10 Feb 2015 23:32:29 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id AD0A153E082; Tue, 10 Feb 2015 15:32:29 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 10 Feb 2015 15:32:29 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <54DA69B2.7030102@gmail.com>
Date: Tue, 10 Feb 2015 18:32:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ew9ilyp8lyE_u7HT4xK7R5M8aY4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Tue, 10 Feb 2015 23:32:32 -0000

On Feb 10, 2015, at 3:27 PM, Tomek Mrugalski =
<tomasz.mrugalski@gmail.com> wrote:
>> The main difference is that dhcpv6-stateful-issues now specifies that
>> clients use a single DHCPv6 session for all IA options, and not
>> clarifying these can break the integrity of the specification.  See,
>> e.g., the very last paragraph of
>> http://www.ietf.org/mail-archive/web/dhcwg/current/msg15934.html
>>=20
>> On the other hand, in RFC3315 it's simply unclear and (implicitly)
>> left to the implementation.   To me, these two are very different
>> kinds of issues.  I can leave the latter open, but not the former.
> How about adding this sentence at the end of the 4.3 section:
> "This change effectively will cause clients to make all renewals in a
> single exchange." Would that be sufficient?

I don't think this really helps, because as Marcin said, there is an =
actual change in expected behavior here.   I think we just ("just!") =
need to say what we think the right behavior is in the case he =
describes.

I must confess however, that I consider this a weakness to the whole =
proposal, and consequently I don't actually have advice.   It seems to =
me that you can have any of the following DHCP server behaviors:

a: a DHCP server will offer IA_NA but not IA_PD
b: a DHCP server will offer IA_PD but not IA_NA
c: a DHCP server will offer both IA_PD and IA_NA if requested

Suppose you have servers corresponding to (a), (b) and (c) configured on =
a particular network.   A client that attempts to get an IA_NA and an =
IA_PD may not succeed in contacting server c, perhaps because it is =
offline.   It could get full service from (a) and (b) combined, but =
we've said that that's not how DHCPv6 is supposed to work.   So it has =
to pick one.

Now suppose (c) comes online and responds to a subsequent request, =
because the client has chosen one of (a) or (b) but is not satisfied.   =
In this case, the client has to either switch to (c) and lose whatever =
it got from (a) or (b), or else it has to continue with its existing =
configuration.   Presumably it will switch, because otherwise why would =
it have persisted in trying to get a new configuration?

The alternative is to say that when possible, DHCP clients will keep the =
state machines for IA_NA and IA_PD in sync, but if it can't get a full =
configuration that way, and can get a full configuration by running two =
separate state machines, it should.   We could add that when (c) =
appears, it should do a soft renumber to (c), deprecating the =
address(es) it got either from (a) or (b), but should maintain two state =
machines during the interim.

I don't have a strong preference.   I think you get better behavior with =
the alternative, but the implementation is easier if we say that the =
client maintains only one state machine.

I haven't read the draft in a while, so I realize that what I just wrote =
may be out of sync with what the draft currently says, but I think what =
I just described represents the two possible ways of addressing this =
concern, and I am okay with either approach.   I think leaving it =
unspecified isn't a great solution, and addressing it with a single =
sentence as Tomek proposed will likely not be understood by many client =
implementors.


From nobody Tue Feb 10 15:37:10 2015
Return-Path: <Ted.Lemon@nominum.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 2AA171A87A2 for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 15:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 EhlMlufnvAbK for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 15:37:02 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D91C51A87A6 for <dhcwg@ietf.org>; Tue, 10 Feb 2015 15:35:55 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id C5055DA029A for <dhcwg@ietf.org>; Tue, 10 Feb 2015 23:35:55 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A098053E085; Tue, 10 Feb 2015 15:35:55 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 10 Feb 2015 15:35:55 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1C998073@xmb-rcd-x04.cisco.com>
Date: Tue, 10 Feb 2015 18:35:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <BA921BEF-CF37-4E0D-9E58-1DA2056B47EE@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1C998073@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ShiW5uFq8hr7tY9iHjGZPp8zUDA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Tue, 10 Feb 2015 23:37:07 -0000

On Feb 10, 2015, at 5:03 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I'm thinking that we really need to be careful about hinting at other =
issues as IESG may ask why not fix those too. But perhaps Ted has some =
advice here?

We can just tell them the 3315bis work is in progress, and will sweep up =
other changes; this draft captures the ones that we considered most =
urgent.



From nobody Tue Feb 10 19:06:45 2015
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 EFD501A010F for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 19:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 AyWvic41y6JE for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 19:06:31 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04C991A00F5 for <dhcwg@ietf.org>; Tue, 10 Feb 2015 19:06:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5865; q=dns/txt; s=iport; t=1423623991; x=1424833591; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=CmxNPbGQDam7/7Z3LWqQ76ib+AwrtCDK8bNp7neOZX0=; b=BHl8KjidmJvV2x5SDvysLlK7eZJ9MzkxthEk0UtgIsxfuuswH5TGy0aF mFMD5fnTp4jv+BizvEQPBnivUubZqEWJfcXSakZdH1mkKoxuknQo204JN 60SnH2qMql7bWqfGDh/rNIen9+cWVni9Q8WrE6e7joeUY1Y77T//P5OXL E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CMBQBTxtpU/5BdJa1bgwZSWgSCfcAchXECgR9DAQEBAQEBfIQMAQEBBCEBVwwEAgEIEQQBAQEBAwYFGAIDAiERFAkIAgQBDQUIARKHfgMRDZ0EnGcBkQANhUMBAQEBAQEBAQEBAQEBAQEBAQEBAQEXgR6IcIM/gVkBAR4mCwIFBoJfMYEUBY8gh2iCXoVKhhGGAyKCAhyBUG8BgQo5fwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,555,1418083200"; d="scan'208";a="122442101"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-2.cisco.com with ESMTP; 11 Feb 2015 03:06:30 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t1B36UZW003036 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Feb 2015 03:06:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0195.001; Tue, 10 Feb 2015 21:06:29 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikAAeCiTAP//tueggAT7bQCAAbZrAIAAM6qAgAAtKHA=
Date: Wed, 11 Feb 2015 03:06:29 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com>
In-Reply-To: <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/i8-UJ6jgYouod6N40hNPdWXgS0g>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 11 Feb 2015 03:06:36 -0000

Just to be clear, the draft only recommends that clients use a single state=
 machine and it makes that better because it offers clients the ability to =
Renew more than the IAs they got (and to keep renewal times in sync). Nothi=
ng in the draft requires that a client only maintain one state machine. The=
 goal was never to prohibit this, just to make it more likely that it would=
 work out correctly. That was the primary motivation for the draft long ago=
.

The key text is:

      We have chosen to recommend that clients use the remaining option:
      a single DHCP session and state machine.  The client maintains a
      single session and state machine. It uses the best configuration it
      is able to obtain during any configuration exchange.   But it
      continues, in each subsequent configuration exchange, to request all
      the configuration information it is programmed to try to obtain,
      including any stateful configuration options for which no results
      were returned in previous exchanges.

Clients already face the issue with how they handle these cases today.

I'm not so sure we can solve this issue - it will really be up to the clien=
t implementers as to what they consider 'required' for minimum service and =
how they handle degraded service (when only NA or PD, not both are availabl=
e). For example, a home gateway should likely be fine without an NA - just =
needs a PD (at least to provide the basic routing service).

Also, while anything is possible, in many cases where NA + PD are used (SP =
networks), it would likely be rare that you'd have combinations of the serv=
ers - except for misconfigured cases. And in those, when the server with th=
e broken configuration is fixed, this single state machine still works sinc=
e on the next Renewal the missing NA or PD will be requested. The reason fo=
r the draft is again that in some cases the lifetimes of NAs can drift from=
 those of PD (or be configured differently) and then you can end up in case=
s where this requires separate state machines.

Perhaps  we can add something regarding this and just explain the issue(s) =
and that it would be up to implementation to decide how best to proceed.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Tuesday, February 10, 2015 6:32 PM
To: Tomek Mrugalski
Cc: =1B$B?@L@C#:H=1B(B; Bernie Volz (volz); dhcwg@ietf.org
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt

On Feb 10, 2015, at 3:27 PM, Tomek Mrugalski <tomasz.mrugalski@gmail.com> w=
rote:
>> The main difference is that dhcpv6-stateful-issues now specifies that=20
>> clients use a single DHCPv6 session for all IA options, and not=20
>> clarifying these can break the integrity of the specification.  See,=20
>> e.g., the very last paragraph of=20
>> http://www.ietf.org/mail-archive/web/dhcwg/current/msg15934.html
>>=20
>> On the other hand, in RFC3315 it's simply unclear and (implicitly)
>> left to the implementation.   To me, these two are very different
>> kinds of issues.  I can leave the latter open, but not the former.
> How about adding this sentence at the end of the 4.3 section:
> "This change effectively will cause clients to make all renewals in a=20
> single exchange." Would that be sufficient?

I don't think this really helps, because as Marcin said, there is an actual=
 change in expected behavior here.   I think we just ("just!") need to say =
what we think the right behavior is in the case he describes.

I must confess however, that I consider this a weakness to the whole propos=
al, and consequently I don't actually have advice.   It seems to me that yo=
u can have any of the following DHCP server behaviors:

a: a DHCP server will offer IA_NA but not IA_PD
b: a DHCP server will offer IA_PD but not IA_NA
c: a DHCP server will offer both IA_PD and IA_NA if requested

Suppose you have servers corresponding to (a), (b) and (c) configured on a =
particular network.   A client that attempts to get an IA_NA and an IA_PD m=
ay not succeed in contacting server c, perhaps because it is offline.   It =
could get full service from (a) and (b) combined, but we've said that that'=
s not how DHCPv6 is supposed to work.   So it has to pick one.

Now suppose (c) comes online and responds to a subsequent request, because =
the client has chosen one of (a) or (b) but is not satisfied.   In this cas=
e, the client has to either switch to (c) and lose whatever it got from (a)=
 or (b), or else it has to continue with its existing configuration.   Pres=
umably it will switch, because otherwise why would it have persisted in try=
ing to get a new configuration?

The alternative is to say that when possible, DHCP clients will keep the st=
ate machines for IA_NA and IA_PD in sync, but if it can't get a full config=
uration that way, and can get a full configuration by running two separate =
state machines, it should.   We could add that when (c) appears, it should =
do a soft renumber to (c), deprecating the address(es) it got either from (=
a) or (b), but should maintain two state machines during the interim.

I don't have a strong preference.   I think you get better behavior with th=
e alternative, but the implementation is easier if we say that the client m=
aintains only one state machine.

I haven't read the draft in a while, so I realize that what I just wrote ma=
y be out of sync with what the draft currently says, but I think what I jus=
t described represents the two possible ways of addressing this concern, an=
d I am okay with either approach.   I think leaving it unspecified isn't a =
great solution, and addressing it with a single sentence as Tomek proposed =
will likely not be understood by many client implementors.


From nobody Tue Feb 10 19:39:37 2015
Return-Path: <Ted.Lemon@nominum.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 E74D81A1B53 for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 19:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 GxcvQZtUuEAL for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 19:39:34 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CDEE1A0040 for <dhcwg@ietf.org>; Tue, 10 Feb 2015 19:39:34 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 1AEB1DA029E for <dhcwg@ietf.org>; Wed, 11 Feb 2015 03:39:34 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D1B7553E084; Tue, 10 Feb 2015 19:39:33 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 10 Feb 2015 19:39:33 -0800
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com>
Date: Tue, 10 Feb 2015 22:39:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <20759D49-9CAB-42DD-A16A-B87D9E22E23E@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/YacKeQ7YlKtgdF3ARnYcXZBjjN8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 11 Feb 2015 03:39:36 -0000

On Feb 10, 2015, at 10:06 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Perhaps  we can add something regarding this and just explain the =
issue(s) and that it would be up to implementation to decide how best to =
proceed.

Sure.   Bear in mind that situations encountered rarely are precisely =
the ones that it's good to describe in the document so that people code =
for them and don't get surprised by them later.


From nobody Tue Feb 10 23:55:57 2015
Return-Path: <otroan@employees.org>
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 83C261A86EC for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 23:55:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 PcSyT6wr93F4 for <dhcwg@ietfa.amsl.com>; Tue, 10 Feb 2015 23:55:53 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B951A86EE for <dhcwg@ietf.org>; Tue, 10 Feb 2015 23:55:53 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 6103C61E9; Tue, 10 Feb 2015 23:55:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=dh/O0ifsNBVg+nOVwKTY5JUF3Cw=; b= HdmTCltU50jMocetQqy2eE3QSRg/uFksmLpQCbyn6TMCwv1ITiL7i67kDSu+yU5s lsirFq7ACALxibHgmh03xwRwQec5hIBXD1j4+CiVvUhyZMSM3fQzAWa2ZJPpqMg6 IC38QV/XD9FQZZ9BGkcsSj8XW9p5cO6m709g2KmvKzY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=cxDxoDXj7kt2ZhsuJrFrj/meR0 G+6WgglDoIhNZU7kNZiSiR8gyTA7O5690/wyJ+zwxKjFrdSx844repYu6u9vPbcF jc8aJXYQOyzLKKVdcRb1XUr6isho2wBoNkOVpUxELW/Ck5wmsFusabeW8H7RvXbS 6FRdjTSS9eMpkPXYw=
Received: from OTROAN-M-Q0RH.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 0CE0061CE; Tue, 10 Feb 2015 23:55:52 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by OTROAN-M-Q0RH.localdomain (Postfix) with ESMTP id CA1193E73513; Wed, 11 Feb 2015 08:55:52 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C7C60465-4F05-4C00-A94F-C150E7A1A95D"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com>
Date: Wed, 11 Feb 2015 08:55:52 +0100
Message-Id: <DD2DE556-485C-4C23-B370-AA785772E897@employees.org>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/A_QYQZWih1LT0bfjfJzLOoHX2sE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 11 Feb 2015 07:55:55 -0000

--Apple-Mail=_C7C60465-4F05-4C00-A94F-C150E7A1A95D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Ted,

> I must confess however, that I consider this a weakness to the whole =
proposal, and consequently I don't actually have advice.   It seems to =
me that you can have any of the following DHCP server behaviors:
>=20
> a: a DHCP server will offer IA_NA but not IA_PD
> b: a DHCP server will offer IA_PD but not IA_NA
> c: a DHCP server will offer both IA_PD and IA_NA if requested
>=20
> Suppose you have servers corresponding to (a), (b) and (c) configured =
on a particular network.   A client that attempts to get an IA_NA and an =
IA_PD may not succeed in contacting server c, perhaps because it is =
offline.   It could get full service from (a) and (b) combined, but =
we've said that that's not how DHCPv6 is supposed to work.   So it has =
to pick one.
>=20
> Now suppose (c) comes online and responds to a subsequent request, =
because the client has chosen one of (a) or (b) but is not satisfied.   =
In this case, the client has to either switch to (c) and lose whatever =
it got from (a) or (b), or else it has to continue with its existing =
configuration.   Presumably it will switch, because otherwise why would =
it have persisted in trying to get a new configuration?

it is hard to see why that isn't a misconfiguration.
you could make up the same failure scenario with other configuration =
options as well.

cheers,
Ole

--Apple-Mail=_C7C60465-4F05-4C00-A94F-C150E7A1A95D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU2wsIAAoJEFuJXizso86gQo0H/1+tkLlVkDNDcn4zAFarytUR
5fUH4tphcClxPXINTyY/qbcRHCFhKwwv12Em6O+8J7lkF5BOdiSt4+QKnYywrUx1
kbq836I4QUTo4enZ0VMdhS74Kcr8Tzh5enhBhrTurtUb88yGruL/C1cpL6VXuHXh
2lHqEpgvtEGbBlT04ZmGK/fZjoI2XH6RHD1ZUCUZe/aSBYtBJqacOs71q7Rwjmso
0NPRGZRk0cHgHf50fVlpj2UGDWz0ymT5h5W6Xqx4Q0vhFU6dfHIacAp5Jx8jq4XE
px/XLLyDcKI55EVeGu90TuUCUS/89XX0cXBZVlPXnfH8T2omH1jhbQ7PSSdZ9Ps=
=OOZ4
-----END PGP SIGNATURE-----

--Apple-Mail=_C7C60465-4F05-4C00-A94F-C150E7A1A95D--


From nobody Wed Feb 11 04:47:01 2015
Return-Path: <Ted.Lemon@nominum.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 66E7E1A8873 for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 04:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 lXe9A2bOQPyi for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 04:46:58 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0FA1A886A for <dhcwg@ietf.org>; Wed, 11 Feb 2015 04:46:57 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 9D57FDA023F for <dhcwg@ietf.org>; Wed, 11 Feb 2015 12:46:57 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6290C53E084; Wed, 11 Feb 2015 04:46:57 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 11 Feb 2015 04:46:57 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <DD2DE556-485C-4C23-B370-AA785772E897@employees.org>
Date: Wed, 11 Feb 2015 07:46:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <2DC5B8D9-16F2-4254-8BA4-4A2A2DF6D72F@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <DD2DE556-485C-4C23-B370-AA785772E897@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/OZAU29g-DX21nem-qZ41H805mXY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 11 Feb 2015 12:46:59 -0000

On Feb 11, 2015, at 2:55 AM, Ole Troan <otroan@employees.org> wrote:
> it is hard to see why that isn't a misconfiguration.
> you could make up the same failure scenario with other configuration =
options as well.

It could be that more than one administrative domain is offering service =
on the wire.  But I tend to agree that it's a bad way to configure =
things; the question is what the client does when things are configured =
that way.


From nobody Wed Feb 11 04:47:50 2015
Return-Path: <Ted.Lemon@nominum.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 20AAF1A888A for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 04:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 aJph_-4DyKCy for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 04:47:41 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 287681A8880 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 04:47:40 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 1C11BDA0234 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 12:47:40 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 0172753E084; Wed, 11 Feb 2015 04:47:40 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 11 Feb 2015 04:47:39 -0800
Content-Type: text/plain; charset="iso-2022-jp"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com>
Date: Wed, 11 Feb 2015 07:47:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/FypDjz61G0NfDxSplXOSiRPWpc4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 11 Feb 2015 12:47:43 -0000

On Feb 10, 2015, at 10:06 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Perhaps  we can add something regarding this and just explain the =
issue(s) and that it would be up to implementation to decide how best to =
proceed.

This is probably the right approach.


From nobody Wed Feb 11 09:06:47 2015
Return-Path: <internet-drafts@ietf.org>
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 449A21A8A1A; Wed, 11 Feb 2015 09:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ExfV8LBDhvMR; Wed, 11 Feb 2015 09:06:39 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BF61A8A50; Wed, 11 Feb 2015 09:04:46 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211170446.1045.11987.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 09:04:46 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/dtXlAEU2TA0FalE5OSrFukJquzk>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-privacy-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Feb 2015 17:06:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Privacy considerations for DHCPv6
        Authors         : Suresh Krishnan
                          Tomek Mrugalski
                          Sheng Jiang
	Filename        : draft-ietf-dhc-dhcpv6-privacy-00.txt
	Pages           : 14
	Date            : 2015-02-09

Abstract:
   DHCPv6 is a protocol that is used to provide addressing and
   configuration information to IPv6 hosts.  This document discusses the
   various identifiers used by DHCPv6 and the potential privacy issues.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-privacy/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-privacy-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 11 09:08:33 2015
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 9D5A91A1A36 for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 09:08:28 -0800 (PST)
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 o2Tloh3lSAwW for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 09:08:27 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A19581A8A1A for <dhcwg@ietf.org>; Wed, 11 Feb 2015 09:08:14 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id r20so18830023wiv.2 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 09:08:13 -0800 (PST)
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=7nePA3jTi6J+rU5Q1UDfBW3Q8C8GDe19KiTzNPFYSxI=; b=PEVz6KATdsls5iwWOCojCrJHuq6H3QRZwohlsYiCCZzTnWkziHP6HVTWAvy9Ja+yJ0 ynCXO0CJ49kGaagFbkah0Qm4qY9lAQ/O3P5GsEzZmVXw+tZEPXxQxYMQotkZMj5hfGUw Pw2uDzTP1nJte2lZJLYih7KXoPq0WJ4kovCwUM7pwj60QeFQfdpfy+LEBpsyVhMYe+Sy f8qaYuX9LaAkAvsMBhM2vzuSdo6xPlABv1GbKERi+h4F1bTZbdqMZo6JfC2qy9Yx7byi 6GFI33sC03nU1fG89/x9y50S3LV6QkWxZRKECJCg4O0vbONyH0Vg5ToMQWjpQi814X9t CTlg==
MIME-Version: 1.0
X-Received: by 10.194.175.39 with SMTP id bx7mr66059087wjc.22.1423674493253; Wed, 11 Feb 2015 09:08:13 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Wed, 11 Feb 2015 09:08:13 -0800 (PST)
In-Reply-To: <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com>
Date: Wed, 11 Feb 2015 09:08:13 -0800
X-Google-Sender-Auth: npDN8275nxnGczASokQzBC9l0_U
Message-ID: <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/TLoL_PfsHcphFsFI5uCiimh_ssY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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, 11 Feb 2015 17:08:29 -0000

(Jumping to this point)

At Wed, 11 Feb 2015 07:47:38 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > Perhaps  we can add something regarding this and just explain the issue(s) and that it would be up to implementation to decide how best to proceed.
>
> This is probably the right approach.

I think it works for me, too.

Commenting on a few more points that may be related:

At Wed, 11 Feb 2015 03:06:29 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> Just to be clear, the draft only recommends that clients use a
> single state machine and it makes that better because it offers
> clients the ability to Renew more than the IAs they got (and to keep
> renewal times in sync). Nothing in the draft requires that a client
> only maintain one state machine.

Hmm, that intent was not clear, at least to me.  Certainly, it doesn't
explicitly prohibit other options than the single DHCPv6 session, but
I basically interpret the overall tone of Section 4 that way.  One
background reason for that is probably because it just talks about
drawbacks of other options and then leads to the text pasted below
(this is also related one of my other comments, which was rejected, to
which I wouldn't be opposed at this point).

> The key text is:
>
>       We have chosen to recommend that clients use the remaining option:
>       a single DHCP session and state machine.  The client maintains a
>       single session and state machine. It uses the best configuration it
>       is able to obtain during any configuration exchange.   But it
>       continues, in each subsequent configuration exchange, to request all
>       the configuration information it is programmed to try to obtain,
>       including any stateful configuration options for which no results
>       were returned in previous exchanges.

If this is intended to mean clients can choose (or may end up
choosing) other options, the intent wasn't clear to me either.

If, for example, section 4 was revised to read like this, I think my
concern will be addressed:

  There can be several choices on how to handle multiple IA options
  (and, specifically IA_NA and IA_PD) including 1-3.  All choices
  have their own pors and cons, but this document focuses on choice #3
  (using a single DHCPv6 session for both IA_NA and IA_PD) because
  it's deemed to work best for common cases of the mixed use of IA_NA
  and IA_PD.  But this document doesn't exclude other choices.  Also,
  in some corner cases it may not feasible to maintain a single DHCPv6
  session for both IA_NA and IA_PD.  These general and corner cases
  are beyond the scope of the discussion and will be deferred to the
  next revision of the base DHCPv6 specification (i.e., 3315bis).

--
JINMEI, Tatuya


From nobody Wed Feb 11 09:47:07 2015
Return-Path: <tomasz.mrugalski@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 D19751A1A3D for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 09:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 aDQIdsvEeeW7 for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 09:47:02 -0800 (PST)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D5B91A007D for <dhcwg@ietf.org>; Wed, 11 Feb 2015 09:47:02 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id l61so4977260wev.13 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 09:47:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Hgc3V35nfrMwGAX8vQSxx3xc2F1CQKToz0KXpkry7PE=; b=N9xnlnTqqyGTovNrvjdS1Nv7+jJupfxcXPbhGJzbwiVFzZgPgFTvrAG3mnTToiD5fU UssUsVRosRBW+axQXdSRfPvSMFiMf8Y3NDzgMrnqg9V7Bc/O+RfUgB/5YPacX87njlzG MN3sckC0zCALSsNpXS3T9hcXnjofdREMCE0KkszvIBhnUolJzXhOgmuDvb92ToeK9zcf kVNMQdQvA5DSXUMRCDjzo/SMBtcmsRd4L74rOaL39UAi+OHpeaOTO8wT5PCd8PZc4atT zNEbKxCv4A6/jFLXLA72ESNDxqAePurO8JkCfTVS3FKEiYQWm/SLGZxjBaohBvz8ppGU YzoA==
X-Received: by 10.180.88.234 with SMTP id bj10mr7977360wib.81.1423676820815; Wed, 11 Feb 2015 09:47:00 -0800 (PST)
Received: from [10.0.0.100] ([109.107.11.157]) by mx.google.com with ESMTPSA id n1sm24196851wib.11.2015.02.11.09.46.59 for <dhcwg@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Feb 2015 09:46:59 -0800 (PST)
Message-ID: <54DB958F.1080406@gmail.com>
Date: Wed, 11 Feb 2015 18:46:55 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1B7A8322@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B7A8322@xmb-rcd-x04.cisco.com>
X-TagToolbar-Keys: D20150211184655031
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pORJn7HUPu9coX7HaGzsP-CILqM>
Subject: [dhcwg] IETF-92 (Dallas) DHC WG Session & Agenda Items - Reminder
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, 11 Feb 2015 17:47:05 -0000

This is just a friendly reminder that we're awaiting for the slot
requests. If you have a draft that requires face to face time, feel free
to request a slot.

We'll have only 1 hour for the regular DHC presentations, so the agenda
may be full if you send your request too late.

Tomek

On 09.01.2015 16:46, Bernie Volz (volz) wrote:
> Hi:
> 
>  
> 
> We will only request a 2 hour time slot for the DHC WG meeting for the
> Dallas IETF. We also plan to use about half the time for work on RFC
> 3315 bis (draft-dhcwg-dhc-rfc3315bis), instead of a separate DHCPv6bis
> team meeting as we hope to have the WG adopt the document before the
> Dallas IETF.
> 
>  
> 
> While it is still a bit more than 2 months away, we are starting to
> collect agenda items for IETF-92’s DHC WG session (and please submit
> your requests soon as we will only have about 1 hour for other requests).
> 
>  
> 
> Please send us (dhc-chairs@tools.ietf.org
> <mailto:dhc-chairs@tools.ietf.org>) requests for sessions and include:
> 
>  
> 
> Name of session:
> 
> Name of draft(s):
> 
> Time requested:
> 
> Presenter name(s):
> 
> Brief description of what issues need discussing and what you hope to
> accomplish by presenting (please focus on open issues, rather than a
> status update):
> 
>  
> 
>  
> 
> Also, if you have individual drafts to present, you may want to consider
> presenting them in INTAREA to get wider involvement by the community.
> Those interested in DHC WG, or other INTAREA WGs, are strongly
> encouraged to attend the INTAREA session.
> 
>  
> 
> More details about the Dallas IETF can be found at
> http://www.ietf.org/meeting/92/index.html.
> 
>  
> 
> -        Bernie & Tomek
> 
>  
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 


From nobody Wed Feb 11 09:55:36 2015
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 C4E791A19E5 for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 09:55:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.422
X-Spam-Level: 
X-Spam-Status: No, score=0.422 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 m742GsQqo8Sk for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 09:55:33 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 018A21A0AC8 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 09:55:33 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id w55so5091497wes.5 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 09:55:31 -0800 (PST)
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=bGDKsQ9JXpN7Sl6F+ZYdqzgUsByKTZH3/io1fWH9mNU=; b=l8ROB9Z7dUD38bXgnJy0a2wgXZ1XiXNM56gc8Q8KSLz4Nw/KbGAqhZxeDOVRc9Kclt o48mUZybh8hbkYIXms/3S0OBnzDwJQ3F9bAnE1hQu5R8oVgy3IyfNUuta5xJwm7Mclyv NwyMvhkP42JGINBSUdqTDxxpmGOU4WUFOalmGqqzJGU9TW5dj2pK/kaVPrRyeMgKdDZu QhTqnI6xAw2sC4o1etWQA83YtDXLTYZiDAxpjJGMfKK4XcsC8y0NsGtdDghHst32pxfG E8sprVCpWOmRTt7IGno9GD30EMchr8oFWKcqIc0gg74eKT1A8nFkOyOgG9kxhwq1tnbS KMIw==
MIME-Version: 1.0
X-Received: by 10.194.22.6 with SMTP id z6mr58647888wje.146.1423677331526; Wed, 11 Feb 2015 09:55:31 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Wed, 11 Feb 2015 09:55:31 -0800 (PST)
In-Reply-To: <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com>
Date: Wed, 11 Feb 2015 09:55:31 -0800
X-Google-Sender-Auth: E59TdcJllRshHjjaBObue3Mm6mw
Message-ID: <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ZFb0zhkwAOnl9oTgR5c0W66Vx7A>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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, 11 Feb 2015 17:55:35 -0000

At Mon, 9 Feb 2015 14:30:03 -0500,
Ted Lemon <mellon@fugue.com> wrote:

> > What I wanted to see was an explanation of "why we need this
> > mechanism".
>
> In my mind, the answer to this is that at present no mechanism exists for=
 security DHCP messages between servers and clients that does not have a se=
rious key distribution problem.   By using public-key-based authentication,=
 we provide a mechanism for securing such messages that can be reasonably d=
eployed without the key distribution problems inherent in the shared-secret=
-based authentication mechanism specified in RFC 3315, either using some fo=
rm of PKI or else Trust-on-first-use (TOFU).
>
> Why do we need to say more than this?

(Trying to recall the original discussion of "why") because, I guess,
a brief statement like this is too high level and is not very clear
about specifically what kind of problem this mechanism solves and why
it's better than an existing one(s).

Authenticating the server on a client using TOFU is probably the
clearest case: we can eliminate the need for manual key distribution
or exchanging keys in plain text at the risk of getting attacked on
first use.

Other cases are not that obvious: using a server certificate on the
client will require some tricky considerations (mainly due to the
chicken-and-egg nature - while it can be addressed as you noted in
your comment, but that wouldn't be obvious); if you think about some
more details, you'd realize using TOFU for authenticating the client
on a server doesn't make sense; if you need to manually configure
clients's public keys on a server, the operational cost wouldn't be
much different from the existing authentication mechanism as of
RFC3315; yet it wouldn't be too obvious how to securely and reliably
publish public keys or certificates of arbitrary clients.

Section 7 of the current draft is an attempt to address these
questions, but as you rightly pointed out, they are largely
speculative and can be controversial or even considered plain wrong
depending on expected assumptions.

Based on the conversation so far, I can think of the following options
for the next step:

1. revise Section 7 to something we can agree on.  it might not be
   feasible because of its speculative nature.  But if we can make it,
   that would be the most reasonable next step for a post WGLC
   document.
2. if the sense of the wg has changed and they now don't see the need
   for explaining why we need it beyond the very high level view like
   the you showed above, just remove Section 7 and move forward.  As I
   said in my previous response, I personally don't like this option,
   but if that's the new consensus of the wg I'm willing to accept it.
3. another radical idea: narrow down the scope of this document to the
   case of "TOFU + server authentication on a client".  I believe
   everyone understands the merit of this use case (to the extent of
   its own risks) and agrees the proposed solution is a good way to
   achieve it.  If we see clearer need for other cases where a good
   solution would be a mechanism like the one described in this
   document, then we can publish another document at that point by
   extending this one.

--
JINMEI, Tatuya


From nobody Wed Feb 11 11:37:41 2015
Return-Path: <mellon@fugue.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 104651A1BCE for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 11:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 JEz5ukfnj9Nj for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 11:37:35 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 3204C1A1A13 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 11:37:01 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 19D4623803D1; Wed, 11 Feb 2015 14:36:59 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com>
Date: Wed, 11 Feb 2015 14:36:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/3q9iFi450gEjc0y4VDgHMuCBsJA>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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, 11 Feb 2015 19:37:37 -0000

On Feb 11, 2015, at 12:55 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> 1. revise Section 7 to something we can agree on.  it might not be
>   feasible because of its speculative nature.  But if we can make it,
>   that would be the most reasonable next step for a post WGLC
>   document.

I think this is a lot of work with no clear benefit, since we can't =
actually know how people will use this until we make it possible for =
them to try it.

> 2. if the sense of the wg has changed and they now don't see the need
>   for explaining why we need it beyond the very high level view like
>   the you showed above, just remove Section 7 and move forward.  As I
>   said in my previous response, I personally don't like this option,
>   but if that's the new consensus of the wg I'm willing to accept it.

Thanks, this would be my preference.

> 3. another radical idea: narrow down the scope of this document to the
>   case of "TOFU + server authentication on a client".  I believe
>   everyone understands the merit of this use case (to the extent of
>   its own risks) and agrees the proposed solution is a good way to
>   achieve it.  If we see clearer need for other cases where a good
>   solution would be a mechanism like the one described in this
>   document, then we can publish another document at that point by
>   extending this one.

I don't think this makes sense, because the point of the document is =
just to describe a mechanism, not suggest ways for using it.   I think =
item 3 above is a good idea, but should be pursued in a separate =
document, probably as a result of some experience from the field.


From nobody Wed Feb 11 18:16:50 2015
Return-Path: <jiangsheng@huawei.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 248051A8A55 for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 18:16:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ENqXiGcvoGSU for <dhcwg@ietfa.amsl.com>; Wed, 11 Feb 2015 18:16:37 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 838271A8A44 for <dhcwg@ietf.org>; Wed, 11 Feb 2015 18:16:36 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSN63605; Thu, 12 Feb 2015 02:16:34 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Feb 2015 02:16:34 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.106]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Thu, 12 Feb 2015 10:16:29 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <mellon@fugue.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
Thread-Index: AQHQQx2McUj9f9+oTEe7lmci6/QZ1ZzoKFcAgAAI64CAAwpAgIAAHFkAgAD0TiA=
Date: Thu, 12 Feb 2015 02:16:28 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com>
In-Reply-To: <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/QuhTQaO2SpAqK5WFDQIsw2NePm0>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Thu, 12 Feb 2015 02:16:47 -0000

Pj4gMi4gaWYgdGhlIHNlbnNlIG9mIHRoZSB3ZyBoYXMgY2hhbmdlZCBhbmQgdGhleSBub3cgZG9u
J3Qgc2VlIHRoZSBuZWVkDQo+PiAgIGZvciBleHBsYWluaW5nIHdoeSB3ZSBuZWVkIGl0IGJleW9u
ZCB0aGUgdmVyeSBoaWdoIGxldmVsIHZpZXcgbGlrZQ0KPj4gICB0aGUgeW91IHNob3dlZCBhYm92
ZSwganVzdCByZW1vdmUgU2VjdGlvbiA3IGFuZCBtb3ZlIGZvcndhcmQuICBBcyBJDQo+PiAgIHNh
aWQgaW4gbXkgcHJldmlvdXMgcmVzcG9uc2UsIEkgcGVyc29uYWxseSBkb24ndCBsaWtlIHRoaXMg
b3B0aW9uLA0KPj4gICBidXQgaWYgdGhhdCdzIHRoZSBuZXcgY29uc2Vuc3VzIG9mIHRoZSB3ZyBJ
J20gd2lsbGluZyB0byBhY2NlcHQgaXQuDQo+DQo+VGhhbmtzLCB0aGlzIHdvdWxkIGJlIG15IHBy
ZWZlcmVuY2UuDQoNClNlcGFyYXRpbmcgdGhlIHVzZSBjYXNlcyBjb3VsZCBtYWtlIHVzIG1vcmUg
Zm9jdXMgb24gdGhlIHNvbHV0aW9uIGFuZCBwcm90b2NvbCBwcm9jZWR1cmVzLiBXZSBjb3VsZCBh
bHdheXMgY29tZSBiYWNrIGluIHRoZSBmdXR1cmUgdG8gc3VtbWFyaXplIHRoZSB1c2UgY2FzZXMg
aW4gdGhlIHByYWN0aWNlLiBNYXliZSwgdGhlIGluZHVzdHJ5IG9yIG1hcmtldCBjb3VsZCBkZXZl
bG9wIG1vcmUgY2FzZXMgdGhhbiB3ZSBjYW4gY2xlYXJseSBkZXNjcmliZSBmb3Igbm93Lg0KDQpC
ZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCj4+IDMuIGFub3RoZXIgcmFkaWNhbCBpZGVhOiBuYXJy
b3cgZG93biB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudCB0byB0aGUNCj4+ICAgY2FzZSBvZiAi
VE9GVSArIHNlcnZlciBhdXRoZW50aWNhdGlvbiBvbiBhIGNsaWVudCIuICBJIGJlbGlldmUNCj4+
ICAgZXZlcnlvbmUgdW5kZXJzdGFuZHMgdGhlIG1lcml0IG9mIHRoaXMgdXNlIGNhc2UgKHRvIHRo
ZSBleHRlbnQgb2YNCj4+ICAgaXRzIG93biByaXNrcykgYW5kIGFncmVlcyB0aGUgcHJvcG9zZWQg
c29sdXRpb24gaXMgYSBnb29kIHdheSB0bw0KPj4gICBhY2hpZXZlIGl0LiAgSWYgd2Ugc2VlIGNs
ZWFyZXIgbmVlZCBmb3Igb3RoZXIgY2FzZXMgd2hlcmUgYSBnb29kDQo+PiAgIHNvbHV0aW9uIHdv
dWxkIGJlIGEgbWVjaGFuaXNtIGxpa2UgdGhlIG9uZSBkZXNjcmliZWQgaW4gdGhpcw0KPj4gICBk
b2N1bWVudCwgdGhlbiB3ZSBjYW4gcHVibGlzaCBhbm90aGVyIGRvY3VtZW50IGF0IHRoYXQgcG9p
bnQgYnkNCj4+ICAgZXh0ZW5kaW5nIHRoaXMgb25lLg0KPg0KPkkgZG9uJ3QgdGhpbmsgdGhpcyBt
YWtlcyBzZW5zZSwgYmVjYXVzZSB0aGUgcG9pbnQgb2YgdGhlIGRvY3VtZW50IGlzIGp1c3QgdG8N
Cj5kZXNjcmliZSBhIG1lY2hhbmlzbSwgbm90IHN1Z2dlc3Qgd2F5cyBmb3IgdXNpbmcgaXQuICAg
SSB0aGluayBpdGVtIDMgYWJvdmUgaXMNCj5hIGdvb2QgaWRlYSwgYnV0IHNob3VsZCBiZSBwdXJz
dWVkIGluIGEgc2VwYXJhdGUgZG9jdW1lbnQsIHByb2JhYmx5IGFzIGENCj5yZXN1bHQgb2Ygc29t
ZSBleHBlcmllbmNlIGZyb20gdGhlIGZpZWxkLg0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+ZGhjd2cgbWFpbGluZyBsaXN0DQo+ZGhjd2dAaWV0
Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo=


From nobody Thu Feb 12 06:38:39 2015
Return-Path: <Ted.Lemon@nominum.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 7A1F11A891C for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 3_-8yKDolPGb for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:38:21 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 608F51A88F8 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 06:38:21 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 11DC2DA02DF for <dhcwg@ietf.org>; Thu, 12 Feb 2015 14:38:21 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C45B653E084; Thu, 12 Feb 2015 06:38:20 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 12 Feb 2015 06:38:20 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <54DCB9FC.5020400@gmail.com>
Date: Thu, 12 Feb 2015 09:38:15 -0500
Content-Transfer-Encoding: 7bit
Message-ID: <5C09BD25-F0A8-40C1-855B-4F1A3CB0A758@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com>
To: Marcin Siodelski <msiodelski@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Dp7lDdJTCIjU5wLn-KL4jEPmdHg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 14:38:30 -0000

On Feb 12, 2015, at 9:34 AM, Marcin Siodelski <msiodelski@gmail.com> wrote:
>   Resetting the state machine and continuing to send Solicit messages
>   may result in the client never completing DHCP and is generally not
>   considered a good solution.  It can also result in a packet storm if
>   the client does not appropriately rate limit its sending of Solicit
>   messages.

Or if there are very many DHCP clients on the network.


From nobody Thu Feb 12 06:40:23 2015
Return-Path: <msiodelski@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 8C99F1A893E for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 h8cVlp8bA_Fk for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:40:17 -0800 (PST)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C92D1A88E2 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 06:40:16 -0800 (PST)
Received: by mail-lb0-f177.google.com with SMTP id z11so9888649lbi.8 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 06:40:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7aO20spE0m7YdmbituoqCxLbx4lWo5L2Wb9+HEtdUhc=; b=HWmYRkauoY/vp6EQLmtEqeC1RuVeA9W/4FK3Hjwa5IJYYDXCR1Ii5tBBTcarusvSw6 XYKRuCyQ1mNSVtRoE1QbrrGacWjeEk2tKyZAfnoqE61kyQ0R+Y5lzR3bemdwa4T7y/JO OT6jyw38n0IJ8P2jayPxmsKnMhJf7AygBqjzHcZAQSKhZDp1W3V2jL2FjTAoG7cnkpa/ yWMFLvfVi6qacixKhJNwBxL7i6MTVcpZnvxN+dHoslw5sFgUVAM2SmeWsn4OjtG6Ki+/ P4SxhRt86HF4e89InKOlj590wwprqdDb39IRRRfcMxvEFHy8+SzGqnHRwDIz1eJXe70X UyWA==
X-Received: by 10.112.170.72 with SMTP id ak8mr3404224lbc.95.1423752015116; Thu, 12 Feb 2015 06:40:15 -0800 (PST)
Received: from [192.168.8.101] (apn-46-169-65-191.dynamic.gprs.plus.pl. [46.169.65.191]) by mx.google.com with ESMTPSA id te7sm809171lbb.3.2015.02.12.06.40.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 06:40:14 -0800 (PST)
Message-ID: <54DCBB4A.8050005@gmail.com>
Date: Thu, 12 Feb 2015 15:40:10 +0100
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <5C09BD25-F0A8-40C1-855B-4F1A3CB0A758@nominum.com>
In-Reply-To: <5C09BD25-F0A8-40C1-855B-4F1A3CB0A758@nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6orcRVwnIdlDbgP5vLyocuT50aA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 14:40:21 -0000

On 12/02/15 15:38, Ted Lemon wrote:
> On Feb 12, 2015, at 9:34 AM, Marcin Siodelski <msiodelski@gmail.com> wrote:
> >   Resetting the state machine and continuing to send Solicit messages
> >   may result in the client never completing DHCP and is generally not
> >   considered a good solution.  It can also result in a packet storm if
> >   the client does not appropriately rate limit its sending of Solicit
> >   messages.
>
> Or if there are very many DHCP clients on the network.
>
duly noted


From nobody Thu Feb 12 06:45:46 2015
Return-Path: <Ted.Lemon@nominum.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 71FB31A88BE for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 NbhYDOqrV5To for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:45:44 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 984DD1A8A90 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 06:45:27 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 8D0C5DA02DC for <dhcwg@ietf.org>; Thu, 12 Feb 2015 14:45:27 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 5B5D453E084; Thu, 12 Feb 2015 06:45:27 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 12 Feb 2015 06:45:27 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <54DCBB4A.8050005@gmail.com>
Date: Thu, 12 Feb 2015 09:45:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <507FE1A5-4998-4CCE-8B15-97D650A3ECFB@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <5C09BD25-F0A8-40C1-855B-4F1A3CB0A758@nominum.com> <54DCBB4A.8050005@gmail.com>
To: Marcin Siodelski <msiodelski@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Lm4r8LvmoK-qjyXH_f408Ajwxgg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 14:45:45 -0000

On Feb 12, 2015, at 9:40 AM, Marcin Siodelski <msiodelski@gmail.com> =
wrote:
>> Or if there are very many DHCP clients on the network.
>>=20
> duly noted

The point being that this gets into the rate limiting problem that RFC =
7083 addresses; it might be worth putting a reference to RFC 7083 here =
and advising implementors who go with this option that they must also =
implement RFC 7083.


From nobody Thu Feb 12 09:31:48 2015
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 602321A0389 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 09:31:40 -0800 (PST)
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 pIFsqXcacA2L for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 09:31:38 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22E7C1A036E for <dhcwg@ietf.org>; Thu, 12 Feb 2015 09:31:34 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so6148262wid.5 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 09:31:32 -0800 (PST)
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=OWMkAPS8uIg8la3F86hdCfCM+LYvb5dxRjawLqE7DEw=; b=VvwzlBFn/hEC4ea3xaCEi09SbGkKtJnHwEzEZ14XuvM1If5Qo63uvOS+hvH4eh0YH0 67LqO6w3fx6jUvw2z2IW1KWdP9Kn3R7SVLpwNO+Z/RNpoLbUHv3JJwzQFHUt3W48iduz 5BbuM4PgnozwD9ychSTZaJWtSi8OvKjHIt9/S7BiYSe4L6gfd9Al/zfkltWe29aI08uC 8rs6+WlP2mFqdPUws7SaPZ4mHcNQO/FvJsazQGJSfhO4PMhtSilJKyOyRfxMkbvIEwKL P+mgug22PklFuSsUbRiSVdljqAzoOtuDsY6sDOs/8MI0vSs0iKd2s8Kk8OxdQoULVT9G 9y/w==
MIME-Version: 1.0
X-Received: by 10.180.73.239 with SMTP id o15mr8364987wiv.14.1423762292769; Thu, 12 Feb 2015 09:31:32 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Thu, 12 Feb 2015 09:31:32 -0800 (PST)
In-Reply-To: <54DCB9FC.5020400@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com>
Date: Thu, 12 Feb 2015 09:31:32 -0800
X-Google-Sender-Auth: wtp65ufnXpnMAlvMQ_-Am0_ywsc
Message-ID: <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Marcin Siodelski <msiodelski@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ME741Wp8Ur2-ipHBNxcI1KE5ZI0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 17:31:40 -0000

At Thu, 12 Feb 2015 15:34:36 +0100,
Marcin Siodelski <msiodelski@gmail.com> wrote:

> As a result of this discussion, we have come up with the following text
> for the section 4. This new text is now being included in the version
> -11 of the draft, but we're holding off the publication until we hear
> from you. However, it would be great if you could review and respond
> today, so as we can publish it and meet the deadlines we have set with Ted.

Thanks, it seems to address my concern.

One editorial point: the added paragraph seems to be mostly a verbatim
copy of my summary text and looks a bit awkward if placed in the
middle of the section.  For example, the first sentence looks
redundant (the section already mentioned that there are several
choices).

And, one minor nit (an error from my own text):

>    choices.  Also, in some corner cases it may not feasible to maintain

s/may not feasible/may not be feasible/

Combining these, I suggest revising the paragraph as follows:

   While all choices have their own pros and cons, we recommend and
   focus on choice 3 for this document because it is deemed to work
   best for common cases of the mixed use of IA_NA and IA_PD.  But
   this document does not exclude other choices.  Also, in some corner
   cases it may not be feasible to maintain a single DHCPv6 session
   for both IA_NA and IA_PD.  These corner cases are beyond the scope
   of this document and may depend on the network in which the client
   (CER) is designed to operate and on the functions the client is
   required to perform.

Also, although it doesn't seem to be critical in terms of my main
point and I wouldn't consider it a blocking issue, this paragraph is
not easy to understand to me:

>    The single session and state machine allows the client to use the
>    best configuration it is able to obtain from a single DHCP server
>    during the configuration exchange.  If the server is not configured
>    to deliver the entire configuration requested by the client, the
>    client could continue to operate using the configuration received.
>    But ideally it then continues, in each subsequent configuration
>    exchange, to request all the configuration information it is
>    programmed to try to obtain, including any stateful configuration
>    options for which no results were returned in previous exchanges.
>    However, this is difficult with the current DHCPv6 specifications.

Does it try to say something like this?

    The single session and state machine allows the client to use the
    best configuration it is able to obtain from a single DHCP server
    during the configuration exchange.  Note, however, that the server
    may not be configured to deliver the entire configuration
    requested by the client.  In that case the client could continue
    to operate only using the configuration received, even if other
    servers can provide the missing configuration.  In practice,
    especially in the case of handling IA_NA and IA_PD, this situation
    should be rare or a temporary operational error.  So, it is more
    likely for the client to get all configuration if it continues, in
    each subsequent configuration exchange, to request all the
    configuration information it is programmed to try to obtain,
    including any stateful configuration options for which no results
    were returned in previous exchanges.

    One major issue of this last approach is that it is difficult to
    allow it with the current DHCPv6 specifications; in some cases
    it is not clear enough, and in other cases existing restrictions
    can make it impossible.  This document introduces some
    clarifications and small modifications to the current
    specification to address this concern.

(The second paragraph is my attempt of rephrasing the very last
sentence of the original paragraph based on my the seeming intent of
it)

If so, and if you think my text is clearer, please feel free to use
it.  If you believe the original text is clear enough (and especially
if others also think so), I'm okay with keeping the original
paragraph.

--
JINMEI, Tatuya


From nobody Thu Feb 12 09:56:40 2015
Return-Path: <msiodelski@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 335391A1A54 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 09:56:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 UB9sxcshJN8a for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 09:56:37 -0800 (PST)
Received: from mail-la0-f45.google.com (mail-la0-f45.google.com [209.85.215.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFB161A00FE for <dhcwg@ietf.org>; Thu, 12 Feb 2015 09:56:36 -0800 (PST)
Received: by labpn19 with SMTP id pn19so11720661lab.4 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 09:56:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=J0ak0jfgCYNoagk0qBGPaeuDKpAAPljGRSG4h5ImBCA=; b=zjYD9c/CRBwYYIY+sROSOErNoUG5jbOvtWsYXPQD/hD9FriThZEMSvqnQFYSFRkiGK vhsYiJEWqDfo1v1yfe382uMjwKwY6jp5uH+BYNX9t7iZTSog8WjEdAZWPDh1LtCxHu1t hNRC2zo6WJdF+n3aQbJd35thrpTsQBw+tZlOiT4Ie6tWW79OzIUfAcxe57YmzF+B/6Vl L/MXvZjbRFHOB+hn3eqD9JKFvg/iOzD4M9lvM8MA4apjoXJGtWnQyB97fxmr1CMdLIc3 qTxgTy506gbHYfRZoz08lk76yiT8S+umaOPFB/Mhl3RAd+7ehl1pIWmwOzGlDo+xFYpY 107Q==
X-Received: by 10.112.150.98 with SMTP id uh2mr4387191lbb.92.1423763794894; Thu, 12 Feb 2015 09:56:34 -0800 (PST)
Received: from [192.168.8.100] (apn-77-115-62-249.dynamic.gprs.plus.pl. [77.115.62.249]) by mx.google.com with ESMTPSA id d6sm896493lbp.16.2015.02.12.09.56.25 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 09:56:34 -0800 (PST)
Message-ID: <54DCE942.9080605@gmail.com>
Date: Thu, 12 Feb 2015 18:56:18 +0100
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com>
In-Reply-To: <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/E-sTgBu8Sxex6E4tszFWjmAz6lc>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 17:56:39 -0000

On 12/02/15 18:31, 神明達哉 wrote:
> At Thu, 12 Feb 2015 15:34:36 +0100,
> Marcin Siodelski <msiodelski@gmail.com> wrote:
>
> > As a result of this discussion, we have come up with the following text
> > for the section 4. This new text is now being included in the version
> > -11 of the draft, but we're holding off the publication until we hear
> > from you. However, it would be great if you could review and respond
> > today, so as we can publish it and meet the deadlines we have set
> with Ted.
>
> Thanks, it seems to address my concern.
>

That's great!

> One editorial point: the added paragraph seems to be mostly a verbatim
> copy of my summary text and looks a bit awkward if placed in the
> middle of the section.  For example, the first sentence looks
> redundant (the section already mentioned that there are several
> choices).
>
> And, one minor nit (an error from my own text):
>
> >    choices.  Also, in some corner cases it may not feasible to maintain
>
> s/may not feasible/may not be feasible/
>
> Combining these, I suggest revising the paragraph as follows:
>
>    While all choices have their own pros and cons, we recommend and
>    focus on choice 3 for this document because it is deemed to work
>    best for common cases of the mixed use of IA_NA and IA_PD.  But
>    this document does not exclude other choices.  Also, in some corner
>    cases it may not be feasible to maintain a single DHCPv6 session
>    for both IA_NA and IA_PD.  These corner cases are beyond the scope
>    of this document and may depend on the network in which the client
>    (CER) is designed to operate and on the functions the client is
>    required to perform.
>

That looks ok to me.

> Also, although it doesn't seem to be critical in terms of my main
> point and I wouldn't consider it a blocking issue, this paragraph is
> not easy to understand to me:
>
> >    The single session and state machine allows the client to use the
> >    best configuration it is able to obtain from a single DHCP server
> >    during the configuration exchange.  If the server is not configured
> >    to deliver the entire configuration requested by the client, the
> >    client could continue to operate using the configuration received.
> >    But ideally it then continues, in each subsequent configuration
> >    exchange, to request all the configuration information it is
> >    programmed to try to obtain, including any stateful configuration
> >    options for which no results were returned in previous exchanges.
> >    However, this is difficult with the current DHCPv6 specifications.
>
> Does it try to say something like this?
>
>     The single session and state machine allows the client to use the
>     best configuration it is able to obtain from a single DHCP server
>     during the configuration exchange.  Note, however, that the server
>     may not be configured to deliver the entire configuration
>     requested by the client.  In that case the client could continue
>     to operate only using the configuration received, even if other
>     servers can provide the missing configuration.  In practice,
>     especially in the case of handling IA_NA and IA_PD, this situation
>     should be rare or a temporary operational error.  So, it is more
>     likely for the client to get all configuration if it continues, in
>     each subsequent configuration exchange, to request all the
>     configuration information it is programmed to try to obtain,
>     including any stateful configuration options for which no results
>     were returned in previous exchanges.
>
>     One major issue of this last approach is that it is difficult to
>     allow it with the current DHCPv6 specifications; in some cases
>     it is not clear enough, and in other cases existing restrictions
>     can make it impossible.  This document introduces some
>     clarifications and small modifications to the current
>     specification to address this concern.
>
> (The second paragraph is my attempt of rephrasing the very last
> sentence of the original paragraph based on my the seeming intent of
> it)
>
> If so, and if you think my text is clearer, please feel free to use
> it.  If you believe the original text is clear enough (and especially
> if others also think so), I'm okay with keeping the original
> paragraph.
>

We will discuss this with Bernie and decide to what extent we will use
your text.


Many thanks for the prompt response!

Marcin


From nobody Thu Feb 12 09:57:17 2015
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 558631A00FE for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 09:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.422
X-Spam-Level: 
X-Spam-Status: No, score=0.422 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 5f26Yks63zjH for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 09:57:13 -0800 (PST)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E30A41A1AB1 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 09:57:07 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id x13so11801148wgg.1 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 09:57:06 -0800 (PST)
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=kTlN+eVAcC/7xDMPXNScEFUwD1NCKQqNhtWEmA38U+k=; b=nifFSsuFL69swhRWPmm4AO8dRHShzY4c0txW5C2eIX0WprUDF5n4bTdMADLlOyZMJw Ib5HActC2YARyv4HU/MueGzUzV5a7VhbXsIriiWtpaYSkvx6v4tAQfcNTGx4WDm25jAX +ngrzyGNnzLtCXxlXFbNGg5mY4S6Ly9rZNgGd71W1t26TOi3f3dji7sGVJkhyQtJ2mUT v60dCvcG3Ee3agdFHtxiLYtNsXd6eatx2R4ycPglahD61CRbpa5+scfjMe2ggmdKAKFA RPCE020m50MrmKM78BNMRWFkxCTjnUSqxLKf7+ihPkHM8H9ewdVg+bGlQOMvJMj63cT0 GS3A==
MIME-Version: 1.0
X-Received: by 10.194.78.72 with SMTP id z8mr10757477wjw.0.1423763826579; Thu, 12 Feb 2015 09:57:06 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Thu, 12 Feb 2015 09:57:06 -0800 (PST)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com>
Date: Thu, 12 Feb 2015 09:57:06 -0800
X-Google-Sender-Auth: a1YobYUvaW60iGhVIx3YUIbOguk
Message-ID: <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/RaDXWj7lnd890JUSmPJ4V1NpqTA>
Cc: dhcwg <dhcwg@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Thu, 12 Feb 2015 17:57:15 -0000

At Thu, 12 Feb 2015 02:16:28 +0000,
Sheng Jiang <jiangsheng@huawei.com> wrote:

> >> 2. if the sense of the wg has changed and they now don't see the need
> >>   for explaining why we need it beyond the very high level view like
> >>   the you showed above, just remove Section 7 and move forward.  As I
> >>   said in my previous response, I personally don't like this option,
> >>   but if that's the new consensus of the wg I'm willing to accept it.
> >
> >Thanks, this would be my preference.
>
> Separating the use cases could make us more focus on the solution and pro=
tocol procedures. We could always come back in the future to summarize the =
use cases in the practice. Maybe, the industry or market could develop more=
 cases than we can clearly describe for now.

To be clear: my current position is still against this option.  I'm
always in the camp of "problem first, then solution".  And that's
also the case of this document since around May 2014:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15520.html

Trying to publish a random idea in a (pretty) formal document like RFC
just because someone thinks it may be useful someday looks to me like
throwing random spaghetti to the wall with the wish that someone may
consider it a fine art.  Maybe that's how "innovations" work, and I
may be in the minority.  But at least around last May our consensus
should have been against that approach, hence the current organization
of the draft.  Just because it triggers a hot discussion doesn't
automatically dismiss the original concern and justify ignoring it.

Unless and until we see a clear wg consensus that we now allow it to
ship even if no one can explain what kind of problem it will solve, I
object to moving forward with just removing this section.  And, IMO,
this consensus change will require another round of WGLC.

--
JINMEI, Tatuya


From nobody Thu Feb 12 10:38:09 2015
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 5E1471A1B48 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 10:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 sxzC5ZBok9oX for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 10:38:05 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5070D1A1B12 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 10:38:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6544; q=dns/txt; s=iport; t=1423766285; x=1424975885; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Z1Stucp95E7Wf62EB9TScZ+aat8YEpG2lWgmCqyqqOY=; b=lI3EjNm2ks8FFcSZeXhnnGNDoqx0MvoA5WzBxt5SLpjh0DSGadw7VvbF LZcybGmjd88LlBrpFdBXPHIJG7U8frYFV7ejUzJS7yNf4DoAckzX98B46 qctI3TOb8GWTasGdq3/vJuGTAF62F6GDP8GXW3M+brMKmjc3dlpeEY2HY 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmQFAOzx3FStJA2L/2dsb2JhbABbgwaBLIMCxhcCHIEOQwEBAQEBAXyEDAEBAQMBIxFFBQsCAQYCDgoCAiYCAgIfERUQAgQOBYgZAwkIoUScbJFMDYVLAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EhiG1+gkOCDxsHgmgugRQBBI8ph22BRoEYgwaIX4JFgz4ig25vgQIkgR0BAQE
X-IronPort-AV: E=Sophos;i="5.09,566,1418083200"; d="scan'208";a="395663825"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-6.cisco.com with ESMTP; 12 Feb 2015 18:38:03 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t1CIc3vE006674 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Feb 2015 18:38:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Thu, 12 Feb 2015 12:38:03 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Marcin Siodelski <msiodelski@gmail.com>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikAAeCiTAP//tueggAT7bQCAAbZrAIAAM6qAgAAtKHCAALEHAIAASM6AgAFnaQCAADFwAIAABusAgAALpwA=
Date: Thu, 12 Feb 2015 18:38:03 +0000
Message-ID: <35AA005E-2A6F-4CAC-B8B3-1D4E2F31DD31@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com> <54DCE942.9080605@gmail.com>
In-Reply-To: <54DCE942.9080605@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-ID: <4F23790403813440858F1B42E2D2633D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/vznmTjm95hE2-EjKrdPKfYYRfVo>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 18:38:07 -0000

bGV0J3MganVzdCBnbyB3aXRoIGl0Lg0KDQotIEJlcm5pZSAoZnJvbSBpUGhvbmUpDQoNCj4gT24g
RmViIDEyLCAyMDE1LCBhdCAxMjo1NiBQTSwgTWFyY2luIFNpb2RlbHNraSA8bXNpb2RlbHNraUBn
bWFpbC5jb20+IHdyb3RlOg0KPiANCj4gDQo+PiBPbiAxMi8wMi8xNSAxODozMSwg56We5piO6YGU
5ZOJIHdyb3RlOg0KPj4gQXQgVGh1LCAxMiBGZWIgMjAxNSAxNTozNDozNiArMDEwMCwNCj4+IE1h
cmNpbiBTaW9kZWxza2kgPG1zaW9kZWxza2lAZ21haWwuY29tPiB3cm90ZToNCj4+IA0KPj4+IEFz
IGEgcmVzdWx0IG9mIHRoaXMgZGlzY3Vzc2lvbiwgd2UgaGF2ZSBjb21lIHVwIHdpdGggdGhlIGZv
bGxvd2luZyB0ZXh0DQo+Pj4gZm9yIHRoZSBzZWN0aW9uIDQuIFRoaXMgbmV3IHRleHQgaXMgbm93
IGJlaW5nIGluY2x1ZGVkIGluIHRoZSB2ZXJzaW9uDQo+Pj4gLTExIG9mIHRoZSBkcmFmdCwgYnV0
IHdlJ3JlIGhvbGRpbmcgb2ZmIHRoZSBwdWJsaWNhdGlvbiB1bnRpbCB3ZSBoZWFyDQo+Pj4gZnJv
bSB5b3UuIEhvd2V2ZXIsIGl0IHdvdWxkIGJlIGdyZWF0IGlmIHlvdSBjb3VsZCByZXZpZXcgYW5k
IHJlc3BvbmQNCj4+PiB0b2RheSwgc28gYXMgd2UgY2FuIHB1Ymxpc2ggaXQgYW5kIG1lZXQgdGhl
IGRlYWRsaW5lcyB3ZSBoYXZlIHNldA0KPj4gd2l0aCBUZWQuDQo+PiANCj4+IFRoYW5rcywgaXQg
c2VlbXMgdG8gYWRkcmVzcyBteSBjb25jZXJuLg0KPiANCj4gVGhhdCdzIGdyZWF0IQ0KPiANCj4+
IE9uZSBlZGl0b3JpYWwgcG9pbnQ6IHRoZSBhZGRlZCBwYXJhZ3JhcGggc2VlbXMgdG8gYmUgbW9z
dGx5IGEgdmVyYmF0aW0NCj4+IGNvcHkgb2YgbXkgc3VtbWFyeSB0ZXh0IGFuZCBsb29rcyBhIGJp
dCBhd2t3YXJkIGlmIHBsYWNlZCBpbiB0aGUNCj4+IG1pZGRsZSBvZiB0aGUgc2VjdGlvbi4gIEZv
ciBleGFtcGxlLCB0aGUgZmlyc3Qgc2VudGVuY2UgbG9va3MNCj4+IHJlZHVuZGFudCAodGhlIHNl
Y3Rpb24gYWxyZWFkeSBtZW50aW9uZWQgdGhhdCB0aGVyZSBhcmUgc2V2ZXJhbA0KPj4gY2hvaWNl
cykuDQo+PiANCj4+IEFuZCwgb25lIG1pbm9yIG5pdCAoYW4gZXJyb3IgZnJvbSBteSBvd24gdGV4
dCk6DQo+PiANCj4+PiAgIGNob2ljZXMuICBBbHNvLCBpbiBzb21lIGNvcm5lciBjYXNlcyBpdCBt
YXkgbm90IGZlYXNpYmxlIHRvIG1haW50YWluDQo+PiANCj4+IHMvbWF5IG5vdCBmZWFzaWJsZS9t
YXkgbm90IGJlIGZlYXNpYmxlLw0KPj4gDQo+PiBDb21iaW5pbmcgdGhlc2UsIEkgc3VnZ2VzdCBy
ZXZpc2luZyB0aGUgcGFyYWdyYXBoIGFzIGZvbGxvd3M6DQo+PiANCj4+ICAgV2hpbGUgYWxsIGNo
b2ljZXMgaGF2ZSB0aGVpciBvd24gcHJvcyBhbmQgY29ucywgd2UgcmVjb21tZW5kIGFuZA0KPj4g
ICBmb2N1cyBvbiBjaG9pY2UgMyBmb3IgdGhpcyBkb2N1bWVudCBiZWNhdXNlIGl0IGlzIGRlZW1l
ZCB0byB3b3JrDQo+PiAgIGJlc3QgZm9yIGNvbW1vbiBjYXNlcyBvZiB0aGUgbWl4ZWQgdXNlIG9m
IElBX05BIGFuZCBJQV9QRC4gIEJ1dA0KPj4gICB0aGlzIGRvY3VtZW50IGRvZXMgbm90IGV4Y2x1
ZGUgb3RoZXIgY2hvaWNlcy4gIEFsc28sIGluIHNvbWUgY29ybmVyDQo+PiAgIGNhc2VzIGl0IG1h
eSBub3QgYmUgZmVhc2libGUgdG8gbWFpbnRhaW4gYSBzaW5nbGUgREhDUHY2IHNlc3Npb24NCj4+
ICAgZm9yIGJvdGggSUFfTkEgYW5kIElBX1BELiAgVGhlc2UgY29ybmVyIGNhc2VzIGFyZSBiZXlv
bmQgdGhlIHNjb3BlDQo+PiAgIG9mIHRoaXMgZG9jdW1lbnQgYW5kIG1heSBkZXBlbmQgb24gdGhl
IG5ldHdvcmsgaW4gd2hpY2ggdGhlIGNsaWVudA0KPj4gICAoQ0VSKSBpcyBkZXNpZ25lZCB0byBv
cGVyYXRlIGFuZCBvbiB0aGUgZnVuY3Rpb25zIHRoZSBjbGllbnQgaXMNCj4+ICAgcmVxdWlyZWQg
dG8gcGVyZm9ybS4NCj4gDQo+IFRoYXQgbG9va3Mgb2sgdG8gbWUuDQo+IA0KPj4gQWxzbywgYWx0
aG91Z2ggaXQgZG9lc24ndCBzZWVtIHRvIGJlIGNyaXRpY2FsIGluIHRlcm1zIG9mIG15IG1haW4N
Cj4+IHBvaW50IGFuZCBJIHdvdWxkbid0IGNvbnNpZGVyIGl0IGEgYmxvY2tpbmcgaXNzdWUsIHRo
aXMgcGFyYWdyYXBoIGlzDQo+PiBub3QgZWFzeSB0byB1bmRlcnN0YW5kIHRvIG1lOg0KPj4gDQo+
Pj4gICBUaGUgc2luZ2xlIHNlc3Npb24gYW5kIHN0YXRlIG1hY2hpbmUgYWxsb3dzIHRoZSBjbGll
bnQgdG8gdXNlIHRoZQ0KPj4+ICAgYmVzdCBjb25maWd1cmF0aW9uIGl0IGlzIGFibGUgdG8gb2J0
YWluIGZyb20gYSBzaW5nbGUgREhDUCBzZXJ2ZXINCj4+PiAgIGR1cmluZyB0aGUgY29uZmlndXJh
dGlvbiBleGNoYW5nZS4gIElmIHRoZSBzZXJ2ZXIgaXMgbm90IGNvbmZpZ3VyZWQNCj4+PiAgIHRv
IGRlbGl2ZXIgdGhlIGVudGlyZSBjb25maWd1cmF0aW9uIHJlcXVlc3RlZCBieSB0aGUgY2xpZW50
LCB0aGUNCj4+PiAgIGNsaWVudCBjb3VsZCBjb250aW51ZSB0byBvcGVyYXRlIHVzaW5nIHRoZSBj
b25maWd1cmF0aW9uIHJlY2VpdmVkLg0KPj4+ICAgQnV0IGlkZWFsbHkgaXQgdGhlbiBjb250aW51
ZXMsIGluIGVhY2ggc3Vic2VxdWVudCBjb25maWd1cmF0aW9uDQo+Pj4gICBleGNoYW5nZSwgdG8g
cmVxdWVzdCBhbGwgdGhlIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb24gaXQgaXMNCj4+PiAgIHBy
b2dyYW1tZWQgdG8gdHJ5IHRvIG9idGFpbiwgaW5jbHVkaW5nIGFueSBzdGF0ZWZ1bCBjb25maWd1
cmF0aW9uDQo+Pj4gICBvcHRpb25zIGZvciB3aGljaCBubyByZXN1bHRzIHdlcmUgcmV0dXJuZWQg
aW4gcHJldmlvdXMgZXhjaGFuZ2VzLg0KPj4+ICAgSG93ZXZlciwgdGhpcyBpcyBkaWZmaWN1bHQg
d2l0aCB0aGUgY3VycmVudCBESENQdjYgc3BlY2lmaWNhdGlvbnMuDQo+PiANCj4+IERvZXMgaXQg
dHJ5IHRvIHNheSBzb21ldGhpbmcgbGlrZSB0aGlzPw0KPj4gDQo+PiAgICBUaGUgc2luZ2xlIHNl
c3Npb24gYW5kIHN0YXRlIG1hY2hpbmUgYWxsb3dzIHRoZSBjbGllbnQgdG8gdXNlIHRoZQ0KPj4g
ICAgYmVzdCBjb25maWd1cmF0aW9uIGl0IGlzIGFibGUgdG8gb2J0YWluIGZyb20gYSBzaW5nbGUg
REhDUCBzZXJ2ZXINCj4+ICAgIGR1cmluZyB0aGUgY29uZmlndXJhdGlvbiBleGNoYW5nZS4gIE5v
dGUsIGhvd2V2ZXIsIHRoYXQgdGhlIHNlcnZlcg0KPj4gICAgbWF5IG5vdCBiZSBjb25maWd1cmVk
IHRvIGRlbGl2ZXIgdGhlIGVudGlyZSBjb25maWd1cmF0aW9uDQo+PiAgICByZXF1ZXN0ZWQgYnkg
dGhlIGNsaWVudC4gIEluIHRoYXQgY2FzZSB0aGUgY2xpZW50IGNvdWxkIGNvbnRpbnVlDQo+PiAg
ICB0byBvcGVyYXRlIG9ubHkgdXNpbmcgdGhlIGNvbmZpZ3VyYXRpb24gcmVjZWl2ZWQsIGV2ZW4g
aWYgb3RoZXINCj4+ICAgIHNlcnZlcnMgY2FuIHByb3ZpZGUgdGhlIG1pc3NpbmcgY29uZmlndXJh
dGlvbi4gIEluIHByYWN0aWNlLA0KPj4gICAgZXNwZWNpYWxseSBpbiB0aGUgY2FzZSBvZiBoYW5k
bGluZyBJQV9OQSBhbmQgSUFfUEQsIHRoaXMgc2l0dWF0aW9uDQo+PiAgICBzaG91bGQgYmUgcmFy
ZSBvciBhIHRlbXBvcmFyeSBvcGVyYXRpb25hbCBlcnJvci4gIFNvLCBpdCBpcyBtb3JlDQo+PiAg
ICBsaWtlbHkgZm9yIHRoZSBjbGllbnQgdG8gZ2V0IGFsbCBjb25maWd1cmF0aW9uIGlmIGl0IGNv
bnRpbnVlcywgaW4NCj4+ICAgIGVhY2ggc3Vic2VxdWVudCBjb25maWd1cmF0aW9uIGV4Y2hhbmdl
LCB0byByZXF1ZXN0IGFsbCB0aGUNCj4+ICAgIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb24gaXQg
aXMgcHJvZ3JhbW1lZCB0byB0cnkgdG8gb2J0YWluLA0KPj4gICAgaW5jbHVkaW5nIGFueSBzdGF0
ZWZ1bCBjb25maWd1cmF0aW9uIG9wdGlvbnMgZm9yIHdoaWNoIG5vIHJlc3VsdHMNCj4+ICAgIHdl
cmUgcmV0dXJuZWQgaW4gcHJldmlvdXMgZXhjaGFuZ2VzLg0KPj4gDQo+PiAgICBPbmUgbWFqb3Ig
aXNzdWUgb2YgdGhpcyBsYXN0IGFwcHJvYWNoIGlzIHRoYXQgaXQgaXMgZGlmZmljdWx0IHRvDQo+
PiAgICBhbGxvdyBpdCB3aXRoIHRoZSBjdXJyZW50IERIQ1B2NiBzcGVjaWZpY2F0aW9uczsgaW4g
c29tZSBjYXNlcw0KPj4gICAgaXQgaXMgbm90IGNsZWFyIGVub3VnaCwgYW5kIGluIG90aGVyIGNh
c2VzIGV4aXN0aW5nIHJlc3RyaWN0aW9ucw0KPj4gICAgY2FuIG1ha2UgaXQgaW1wb3NzaWJsZS4g
IFRoaXMgZG9jdW1lbnQgaW50cm9kdWNlcyBzb21lDQo+PiAgICBjbGFyaWZpY2F0aW9ucyBhbmQg
c21hbGwgbW9kaWZpY2F0aW9ucyB0byB0aGUgY3VycmVudA0KPj4gICAgc3BlY2lmaWNhdGlvbiB0
byBhZGRyZXNzIHRoaXMgY29uY2Vybi4NCj4+IA0KPj4gKFRoZSBzZWNvbmQgcGFyYWdyYXBoIGlz
IG15IGF0dGVtcHQgb2YgcmVwaHJhc2luZyB0aGUgdmVyeSBsYXN0DQo+PiBzZW50ZW5jZSBvZiB0
aGUgb3JpZ2luYWwgcGFyYWdyYXBoIGJhc2VkIG9uIG15IHRoZSBzZWVtaW5nIGludGVudCBvZg0K
Pj4gaXQpDQo+PiANCj4+IElmIHNvLCBhbmQgaWYgeW91IHRoaW5rIG15IHRleHQgaXMgY2xlYXJl
ciwgcGxlYXNlIGZlZWwgZnJlZSB0byB1c2UNCj4+IGl0LiAgSWYgeW91IGJlbGlldmUgdGhlIG9y
aWdpbmFsIHRleHQgaXMgY2xlYXIgZW5vdWdoIChhbmQgZXNwZWNpYWxseQ0KPj4gaWYgb3RoZXJz
IGFsc28gdGhpbmsgc28pLCBJJ20gb2theSB3aXRoIGtlZXBpbmcgdGhlIG9yaWdpbmFsDQo+PiBw
YXJhZ3JhcGguDQo+IA0KPiBXZSB3aWxsIGRpc2N1c3MgdGhpcyB3aXRoIEJlcm5pZSBhbmQgZGVj
aWRlIHRvIHdoYXQgZXh0ZW50IHdlIHdpbGwgdXNlDQo+IHlvdXIgdGV4dC4NCj4gDQo+IA0KPiBN
YW55IHRoYW5rcyBmb3IgdGhlIHByb21wdCByZXNwb25zZSENCj4gDQo+IE1hcmNpbg0K


From nobody Thu Feb 12 12:44:36 2015
Return-Path: <msiodelski@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 459541A8884 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_05=-0.5,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 qqge-adTM_yg for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 06:34:42 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCC611A8872 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 06:34:41 -0800 (PST)
Received: by labgd6 with SMTP id gd6so10449399lab.7 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 06:34:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=v4TUy2KwHpU3JECkPNAYaoHzOB4OmbBzkVaZweCZaxM=; b=ifKM1pciwVBIPlPALGoOF/15UlcNZsffEkCM/8PN6fTsKamilrE6/Hh2/YUFBB7coh j7V5RPHh951zHPLLq/M34YoCjXJ/7LWg1hriVP/Yd8hQcZSFjBIF2yGxqX8twFJvrNNy EXzUt9kxSBdcFxSdUDrWn4efdq+vu7aPntEbauLesJ7tumGygq7kXc43etabtPIdmdTI ionCK7sHpw4tlCgtLmeaoz/dj9evc25KFfH9s1MU5eXe/8cWp1VzDdTM02DyL8c1K4iV x1Zg7gD+BZjgT9Cja7gDiWJvOvzxtpGZj6SCxak6YEjNASQFkdUaM72WgsN8DBZL4grv uGEA==
X-Received: by 10.112.53.137 with SMTP id b9mr3685621lbp.66.1423751680302; Thu, 12 Feb 2015 06:34:40 -0800 (PST)
Received: from [192.168.8.101] (apn-46-169-65-191.dynamic.gprs.plus.pl. [46.169.65.191]) by mx.google.com with ESMTPSA id p11sm796456lal.41.2015.02.12.06.34.37 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 06:34:39 -0800 (PST)
Message-ID: <54DCB9FC.5020400@gmail.com>
Date: Thu, 12 Feb 2015 15:34:36 +0100
From: Marcin Siodelski <msiodelski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>,  Ted Lemon <Ted.Lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com>
In-Reply-To: <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------080604030805010102060505"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/svKVOr99GZuth7XvHoptUlQl0D0>
X-Mailman-Approved-At: Thu, 12 Feb 2015 12:44:34 -0800
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 14:34:52 -0000

This is a multi-part message in MIME format.
--------------080604030805010102060505
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 11/02/15 18:08, 神明達哉 wrote:
> (Jumping to this point)
> 
> At Wed, 11 Feb 2015 07:47:38 -0500,
> Ted Lemon <Ted.Lemon@nominum.com> wrote:
> 
>>> Perhaps  we can add something regarding this and just explain the issue(s) and that it would be up to implementation to decide how best to proceed.
>>
>> This is probably the right approach.
> 
> I think it works for me, too.
> 
> Commenting on a few more points that may be related:
> 
> At Wed, 11 Feb 2015 03:06:29 +0000,
> "Bernie Volz (volz)" <volz@cisco.com> wrote:
> 
>> Just to be clear, the draft only recommends that clients use a
>> single state machine and it makes that better because it offers
>> clients the ability to Renew more than the IAs they got (and to keep
>> renewal times in sync). Nothing in the draft requires that a client
>> only maintain one state machine.
> 
> Hmm, that intent was not clear, at least to me.  Certainly, it doesn't
> explicitly prohibit other options than the single DHCPv6 session, but
> I basically interpret the overall tone of Section 4 that way.  One
> background reason for that is probably because it just talks about
> drawbacks of other options and then leads to the text pasted below
> (this is also related one of my other comments, which was rejected, to
> which I wouldn't be opposed at this point).
> 
>> The key text is:
>>
>>       We have chosen to recommend that clients use the remaining option:
>>       a single DHCP session and state machine.  The client maintains a
>>       single session and state machine. It uses the best configuration it
>>       is able to obtain during any configuration exchange.   But it
>>       continues, in each subsequent configuration exchange, to request all
>>       the configuration information it is programmed to try to obtain,
>>       including any stateful configuration options for which no results
>>       were returned in previous exchanges.
> 
> If this is intended to mean clients can choose (or may end up
> choosing) other options, the intent wasn't clear to me either.
> 
> If, for example, section 4 was revised to read like this, I think my
> concern will be addressed:
> 
>   There can be several choices on how to handle multiple IA options
>   (and, specifically IA_NA and IA_PD) including 1-3.  All choices
>   have their own pors and cons, but this document focuses on choice #3
>   (using a single DHCPv6 session for both IA_NA and IA_PD) because
>   it's deemed to work best for common cases of the mixed use of IA_NA
>   and IA_PD.  But this document doesn't exclude other choices.  Also,
>   in some corner cases it may not feasible to maintain a single DHCPv6
>   session for both IA_NA and IA_PD.  These general and corner cases
>   are beyond the scope of the discussion and will be deferred to the
>   next revision of the base DHCPv6 specification (i.e., 3315bis).
> 


Jinmei et al.

As a result of this discussion, we have come up with the following text
for the section 4. This new text is now being included in the version
-11 of the draft, but we're holding off the publication until we hear
from you. However, it would be great if you could review and respond
today, so as we can publish it and meet the deadlines we have set with Ted.

I have also attached the (unpublished) version -11 in the text format.

Many thanks!
Marcin

-------------------

   The DHCPv6 specification [RFC3315] was written with the assumption
   that the only stateful options were for assigning addresses.  DHCPv6
   Prefix Delegation [RFC3633] describes how to extend the DHCPv6
   protocol to handle prefix delegation, but does not clearly specify
   how the DHCP address assignment and prefix delegation co-exist.

   If a client requests multiple IA option types, but the server is
   configured to only offer a subset of them, the client could react in
   several ways:

   1.  Reset the state machine and continue to send Solicit messages,

   2.  Create separate DHCP sessions for each IA option type and
       continue to Solicit for the unfulfilled IA options, or

   3.  The client could continue with the single session, and include
       the unfulfilled IA options in subsequent messages to the server.

   Resetting the state machine and continuing to send Solicit messages
   may result in the client never completing DHCP and is generally not
   considered a good solution.  It can also result in a packet storm if
   the client does not appropriately rate limit its sending of Solicit
   messages.

   Creating a separate DHCP session (separate instances of the client
   state machine) per IA option type, while conceptually simple, causes
   a number of issues: additional host resources required to create and
   maintain multiple instances of the state machine in clients,
   additional DHCP protocol traffic, unnecessary duplication of other
   configuration options and the potential for conflict, divergence in
   that each IA option type specification specifies its 'own' version of
   the DHCP protocol.

   The single session and state machine allows the client to use the
   best configuration it is able to obtain from a single DHCP server
   during the configuration exchange.  If the server is not configured
   to deliver the entire configuration requested by the client, the
   client could continue to operate using the configuration received.
   But ideally it then continues, in each subsequent configuration
   exchange, to request all the configuration information it is
   programmed to try to obtain, including any stateful configuration
   options for which no results were returned in previous exchanges.
   However, this is difficult with the current DHCPv6 specifications.

   There are several choices on how to handle multiple IA options (and,
   specifically IA_NA and IA_PD) including 1-3 above.  Each choice has
   its own pros and cons.  For this document, we recommend and focus on
   choice 3 (using a single DHCPv6 session for both IA_NA and IA_PD)
   because it is deemed to work best for common cases of the mixed use
   of IA_NA and IA_PD.  But this document does not exclude other
   choices.  Also, in some corner cases it may not feasible to maintain
   a single DHCPv6 session for both IA_NA and IA_PD.  These corner cases
   are beyond the scope of this document and may depend on the network
   in which the client (CER) is designed to operate and on the functions
   the client is required to perform.

   The sections which follow update RFC 3315 and RFC 3633 to accommodate
   the recommendation, though many of the changes are also applicable
   even if other choices are used.

-----


--------------080604030805010102060505
Content-Type: text/plain; charset=UTF-8;
 name="draft-ietf-dhc-dhcpv6-stateful-issues.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-dhc-dhcpv6-stateful-issues.txt"

CgoKCk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICBPLiBUcm9hbgpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEIuIFZvbHoKVXBkYXRlczogMzMx
NSwzNjMzIChpZiBhcHByb3ZlZCkgICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1z
LCBJbmMuCkludGVuZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIE0uIFNpb2RlbHNraQpFeHBpcmVzOiBBdWd1c3QgMTYsIDIwMTUgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBJU0MKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEZlYnJ1YXJ5
IDEyLCAyMDE1CgoKICAgIElzc3VlcyBhbmQgUmVjb21tZW5kYXRpb25zIHdpdGggTXVsdGlw
bGUgU3RhdGVmdWwgREhDUHY2IE9wdGlvbnMKICAgICAgICAgICAgICBkcmFmdC1pZXRmLWRo
Yy1kaGNwdjYtc3RhdGVmdWwtaXNzdWVzLTExLnR4dAoKQWJzdHJhY3QKCiAgIFRoZSBEeW5h
bWljIEhvc3QgQ29uZmlndXJhdGlvbiBQcm90b2NvbCBmb3IgSVB2NiAoREhDUHY2KQogICBz
cGVjaWZpY2F0aW9uIGRlZmluZWQgdHdvIHN0YXRlZnVsIG9wdGlvbnMsIElBX05BIGFuZCBJ
QV9UQSwgYnV0IGRpZAogICBub3QgYW50aWNpcGF0ZSB0aGUgZGV2ZWxvcG1lbnQgb2YgYWRk
aXRpb25hbCBzdGF0ZWZ1bCBvcHRpb25zLgogICBESENQdjYgUHJlZml4IERlbGVnYXRpb24g
YWRkZWQgdGhlIElBX1BEIG9wdGlvbiwgd2hpY2ggaXMgc3RhdGVmdWwuCiAgIEFwcGxpY2F0
aW9ucyB0aGF0IHVzZSBJQV9OQSBhbmQgSUFfUEQgdG9nZXRoZXIgaGF2ZSByZXZlYWxlZCBp
c3N1ZXMKICAgdGhhdCBuZWVkIHRvIGJlIGFkZHJlc3NlZC4gIFRoaXMgZG9jdW1lbnQgdXBk
YXRlcyBSRkMgMzMxNSBhbmQgUkZDCiAgIDM2MzMgdG8gYWRkcmVzcyB0aGVzZSBpc3N1ZXMu
CgpTdGF0dXMgb2YgVGhpcyBNZW1vCgogICBUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1p
dHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlCiAgIHByb3Zpc2lvbnMgb2YgQkNQ
IDc4IGFuZCBCQ1AgNzkuCgogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1l
bnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZwogICBUYXNrIEZvcmNlIChJRVRGKS4g
IE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQogICB3b3JraW5n
IGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJyZW50IElu
dGVybmV0LQogICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2Ry
YWZ0cy9jdXJyZW50Ly4KCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRz
IHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocwogICBhbmQgbWF5IGJlIHVwZGF0
ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQog
ICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFz
IHJlZmVyZW5jZQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAi
d29yayBpbiBwcm9ncmVzcy4iCgogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJl
IG9uIEF1Z3VzdCAxNiwgMjAxNS4KCkNvcHlyaWdodCBOb3RpY2UKCiAgIENvcHlyaWdodCAo
YykgMjAxNSBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZQog
ICBkb2N1bWVudCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC4KCiAgIFRoaXMgZG9j
dW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWwK
ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cwogICAoaHR0cDovL3Ry
dXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2YK
ICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2Ug
ZG9jdW1lbnRzCiAgIGNhcmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBh
bmQgcmVzdHJpY3Rpb25zIHdpdGggcmVzcGVjdAoKCgpUcm9hbiwgZXQgYWwuICAgICAgICAg
ICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUgICAgICAgICAgICAgICAgW1BhZ2UgMV0KDApJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAg
ICAgIEZlYnJ1YXJ5IDIwMTUKCgogICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBDb21wb25l
bnRzIGV4dHJhY3RlZCBmcm9tIHRoaXMgZG9jdW1lbnQgbXVzdAogICBpbmNsdWRlIFNpbXBs
aWZpZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0LmUgb2YK
ICAgdGhlIFRydXN0IExlZ2FsIFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0
IHdhcnJhbnR5IGFzCiAgIGRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5z
ZS4KCiAgIFRoaXMgZG9jdW1lbnQgbWF5IGNvbnRhaW4gbWF0ZXJpYWwgZnJvbSBJRVRGIERv
Y3VtZW50cyBvciBJRVRGCiAgIENvbnRyaWJ1dGlvbnMgcHVibGlzaGVkIG9yIG1hZGUgcHVi
bGljbHkgYXZhaWxhYmxlIGJlZm9yZSBOb3ZlbWJlcgogICAxMCwgMjAwOC4gIFRoZSBwZXJz
b24ocykgY29udHJvbGxpbmcgdGhlIGNvcHlyaWdodCBpbiBzb21lIG9mIHRoaXMKICAgbWF0
ZXJpYWwgbWF5IG5vdCBoYXZlIGdyYW50ZWQgdGhlIElFVEYgVHJ1c3QgdGhlIHJpZ2h0IHRv
IGFsbG93CiAgIG1vZGlmaWNhdGlvbnMgb2Ygc3VjaCBtYXRlcmlhbCBvdXRzaWRlIHRoZSBJ
RVRGIFN0YW5kYXJkcyBQcm9jZXNzLgogICBXaXRob3V0IG9idGFpbmluZyBhbiBhZGVxdWF0
ZSBsaWNlbnNlIGZyb20gdGhlIHBlcnNvbihzKSBjb250cm9sbGluZwogICB0aGUgY29weXJp
Z2h0IGluIHN1Y2ggbWF0ZXJpYWxzLCB0aGlzIGRvY3VtZW50IG1heSBub3QgYmUgbW9kaWZp
ZWQKICAgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2VzcywgYW5kIGRlcml2YXRp
dmUgd29ya3Mgb2YgaXQgbWF5CiAgIG5vdCBiZSBjcmVhdGVkIG91dHNpZGUgdGhlIElFVEYg
U3RhbmRhcmRzIFByb2Nlc3MsIGV4Y2VwdCB0byBmb3JtYXQKICAgaXQgZm9yIHB1YmxpY2F0
aW9uIGFzIGFuIFJGQyBvciB0byB0cmFuc2xhdGUgaXQgaW50byBsYW5ndWFnZXMgb3RoZXIK
ICAgdGhhbiBFbmdsaXNoLgoKVGFibGUgb2YgQ29udGVudHMKCiAgIDEuICBJbnRyb2R1Y3Rp
b24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAg
MwogICAyLiAgQ29udmVudGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgIDMKICAgMy4gIFRlcm1pbm9sb2d5IC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICAzCiAgIDQuICBIYW5kbGlu
ZyBvZiBNdWx0aXBsZSBJQSBPcHRpb24gVHlwZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAgNAogICAgIDQuMS4gIFBsYWNlbWVudCBvZiBTdGF0dXMgQ29kZXMgaW4gYW4gQWR2ZXJ0
aXNlIE1lc3NhZ2UgLiAuIC4gLiAgIDUKICAgICA0LjIuICBBZHZlcnRpc2UgTWVzc2FnZSBQ
cm9jZXNzaW5nIGJ5IGEgQ2xpZW50ICAuIC4gLiAuIC4gLiAuIC4gICA3CiAgICAgNC4zLiAg
VDEvVDIgVGltZXJzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAgOAogICAgIDQuNC4gIFJlbmV3IGFuZCBSZWJpbmQgTWVzc2FnZXMgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDkKICAgICAgIDQuNC4xLiAgUmVuZXcgTWVzc2Fn
ZSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA5CiAgICAgICA0
LjQuMi4gIFJlYmluZCBNZXNzYWdlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAxMAogICAgICAgNC40LjMuICBVcGRhdGVzIHRvIHNlY3Rpb24gMTguMS4zIG9m
IFJGQyAzMzE1IC4gLiAuIC4gLiAuIC4gLiAgMTAKICAgICAgIDQuNC40LiAgVXBkYXRlcyB0
byBTZWN0aW9uIDE4LjEuNCBvZiBSRkMgMzMxNSAuIC4gLiAuIC4gLiAuIC4gIDEyCiAgICAg
ICA0LjQuNS4gIFVwZGF0ZXMgdG8gU2VjdGlvbiAxOC4xLjggb2YgUkZDIDMzMTUgLiAuIC4g
LiAuIC4gLiAuICAxMgogICAgICAgNC40LjYuICBVcGRhdGVzIHRvIFNlY3Rpb24gMTguMi4z
IG9mIFJGQyAzMzE1IC4gLiAuIC4gLiAuIC4gLiAgMTUKICAgICAgIDQuNC43LiAgVXBkYXRl
cyB0byBTZWN0aW9uIDE4LjIuNCBvZiBSRkMgMzMxNSAuIC4gLiAuIC4gLiAuIC4gIDE2CiAg
ICAgICA0LjQuOC4gIFVwZGF0ZXMgdG8gUkZDIDM2MzMgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxOAogICAgIDQuNS4gIENvbmZpcm0gTWVzc2FnZSAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTkKICAgICA0LjYuICBEZWNsaW5l
IFNob3VsZCBOb3QgTmVjZXNzYXJpbHkgVHJpZ2dlciBhIFJlbGVhc2UgIC4gLiAuIC4gIDIw
CiAgICAgNC43LiAgTXVsdGlwbGUgUHJvdmlzaW9uaW5nIERvbWFpbnMgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICAyMAogICA1LiAgSUFOQSBDb25zaWRlcmF0aW9ucyAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjAKICAgNi4gIFNlY3VyaXR5
IENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
IDIxCiAgIDcuICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICAyMQogICA4LiAgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjEKICAgICA4LjEuICBO
b3JtYXRpdmUgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDIxCiAgICAgOC4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAyMQogICBBdXRob3JzJyBBZGRyZXNzZXMgIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMjIKCgoKCgoKVHJv
YW4sIGV0IGFsLiAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAg
ICAgICAgIFtQYWdlIDJdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3Rh
dGVmdWwgT3B0aW9ucyAgICAgICAgICBGZWJydWFyeSAyMDE1CgoKMS4gIEludHJvZHVjdGlv
bgoKICAgREhDUHY2IFtSRkMzMzE1XSB3YXMgd3JpdHRlbiB3aXRob3V0IHRoZSBleHBlY3Rh
dGlvbiB0aGF0IGFkZGl0aW9uYWwKICAgc3RhdGVmdWwgREhDUHY2IG9wdGlvbnMgd291bGQg
YmUgZGV2ZWxvcGVkLiAgREhDUHY2IFByZWZpeCBEZWxlZ2F0aW9uCiAgIFtSRkMzNjMzXSBz
aW5jZSBhZGRlZCBhIG5ldyBzdGF0ZWZ1bCBvcHRpb24gZm9yIFByZWZpeCBEZWxlZ2F0aW9u
IHRvCiAgIERIQ1B2Ni4gIEltcGxlbWVudGF0aW9uIGV4cGVyaWVuY2Ugb2YgdGhlIEN1c3Rv
bWVyIEVkZ2UgUm91dGVyIG1vZGVsCiAgIGRlc2NyaWJlZCBpbiBbUkZDNzA4NF0gaGFzIHNo
b3duIGlzc3VlcyB3aXRoIHRoZSBESENQdjYgcHJvdG9jb2wgaW4KICAgc3VwcG9ydGluZyBt
dWx0aXBsZSBzdGF0ZWZ1bCBvcHRpb24gdHlwZXMsIGluIHBhcnRpY3VsYXIgSUFfTkEgKG5v
bi0KICAgdGVtcG9yYXJ5IGFkZHJlc3NlcykgYW5kIElBX1BEIChkZWxlZ2F0ZWQgcHJlZml4
ZXMpLgoKICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBudW1iZXIgb2YgcHJvYmxlbXMg
ZW5jb3VudGVyZWQgd2l0aAogICBjb2V4aXN0ZW5jZSBvZiB0aGUgSUFfTkEgYW5kIElBX1BE
IG9wdGlvbiB0eXBlcyBhbmQgc3BlY2lmaWVzIGNoYW5nZXMKICAgdG8gdGhlIERIQ1B2NiBw
cm90b2NvbCB0byBhZGRyZXNzIHRoZXNlIHByb2JsZW1zLgoKICAgVGhlIGludGVudGlvbiBv
ZiB0aGlzIHdvcmsgaXMgdG8gY2xhcmlmeSBhbmQsIHdoZXJlIG5lZWRlZCwgbW9kaWZ5CiAg
IHRoZSBESENQdjYgcHJvdG9jb2wgc3BlY2lmaWNhdGlvbiB0byBzdXBwb3J0IElBX05BIGFu
ZCBJQV9QRCBvcHRpb24KICAgdHlwZXMgd2l0aGluIGEgc2luZ2xlIERIQ1B2NiBzZXNzaW9u
LgoKICAgTm90ZSB0aGF0IHdoaWxlIElBX1RBICh0ZW1wb3JhcnkgYWRkcmVzc2VzKSBvcHRp
b25zIG1heSBiZSBpbmNsdWRlZAogICB3aXRoIG90aGVyIElBIG9wdGlvbiB0eXBlIHJlcXVl
c3RzLCB0aGVzZSBnZW5lcmFsbHkgYXJlIG5vdCByZW5ld2VkCiAgICh0aGVyZSBhcmUgbm8g
VDEvVDIgdGltZXMpIGFuZCBoYXZlIGEgc2VwYXJhdGUgbGlmZSBjeWNsZSBmcm9tIElBX05B
CiAgIGFuZCBJQV9QRCBvcHRpb24gdHlwZXMuICBUaGVyZWZvcmUsIHRoZSBJQV9UQSBvcHRp
b24gdHlwZSBpcyBtb3N0bHkKICAgb3V0IG9mIHNjb3BlIGZvciB0aGlzIGRvY3VtZW50LgoK
ICAgVGhlIGNoYW5nZXMgZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgYXJlIGludGVuZGVk
IHRvIGJlCiAgIGluY29ycG9yYXRlZCBpbiBhIG5ldyByZXZpc2lvbiBvZiB0aGUgREhDUHY2
IHByb3RvY29sIHNwZWNpZmljYXRpb24KICAgKFtJLUQuZGhjd2ctZGhjLXJmYzMzMTViaXNd
KS4KCjIuICBDb252ZW50aW9ucwoKICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5P
VCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLAogICAiU0hPVUxEIiwgIlNI
T1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05BTCIgaW4gdGhp
cwogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtS
RkMyMTE5XS4KCjMuICBUZXJtaW5vbG9neQoKICAgSW4gYWRkaXRpb24gdG8gdGhlIHRlcm1p
bm9sb2d5IGRlZmluZWQgaW4gW1JGQzMzMTVdLCBbUkZDMzYzM10sIGFuZAogICBbUkZDNzIy
N10sIHRoZSBmb2xsb3dpbmcgdGVybWlub2xvZ3kgaXMgdXNlZCBpbiB0aGlzIGRvY3VtZW50
OgoKICAgSWRlbnRpdHkgYXNzb2NpYXRpb24gKElBKTogICAgICBUaHJvdWdob3V0IHRoaXMg
ZG9jdW1lbnQsICJJQSIgaXMKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB1
c2VkIHRvIHJlZmVyIHRvIHRoZSBJZGVudGl0eQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIEFzc29jaWF0aW9uIGNvbnRhaW5pbmcgYWRkcmVzc2VzIG9yCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgcHJlZml4ZXMgYXNzaWduZWQgdG8gYSBjbGll
bnQgYW5kCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgY2FycmllZCBpbiB0
aGUgSUFfTkEgb3IgSUFfUEQgb3B0aW9ucwogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHJlc3BlY3RpdmVseS4KCiAgIElBIG9wdGlvbiB0eXBlczogICAgICAgICAgICAg
ICAgVGhpcyBpcyB1c2VkIHRvIGdlbmVyYWxseSBtZWFuIGFuCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgSUFfTkEgYW5kL29yIElBX1BEIG9wdGlvbi4KCgoKVHJvYW4s
IGV0IGFsLiAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAg
ICAgIFtQYWdlIDNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVm
dWwgT3B0aW9ucyAgICAgICAgICBGZWJydWFyeSAyMDE1CgoKICAgU3RhdGVmdWwgb3B0aW9u
czogICAgICAgICAgICAgICBPcHRpb25zIHRoYXQgcmVxdWlyZSBkeW5hbWljIGJpbmRpbmcK
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBzdGF0ZSBwZXIgY2xpZW50IG9u
IHRoZSBzZXJ2ZXIuCgogICBUb3AtbGV2ZWwgb3B0aW9uczogICAgICAgICAgICAgIFRvcC1s
ZXZlbCBvcHRpb25zIGFyZSBESENQdjYgb3B0aW9ucwogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIHRoYXQgYXJlIG5vdCBlbmNhcHN1bGF0ZWQgd2l0aGluCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgb3RoZXIgb3B0aW9ucywgZXhjbHVkaW5nIHRo
ZSBSZWxheS0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBNZXNzYWdlIG9w
dGlvbi4gIE9wdGlvbnMgZW5jYXBzdWxhdGVkCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgYnkgUmVsYXktbWVzc2FnZSBvcHRpb25zLCBidXQgbm90IGJ5CiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgYW55IG90aGVyIG9wdGlvbiwgYXJlIHN0aWxs
IHRvcC1sZXZlbAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIG9wdGlvbnMs
IHdoZXRoZXIgdGhleSBhcHBlYXIgaW4gYQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHJlbGF5IGFnZW50IG1lc3NhZ2Ugb3IgYSBzZXJ2ZXIKICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBtZXNzYWdlLiAgU2VlIFtSRkM3MjI3XS4KCjQuICBIYW5k
bGluZyBvZiBNdWx0aXBsZSBJQSBPcHRpb24gVHlwZXMKCiAgIFRoZSBESENQdjYgc3BlY2lm
aWNhdGlvbiBbUkZDMzMxNV0gd2FzIHdyaXR0ZW4gd2l0aCB0aGUgYXNzdW1wdGlvbgogICB0
aGF0IHRoZSBvbmx5IHN0YXRlZnVsIG9wdGlvbnMgd2VyZSBmb3IgYXNzaWduaW5nIGFkZHJl
c3Nlcy4gIERIQ1B2NgogICBQcmVmaXggRGVsZWdhdGlvbiBbUkZDMzYzM10gZGVzY3JpYmVz
IGhvdyB0byBleHRlbmQgdGhlIERIQ1B2NgogICBwcm90b2NvbCB0byBoYW5kbGUgcHJlZml4
IGRlbGVnYXRpb24sIGJ1dCBkb2VzIG5vdCBjbGVhcmx5IHNwZWNpZnkKICAgaG93IHRoZSBE
SENQIGFkZHJlc3MgYXNzaWdubWVudCBhbmQgcHJlZml4IGRlbGVnYXRpb24gY28tZXhpc3Qu
CgogICBJZiBhIGNsaWVudCByZXF1ZXN0cyBtdWx0aXBsZSBJQSBvcHRpb24gdHlwZXMsIGJ1
dCB0aGUgc2VydmVyIGlzCiAgIGNvbmZpZ3VyZWQgdG8gb25seSBvZmZlciBhIHN1YnNldCBv
ZiB0aGVtLCB0aGUgY2xpZW50IGNvdWxkIHJlYWN0IGluCiAgIHNldmVyYWwgd2F5czoKCiAg
IDEuICBSZXNldCB0aGUgc3RhdGUgbWFjaGluZSBhbmQgY29udGludWUgdG8gc2VuZCBTb2xp
Y2l0IG1lc3NhZ2VzLAoKICAgMi4gIENyZWF0ZSBzZXBhcmF0ZSBESENQIHNlc3Npb25zIGZv
ciBlYWNoIElBIG9wdGlvbiB0eXBlIGFuZAogICAgICAgY29udGludWUgdG8gU29saWNpdCBm
b3IgdGhlIHVuZnVsZmlsbGVkIElBIG9wdGlvbnMsIG9yCgogICAzLiAgVGhlIGNsaWVudCBj
b3VsZCBjb250aW51ZSB3aXRoIHRoZSBzaW5nbGUgc2Vzc2lvbiwgYW5kIGluY2x1ZGUKICAg
ICAgIHRoZSB1bmZ1bGZpbGxlZCBJQSBvcHRpb25zIGluIHN1YnNlcXVlbnQgbWVzc2FnZXMg
dG8gdGhlIHNlcnZlci4KCiAgIFJlc2V0dGluZyB0aGUgc3RhdGUgbWFjaGluZSBhbmQgY29u
dGludWluZyB0byBzZW5kIFNvbGljaXQgbWVzc2FnZXMKICAgbWF5IHJlc3VsdCBpbiB0aGUg
Y2xpZW50IG5ldmVyIGNvbXBsZXRpbmcgREhDUCBhbmQgaXMgZ2VuZXJhbGx5IG5vdAogICBj
b25zaWRlcmVkIGEgZ29vZCBzb2x1dGlvbi4gIEl0IGNhbiBhbHNvIHJlc3VsdCBpbiBhIHBh
Y2tldCBzdG9ybSBpZgogICB0aGUgY2xpZW50IGRvZXMgbm90IGFwcHJvcHJpYXRlbHkgcmF0
ZSBsaW1pdCBpdHMgc2VuZGluZyBvZiBTb2xpY2l0CiAgIG1lc3NhZ2VzLgoKICAgQ3JlYXRp
bmcgYSBzZXBhcmF0ZSBESENQIHNlc3Npb24gKHNlcGFyYXRlIGluc3RhbmNlcyBvZiB0aGUg
Y2xpZW50CiAgIHN0YXRlIG1hY2hpbmUpIHBlciBJQSBvcHRpb24gdHlwZSwgd2hpbGUgY29u
Y2VwdHVhbGx5IHNpbXBsZSwgY2F1c2VzCiAgIGEgbnVtYmVyIG9mIGlzc3VlczogYWRkaXRp
b25hbCBob3N0IHJlc291cmNlcyByZXF1aXJlZCB0byBjcmVhdGUgYW5kCiAgIG1haW50YWlu
IG11bHRpcGxlIGluc3RhbmNlcyBvZiB0aGUgc3RhdGUgbWFjaGluZSBpbiBjbGllbnRzLAog
ICBhZGRpdGlvbmFsIERIQ1AgcHJvdG9jb2wgdHJhZmZpYywgdW5uZWNlc3NhcnkgZHVwbGlj
YXRpb24gb2Ygb3RoZXIKICAgY29uZmlndXJhdGlvbiBvcHRpb25zIGFuZCB0aGUgcG90ZW50
aWFsIGZvciBjb25mbGljdCwgZGl2ZXJnZW5jZSBpbgogICB0aGF0IGVhY2ggSUEgb3B0aW9u
IHR5cGUgc3BlY2lmaWNhdGlvbiBzcGVjaWZpZXMgaXRzICdvd24nIHZlcnNpb24gb2YKICAg
dGhlIERIQ1AgcHJvdG9jb2wuCgoKCgpUcm9hbiwgZXQgYWwuICAgICAgICAgICAgRXhwaXJl
cyBBdWd1c3QgMTYsIDIwMTUgICAgICAgICAgICAgICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1E
cmFmdCAgICAgICAgICBNdWx0aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAgICAgIEZlYnJ1
YXJ5IDIwMTUKCgogICBUaGUgc2luZ2xlIHNlc3Npb24gYW5kIHN0YXRlIG1hY2hpbmUgYWxs
b3dzIHRoZSBjbGllbnQgdG8gdXNlIHRoZQogICBiZXN0IGNvbmZpZ3VyYXRpb24gaXQgaXMg
YWJsZSB0byBvYnRhaW4gZnJvbSBhIHNpbmdsZSBESENQIHNlcnZlcgogICBkdXJpbmcgdGhl
IGNvbmZpZ3VyYXRpb24gZXhjaGFuZ2UuICBJZiB0aGUgc2VydmVyIGlzIG5vdCBjb25maWd1
cmVkCiAgIHRvIGRlbGl2ZXIgdGhlIGVudGlyZSBjb25maWd1cmF0aW9uIHJlcXVlc3RlZCBi
eSB0aGUgY2xpZW50LCB0aGUKICAgY2xpZW50IGNvdWxkIGNvbnRpbnVlIHRvIG9wZXJhdGUg
dXNpbmcgdGhlIGNvbmZpZ3VyYXRpb24gcmVjZWl2ZWQuCiAgIEJ1dCBpZGVhbGx5IGl0IHRo
ZW4gY29udGludWVzLCBpbiBlYWNoIHN1YnNlcXVlbnQgY29uZmlndXJhdGlvbgogICBleGNo
YW5nZSwgdG8gcmVxdWVzdCBhbGwgdGhlIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb24gaXQg
aXMKICAgcHJvZ3JhbW1lZCB0byB0cnkgdG8gb2J0YWluLCBpbmNsdWRpbmcgYW55IHN0YXRl
ZnVsIGNvbmZpZ3VyYXRpb24KICAgb3B0aW9ucyBmb3Igd2hpY2ggbm8gcmVzdWx0cyB3ZXJl
IHJldHVybmVkIGluIHByZXZpb3VzIGV4Y2hhbmdlcy4KICAgSG93ZXZlciwgdGhpcyBpcyBk
aWZmaWN1bHQgd2l0aCB0aGUgY3VycmVudCBESENQdjYgc3BlY2lmaWNhdGlvbnMuCgogICBU
aGVyZSBhcmUgc2V2ZXJhbCBjaG9pY2VzIG9uIGhvdyB0byBoYW5kbGUgbXVsdGlwbGUgSUEg
b3B0aW9ucyAoYW5kLAogICBzcGVjaWZpY2FsbHkgSUFfTkEgYW5kIElBX1BEKSBpbmNsdWRp
bmcgMS0zIGFib3ZlLiAgRWFjaCBjaG9pY2UgaGFzCiAgIGl0cyBvd24gcHJvcyBhbmQgY29u
cy4gIEZvciB0aGlzIGRvY3VtZW50LCB3ZSByZWNvbW1lbmQgYW5kIGZvY3VzIG9uCiAgIGNo
b2ljZSAzICh1c2luZyBhIHNpbmdsZSBESENQdjYgc2Vzc2lvbiBmb3IgYm90aCBJQV9OQSBh
bmQgSUFfUEQpCiAgIGJlY2F1c2UgaXQgaXMgZGVlbWVkIHRvIHdvcmsgYmVzdCBmb3IgY29t
bW9uIGNhc2VzIG9mIHRoZSBtaXhlZCB1c2UKICAgb2YgSUFfTkEgYW5kIElBX1BELiAgQnV0
IHRoaXMgZG9jdW1lbnQgZG9lcyBub3QgZXhjbHVkZSBvdGhlcgogICBjaG9pY2VzLiAgQWxz
bywgaW4gc29tZSBjb3JuZXIgY2FzZXMgaXQgbWF5IG5vdCBmZWFzaWJsZSB0byBtYWludGFp
bgogICBhIHNpbmdsZSBESENQdjYgc2Vzc2lvbiBmb3IgYm90aCBJQV9OQSBhbmQgSUFfUEQu
ICBUaGVzZSBjb3JuZXIgY2FzZXMKICAgYXJlIGJleW9uZCB0aGUgc2NvcGUgb2YgdGhpcyBk
b2N1bWVudCBhbmQgbWF5IGRlcGVuZCBvbiB0aGUgbmV0d29yawogICBpbiB3aGljaCB0aGUg
Y2xpZW50IChDRVIpIGlzIGRlc2lnbmVkIHRvIG9wZXJhdGUgYW5kIG9uIHRoZSBmdW5jdGlv
bnMKICAgdGhlIGNsaWVudCBpcyByZXF1aXJlZCB0byBwZXJmb3JtLgoKICAgVGhlIHNlY3Rp
b25zIHdoaWNoIGZvbGxvdyB1cGRhdGUgUkZDIDMzMTUgYW5kIFJGQyAzNjMzIHRvIGFjY29t
bW9kYXRlCiAgIHRoZSByZWNvbW1lbmRhdGlvbiwgdGhvdWdoIG1hbnkgb2YgdGhlIGNoYW5n
ZXMgYXJlIGFsc28gYXBwbGljYWJsZQogICBldmVuIGlmIG90aGVyIGNob2ljZXMgYXJlIHVz
ZWQuCgo0LjEuICBQbGFjZW1lbnQgb2YgU3RhdHVzIENvZGVzIGluIGFuIEFkdmVydGlzZSBN
ZXNzYWdlCgogICBJbiBSZXBseSBtZXNzYWdlcyBJQSBzcGVjaWZpYyBzdGF0dXMgY29kZXMg
KGkuZS4sIE5vQWRkcnNBdmFpbCwKICAgTm90T25MaW5rLCBOb0JpbmRpbmcsIE5vUHJlZml4
QXZhaWwpIGFyZSBlbmNhcHN1bGF0ZWQgaW4gdGhlIElBCiAgIG9wdGlvbi4gIEluIEFkdmVy
dGlzZSBtZXNzYWdlcyB0aG91Z2gsIHRoZSBOb0FkZHJzQXZhaWwgY29kZSBpcwogICByZXR1
cm5lZCBhdCBpbiB0aGUgdG9wIGxldmVsLiAgVGhpcyBtYWtlcyBzZW5zZSBpZiB0aGUgY2xp
ZW50IGlzIG9ubHkKICAgaW50ZXJlc3RlZCBpbiB0aGUgYXNzaWdubWVudCBvZiB0aGUgYWRk
cmVzc2VzIGFuZCB0aGUgZmFpbHVyZSBjYXNlIGlzCiAgIGZhdGFsLiAgSG93ZXZlciwgaWYg
dGhlIGNsaWVudCBzZW5kcyBib3RoIElBX05BIGFuZCBJQV9QRCBvcHRpb25zIGluCiAgIGEg
U29saWNpdCBtZXNzYWdlLCBpdCBpcyBwb3NzaWJsZSB0aGF0IHRoZSBzZXJ2ZXIgb2ZmZXJz
IG5vIGFkZHJlc3NlcwogICBidXQgaXQgb2ZmZXJzIHNvbWUgcHJlZml4ZXMsIGFuZCB0aGUg
Y2xpZW50IG1heSBjaG9vc2UgdG8gc2VuZCBhCiAgIFJlcXVlc3QgbWVzc2FnZSB0byBvYnRh
aW4gdGhlIG9mZmVyZWQgcHJlZml4ZXMuICBJbiB0aGlzIGNhc2UsIGl0IGlzCiAgIGJldHRl
ciBpZiB0aGUgU3RhdHVzIENvZGUgb3B0aW9uIGZvciBJQSBzcGVjaWZpYyBzdGF0dXMgY29k
ZXMgaXMKICAgZW5jYXBzdWxhdGVkIGluIHRoZSBJQSBvcHRpb24gdG8gaW5kaWNhdGUgdGhh
dCB0aGUgZmFpbHVyZSBvY2N1cnJlZAogICBmb3IgdGhlIHNwZWNpZmljIElBLiAgVGhpcyBh
bHNvIG1ha2VzIHRoZSBOb0FkZHJzQXZhaWwgYW5kCiAgIE5vUHJlZml4QXZhaWwgU3RhdHVz
IENvZGUgb3B0aW9uIHBsYWNlbWVudCBmb3IgQWR2ZXJ0aXNlIG1lc3NhZ2VzCiAgIGlkZW50
aWNhbCB0byBSZXBseSBtZXNzYWdlcy4KCiAgIEluIGFkZGl0aW9uLCBob3cgYSBzZXJ2ZXIg
Zm9ybWF0cyB0aGUgQWR2ZXJ0aXNlIG1lc3NhZ2Ugd2hlbgogICBhZGRyZXNzZXMgYXJlIG5v
dCBhdmFpbGFibGUgaGFzIGJlZW4gYSBwb2ludCBvZiBzb21lIGNvbmZ1c2lvbiBhbmQKICAg
aW1wbGVtZW50YXRpb25zIHNlZW0gdG8gdmFyeSAoc29tZSBzdHJpY3RseSBmb2xsb3cgUkZD
IDMzMTUgd2hpbGUKCgoKClRyb2FuLCBldCBhbC4gICAgICAgICAgICBFeHBpcmVzIEF1Z3Vz
dCAxNiwgMjAxNSAgICAgICAgICAgICAgICBbUGFnZSA1XQoMCkludGVybmV0LURyYWZ0ICAg
ICAgICAgIE11bHRpcGxlIFN0YXRlZnVsIE9wdGlvbnMgICAgICAgICAgRmVicnVhcnkgMjAx
NQoKCiAgIG90aGVycyBhc3N1bWVkIGl0IHdhcyBlbmNhcHN1bGF0ZWQgaW4gdGhlIElBIG9w
dGlvbiBhcyBmb3IgUmVwbHkKICAgbWVzc2FnZXMpLgoKICAgV2UgaGF2ZSBjaG9zZW4gdGhl
IGZvbGxvd2luZyBzb2x1dGlvbjoKCiAgIENsaWVudHMgTVVTVCBiZSBwcmVwYXJlZCB0byBo
YW5kbGUgZWFjaCBvZiB0aGUgZm9sbG93aW5nIEFkdmVydGlzZQogICBtZXNzYWdlcyBmb3Jt
YXRzIHdoZW4gdGhlcmUgYXJlIG5vIGFkZHJlc3NlcyBhdmFpbGFibGUgKGV2ZW4gd2hlbiBu
bwogICBvdGhlciBJQSBvcHRpb24gdHlwZXMgd2VyZSBpbiB0aGUgU29saWNpdCk6CgogICAx
LiAgQWR2ZXJ0aXNlIGNvbnRhaW5pbmcgdGhlIElBX05BcyBhbmQvb3IgSUFfVEFzIHdpdGgg
ZW5jYXBzdWxhdGVkCiAgICAgICBTdGF0dXMgQ29kZSBvcHRpb24gb2YgTm9BZGRyc0F2YWls
IGFuZCBubyB0b3AtbGV2ZWwgU3RhdHVzIENvZGUKICAgICAgIG9wdGlvbi4KCiAgIDIuICBB
ZHZlcnRpc2UgY29udGFpbmluZyBqdXN0IGEgdG9wLWxldmVsIFN0YXR1cyBDb2RlIG9wdGlv
biBvZgogICAgICAgTm9BZGRyc0F2YWlsIGFuZCBubyBJQV9OQXMvSUFfVEFzLgoKICAgMy4g
IEFkdmVydGlzZSBjb250YWluaW5nIGEgdG9wLWxldmVsIFN0YXR1cyBDb2RlIG9wdGlvbiBv
ZgogICAgICAgTm9BZGRyc0F2YWlsIGFuZCBJQV9OQXMgYW5kL29yIElBX1RBcyB3aXRoIGEg
U3RhdHVzIENvZGUgb3B0aW9uCiAgICAgICBvZiBOb0FkZHJzQXZhaWwuCgogICBOb3RlOiBD
bGllbnRzIE1VU1QgYmUgcHJlcGFyZWQgdG8gaGFuZGxlIHRoZSBsYXN0IHR3byBmb3JtYXRz
IGxpc3RlZAogICBhYm92ZSB0byBmYWNpbGl0YXRlIGJhY2t3YXJkIGNvbXBhdGliaWxpdHkg
d2l0aCB0aGUgc2VydmVycyB3aGljaAogICBoYXZlIG5vdCBiZWVuIHVwZGF0ZWQgdG8gdGhp
cyBzcGVjaWZpY2F0aW9uLgoKICAgU2VlIFNlY3Rpb24gNC4yIGZvciB1cGRhdGVkIHRleHQg
Zm9yIFNlY3Rpb24gMTcuMS4zIG9mIFJGQyAzMzE1IGFuZAogICBTZWN0aW9uIDExLjEgb2Yg
UkZDIDM2MzMuCgogICBTZXJ2ZXJzIE1VU1QgcmV0dXJuIHRoZSBTdGF0dXMgQ29kZSBvcHRp
b24gb2YgTm9BZGRyc0F2YWlsCiAgIGVuY2Fwc3VsYXRlZCBpbiBhbiBJQV9OQS9JQV9UQSBv
cHRpb25zIGFuZCBub3QgYXMgYSB0b3AtbGV2ZWwgU3RhdHVzCiAgIENvZGUgb3B0aW9uIG9m
IE5vQWRkcnNBdmFpbCB3aGVuIG5vIGFkZHJlc3NlcyB3aWxsIGJlIGFzc2lnbmVkICgxIGlu
CiAgIHRoZSBhYm92ZSBsaXN0KS4gIFRoaXMgbWVhbnMgdGhhdCB0aGUgQWR2ZXJ0aXNlIHJl
c3BvbnNlIG1hdGNoZXMgdGhlCiAgIFJlcGx5IHJlc3BvbnNlIHdpdGggcmVzcGVjdCB0byB0
aGUgaGFuZGxpbmcgb2YgdGhlIE5vQWRkcnNBdmFpbAogICBzdGF0dXMuCgogICBSZXBsYWNl
IHRoZSBmb2xsb3dpbmcgcGFyYWdyYXBoIGluIFJGQyAzMzE1LCBzZWN0aW9uIDE3LjIuMjoK
CiAgICAgIElmIHRoZSBzZXJ2ZXIgd2lsbCBub3QgYXNzaWduIGFueSBhZGRyZXNzZXMgdG8g
YW55IElBcyBpbiBhCiAgICAgIHN1YnNlcXVlbnQgUmVxdWVzdCBmcm9tIHRoZSBjbGllbnQs
IHRoZSBzZXJ2ZXIgTVVTVCBzZW5kIGFuCiAgICAgIEFkdmVydGlzZSBtZXNzYWdlIHRvIHRo
ZSBjbGllbnQgdGhhdCBpbmNsdWRlcyBvbmx5IGEgU3RhdHVzCiAgICAgIENvZGUgb3B0aW9u
IHdpdGggY29kZSBOb0FkZHJzQXZhaWwgYW5kIGEgc3RhdHVzIG1lc3NhZ2UgZm9yCiAgICAg
IHRoZSB1c2VyLCBhIFNlcnZlciBJZGVudGlmaWVyIG9wdGlvbiB3aXRoIHRoZSBzZXJ2ZXIn
cyBEVUlELAogICAgICBhbmQgYSBDbGllbnQgSWRlbnRpZmllciBvcHRpb24gd2l0aCB0aGUg
Y2xpZW50J3MgRFVJRC4KCiAgIFdpdGg6CgoKCgoKCgpUcm9hbiwgZXQgYWwuICAgICAgICAg
ICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUgICAgICAgICAgICAgICAgW1BhZ2UgNl0KDApJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAg
ICAgIEZlYnJ1YXJ5IDIwMTUKCgogICAgICBJZiB0aGUgc2VydmVyIHdpbGwgbm90IGFzc2ln
biBhbnkgYWRkcmVzc2VzIHRvIGFuIElBIGluIGEKICAgICAgc3Vic2VxdWVudCBSZXF1ZXN0
IGZyb20gdGhlIGNsaWVudCwgdGhlIHNlcnZlciBNVVNUIGluY2x1ZGUKICAgICAgdGhlIElB
IGluIHRoZSBBZHZlcnRpc2UgbWVzc2FnZSB3aXRoIG5vIGFkZHJlc3NlcyBpbiB0aGUgSUEK
ICAgICAgYW5kIGEgU3RhdHVzIENvZGUgb3B0aW9uIGVuY2Fwc3VsYXRlZCBpbiB0aGUgSUEg
Y29udGFpbmluZwogICAgICBzdGF0dXMgY29kZSBOb0FkZHJzQXZhaWwuCgo0LjIuICBBZHZl
cnRpc2UgTWVzc2FnZSBQcm9jZXNzaW5nIGJ5IGEgQ2xpZW50CgogICBbUkZDMzMxNV0gc3Bl
Y2lmaWVzIHRoYXQgYSBjbGllbnQgbXVzdCBpZ25vcmUgYW4gQWR2ZXJ0aXNlIG1lc3NhZ2Ug
aWYKICAgYSBzZXJ2ZXIgd2lsbCBub3QgYXNzaWduIGFueSBhZGRyZXNzZXMgdG8gYSBjbGll
bnQsIGFuZCBbUkZDMzYzM10KICAgc3BlY2lmaWVzIHRoYXQgYSBjbGllbnQgbXVzdCBpZ25v
cmUgYW4gQWR2ZXJ0aXNlIG1lc3NhZ2UgaWYgYSBzZXJ2ZXIKICAgcmV0dXJucyB0aGUgTm9Q
cmVmaXhBdmFpbCBzdGF0dXMgdG8gYSByZXF1ZXN0aW5nIHJvdXRlci4gIFRodXMsIGEKICAg
Y2xpZW50IHJlcXVlc3RpbmcgYm90aCBJQV9OQSBhbmQgSUFfUEQsIHdpdGggYSBzZXJ2ZXIg
dGhhdCBvbmx5CiAgIG9mZmVycyBlaXRoZXIgYWRkcmVzc2VzIG9yIGRlbGVnYXRlZCBwcmVm
aXhlcywgaXMgbm90IHN1cHBvcnRlZCBieQogICB0aGUgY3VycmVudCBwcm90b2NvbCBzcGVj
aWZpY2F0aW9ucy4KCiAgIFNvbHV0aW9uOiBhIGNsaWVudCBTSE9VTEQgYWNjZXB0IEFkdmVy
dGlzZSBtZXNzYWdlcywgZXZlbiB3aGVuIG5vdAogICBhbGwgSUEgb3B0aW9uIHR5cGVzIGFy
ZSBiZWluZyBvZmZlcmVkLiAgQW5kLCBpbiB0aGlzIGNhc2UsIHRoZSBjbGllbnQKICAgU0hP
VUxEIGluY2x1ZGUgdGhlIG5vdCBvZmZlcmVkIElBIG9wdGlvbiB0eXBlcyBpbiBpdHMgUmVx
dWVzdC4gIEEKICAgY2xpZW50IFNIT1VMRCBvbmx5IGlnbm9yZSBhbiBBZHZlcnRpc2UgbWVz
c2FnZSB3aGVuIG5vbmUgb2YgdGhlCiAgIHJlcXVlc3RlZCBJQSBvcHRpb25zIGluY2x1ZGUg
b2ZmZXJlZCBhZGRyZXNzZXMgb3IgZGVsZWdhdGVkIHByZWZpeGVzLgogICBOb3RlIHRoYXQg
aWdub3JlZCBtZXNzYWdlcyBNVVNUIHN0aWxsIGJlIHByb2Nlc3NlZCBmb3IgU09MX01BWF9S
VCBhbmQKICAgSU5GX01BWF9SVCBvcHRpb25zIGFzIHNwZWNpZmllZCBpbiBbUkZDNzA4M10u
CgogICBSZXBsYWNlIFNlY3Rpb24gMTcuMS4zIG9mIFJGQyAzMzE1OiAoZXhpc3RpbmcgZXJy
YXRhKQoKICAgICBUaGUgY2xpZW50IE1VU1QgaWdub3JlIGFueSBBZHZlcnRpc2UgbWVzc2Fn
ZSB0aGF0IGluY2x1ZGVzIGEgU3RhdHVzCiAgICAgQ29kZSBvcHRpb24gY29udGFpbmluZyB0
aGUgdmFsdWUgTm9BZGRyc0F2YWlsLCB3aXRoIHRoZSBleGNlcHRpb24KICAgICB0aGF0IHRo
ZSBjbGllbnQgTUFZIGRpc3BsYXkgdGhlIGFzc29jaWF0ZWQgc3RhdHVzIG1lc3NhZ2Uocykg
dG8gdGhlCiAgICAgdXNlci4KCiAgIFdpdGggKHRoaXMgaW5jbHVkZXMgdGhlIGNoYW5nZXMg
bWFkZSBieSBbUkZDNzA4M10pOgoKICAgICBUaGUgY2xpZW50IE1VU1QgaWdub3JlIGFueSBB
ZHZlcnRpc2UgbWVzc2FnZSB0aGF0IGNvbnRhaW5zIG5vCiAgICAgYWRkcmVzc2VzIChJQUFE
RFIgb3B0aW9ucyBlbmNhcHN1bGF0ZWQgaW4gSUFfTkEgb3IgSUFfVEEgb3B0aW9ucykKICAg
ICBhbmQgbm8gZGVsZWdhdGVkIHByZWZpeGVzIChJQVBSRUZJWCBvcHRpb25zIGVuY2Fwc3Vs
YXRlZCBpbiBJQV9QRAogICAgIG9wdGlvbnMsIHNlZSBSRkMgMzYzMykgd2l0aCB0aGUgZXhj
ZXB0aW9uIHRoYXQgdGhlIGNsaWVudDoKICAgICAgIC0gTVVTVCBwcm9jZXNzIGFuIGluY2x1
ZGVkIFNPTF9NQVhfUlQgb3B0aW9uIChSRkMgNzA4MyksCiAgICAgICAtIE1VU1QgcHJvY2Vz
cyBhbiBpbmNsdWRlZCBJTkZfTUFYX1JUIG9wdGlvbiAoUkZDIDcwODMpLCBhbmQKICAgICAg
IC0gTUFZIGRpc3BsYXkgYW55IGFzc29jaWF0ZWQgc3RhdHVzIG1lc3NhZ2UocykgdG8gdGhl
IHVzZXIuCiAgICAgVGhlIGNsaWVudCBpZ25vcmluZyB0aGlzIEFkdmVydGlzZSBtZXNzYWdl
IE1VU1QgTk9UIHJlc3RhcnQgdGhlCiAgICAgU29saWNpdCByZXRyYW5zbWlzc2lvbiB0aW1l
ci4KCiAgIEFuZCwgcmVwbGFjZToKCiAgICAgLSAgVGhlIGNsaWVudCBNQVkgY2hvb3NlIGEg
bGVzcy1wcmVmZXJyZWQgc2VydmVyIGlmIHRoYXQgc2VydmVyCiAgICAgICAgaGFzIGEgYmV0
dGVyIHNldCBvZiBhZHZlcnRpc2VkIHBhcmFtZXRlcnMsIHN1Y2ggYXMgdGhlCiAgICAgICAg
YXZhaWxhYmxlIGFkZHJlc3NlcyBhZHZlcnRpc2VkIGluIElBcy4KCgoKVHJvYW4sIGV0IGFs
LiAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAgICAgIFtQ
YWdlIDddCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVmdWwgT3B0
aW9ucyAgICAgICAgICBGZWJydWFyeSAyMDE1CgoKICAgV2l0aDoKCiAgICAgLSAgVGhlIGNs
aWVudCBNQVkgY2hvb3NlIGEgbGVzcy1wcmVmZXJyZWQgc2VydmVyIGlmIHRoYXQgc2VydmVy
IGhhcwogICAgICAgIGEgYmV0dGVyIHNldCBvZiBhZHZlcnRpc2VkIHBhcmFtZXRlcnMsIHN1
Y2ggYXMgdGhlIGF2YWlsYWJsZSBzZXQKICAgICAgICBvZiBJQXMsIGFzIHdlbGwgYXMgdGhl
IHNldCBvZiBvdGhlciBjb25maWd1cmF0aW9uIG9wdGlvbnMKICAgICAgICBhZHZlcnRpc2Vk
LgoKICAgQW5kLCByZXBsYWNlIHRoZSBsYXN0IHBhcmFncmFwaCBvZiBTZWN0aW9uIDExLjEg
b2YgUkZDIDM2MzMgd2l0aDoKCiAgICAgVGhlIHJlcXVlc3Rpbmcgcm91dGVyIE1VU1QgaWdu
b3JlIGFueSBBZHZlcnRpc2UgbWVzc2FnZSB0aGF0CiAgICAgY29udGFpbnMgbm8gYWRkcmVz
c2VzIChJQUFERFIgb3B0aW9ucyBlbmNhcHN1bGF0ZWQgaW4gSUFfTkEgb3IKICAgICBJQV9U
QSBvcHRpb25zKSBhbmQgbm8gZGVsZWdhdGVkIHByZWZpeGVzIChJQVBSRUZJWCBvcHRpb25z
CiAgICAgZW5jYXBzdWxhdGVkIGluIElBX1BEIG9wdGlvbnMsIHNlZSBSRkMgMzYzMykgd2l0
aCB0aGUgZXhjZXB0aW9uCiAgICAgdGhhdCB0aGUgcmVxdWVzdGluZyByb3V0ZXI6CiAgICAg
ICAtIE1VU1QgcHJvY2VzcyBhbiBpbmNsdWRlZCBTT0xfTUFYX1JUIG9wdGlvbiAoUkZDIDcw
ODMpLAogICAgICAgLSBNVVNUIHByb2Nlc3MgYW4gaW5jbHVkZWQgSU5GX01BWF9SVCBvcHRp
b24gKFJGQyA3MDgzKSwgYW5kCiAgICAgICAtIE1BWSBkaXNwbGF5IGFueSBhc3NvY2lhdGVk
IHN0YXR1cyBtZXNzYWdlKHMpIHRvIHRoZSB1c2VyLgogICAgIFRoZSByZXF1ZXN0aW5nIHJv
dXRlciBpZ25vcmluZyB0aGlzIEFkdmVydGlzZSBtZXNzYWdlIE1VU1QgTk9UCiAgICAgcmVz
dGFydCB0aGUgU29saWNpdCByZXRyYW5zbWlzc2lvbiB0aW1lci4KCjQuMy4gIFQxL1QyIFRp
bWVycwoKICAgVGhlIFQxIGFuZCBUMiB0aW1lcyBkZXRlcm1pbmUgd2hlbiB0aGUgY2xpZW50
IHdpbGwgY29udGFjdCB0aGUgc2VydmVyCiAgIHRvIGV4dGVuZCBsaWZldGltZXMgb2YgaW5m
b3JtYXRpb24gcmVjZWl2ZWQgaW4gYW4gSUEuICBIb3cgc2hvdWxkIGEKICAgY2xpZW50IGhh
bmRsZSB0aGUgY2FzZSB3aGVyZSBtdWx0aXBsZSBJQSBvcHRpb25zIGhhdmUgZGlmZmVyZW50
IFQxCiAgIGFuZCBUMiB0aW1lcz8KCiAgIEluIGEgbXVsdGlwbGUgSUEgb3B0aW9uIHR5cGUg
bW9kZWwsIHRoZSBUMS9UMiB0aW1lcyBhcmUgcHJvdG9jb2wKICAgdGltZXJzLCB0aGF0IHNo
b3VsZCBiZSBpbmRlcGVuZGVudCBvZiB0aGUgSUEgb3B0aW9ucyB0aGVtc2VsdmVzLiAgSWYK
ICAgd2Ugd2VyZSB0byByZWRvIHRoZSBESENQIHByb3RvY29sIGZyb20gc2NyYXRjaCB0aGUg
VDEvVDIgdGltZXMgc2hvdWxkCiAgIGJlIGNhcnJpZWQgaW4gYSBzZXBhcmF0ZSBESENQIG9w
dGlvbi4KCiAgIFNvbHV0aW9uOiBUaGUgc2VydmVyIE1VU1Qgc2V0IHRoZSBUMS9UMiB0aW1l
cyBpbiBhbGwgSUEgb3B0aW9ucyBpbiBhCiAgIFJlcGx5IG9yIEFkdmVydGlzZSBtZXNzYWdl
IHRvIHRoZSBzYW1lIHZhbHVlLiAgVG8gZGVhbCB3aXRoIHRoZSBjYXNlCiAgIHdoZXJlIHNl
cnZlcnMgaGF2ZSBub3QgeWV0IGJlZW4gdXBkYXRlZCB0byBkbyB0aGF0LCB0aGUgY2xpZW50
IE1VU1QKICAgc2VsZWN0IGEgVDEgYW5kIFQyIHRpbWUgZnJvbSBhbGwgSUEgb3B0aW9ucyB3
aGljaCB3aWxsIGd1YXJhbnRlZSB0aGF0CiAgIHRoZSBjbGllbnQgd2lsbCBzZW5kIFJlbmV3
L1JlYmluZCBtZXNzYWdlcyBub3QgbGF0ZXIgdGhhbiBhdCB0aGUgVDEvCiAgIFQyIHRpbWVz
IGFzc29jaWF0ZWQgd2l0aCBhbnkgb2YgdGhlIGNsaWVudCdzIGJpbmRpbmdzLgoKICAgQXMg
YW4gZXhhbXBsZSwgaWYgdGhlIGNsaWVudCByZWNlaXZlcyBhIFJlcGx5IHdpdGggVDFfTkEg
b2YgMzYwMCAvCiAgIFQyX05BIG9mIDU3NjAgYW5kIFQxX1BEIG9mIDAgLyBUMl9QRCBvZiAx
ODAwLCB0aGUgY2xpZW50IFNIT1VMRCB1c2UKICAgdGhlIFQxX1BEIG9mIDAgLyBUMl9QRCBv
ZiAxODAwLiAgVGhlIHJlYXNvbiBmb3IgdGhpcyBpcyB0aGF0IGEgVDEgb2YKICAgMCBtZWFu
cyB0aGF0IHRoZSBSZW5ldyB0aW1lIGlzIGF0IHRoZSBjbGllbnQncyBkaXNjcmV0aW9uLCBi
dXQgdGhpcwogICB2YWx1ZSBjYW5ub3QgYmUgZ3JlYXRlciB0aGFuIHRoZSBUMiB2YWx1ZSAo
MTgwMCkuCgogICBUaGUgZm9sbG93aW5nIHBhcmFncmFwaCBzaG91bGQgYmUgYWRkZWQgdG8g
U2VjdGlvbnMgMTguMi4xLCAxOC4yLjMsCiAgIGFuZCAxOC4yLjQgb2YgUkZDIDMzMTU6CgoK
CgpUcm9hbiwgZXQgYWwuICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUgICAg
ICAgICAgICAgICAgW1BhZ2UgOF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0aXBs
ZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAgICAgIEZlYnJ1YXJ5IDIwMTUKCgogICAgIFRoZSBU
MS9UMiB0aW1lcyBzZXQgaW4gZWFjaCBhcHBsaWNhYmxlIElBIG9wdGlvbiBmb3IgYSBSZXBs
eSBNVVNUCiAgICAgYmUgdGhlIHNhbWUgdmFsdWVzIGFjcm9zcyBhbGwgSUFzLiAgVGhlIHNl
cnZlciBNVVNUIGRldGVybWluZSB0aGUKICAgICBUMS9UMiB0aW1lcyBhY3Jvc3MgYWxsIG9m
IHRoZSBhcHBsaWNhYmxlIGNsaWVudCdzIGJpbmRpbmdzIGluIHRoZQogICAgIFJlcGx5LiAg
VGhpcyBmYWNpbGl0YXRlcyB0aGUgY2xpZW50IGJlaW5nIGFibGUgdG8gcmVuZXcgYWxsIG9m
IHRoZQogICAgIGJpbmRpbmdzIGF0IHRoZSBzYW1lIHRpbWUuCgogICBOb3RlOiBUaGlzIGFk
ZGl0aW9uYWwgcGFyYWdyYXBoIGhhcyBhbHNvIGJlZW4gaW5jbHVkZWQgaW4gdGhlIHJldmlz
ZWQKICAgdGV4dCBsYXRlciBmb3IgU2VjdGlvbnMgMTguMi4zIGFuZCAxOC4yLjQgb2YgUkZD
IDMzMTUuCgogICBDaGFuZ2VzIGZvciBjbGllbnQgVDEvVDIgaGFuZGxpbmcgYXJlIGluY2x1
ZGVkIGluIFNlY3Rpb24gNC40LjMgYW5kCiAgIFNlY3Rpb24gNC40LjQuCgo0LjQuICBSZW5l
dyBhbmQgUmViaW5kIE1lc3NhZ2VzCgogICBUaGlzIHNlY3Rpb24gcHJlc2VudHMgaXNzdWVz
IHdpdGggaGFuZGxpbmcgbXVsdGlwbGUgSUEgb3B0aW9uIHR5cGVzCiAgIGluIHRoZSBjb250
ZXh0IG9mIGNyZWF0aW9uIGFuZCBwcm9jZXNzaW5nIHRoZSBSZW5ldyBhbmQgUmViaW5kCiAg
IG1lc3NhZ2VzLiAgSXQgYWxzbyBpbnRyb2R1Y2VzIHJlbGV2YW50IHVwZGF0ZXMgdG8gdGhl
IFtSRkMzMzE1XSBhbmQKICAgW1JGQzM2MzNdLgoKNC40LjEuICBSZW5ldyBNZXNzYWdlCgog
ICBJbiBtdWx0aXBsZSBJQSBvcHRpb24gdHlwZSBtb2RlbCwgdGhlIGNsaWVudCBtYXkgaW5j
bHVkZSBtdWx0aXBsZSBJQQogICBvcHRpb25zIGluIHRoZSBSZXF1ZXN0IG1lc3NhZ2UsIGFu
ZCB0aGUgc2VydmVyIG1heSBjcmVhdGUgYmluZGluZ3MKICAgb25seSBmb3IgYSBzdWJzZXQg
b2YgdGhlIElBIG9wdGlvbnMgaW5jbHVkZWQgYnkgdGhlIGNsaWVudC4gIEZvciB0aGUKICAg
SUEgb3B0aW9ucyBpbiB0aGUgUmVxdWVzdCBtZXNzYWdlIGZvciB3aGljaCB0aGUgc2VydmVy
IGRvZXMgbm90CiAgIGNyZWF0ZSB0aGUgYmluZGluZ3MsIHRoZSBzZXJ2ZXIgc2VuZHMgdGhl
IElBIG9wdGlvbnMgaW4gdGhlIFJlcGx5CiAgIG1lc3NhZ2Ugd2l0aCB0aGUgTm9BZGRyc0F2
YWlsIG9yIE5vUHJlZml4QXZhaWwgc3RhdHVzIGNvZGVzLgoKICAgVGhlIGNsaWVudCBtYXkg
YWNjZXB0IHRoZSBiaW5kaW5ncyBjcmVhdGVkIGJ5IHRoZSBzZXJ2ZXIsIGJ1dCBtYXkKICAg
ZGVzaXJlIHRoZSBvdGhlciBiaW5kaW5ncyB0byBiZSBjcmVhdGVkIG9uY2UgdGhleSBiZWNv
bWUgYXZhaWxhYmxlLAogICBlLmcuIHdoZW4gdGhlIHNlcnZlciBjb25maWd1cmF0aW9uIGlz
IGNoYW5nZWQuICBUaGUgY2xpZW50IHdoaWNoCiAgIGFjY2VwdGVkIHRoZSBiaW5kaW5ncyBj
cmVhdGVkIGJ5IHRoZSBzZXJ2ZXIgd2lsbCBwZXJpb2RpY2FsbHkgc2VuZCBhCiAgIFJlbmV3
IG1lc3NhZ2UgdG8gZXh0ZW5kIHRoZWlyIGxpZmV0aW1lcy4gIEhvd2V2ZXIsIHRoZSBSZW5l
dyBtZXNzYWdlLAogICBhcyBkZXNjcmliZWQgaW4gdGhlIFtSRkMzMzE1XSwgZG9lcyBub3Qg
c3VwcG9ydCB0aGUgYWJpbGl0eSBmb3IgdGhlCiAgIGNsaWVudCB0byBleHRlbmQgdGhlIGxp
ZmV0aW1lcyBvZiB0aGUgYmluZGluZ3MgZm9yIHNvbWUgSUFzLCB3aGlsZQogICByZXF1ZXN0
aW5nIGJpbmRpbmdzIGZvciBvdGhlciBJQXMuCgogICBTb2x1dGlvbjogVGhlIGNsaWVudCwg
d2hpY2ggc2VuZHMgYSBSZW5ldyBtZXNzYWdlIHRvIGV4dGVuZCB0aGUKICAgbGlmZXRpbWVz
IG9mIHRoZSBiaW5kaW5ncyBhc3NpZ25lZCB0byB0aGUgY2xpZW50LCBzaG91bGQgaW5jbHVk
ZSBJQQogICBvcHRpb25zIGZvciB0aGVzZSBiaW5kaW5ncyBhcyB3ZWxsIGFzIElBIG9wdGlv
bnMgZm9yIGFsbCBvdGhlcgogICBiaW5kaW5ncyB0aGF0IHRoZSBjbGllbnQgZGVzaXJlcyBi
dXQgaGFzIGJlZW4gdW5hYmxlIHRvIG9idGFpbi4gIFRoZQogICBjbGllbnQgYW5kIHNlcnZl
ciBwcm9jZXNzaW5nIG5lZWQgdG8gYmUgbW9kaWZpZWQuICBOb3RlIHRoYXQgdGhpcwogICBj
aGFuZ2UgbWFrZXMgdGhlIHNlcnZlcidzIElBIHByb2Nlc3Npbmcgb2YgUmVuZXcgc2ltaWxh
ciB0byB0aGUKICAgUmVxdWVzdCBwcm9jZXNzaW5nLgoKCgoKCgoKVHJvYW4sIGV0IGFsLiAg
ICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAgICAgIFtQYWdl
IDldCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVmdWwgT3B0aW9u
cyAgICAgICAgICBGZWJydWFyeSAyMDE1CgoKNC40LjIuICBSZWJpbmQgTWVzc2FnZQoKICAg
QWNjb3JkaW5nIHRvIHRoZSBTZWN0aW9uIDQuNC4xLCB0aGUgY2xpZW50IGluY2x1ZGVzIElB
IG9wdGlvbnMgaW4gYQogICBSZW5ldyBtZXNzYWdlIGZvciB0aGUgYmluZGluZ3MgaXQgZGVz
aXJlcyBidXQgaGFzIGJlZW4gdW5hYmxlIHRvCiAgIG9idGFpbiBieSBzZW5kaW5nIGEgUmVx
dWVzdCBtZXNzYWdlLCBhcGFydCBmcm9tIHRoZSBJQSBvcHRpb25zIGZvcgogICB0aGUgZXhp
c3RpbmcgYmluZGluZ3MuCgogICBBdCB0aW1lIFQyLCB0aGUgY2xpZW50IHN0b3BzIHNlbmRp
bmcgUmVuZXcgbWVzc2FnZXMgdG8gdGhlIHNlcnZlciBhbmQKICAgaW5pdGlhdGVzIHRoZSBS
ZWJpbmQvUmVwbHkgbWVzc2FnZSBleGNoYW5nZSB3aXRoIGFueSBhdmFpbGFibGUKICAgc2Vy
dmVyLiAgSW4gdGhpcyBjYXNlLCBpdCBzaG91bGQgYmUgcG9zc2libGUgdG8gY29udGludWUg
dHJ5aW5nIHRvCiAgIG9idGFpbiBuZXcgYmluZGluZ3MgdXNpbmcgdGhlIFJlYmluZCBtZXNz
YWdlIGlmIHRoZSBjbGllbnQgZmFpbGVkIHRvCiAgIGdldCB0aGUgcmVzcG9uc2UgZnJvbSB0
aGUgc2VydmVyIHRvIHRoZSBSZW5ldyBtZXNzYWdlLgoKICAgU29sdXRpb246IFRoZSBjbGll
bnQgc2hvdWxkIGNvbnRpbnVlIHRvIGluY2x1ZGUgdGhlIElBIG9wdGlvbnMKICAgcmVjZWl2
ZWQgZnJvbSB0aGUgc2VydmVyIGFuZCBpdCBtYXkgaW5jbHVkZSBhZGRpdGlvbmFsIElBIG9w
dGlvbnMgdG8KICAgcmVxdWVzdCBjcmVhdGlvbiBvZiB0aGUgYWRkaXRpb25hbCBiaW5kaW5n
cy4KCjQuNC4zLiAgVXBkYXRlcyB0byBzZWN0aW9uIDE4LjEuMyBvZiBSRkMgMzMxNQoKICAg
UmVwbGFjZSBTZWN0aW9uIDE4LjEuMyBvZiBSRkMgMzMxNSB3aXRoIHRoZSBmb2xsb3dpbmcg
dGV4dDoKCiAgICAgVG8gZXh0ZW5kIHRoZSB2YWxpZCBhbmQgcHJlZmVycmVkIGxpZmV0aW1l
cyBmb3IgdGhlIGFkZHJlc3NlcwogICAgIGFzc2lnbmVkIHRvIGFuIElBLCB0aGUgY2xpZW50
IHNlbmRzIGEgUmVuZXcgbWVzc2FnZSB0byB0aGUgc2VydmVyCiAgICAgZnJvbSB3aGljaCB0
aGUgYWRkcmVzc2VzIHdlcmUgb2J0YWluZWQsIHdoaWNoIGluY2x1ZGVzIGFuIElBIG9wdGlv
bgogICAgIGZvciB0aGUgSUEgd2hvc2UgYWRkcmVzcyBsaWZldGltZXMgYXJlIHRvIGJlIGV4
dGVuZGVkLiAgVGhlIGNsaWVudAogICAgIGluY2x1ZGVzIElBIEFkZHJlc3Mgb3B0aW9ucyB3
aXRoaW4gdGhlIElBIG9wdGlvbiBmb3IgdGhlIGFkZHJlc3NlcwogICAgIGFzc2lnbmVkIHRv
IHRoZSBJQS4gIFRoZSBzZXJ2ZXIgZGV0ZXJtaW5lcyBuZXcgbGlmZXRpbWVzIGZvciB0aGVz
ZQogICAgIGFkZHJlc3NlcyBhY2NvcmRpbmcgdG8gdGhlIGFkbWluaXN0cmF0aXZlIGNvbmZp
Z3VyYXRpb24gb2YgdGhlCiAgICAgc2VydmVyLiAgVGhlIHNlcnZlciBtYXkgYWxzbyBhZGQg
bmV3IGFkZHJlc3NlcyB0byB0aGUgSUEuICBUaGUKICAgICBzZXJ2ZXIgY2FuIHJlbW92ZSBh
ZGRyZXNzZXMgZnJvbSB0aGUgSUEgYnkgcmV0dXJuaW5nIElBIEFkZHJlc3MKICAgICBvcHRp
b25zIGZvciBzdWNoIGFkZHJlc3NlcyB3aXRoIHByZWZlcnJlZCBhbmQgdmFsaWQgbGlmZXRp
bWVzIHNldAogICAgIHRvIHplcm8uCgogICAgIFRoZSBzZXJ2ZXIgY29udHJvbHMgdGhlIHRp
bWUgYXQgd2hpY2ggdGhlIGNsaWVudCBjb250YWN0cyB0aGUKICAgICBzZXJ2ZXIgdG8gZXh0
ZW5kIHRoZSBsaWZldGltZXMgb24gYXNzaWduZWQgYWRkcmVzc2VzIHRocm91Z2ggdGhlIFQx
CiAgICAgYW5kIFQyIHBhcmFtZXRlcnMgYXNzaWduZWQgdG8gYW4gSUEuICBIb3dldmVyLCBh
cyB0aGUgY2xpZW50CiAgICAgUmVuZXdzL1JlYmluZHMgYWxsIElBcyBmcm9tIHRoZSBzZXJ2
ZXIgYXQgdGhlIHNhbWUgdGltZSwgdGhlIGNsaWVudAogICAgIE1VU1Qgc2VsZWN0IGEgVDEg
YW5kIFQyIHRpbWUgZnJvbSBhbGwgSUEgb3B0aW9ucyB3aGljaCB3aWxsCiAgICAgZ3VhcmFu
dGVlIHRoYXQgdGhlIGNsaWVudCB3aWxsIHNlbmQgUmVuZXcvUmViaW5kIG1lc3NhZ2VzIG5v
dCBsYXRlcgogICAgIHRoYW4gYXQgdGhlIFQxL1QyIHRpbWVzIGFzc29jaWF0ZWQgd2l0aCBh
bnkgb2YgdGhlIGNsaWVudCdzCiAgICAgYmluZGluZ3MuCgogICAgIEF0IHRpbWUgVDEsIHRo
ZSBjbGllbnQgaW5pdGlhdGVzIGEgUmVuZXcvUmVwbHkgbWVzc2FnZSBleGNoYW5nZSB0bwog
ICAgIGV4dGVuZCB0aGUgbGlmZXRpbWVzIG9uIGFueSBhZGRyZXNzZXMgaW4gdGhlIElBLgoK
ICAgICBJZiBUMSBvciBUMiBoYWQgYmVlbiBzZXQgdG8gMCBieSB0aGUgc2VydmVyIChmb3Ig
YW4gSUFfTkEpIG9yIHRoZXJlCiAgICAgYXJlIG5vIFQxIG9yIFQyIHRpbWVzIChmb3IgYW4g
SUFfVEEpIGluIGEgcHJldmlvdXMgUmVwbHksIHRoZQoKCgoKVHJvYW4sIGV0IGFsLiAgICAg
ICAgICAgIEV4cGlyZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAgICAgW1BhZ2UgMTBd
CgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVmdWwgT3B0aW9ucyAg
ICAgICAgICBGZWJydWFyeSAyMDE1CgoKICAgICBjbGllbnQgbWF5IHNlbmQgYSBSZW5ldyBv
ciBSZWJpbmQgbWVzc2FnZSwgcmVzcGVjdGl2ZWx5LCBhdCB0aGUKICAgICBjbGllbnQncyBk
aXNjcmV0aW9uLgoKICAgICBUaGUgY2xpZW50IHNldHMgdGhlICJtc2ctdHlwZSIgZmllbGQg
dG8gUkVORVcuICBUaGUgY2xpZW50CiAgICAgZ2VuZXJhdGVzIGEgdHJhbnNhY3Rpb24gSUQg
YW5kIGluc2VydHMgdGhpcyB2YWx1ZSBpbiB0aGUKICAgICAidHJhbnNhY3Rpb24taWQiIGZp
ZWxkLgoKICAgICBUaGUgY2xpZW50IHBsYWNlcyB0aGUgaWRlbnRpZmllciBvZiB0aGUgZGVz
dGluYXRpb24gc2VydmVyIGluIGEKICAgICBTZXJ2ZXIgSWRlbnRpZmllciBvcHRpb24uCgog
ICAgIFRoZSBjbGllbnQgTVVTVCBpbmNsdWRlIGEgQ2xpZW50IElkZW50aWZpZXIgb3B0aW9u
IHRvIGlkZW50aWZ5CiAgICAgaXRzZWxmIHRvIHRoZSBzZXJ2ZXIuICBUaGUgY2xpZW50IGFk
ZHMgYW55IGFwcHJvcHJpYXRlIG9wdGlvbnMsCiAgICAgaW5jbHVkaW5nIG9uZSBvciBtb3Jl
IElBIG9wdGlvbnMuCgogICAgIEZvciBJQXMgdG8gd2hpY2ggYWRkcmVzc2VzIGhhdmUgYmVl
biBhc3NpZ25lZCwgdGhlIGNsaWVudCBpbmNsdWRlcwogICAgIGEgY29ycmVzcG9uZGluZyBJ
QSBvcHRpb24gY29udGFpbmluZyBhbiBJQSBBZGRyZXNzIG9wdGlvbiBmb3IgZWFjaAogICAg
IGFkZHJlc3MgYXNzaWduZWQgdG8gdGhlIElBLiAgVGhlIGNsaWVudCBNVVNUIE5PVCBpbmNs
dWRlIGFkZHJlc3NlcwogICAgIGluIGFueSBJQSBvcHRpb24gdGhhdCB0aGUgY2xpZW50IGRp
ZCBub3Qgb2J0YWluIGZyb20gdGhlIHNlcnZlciBvcgogICAgIHRoYXQgYXJlIG5vIGxvbmdl
ciB2YWxpZCAodGhhdCBoYXZlIGEgemVybyB2YWxpZCBsaWZldGltZSkuCgogICAgIFRoZSBj
bGllbnQgTUFZIGluY2x1ZGUgYW4gSUEgb3B0aW9uIGZvciBlYWNoIGJpbmRpbmcgaXQgZGVz
aXJlcyBidXQKICAgICBoYXMgYmVlbiB1bmFibGUgdG8gb2J0YWluLiAgVGhpcyBJQSBvcHRp
b24gTVVTVCBOT1QgY29udGFpbiBhbnkKICAgICBhZGRyZXNzZXMuICBIb3dldmVyLCBpdCBN
QVkgY29udGFpbiB0aGUgSUEgQWRkcmVzcyBvcHRpb24gd2l0aCBJUHY2CiAgICAgYWRkcmVz
cyBmaWVsZCBzZXQgdG8gMCB0byBpbmRpY2F0ZSB0aGUgY2xpZW50J3MgcHJlZmVyZW5jZSBm
b3IgdGhlCiAgICAgcHJlZmVycmVkIGFuZCB2YWxpZCBsaWZldGltZXMgZm9yIGFueSBuZXds
eSBhc3NpZ25lZCBhZGRyZXNzZXMuCgogICAgIFRoZSBjbGllbnQgTVVTVCBpbmNsdWRlIGFu
IE9wdGlvbiBSZXF1ZXN0IG9wdGlvbiAoc2VlIHNlY3Rpb24gMjIuNykKICAgICB0byBpbmRp
Y2F0ZSB0aGUgb3B0aW9ucyB0aGUgY2xpZW50IGlzIGludGVyZXN0ZWQgaW4gcmVjZWl2aW5n
LiAgVGhlCiAgICAgY2xpZW50IE1BWSBpbmNsdWRlIG9wdGlvbnMgd2l0aCBkYXRhIHZhbHVl
cyBhcyBoaW50cyB0byB0aGUgc2VydmVyCiAgICAgYWJvdXQgcGFyYW1ldGVyIHZhbHVlcyB0
aGUgY2xpZW50IHdvdWxkIGxpa2UgdG8gaGF2ZSByZXR1cm5lZC4KCiAgICAgVGhlIGNsaWVu
dCB0cmFuc21pdHMgdGhlIG1lc3NhZ2UgYWNjb3JkaW5nIHRvIHNlY3Rpb24gMTQsIHVzaW5n
IHRoZQogICAgIGZvbGxvd2luZyBwYXJhbWV0ZXJzOgoKICAgICAgICBJUlQgICAgIFJFTl9U
SU1FT1VUCgogICAgICAgIE1SVCAgICAgUkVOX01BWF9SVAoKICAgICAgICBNUkMgICAgIDAK
CiAgICAgICAgTVJEICAgICBSZW1haW5pbmcgdGltZSB1bnRpbCBUMgoKICAgICBUaGUgbWVz
c2FnZSBleGNoYW5nZSBpcyB0ZXJtaW5hdGVkIHdoZW4gdGltZSBUMiBpcyByZWFjaGVkIChz
ZWUKICAgICBzZWN0aW9uIDE4LjEuNCksIGF0IHdoaWNoIHRpbWUgdGhlIGNsaWVudCBiZWdp
bnMgYSBSZWJpbmQgbWVzc2FnZQogICAgIGV4Y2hhbmdlLgoKCgoKCgpUcm9hbiwgZXQgYWwu
ICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUgICAgICAgICAgICAgICBbUGFn
ZSAxMV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0aXBsZSBTdGF0ZWZ1bCBPcHRp
b25zICAgICAgICAgIEZlYnJ1YXJ5IDIwMTUKCgo0LjQuNC4gIFVwZGF0ZXMgdG8gU2VjdGlv
biAxOC4xLjQgb2YgUkZDIDMzMTUKCiAgIFJlcGxhY2UgU2VjdGlvbiAxOC4xLjQgb2YgUkZD
IDMzMTUgd2l0aCB0aGUgZm9sbG93aW5nIHRleHQ6CgogICAgIEF0IHRpbWUgVDIgKHdoaWNo
IHdpbGwgb25seSBiZSByZWFjaGVkIGlmIHRoZSBzZXJ2ZXIgdG8gd2hpY2ggdGhlCiAgICAg
UmVuZXcgbWVzc2FnZSB3YXMgc2VudCBhdCB0aW1lIFQxIGhhcyBub3QgcmVzcG9uZGVkKSwg
dGhlIGNsaWVudAogICAgIGluaXRpYXRlcyBhIFJlYmluZC9SZXBseSBtZXNzYWdlIGV4Y2hh
bmdlIHdpdGggYW55IGF2YWlsYWJsZQogICAgIHNlcnZlci4KCiAgICAgVGhlIGNsaWVudCBj
b25zdHJ1Y3RzIHRoZSBSZWJpbmQgbWVzc2FnZSBhcyBkZXNjcmliZWQgaW4gMTguMS4zCiAg
ICAgd2l0aCB0aGUgZm9sbG93aW5nIGRpZmZlcmVuY2VzOgoKICAgICAtICBUaGUgY2xpZW50
IHNldHMgdGhlICJtc2ctdHlwZSIgZmllbGQgdG8gUkVCSU5ELgoKICAgICAtICBUaGUgY2xp
ZW50IGRvZXMgbm90IGluY2x1ZGUgdGhlIFNlcnZlciBJZGVudGlmaWVyIG9wdGlvbiBpbiB0
aGUKICAgICAgICBSZWJpbmQgbWVzc2FnZS4KCiAgICAgVGhlIGNsaWVudCB0cmFuc21pdHMg
dGhlIG1lc3NhZ2UgYWNjb3JkaW5nIHRvIHNlY3Rpb24gMTQsIHVzaW5nIHRoZQogICAgIGZv
bGxvd2luZyBwYXJhbWV0ZXJzOgoKICAgICAgICBJUlQgICAgIFJFQl9USU1FT1VUCgogICAg
ICAgIE1SVCAgICAgUkVCX01BWF9SVAoKICAgICAgICBNUkMgICAgIDAKCiAgICAgICAgTVJE
ICAgICBSZW1haW5pbmcgdGltZSB1bnRpbCB2YWxpZCBsaWZldGltZXMgb2YgYWxsIGFkZHJl
c3NlcyBpbgogICAgICAgICAgICAgICAgYWxsIElBcyBoYXZlIGV4cGlyZWQKCiAgICAgSWYg
YWxsIGFkZHJlc3NlcyBmb3IgYW4gSUEgaGF2ZSBleHBpcmVkIHRoZSBjbGllbnQgbWF5IGNo
b29zZSB0bwogICAgIGluY2x1ZGUgdGhpcyBJQSB3aXRob3V0IGFueSBhZGRyZXNzZXMgKG9y
IHdpdGggb25seSBhIGhpbnQgZm9yCiAgICAgbGlmZXRpbWVzKSBpbiBzdWJzZXF1ZW50IFJl
YmluZCBtZXNzYWdlcyB0byBpbmRpY2F0ZSB0aGF0IHRoZQogICAgIGNsaWVudCBpcyBpbnRl
cmVzdGVkIGluIGFzc2lnbm1lbnQgb2YgdGhlIGFkZHJlc3NlcyB0byB0aGlzIElBLgoKICAg
ICBUaGUgbWVzc2FnZSBleGNoYW5nZSBpcyB0ZXJtaW5hdGVkIHdoZW4gdGhlIHZhbGlkIGxp
ZmV0aW1lcyBvZiBhbGwKICAgICBhZGRyZXNzZXMgYWNyb3NzIGFsbCBJQXMgaGF2ZSBleHBp
cmVkLCBhdCB3aGljaCB0aW1lIHRoZSBjbGllbnQKICAgICB1c2VzIFNvbGljaXQgbWVzc2Fn
ZSB0byBsb2NhdGUgYSBuZXcgREhDUCBzZXJ2ZXIgYW5kIHNlbmRzIGEKICAgICBSZXF1ZXN0
IGZvciB0aGUgZXhwaXJlZCBJQXMgdG8gdGhlIG5ldyBzZXJ2ZXIuCgo0LjQuNS4gIFVwZGF0
ZXMgdG8gU2VjdGlvbiAxOC4xLjggb2YgUkZDIDMzMTUKCiAgIFJlcGxhY2UgU2VjdGlvbiAx
OC4xLjggb2YgUkZDIDMzMTUgd2l0aCB0aGUgZm9sbG93aW5nIHRleHQ6CgogICAgIFVwb24g
dGhlIHJlY2VpcHQgb2YgYSB2YWxpZCBSZXBseSBtZXNzYWdlIGluIHJlc3BvbnNlIHRvIGEg
U29saWNpdAogICAgICh3aXRoIGEgUmFwaWQgQ29tbWl0IG9wdGlvbiksIFJlcXVlc3QsIENv
bmZpcm0sIFJlbmV3LCBSZWJpbmQgb3IKICAgICBJbmZvcm1hdGlvbi1yZXF1ZXN0IG1lc3Nh
Z2UsIHRoZSBjbGllbnQgZXh0cmFjdHMgdGhlIGNvbmZpZ3VyYXRpb24KICAgICBpbmZvcm1h
dGlvbiBjb250YWluZWQgaW4gdGhlIFJlcGx5LiAgVGhlIGNsaWVudCBNQVkgY2hvb3NlIHRv
CgoKCgpUcm9hbiwgZXQgYWwuICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUg
ICAgICAgICAgICAgICBbUGFnZSAxMl0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0
aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAgICAgIEZlYnJ1YXJ5IDIwMTUKCgogICAgIHJl
cG9ydCBhbnkgc3RhdHVzIGNvZGUgb3IgbWVzc2FnZSBmcm9tIHRoZSBzdGF0dXMgY29kZSBv
cHRpb24gaW4KICAgICB0aGUgUmVwbHkgbWVzc2FnZS4KCiAgICAgSWYgdGhlIGNsaWVudCBy
ZWNlaXZlcyBhIFJlcGx5IG1lc3NhZ2Ugd2l0aCBhIFN0YXR1cyBDb2RlCiAgICAgY29udGFp
bmluZyBVbnNwZWNGYWlsLCB0aGUgc2VydmVyIGlzIGluZGljYXRpbmcgdGhhdCBpdCB3YXMg
dW5hYmxlCiAgICAgdG8gcHJvY2VzcyB0aGUgbWVzc2FnZSBkdWUgdG8gYW4gdW5zcGVjaWZp
ZWQgZmFpbHVyZSBjb25kaXRpb24uICBJZgogICAgIHRoZSBjbGllbnQgcmV0cmFuc21pdHMg
dGhlIG9yaWdpbmFsIG1lc3NhZ2UgdG8gdGhlIHNhbWUgc2VydmVyIHRvCiAgICAgcmV0cnkg
dGhlIGRlc2lyZWQgb3BlcmF0aW9uLCB0aGUgY2xpZW50IE1VU1QgbGltaXQgdGhlIHJhdGUg
YXQKICAgICB3aGljaCBpdCByZXRyYW5zbWl0cyB0aGUgbWVzc2FnZSBhbmQgbGltaXQgdGhl
IGR1cmF0aW9uIG9mIHRoZSB0aW1lCiAgICAgZHVyaW5nIHdoaWNoIGl0IHJldHJhbnNtaXRz
IHRoZSBtZXNzYWdlLgoKICAgICBXaGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYSBSZXBseSBt
ZXNzYWdlIHdpdGggYSBTdGF0dXMgQ29kZSBvcHRpb24KICAgICB3aXRoIHRoZSB2YWx1ZSBV
c2VNdWx0aWNhc3QsIHRoZSBjbGllbnQgcmVjb3JkcyB0aGUgcmVjZWlwdCBvZiB0aGUKICAg
ICBtZXNzYWdlIGFuZCBzZW5kcyBzdWJzZXF1ZW50IG1lc3NhZ2VzIHRvIHRoZSBzZXJ2ZXIg
dGhyb3VnaCB0aGUKICAgICBpbnRlcmZhY2Ugb24gd2hpY2ggdGhlIG1lc3NhZ2Ugd2FzIHJl
Y2VpdmVkIHVzaW5nIG11bHRpY2FzdC4gIFRoZQogICAgIGNsaWVudCByZXNlbmRzIHRoZSBv
cmlnaW5hbCBtZXNzYWdlIHVzaW5nIG11bHRpY2FzdC4KCiAgICAgV2hlbiB0aGUgY2xpZW50
IHJlY2VpdmVzIGEgTm90T25MaW5rIHN0YXR1cyBmcm9tIHRoZSBzZXJ2ZXIgaW4KICAgICBy
ZXNwb25zZSB0byBhIENvbmZpcm0gbWVzc2FnZSwgdGhlIGNsaWVudCBwZXJmb3JtcyBESENQ
IHNlcnZlcgogICAgIHNvbGljaXRhdGlvbiwgYXMgZGVzY3JpYmVkIGluIHNlY3Rpb24gMTcs
IGFuZCBjbGllbnQtaW5pdGlhdGVkCiAgICAgY29uZmlndXJhdGlvbiBhcyBkZXNjcmliZWQg
aW4gc2VjdGlvbiAxOC4gIElmIHRoZSBjbGllbnQgcmVjZWl2ZXMKICAgICBhbnkgUmVwbHkg
bWVzc2FnZXMgdGhhdCBkbyBub3QgaW5kaWNhdGUgYSBOb3RPbkxpbmsgc3RhdHVzLCB0aGUK
ICAgICBjbGllbnQgY2FuIHVzZSB0aGUgYWRkcmVzc2VzIGluIHRoZSBJQSBhbmQgaWdub3Jl
IGFueSBtZXNzYWdlcyB0aGF0CiAgICAgaW5kaWNhdGUgYSBOb3RPbkxpbmsgc3RhdHVzLgoK
ICAgICBXaGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYSBOb3RPbkxpbmsgc3RhdHVzIGZyb20g
dGhlIHNlcnZlciBpbgogICAgIHJlc3BvbnNlIHRvIGEgUmVxdWVzdCwgdGhlIGNsaWVudCBj
YW4gZWl0aGVyIHJlLWlzc3VlIHRoZSBSZXF1ZXN0CiAgICAgd2l0aG91dCBzcGVjaWZ5aW5n
IGFueSBhZGRyZXNzZXMgb3IgcmVzdGFydCB0aGUgREhDUCBzZXJ2ZXIKICAgICBkaXNjb3Zl
cnkgcHJvY2VzcyAoc2VlIHNlY3Rpb24gMTcpLgoKICAgICBUaGUgY2xpZW50IFNIT1VMRCBw
ZXJmb3JtIGR1cGxpY2F0ZSBhZGRyZXNzIGRldGVjdGlvbiBbMTddIG9uIGVhY2gKICAgICBv
ZiB0aGUgcmVjZWl2ZWQgYWRkcmVzc2VzIGluIGFueSBJQXMsIG9uIHdoaWNoIGl0IGhhcyBu
b3QgcGVyZm9ybWVkCiAgICAgZHVwbGljYXRlIGFkZHJlc3MgZGV0ZWN0aW9uIGR1cmluZyBw
cm9jZXNzaW5nIG9mIGFueSBvZiB0aGUKICAgICBwcmV2aW91cyBSZXBseSBtZXNzYWdlcyBm
cm9tIHRoZSBzZXJ2ZXIuICBUaGUgY2xpZW50IHBlcmZvcm1zIHRoZQogICAgIGR1cGxpY2F0
ZSBhZGRyZXNzIGRldGVjdGlvbiBiZWZvcmUgdXNpbmcgdGhlIHJlY2VpdmVkIGFkZHJlc3Nl
cyBmb3IKICAgICB0aGUgdHJhZmZpYy4gIElmIGFueSBvZiB0aGUgYWRkcmVzc2VzIGFyZSBm
b3VuZCB0byBiZSBpbiB1c2Ugb24gdGhlCiAgICAgbGluaywgdGhlIGNsaWVudCBzZW5kcyBh
IERlY2xpbmUgbWVzc2FnZSB0byB0aGUgc2VydmVyIGZvciB0aG9zZQogICAgIGFkZHJlc3Nl
cyBhcyBkZXNjcmliZWQgaW4gc2VjdGlvbiAxOC4xLjcuCgogICAgIElmIHRoZSBSZXBseSB3
YXMgcmVjZWl2ZWQgaW4gcmVzcG9uc2UgdG8gYSBTb2xpY2l0ICh3aXRoIGEgUmFwaWQKICAg
ICBDb21taXQgb3B0aW9uKSwgUmVxdWVzdCwgUmVuZXcgb3IgUmViaW5kIG1lc3NhZ2UsIHRo
ZSBjbGllbnQKICAgICB1cGRhdGVzIHRoZSBpbmZvcm1hdGlvbiBpdCBoYXMgcmVjb3JkZWQg
YWJvdXQgSUFzIGZyb20gdGhlIElBCiAgICAgb3B0aW9ucyBjb250YWluZWQgaW4gdGhlIFJl
cGx5IG1lc3NhZ2U6CgogICAgIC0gIFJlY29yZCBUMSBhbmQgVDIgdGltZXMuCgogICAgIC0g
IEFkZCBhbnkgbmV3IGFkZHJlc3NlcyBpbiB0aGUgSUEgb3B0aW9uIHRvIHRoZSBJQSBhcyBy
ZWNvcmRlZCBieQogICAgICAgIHRoZSBjbGllbnQuCgoKClRyb2FuLCBldCBhbC4gICAgICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCAxNiwgMjAxNSAgICAgICAgICAgICAgIFtQYWdlIDEzXQoM
CkludGVybmV0LURyYWZ0ICAgICAgICAgIE11bHRpcGxlIFN0YXRlZnVsIE9wdGlvbnMgICAg
ICAgICAgRmVicnVhcnkgMjAxNQoKCiAgICAgLSAgVXBkYXRlIGxpZmV0aW1lcyBmb3IgYW55
IGFkZHJlc3NlcyBpbiB0aGUgSUEgb3B0aW9uIHRoYXQgdGhlCiAgICAgICAgY2xpZW50IGFs
cmVhZHkgaGFzIHJlY29yZGVkIGluIHRoZSBJQS4KCiAgICAgLSAgRGlzY2FyZCBhbnkgYWRk
cmVzc2VzIGZyb20gdGhlIElBLCBhcyByZWNvcmRlZCBieSB0aGUgY2xpZW50LAogICAgICAg
IHRoYXQgaGF2ZSBhIHZhbGlkIGxpZmV0aW1lIG9mIDAgaW4gdGhlIElBIEFkZHJlc3Mgb3B0
aW9uLgoKICAgICAtICBMZWF2ZSB1bmNoYW5nZWQgYW55IGluZm9ybWF0aW9uIGFib3V0IGFk
ZHJlc3NlcyB0aGUgY2xpZW50IGhhcwogICAgICAgIHJlY29yZGVkIGluIHRoZSBJQSBidXQg
dGhhdCB3ZXJlIG5vdCBpbmNsdWRlZCBpbiB0aGUgSUEgZnJvbSB0aGUKICAgICAgICBzZXJ2
ZXIuCgogICAgIE1hbmFnZW1lbnQgb2YgdGhlIHNwZWNpZmljIGNvbmZpZ3VyYXRpb24gaW5m
b3JtYXRpb24gaXMgZGV0YWlsZWQgaW4KICAgICB0aGUgZGVmaW5pdGlvbiBvZiBlYWNoIG9w
dGlvbiBpbiBzZWN0aW9uIDIyLgoKICAgICBUaGUgY2xpZW50IGV4YW1pbmVzIHRoZSBzdGF0
dXMgY29kZSBpbiBlYWNoIElBIGluZGl2aWR1YWxseS4gIElmCiAgICAgdGhlIGNsaWVudCBy
ZWNlaXZlcyBhIE5vQWRkcnNBdmFpbCBzdGF0dXMgY29kZSwgdGhlIGNsaWVudCBoYXMKICAg
ICByZWNlaXZlZCBubyB1c2FibGUgYWRkcmVzc2VzIGluIHRoZSBJQS4KCiAgICAgSWYgdGhl
IGNsaWVudCBjYW4gb3BlcmF0ZSB3aXRoIHRoZSBhZGRyZXNzZXMgb2J0YWluZWQgZnJvbSB0
aGUKICAgICBzZXJ2ZXIgdGhlIGNsaWVudCB1c2VzIGFkZHJlc3NlcyBhbmQgb3RoZXIgaW5m
b3JtYXRpb24gZnJvbSBhbnkgSUFzCiAgICAgdGhhdCBkbyBub3QgY29udGFpbiBhIFN0YXR1
cyBDb2RlIG9wdGlvbiB3aXRoIHRoZSBOb0FkZHJzQXZhaWwKICAgICBzdGF0dXMgY29kZS4g
IFRoZSBjbGllbnQgTUFZIGluY2x1ZGUgdGhlIElBcyBmb3Igd2hpY2ggaXQgcmVjZWl2ZWQK
ICAgICB0aGUgTm9BZGRyc0F2YWlsIHN0YXR1cyBjb2RlLCB3aXRoIG5vIGFkZHJlc3Nlcywg
aW4gc3Vic2VxdWVudAogICAgIFJlbmV3IGFuZCBSZWJpbmQgbWVzc2FnZXMgc2VudCB0byB0
aGUgc2VydmVyLCB0byByZXRyeSBvYnRhaW5pbmcKICAgICB0aGUgYWRkcmVzc2VzIGZvciB0
aGVzZSBJQXMuCgogICAgIElmIHRoZSBjbGllbnQgY2Fubm90IG9wZXJhdGUgd2l0aG91dCB0
aGUgYWRkcmVzc2VzIGZvciB0aGUgSUFzIGZvcgogICAgIHdoaWNoIGl0IHJlY2VpdmVkIHRo
ZSBOb0FkZHJzQXZhaWwgc3RhdHVzIGNvZGUsIHRoZSBjbGllbnQgbWF5IHRyeQogICAgIGFu
b3RoZXIgc2VydmVyIChwZXJoYXBzIGJ5IHJlc3RhcnRpbmcgdGhlIERIQ1Agc2VydmVyIGRp
c2NvdmVyeQogICAgIHByb2Nlc3MpLgoKICAgICBJZiB0aGUgY2xpZW50IGZpbmRzIG5vIHVz
YWJsZSBhZGRyZXNzZXMgaW4gYW55IG9mIHRoZSBJQXMsIGl0IG1heQogICAgIGVpdGhlciB0
cnkgYW5vdGhlciBzZXJ2ZXIgKHBlcmhhcHMgcmVzdGFydGluZyB0aGUgREhDUCBzZXJ2ZXIK
ICAgICBkaXNjb3ZlcnkgcHJvY2Vzcykgb3IgdXNlIHRoZSBJbmZvcm1hdGlvbi1yZXF1ZXN0
IG1lc3NhZ2UgdG8gb2J0YWluCiAgICAgb3RoZXIgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlv
biBvbmx5LgoKICAgICBXaGVuIHRoZSBjbGllbnQgcmVjZWl2ZXMgYSBSZXBseSBtZXNzYWdl
IGluIHJlc3BvbnNlIHRvIGEgUmVuZXcgb3IKICAgICBSZWJpbmQgbWVzc2FnZSwgdGhlIGNs
aWVudDoKCiAgICAgLSAgc2VuZHMgYSBSZXF1ZXN0IG1lc3NhZ2UgaWYgYW55IG9mIHRoZSBJ
QXMgaW4gdGhlIFJlcGx5IG1lc3NhZ2UKICAgICAgICBjb250YWlucyB0aGUgTm9CaW5kaW5n
IHN0YXR1cyBjb2RlLiAgVGhlIGNsaWVudCBwbGFjZXMgSUEKICAgICAgICBvcHRpb25zIGlu
IHRoaXMgbWVzc2FnZSBmb3Igb25seSB0aG9zZSBJQXMgZm9yIHdoaWNoIHRoZSBzZXJ2ZXIK
ICAgICAgICByZXR1cm5lZCB0aGUgTm9CaW5kaW5nIHN0YXR1cyBjb2RlIGluIHRoZSBSZXBs
eSBtZXNzYWdlLiAgVGhlCiAgICAgICAgY2xpZW50IGNvbnRpbnVlcyB0byB1c2Ugb3RoZXIg
YmluZGluZ3MgZm9yIHdoaWNoIHRoZSBzZXJ2ZXIgZGlkCiAgICAgICAgbm90IHJldHVybiBh
biBlcnJvcgoKICAgICAtICBzZW5kcyBhIFJlbmV3L1JlYmluZCBpZiBhbnkgb2YgdGhlIElB
cyBpcyBub3QgaW4gdGhlIFJlcGx5CiAgICAgICAgbWVzc2FnZSwgYnV0IGluIHRoaXMgY2Fz
ZSB0aGUgY2xpZW50IE1VU1QgbGltaXQgdGhlIHJhdGUgYXQKICAgICAgICB3aGljaCBpdCBz
ZW5kcyB0aGVzZSBtZXNzYWdlcywgdG8gYXZvaWQgdGhlIFJlbmV3L1JlYmluZCBzdG9ybQoK
CgpUcm9hbiwgZXQgYWwuICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUgICAg
ICAgICAgICAgICBbUGFnZSAxNF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0aXBs
ZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAgICAgIEZlYnJ1YXJ5IDIwMTUKCgogICAgIC0gIG90
aGVyd2lzZSBhY2NlcHRzIHRoZSBpbmZvcm1hdGlvbiBpbiB0aGUgSUEuCgogICAgIFdoZW4g
dGhlIGNsaWVudCByZWNlaXZlcyBhIHZhbGlkIFJlcGx5IG1lc3NhZ2UgaW4gcmVzcG9uc2Ug
dG8gYQogICAgIFJlbGVhc2UgbWVzc2FnZSwgdGhlIGNsaWVudCBjb25zaWRlcnMgdGhlIFJl
bGVhc2UgZXZlbnQgY29tcGxldGVkLAogICAgIHJlZ2FyZGxlc3Mgb2YgdGhlIFN0YXR1cyBD
b2RlIG9wdGlvbihzKSByZXR1cm5lZCBieSB0aGUgc2VydmVyLgoKICAgICBXaGVuIHRoZSBj
bGllbnQgcmVjZWl2ZXMgYSB2YWxpZCBSZXBseSBtZXNzYWdlIGluIHJlc3BvbnNlIHRvIGEK
ICAgICBEZWNsaW5lIG1lc3NhZ2UsIHRoZSBjbGllbnQgY29uc2lkZXJzIHRoZSBEZWNsaW5l
IGV2ZW50IGNvbXBsZXRlZCwKICAgICByZWdhcmRsZXNzIG9mIHRoZSBTdGF0dXMgQ29kZSBv
cHRpb24ocykgcmV0dXJuZWQgYnkgdGhlIHNlcnZlci4KCjQuNC42LiAgVXBkYXRlcyB0byBT
ZWN0aW9uIDE4LjIuMyBvZiBSRkMgMzMxNQoKICAgUmVwbGFjZSBTZWN0aW9uIDE4LjIuMyBv
ZiBSRkMgMzMxNSB3aXRoIHRoZSBmb2xsb3dpbmcgdGV4dDoKCiAgICAgV2hlbiB0aGUgc2Vy
dmVyIHJlY2VpdmVzIGEgUmVuZXcgbWVzc2FnZSB2aWEgdW5pY2FzdCBmcm9tIGEgY2xpZW50
CiAgICAgdG8gd2hpY2ggdGhlIHNlcnZlciBoYXMgbm90IHNlbnQgYSB1bmljYXN0IG9wdGlv
biwgdGhlIHNlcnZlcgogICAgIGRpc2NhcmRzIHRoZSBSZW5ldyBtZXNzYWdlIGFuZCByZXNw
b25kcyB3aXRoIGEgUmVwbHkgbWVzc2FnZQogICAgIGNvbnRhaW5pbmcgYSBTdGF0dXMgQ29k
ZSBvcHRpb24gd2l0aCB0aGUgdmFsdWUgVXNlTXVsdGljYXN0LCBhCiAgICAgU2VydmVyIElk
ZW50aWZpZXIgb3B0aW9uIGNvbnRhaW5pbmcgdGhlIHNlcnZlcidzIERVSUQsIHRoZSBDbGll
bnQKICAgICBJZGVudGlmaWVyIG9wdGlvbiBmcm9tIHRoZSBjbGllbnQgbWVzc2FnZSwgYW5k
IG5vIG90aGVyIG9wdGlvbnMuCgogICAgIEZvciBlYWNoIElBIGluIHRoZSBSZW5ldyBtZXNz
YWdlIGZyb20gYSBjbGllbnQsIHRoZSBzZXJ2ZXIgbG9jYXRlcwogICAgIHRoZSBjbGllbnQn
cyBiaW5kaW5nIGFuZCB2ZXJpZmllcyB0aGF0IHRoZSBpbmZvcm1hdGlvbiBpbiB0aGUgSUEK
ICAgICBmcm9tIHRoZSBjbGllbnQgbWF0Y2hlcyB0aGUgaW5mb3JtYXRpb24gc3RvcmVkIGZv
ciB0aGF0IGNsaWVudC4KCiAgICAgSWYgdGhlIHNlcnZlciBmaW5kcyB0aGUgY2xpZW50IGVu
dHJ5IGZvciB0aGUgSUEgdGhlIHNlcnZlciBzZW5kcwogICAgIGJhY2sgdGhlIElBIHRvIHRo
ZSBjbGllbnQgd2l0aCBuZXcgbGlmZXRpbWVzIGFuZCwgaWYgYXBwbGljYWJsZSwKICAgICBU
MS9UMiB0aW1lcy4gIElmIHRoZSBzZXJ2ZXIgaXMgdW5hYmxlIHRvIGV4dGVuZCB0aGUgbGlm
ZXRpbWVzIG9mIGFuCiAgICAgYWRkcmVzcyBpbiB0aGUgSUEsIHRoZSBzZXJ2ZXIgTUFZIGNo
b29zZSBub3QgdG8gaW5jbHVkZSB0aGUgSUEKICAgICBBZGRyZXNzIG9wdGlvbiBmb3IgdGhp
cyBhZGRyZXNzLgoKICAgICBUaGUgc2VydmVyIG1heSBjaG9vc2UgdG8gY2hhbmdlIHRoZSBs
aXN0IG9mIGFkZHJlc3NlcyBhbmQgdGhlCiAgICAgbGlmZXRpbWVzIG9mIGFkZHJlc3NlcyBp
biBJQXMgdGhhdCBhcmUgcmV0dXJuZWQgdG8gdGhlIGNsaWVudC4KCiAgICAgSWYgdGhlIHNl
cnZlciBmaW5kcyB0aGF0IGFueSBvZiB0aGUgYWRkcmVzc2VzIGluIHRoZSBJQSBhcmUgbm90
CiAgICAgYXBwcm9wcmlhdGUgZm9yIHRoZSBsaW5rIHRvIHdoaWNoIHRoZSBjbGllbnQgaXMg
YXR0YWNoZWQsIHRoZQogICAgIHNlcnZlciByZXR1cm5zIHRoZSBhZGRyZXNzIHRvIHRoZSBj
bGllbnQgd2l0aCBsaWZldGltZXMgb2YgMC4KCiAgICAgRm9yIGVhY2ggSUEgZm9yIHdoaWNo
IHRoZSBzZXJ2ZXIgY2Fubm90IGZpbmQgYSBjbGllbnQgZW50cnksIHRoZQogICAgIHNlcnZl
ciBoYXMgdGhlIGZvbGxvd2luZyBjaG9pY2VzIGRlcGVuZGluZyBvbiB0aGUgc2VydmVyJ3Mg
cG9saWN5CiAgICAgYW5kIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb246CgogICAgIC0gIElm
IHRoZSBzZXJ2ZXIgaXMgY29uZmlndXJlZCB0byBjcmVhdGUgbmV3IGJpbmRpbmdzIGFzIGEg
cmVzdWx0CiAgICAgICAgb2YgcHJvY2Vzc2luZyBSZW5ldyBtZXNzYWdlcywgdGhlIHNlcnZl
ciBTSE9VTEQgY3JlYXRlIGEgYmluZGluZwogICAgICAgIGFuZCByZXR1cm4gdGhlIElBIHdp
dGggYWxsb2NhdGVkIGFkZHJlc3NlcyB3aXRoIGxpZmV0aW1lcyBhbmQsCiAgICAgICAgaWYg
YXBwbGljYWJsZSwgVDEvVDIgdGltZXMgYW5kIG90aGVyIGluZm9ybWF0aW9uIHJlcXVlc3Rl
ZCBieQogICAgICAgIHRoZSBjbGllbnQuICBUaGUgc2VydmVyIE1BWSB1c2UgdmFsdWVzIGlu
IHRoZSBJQSBBZGRyZXNzIG9wdGlvbgogICAgICAgIChpZiBpbmNsdWRlZCkgYXMgYSBoaW50
LgoKCgpUcm9hbiwgZXQgYWwuICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUg
ICAgICAgICAgICAgICBbUGFnZSAxNV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0
aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAgICAgIEZlYnJ1YXJ5IDIwMTUKCgogICAgIC0g
IElmIHRoZSBzZXJ2ZXIgaXMgY29uZmlndXJlZCB0byBjcmVhdGUgbmV3IGJpbmRpbmdzIGFz
IGEgcmVzdWx0CiAgICAgICAgb2YgcHJvY2Vzc2luZyBSZW5ldyBtZXNzYWdlcywgYnV0IHRo
ZSBzZXJ2ZXIgd2lsbCBub3QgYXNzaWduIGFueQogICAgICAgIGFkZHJlc3NlcyB0byBhbiBJ
QSwgdGhlIHNlcnZlciByZXR1cm5zIHRoZSBJQSBvcHRpb24gY29udGFpbmluZwogICAgICAg
IGEgU3RhdHVzIENvZGUgb3B0aW9uIHdpdGggdGhlIE5vQWRkcnNBdmFpbCBzdGF0dXMgY29k
ZSBhbmQgYQogICAgICAgIHN0YXR1cyBtZXNzYWdlIGZvciBhIHVzZXIuCgogICAgIC0gIElm
IHRoZSBzZXJ2ZXIgZG9lcyBub3Qgc3VwcG9ydCBjcmVhdGlvbiBvZiBuZXcgYmluZGluZ3Mg
Zm9yIHRoZQogICAgICAgIGNsaWVudCBzZW5kaW5nIGEgUmVuZXcgbWVzc2FnZSwgb3IgaWYg
dGhpcyBiZWhhdmlvciBpcyBkaXNhYmxlZAogICAgICAgIGFjY29yZGluZyB0byB0aGUgc2Vy
dmVyJ3MgcG9saWN5IG9yIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb24sCiAgICAgICAgdGhl
IHNlcnZlciByZXR1cm5zIHRoZSBJQSBvcHRpb24gY29udGFpbmluZyBhIFN0YXR1cyBjb2Rl
IG9wdGlvbgogICAgICAgIHdpdGggdGhlIE5vQmluZGluZyBzdGF0dXMgY29kZSBhbmQgYSBz
dGF0dXMgbWVzc2FnZSBmb3IgYSB1c2VyLgoKICAgICBUaGUgc2VydmVyIGNvbnN0cnVjdHMg
YSBSZXBseSBtZXNzYWdlIGJ5IHNldHRpbmcgdGhlICJtc2ctdHlwZSIKICAgICBmaWVsZCB0
byBSRVBMWSwgYW5kIGNvcHlpbmcgdGhlIHRyYW5zYWN0aW9uIElEIGZyb20gdGhlIFJlbmV3
CiAgICAgbWVzc2FnZSBpbnRvIHRoZSB0cmFuc2FjdGlvbi1pZCBmaWVsZC4KCiAgICAgVGhl
IHNlcnZlciBNVVNUIGluY2x1ZGUgYSBTZXJ2ZXIgSWRlbnRpZmllciBvcHRpb24gY29udGFp
bmluZyB0aGUKICAgICBzZXJ2ZXIncyBEVUlEIGFuZCB0aGUgQ2xpZW50IElkZW50aWZpZXIg
b3B0aW9uIGZyb20gdGhlIFJlbmV3CiAgICAgbWVzc2FnZSBpbiB0aGUgUmVwbHkgbWVzc2Fn
ZS4KCiAgICAgVGhlIHNlcnZlciBpbmNsdWRlcyBvdGhlciBvcHRpb25zIGNvbnRhaW5pbmcg
Y29uZmlndXJhdGlvbgogICAgIGluZm9ybWF0aW9uIHRvIGJlIHJldHVybmVkIHRvIHRoZSBj
bGllbnQgYXMgZGVzY3JpYmVkIGluIHNlY3Rpb24KICAgICAxOC4yLgoKICAgICBUaGUgVDEv
VDIgdGltZXMgc2V0IGluIGVhY2ggYXBwbGljYWJsZSBJQSBvcHRpb24gZm9yIGEgUmVwbHkg
TVVTVAogICAgIGJlIHRoZSBzYW1lIHZhbHVlcyBhY3Jvc3MgYWxsIElBcy4gIFRoZSBzZXJ2
ZXIgTVVTVCBkZXRlcm1pbmUgdGhlCiAgICAgVDEvVDIgdGltZXMgYWNyb3NzIGFsbCBvZiB0
aGUgYXBwbGljYWJsZSBjbGllbnQncyBiaW5kaW5ncyBpbiB0aGUKICAgICBSZXBseS4gIFRo
aXMgZmFjaWxpdGF0ZXMgdGhlIGNsaWVudCBiZWluZyBhYmxlIHRvIHJlbmV3IGFsbCBvZiB0
aGUKICAgICBiaW5kaW5ncyBhdCB0aGUgc2FtZSB0aW1lLgoKNC40LjcuICBVcGRhdGVzIHRv
IFNlY3Rpb24gMTguMi40IG9mIFJGQyAzMzE1CgogICBSZXBsYWNlIFNlY3Rpb24gMTguMi40
IG9mIFJGQyAzMzE1IHdpdGggdGhlIGZvbGxvd2luZyB0ZXh0OgoKICAgICAgV2hlbiB0aGUg
c2VydmVyIHJlY2VpdmVzIGEgUmViaW5kIG1lc3NhZ2UgdGhhdCBjb250YWlucyBhbiBJQQog
ICAgICBvcHRpb24gZnJvbSBhIGNsaWVudCwgaXQgbG9jYXRlcyB0aGUgY2xpZW50J3MgYmlu
ZGluZyBhbmQgdmVyaWZpZXMKICAgICAgdGhhdCB0aGUgaW5mb3JtYXRpb24gaW4gdGhlIElB
IGZyb20gdGhlIGNsaWVudCBtYXRjaGVzIHRoZQogICAgICBpbmZvcm1hdGlvbiBzdG9yZWQg
Zm9yIHRoYXQgY2xpZW50LgoKICAgICAgSWYgdGhlIHNlcnZlciBmaW5kcyB0aGUgY2xpZW50
IGVudHJ5IGZvciB0aGUgSUEgYW5kIHRoZSBzZXJ2ZXIKICAgICAgZGV0ZXJtaW5lcyB0aGF0
IHRoZSBhZGRyZXNzZXMgaW4gdGhlIElBIGFyZSBhcHByb3ByaWF0ZSBmb3IgdGhlCiAgICAg
IGxpbmsgdG8gd2hpY2ggdGhlIGNsaWVudCdzIGludGVyZmFjZSBpcyBhdHRhY2hlZCBhY2Nv
cmRpbmcgdG8gdGhlCiAgICAgIHNlcnZlcidzIGV4cGxpY2l0IGNvbmZpZ3VyYXRpb24gaW5m
b3JtYXRpb24sIHRoZSBzZXJ2ZXIgU0hPVUxECiAgICAgIHNlbmQgYmFjayB0aGUgSUEgdG8g
dGhlIGNsaWVudCB3aXRoIG5ldyBsaWZldGltZXMgYW5kLCBpZgogICAgICBhcHBsaWNhYmxl
LCBUMS9UMiB0aW1lcy4gIElmIHRoZSBzZXJ2ZXIgaXMgdW5hYmxlIHRvIGV4dGVuZCB0aGUK
ICAgICAgbGlmZXRpbWVzIG9mIGFuIGFkZHJlc3MgaW4gdGhlIElBLCB0aGUgc2VydmVyIE1B
WSBjaG9vc2Ugbm90IHRvCiAgICAgIGluY2x1ZGUgdGhlIElBIEFkZHJlc3Mgb3B0aW9uIGZv
ciB0aGlzIGFkZHJlc3MuCgoKCgpUcm9hbiwgZXQgYWwuICAgICAgICAgICAgRXhwaXJlcyBB
dWd1c3QgMTYsIDIwMTUgICAgICAgICAgICAgICBbUGFnZSAxNl0KDApJbnRlcm5ldC1EcmFm
dCAgICAgICAgICBNdWx0aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAgICAgICAgIEZlYnJ1YXJ5
IDIwMTUKCgogICAgICBJZiB0aGUgc2VydmVyIGZpbmRzIHRoZSBjbGllbnQgZW50cnkgZm9y
IHRoZSBJQSBhbmQgYW55IG9mIHRoZQogICAgICBhZGRyZXNzZXMgYXJlIG5vIGxvbmdlciBh
cHByb3ByaWF0ZSBmb3IgdGhlIGxpbmsgdG8gd2hpY2ggdGhlCiAgICAgIGNsaWVudCdzIGlu
dGVyZmFjZSBpcyBhdHRhY2hlZCBhY2NvcmRpbmcgdG8gdGhlIHNlcnZlcidzIGV4cGxpY2l0
CiAgICAgIGNvbmZpZ3VyYXRpb24gaW5mb3JtYXRpb24sIHRoZSBzZXJ2ZXIgcmV0dXJucyB0
aGUgYWRkcmVzcyB0byB0aGUKICAgICAgY2xpZW50IHdpdGggbGlmZXRpbWVzIG9mIDAuCgog
ICAgICBJZiB0aGUgc2VydmVyIGNhbm5vdCBmaW5kIGEgY2xpZW50IGVudHJ5IGZvciB0aGUg
SUEsIHRoZSBJQQogICAgICBjb250YWlucyBhZGRyZXNzZXMgYW5kIHRoZSBzZXJ2ZXIgZGV0
ZXJtaW5lcyB0aGF0IHRoZSBhZGRyZXNzZXMgaW4KICAgICAgdGhlIElBIGFyZSBub3QgYXBw
cm9wcmlhdGUgZm9yIHRoZSBsaW5rIHRvIHdoaWNoIHRoZSBjbGllbnQncwogICAgICBpbnRl
cmZhY2UgaXMgYXR0YWNoZWQgYWNjb3JkaW5nIHRvIHRoZSBzZXJ2ZXIncyBleHBsaWNpdAog
ICAgICBjb25maWd1cmF0aW9uIGluZm9ybWF0aW9uLCB0aGUgc2VydmVyIE1BWSBzZW5kIGEg
UmVwbHkgbWVzc2FnZSB0bwogICAgICB0aGUgY2xpZW50IGNvbnRhaW5pbmcgdGhlIGNsaWVu
dCdzIElBLCB3aXRoIHRoZSBsaWZldGltZXMgZm9yIHRoZQogICAgICBhZGRyZXNzZXMgaW4g
dGhlIElBIHNldCB0byAwLiAgVGhpcyBSZXBseSBjb25zdGl0dXRlcyBhbiBleHBsaWNpdAog
ICAgICBub3RpZmljYXRpb24gdG8gdGhlIGNsaWVudCB0aGF0IHRoZSBhZGRyZXNzZXMgaW4g
dGhlIElBIGFyZSBubwogICAgICBsb25nZXIgdmFsaWQuICBJbiB0aGlzIHNpdHVhdGlvbiwg
aWYgdGhlIHNlcnZlciBkb2VzIG5vdCBzZW5kIGEKICAgICAgUmVwbHkgbWVzc2FnZSBpdCBz
aWxlbnRseSBkaXNjYXJkcyB0aGUgUmViaW5kIG1lc3NhZ2UuCgogICAgICBPdGhlcndpc2Us
IGZvciBlYWNoIElBIGZvciB3aGljaCB0aGUgc2VydmVyIGNhbm5vdCBmaW5kIGEgY2xpZW50
CiAgICAgIGVudHJ5LCB0aGUgc2VydmVyIGhhcyB0aGUgZm9sbG93aW5nIGNob2ljZXMgZGVw
ZW5kaW5nIG9uIHRoZQogICAgICBzZXJ2ZXIncyBwb2xpY3kgYW5kIGNvbmZpZ3VyYXRpb24g
aW5mb3JtYXRpb246CgogICAgICAtICBJZiB0aGUgc2VydmVyIGlzIGNvbmZpZ3VyZWQgdG8g
Y3JlYXRlIG5ldyBiaW5kaW5ncyBhcyBhIHJlc3VsdAogICAgICAgICBvZiBwcm9jZXNzaW5n
IFJlYmluZCBtZXNzYWdlcyAoYWxzbyBzZWUgdGhlIG5vdGUgYWJvdXQgdGhlCiAgICAgICAg
IFJhcGlkIENvbW1pdCBvcHRpb24gYmVsb3cpLCB0aGUgc2VydmVyIFNIT1VMRCBjcmVhdGUg
YSBiaW5kaW5nCiAgICAgICAgIGFuZCByZXR1cm4gdGhlIElBIHdpdGggYWxsb2NhdGVkIGFk
ZHJlc3NlcyB3aXRoIGxpZmV0aW1lcyBhbmQsCiAgICAgICAgIGlmIGFwcGxpY2FibGUsIFQx
L1QyIHRpbWVzIGFuZCBvdGhlciBpbmZvcm1hdGlvbiByZXF1ZXN0ZWQgYnkKICAgICAgICAg
dGhlIGNsaWVudC4gIFRoZSBzZXJ2ZXIgTUFZIHVzZSB2YWx1ZXMgaW4gdGhlIElBIEFkZHJl
c3Mgb3B0aW9uCiAgICAgICAgIChpZiBpbmNsdWRlZCkgYXMgYSBoaW50LgoKICAgICAgLSAg
SWYgdGhlIHNlcnZlciBpcyBjb25maWd1cmVkIHRvIGNyZWF0ZSBuZXcgYmluZGluZ3MgYXMg
YSByZXN1bHQKICAgICAgICAgb2YgcHJvY2Vzc2luZyBSZWJpbmQgbWVzc2FnZXMsIGJ1dCB0
aGUgc2VydmVyIHdpbGwgbm90IGFzc2lnbgogICAgICAgICBhbnkgYWRkcmVzc2VzIHRvIGFu
IElBLCB0aGUgc2VydmVyIHJldHVybnMgdGhlIElBIG9wdGlvbgogICAgICAgICBjb250YWlu
aW5nIGEgU3RhdHVzIENvZGUgb3B0aW9uIHdpdGggdGhlIE5vQWRkcnNBdmFpbCBzdGF0dXMK
ICAgICAgICAgY29kZSBhbmQgYSBzdGF0dXMgbWVzc2FnZSBmb3IgYSB1c2VyLgoKICAgICAg
LSAgSWYgdGhlIHNlcnZlciBkb2VzIG5vdCBzdXBwb3J0IGNyZWF0aW9uIG9mIG5ldyBiaW5k
aW5ncyBmb3IgdGhlCiAgICAgICAgIGNsaWVudCBzZW5kaW5nIGEgUmViaW5kIG1lc3NhZ2Us
IG9yIGlmIHRoaXMgYmVoYXZpb3IgaXMKICAgICAgICAgZGlzYWJsZWQgYWNjb3JkaW5nIHRv
IHRoZSBzZXJ2ZXIncyBwb2xpY3kgb3IgY29uZmlndXJhdGlvbgogICAgICAgICBpbmZvcm1h
dGlvbiwgdGhlIHNlcnZlciByZXR1cm5zIHRoZSBJQSBvcHRpb24gY29udGFpbmluZyBhCiAg
ICAgICAgIFN0YXR1cyBDb2RlIG9wdGlvbiB3aXRoIHRoZSBOb0JpbmRpbmcgc3RhdHVzIGNv
ZGUgYW5kIGEgc3RhdHVzCiAgICAgICAgIG1lc3NhZ2UgZm9yIGEgdXNlci4KCiAgICAgIFdo
ZW4gdGhlIHNlcnZlciBjcmVhdGVzIG5ldyBiaW5kaW5ncyBmb3IgdGhlIElBIGl0IGlzIHBv
c3NpYmxlCiAgICAgIHRoYXQgb3RoZXIgc2VydmVycyBhbHNvIGNyZWF0ZSBiaW5kaW5ncyBh
cyBhIHJlc3VsdCBvZiByZWNlaXZpbmcKICAgICAgdGhlIHNhbWUgUmViaW5kIG1lc3NhZ2Uu
ICBUaGlzIGlzIHRoZSBzYW1lIGlzc3VlIGFzIGluIHRoZQogICAgICBEaXNjdXNzaW9uIHVu
ZGVyIHRoZSBSYXBpZCBDb21taXQgb3B0aW9uLCBzZWUgc2VjdGlvbiAyMi4xNC4KICAgICAg
VGhlcmVmb3JlLCB0aGUgc2VydmVyIFNIT1VMRCBvbmx5IGNyZWF0ZSBuZXcgYmluZGluZ3Mg
ZHVyaW5nCiAgICAgIHByb2Nlc3Npbmcgb2YgYSBSZWJpbmQgbWVzc2FnZSBpZiB0aGUgc2Vy
dmVyIGlzIGNvbmZpZ3VyZWQgdG8KCgoKVHJvYW4sIGV0IGFsLiAgICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAgICAgW1BhZ2UgMTddCgwKSW50ZXJuZXQt
RHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVmdWwgT3B0aW9ucyAgICAgICAgICBGZWJy
dWFyeSAyMDE1CgoKICAgICAgcmVzcG9uZCB3aXRoIGEgUmVwbHkgbWVzc2FnZSB0byBhIFNv
bGljaXQgbWVzc2FnZSBjb250YWluaW5nIHRoZQogICAgICBSYXBpZCBDb21taXQgb3B0aW9u
LgoKICAgICAgVGhlIHNlcnZlciBjb25zdHJ1Y3RzIGEgUmVwbHkgbWVzc2FnZSBieSBzZXR0
aW5nIHRoZSAibXNnLXR5cGUiCiAgICAgIGZpZWxkIHRvIFJFUExZLCBhbmQgY29weWluZyB0
aGUgdHJhbnNhY3Rpb24gSUQgZnJvbSB0aGUgUmViaW5kCiAgICAgIG1lc3NhZ2UgaW50byB0
aGUgdHJhbnNhY3Rpb24taWQgZmllbGQuCgogICAgICBUaGUgc2VydmVyIE1VU1QgaW5jbHVk
ZSBhIFNlcnZlciBJZGVudGlmaWVyIG9wdGlvbiBjb250YWluaW5nIHRoZQogICAgICBzZXJ2
ZXIncyBEVUlEIGFuZCB0aGUgQ2xpZW50IElkZW50aWZpZXIgb3B0aW9uIGZyb20gdGhlIFJl
YmluZAogICAgICBtZXNzYWdlIGluIHRoZSBSZXBseSBtZXNzYWdlLgoKICAgICAgVGhlIHNl
cnZlciBpbmNsdWRlcyBvdGhlciBvcHRpb25zIGNvbnRhaW5pbmcgY29uZmlndXJhdGlvbgog
ICAgICBpbmZvcm1hdGlvbiB0byBiZSByZXR1cm5lZCB0byB0aGUgY2xpZW50IGFzIGRlc2Ny
aWJlZCBpbiBzZWN0aW9uCiAgICAgIDE4LjIuCgogICAgICBUaGUgVDEvVDIgdGltZXMgc2V0
IGluIGVhY2ggYXBwbGljYWJsZSBJQSBvcHRpb24gZm9yIGEgUmVwbHkgTVVTVAogICAgICBi
ZSB0aGUgc2FtZSB2YWx1ZXMgYWNyb3NzIGFsbCBJQXMuICBUaGUgc2VydmVyIE1VU1QgZGV0
ZXJtaW5lIHRoZQogICAgICBUMS9UMiB0aW1lcyBhY3Jvc3MgYWxsIG9mIHRoZSBhcHBsaWNh
YmxlIGNsaWVudCdzIGJpbmRpbmdzIGluIHRoZQogICAgICBSZXBseS4gIFRoaXMgZmFjaWxp
dGF0ZXMgdGhlIGNsaWVudCBiZWluZyBhYmxlIHRvIHJlbmV3IGFsbCBvZiB0aGUKICAgICAg
YmluZGluZ3MgYXQgdGhlIHNhbWUgdGltZS4KCjQuNC44LiAgVXBkYXRlcyB0byBSRkMgMzYz
MwoKICAgUmVwbGFjZSB0aGUgZm9sbG93aW5nIHRleHQgaW4gU2VjdGlvbiAxMi4xIG9mIFJG
QyAzNjMzOgoKICAgICAgRWFjaCBwcmVmaXggaGFzIHZhbGlkIGFuZCBwcmVmZXJyZWQgbGlm
ZXRpbWVzIHdob3NlIGR1cmF0aW9ucyBhcmUKICAgICAgc3BlY2lmaWVkIGluIHRoZSBJQV9Q
RCBQcmVmaXggb3B0aW9uIGZvciB0aGF0IHByZWZpeC4gIFRoZQogICAgICByZXF1ZXN0aW5n
IHJvdXRlciB1c2VzIFJlbmV3IGFuZCBSZWJpbmQgbWVzc2FnZXMgdG8gcmVxdWVzdCB0aGUK
ICAgICAgZXh0ZW5zaW9uIG9mIHRoZSBsaWZldGltZXMgb2YgYSBkZWxlZ2F0ZWQgcHJlZml4
LgoKICAgV2l0aDoKCiAgICAgIEVhY2ggcHJlZml4IGhhcyB2YWxpZCBhbmQgcHJlZmVycmVk
IGxpZmV0aW1lcyB3aG9zZSBkdXJhdGlvbnMgYXJlCiAgICAgIHNwZWNpZmllZCBpbiB0aGUg
SUFfUEQgUHJlZml4IG9wdGlvbiBmb3IgdGhhdCBwcmVmaXguICBUaGUKICAgICAgcmVxdWVz
dGluZyByb3V0ZXIgdXNlcyBSZW5ldyBhbmQgUmViaW5kIG1lc3NhZ2VzIHRvIHJlcXVlc3Qg
dGhlCiAgICAgIGV4dGVuc2lvbiBvZiB0aGUgbGlmZXRpbWVzIG9mIGEgZGVsZWdhdGVkIHBy
ZWZpeC4KCiAgICAgIFRoZSByZXF1ZXN0aW5nIHJvdXRlciBNQVkgaW5jbHVkZSBJQV9QRCBv
cHRpb25zIHdpdGhvdXQgYW55CiAgICAgIHByZWZpeGVzLCBpLmUuIHdpdGhvdXQgSUEgUHJl
Zml4IG9wdGlvbiBvciB3aXRoIElQdjYgcHJlZml4IGZpZWxkCiAgICAgIG9mIElBIFByZWZp
eCBvcHRpb24gc2V0IHRvIDAsIGluIGEgUmVuZXcgb3IgUmViaW5kIG1lc3NhZ2UgdG8KICAg
ICAgb2J0YWluIGJpbmRpbmdzIGl0IGRlc2lyZXMgYnV0IGhhcyBiZWVuIHVuYWJsZSB0byBv
YnRhaW4uICBUaGUKICAgICAgcmVxdWVzdGluZyByb3V0ZXIgTUFZIHNldCB0aGUgcHJlZml4
LWxlbmd0aCBmaWVsZCBvZiB0aGUgSUEgUHJlZml4CiAgICAgIG9wdGlvbiBhcyBhIGhpbnQg
dG8gdGhlIHNlcnZlci4gIEFzIGluIFtSRkMzMzE1XSwgdGhlIHJlcXVlc3RpbmcKICAgICAg
cm91dGVyIE1BWSBhbHNvIHByb3ZpZGUgbGlmZXRpbWUgaGludHMgaW4gdGhlIElBIFByZWZp
eCBvcHRpb24uCgogICBSZXBsYWNlIHRoZSBmb2xsb3dpbmcgdGV4dCBpbiBTZWN0aW9uIDEy
LjIgb2YgUkZDIDM2MzM6CgoKCgoKVHJvYW4sIGV0IGFsLiAgICAgICAgICAgIEV4cGlyZXMg
QXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAgICAgW1BhZ2UgMThdCgwKSW50ZXJuZXQtRHJh
ZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVmdWwgT3B0aW9ucyAgICAgICAgICBGZWJydWFy
eSAyMDE1CgoKICAgICAgVGhlIGRlbGVnYXRpbmcgcm91dGVyIGJlaGF2ZXMgYXMgZm9sbG93
cyB3aGVuIGl0IGNhbm5vdCBmaW5kIGEKICAgICAgYmluZGluZyBmb3IgdGhlIHJlcXVlc3Rp
bmcgcm91dGVyJ3MgSUFfUEQ6CgogICBXaXRoOgoKICAgICAgRm9yIHRoZSBSZW5ldyBvciBS
ZWJpbmQsIGlmIHRoZSBJQV9QRCBjb250YWlucyBubyBJQSBQcmVmaXggb3B0aW9uCiAgICAg
IG9yIGl0IGNvbnRhaW5zIGFuIElBIFByZWZpeCBvcHRpb24gd2l0aCB0aGUgSVB2NiBwcmVm
aXggZmllbGQgc2V0CiAgICAgIHRvIDAsIHRoZSBkZWxlZ2F0aW5nIHJvdXRlciBTSE9VTEQg
YXNzaWduIHByZWZpeGVzIHRvIHRoZSBJQV9QRAogICAgICBhY2NvcmRpbmcgdG8gdGhlIGRl
bGVnYXRpbmcgcm91dGVyJ3MgZXhwbGljaXQgY29uZmlndXJhdGlvbgogICAgICBpbmZvcm1h
dGlvbi4gIEluIHRoaXMgY2FzZSwgaWYgdGhlIElBX1BEIGNvbnRhaW5zIGFuIElBIFByZWZp
eAogICAgICBvcHRpb24gd2l0aCB0aGUgSVB2NiBwcmVmaXggZmllbGQgc2V0IHRvIDAsIHRo
ZSBkZWxlZ2F0aW5nIHJvdXRlcgogICAgICBNQVkgdXNlIHRoZSB2YWx1ZSBpbiB0aGUgcHJl
Zml4LWxlbmd0aCBmaWVsZCBvZiB0aGUgSUEgUHJlZml4CiAgICAgIG9wdGlvbiBhcyBhIGhp
bnQgZm9yIHRoZSBsZW5ndGggb2YgdGhlIHByZWZpeGVzIHRvIGJlIGFzc2lnbmVkLgogICAg
ICBUaGUgZGVsZWdhdGluZyByb3V0ZXIgTUFZIGFsc28gcmVzcGVjdCBsaWZldGltZSBoaW50
cyBwcm92aWRlZCBieQogICAgICB0aGUgcmVxdWVzdGluZyByb3V0ZXIgaW4gdGhlIElBIFBy
ZWZpeCBvcHRpb24uCgogICAgICBUaGUgZGVsZWdhdGluZyByb3V0ZXIgYmVoYXZlcyBhcyBm
b2xsb3dzIHdoZW4gaXQgY2Fubm90IGZpbmQgYQogICAgICBiaW5kaW5nIGZvciB0aGUgcmVx
dWVzdGluZyByb3V0ZXIncyBJQV9QRCBjb250YWluaW5nIHByZWZpeGVzOgoKNC41LiAgQ29u
ZmlybSBNZXNzYWdlCgogICBUaGUgQ29uZmlybSBtZXNzYWdlLCBhcyBkZXNjcmliZWQgaW4g
W1JGQzMzMTVdLCBpcyBzcGVjaWZpYyB0bwogICBhZGRyZXNzIGFzc2lnbm1lbnQuICBJdCBh
bGxvd3MgYSBzZXJ2ZXIgd2l0aG91dCBhIGJpbmRpbmcgdG8gcmVwbHkgdG8KICAgdGhlIG1l
c3NhZ2UsIHVuZGVyIHRoZSBhc3N1bXB0aW9uIHRoYXQgdGhlIHNlcnZlciBvbmx5IG5lZWRz
CiAgIGtub3dsZWRnZSBhYm91dCB0aGUgcHJlZml4KGVzKSBvbiB0aGUgbGluaywgdG8gaW5m
b3JtIHRoZSBjbGllbnQgdGhhdAogICB0aGUgYWRkcmVzcyBpcyBsaWtlbHkgdmFsaWQgb3Ig
bm90LiAgVGhpcyBtZXNzYWdlIGlzIHNlbnQgd2hlbiBlLmcuCiAgIHRoZSBjbGllbnQgaGFz
IG1vdmVkIGFuZCBuZWVkcyB0byB2YWxpZGF0ZSBpdHMgYWRkcmVzc2VzLiAgTm90IGFsbAog
ICBiaW5kaW5ncyBjYW4gYmUgdmFsaWRhdGVkIGJ5IHNlcnZlcnMgYW5kIHRoZSBDb25maXJt
IG1lc3NhZ2UgcHJvdmlkZXMKICAgZm9yIHRoaXMgYnkgc3BlY2lmeWluZyB0aGF0IGEgc2Vy
dmVyIHRoYXQgaXMgdW5hYmxlIHRvIGRldGVybWluZSB0aGUKICAgb24tbGluayBzdGF0dXMg
TVVTVCBOT1Qgc2VuZCBhIFJlcGx5LgoKICAgTm90ZTogQ29uZmlybSBoYXMgYSBzcGVjaWZp
YyBtZWFuaW5nIGFuZCBkb2VzIG5vdCBvdmVybG9hZCBSZW5ldy8KICAgUmViaW5kLiAgSXQg
YWxzbyBpcyBsb3dlciBwcm9jZXNzaW5nIGNvc3QgYXMgdGhlIHNlcnZlciBkb2VzIE5PVCBu
ZWVkCiAgIHRvIGV4dGVuZCBsZWFzZSB0aW1lcyBvciBvdGhlcndpc2Ugc2VuZCBiYWNrIG90
aGVyIGNvbmZpZ3VyYXRpb24KICAgb3B0aW9ucy4KCiAgIFRoZSBDb25maXJtIG1lc3NhZ2Ug
aXMgdXNlZCBieSB0aGUgY2xpZW50IHRvIHZlcmlmeSB0aGF0IGl0IGhhcyBub3QKICAgbW92
ZWQgdG8gYSBkaWZmZXJlbnQgbGluay4gIEZvciBJQXMgd2l0aCBhZGRyZXNzZXMsIHRoZSBt
ZWNoYW5pc20KICAgdXNlZCB0byB2ZXJpZnkgaWYgYSBjbGllbnQgaGFzIG1vdmVkIG9yIG5v
dCwgaXMgYnkgbWF0Y2hpbmcgdGhlCiAgIGxpbmsncyBvbi1saW5rIHByZWZpeChlcykgKHR5
cGljYWxseSBhIC82NCkgYWdhaW5zdCB0aGUgcHJlZml4LWxlbmd0aAogICBmaXJzdCBiaXRz
IG9mIHRoZSBhZGRyZXNzZXMgcHJvdmlkZWQgYnkgdGhlIGNsaWVudCBpbiB0aGUgSUFfTkEg
b3IKICAgSUFfVEEgSUEtdHlwZXMuICBBcyBhIGNvbnNlcXVlbmNlIENvbmZpcm0gY2FuIG9u
bHkgYmUgdXNlZCB3aGVuIHRoZQogICBjbGllbnQgaGFzIGFuIElBIHdpdGggYWRkcmVzcyhl
cykgKElBX05BIG9yIElBX1RBKS4KCiAgIEEgY2xpZW50IE1VU1QgaGF2ZSBhIGJpbmRpbmcg
aW5jbHVkaW5nIGFuIElBIHdpdGggYWRkcmVzc2VzIHRvIHVzZQogICB0aGUgQ29uZmlybSBt
ZXNzYWdlLiAgQSBjbGllbnQgd2l0aCBJQXMgd2l0aCBhZGRyZXNzZXMgYXMgd2VsbCBhcwog
ICBvdGhlciBJQS10eXBlcyBNQVksIGRlcGVuZGluZyBvbiB0aGUgSUEtdHlwZSwgdXNlIHRo
ZSBDb25maXJtIG1lc3NhZ2UKICAgdG8gZGV0ZWN0IGlmIHRoZSBjbGllbnQgaGFzIG1vdmVk
IHRvIGEgZGlmZmVyZW50IGxpbmsuICBBIGNsaWVudCB0aGF0CgoKClRyb2FuLCBldCBhbC4g
ICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCAxNiwgMjAxNSAgICAgICAgICAgICAgIFtQYWdl
IDE5XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgIE11bHRpcGxlIFN0YXRlZnVsIE9wdGlv
bnMgICAgICAgICAgRmVicnVhcnkgMjAxNQoKCiAgIGRvZXMgbm90IGhhdmUgYSBiaW5kaW5n
IHdpdGggYW4gSUEgd2l0aCBhZGRyZXNzZXMgTVVTVCB1c2UgdGhlIFJlYmluZAogICBtZXNz
YWdlIGluc3RlYWQuCgogICBJQV9QRCByZXF1aXJlcyB2ZXJpZmljYXRpb24gdGhhdCB0aGUg
ZGVsZWdhdGluZyByb3V0ZXIgKHNlcnZlcikgaGFzCiAgIHRoZSBiaW5kaW5nIGZvciB0aGUg
SUFzLiAgSW4gdGhhdCBjYXNlIGEgcmVxdWVzdGluZyByb3V0ZXIgKGNsaWVudCkKICAgTVVT
VCB1c2UgdGhlIFJlYmluZCBtZXNzYWdlIGluIHBsYWNlIG9mIHRoZSBDb25maXJtIG1lc3Nh
Z2UgYW5kIGl0CiAgIE1VU1QgaW5jbHVkZSBhbGwgb2YgaXRzIGJpbmRpbmdzLCBldmVuIGFk
ZHJlc3MgSUFzLgoKICAgTm90ZSB0aGF0IFNlY3Rpb24gMTguMS4yIG9mIFJGQyAzMzE1IHN0
YXRlcyB0aGF0IGEgY2xpZW50IE1VU1QKICAgaW5pdGlhdGUgYSBDb25maXJtIHdoZW4gaXQg
bWF5IGhhdmUgbW92ZWQgdG8gYSBuZXcgbGluay4gIFRoaXMgaXMKICAgcmVsYXhlZCB0byBh
IFNIT1VMRCBhcyBhIGNsaWVudCBtYXkgaGF2ZSBkZXRlcm1pbmVkIHdoZXRoZXIgaXQgaGFz
IG9yCiAgIGhhcyBub3QgbW92ZWQgdXNpbmcgb3RoZXIgdGVjaG5pcXVlcywgc3VjaCBhcyBk
ZXNjcmliZWQgaW4gW1JGQzYwNTldLgogICBBbmQsIGFzIHN0YXRlZCBhYm92ZSwgYSBjbGll
bnQgd2l0aCBkZWxlZ2F0ZWQgcHJlZml4ZXMsIE1VU1Qgc2VuZCBhCiAgIFJlYmluZCBpbnN0
ZWFkIG9mIGEgQ29uZmlybS4KCjQuNi4gIERlY2xpbmUgU2hvdWxkIE5vdCBOZWNlc3Nhcmls
eSBUcmlnZ2VyIGEgUmVsZWFzZQoKICAgU29tZSBjbGllbnQgaW1wbGVtZW50YXRpb25zIGhh
dmUgYmVlbiBmb3VuZCB0byBzZW5kIGEgUmVsZWFzZSBtZXNzYWdlCiAgIGZvciBvdGhlciBi
aW5kaW5ncyB0aGV5IG1heSBoYXZlIHJlY2VpdmVkIGFmdGVyIHRoZXkgZGV0ZXJtaW5lIGEK
ICAgY29uZmxpY3QgYW5kIGhhdmUgY29ycmVjdGx5IHNlbnQgYSBEZWNsaW5lIG1lc3NhZ2Ug
Zm9yIHRoZQogICBjb25mbGljdGluZyBhZGRyZXNzKGVzKS4KCiAgIEl0IGlzIHJlY29tbWVu
ZGVkIHRoYXQgYSBjbGllbnQgU0hPVUxEIE5PVCBzZW5kIGEgUmVsZWFzZSBtZXNzYWdlIGZv
cgogICBvdGhlciBiaW5kaW5ncyBpdCBtYXkgaGF2ZSByZWNlaXZlZCBqdXN0IGJlY2F1c2Ug
aXQgc2VudCBhIERlY2xpbmUKICAgbWVzc2FnZS4gIFRoZSBjbGllbnQgU0hPVUxEIHJldGFp
biB0aGUgbm9uLWNvbmZsaWN0aW5nIGJpbmRpbmdzLiAgVGhlCiAgIGNsaWVudCBTSE9VTEQg
dHJlYXQgdGhlIGZhaWx1cmUgdG8gYWNxdWlyZSBhIGJpbmRpbmcgYXMgYSByZXN1bHQgb2YK
ICAgdGhlIGNvbmZsaWN0LCB0byBiZSBlcXVpdmFsZW50IHRvIG5vdCBoYXZpbmcgcmVjZWl2
ZWQgdGhlIGJpbmRpbmcsCiAgIGluc29mYXIgYXMgaXQgYmVoYXZlcyB3aGVuIHNlbmRpbmcg
UmVuZXcgYW5kIFJlYmluZCBtZXNzYWdlcy4KCjQuNy4gIE11bHRpcGxlIFByb3Zpc2lvbmlu
ZyBEb21haW5zCgogICBUaGlzIGRvY3VtZW50IGhhcyBhc3N1bWVkIHRoYXQgYWxsIERIQ1Ag
c2VydmVycyBvbiBhIG5ldHdvcmsgYXJlIGluIGEKICAgc2luZ2xlIHByb3Zpc2lvbmluZyBk
b21haW4gYW5kIHRodXMgc2hvdWxkIGJlICJlcXVhbCIgaW4gdGhlIHNlcnZpY2UKICAgdGhh
dCB0aGV5IG9mZmVyLiAgVGhpcyB3YXMgYWxzbyBhc3N1bWVkIGJ5IFtSRkMzMzE1XSBhbmQg
W1JGQzM2MzNdLgoKICAgT25lIGNvdWxkIGVudmlzaW9uIGEgbmV0d29yayB3aGVyZSB0aGUg
REhDUCBzZXJ2ZXJzIGFyZSBpbiBtdWx0aXBsZQogICBwcm92aXNpb25pbmcgZG9tYWlucywg
YW5kIGl0IG1heSBiZSBkZXNpcmFibGUgdG8gaGF2ZSB0aGUgREhDUCBjbGllbnQKICAgb2J0
YWluIGRpZmZlcmVudCBJQSB0eXBlcyBmcm9tIGRpZmZlcmVudCBwcm92aXNpb25pbmcgZG9t
YWlucy4gIEhvdyBhCiAgIGNsaWVudCBkZXRlY3RzIHRoZSBtdWx0aXBsZSBwcm92aXNpb25p
bmcgZG9tYWlucyBhbmQgaG93IGl0IHdvdWxkCiAgIGludGVyYWN0IHdpdGggdGhlIG11bHRp
cGxlIHNlcnZlcnMgaW4gdGhlc2UgZGlmZmVyZW50IGRvbWFpbnMgaXMKICAgb3V0c2lkZSB0
aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudCAoc2VlIFtJLUQuaWV0Zi1taWYtbXB2ZC1hcmNo
XSBhbmQKICAgW0ktRC5pZXRmLW1pZi1tcHZkLWRoY3Atc3VwcG9ydF0pLgoKNS4gIElBTkEg
Q29uc2lkZXJhdGlvbnMKCiAgIFRoaXMgc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCByZXF1aXJl
IGFueSBJQU5BIGFjdGlvbnMuCgoKCgoKVHJvYW4sIGV0IGFsLiAgICAgICAgICAgIEV4cGly
ZXMgQXVndXN0IDE2LCAyMDE1ICAgICAgICAgICAgICAgW1BhZ2UgMjBdCgwKSW50ZXJuZXQt
RHJhZnQgICAgICAgICAgTXVsdGlwbGUgU3RhdGVmdWwgT3B0aW9ucyAgICAgICAgICBGZWJy
dWFyeSAyMDE1CgoKNi4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zCgogICBUaGVyZSBhcmUg
bm8gbmV3IHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIHBlcnRhaW5pbmcgdG8gdGhpcyBkb2N1
bWVudC4KCjcuICBBY2tub3dsZWRnZW1lbnRzCgogICBUaGFua3MgdG8gbWFueSBwZW9wbGUg
dGhhdCBjb250cmlidXRlZCB0byBpZGVudGlmeSB0aGUgc3RhdGVmdWwKICAgaXNzdWVzIGFk
ZHJlc3NlZCBieSB0aGlzIGRvY3VtZW50IGFuZCBmb3IgcmV2aWV3aW5nIGRyYWZ0cyBvZiB0
aGUKICAgZG9jdW1lbnQsIGluY2x1ZGluZyBSYWxwaCBEcm9tcywgSm9obiBCcnpvem93c2tp
LCBUZWQgTGVtb24sIEhlbWFudAogICBTaW5naCwgV2VzIEJlZWJlZSwgR2F1cmF1IEhhbHdh
c2lhLCBCdWQgTWlsbHdvcmQsIFRpbSBXaW50ZXJzLCBSb2IKICAgU2hha2lyLCBKaW5tZWkg
VGF0dXlhLCBBbmRyZXcgWW91cnRjaGVua28sIEZyZWQgVGVtcGxpbiwgVG9tZWsKICAgTXJ1
Z2Fsc2tpLCBTdXJlc2ggS3Jpc2huYW4sIGFuZCBJYW4gRmFycmVyLgoKOC4gIFJlZmVyZW5j
ZXMKCjguMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzCgogICBbUkZDMjExOV0gIEJyYWRuZXIs
IFMuLCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZQogICAgICAgICAg
ICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksIE1hcmNoIDE5OTcu
CgogICBbUkZDMzMxNV0gIERyb21zLCBSLiwgQm91bmQsIEouLCBWb2x6LCBCLiwgTGVtb24s
IFQuLCBQZXJraW5zLCBDLiwKICAgICAgICAgICAgICBhbmQgTS4gQ2FybmV5LCAiRHluYW1p
YyBIb3N0IENvbmZpZ3VyYXRpb24gUHJvdG9jb2wgZm9yCiAgICAgICAgICAgICAgSVB2NiAo
REhDUHY2KSIsIFJGQyAzMzE1LCBKdWx5IDIwMDMuCgogICBbUkZDMzYzM10gIFRyb2FuLCBP
LiBhbmQgUi4gRHJvbXMsICJJUHY2IFByZWZpeCBPcHRpb25zIGZvciBEeW5hbWljCiAgICAg
ICAgICAgICAgSG9zdCBDb25maWd1cmF0aW9uIFByb3RvY29sIChESENQKSB2ZXJzaW9uIDYi
LCBSRkMgMzYzMywKICAgICAgICAgICAgICBEZWNlbWJlciAyMDAzLgoKICAgW1JGQzcwODNd
ICBEcm9tcywgUi4sICJNb2RpZmljYXRpb24gdG8gRGVmYXVsdCBWYWx1ZXMgb2YgU09MX01B
WF9SVAogICAgICAgICAgICAgIGFuZCBJTkZfTUFYX1JUIiwgUkZDIDcwODMsIE5vdmVtYmVy
IDIwMTMuCgo4LjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzCgogICBbSS1ELmRoY3dnLWRo
Yy1yZmMzMzE1YmlzXQogICAgICAgICAgICAgIE1ydWdhbHNraSwgVC4sIFNpb2RlbHNraSwg
TS4sIFZvbHosIEIuLCBZb3VydGNoZW5rbywgQS4sCiAgICAgICAgICAgICAgUmljaGFyZHNv
biwgTS4sIEppYW5nLCBTLiwgYW5kIFQuIExlbW9uLCAiRHluYW1pYyBIb3N0CiAgICAgICAg
ICAgICAgQ29uZmlndXJhdGlvbiBQcm90b2NvbCBmb3IgSVB2NiAoREhDUHY2KSBiaXMiLCBk
cmFmdC0KICAgICAgICAgICAgICBkaGN3Zy1kaGMtcmZjMzMxNWJpcy0wMyAod29yayBpbiBw
cm9ncmVzcyksIE9jdG9iZXIgMjAxNC4KCiAgIFtJLUQuaWV0Zi1taWYtbXB2ZC1hcmNoXQog
ICAgICAgICAgICAgIEFuaXBrbywgRC4sICJNdWx0aXBsZSBQcm92aXNpb25pbmcgRG9tYWlu
IEFyY2hpdGVjdHVyZSIsCiAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1taWYtbXB2ZC1hcmNo
LTEwICh3b3JrIGluIHByb2dyZXNzKSwgRmVicnVhcnkKICAgICAgICAgICAgICAyMDE1LgoK
ICAgW0ktRC5pZXRmLW1pZi1tcHZkLWRoY3Atc3VwcG9ydF0KICAgICAgICAgICAgICBLcmlz
aG5hbiwgUy4sIEtvcmhvbmVuLCBKLiwgYW5kIFMuIEJoYW5kYXJpLCAiU3VwcG9ydCBmb3IK
ICAgICAgICAgICAgICBtdWx0aXBsZSBwcm92aXNpb25pbmcgZG9tYWlucyBpbiBESENQdjYi
LCBkcmFmdC1pZXRmLW1pZi0KICAgICAgICAgICAgICBtcHZkLWRoY3Atc3VwcG9ydC0wMCAo
d29yayBpbiBwcm9ncmVzcyksIEF1Z3VzdCAyMDE0LgoKCgpUcm9hbiwgZXQgYWwuICAgICAg
ICAgICAgRXhwaXJlcyBBdWd1c3QgMTYsIDIwMTUgICAgICAgICAgICAgICBbUGFnZSAyMV0K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgICBNdWx0aXBsZSBTdGF0ZWZ1bCBPcHRpb25zICAg
ICAgICAgIEZlYnJ1YXJ5IDIwMTUKCgogICBbUkZDNjA1OV0gIEtyaXNobmFuLCBTLiBhbmQg
Ry4gRGFsZXksICJTaW1wbGUgUHJvY2VkdXJlcyBmb3IKICAgICAgICAgICAgICBEZXRlY3Rp
bmcgTmV0d29yayBBdHRhY2htZW50IGluIElQdjYiLCBSRkMgNjA1OSwgTm92ZW1iZXIKICAg
ICAgICAgICAgICAyMDEwLgoKICAgW1JGQzcwODRdICBTaW5naCwgSC4sIEJlZWJlZSwgVy4s
IERvbmxleSwgQy4sIGFuZCBCLiBTdGFyaywgIkJhc2ljCiAgICAgICAgICAgICAgUmVxdWly
ZW1lbnRzIGZvciBJUHY2IEN1c3RvbWVyIEVkZ2UgUm91dGVycyIsIFJGQyA3MDg0LAogICAg
ICAgICAgICAgIE5vdmVtYmVyIDIwMTMuCgogICBbUkZDNzIyN10gIEhhbmtpbnMsIEQuLCBN
cnVnYWxza2ksIFQuLCBTaW9kZWxza2ksIE0uLCBKaWFuZywgUy4sIGFuZAogICAgICAgICAg
ICAgIFMuIEtyaXNobmFuLCAiR3VpZGVsaW5lcyBmb3IgQ3JlYXRpbmcgTmV3IERIQ1B2NiBP
cHRpb25zIiwKICAgICAgICAgICAgICBCQ1AgMTg3LCBSRkMgNzIyNywgTWF5IDIwMTQuCgpB
dXRob3JzJyBBZGRyZXNzZXMKCiAgIE9sZSBUcm9hbgogICBDaXNjbyBTeXN0ZW1zLCBJbmMu
CiAgIFBoaWxpcCBQZWRlcnNlbnMgdmVpIDIwCiAgIE4tMTMyNCBMeXNha2VyCiAgIE5vcndh
eQoKICAgRW1haWw6IG90QGNpc2NvLmNvbQoKCiAgIEJlcm5pZSBWb2x6CiAgIENpc2NvIFN5
c3RlbXMsIEluYy4KICAgMTQxNCBNYXNzYWNodXNldHRzIEF2ZQogICBCb3hib3JvdWdoLCBN
QSAgMDE3MTkKICAgVVNBCgogICBFbWFpbDogdm9sekBjaXNjby5jb20KCgogICBNYXJjaW4g
U2lvZGVsc2tpCiAgIElTQwogICA5NTAgQ2hhcnRlciBTdHJlZXQKICAgUmVkd29vZCBDaXR5
LCBDQSAgOTQwNjMKICAgVVNBCgogICBFbWFpbDogbXNpb2RlbHNraUBnbWFpbC5jb20KCgoK
CgoKCgoKCgoKVHJvYW4sIGV0IGFsLiAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDE2LCAy
MDE1ICAgICAgICAgICAgICAgW1BhZ2UgMjJdCg==
--------------080604030805010102060505--


From nobody Thu Feb 12 14:15:09 2015
Return-Path: <mellon@fugue.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 D04451A0377 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 14:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 Wxh84rLXAgv3 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 14:14:57 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 601D51A0371 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 14:14:57 -0800 (PST)
Received: from [192.168.1.102] (rich-dsl1-136.greenmountainaccess.net [65.19.75.136]) by toccata.fugue.com (Postfix) with ESMTPSA id 11F9723805DB; Thu, 12 Feb 2015 17:14:54 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com>
Date: Thu, 12 Feb 2015 17:14:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com> <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/TiF7AtLvJ6-BcsjrVSKMDwzoqTY>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Thu, 12 Feb 2015 22:15:00 -0000

On Feb 12, 2015, at 12:57 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> To be clear: my current position is still against this option.  I'm
> always in the camp of "problem first, then solution".  And that's
> also the case of this document since around May 2014:
> http://www.ietf.org/mail-archive/web/dhcwg/current/msg15520.html

This is a fine idea in theory.   However, section 7 does not represent a =
valid problem statement.

> But at least around last May our consensus
> should have been against that approach, hence the current organization
> of the draft.  Just because it triggers a hot discussion doesn't
> automatically dismiss the original concern and justify ignoring it.

It wasn't clear to me that there was a consensus to add the speculative =
use cases to the document, but I will leave that to the chairs to =
decide.

> Unless and until we see a clear wg consensus that we now allow it to
> ship even if no one can explain what kind of problem it will solve, I
> object to moving forward with just removing this section.  And, IMO,
> this consensus change will require another round of WGLC.

That's a reasonable request.

But that said, let's be clear: we do actually have a problem.   The =
problem is that the authentication scheme described in RFC 3315 is not =
deployable, because it relies on a key distribution model that doesn't =
work with a typical DHCP deployment.   This document uses a key =
distribution model that would work better.   So this is definitely an =
improvement over RFC 3315.

It is however true that we do not know who would use this.   This =
document is very speculative.   And I can imagine other ways to solve =
this problem--for example, doing a shared secret exchange using public =
keys.   But these are problems that the working group has been aware of =
for over a decade, and we've made no forward progress.

The reason I support issuing this document as an RFC is that I think it =
would work, and would work better than what we have now, and I'd like to =
see if anybody will implement it.   Until there is a document to =
implement, clearly nobody is going to implement anything.

So that's why despite the lack of a use case document or a list of known =
use cases other than section 7, I think we should publish the document.


From nobody Thu Feb 12 15:13:43 2015
Return-Path: <internet-drafts@ietf.org>
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 DB5811A0368; Thu, 12 Feb 2015 15:13:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 YPBduGNh--2b; Thu, 12 Feb 2015 15:13:38 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF3C1A1ADA; Thu, 12 Feb 2015 15:13:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150212231338.32166.46250.idtracker@ietfa.amsl.com>
Date: Thu, 12 Feb 2015 15:13:38 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/-Z69Zen8ajhq5zQuGpyJCmaCBdw>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-stateful-issues-11.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 12 Feb 2015 23:13:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Issues and Recommendations with Multiple Stateful DHCPv6 Options
        Authors         : Ole Troan
                          Bernie Volz
                          Marcin Siodelski
	Filename        : draft-ietf-dhc-dhcpv6-stateful-issues-11.txt
	Pages           : 23
	Date            : 2015-02-12

Abstract:
   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
   specification defined two stateful options, IA_NA and IA_TA, but did
   not anticipate the development of additional stateful options.
   DHCPv6 Prefix Delegation added the IA_PD option, which is stateful.
   Applications that use IA_NA and IA_PD together have revealed issues
   that need to be addressed.  This document updates RFC 3315 and RFC
   3633 to address these issues.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dhcpv6-stateful-issues-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Feb 12 15:21:27 2015
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 21F0E1A02BE for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 15:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 udW759awa25M for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 15:21:10 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCEA21A1DBE for <dhcwg@ietf.org>; Thu, 12 Feb 2015 15:21:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8236; q=dns/txt; s=iport; t=1423783269; x=1424992869; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=7jM3kqL8Go4WjrMAfUFcvTvGVxfXTJ4rfcP1kTufF8s=; b=iyq2Br1UjK/wwACo4rMR7FGeRs6T5c6nHfC0gzKsS6RcSyK3DcQ071KJ hPj0fwk9H9bTxIo2Ql17DGRsCWoEbO02BWWhjIXBKaqP0vuxvTDDg/DHP NDFF7AUHXzzag5RNgtDItRXAcODnb5gm+ozm//ePY0T+AEYn6UGCjWISy U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BoBQC2NN1U/4ENJK1bgwZSWgSCfsAmhXECHIEJQwEBAQEBAXyEDAEBAQMBIxFFBQcEAgEGAg4DBAEBAQICBh0DAgICHxEUAQgIAgQBDQUIiBEDCQgNoTKcbJFRDYVVAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EhiG1+gkOBeRYQCwcGgmIugRQBBI1CgWeDVoNkM4JeECiCTohfgkWDPiKDbm+BAiQefwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,567,1418083200"; d="scan'208";a="123047550"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP; 12 Feb 2015 23:21:07 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t1CNL7hx010565 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Feb 2015 23:21:07 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0195.001; Thu, 12 Feb 2015 17:21:07 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Marcin Siodelski <msiodelski@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikAAeCiTAP//tueggAT7bQCAAbZrAIAAM6qAgAAtKHCAALEHAIAASM6AgAFnaQCAADFwAIAABusAgAALKIA=
Date: Thu, 12 Feb 2015 23:21:07 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9A09C0@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com> <54DCE942.9080605@gmail.com>
In-Reply-To: <54DCE942.9080605@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SYRfl78gRBHO1SnWgPmBMarXSG4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Thu, 12 Feb 2015 23:21:19 -0000

SSBoYXZlIHB1Ymxpc2hlZCBhIC0xMSB2ZXJzaW9uIG9mIHRoZSBkcmFmdCB0aGF0IGhvcGVmdWxs
eSBhZGRyZXNzZXMgSmlubWVpJ3MgYW5kIFRlZCdzIG1vc3QgcmVjZW50IGNvbW1lbnRzLg0KDQpU
aGUgd29yZGluZyB3YXMgdHdlYWtlZCBzbGlnaHRseSBmcm9tIHRoYXQgZGlzY3Vzc2VkLg0KDQpQ
bGVhc2Ugc2VlIHRoZSAtMTEgZHJhZnQuIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWlldGYtZGhjLWRoY3B2Ni1zdGF0ZWZ1bC1pc3N1ZXMuDQoNClRoZSBjb3B5cmlnaHQgbm90aWNl
IHdhcyBhbHNvIGFkanVzdGVkIGFzIHBvaW50ZWQgb3V0IGJ5IFRvbWVrIGFzIHdlIGFyZSByZWZl
cmVuY2luZyB0ZXh0IGZyb20gcHJlIDIwMDggUkZDcy4NCg0KICAgVGhpcyBkb2N1bWVudCBtYXkg
Y29udGFpbiBtYXRlcmlhbCBmcm9tIElFVEYgRG9jdW1lbnRzIG9yIElFVEYNCiAgIENvbnRyaWJ1
dGlvbnMgcHVibGlzaGVkIG9yIG1hZGUgcHVibGljbHkgYXZhaWxhYmxlIGJlZm9yZSBOb3ZlbWJl
cg0KICAgMTAsIDIwMDguICBUaGUgcGVyc29uKHMpIGNvbnRyb2xsaW5nIHRoZSBjb3B5cmlnaHQg
aW4gc29tZSBvZiB0aGlzDQogICBtYXRlcmlhbCBtYXkgbm90IGhhdmUgZ3JhbnRlZCB0aGUgSUVU
RiBUcnVzdCB0aGUgcmlnaHQgdG8gYWxsb3cNCiAgIG1vZGlmaWNhdGlvbnMgb2Ygc3VjaCBtYXRl
cmlhbCBvdXRzaWRlIHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLg0KICAgV2l0aG91dCBvYnRh
aW5pbmcgYW4gYWRlcXVhdGUgbGljZW5zZSBmcm9tIHRoZSBwZXJzb24ocykgY29udHJvbGxpbmcN
CiAgIHRoZSBjb3B5cmlnaHQgaW4gc3VjaCBtYXRlcmlhbHMsIHRoaXMgZG9jdW1lbnQgbWF5IG5v
dCBiZSBtb2RpZmllZA0KICAgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2VzcywgYW5k
IGRlcml2YXRpdmUgd29ya3Mgb2YgaXQgbWF5DQogICBub3QgYmUgY3JlYXRlZCBvdXRzaWRlIHRo
ZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLCBleGNlcHQgdG8gZm9ybWF0DQogICBpdCBmb3IgcHVi
bGljYXRpb24gYXMgYW4gUkZDIG9yIHRvIHRyYW5zbGF0ZSBpdCBpbnRvIGxhbmd1YWdlcyBvdGhl
cg0KICAgdGhhbiBFbmdsaXNoLg0KDQotIEJlcm5pZSAoYW5kIE1hcmNpbiBhbmQgT2xlKQ0KDQot
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWFyY2luIFNpb2RlbHNraSBbbWFpbHRv
Om1zaW9kZWxza2lAZ21haWwuY29tXSANClNlbnQ6IFRodXJzZGF5LCBGZWJydWFyeSAxMiwgMjAx
NSAxMjo1NiBQTQ0KVG86IOelnuaYjumBlOWTiQ0KQ2M6IFRlZCBMZW1vbjsgZGhjd2dAaWV0Zi5v
cmc7IEJlcm5pZSBWb2x6ICh2b2x6KQ0KU3ViamVjdDogUmU6IFtkaGN3Z10gZHJhZnQtaWV0Zi1k
aGMtZGhjcHY2LXN0YXRlZnVsLWlzc3Vlcy0xMC50eHQNCg0KDQpPbiAxMi8wMi8xNSAxODozMSwg
56We5piO6YGU5ZOJIHdyb3RlOg0KPiBBdCBUaHUsIDEyIEZlYiAyMDE1IDE1OjM0OjM2ICswMTAw
LA0KPiBNYXJjaW4gU2lvZGVsc2tpIDxtc2lvZGVsc2tpQGdtYWlsLmNvbT4gd3JvdGU6DQo+DQo+
ID4gQXMgYSByZXN1bHQgb2YgdGhpcyBkaXNjdXNzaW9uLCB3ZSBoYXZlIGNvbWUgdXAgd2l0aCB0
aGUgZm9sbG93aW5nIA0KPiA+IHRleHQgZm9yIHRoZSBzZWN0aW9uIDQuIFRoaXMgbmV3IHRleHQg
aXMgbm93IGJlaW5nIGluY2x1ZGVkIGluIHRoZSANCj4gPiB2ZXJzaW9uDQo+ID4gLTExIG9mIHRo
ZSBkcmFmdCwgYnV0IHdlJ3JlIGhvbGRpbmcgb2ZmIHRoZSBwdWJsaWNhdGlvbiB1bnRpbCB3ZSAN
Cj4gPiBoZWFyIGZyb20geW91LiBIb3dldmVyLCBpdCB3b3VsZCBiZSBncmVhdCBpZiB5b3UgY291
bGQgcmV2aWV3IGFuZCANCj4gPiByZXNwb25kIHRvZGF5LCBzbyBhcyB3ZSBjYW4gcHVibGlzaCBp
dCBhbmQgbWVldCB0aGUgZGVhZGxpbmVzIHdlIA0KPiA+IGhhdmUgc2V0DQo+IHdpdGggVGVkLg0K
Pg0KPiBUaGFua3MsIGl0IHNlZW1zIHRvIGFkZHJlc3MgbXkgY29uY2Vybi4NCj4NCg0KVGhhdCdz
IGdyZWF0IQ0KDQo+IE9uZSBlZGl0b3JpYWwgcG9pbnQ6IHRoZSBhZGRlZCBwYXJhZ3JhcGggc2Vl
bXMgdG8gYmUgbW9zdGx5IGEgdmVyYmF0aW0gDQo+IGNvcHkgb2YgbXkgc3VtbWFyeSB0ZXh0IGFu
ZCBsb29rcyBhIGJpdCBhd2t3YXJkIGlmIHBsYWNlZCBpbiB0aGUgDQo+IG1pZGRsZSBvZiB0aGUg
c2VjdGlvbi4gIEZvciBleGFtcGxlLCB0aGUgZmlyc3Qgc2VudGVuY2UgbG9va3MgDQo+IHJlZHVu
ZGFudCAodGhlIHNlY3Rpb24gYWxyZWFkeSBtZW50aW9uZWQgdGhhdCB0aGVyZSBhcmUgc2V2ZXJh
bCANCj4gY2hvaWNlcykuDQo+DQo+IEFuZCwgb25lIG1pbm9yIG5pdCAoYW4gZXJyb3IgZnJvbSBt
eSBvd24gdGV4dCk6DQo+DQo+ID4gICAgY2hvaWNlcy4gIEFsc28sIGluIHNvbWUgY29ybmVyIGNh
c2VzIGl0IG1heSBub3QgZmVhc2libGUgdG8gDQo+ID4gbWFpbnRhaW4NCj4NCj4gcy9tYXkgbm90
IGZlYXNpYmxlL21heSBub3QgYmUgZmVhc2libGUvDQo+DQo+IENvbWJpbmluZyB0aGVzZSwgSSBz
dWdnZXN0IHJldmlzaW5nIHRoZSBwYXJhZ3JhcGggYXMgZm9sbG93czoNCj4NCj4gICAgV2hpbGUg
YWxsIGNob2ljZXMgaGF2ZSB0aGVpciBvd24gcHJvcyBhbmQgY29ucywgd2UgcmVjb21tZW5kIGFu
ZA0KPiAgICBmb2N1cyBvbiBjaG9pY2UgMyBmb3IgdGhpcyBkb2N1bWVudCBiZWNhdXNlIGl0IGlz
IGRlZW1lZCB0byB3b3JrDQo+ICAgIGJlc3QgZm9yIGNvbW1vbiBjYXNlcyBvZiB0aGUgbWl4ZWQg
dXNlIG9mIElBX05BIGFuZCBJQV9QRC4gIEJ1dA0KPiAgICB0aGlzIGRvY3VtZW50IGRvZXMgbm90
IGV4Y2x1ZGUgb3RoZXIgY2hvaWNlcy4gIEFsc28sIGluIHNvbWUgY29ybmVyDQo+ICAgIGNhc2Vz
IGl0IG1heSBub3QgYmUgZmVhc2libGUgdG8gbWFpbnRhaW4gYSBzaW5nbGUgREhDUHY2IHNlc3Np
b24NCj4gICAgZm9yIGJvdGggSUFfTkEgYW5kIElBX1BELiAgVGhlc2UgY29ybmVyIGNhc2VzIGFy
ZSBiZXlvbmQgdGhlIHNjb3BlDQo+ICAgIG9mIHRoaXMgZG9jdW1lbnQgYW5kIG1heSBkZXBlbmQg
b24gdGhlIG5ldHdvcmsgaW4gd2hpY2ggdGhlIGNsaWVudA0KPiAgICAoQ0VSKSBpcyBkZXNpZ25l
ZCB0byBvcGVyYXRlIGFuZCBvbiB0aGUgZnVuY3Rpb25zIHRoZSBjbGllbnQgaXMNCj4gICAgcmVx
dWlyZWQgdG8gcGVyZm9ybS4NCj4NCg0KVGhhdCBsb29rcyBvayB0byBtZS4NCg0KPiBBbHNvLCBh
bHRob3VnaCBpdCBkb2Vzbid0IHNlZW0gdG8gYmUgY3JpdGljYWwgaW4gdGVybXMgb2YgbXkgbWFp
biANCj4gcG9pbnQgYW5kIEkgd291bGRuJ3QgY29uc2lkZXIgaXQgYSBibG9ja2luZyBpc3N1ZSwg
dGhpcyBwYXJhZ3JhcGggaXMgDQo+IG5vdCBlYXN5IHRvIHVuZGVyc3RhbmQgdG8gbWU6DQo+DQo+
ID4gICAgVGhlIHNpbmdsZSBzZXNzaW9uIGFuZCBzdGF0ZSBtYWNoaW5lIGFsbG93cyB0aGUgY2xp
ZW50IHRvIHVzZSB0aGUNCj4gPiAgICBiZXN0IGNvbmZpZ3VyYXRpb24gaXQgaXMgYWJsZSB0byBv
YnRhaW4gZnJvbSBhIHNpbmdsZSBESENQIHNlcnZlcg0KPiA+ICAgIGR1cmluZyB0aGUgY29uZmln
dXJhdGlvbiBleGNoYW5nZS4gIElmIHRoZSBzZXJ2ZXIgaXMgbm90IGNvbmZpZ3VyZWQNCj4gPiAg
ICB0byBkZWxpdmVyIHRoZSBlbnRpcmUgY29uZmlndXJhdGlvbiByZXF1ZXN0ZWQgYnkgdGhlIGNs
aWVudCwgdGhlDQo+ID4gICAgY2xpZW50IGNvdWxkIGNvbnRpbnVlIHRvIG9wZXJhdGUgdXNpbmcg
dGhlIGNvbmZpZ3VyYXRpb24gcmVjZWl2ZWQuDQo+ID4gICAgQnV0IGlkZWFsbHkgaXQgdGhlbiBj
b250aW51ZXMsIGluIGVhY2ggc3Vic2VxdWVudCBjb25maWd1cmF0aW9uDQo+ID4gICAgZXhjaGFu
Z2UsIHRvIHJlcXVlc3QgYWxsIHRoZSBjb25maWd1cmF0aW9uIGluZm9ybWF0aW9uIGl0IGlzDQo+
ID4gICAgcHJvZ3JhbW1lZCB0byB0cnkgdG8gb2J0YWluLCBpbmNsdWRpbmcgYW55IHN0YXRlZnVs
IGNvbmZpZ3VyYXRpb24NCj4gPiAgICBvcHRpb25zIGZvciB3aGljaCBubyByZXN1bHRzIHdlcmUg
cmV0dXJuZWQgaW4gcHJldmlvdXMgZXhjaGFuZ2VzLg0KPiA+ICAgIEhvd2V2ZXIsIHRoaXMgaXMg
ZGlmZmljdWx0IHdpdGggdGhlIGN1cnJlbnQgREhDUHY2IHNwZWNpZmljYXRpb25zLg0KPg0KPiBE
b2VzIGl0IHRyeSB0byBzYXkgc29tZXRoaW5nIGxpa2UgdGhpcz8NCj4NCj4gICAgIFRoZSBzaW5n
bGUgc2Vzc2lvbiBhbmQgc3RhdGUgbWFjaGluZSBhbGxvd3MgdGhlIGNsaWVudCB0byB1c2UgdGhl
DQo+ICAgICBiZXN0IGNvbmZpZ3VyYXRpb24gaXQgaXMgYWJsZSB0byBvYnRhaW4gZnJvbSBhIHNp
bmdsZSBESENQIHNlcnZlcg0KPiAgICAgZHVyaW5nIHRoZSBjb25maWd1cmF0aW9uIGV4Y2hhbmdl
LiAgTm90ZSwgaG93ZXZlciwgdGhhdCB0aGUgc2VydmVyDQo+ICAgICBtYXkgbm90IGJlIGNvbmZp
Z3VyZWQgdG8gZGVsaXZlciB0aGUgZW50aXJlIGNvbmZpZ3VyYXRpb24NCj4gICAgIHJlcXVlc3Rl
ZCBieSB0aGUgY2xpZW50LiAgSW4gdGhhdCBjYXNlIHRoZSBjbGllbnQgY291bGQgY29udGludWUN
Cj4gICAgIHRvIG9wZXJhdGUgb25seSB1c2luZyB0aGUgY29uZmlndXJhdGlvbiByZWNlaXZlZCwg
ZXZlbiBpZiBvdGhlcg0KPiAgICAgc2VydmVycyBjYW4gcHJvdmlkZSB0aGUgbWlzc2luZyBjb25m
aWd1cmF0aW9uLiAgSW4gcHJhY3RpY2UsDQo+ICAgICBlc3BlY2lhbGx5IGluIHRoZSBjYXNlIG9m
IGhhbmRsaW5nIElBX05BIGFuZCBJQV9QRCwgdGhpcyBzaXR1YXRpb24NCj4gICAgIHNob3VsZCBi
ZSByYXJlIG9yIGEgdGVtcG9yYXJ5IG9wZXJhdGlvbmFsIGVycm9yLiAgU28sIGl0IGlzIG1vcmUN
Cj4gICAgIGxpa2VseSBmb3IgdGhlIGNsaWVudCB0byBnZXQgYWxsIGNvbmZpZ3VyYXRpb24gaWYg
aXQgY29udGludWVzLCBpbg0KPiAgICAgZWFjaCBzdWJzZXF1ZW50IGNvbmZpZ3VyYXRpb24gZXhj
aGFuZ2UsIHRvIHJlcXVlc3QgYWxsIHRoZQ0KPiAgICAgY29uZmlndXJhdGlvbiBpbmZvcm1hdGlv
biBpdCBpcyBwcm9ncmFtbWVkIHRvIHRyeSB0byBvYnRhaW4sDQo+ICAgICBpbmNsdWRpbmcgYW55
IHN0YXRlZnVsIGNvbmZpZ3VyYXRpb24gb3B0aW9ucyBmb3Igd2hpY2ggbm8gcmVzdWx0cw0KPiAg
ICAgd2VyZSByZXR1cm5lZCBpbiBwcmV2aW91cyBleGNoYW5nZXMuDQo+DQo+ICAgICBPbmUgbWFq
b3IgaXNzdWUgb2YgdGhpcyBsYXN0IGFwcHJvYWNoIGlzIHRoYXQgaXQgaXMgZGlmZmljdWx0IHRv
DQo+ICAgICBhbGxvdyBpdCB3aXRoIHRoZSBjdXJyZW50IERIQ1B2NiBzcGVjaWZpY2F0aW9uczsg
aW4gc29tZSBjYXNlcw0KPiAgICAgaXQgaXMgbm90IGNsZWFyIGVub3VnaCwgYW5kIGluIG90aGVy
IGNhc2VzIGV4aXN0aW5nIHJlc3RyaWN0aW9ucw0KPiAgICAgY2FuIG1ha2UgaXQgaW1wb3NzaWJs
ZS4gIFRoaXMgZG9jdW1lbnQgaW50cm9kdWNlcyBzb21lDQo+ICAgICBjbGFyaWZpY2F0aW9ucyBh
bmQgc21hbGwgbW9kaWZpY2F0aW9ucyB0byB0aGUgY3VycmVudA0KPiAgICAgc3BlY2lmaWNhdGlv
biB0byBhZGRyZXNzIHRoaXMgY29uY2Vybi4NCj4NCj4gKFRoZSBzZWNvbmQgcGFyYWdyYXBoIGlz
IG15IGF0dGVtcHQgb2YgcmVwaHJhc2luZyB0aGUgdmVyeSBsYXN0IA0KPiBzZW50ZW5jZSBvZiB0
aGUgb3JpZ2luYWwgcGFyYWdyYXBoIGJhc2VkIG9uIG15IHRoZSBzZWVtaW5nIGludGVudCBvZg0K
PiBpdCkNCj4NCj4gSWYgc28sIGFuZCBpZiB5b3UgdGhpbmsgbXkgdGV4dCBpcyBjbGVhcmVyLCBw
bGVhc2UgZmVlbCBmcmVlIHRvIHVzZSANCj4gaXQuICBJZiB5b3UgYmVsaWV2ZSB0aGUgb3JpZ2lu
YWwgdGV4dCBpcyBjbGVhciBlbm91Z2ggKGFuZCBlc3BlY2lhbGx5IA0KPiBpZiBvdGhlcnMgYWxz
byB0aGluayBzbyksIEknbSBva2F5IHdpdGgga2VlcGluZyB0aGUgb3JpZ2luYWwgDQo+IHBhcmFn
cmFwaC4NCj4NCg0KV2Ugd2lsbCBkaXNjdXNzIHRoaXMgd2l0aCBCZXJuaWUgYW5kIGRlY2lkZSB0
byB3aGF0IGV4dGVudCB3ZSB3aWxsIHVzZSB5b3VyIHRleHQuDQoNCg0KTWFueSB0aGFua3MgZm9y
IHRoZSBwcm9tcHQgcmVzcG9uc2UhDQoNCk1hcmNpbg0K


From nobody Thu Feb 12 17:14:40 2015
Return-Path: <jiangsheng@huawei.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 6A4681A026C for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 17:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ayeYc56_i6pg for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 17:14:23 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98D731A0242 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 17:14:22 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPF63557; Fri, 13 Feb 2015 01:14:20 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Feb 2015 01:14:20 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.106]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Fri, 13 Feb 2015 09:14:12 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <mellon@fugue.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
Thread-Index: AQHQQx2McUj9f9+oTEe7lmci6/QZ1ZzoKFcAgAAI64CAAwpAgIAAHFkAgAD0TiCAAIIfAIAASAeAgAC0l/A=
Date: Fri, 13 Feb 2015 01:14:11 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923B04D5A6@nkgeml512-mbx.china.huawei.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com> <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com> <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com>
In-Reply-To: <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/iX11k-t6Kvh5klC4caDvRR2Asbc>
Cc: dhcwg <dhcwg@ietf.org>, "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Fri, 13 Feb 2015 01:14:31 -0000

Pk9uIEZlYiAxMiwgMjAxNSwgYXQgMTI6NTcgUE0sIOelnuaYjumBlOWTiSA8amlubWVpQHdpZGUu
YWQuanA+IHdyb3RlOg0KPj4gVG8gYmUgY2xlYXI6IG15IGN1cnJlbnQgcG9zaXRpb24gaXMgc3Rp
bGwgYWdhaW5zdCB0aGlzIG9wdGlvbi4gIEknbQ0KPj4gYWx3YXlzIGluIHRoZSBjYW1wIG9mICJw
cm9ibGVtIGZpcnN0LCB0aGVuIHNvbHV0aW9uIi4gIEFuZCB0aGF0J3MNCj4+IGFsc28gdGhlIGNh
c2Ugb2YgdGhpcyBkb2N1bWVudCBzaW5jZSBhcm91bmQgTWF5IDIwMTQ6DQo+PiBodHRwOi8vd3d3
LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvZGhjd2cvY3VycmVudC9tc2cxNTUyMC5odG1sDQo+
DQo+VGhpcyBpcyBhIGZpbmUgaWRlYSBpbiB0aGVvcnkuICAgSG93ZXZlciwgc2VjdGlvbiA3IGRv
ZXMgbm90IHJlcHJlc2VudCBhIHZhbGlkDQo+cHJvYmxlbSBzdGF0ZW1lbnQuDQo+DQo+PiBCdXQg
YXQgbGVhc3QgYXJvdW5kIGxhc3QgTWF5IG91ciBjb25zZW5zdXMNCj4+IHNob3VsZCBoYXZlIGJl
ZW4gYWdhaW5zdCB0aGF0IGFwcHJvYWNoLCBoZW5jZSB0aGUgY3VycmVudCBvcmdhbml6YXRpb24N
Cj4+IG9mIHRoZSBkcmFmdC4gIEp1c3QgYmVjYXVzZSBpdCB0cmlnZ2VycyBhIGhvdCBkaXNjdXNz
aW9uIGRvZXNuJ3QNCj4+IGF1dG9tYXRpY2FsbHkgZGlzbWlzcyB0aGUgb3JpZ2luYWwgY29uY2Vy
biBhbmQganVzdGlmeSBpZ25vcmluZyBpdC4NCj4NCj5JdCB3YXNuJ3QgY2xlYXIgdG8gbWUgdGhh
dCB0aGVyZSB3YXMgYSBjb25zZW5zdXMgdG8gYWRkIHRoZSBzcGVjdWxhdGl2ZSB1c2UNCj5jYXNl
cyB0byB0aGUgZG9jdW1lbnQsIGJ1dCBJIHdpbGwgbGVhdmUgdGhhdCB0byB0aGUgY2hhaXJzIHRv
IGRlY2lkZS4NCj4NCj4+IFVubGVzcyBhbmQgdW50aWwgd2Ugc2VlIGEgY2xlYXIgd2cgY29uc2Vu
c3VzIHRoYXQgd2Ugbm93IGFsbG93IGl0IHRvDQo+PiBzaGlwIGV2ZW4gaWYgbm8gb25lIGNhbiBl
eHBsYWluIHdoYXQga2luZCBvZiBwcm9ibGVtIGl0IHdpbGwgc29sdmUsIEkNCj4+IG9iamVjdCB0
byBtb3ZpbmcgZm9yd2FyZCB3aXRoIGp1c3QgcmVtb3ZpbmcgdGhpcyBzZWN0aW9uLiAgQW5kLCBJ
TU8sDQo+PiB0aGlzIGNvbnNlbnN1cyBjaGFuZ2Ugd2lsbCByZXF1aXJlIGFub3RoZXIgcm91bmQg
b2YgV0dMQy4NCj4NCj5UaGF0J3MgYSByZWFzb25hYmxlIHJlcXVlc3QuDQo+DQo+QnV0IHRoYXQg
c2FpZCwgbGV0J3MgYmUgY2xlYXI6IHdlIGRvIGFjdHVhbGx5IGhhdmUgYSBwcm9ibGVtLiAgIFRo
ZSBwcm9ibGVtIGlzDQo+dGhhdCB0aGUgYXV0aGVudGljYXRpb24gc2NoZW1lIGRlc2NyaWJlZCBp
biBSRkMgMzMxNSBpcyBub3QgZGVwbG95YWJsZSwNCj5iZWNhdXNlIGl0IHJlbGllcyBvbiBhIGtl
eSBkaXN0cmlidXRpb24gbW9kZWwgdGhhdCBkb2Vzbid0IHdvcmsgd2l0aCBhIHR5cGljYWwNCj5E
SENQIGRlcGxveW1lbnQuICAgVGhpcyBkb2N1bWVudCB1c2VzIGEga2V5IGRpc3RyaWJ1dGlvbiBt
b2RlbCB0aGF0IHdvdWxkDQo+d29yayBiZXR0ZXIuICAgU28gdGhpcyBpcyBkZWZpbml0ZWx5IGFu
IGltcHJvdmVtZW50IG92ZXIgUkZDIDMzMTUuDQo+DQo+SXQgaXMgaG93ZXZlciB0cnVlIHRoYXQg
d2UgZG8gbm90IGtub3cgd2hvIHdvdWxkIHVzZSB0aGlzLiAgIFRoaXMgZG9jdW1lbnQNCj5pcyB2
ZXJ5IHNwZWN1bGF0aXZlLiAgIEFuZCBJIGNhbiBpbWFnaW5lIG90aGVyIHdheXMgdG8gc29sdmUg
dGhpcyBwcm9ibGVtLS1mb3INCj5leGFtcGxlLCBkb2luZyBhIHNoYXJlZCBzZWNyZXQgZXhjaGFu
Z2UgdXNpbmcgcHVibGljIGtleXMuICAgQnV0IHRoZXNlIGFyZQ0KPnByb2JsZW1zIHRoYXQgdGhl
IHdvcmtpbmcgZ3JvdXAgaGFzIGJlZW4gYXdhcmUgb2YgZm9yIG92ZXIgYSBkZWNhZGUsIGFuZA0K
PndlJ3ZlIG1hZGUgbm8gZm9yd2FyZCBwcm9ncmVzcy4NCj4NCj5UaGUgcmVhc29uIEkgc3VwcG9y
dCBpc3N1aW5nIHRoaXMgZG9jdW1lbnQgYXMgYW4gUkZDIGlzIHRoYXQgSSB0aGluayBpdCB3b3Vs
ZA0KPndvcmssIGFuZCB3b3VsZCB3b3JrIGJldHRlciB0aGFuIHdoYXQgd2UgaGF2ZSBub3csIGFu
ZCBJJ2QgbGlrZSB0byBzZWUgaWYNCj5hbnlib2R5IHdpbGwgaW1wbGVtZW50IGl0LiAgIFVudGls
IHRoZXJlIGlzIGEgZG9jdW1lbnQgdG8gaW1wbGVtZW50LCBjbGVhcmx5DQo+bm9ib2R5IGlzIGdv
aW5nIHRvIGltcGxlbWVudCBhbnl0aGluZy4NCj4NCj5TbyB0aGF0J3Mgd2h5IGRlc3BpdGUgdGhl
IGxhY2sgb2YgYSB1c2UgY2FzZSBkb2N1bWVudCBvciBhIGxpc3Qgb2Yga25vd24gdXNlDQo+Y2Fz
ZXMgb3RoZXIgdGhhbiBzZWN0aW9uIDcsIEkgdGhpbmsgd2Ugc2hvdWxkIHB1Ymxpc2ggdGhlIGRv
Y3VtZW50Lg0KDQpUaGVyZSBhcmUgdHdvIGNoYW5nZXMgZmVlZGJhY2sgZnJvbSBBRCByZXZpZXcs
IHRoYXQgd291bGQgcmVxdWlyZSBhbm90aGVyIFdHTEMgaW4gbXkgb3BpbmlvbjoNCg0KMSkgcmVt
b3ZlIHRoZSBzZWN0aW9uIHRoYXQgZGVzY3JpcHQgbm90aW9uYWwgdXNlIGNhc2VzLCB3aGljaCBk
b2VzIG5vdCByZXByZXNlbnQgYSB2YWxpZCBwcm9ibGVtIHN0YXRlbWVudC4gSXQgd2lsbCByZXN1
bHQgbm8gdXNlIGNhc2UgZGVzY3JpcHRpb24gaW4gdGhlIGRvY3VtZW50LiBCdXQgdGhlIG9yaWdp
bmFsIHByb2JsZW0sIHRoYXQgbm8gbWVjaGFuaXNtIGV4aXN0cyBmb3Igc2VjdXJpdHkgREhDUCBt
ZXNzYWdlcyBiZXR3ZWVuIHNlcnZlcnMgYW5kIGNsaWVudHMgdGhhdCBkb2VzIG5vdCBoYXZlIGEg
c2VyaW91cyBrZXkgZGlzdHJpYnV0aW9uIHByb2JsZW0sIHNob3VsZCBiZSBzdWZmaWNpZW50IHRv
IG1vdGl2YXRlIHRoZSBwcm9wb3NlZCBtZWNoYW5pc20uDQoyKSByZW1vdmUgdGhlIGxpbWl0YXRp
b24gdGhhdCBvbmx5IGNsaWVudHMgdXNlIFBLSS0gY2VydGlmaWNhdGVzIGFuZCBvbmx5IHNlcnZl
cnMgdXNlIHB1YmxpYyBrZXlzLiBUaGUgbmV3IHRleHQgd291bGQgYWxsb3cgY2xpZW50cyB1c2Ug
cHVibGljIGtleXMgYW5kIHNlcnZlcnMgdXNlIFBLSS1jZXJ0aWZpY2F0ZXMuDQoNCkkgd2lsbCBh
cHBseSB0aGUgYWJvdmUgdHdvIGNoYW5nZXMgYW5kIHN1Ym1pdCBhbiB1cGRhdGUgdmVyc2lvbiB0
b2RheS4gVGhlbiBESEMgY2hhaXJzIG1heSBsYXVuY2ggYSBzaG9ydCBXR0xDIHRvIHNlZSB3aGV0
aGVyIHRoZSBXRyBjb3VsZCByZWFjaCBjb25zZW5zdXMgb24gdGhpcy4gSXQgd291bGQgZm9ybSB0
aGUgZm9sbG93LXVwIGFjdGlvbi4NCg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZw0KDQo=


From nobody Thu Feb 12 17:32:04 2015
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 3CB1E1A0177 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 17:32:01 -0800 (PST)
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 BNrFs1BgbH64 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 17:32:00 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B34FB1A0173 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 17:31:59 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id x3so13766145wes.6 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 17:31:58 -0800 (PST)
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=G2TKFsthQpdMLtRBKYZs+R3osEDOPG2p8xhyMXVrxW0=; b=IWRxmt3k+VZZsS4c0GmEiQaxW1RMyO6pju6TsO1OczWz2PU5zErwv88EicI0HZSqZE v9Raiil1p9okfMNOHo6CVm8YU4p5/zaW3GC1gNre8Wo+uo1hdiUmsVgBRSclLsHcrUyc zLoisc7ozmZ2+dj/b/DM1YgQQAwAuzyE4VLW8VR9ZEzxz7+tit61Pqr2ofVdOhC+U8ks BdjHx+jpXGQfliIhpBM48Zcj8So3X5uWLkbPp1tjZmOPdRVRo8mkAG/25jrLTmRg9UgX qGCQdl7Z9ii0TkTRyw6yrzIVI2M5G18EtkJogwxwc8vJ4+uIM8/OmXtnXlVbP8NkS49B Uttw==
MIME-Version: 1.0
X-Received: by 10.180.108.178 with SMTP id hl18mr11102526wib.92.1423791118464;  Thu, 12 Feb 2015 17:31:58 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.44 with HTTP; Thu, 12 Feb 2015 17:31:58 -0800 (PST)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923B04D5A6@nkgeml512-mbx.china.huawei.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com> <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com> <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04D5A6@nkgeml512-mbx.china.huawei.com>
Date: Thu, 12 Feb 2015 17:31:58 -0800
X-Google-Sender-Auth: UBbMrc8TRUfHA2AeOrl0sOe15cA
Message-ID: <CAJE_bqdf37XJVgTqd6AKBedj+kNSyiJ_iH8Qfyw674Mc9E4uFQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/2Y3-QHQc6easvM7prbhbYbvcmT4>
Cc: dhcwg <dhcwg@ietf.org>, "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Fri, 13 Feb 2015 01:32:01 -0000

At Fri, 13 Feb 2015 01:14:11 +0000,
Sheng Jiang <jiangsheng@huawei.com> wrote:

> There are two changes feedback from AD review, that would require another=
 WGLC in my opinion:
>
> 1) remove the section that descript notional use cases, which does not re=
present a valid problem statement. It will result no use case description i=
n the document. But the original problem, that no mechanism exists for secu=
rity DHCP messages between servers and clients that does not have a serious=
 key distribution problem, should be sufficient to motivate the proposed me=
chanism.

I don't think we have a consensus on removing that section yet.  IMO
the right process is
- revise the draft addressing other comments from Ted
- start discussion on the wg about how to handle the usage section
- apply any result of the discussion to the draft and revise it.  at
  this point we may remove the section, revise it, or address the
  underlying issue in a different way.
- then start another WGLC

--
JINMEI, Tatuya


From nobody Thu Feb 12 18:00:49 2015
Return-Path: <mellon@fugue.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 F34191A0372 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 18:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 ylQl_AMaZWSZ for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 18:00:46 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id AD0C71A03A0 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 18:00:46 -0800 (PST)
Received: from [192.168.1.102] (rich-dsl1-136.greenmountainaccess.net [65.19.75.136]) by toccata.fugue.com (Postfix) with ESMTPSA id 9BF5723805DB; Thu, 12 Feb 2015 21:00:44 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAJE_bqdf37XJVgTqd6AKBedj+kNSyiJ_iH8Qfyw674Mc9E4uFQ@mail.gmail.com>
Date: Thu, 12 Feb 2015 21:00:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE1691BB-8B7B-4844-9CD8-5A81499745B2@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com> <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com> <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04D5A6@nkgeml512-mbx.china.huawei.com> <CAJE_bqdf37XJVgTqd6AKBedj+kNSyiJ_iH8Qfyw674Mc9E4uFQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/4p5M9tn-EBEBvK3wCSPkTFSCU_4>
Cc: dhcwg <dhcwg@ietf.org>, "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Fri, 13 Feb 2015 02:00:48 -0000

On Feb 12, 2015, at 8:31 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> I don't think we have a consensus on removing that section yet.  IMO
> the right process is
> - revise the draft addressing other comments from Ted
> - start discussion on the wg about how to handle the usage section
> - apply any result of the discussion to the draft and revise it.  at
>  this point we may remove the section, revise it, or address the
>  underlying issue in a different way.
> - then start another WGLC

I don't understand why this section was added in the first place.   I =
objected to the idea of adding these use cases back when it was being =
talked about because I didn't think what was being proposed made sense; =
the result was the current version, which is more specific, but =
consequently is even worse because the use cases for this proposal are =
completely hypothetical.   I didn't have time to review the document =
again until the AD review, but the idea that there was consensus to =
include this text is only correct if you discount the objections I =
raised back in June of last year.

As far as I can tell the only person other than you who was in favor of =
adding this text was Ralph, and I am not convinced that he reviewed it =
again after it was added--the last comment I see from him in the archive =
is expressing support for the general idea, but objecting to the =
particulars, and that predates the addition of section 7 to the =
document.

I tend to agree that there is a need to get some clarity on the =
consensus for or against this text, and it may be that the right thing =
to do is give up on advancing this document during my tenure as AD.   If =
we wait for Terry to take over, then I can participate as a regular =
working group participant who has enough free time to actually stay on =
top of the discussion.

I don't see any reason to think that Terry would object to this work, =
and a rush to get this out before March when we are not in agreement =
doesn't seem like a good idea.=


From nobody Thu Feb 12 21:54:21 2015
Return-Path: <jiangsheng@huawei.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 78AE11A03C7 for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 21:54:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 F-SVtxg-MBSp for <dhcwg@ietfa.amsl.com>; Thu, 12 Feb 2015 21:54:17 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92E161A03A2 for <dhcwg@ietf.org>; Thu, 12 Feb 2015 21:54:15 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSO87601; Fri, 13 Feb 2015 05:54:13 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 13 Feb 2015 05:54:12 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.106]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Fri, 13 Feb 2015 13:54:09 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <mellon@fugue.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Thread-Topic: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
Thread-Index: AQHQQx2McUj9f9+oTEe7lmci6/QZ1ZzoKFcAgAAI64CAAwpAgIAAHFkAgAD0TiCAAIIfAIAASAeAgAC0l/D//4J5AIAACAcAgADEHcA=
Date: Fri, 13 Feb 2015 05:54:08 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923B04D74A@nkgeml512-mbx.china.huawei.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com> <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com> <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04D5A6@nkgeml512-mbx.china.huawei.com> <CAJE_bqdf37XJVgTqd6AKBedj+kNSyiJ_iH8Qfyw674Mc9E4uFQ@mail.gmail.com> <DE1691BB-8B7B-4844-9CD8-5A81499745B2@fugue.com>
In-Reply-To: <DE1691BB-8B7B-4844-9CD8-5A81499745B2@fugue.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/gdQKcUG37U8fURnNVTqzHHLMWxU>
Cc: dhcwg <dhcwg@ietf.org>, "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Fri, 13 Feb 2015 05:54:19 -0000

PkkgdGVuZCB0byBhZ3JlZSB0aGF0IHRoZXJlIGlzIGEgbmVlZCB0byBnZXQgc29tZSBjbGFyaXR5
IG9uIHRoZSBjb25zZW5zdXMgZm9yDQo+b3IgYWdhaW5zdCB0aGlzIHRleHQsIGFuZCBpdCBtYXkg
YmUgdGhhdCB0aGUgcmlnaHQgdGhpbmcgdG8gZG8gaXMgZ2l2ZSB1cCBvbg0KPmFkdmFuY2luZyB0
aGlzIGRvY3VtZW50IGR1cmluZyBteSB0ZW51cmUgYXMgQUQuICAgSWYgd2Ugd2FpdCBmb3IgVGVy
cnkgdG8NCj50YWtlIG92ZXIsIHRoZW4gSSBjYW4gcGFydGljaXBhdGUgYXMgYSByZWd1bGFyIHdv
cmtpbmcgZ3JvdXAgcGFydGljaXBhbnQgd2hvDQo+aGFzIGVub3VnaCBmcmVlIHRpbWUgdG8gYWN0
dWFsbHkgc3RheSBvbiB0b3Agb2YgdGhlIGRpc2N1c3Npb24uDQo+DQo+SSBkb24ndCBzZWUgYW55
IHJlYXNvbiB0byB0aGluayB0aGF0IFRlcnJ5IHdvdWxkIG9iamVjdCB0byB0aGlzIHdvcmssIGFu
ZCBhIHJ1c2gNCj50byBnZXQgdGhpcyBvdXQgYmVmb3JlIE1hcmNoIHdoZW4gd2UgYXJlIG5vdCBp
biBhZ3JlZW1lbnQgZG9lc24ndCBzZWVtIGxpa2UNCj5hIGdvb2QgaWRlYS4NCg0KT0suIEF0IGxl
YXN0LCB3ZSByZWFjaCB0aGUgY29uc2Vuc3VzIHRoYXQgd2Ugc2hvdWxkIGNvbnRpbnVlIHRvIGRp
c2N1c3MgdGhpcywgcmF0aGVyIHRoYW4gYW55IHJ1c2hpbmcuDQoNClBlcnNvbmFsbHksIEkgZG9u
J3QgdGFrZSBhbnkgc3Ryb25nIHBvc2l0aW9uIHdoZXRoZXIgd2Ugc2hvdWxkIGhhdmUgdXNlIGNh
c2UgZGVzY3JpcHRpb24gb3Igbm90LiBNeSByZWFkaW5nIGZyb20gVGVkJ3MgY29tbWVudHMgaXMg
aGUgZGlkIG5vdCByZWFsbHkgb2JqZWN0IChhbHRob3VnaCBoZSBtYXkgcHJlZmVyIHRvIG5vdCkg
dG8gaGF2ZSB1c2UgY2FzZSBkZXNjcmlwdGlvbiwgYnV0IHRoZSBjdXJyZW50IHRleHQgZm9yIHVz
ZSBjYXNlIGRlc2NyaXB0aW9uIGhhcyBzb21lIHNlcmlvdXMgaXNzdWVzLiBBbSBJIHJpZ2h0LCBU
ZWQ/IElmIHNvLCBsZXQncyB0cnkgdG8gZml4IHRoZXNlIHRleHQuIENvcnJlY3QgdXNlIGNhc2Ug
ZGVzY3JpcHRpb24gYXJlIG5vdCBoYXJtZnVsLiBIb3dldmVyLCB3ZSBtYXkgc3RhdGUgdGhhdCB0
aGVzZSB1c2UgY2FzZXMgYXJlIG5vdGlvbmFsLiBNYXliZSwgdGhlIGluZHVzdHJ5IG9yIG1hcmtl
dCBjb3VsZCBkZXZlbG9wIG1vcmUgY2FzZXMgdGhhbiB3ZSBjYW4gY2xlYXJseSBkZXNjcmliZSBm
b3Igbm93Lg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQo=


From nobody Fri Feb 13 04:50:00 2015
Return-Path: <mellon@fugue.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 BBFFE1A6F29 for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 04:49:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 G_SqD5rHZgQm for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 04:49:56 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 6228C1A6FFA for <dhcwg@ietf.org>; Fri, 13 Feb 2015 04:49:56 -0800 (PST)
Received: from [192.168.1.102] (rich-dsl1-136.greenmountainaccess.net [65.19.75.136]) by toccata.fugue.com (Postfix) with ESMTPSA id E992F23805E2; Fri, 13 Feb 2015 07:49:54 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923B04D74A@nkgeml512-mbx.china.huawei.com>
Date: Fri, 13 Feb 2015 07:49:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <15F11E28-3367-4BC4-B3E2-5A52BD006746@fugue.com>
References: <D2D56951-A166-4A37-B81C-D2B1E5BC148E@fugue.com> <CAJE_bqdfiD0du-O9eX2ARCMATh9DY5kYauH7EzLEW7VHZftrcw@mail.gmail.com> <FC84E866-E474-45C3-A40C-93D23CDD3B84@fugue.com> <CAJE_bqd1hicxkKJREFHSsusGq6GZpJLHaXGLEhm_gxf+aT0uHw@mail.gmail.com> <92FABA46-F97D-42B3-A50B-3EDD360084B3@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04BCE6@nkgeml512-mbx.china.huawei.com> <CAJE_bqcNb7J0mpktj84H0gL_rteLhVbL1Acvzx_iS5+pVPNQhw@mail.gmail.com> <99E526A8-8BEA-4DF9-A182-799BCBC36D6D@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04D5A6@nkgeml512-mbx.china.huawei.com> <CAJE_bqdf37XJVgTqd6AKBedj+kNSyiJ_iH8Qfyw674Mc9E4uFQ@mail.gmail.com> <DE1691BB-8B7B-4844-9CD8-5A81499745B2@fugue.com> <5D36713D8A4E7348A7E10DF7437A4B923B04D74A@nkgeml512-mbx.china.huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/NMvlAI5YfalAwcnWJxViZBlLqw0>
Cc: dhcwg <dhcwg@ietf.org>, "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-sedhcpv6-05
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: Fri, 13 Feb 2015 12:49:58 -0000

On Feb 13, 2015, at 12:54 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:
> Personally, I don't take any strong position whether we should have =
use case description or not. My reading from Ted's comments is he did =
not really object (although he may prefer to not) to have use case =
description, but the current text for use case description has some =
serious issues. Am I right, Ted? If so, let's try to fix these text. =
Correct use case description are not harmful. However, we may state that =
these use cases are notional. Maybe, the industry or market could =
develop more cases than we can clearly describe for now.

If there were some clear description of actual use cases that did not =
exclude other plausible use cases, and that we thought would actually be =
useful, I would not necessarily object to that, but in that case it =
should be expressed as suggestions, not clear statements of what is =
right, because we have zero deployment experience and would just be =
speculating.

All things being equal, I think that such text is better left as future =
work, because it would be speculative.   But if we can come up with some =
solid use cases and explain how to do them, I'm okay with that.   The =
trick is that it can't just be a few paragraphs roughly outlining how to =
do it--it would have to be quite detailed.

If the consensus of the working group is to do that, I'll have some free =
time after March and would be happy to participate in making it =
happen--I do have some ideas for use cases.


From nobody Fri Feb 13 09:54:58 2015
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 4E8C51A0162 for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 09:54:57 -0800 (PST)
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 DwubdB2-fXai for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 09:54:56 -0800 (PST)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A6B71A0161 for <dhcwg@ietf.org>; Fri, 13 Feb 2015 09:54:55 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id h11so13935811wiw.1 for <dhcwg@ietf.org>; Fri, 13 Feb 2015 09:54:54 -0800 (PST)
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=mdx3j8AMXtTSnAEjSV4gd9aTZ/XSm/v3tN8onrGsm2c=; b=to1RfnM0IcCaNyd/IzboAXm1OyBsPTkxoUcmr7kbSJD8JWHKoj9UaB6j1WlgpWrvo0 S61qsWkQqcQHsXpv4nWyirxaeyjsTyr4YGM8rXK7RAgsoLDj30z0dXH4csgtIm3ltfia RuGpFMHkV7JOaheVgfVQqBk4VIA87anaRiuSYWdcq2abakQ0UiVjVYPbK5pBfjJXUca0 zyyp1vEl2/deTyq+Ma8Vncd+skOCATgYIWIsQuCCwsebD/ABjEB5twDpb6JPX3nHq67l IgwYwY2EkGJGhp7vujTDx2NC4dsFwI290Mwn59hVUzLclPpyKCzop2eY3IJDyMfgja0M LJ8Q==
MIME-Version: 1.0
X-Received: by 10.194.78.72 with SMTP id z8mr21530366wjw.0.1423850094141; Fri, 13 Feb 2015 09:54:54 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Fri, 13 Feb 2015 09:54:54 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1C9A09C0@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com> <54DCE942.9080605@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1C9A09C0@xmb-rcd-x04.cisco.com>
Date: Fri, 13 Feb 2015 09:54:54 -0800
X-Google-Sender-Auth: 64nwGjvQBXCxxKI_25OBpi7bvFg
Message-ID: <CAJE_bqeHpu_mpc54kzFdBLkwkMjv3L4fubsb5eGyp94TC48aFQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <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/HwVmldjvtlNBRIeeeLillmSiztw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Fri, 13 Feb 2015 17:54:57 -0000

At Thu, 12 Feb 2015 23:21:07 +0000,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> I have published a -11 version of the draft that hopefully addresses Jinmei's and Ted's most recent comments.
>
> The wording was tweaked slightly from that discussed.
>
> Please see the -11 draft. http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-stateful-issues.

In case an explicit confirmation was expected: I have no objection to
shipping it.

--
JINMEI, Tatuya


From nobody Fri Feb 13 09:57:37 2015
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 C36891A01F4 for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 09:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 NGdU19-quIjR for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 09:57:34 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E810F1A0141 for <dhcwg@ietf.org>; Fri, 13 Feb 2015 09:57:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1258; q=dns/txt; s=iport; t=1423850254; x=1425059854; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=UlzRB5fnctcKRHTdX0bEuZu51nydrUixYXdfTqdKw4s=; b=ey9A3U9q5xD5UoYAO+WkJ/UfbB/UmMaAm63kCVqDvzdoIZWKQSk+3ovG gt851x4YAumJNGFss+Ogb8oLcqGHpguI5UMhMX3Z0ubx2nAQg8XDfxvf+ WQLrigHxeUjbawenhk8aACkphTHtllbhOSDxEimGrsbRDvHSguTsGwuu5 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FAOY53lStJV2R/2dsb2JhbABbgwZSWgSCfr8shXECHHhDAQEBAQEBfIQMAQEBAwEjEUUFBwQCAQgRBAEBAwIGHQMCAgIfERQBCAgCBAENBQiIEQMJCA2+D5FHDYVMAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4EhiWuCQ4F5FhsHBoJiLoEUAQSNSYFrg1aEGYJeOIJPiGKGBCKDbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,572,1418083200"; d="scan'208";a="395959603"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-3.cisco.com with ESMTP; 13 Feb 2015 17:57:33 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t1DHvWYX028948 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Feb 2015 17:57:33 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Fri, 13 Feb 2015 11:57:32 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Tomek Mrugalski (tomasz.mrugalski@gmail.com)" <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.txt
Thread-Index: AdA8x8lsczM1NFL9RxaqwuSBmk55XgCevsGAAFKgikAAeCiTAP//tueggAT7bQCAAbZrAIAAM6qAgAAtKHCAALEHAIAASM6AgAFnaQCAADFwAIAABusAgAALKICAAYbJAIAAY/tw
Date: Fri, 13 Feb 2015 17:57:32 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9A3B85@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1B7DAA99@xmb-rcd-x04.cisco.com> <CAJE_bqcR0MC3hSBUDi1vh0euvGfC1m1ZxtrE3oLQkDiKpD0nWw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1B80C36D@xmb-rcd-x04.cisco.com> <CAJE_bqcj74ZbuPOLMZ2PRZyZUNcEPKXTeB7V4GbQGsWi6HrMfQ@mail.gmail.com> <B57385A8-AAAB-46D9-BE07-9B3BC4EC1129@cisco.com> <CAJE_bqeOojbpxSRZEThMTuyz+PD3ae4F4jM3g=GixxQraQOfig@mail.gmail.com> <54DA69B2.7030102@gmail.com> <70C16D69-C2E4-48DD-A768-B25731D05D26@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1C99843A@xmb-rcd-x04.cisco.com> <4FE80FD5-CA8E-48EF-A040-A36D37480595@nominum.com> <CAJE_bqfH-m-=ABbi3VYYY8K5Mjs_t0kKjxM7AnjSAASiDUf_YA@mail.gmail.com> <54DCB9FC.5020400@gmail.com> <CAJE_bqe53dU-C4V_3RLzv3Cq2sJnhYsmVfw6xpOkwvJWnYB=-g@mail.gmail.com> <54DCE942.9080605@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1C9A09C0@xmb-rcd-x04.cisco.com> <CAJE_bqeHpu_mpc54kzFdBLkwkMjv3L4fubsb5eGyp94TC48aFQ@mail.gmail.com>
In-Reply-To: <CAJE_bqeHpu_mpc54kzFdBLkwkMjv3L4fubsb5eGyp94TC48aFQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/XsHXDT17KF91WK6bFoUifpyPgAU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] draft-ietf-dhc-dhcpv6-stateful-issues-10.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: Fri, 13 Feb 2015 17:57:36 -0000

VGhhbmtzIQ0KDQpJIHRoaW5rIFRvbWVrIHNob3VsZCBiZSByZWFkeSB0byBwcm92aWRlIFRlZCB0
aGUgc2hlcGhlcmQgd3JpdGUtdXAgYW5kIHN1Ym1pdCBmb3IgcHVibGljYXRpb24gLSBzbyBob3Bl
ZnVsbHkgaXQgd2lsbCBoYXBwZW4gc2hvcnRseSENCg0KLSBCZXJuaWUNCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IGppbm1laS50YXR1eWFAZ21haWwuY29tIFttYWlsdG86amlu
bWVpLnRhdHV5YUBnbWFpbC5jb21dIE9uIEJlaGFsZiBPZiA/Pz8/DQpTZW50OiBGcmlkYXksIEZl
YnJ1YXJ5IDEzLCAyMDE1IDEyOjU1IFBNDQpUbzogQmVybmllIFZvbHogKHZvbHopDQpDYzogTWFy
Y2luIFNpb2RlbHNraTsgZGhjd2dAaWV0Zi5vcmc7IFRlZCBMZW1vbg0KU3ViamVjdDogUmU6IFtk
aGN3Z10gZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXN0YXRlZnVsLWlzc3Vlcy0xMC50eHQNCg0KQXQg
VGh1LCAxMiBGZWIgMjAxNSAyMzoyMTowNyArMDAwMCwNCiJCZXJuaWUgVm9seiAodm9seikiIDx2
b2x6QGNpc2NvLmNvbT4gd3JvdGU6DQoNCj4gSSBoYXZlIHB1Ymxpc2hlZCBhIC0xMSB2ZXJzaW9u
IG9mIHRoZSBkcmFmdCB0aGF0IGhvcGVmdWxseSBhZGRyZXNzZXMgSmlubWVpJ3MgYW5kIFRlZCdz
IG1vc3QgcmVjZW50IGNvbW1lbnRzLg0KPg0KPiBUaGUgd29yZGluZyB3YXMgdHdlYWtlZCBzbGln
aHRseSBmcm9tIHRoYXQgZGlzY3Vzc2VkLg0KPg0KPiBQbGVhc2Ugc2VlIHRoZSAtMTEgZHJhZnQu
IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZGhjLWRoY3B2Ni1zdGF0ZWZ1
bC1pc3N1ZXMuDQoNCkluIGNhc2UgYW4gZXhwbGljaXQgY29uZmlybWF0aW9uIHdhcyBleHBlY3Rl
ZDogSSBoYXZlIG5vIG9iamVjdGlvbiB0byBzaGlwcGluZyBpdC4NCg0KLS0NCkpJTk1FSSwgVGF0
dXlhDQo=


From nobody Fri Feb 13 13:25:30 2015
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 262EC1A1A14 for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 13:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 z_NGPTCGh1V9 for <dhcwg@ietfa.amsl.com>; Fri, 13 Feb 2015 13:25:26 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 767741A1A58 for <dhcwg@ietf.org>; Fri, 13 Feb 2015 13:25:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6234; q=dns/txt; s=iport; t=1423862726; x=1425072326; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=MajdUVFv/yfqFrMqOePgOtPyUJ+n1THyPdxV/dyI8x8=; b=IDa37OIfmUH6pe2JaQzMTwuZdDRuROABWKspJkHofoNlR9WcVeIco4ak k/eBWEO97K4B+cUy/aCPB0r0vHzYHoJzwmsa2c63mEk5gYh+rha+PffFG IzfkF77CVjPjK9ZHXeIbKCXbn17DSk9T9ugyoxz/2ITP0rVcudDNI94EC I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFAFVq3lStJA2D/2dsb2JhbABbgwZSVQUEwiMMhW8CgRRDAQEBAQEBfIQMAQEBBAEBATc0CwwGARkEAQELFAkuCxQJCQEEDgUIAYgkCAXVAAEBAQEBAQEBAQEBAQEBAQEBAQEBGIoOhToPIg2DEIEUBY80g1aGdziCT45mIoICHIFQb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,573,1418083200"; d="scan'208";a="395995928"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-5.cisco.com with ESMTP; 13 Feb 2015 21:25:25 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t1DLPPvY022537 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Feb 2015 21:25:25 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Fri, 13 Feb 2015 15:25:25 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "draft-ietf-dhc-dynamic-shared-v4allocation@tools.ietf.org" <draft-ietf-dhc-dynamic-shared-v4allocation@tools.ietf.org>
Thread-Topic: Advancing draft-ietf-dhc-dynamic-shared-v4allocation-03.txt
Thread-Index: AdBHzr8SSeEEqn00T96nSXYYloaDgA==
Date: Fri, 13 Feb 2015 21:25:25 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9A44E5@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6WD_s3JROm9YnI17Wcr6na0x1lE>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: [dhcwg] Advancing draft-ietf-dhc-dynamic-shared-v4allocation-03.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: Fri, 13 Feb 2015 21:25:29 -0000

Hi:

So in working on the shepherding document for this draft, I found some issu=
es that were introduced in the 03 draft (or perhaps also missed in the 02).=
 I think before sending this on, these should be fixed. These are mostly mi=
nor, but because of the number of them I think it best to address them firs=
t and publish an 04 version.

- In section 4, last paragraph - "with one of the offers does not containin=
g OPTION_V4_PORTPARAMS" should be replaced with "where a received offer doe=
s not contain OPTIION_V4_PORTPARAMS"?

- In section 5, list -  is the client allowed to send an instance of the OP=
TION_V4_PORTPARAMS in the DHCPDISCOVER? I think from later material it is, =
so should this be mentioned in #1?

And, for #2, shouldn't the "If the received OPTION_V4_PORTPARAMS ..." sente=
nce appear before what the response must contain? And, would it not be bett=
er to say "The DHCPOFFER message is then encapsulated in ..."? Perhaps enti=
re #2 should be:

2. DHCP 4o6 Servers that receive the DHCPDISCOVER message and support share=
d IPv4 addresses respond with a DHCPOFFER message as usual with the shared =
IPv4 address in the 'yiaddr' field and MUST add an OPTION_V4_PORTPARAMS opt=
ion containing an available restricted port set. If the DHCPDISCOVER includ=
ed an OPTION_V4_PORTPARAMS option containing a non-zero PSID-Len field, the=
 DHCP  4o6 Server MAY allocate a port set of the requested size to the clie=
nt (depending on policy).  The DHCPOFFER message is then encapsulated in th=
e DHCPv4-response message and sent to the client.

And, for #3, why point out the "selected DHCP server's server identifier"? =
Isn't that normally added anyway? Shouldn't it just say the OPTION_V4_PORTP=
ARAMs? (Remove "the selected DHCP server's server identifier and"?

For #4, I think it would be best to be clear that the OPTION_V4_PORTPARAMs =
MUST be sent in the DHCPACK?

For #5, perhaps "perform a final check" to "perform an in-use probe"? (This=
 is more in line with what was used in section 6.)

For #6, why "MUST include the original client identifier"? Is this again a =
requirement above what is normal for clients? And, if this is important her=
e, why not in the DHCPDISCOVER and DHCPREQUEST?=20

The point with several of the above is just document what is NEWLY required=
 for this shared IPv4 allocation to work; avoid mentioning things that are =
already standardize elsewhere (as that could confuse people as to why you m=
ention it). If it is needed because it was not covered elsewhere, then it i=
s OK to include.

- In section 5, last paragraph - "followedon condition" should be "followed=
 on the condition"?

Also, would indicating that this is the INIT-REBOOT state from RFC 2131 mak=
e sense (yes, section 3.2 never says this, but it is used later and also ea=
sier for people to recognize?).

- In section 6, first paragraph - change "applying for a shared" should be =
"discovering for a shared"?

And, I don't really follow the sentence "The client retrieves a port set us=
ing the values contained in OPTION_V4_PORTPARMS", especially given the sent=
ence which follows. Perhaps clarify from WHERE the client retrieves would h=
elp (is this from the DHCPOFFER/DHCPACK or from it stored "binding" informa=
tion and thus related to the sentence that follows?

- In section 6.1, the first bullet has "e.g" instead of "e.g.".

- In section 8, last paragraph, would "ports reserved" be better than "port=
s saved"?

- In section 9.2, "CPE" is used. Perhaps best to just replace with "Custome=
r Provided Equipment"? You could add to the Terminology section, but as onl=
y used once doesn't seem worth it. Perhaps "CPE" isn't the best term here a=
nd just client would be sufficient?

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of internet-drafts@ie=
tf.org
Sent: Thursday, January 29, 2015 8:48 AM
To: i-d-announce@ietf.org
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dynamic-shared-v4allocation-03.=
txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Dynamic Host Configuration Working Group =
of the IETF.

        Title           : Dynamic Allocation of Shared IPv4 Addresses
        Authors         : Yong Cui
                          Qiong Sun
                          Ian Farrer
                          Yiu L. Lee
                          Qi Sun
                          Mohamed Boucadair
	Filename        : draft-ietf-dhc-dynamic-shared-v4allocation-03.txt
	Pages           : 13
	Date            : 2015-01-29

Abstract:
   This memo describes the dynamic allocation of shared IPv4 addresses
   to clients using DHCPv4.  Address sharing allows a single IPv4
   address to be allocated to multiple active clients simultaneously,
   each client being differentiated by a unique set of transport layer
   source port numbers.  The necessary changes to existing DHCPv4 client
   and server behavior are described and a new DHCPv4 option for
   provisioning clients with shared IPv4 addresses is included.

   Due to the nature of IP address sharing, some limitations to its
   applicability are necessary.  This memo describes these limitations
   and recommends suitable architectures and technologies where address
   sharing may be utilized.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation=
/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dynamic-shared-v4allocati=
on-03


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Mon Feb 16 23:19:50 2015
Return-Path: <internet-drafts@ietf.org>
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 231541A03A8; Mon, 16 Feb 2015 23:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 mkMgyVYghN3r; Mon, 16 Feb 2015 23:19:47 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A17251A8722; Mon, 16 Feb 2015 23:19:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150217071947.23544.33378.idtracker@ietfa.amsl.com>
Date: Mon, 16 Feb 2015 23:19:47 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/2ROgWRIKI_XFxj5sxNWGwveEhtU>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dynamic-shared-v4allocation-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Feb 2015 07:19:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Dynamic Allocation of Shared IPv4 Addresses
        Authors         : Yong Cui
                          Qiong Sun
                          Ian Farrer
                          Yiu L. Lee
                          Qi Sun
                          Mohamed Boucadair
	Filename        : draft-ietf-dhc-dynamic-shared-v4allocation-04.txt
	Pages           : 13
	Date            : 2015-02-16

Abstract:
   This memo describes the dynamic allocation of shared IPv4 addresses
   to clients using DHCPv4.  Address sharing allows a single IPv4
   address to be allocated to multiple active clients simultaneously,
   each client being differentiated by a unique set of transport layer
   source port numbers.  The necessary changes to existing DHCPv4 client
   and server behavior are described and a new DHCPv4 option for
   provisioning clients with shared IPv4 addresses is included.

   Due to the nature of IP address sharing, some limitations to its
   applicability are necessary.  This memo describes these limitations
   and recommends suitable architectures and technologies where address
   sharing may be utilized.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dynamic-shared-v4allocation-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 17 02:06:02 2015
Return-Path: <internet-drafts@ietf.org>
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 A353A1A8710; Tue, 17 Feb 2015 02:05:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ZNUx6sEKUn81; Tue, 17 Feb 2015 02:05:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D9BF1A8547; Tue, 17 Feb 2015 02:05:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150217100558.28129.21299.idtracker@ietfa.amsl.com>
Date: Tue, 17 Feb 2015 02:05:58 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/UiLE8ViFy0g2D5GeL2uodJxDzkk>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dynamic-shared-v4allocation-05.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Feb 2015 10:05:59 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Dynamic Allocation of Shared IPv4 Addresses
        Authors         : Yong Cui
                          Qiong Sun
                          Ian Farrer
                          Yiu L. Lee
                          Qi Sun
                          Mohamed Boucadair
	Filename        : draft-ietf-dhc-dynamic-shared-v4allocation-05.txt
	Pages           : 13
	Date            : 2015-02-17

Abstract:
   This memo describes the dynamic allocation of shared IPv4 addresses
   to clients using DHCPv4.  Address sharing allows a single IPv4
   address to be allocated to multiple active clients simultaneously,
   each client being differentiated by a unique set of transport layer
   source port numbers.  The necessary changes to existing DHCPv4 client
   and server behavior are described and a new DHCPv4 option for
   provisioning clients with shared IPv4 addresses is included.

   Due to the nature of IP address sharing, some limitations to its
   applicability are necessary.  This memo describes these limitations
   and recommends suitable architectures and technologies where address
   sharing may be utilized.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-dynamic-shared-v4allocation-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 18 00:29:07 2015
Return-Path: <internet-drafts@ietf.org>
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 B30211A9136; Wed, 18 Feb 2015 00:29:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 6C-YeSrIcQbP; Wed, 18 Feb 2015 00:29:03 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB581A0105; Wed, 18 Feb 2015 00:29:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218082903.16108.933.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 00:29:03 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/sjlzeeLzcv0OMpQR0KYEdF16qHs>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-stable-privacy-addresses-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Feb 2015 08:29:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : A Method for Generating Semantically Opaque Interface Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
        Authors         : Fernando Gont
                          Will(Shucheng) Liu
	Filename        : draft-ietf-dhc-stable-privacy-addresses-01.txt
	Pages           : 9
	Date            : 2015-02-18

Abstract:
   This document specifies a method for selecting IPv6 Interface
   Identifiers, to be employed by Dynamic Host Configuration Protocol
   for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses
   to DHCPv6 clients.  This method is a DHCPv6 server side algorithm,
   that does not require any updates to the existing DHCPv6
   specifications.  The aforementioned method results in stable
   addresses within each subnet, even in the presence of multiple DHCPv6
   servers or DHCPv6 server reinstallments.  It is a DHCPv6-variant of
   the method specified in RFC 7217 for IPv6 Stateless Address
   Autoconfiguration.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-stable-privacy-addresses/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-stable-privacy-addresses-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-stable-privacy-addresses-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 18 00:38:13 2015
Return-Path: <fgont@si6networks.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 92B811A7113 for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 00:38:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level: 
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] 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 zDlUC19dD-Tx for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 00:38:08 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8ECE1A1A5F for <dhcwg@ietf.org>; Wed, 18 Feb 2015 00:38:07 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YO08t-00058T-0V; Wed, 18 Feb 2015 09:37:59 +0100
Message-ID: <54E44F2D.1000602@si6networks.com>
Date: Wed, 18 Feb 2015 05:37:01 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <20150218082904.16108.26586.idtracker@ietfa.amsl.com>
In-Reply-To: <20150218082904.16108.26586.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20150218082904.16108.26586.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/DQ-atgjok9Jn8-HYbsAQMoR0dl0>
Cc: draft-ietf-dhc-stable-privacy-addresses@tools.ietf.org
Subject: [dhcwg] Revision of draft-ietf-dhc-stable-privacy-addresses (Fwd: New Version Notification for draft-ietf-dhc-stable-privacy-addresses-01.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, 18 Feb 2015 08:38:12 -0000

Folks,

We have published a revision of the aforementioned I-D. The two main
changes are:

1) Specification of data types, byte order, etc.

Each parameter of the F() function has now an associate datatype, byte
order, etc. This is crucial for the result of the function to be the
same across platforms and implementations.

2) F() now supports address ranges

The "Prefix" variable has been replaced with two parameters that specify
an IPv6 address range. Namely:

---- cut here ----
   1.  Compute a random (but stable) identifier with the expression:

       RID = F(IPV6_ADDR_HI | IPV6_ADDR_LOW | Client_DUID | IAID |
       Counter | secret_key)

       Where:

       RID:
          Random (but stable) Identifier

[....]

       IPV6_ADDR_HI:
          An IPv6 address specifying the upper boundary of the IPv6
          address pool from which the DHCPv6 server leases IPv6
          addresses.  It MUST be represented as a 128-bit unsigned
          integer in network byte order.  If multiple servers operate on
          the same network to provide increased availability, all such
          DHCPv6 servers MUST be configured with the address range
          (i.e., the same IPV6_ADDR_HI and IPV6_ADDR_LOW parameters).
          It is the administrator's responsibility that the
          aforementioned requirement is met.

       IPV6_ADDR_LOW:
          An IPv6 address specifying the lower boundary of the IPv6
          address pool from which the DHCPv6 server leases IPv6
          addresses.  It MUST be represented as a 128-bit unsigned
          integer in network byte order.  If multiple servers operate on
          the same network to provide increased availability, all such
          DHCPv6 servers MUST be configured with the address range
          (i.e., the same IPV6_ADDR_HI and IPV6_ADDR_LOW parameters).
          It is the administrator's responsibility that the
          aforementioned requirement is met.
---- cut here ----

Any comments will be very appreciated.

Thanks!

Best regards,
Fernando & Will




-------- Forwarded Message --------
Subject: New Version Notification for
draft-ietf-dhc-stable-privacy-addresses-01.txt
Date: Wed, 18 Feb 2015 00:29:04 -0800
From: internet-drafts@ietf.org
To: Fernando Gont <fgont@si6networks.com>, Will Liu (Shucheng)
<liushucheng@huawei.com>, Fernando Gont <fgont@si6networks.com>,
Shucheng LIU (Will) <liushucheng@huawei.com>


A new version of I-D, draft-ietf-dhc-stable-privacy-addresses-01.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-ietf-dhc-stable-privacy-addresses
Revision:	01
Title:		A Method for Generating Semantically Opaque Interface
Identifiers with Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Document date:	2015-02-18
Group:		dhc
Pages:		9
URL:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-stable-privacy-addresses-01.txt
Status:
https://datatracker.ietf.org/doc/draft-ietf-dhc-stable-privacy-addresses/
Htmlized:
http://tools.ietf.org/html/draft-ietf-dhc-stable-privacy-addresses-01
Diff:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-stable-privacy-addresses-01

Abstract:
   This document specifies a method for selecting IPv6 Interface
   Identifiers, to be employed by Dynamic Host Configuration Protocol
   for IPv6 (DHCPv6) servers when leasing non-temporary IPv6 addresses
   to DHCPv6 clients.  This method is a DHCPv6 server side algorithm,
   that does not require any updates to the existing DHCPv6
   specifications.  The aforementioned method results in stable
   addresses within each subnet, even in the presence of multiple DHCPv6
   servers or DHCPv6 server reinstallments.  It is a DHCPv6-variant of
   the method specified in RFC 7217 for IPv6 Stateless Address
   Autoconfiguration.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat





From nobody Wed Feb 18 03:32:25 2015
Return-Path: <fgont@si6networks.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 ACC5D1A87E2 for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 03:32:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 O6NFvWSK2fjc for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 03:32:21 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5C731A87E8 for <dhcwg@ietf.org>; Wed, 18 Feb 2015 03:32:18 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YO2rV-0006Wt-O5; Wed, 18 Feb 2015 12:32:14 +0100
Message-ID: <54E47156.3000100@si6networks.com>
Date: Wed, 18 Feb 2015 08:02:46 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/unkagcK6L_kf2iqaiFXcJnRAeJg>
Subject: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
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, 18 Feb 2015 11:32:23 -0000

Folks,

The current version of the I-D (-01, posted today), tries to implement
support for address ranges (as opposed to just prefixes) as follows:


       RID = F(IPV6_ADDR_HI | IPV6_ADDR_LOW | Client_DUID | IAID |
       Counter | secret_key)


       Where:

       RID:
          Random (but stable) Identifier

       IPV6_ADDR_HI:
          An IPv6 address specifying the upper boundary of the IPv6
          address pool from which the DHCPv6 server leases IPv6
          addresses.  It MUST be represented as a 128-bit unsigned
          integer in network byte order.

       IPV6_ADDR_LOW:
          An IPv6 address specifying the lower boundary of the IPv6
          address pool from which the DHCPv6 server leases IPv6
          addresses.  It MUST be represented as a 128-bit unsigned
          integer in network byte order.  If multiple servers operate on
          the same network to provide increased availability, all such
          DHCPv6 servers MUST be configured with the address range
          (i.e., the same IPV6_ADDR_HI and IPV6_ADDR_LOW parameters).
          It is the administrator's responsibility that the
          aforementioned requirement is met.
[....]

and then doing:

       IPV6_ADDRESS = IPV6_ADDR_LOW + RID % (IPV6_ADDR_HI -
       IPV6_ADDR_LOW + 1)

(where addresses are processed as 128-bit unsigned integers)


The potential "problem" with this approach is that in order to implement
this you need to do math with rather large numbers.

Maybe a simpler approach would be do do something along the lines of:

IPV6_ADDRESS[n]= IPV6_ADDR_LOW[n] + RID[n] % (IPV6_ADDR_H[n]-
                              IPV6_ADDR_LOW[n] +1)

Where we process IPv6 addresses as an array of 16-bit integers -- and
hence should apply this expression for n= 4..7.

While this doesn't look so nice, as the expression in the current
version of the I-D, the advantage is that we don't need to d math with
"large" numbers, and also that the algorithm can support address ranges
for this sort: 2001:db8::0-ffff:1:2:10-50  (where we have specified
"ranges" for two 16-bit words, and hence the address pool will result in
a noncontiguous set of addresses).

(If you like this latter approach, there are a few other nits to be
discussed... but let's settle on the high-order bit first :-) )

Thoughts?

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Feb 18 06:47:45 2015
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 9E7211A8835 for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 06:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 eAQfTzSoIFO7 for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 06:47:39 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 179011A1B34 for <dhcwg@ietf.org>; Wed, 18 Feb 2015 06:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5537; q=dns/txt; s=iport; t=1424270859; x=1425480459; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ylwEDM+LuXjjbqaGAr9rXmdi1fmNtY2OufYmtcQsoBM=; b=Sv1O6QajNaCZWkdESMYy3a9jq6i5sPgNRWwO5+lncPRI+2bERuNLXS49 0h1IwxnUANFvzQG5sbE/vbjAcv8h0I1P3M9AVQoK0hZ7y7OF5IqXgZ+jU KrPnqk+yJ9S+Ywg+3tOo16aiv6X8Hrh+p9Pd5vgBEGDcMHMqgVH5p5WJh I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BaBQASpeRU/4kNJK1bgwZSWgTCTgqFcQKBHEMBAQEBAQF8hAwBAQEEAQEBNzQDFAQCAQgOAwQBAQsUCQcnCxQJCAIEARIIiCcN0jkBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIsPhBcmJhIGgxCBFAWNVoFthW+OM4gsIoF9BRyBUG+BA0F/AQEB
X-IronPort-AV: E=Sophos;i="5.09,602,1418083200"; d="scan'208";a="124660129"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-1.cisco.com with ESMTP; 18 Feb 2015 14:47:39 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1IElcA5015336 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Feb 2015 14:47:38 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Wed, 18 Feb 2015 08:47:38 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
Thread-Index: AQHQS26WGpYYq65EEUS0p0yvML6blpz2eEgA
Date: Wed, 18 Feb 2015 14:47:37 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9AC5C1@xmb-rcd-x04.cisco.com>
References: <54E47156.3000100@si6networks.com>
In-Reply-To: <54E47156.3000100@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.36.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6cpYu9U3y_PyIy1_WQfz_aj4quk>
Subject: Re: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
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, 18 Feb 2015 14:47:43 -0000

Hi:

There are servers that use full prefixes (i.e., can assign any addresses in=
 /64) - and I guess you'd say to use ADDR_HI of x:x:x:x:FFFF:FFFF:FFFF:FFFF=
 and ADDR_LOW of x:x:x:x:0:0:0:0? In these cases, the extra math is not req=
uired. (The above works for other prefix lengths too - just take the "lower=
 order" 128-length bits of the result).

And, for servers that have specific range (low to high), they will always h=
ave to do some "math". Also, I think it would be safe for most implementati=
ons to assume that doing this math with 64-bits is more than sufficient. Pr=
obably 32-bits is OK too, but that may not be as future proof :).

An interesting question then is whether to change from Prefix to IPV6_ADDR_=
HI and IPV6_ADDR_LOW in the first place? Why not just stick to using the pr=
efix that is in the RA (I would expect servers to know that since the confi=
guration is probably a prefix with range(s)). Then the "range" is only appl=
ied at the end.

Note also that:
- Ranges may not be contiguous. What if there are multiple ranges (i.e., 10=
 to 1000, 2000 to 3000)? This is why I think dropping the idea of start/end=
 range makes the most sense - just use the prefix.
- Ranges like this also have the interesting property that it breaks the id=
ea of "stable" addresses whenever a change to the range occurs - increasing=
 or decreasing the range will break stability.

Also, shouldn't the IA option type be part of the expression? While today w=
e have IA_NA and IA_TA and you probably don't want to do this for IA_TA, mi=
ght not hurt to include this in case there are other types developed in the=
 future? It probably isn't a big deal if we don't since that is less likely=
 to be the case.


An interesting question that might be asked is whether this work even needs=
 to be standardized. Also, what might happen with a DHCPv6 failover impleme=
ntation (in this case, it could be that the resulting address that is gener=
ated by this is not available to that server (assigned to partner) and so c=
ounter would have to be incremented and regenerate an address ... which cou=
ld happen multiple times).

If DHCPv6 is supposed to provide stable addresses, why not just have the se=
rver remember the addresses that it assigned to a specific client (or Clien=
t & IA)? Servers have to have state, so this is not that challenging. Sure,=
 you have to limit the time (otherwise you could build up a large amount of=
 state), but would you really want to have the same address after many mont=
hs?

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Fernando Gont
Sent: Wednesday, February 18, 2015 6:03 AM
To: dhcwg@ietf.org
Subject: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on addre=
ss ranges

Folks,

The current version of the I-D (-01, posted today), tries to implement
support for address ranges (as opposed to just prefixes) as follows:


       RID =3D F(IPV6_ADDR_HI | IPV6_ADDR_LOW | Client_DUID | IAID |
       Counter | secret_key)


       Where:

       RID:
          Random (but stable) Identifier

       IPV6_ADDR_HI:
          An IPv6 address specifying the upper boundary of the IPv6
          address pool from which the DHCPv6 server leases IPv6
          addresses.  It MUST be represented as a 128-bit unsigned
          integer in network byte order.

       IPV6_ADDR_LOW:
          An IPv6 address specifying the lower boundary of the IPv6
          address pool from which the DHCPv6 server leases IPv6
          addresses.  It MUST be represented as a 128-bit unsigned
          integer in network byte order.  If multiple servers operate on
          the same network to provide increased availability, all such
          DHCPv6 servers MUST be configured with the address range
          (i.e., the same IPV6_ADDR_HI and IPV6_ADDR_LOW parameters).
          It is the administrator's responsibility that the
          aforementioned requirement is met.
[....]

and then doing:

       IPV6_ADDRESS =3D IPV6_ADDR_LOW + RID % (IPV6_ADDR_HI -
       IPV6_ADDR_LOW + 1)

(where addresses are processed as 128-bit unsigned integers)


The potential "problem" with this approach is that in order to implement
this you need to do math with rather large numbers.

Maybe a simpler approach would be do do something along the lines of:

IPV6_ADDRESS[n]=3D IPV6_ADDR_LOW[n] + RID[n] % (IPV6_ADDR_H[n]-
                              IPV6_ADDR_LOW[n] +1)

Where we process IPv6 addresses as an array of 16-bit integers -- and
hence should apply this expression for n=3D 4..7.

While this doesn't look so nice, as the expression in the current
version of the I-D, the advantage is that we don't need to d math with
"large" numbers, and also that the algorithm can support address ranges
for this sort: 2001:db8::0-ffff:1:2:10-50  (where we have specified
"ranges" for two 16-bit words, and hence the address pool will result in
a noncontiguous set of addresses).

(If you like this latter approach, there are a few other nits to be
discussed... but let's settle on the high-order bit first :-) )

Thoughts?

Thanks!

Best regards,
--=20
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Wed Feb 18 08:10:43 2015
Return-Path: <fgont@si6networks.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 2F47C1A8852 for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 08:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 D7JPVWF4QSEL for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 08:10:37 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CEA11A1B34 for <dhcwg@ietf.org>; Wed, 18 Feb 2015 08:10:37 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YO7Cl-0007rO-2p; Wed, 18 Feb 2015 17:10:28 +0100
Message-ID: <54E4B956.4090106@si6networks.com>
Date: Wed, 18 Feb 2015 13:09:58 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <54E47156.3000100@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1C9AC5C1@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1C9AC5C1@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/8WnxAS-LDuQzg47TUmH8s6VHR38>
Subject: Re: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
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, 18 Feb 2015 16:10:40 -0000

Hi, Bernie,

Thanks so much for your prompt response! Please find my comments in-line....

On 02/18/2015 11:47 AM, Bernie Volz (volz) wrote:
> 
> There are servers that use full prefixes (i.e., can assign any
> addresses in /64) - and I guess you'd say to use ADDR_HI of
> x:x:x:x:FFFF:FFFF:FFFF:FFFF and ADDR_LOW of x:x:x:x:0:0:0:0?

Exactly. Actually, they could use the prefix notation in the
configuration file, and it would be the DHCPv6 server software
converting from prefix notation to low/hi.



> In these
> cases, the extra math is not required. 

You mean the low/hi thing?



> And, for servers that have specific range (low to high), they will
> always have to do some "math". Also, I think it would be safe for
> most implementations to assume that doing this math with 64-bits is
> more than sufficient. 

You mean to assume that the upper 64 bits (the prefix) is the same for
low ad hi?


> An interesting question then is whether to change from Prefix to
> IPV6_ADDR_HI and IPV6_ADDR_LOW in the first place? Why not just stick
> to using the prefix that is in the RA (I would expect servers to know
> that since the configuration is probably a prefix with range(s)).
> Then the "range" is only applied at the end.

Because if what you specify is really a range, I'm not sure that the
prefix is meaningful anymore?



> Note also that: - Ranges may not be contiguous. What if there are
> multiple ranges (i.e., 10 to 1000, 2000 to 3000)? This is why I think
> dropping the idea of start/end range makes the most sense - just use
> the prefix. - Ranges like this also have the interesting property
> that it breaks the idea of "stable" addresses whenever a change to
> the range occurs - increasing or decreasing the range will break
> stability.

This later point is very interesting indeed, and makes strong case for
using the Prefix in the hash, rather than the range. How about employing
the Prefix in the hash function (as in the previous versions of the
I-D), and then "adjusting" the selected address to the hi/lo range as
follows:


if(IID < IID_low){
	IID=IID_low + iid % (IID_hi - IID_low + 1);
}
else if(IID > IID_hi){
	IID= IID_low + IID_hi  % (IID_hi - IID_low + 1);
}


?


> Also, shouldn't the IA option type be part of the expression? While
> today we have IA_NA and IA_TA and you probably don't want to do this
> for IA_TA, might not hurt to include this in case there are other
> types developed in the future? It probably isn't a big deal if we
> don't since that is less likely to be the case.

In this case it would be kind of redundant, since the spec itself says
that it's the IA_NA that we include (i.e., the type is implicit).
However, I agree that this wouldn't hurt.

Please let me know if you think it would be great to apply the suggested
change, and we'll do it (meanwhile maybe others can weigh in?).


> An interesting question that might be asked is whether this work even
> needs to be standardized. 

Well, you do need a spec if you need to achive the goals set forth in
this document. Note that e.g., we've specified port-number randomization
in RFC6056....



> Also, what might happen with a DHCPv6
> failover implementation (in this case, it could be that the resulting
> address that is generated by this is not available to that server
> (assigned to partner) and so counter would have to be incremented and
> regenerate an address ... which could happen multiple times).

Well, since the address space is supposed to be large, collissions
should be pretty low.

But... maybe we should add a note regarding the address range? i.e.
"don't make it too small ore collisions might happen".



> If DHCPv6 is supposed to provide stable addresses, why not just have
> the server remember the addresses that it assigned to a specific
> client (or Client & IA)? Servers have to have state, so this is not
> that challenging. Sure, you have to limit the time (otherwise you
> could build up a large amount of state), but would you really want to
> have the same address after many months?

Yes. Why would you want to change it? -- think ACLs, logging, etc.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Feb 18 10:07:24 2015
Return-Path: <internet-drafts@ietf.org>
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 4AC791A8BBD; Wed, 18 Feb 2015 10:07:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ALbO-YU6pbzu; Wed, 18 Feb 2015 10:07:22 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5DB1A8AB7; Wed, 18 Feb 2015 10:07:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218180722.14243.95784.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 10:07:22 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/A7FSwQjJTENLTGtE7W2gQdBGKCA>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-sedhcpv6-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Feb 2015 18:07:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

        Title           : Secure DHCPv6
        Authors         : Sheng Jiang
                          Sean Shen
                          Dacheng Zhang
                          Tatuya Jinmei
	Filename        : draft-ietf-dhc-sedhcpv6-06.txt
	Pages           : 23
	Date            : 2015-02-18

Abstract:
   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) enables
   DHCPv6 servers to pass configuration parameters.  It offers
   configuration flexibility.  If not being secured, DHCPv6 is
   vulnerable to various attacks, particularly spoofing attacks.  This
   document analyzes the security issues of DHCPv6 and specifies a
   Secure DHCPv6 mechanism for communications between DHCPv6 clients and
   DHCPv6 servers.  This document provides a DHCPv6 client/server
   authentication mechanism based on sender's public/private key pairs
   or certificates with associated private keys.  The DHCPv6 message
   exchanges are protected by the signature option and the timestamp
   option newly defined in this document.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-sedhcpv6/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-sedhcpv6-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 18 10:07:34 2015
Return-Path: <internet-drafts@ietf.org>
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 9A4F21A8F4D; Wed, 18 Feb 2015 10:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 aK4qQla__RSQ; Wed, 18 Feb 2015 10:07:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0F11A8AC9; Wed, 18 Feb 2015 10:07:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <draft-ietf-dhc-sedhcpv6.all@ietf.org>, <dhcwg@ietf.org>, <dhc-chairs@ietf.org>, <tomasz.mrugalski@eti.pg.gda.pl>, <ted.lemon@nominum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218180722.14243.58464.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 10:07:22 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/iZ61SK58rbw6TBrd2ZlatK63ghI>
Subject: [dhcwg] New Version Notification - draft-ietf-dhc-sedhcpv6-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Feb 2015 18:07:25 -0000

A new version (-06) has been submitted for draft-ietf-dhc-sedhcpv6:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-sedhcpv6-06.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-sedhcpv6/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-sedhcpv6-06

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Wed Feb 18 10:07:35 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: expand-draft-ietf-dhc-sedhcpv6.all@virtual.ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id BE1971A9024; Wed, 18 Feb 2015 10:07:25 -0800 (PST)
X-Original-To: xfilter-draft-ietf-dhc-sedhcpv6.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-dhc-sedhcpv6.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4F21A8F4D; Wed, 18 Feb 2015 10:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 aK4qQla__RSQ; Wed, 18 Feb 2015 10:07:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0F11A8AC9; Wed, 18 Feb 2015 10:07:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <draft-ietf-dhc-sedhcpv6.all@ietf.org>, <dhcwg@ietf.org>, <dhc-chairs@ietf.org>, <tomasz.mrugalski@eti.pg.gda.pl>, <ted.lemon@nominum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218180722.14243.58464.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 10:07:22 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/iZ61SK58rbw6TBrd2ZlatK63ghI>
Subject: [dhcwg] New Version Notification - draft-ietf-dhc-sedhcpv6-06.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Feb 2015 18:07:26 -0000

A new version (-06) has been submitted for draft-ietf-dhc-sedhcpv6:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-sedhcpv6-06.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-sedhcpv6/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-sedhcpv6-06

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Wed Feb 18 10:18:31 2015
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 5C5791A0016 for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 10:18:30 -0800 (PST)
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 sD-943HCx-cM for <dhcwg@ietfa.amsl.com>; Wed, 18 Feb 2015 10:18:29 -0800 (PST)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF3351A0007 for <dhcwg@ietf.org>; Wed, 18 Feb 2015 10:18:28 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id k14so2823522wgh.3 for <dhcwg@ietf.org>; Wed, 18 Feb 2015 10:18:27 -0800 (PST)
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:content-type; bh=BhOOih1hfg12g5uyXDdTr1ZvIk2TBBeLYoAcvwBDz4M=; b=RQi/N9UFQcDJlJn7gHv2KuJIKsFHhd3ayagwTFu7pMd8SOdQSvIlZs6/gidaOIsivI Guz9dykChj+63YYs4Ieg7uyntKj7EAyGGDQjwQzpdlZdDGwX/I5AUey7Gdj25N2SRsIw tqLrRGqAih4mY/cbGHlZWhYOxCeNWLYvrjhEj8bwxobrVLwcon84mHkoV9PlKSMJN6+k NiR3dg3NNXB/PpuJpPgXkpaYK69oJEjd6CE6QiuXOZlei8d6pBF1XacA/0wXjAkyEMig oU/CuBDAXaw1twtyjSQaoHCtMRAkeSQm5yI67PzmYboIFEJ10sC2u2/4gMpVVSBYypYA yptg==
MIME-Version: 1.0
X-Received: by 10.180.108.178 with SMTP id hl18mr2512322wib.92.1424283507492;  Wed, 18 Feb 2015 10:18:27 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Wed, 18 Feb 2015 10:18:27 -0800 (PST)
In-Reply-To: <20150218180722.14243.95784.idtracker@ietfa.amsl.com>
References: <20150218180722.14243.95784.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 10:18:27 -0800
X-Google-Sender-Auth: YP3lHw4CSHlvCItENKR3p2zBdK4
Message-ID: <CAJE_bqe-G1Gj3JjWJZ7CqBd7DXREeGppj8N2jpkDEVj7r+s7hg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/5N4QvqlyYdoV8GaDdGKjrp8fGwY>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-sedhcpv6-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, 18 Feb 2015 18:18:30 -0000

At Wed, 18 Feb 2015 10:07:22 -0800,
internet-drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.
>
>         Title           : Secure DHCPv6
>         Authors         : Sheng Jiang
>                           Sean Shen
>                           Dacheng Zhang
>                           Tatuya Jinmei
>     Filename        : draft-ietf-dhc-sedhcpv6-06.txt
>     Pages           : 23
>     Date            : 2015-02-18

I've submitted this version on behalf of other authors (they are on
holidays).  This version includes updates to address some of the AD review
comments by Ted.  It doesn't address one major issue: what to do with
the applicability section.  I'll initiate a discussion for that on
this list.

--
JINMEI, Tatuya


From nobody Wed Feb 18 14:35:38 2015
Return-Path: <tomasz.mrugalski@eti.pg.gda.pl>
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 052861A1AF4; Wed, 18 Feb 2015 14:35:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 6huYkqGJuM1n; Wed, 18 Feb 2015 14:35:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B5D1A0102; Wed, 18 Feb 2015 14:35:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Tomek Mrugalski" <tomasz.mrugalski@eti.pg.gda.pl>
To: <ted.lemon@nominum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218223535.19832.16514.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 14:35:35 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/3GztJi2jXUXDuLRMmGtDQ9ReccE>
Cc: draft-ietf-dhc-dhcpv6-stateful-issues@ietf.org, dhc-chairs@ietf.org, dhc-chairs@tools.ietf.org, draft-ietf-dhc-dhcpv6-stateful-issues.shepherd@ietf.org, tomasz.mrugalski@eti.pg.gda.pl, iesg-secretary@ietf.org, draft-ietf-dhc-dhcpv6-stateful-issues.ad@ietf.org, dhcwg@ietf.org
Subject: [dhcwg] Publication has been requested for draft-ietf-dhc-dhcpv6-stateful-issues-11
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Feb 2015 22:35:37 -0000

Tomek Mrugalski has requested publication of draft-ietf-dhc-dhcpv6-stateful-issues-11 as Proposed Standard on behalf of the DHC working group.

Please verify the document's state at http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/


From nobody Wed Feb 18 14:48:54 2015
Return-Path: <iesg-secretary@ietf.org>
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 99D9E1A1B82; Wed, 18 Feb 2015 14:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 3OYnYcey-PzM; Wed, 18 Feb 2015 14:48:51 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 287901A0113; Wed, 18 Feb 2015 14:48:51 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20150218224851.2888.39053.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 14:48:51 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/3oHqX43TbXtC8G9jsrmdxRI9hOk>
Cc: dhcwg@ietf.org
Subject: [dhcwg] Last Call: <draft-ietf-dhc-dhcpv6-stateful-issues-11.txt> (Issues and Recommendations with Multiple Stateful DHCPv6 Options) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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, 18 Feb 2015 22:48:52 -0000

The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'Issues and Recommendations with Multiple Stateful DHCPv6 Options'
  <draft-ietf-dhc-dhcpv6-stateful-issues-11.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-03-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
   specification defined two stateful options, IA_NA and IA_TA, but did
   not anticipate the development of additional stateful options.
   DHCPv6 Prefix Delegation added the IA_PD option, which is stateful.
   Applications that use IA_NA and IA_PD together have revealed issues
   that need to be addressed.  This document updates RFC 3315 and RFC
   3633 to address these issues.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-stateful-issues/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Thu Feb 19 10:18:54 2015
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 BDBD91A6FF3 for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 10:18:52 -0800 (PST)
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 GbwmHGPDvTuZ for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 10:18:51 -0800 (PST)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBBFC1A7033 for <dhcwg@ietf.org>; Thu, 19 Feb 2015 10:18:47 -0800 (PST)
Received: by mail-wi0-f181.google.com with SMTP id r20so11127654wiv.2 for <dhcwg@ietf.org>; Thu, 19 Feb 2015 10:18:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=r5oFEc1Y9x9xTlsqYNaot0/5autt8QR6qrKJiBnZODM=; b=xzdcmNhimjW0rNOJjmc2m+yZSpGOA6/27vvrdzlDuY6ZRvDuS5RgJijSkXwvzXkrQY K0hVbrg/07Yk3QAgxY5nEVlxzYVpgYOhx2pzfrNsk3gKOb32JaOv0xoMn6AmRsG2/Jqt Y5DxOVq8IQLOJyWAingVphtaABG2TWnvivjnTohRN90rkWYQZhMjAMB+0HqaquScGPkU bAmbqxe3MyQJ76b2FQ4QY0jVNw0rMg7Hsi3zUaFJ/qRrZEtHI6D2MtMFe0BpyG3iXPqB TuY9dqTq6ieICsngGJNkVStBF5ovHx+dJHffEDVQXzaGCfc6B0DXpikzUGw4GBBtTaQ4 L3EA==
MIME-Version: 1.0
X-Received: by 10.181.11.136 with SMTP id ei8mr12993600wid.10.1424369926189; Thu, 19 Feb 2015 10:18:46 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Thu, 19 Feb 2015 10:18:46 -0800 (PST)
Date: Thu, 19 Feb 2015 10:18:46 -0800
X-Google-Sender-Auth: qoPngyMkGURtm6mpuUEWe7DvyHU
Message-ID: <CAJE_bqf7JDrSqpJR-FVj1QWPCSaO0Dpkf8CxFwoUA+cFpMZxaA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/SiJlkDgKHdAXSnDx7c7HioQdgEU>
Subject: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 19 Feb 2015 18:18:52 -0000

This is my attempt of addressing the AD review comments on the
"Deployment Consideration" section of draft-ietf-dhc-sedhcpv6.

I begin with my own message in a previous thread on this topic:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg16211.html

Quoting Ted:

> In my mind, the answer to this is that at present no mechanism
> exists for security DHCP messages between servers and clients that
> does not have a serious key distribution problem.

I see this is a valid problem statement.

> By using public-key-based authentication, we provide a mechanism for
> securing such messages that can be reasonably deployed without the
> key distribution problems inherent in the shared-secret-based
> authentication mechanism specified in RFC 3315, either using some
> form of PKI or else Trust-on-first-use (TOFU).

I also see sedhcpv6 would be a reasonable solution for that problem in
the case of authenticating the server and messages from the server at
a client.  I can personally accept the solution without a specific use
case for this pair of problem-solution.  But I guess we could also
provide some feasible use case if we want to address a previous
inquiry from Ralph:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15528.html

I think most of the controversy exists in authenticating clients at a
server.  First off, it's not clear whether this is a valid solution to
the stated problem: "a mechanism for DHCP security that does not have
a serious key distribution problem".  Unlike the case of
authenticating a server, clients are generally more arbitrary, and
it's not clear (to me) whether/how we can manage certificates of these
clients without "a key distribution problem"; we could install each
client's public key or certificate by hand, but that's actually a "key
distribution problem" itself, not a solution.  And, depending on the
expected use case (which is also not clear and we can only provide
speculation), TOFU is not feasible in this case.

If the protocol can be completely independent from these issues, it
might make sense to publish the protocol part first.  But I suspect
that if and when we figure out these points the result will affect
protocol details.  Or we might even find that this kind of security
mechanism is not a viable solution to the stated problem in the end.
That's why I requested we first clarify exactly what kind of problem
this mechanism can solve and how it does so.  The section that
explains possible use cases is an attempt to address that concern.
But, according to the review feedback and the followup thread, that
attempt seemed to fail, at least for the case of authenticating
clients.

So my question to the wg would be: "whether it's okay to publish a
mechanism with details of the case of authenticating clients without
knowing specially how it's used or whether it really solves 'key
distribution problems'".  If the answer is "Yes", our next step would
be remove the use case section and move it forward.

My personal answer is "no, it's not okay", and I have a proposal that
might address my own concern and can still publish something useful
without much delay.  But to keep the discussion more focused I'll
defer it to a separate message.

--
JINMEI, Tatuya


From nobody Thu Feb 19 10:20:40 2015
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 A3EBE1A86F3 for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 10:20:39 -0800 (PST)
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 QInYlJoFha7G for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 10:20:38 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4E3B1A797C for <dhcwg@ietf.org>; Thu, 19 Feb 2015 10:20:37 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so11091980wid.5 for <dhcwg@ietf.org>; Thu, 19 Feb 2015 10:20:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=wV/M+zCW0CsQ8Ns7Sl0y+DWjYhEDoWtn1VAjbBa9HN4=; b=Gm30YHtyzp1WAllSiMsy5dhHXVnYkMfzzjHmCa9/ADl5Acg/LleZ2ogZDcgHNwB31o dDvv81dCFNSbuf6ur5OkvExnwWtqtjkaFswQsh+TPr+8sEFHpRB/cfQDepUQFdQB2Um1 gGiYGKSdh5XRWnkYTW0KFtWPtDNa3vqmczVELP4v9li5uH/ZOpcusxNnZQUYFOmqPb+g gOb7C1+n/E/Y6aY/de/fiSgV0x80CDEQT32GtMR/1p7uqCKO797bDes1lrFe5eklpJxb 9koSFpapX7OiCZiLhNSvnn/QkLLPHEHcQHuSSs3s+ay7fY31xeO5RJKbdg/a8Nf9QMgt BNaA==
MIME-Version: 1.0
X-Received: by 10.180.108.178 with SMTP id hl18mr12213119wib.92.1424370036370;  Thu, 19 Feb 2015 10:20:36 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Thu, 19 Feb 2015 10:20:36 -0800 (PST)
Date: Thu, 19 Feb 2015 10:20:36 -0800
X-Google-Sender-Auth: 9-K075Qt5ysvzUa_y8_7xysmZOo
Message-ID: <CAJE_bqcsJOg0M_GXGtLSZMCGMmNJKcpRk-YD2HFVkX-roY5EWw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/c55A_ug8l7Xy2RrHCbI675JayFE>
Subject: [dhcwg] proposal: make draft-ietf-dhc-sedhcpv6 more client-side centric
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: Thu, 19 Feb 2015 18:20:39 -0000

As a followup to my previous message, this is my personal proposal for
the "use case" issue of draft-ietf-dhc-sedhcpv6.  This is mostly
self-contained, but it's probably better to read the previous message
first.

As I stated in the previous message, I think the main issue in this
sense is about authenticating clients at a server.  In my
understanding, it's much less controversial for the case of
authenticating servers.

So my basic point of the proposal is to make this document more focus
on authenticating servers, and describe in more detail what's the
problem and how the proposed mechanism solves it.  We generally leave
authenticating clients beyond the scope of this document, and don't
describe details specific to that case.

More specifically,

- Revise Section 1 (Introduction) and 3 (Overview) so they will more
  focus on authenticating servers.  Give a more detailed problem
  statement in either Section 1 or 3, with the explanation of how
  sedhcpv6 solves it.  Possible use cases (if they are still
  considered useful and less controversial) would probably belong
  here, too.
- In Section 1, declare the case of authenticating clients is beyond
  the scope of this document, even if clients can send some of the
  security options to the server and the document would describe how
  servers would handle it to the extent they are necessary for the
  main topic.
- Revise Section 6 (rules and behaviors) so it concentrates on the
  main use case.  In particular, since client authentication is not
  in the scope, the server would basically only use the received
  security options as a signal for using the mechanism and to know the
  algorithm the client wants to use.  Further details would probably
  be beyond the scope of the doc.
- Remove Section 7
- Adjust Section 8 to match the sense of the focus (e.g., remove any
  note specific to the case of authenticating clients).

This is closer to option #3 I showed in a previous message:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg16211.html

But this revised proposal does not explicitly limit the use cases,
just saying some points are out of scope if we are not certain about
how/why for them.  This way we can avoid sending the wrong signal that
this mechanism solves issues for cases where we don't know if it
really does, and avoid wasting people's time to implement something
possibly useless or even harmful just because it's published in an
RFC.  Yet many of the protocol components will still remain, so a
well-educated die harder might try to implement and use it for the
open case and may really find it useful.  If that's the case, that
would be great, and we can then describe the rest of the details with
actual experiments.

--
JINMEI, Tatuya


From nobody Thu Feb 19 10:59:26 2015
Return-Path: <Ted.Lemon@nominum.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 240761A8783 for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 10:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 HEITJgDu38sT for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 10:59:21 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19AF61A797C for <dhcwg@ietf.org>; Thu, 19 Feb 2015 10:59:21 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 0DC97DA01E4 for <dhcwg@ietf.org>; Thu, 19 Feb 2015 18:59:21 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id F0C2F53E07C; Thu, 19 Feb 2015 10:59:20 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 19 Feb 2015 10:59:20 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqf7JDrSqpJR-FVj1QWPCSaO0Dpkf8CxFwoUA+cFpMZxaA@mail.gmail.com>
Date: Thu, 19 Feb 2015 13:58:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <DCD0EBE2-3CF0-47F4-BCC1-82D73DD44277@nominum.com>
References: <CAJE_bqf7JDrSqpJR-FVj1QWPCSaO0Dpkf8CxFwoUA+cFpMZxaA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/x7ewAn7QLigx2LGyFXTlC2cqR2k>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 19 Feb 2015 18:59:22 -0000

On Feb 19, 2015, at 1:18 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>  Unlike the case of
> authenticating a server, clients are generally more arbitrary, and
> it's not clear (to me) whether/how we can manage certificates of these
> clients without "a key distribution problem"; we could install each
> client's public key or certificate by hand, but that's actually a "key
> distribution problem" itself, not a solution.

The client generates the key, so there's no distribution problem.   The =
server gets the public key with the message, and can retain it for =
future use.   Establishing a trust relationship for that key is out of =
scope.   Likely it would be done using some kind of HTTP-based =
registration process using a captive portal.

The one concern I have with the protocol as currently proposed and as it =
relates to this flow is that the client may wish to present different =
keys to different servers, and may wish to defer presenting any key at =
all until it has seen and validated the server's identity.


From nobody Thu Feb 19 11:03:13 2015
Return-Path: <Ted.Lemon@nominum.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 DB7A51A0040 for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 11:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 dV2_9eC7nJ8C for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 11:03:07 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BEF21A0013 for <dhcwg@ietf.org>; Thu, 19 Feb 2015 11:03:07 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 20E74DA018F for <dhcwg@ietf.org>; Thu, 19 Feb 2015 19:03:07 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 10CDF53E07C; Thu, 19 Feb 2015 11:03:07 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 19 Feb 2015 11:03:06 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqcsJOg0M_GXGtLSZMCGMmNJKcpRk-YD2HFVkX-roY5EWw@mail.gmail.com>
Date: Thu, 19 Feb 2015 14:02:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <E588E08B-540C-4B65-874E-FF38D7B594EF@nominum.com>
References: <CAJE_bqcsJOg0M_GXGtLSZMCGMmNJKcpRk-YD2HFVkX-roY5EWw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/enE3BIscl0ljV_vniV8ttkSPSkQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] proposal: make draft-ietf-dhc-sedhcpv6 more client-side centric
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: Thu, 19 Feb 2015 19:03:12 -0000

On Feb 19, 2015, at 1:20 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> Revise Section 1 (Introduction) and 3 (Overview) so they will more
>  focus on authenticating servers.

I am hugely uncomfortable with this proposal.

The whole problem with the document as I see it is that it treats =
clients and servers as having distinct security models, when we do not =
actually know what security model will be used.   I don't mean to say =
that clients and servers won't have distinct security models, but we =
don't know what those security models will be.

This appears to me to be a classic example of the "mechanism, not =
policy" philosophy that the Athena project used to follow.   We are =
providing a mechanism here.   How it will used appears to me to be out =
of scope at present.


From nobody Thu Feb 19 14:16:13 2015
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 E2BD91A0379 for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 14:16:02 -0800 (PST)
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 WjiUKSAeE3Ls for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 14:16:01 -0800 (PST)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F40DF1A036F for <dhcwg@ietf.org>; Thu, 19 Feb 2015 14:15:59 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id hi2so51249561wib.4 for <dhcwg@ietf.org>; Thu, 19 Feb 2015 14:15:58 -0800 (PST)
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=A6DuxW3AlgPIoYAjwTaC8bMka119Ga1zNW1nFLe4HZA=; b=Ty+4oHxqH/axn2ujTOXytr9vZrkNYnztNxHai9gqjK+UCK6cdprnAaTkSCSTq/Bs2n EJGUvx+RZNis5cdlvDUNc6fJHi8bJBFA+X5lIbg30kli27I+FGvmL8jKXM/tOP8PoPsd dt2SHG7YlCkCo5IKQ5Yash7AIDUaxNXx6GZZ1KsJu6Is4SUm01zICMBiVKM2wMdyiNUO GwnTxNx9naNBTmQ1hHeKGgWiVQXniqv6+Quz9DlQnhiFQQ7VimD8THdlkRVcGOepyE58 97veiVsv3IbDBcddwhe/PQ8uj8gtZ9zfOK9qnr1BKAHMcAGKHwlQ/OFgCaj6ev+9xFnX MiSw==
MIME-Version: 1.0
X-Received: by 10.194.22.6 with SMTP id z6mr12783675wje.146.1424384158798; Thu, 19 Feb 2015 14:15:58 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Thu, 19 Feb 2015 14:15:58 -0800 (PST)
In-Reply-To: <E588E08B-540C-4B65-874E-FF38D7B594EF@nominum.com>
References: <CAJE_bqcsJOg0M_GXGtLSZMCGMmNJKcpRk-YD2HFVkX-roY5EWw@mail.gmail.com> <E588E08B-540C-4B65-874E-FF38D7B594EF@nominum.com>
Date: Thu, 19 Feb 2015 14:15:58 -0800
X-Google-Sender-Auth: wUdp3OHxOw9Mk1WmaOBqN65IHQY
Message-ID: <CAJE_bqdARhHbmjyc-3Cw3E3pd0QKyFewOtM2t+OC3aM+Nm+g9g@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/CJVQYDANPZZffpPWA6w9l4lb2Rs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] proposal: make draft-ietf-dhc-sedhcpv6 more client-side centric
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: Thu, 19 Feb 2015 22:16:03 -0000

At Thu, 19 Feb 2015 14:02:32 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > Revise Section 1 (Introduction) and 3 (Overview) so they will more
> >  focus on authenticating servers.
>
> I am hugely uncomfortable with this proposal.
[...]
> This appears to me to be a classic example of the "mechanism, not policy" philosophy that the Athena project used to follow.   We are providing a mechanism here.   How it will used appears to me to be out of scope at present.

Hmm, so it looks like we have to agree to disagree on this fundamental
point:-)

>> If the protocol can be completely independent from these issues, it
>> might make sense to publish the protocol part first.  But I suspect
>> that if and when we figure out these points the result will affect
>> protocol details.  Or we might even find that this kind of security
>> mechanism is not a viable solution to the stated problem in the end.
>> That's why I requested we first clarify exactly what kind of problem
>> this mechanism can solve and how it does so.  The section that
>> explains possible use cases is an attempt to address that concern.
>> But, according to the review feedback and the followup thread, that
>> attempt seemed to fail, at least for the case of authenticating
>> clients.

>> So my question to the wg would be: "whether it's okay to publish a
>> mechanism with details of the case of authenticating clients without
>> knowing specially how it's used or whether it really solves 'key
>> distribution problems'".  If the answer is "Yes", our next step would
>> be remove the use case section and move it forward.

I'll see what's the latest consensus of the wg on this question at the
moment.

--
JINMEI, Tatuya


From nobody Thu Feb 19 15:25:06 2015
Return-Path: <Francis.Dupont@fdupont.fr>
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 3040F1A1A11 for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 15:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.162
X-Spam-Level: 
X-Spam-Status: No, score=-0.162 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 I1K98BWLSR0m for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 15:25:04 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C41D61A1A1D for <dhcwg@ietf.org>; Thu, 19 Feb 2015 15:25:03 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t1JNKpVY001185; Fri, 20 Feb 2015 00:20:51 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201502192320.t1JNKpVY001185@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-reply-to: Your message of Thu, 19 Feb 2015 13:58:46 EST. <DCD0EBE2-3CF0-47F4-BCC1-82D73DD44277@nominum.com> 
Date: Fri, 20 Feb 2015 00:20:51 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/xgxh5DwzdkTWsLuMsW-FUoPQd3w>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 19 Feb 2015 23:25:05 -0000

 In your previous mail you wrote:

>>  JINMEI wrote:
>> Unlike the case of authenticating a server, clients are generally
>> more arbitrary, and it's not clear (to me) whether/how we can manage
>> certificates of these clients without "a key distribution problem";
>> we could install each client's public key or certificate by hand,
>> but that's actually a "key distribution problem" itself, not a
>> solution.

> The client generates the key, so there's no distribution problem.
> The server gets the public key with the message, and can retain it
> for future use.  Establishing a trust relationship for that key is
> out of scope.  Likely it would be done using some kind of HTTP-based
> registration process using a captive portal.

=> as far as I know the proposed client->server authentication uses
(X.509 public key) certificates, and TOFU is only one of the possible
options. Nevertheless I agree the idea to put the "key distribution
problem" out of scope as it is simply the only option if we want to
get the document adopted one day. Note in many DHCPv6 deployments
clients are already registered in the server config(s) so there is
no issue with associating each client entry with a short list of
certificates in this config.

> The one concern I have with the protocol as currently proposed and
> as it relates to this flow is that the client may wish to present
> different keys to different servers, and may wish to defer
> presenting any key at all until it has seen and validated the
> server's identity.

=> this can lead to a chicken and egg issue, in particular if someone
adds privacy consideration. I suggest to target first easy cases, even
they have little technical incentive...

Regards

Francis.Dupont@fdupont.fr


From nobody Thu Feb 19 18:23:52 2015
Return-Path: <Ted.Lemon@nominum.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 95ED01A1B6D for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 18:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 Y8SsPGrxdxAf for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 18:23:50 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 444D81A1B6B for <dhcwg@ietf.org>; Thu, 19 Feb 2015 18:23:50 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 21111DA0153 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 02:23:50 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DC57D53E07B; Thu, 19 Feb 2015 18:23:49 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 19 Feb 2015 18:23:50 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201502192320.t1JNKpVY001185@givry.fdupont.fr>
Date: Thu, 19 Feb 2015 21:23:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <92978990-CA64-4B73-BED3-050042DAE95B@nominum.com>
References: <201502192320.t1JNKpVY001185@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/4z166hRguosgi3X5520drpWELkU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 02:23:51 -0000

On Feb 19, 2015, at 6:20 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:
> as far as I know the proposed client->server authentication uses
> (X.509 public key) certificates, and TOFU is only one of the possible
> options.

Right, but I think there is almost no chance that this would be deployed =
in practice, which was one of my objections to the proposal.   What =
value does it add to have a PKI-authenticated key on the client?

> =3D> this can lead to a chicken and egg issue, in particular if =
someone
> adds privacy consideration. I suggest to target first easy cases, even
> they have little technical incentive...

What's the chicken/egg issue?   Do you mean because the server is =
allocating a scarce resource, and would want the client to authenticate =
first?


From nobody Fri Feb 20 07:27:15 2015
Return-Path: <Francis.Dupont@fdupont.fr>
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 3E25C1A6FED for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 07:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 JcUlzj3Rpd8D for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 07:27:13 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E39F31A87A9 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 07:27:05 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t1KFMp1W060406; Fri, 20 Feb 2015 16:22:51 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201502201522.t1KFMp1W060406@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-reply-to: Your message of Thu, 19 Feb 2015 21:23:09 EST. <92978990-CA64-4B73-BED3-050042DAE95B@nominum.com> 
Date: Fri, 20 Feb 2015 16:22:51 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/QOzXgk_OsKV8XDmHzaSiQIh0Mqg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 15:27:14 -0000

 In your previous mail you wrote:

>  On Feb 19, 2015, at 6:20 PM, Francis Dupont <Francis.Dupont@fdupont.fr> 
>  wrote:
>  > as far as I know the proposed client->server authentication uses
>  > (X.509 public key) certificates, and TOFU is only one of the possible
>  > options.
>  
>  Right, but I think there is almost no chance that this would be deployed
>  in practice, which was one of my objections to the proposal.

=> I can't remember if your objection is about public key vs. certificate.
If it is the case they are in fact equivalent as a certificate embeds
a public key. Note in the server->client way a certificate has a little
added value because a bootstrapping client has by definition no access to
a PKI.
If your objection is about the whole proposal then there is no required
PKI in all cases. For instance you can add to a static config (a server
config with a dedicated entry per client, clients with static identity)
the keying material. I agree DHCP doesn't bring a lot but I know
many places where DHCPv6 is used just because DHCPv4 was and there
is no good reason to change something which proved to work well.

>  What value does it add to have a PKI-authenticated key on the client?

=> IMHO none for the "PKI-authenticated" but there is one for
the "authenticated" by TOFU or static config.

>  > => this can lead to a chicken and egg issue, in particular if someone
>  > adds privacy consideration. I suggest to target first easy cases, even
>  > they have little technical incentive...
>  
>  What's the chicken/egg issue?

=> the server discards packets sent by the client without authentication
options, the client doesn't know which authentication to use so uses none.

> Do you mean because the server is allocating a scarce resource, and
> would want the client to authenticate first?

=> yes with any kind of reasons/policies for the server.
The privacy point is from the fact authentication, in particular
a certificate, can reveal a lot about the client. But someone has
to do the first step.

Thanks

Francis.Dupont@fdupont.fr


From nobody Fri Feb 20 08:42:34 2015
Return-Path: <Ted.Lemon@nominum.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 51BCD1A0187 for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 08:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 ZVQ0-j8wSj32 for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 08:42:31 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 764031A0167 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 08:42:31 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 34D15DA01F8 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 16:42:31 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id EFA4953E07B; Fri, 20 Feb 2015 08:42:30 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 20 Feb 2015 08:42:30 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201502201522.t1KFMp1W060406@givry.fdupont.fr>
Date: Fri, 20 Feb 2015 11:41:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <8461A1EA-866E-4487-90E2-17AFDCFF77D5@nominum.com>
References: <201502201522.t1KFMp1W060406@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/gtp4udRvS8Vqam_NCxr4nDRlv60>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 16:42:33 -0000

On Feb 20, 2015, at 10:22 AM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:
> =3D> I can't remember if your objection is about public key vs. =
certificate.
> If it is the case they are in fact equivalent as a certificate embeds
> a public key. Note in the server->client way a certificate has a =
little
> added value because a bootstrapping client has by definition no access =
to
> a PKI.

What you are saying seems to represent a fundamental misunderstanding of =
how PKI works and how it would make sense to use it.   Let me try to =
explain:

A cert from client to server makes no sense because certs are signed by =
CAs, and there's (at least at present) no way to automate that.   I'm =
not saying such a thing could never make sense, but I don't see how it =
adds value.   The use model for such a cert that I can imagine would be =
that a provider signs clients certs with a provider key during some =
initial registration process, and then the DHCP server just trusts all =
keys signed by the provider key.

But that doesn't make sense.   What most providers want is a one-to-one =
accounting model, and you don't need a cert for that--you just need to =
collect the client-generated key at registration time and mark it as =
allowed in a key database.   This means that later if the client doesn't =
pay the bill, you can mark it in the database as no longer allowed.   =
The DHCP server just checks in the database to see how the key is =
marked, and replies accordingly, directing non-allowed keys to a captive =
portal, and immediately allowing access for allowed keys.

And in the reverse direction, it _does_ make sense for the server's key =
to be signed by a PKI, for two reasons.   First, because of the way PKI =
works.   The x.509 PKI that is used by web browsers relies on the =
browser having a list of known roots, and if a cert's signature chain =
leads back to a known root, the cert is considered valid.   You need =
connectivity to check for revoked certs, but not otherwise.

The second reason this makes sense is that providers have =
infrastructure, and you don't want to have one key known to the client =
where the private key is stored on every piece of infrastructure in the =
provider network, because this means that the compromise of any one =
infrastructure node will compromise the entire network.   No, what you =
want is for the provider to have a key that it uses to sign =
infrastructure keys, and then you want each piece of infrastructure to =
have its own key signed with the provider key.   You want the provider =
key to be long-lived, and you want the infrastructure keys to be very =
short-lived, like maybe a week at most.   This way stealing an =
infrastructure key has limited value, and yet the client can reliably =
identify infrastructure keys as belonging to the provider.

So the use model that seems plausible to me is the exact opposite of =
what's currently described in the draft, and what you are describing =
here, Francis.

>> What value does it add to have a PKI-authenticated key on the client?
>=20
> =3D> IMHO none for the "PKI-authenticated" but there is one for
> the "authenticated" by TOFU or static config.

Right, and so there's no need for the client to send a cert in this =
case.

> =3D> the server discards packets sent by the client without =
authentication
> options, the client doesn't know which authentication to use so uses =
none.

This is easily fixed: have the server discard packets that allocate =
resources, but not discard solicit packets or information request =
packets.   The client then sends an unauthenticated solicit, and if it =
recognizes the server in the advertise, it sends an authenticated =
request.


From nobody Fri Feb 20 10:37:41 2015
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 1D2D61A00FD for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 10:37:40 -0800 (PST)
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 CQme69XNkTpU for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 10:37:38 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F4EE1A007A for <dhcwg@ietf.org>; Fri, 20 Feb 2015 10:37:38 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so4824302wid.5 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 10:37:36 -0800 (PST)
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=W6OrqcXZejjtmWbGg9XXyZx/ktKnpXu5ne10jtcdyVM=; b=vFkK631tpyWWQsuFhMqqQOuuPCukkZSap1mwe+WvNJHIkFDR6fnFZsXd6WyMGq7x2X 1rh8eJagDZaeBEUdczUU1E7pzpDmj2U3TlU68Q4BnGLlo5rFTPXGMsCSVjDlJgy31zSV /QIwLC2YEERhBkEt/ZfW+wjXyK/sQjVuwa7FPRxhXmBijj6Y2Lghv+TsnEXQtA6qjhGD mFyfXffgJz6szdAckvrReg2ygIgZDPCIXo2hthz+h0TuOkQXWlwhJqqBizOTSEQNNIPm NNxRcRoiF8wqhUR9KhyB1vH7TAfRM0Ony2D0JeFbin25njg+F7MJLVeeYsPYShXA8yXa d4Fw==
MIME-Version: 1.0
X-Received: by 10.194.22.6 with SMTP id z6mr20807576wje.146.1424457456889; Fri, 20 Feb 2015 10:37:36 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Fri, 20 Feb 2015 10:37:36 -0800 (PST)
In-Reply-To: <201502192320.t1JNKpVY001185@givry.fdupont.fr>
References: <DCD0EBE2-3CF0-47F4-BCC1-82D73DD44277@nominum.com> <201502192320.t1JNKpVY001185@givry.fdupont.fr>
Date: Fri, 20 Feb 2015 10:37:36 -0800
X-Google-Sender-Auth: ybxlSyln52_Ww8QDA9nPX8-pXI4
Message-ID: <CAJE_bqe7DMWabw_cnSdKThh-E5A=eM2vD6RruJTp5aGetoLhfw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/avwm9CbCeHuDjKGXHeh6Q_t0FFQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 18:37:40 -0000

At Fri, 20 Feb 2015 00:20:51 +0100,
Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

> => as far as I know the proposed client->server authentication uses
> (X.509 public key) certificates, and TOFU is only one of the possible
> options. Nevertheless I agree the idea to put the "key distribution
> problem" out of scope as it is simply the only option if we want to
> get the document adopted one day.

In case I wasn't clear, I didn't intend to insist the "key
distribution problem" should be fully solved before or in this
document.  But if we totally ignore it, we could end up publishing
something that doesn't soleve any new problem.  For example, if our
expected operation is to manually configure clients' public keys on a
server or via some imaginary "portal", the underlying security
mechanism doesn't have to be sedhcpv6; the plain-old RFC3315 security
protocol using a shared secret should suffice.  So, IMO, in order to
show this mechanism provides some new value we'll at least need to
provide some level of consideration on how the keys are securely
distributed and explain how the proposed security protocol (sedhcpv6)
along with the intended key distribution solves a new problem that
can't be solved with existing tools.

Aside from whether to add such consideration in the document, I've not
seen an argument in the case of authenticating "client->server" that
can answer this question of mine.  And, at least to me, it's
irresponsible to publish the result without even understanding it.

--
JINMEI, Tatuya


From nobody Fri Feb 20 13:03:05 2015
Return-Path: <Francis.Dupont@fdupont.fr>
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 C7DD41A8799 for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 13:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 qJEHRvK1IIyv for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 13:03:02 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84E2B1A879F for <dhcwg@ietf.org>; Fri, 20 Feb 2015 13:03:01 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t1KKwjKB080855; Fri, 20 Feb 2015 21:58:45 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201502202058.t1KKwjKB080855@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-reply-to: Your message of Fri, 20 Feb 2015 11:41:39 EST. <8461A1EA-866E-4487-90E2-17AFDCFF77D5@nominum.com> 
Date: Fri, 20 Feb 2015 21:58:45 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/a60PRlXUxkDBhqQ9wKtL_P62p70>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 21:03:04 -0000

 In your previous mail you wrote:

>  On Feb 20, 2015, at 10:22 AM, Francis Dupont <Francis.Dupont@fdupont.fr> =
>  wrote:
>  > => I can't remember if your objection is about public key
>  > vs. certificate.  If it is the case they are in fact equivalent
>  > as a certificate embeds a public key. Note in the server->client
>  > way a certificate has a little added value because a
>  > bootstrapping client has by definition no access to a PKI.
>  
>  What you are saying seems to represent a fundamental misunderstanding of
>  how PKI works and how it would make sense to use it.   Let me try to
>  explain:
>  
>  A cert from client to server makes no sense because certs are
>  signed by CAs, and there's (at least at present) no way to automate
>  that.  I'm not saying such a thing could never make sense, but I
>  don't see how it adds value.  The use model for such a cert that I
>  can imagine would be that a provider signs clients certs with a
>  provider key during some initial registration process, and then the
>  DHCP server just trusts all keys signed by the provider key.

=> I have to disagree:
 - first you have to bind a short list of keys (or certificates)
  to each client. Without this a client can too easily impersonate
  any other client.

 - a supposed benefit of certificate vs. a raw public key is to be
  able to associate the public key to identity, to provide revocation
  list, validity dates, etc. I believe most of these benefits are
  illusion but at least on the paper a PKI is supposed to be easier
  to manage.

 - the computing power, permanent/high bandwidth network access,
  management facilities, etc, are clearly by default on the server
  side.

So I am not against a certificate on the client->server way,
at the important condition it is not required, i.e., one can use
a raw public key. Note it is what I have said from the beginning.

>  But that doesn't make sense.  What most providers want is a
>  one-to-one accounting model, and you don't need a cert for
>  that--you just need to collect the client-generated key at
>  registration time and mark it as allowed in a key database.

=> at the exception of the key/client binding I have no concern
about this.

>  This means that later if the client doesn't pay the bill, you can
>  mark it in the database as no longer allowed.  The DHCP server just
>  checks in the database to see how the key is marked, and replies
>  accordingly, directing non-allowed keys to a captive portal, and
>  immediately allowing access for allowed keys.

=> the portal idea is more for an AAA system and if you want to
plug the DHCPv6 server to an AAA agent perhaps you will need
more than a certificate?

>  And in the reverse direction, it _does_ make sense for the server's
>  key to be signed by a PKI, for two reasons.  First, because of the
>  way PKI works.  The x.509 PKI that is used by web browsers relies
>  on the browser having a list of known roots, and if a cert's
>  signature chain leads back to a known root, the cert is considered
>  valid.  You need connectivity to check for revoked certs, but not
>  otherwise.

=> I am afraid this illusion of security is exactly what we don't
want... Adn network connectivity is required for validity dates too.

>  The second reason this makes sense is that providers have
>  infrastructure, and you don't want to have one key known to the
>  client where the private key is stored on every piece of
>  infrastructure in the provider network, because this means that the
>  compromise of any one infrastructure node will compromise the
>  entire network.

=> so you believe in the ease of management provided by PKIs
but only in this way?

>  No, what you want is for the provider to have a key that it uses to
>  sign infrastructure keys, and then you want each piece of
>  infrastructure to have its own key signed with the provider key.
>  You want the provider key to be long-lived, and you want the
>  infrastructure keys to be very short-lived, like maybe a week at
>  most.

=> short-lived public keys don't bring an important security advantage
but surely they raise clear operational issues.

>  This way stealing an infrastructure key has limited value, and yet
>  the client can reliably identify infrastructure keys as belonging
>  to the provider.

=> the client can detect an obsolete or revoked key only a posteriori
so likely too late. More, this model requires a lot of resources
on the client: when you ask for crypto support on smartphones
you get answers saying it is too expensive, etc, even 3D video
doesn't seem to be (:-). BTW I am afraid it is easier to mount
an attack using bad certificates (i.e., your use model) to drain
the battery than with raw keys (i.e., the use model of previous drafts).
 A last point: your use model will work better if the server provides
a certificate chain. As far as I know it is not supported and
it is not easy with UDP (cf. SeND which is my reference for
what we can (should?) do).

>  So the use model that seems plausible to me is the exact opposite of
>  what's currently described in the draft, and what you are describing
>  here, Francis.

=> perhaps it doesn't matter as the current direction is to allow
raw public keys or certificates in both ways, so independent of
use models...

>  >> What value does it add to have a PKI-authenticated key on the client?
>  > => IMHO none for the "PKI-authenticated" but there is one for
>  > the "authenticated" by TOFU or static config.
>  
>  Right, and so there's no need for the client to send a cert in this case.

=> one point we agree.

>  > => the server discards packets sent by the client without
>  > authentication options, the client doesn't know which
>  > authentication to use so uses none.
>
>  This is easily fixed: have the server discard packets that allocate
>  resources, but not discard solicit packets or information request
>  packets.  The client then sends an unauthenticated solicit, and if
>  it recognizes the server in the advertise, it sends an
>  authenticated request.

=> I didn't say it was a hard problem: just add complexity, have
corner cases (e.g., rapid commit), etc.

Regards

Francis.Dupont@fdupont.fr

PS: I prepared the code to support Secure DHCPv6 on the server side.
I provided a way to use per client certificates or raw public keys,
with certificate validation at any time, including before packet
receive, and simple compare between the received option and the
config. BTW I use Botan and OpenSSL backends and for both the
certificate comparison is not the bit to bit one could expect (:-).


From nobody Fri Feb 20 13:23:54 2015
Return-Path: <Francis.Dupont@fdupont.fr>
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 640051A01AA for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 13:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.262
X-Spam-Level: 
X-Spam-Status: No, score=-1.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ryi9DWF1ijuJ for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 13:23:52 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 308331A0199 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 13:23:52 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t1KLJak3082335; Fri, 20 Feb 2015 22:19:36 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201502202119.t1KLJak3082335@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
In-reply-to: Your message of Fri, 20 Feb 2015 10:37:36 PST. <CAJE_bqe7DMWabw_cnSdKThh-E5A=eM2vD6RruJTp5aGetoLhfw@mail.gmail.com> 
Date: Fri, 20 Feb 2015 22:19:36 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/drJwyYLgYOhjIMzbGgE7WuaQXe8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 21:23:53 -0000

I have to disagree: private/public key mechanisms are strictly more
secure than shared secret mechanisms. So you can't say the RFC3315
security is enough.

Now about the use model it seems there is no possible concensus for
one in a reasonable timeframe so the idea to put this point out of
scope is the right one.

Regards

Francis.Dupont@fdupont.fr

PS: it seems we are in the good enough now vs perfect in the next
century case, so I am refraining my preference for the second (:-).


From nobody Fri Feb 20 14:18:58 2015
Return-Path: <Ted.Lemon@nominum.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 D68D01A026C for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 14:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 xcADWs-YB76M for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 14:18:54 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 645BB1A019B for <dhcwg@ietf.org>; Fri, 20 Feb 2015 14:18:54 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 47DA4DA00EF for <dhcwg@ietf.org>; Fri, 20 Feb 2015 22:18:54 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 12C0553E07B; Fri, 20 Feb 2015 14:18:54 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 20 Feb 2015 14:18:53 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201502202058.t1KKwjKB080855@givry.fdupont.fr>
Date: Fri, 20 Feb 2015 17:17:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <500F4B05-4ADB-4C35-A2A6-BB60373AD4E3@nominum.com>
References: <201502202058.t1KKwjKB080855@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/fS81H9K6o3FORf2iFNgJtIUX7Uw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 20 Feb 2015 22:18:57 -0000

On Feb 20, 2015, at 3:58 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:
>> On Feb 20, 2015, at 10:22 AM, Francis Dupont =
<Francis.Dupont@fdupont.fr> =3D
>> wrote:
>>> =3D> I can't remember if your objection is about public key
>>> vs. certificate.  If it is the case they are in fact equivalent
>>> as a certificate embeds a public key. Note in the server->client
>>> way a certificate has a little added value because a
>>> bootstrapping client has by definition no access to a PKI.
>>=20
>> What you are saying seems to represent a fundamental misunderstanding =
of
>> how PKI works and how it would make sense to use it.   Let me try to
>> explain:
>>=20
>> A cert from client to server makes no sense because certs are
>> signed by CAs, and there's (at least at present) no way to automate
>> that.  I'm not saying such a thing could never make sense, but I
>> don't see how it adds value.  The use model for such a cert that I
>> can imagine would be that a provider signs clients certs with a
>> provider key during some initial registration process, and then the
>> DHCP server just trusts all keys signed by the provider key.
>=20
> =3D> I have to disagree:
> - first you have to bind a short list of keys (or certificates)
>  to each client. Without this a client can too easily impersonate
>  any other client.

How can a client impersonate a different client without knowing that =
client's private key?

> - a supposed benefit of certificate vs. a raw public key is to be
>  able to associate the public key to identity, to provide revocation
>  list, validity dates, etc. I believe most of these benefits are
>  illusion but at least on the paper a PKI is supposed to be easier
>  to manage.

Sure, but if for some reason the client's private key is compromised, =
the client can just generate a new key and re-register.   That's not =
very convenient, but it's no less convenient than pre-emptively signing =
keys and then revoking them if they are compromised.   The difference is =
that in the case where you are using certs, the cost is paid regardless =
of whether the key is ever compromised.

> - the computing power, permanent/high bandwidth network access,
>  management facilities, etc, are clearly by default on the server
>  side.

What does that have to do with anything?   Are you saying that the =
client shouldn't have to generate its key?

> So I am not against a certificate on the client->server way,
> at the important condition it is not required, i.e., one can use
> a raw public key. Note it is what I have said from the beginning.

I'm not against a certificate on the client either--I just don't think =
there is a valid use case for it, whereas clearly there is a valid use =
case for a public key on the client.

>> But that doesn't make sense.  What most providers want is a
>> one-to-one accounting model, and you don't need a cert for
>> that--you just need to collect the client-generated key at
>> registration time and mark it as allowed in a key database.
>=20
> =3D> at the exception of the key/client binding I have no concern
> about this.

So you agree that the server has to maintain a database of client keys?

>> This means that later if the client doesn't pay the bill, you can
>> mark it in the database as no longer allowed.  The DHCP server just
>> checks in the database to see how the key is marked, and replies
>> accordingly, directing non-allowed keys to a captive portal, and
>> immediately allowing access for allowed keys.
>=20
> =3D> the portal idea is more for an AAA system and if you want to
> plug the DHCPv6 server to an AAA agent perhaps you will need
> more than a certificate?

Captive portals and AAA are orthogonal.   Certainly they can work =
together, but there is no requirement that they be made to work =
together.   If they did, the flow would be that you'd present your key =
to authenticate your DHCP transaction, the key wouldn't be recognized, =
and you'd be sent to the captive portal to enter your username and =
password, which would be validated using AAA.   The two systems here are =
essentially orthogonal: once the key is associated with the user ID, you =
don't need to consult AAA anymore.   This is important because the =
public key solution provides automatic authentication, whereas AAA =
through the captive portal requires user intervention.   You don't want =
to have to interact with the captive portal every time you join the =
network.

>> And in the reverse direction, it _does_ make sense for the server's
>> key to be signed by a PKI, for two reasons.  First, because of the
>> way PKI works.  The x.509 PKI that is used by web browsers relies
>> on the browser having a list of known roots, and if a cert's
>> signature chain leads back to a known root, the cert is considered
>> valid.  You need connectivity to check for revoked certs, but not
>> otherwise.
>=20
> =3D> I am afraid this illusion of security is exactly what we don't
> want... Adn network connectivity is required for validity dates too.

No it's not.   Your device has a clock on it.   And if you want to fight =
the PKI battle, this is not the place to do it.   I agree that x.509 has =
issues, but the cert could also be a DNSSEC validation chain, at least =
in principle.

>> The second reason this makes sense is that providers have
>> infrastructure, and you don't want to have one key known to the
>> client where the private key is stored on every piece of
>> infrastructure in the provider network, because this means that the
>> compromise of any one infrastructure node will compromise the
>> entire network.
>=20
> =3D> so you believe in the ease of management provided by PKIs
> but only in this way?

I don't see a way to associate an infrastructure key with a provider =
that doesn't involve certs, no, other than a global infrastructure key =
with the problems I've described.

>> No, what you want is for the provider to have a key that it uses to
>> sign infrastructure keys, and then you want each piece of
>> infrastructure to have its own key signed with the provider key.
>> You want the provider key to be long-lived, and you want the
>> infrastructure keys to be very short-lived, like maybe a week at
>> most.
>=20
> =3D> short-lived public keys don't bring an important security =
advantage
> but surely they raise clear operational issues.

Either the key has to be short-lived, or there has to be a way to prove =
that it hasn't been revoked.

>> This way stealing an infrastructure key has limited value, and yet
>> the client can reliably identify infrastructure keys as belonging
>> to the provider.
>=20
> =3D> the client can detect an obsolete or revoked key only a =
posteriori
> so likely too late. More, this model requires a lot of resources
> on the client: when you ask for crypto support on smartphones
> you get answers saying it is too expensive, etc, even 3D video
> doesn't seem to be (:-). BTW I am afraid it is easier to mount
> an attack using bad certificates (i.e., your use model) to drain
> the battery than with raw keys (i.e., the use model of previous =
drafts).
> A last point: your use model will work better if the server provides
> a certificate chain. As far as I know it is not supported and
> it is not easy with UDP (cf. SeND which is my reference for
> what we can (should?) do).

If you have a trust relationship with a provider, the infrastructure key =
can be signed by a provider key that you have accepted, so the chain is =
one key deep.   Phones check certs all the time.   It's true that if you =
connect to a wifi network that wants to DoS your battery, you'd have to =
have a way of noticing that this is happening and dissociating with that =
AP after a certain number of failures.

> =3D> I didn't say it was a hard problem: just add complexity, have
> corner cases (e.g., rapid commit), etc.

Does anyone use Rapid Commit?

> PS: I prepared the code to support Secure DHCPv6 on the server side.
> I provided a way to use per client certificates or raw public keys,
> with certificate validation at any time, including before packet
> receive, and simple compare between the received option and the
> config. BTW I use Botan and OpenSSL backends and for both the
> certificate comparison is not the bit to bit one could expect (:-).

BTW, one thing we haven't discussed is using public keys to establish =
shared secrets rather than using the public keys themselves on every =
transaction.   It is possible that this would be a better solution.   =
But the bottom line is that right now we are shooting in the dark, and I =
don't see a way forward that doesn't involve proposing something and =
seeing if people use it.   The PK->shared secret method would involve a =
change to the DHCP state machine, so this seems like a better place to =
start.


From nobody Fri Feb 20 16:13:00 2015
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 93B3A1A0266 for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 16:12:58 -0800 (PST)
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 pymH-xu2yCPG for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 16:12:57 -0800 (PST)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1652C1A0055 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 16:12:56 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id bs8so6208622wib.4 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 16:12:55 -0800 (PST)
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=lEFJpgc4IPoZZcmtegazv+v7ypCUodzbKPqa/yUUxl4=; b=dCqxIZWxX9jIeMNHMHmtxWW/Clnlqax4rGfu2QlKTKhGnJfIAFAdJ308tWQDTfrVnW 26KgNSx8rZGDVXzE/kAirIOKcx01uvkW44hTGh/fHwkR5qpLDwB/TIRnW4mCu4zPBfOT /TJatF5aj//CJOM2ZmmiYzUqBiwgdm+Q+4LAv3Jqj6ctLJjZlIIy9NLZYj95EA7sCSKo t6JulmrE37XLRlGucZlMMxF8Eqaw/We0pLdgBrKEyK8+PP/agxIbn2TxI0NH5EBqYC1C 0hGN8xxHo/Iez1PPk+RZzgTww3qAUPsVkAlmbG3sK7BhKpyAgkAQC7qLs3cFVPDtUZAf M9MQ==
MIME-Version: 1.0
X-Received: by 10.180.198.101 with SMTP id jb5mr2108724wic.92.1424477575450; Fri, 20 Feb 2015 16:12:55 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.78.41 with HTTP; Fri, 20 Feb 2015 16:12:55 -0800 (PST)
In-Reply-To: <201502202119.t1KLJak3082335@givry.fdupont.fr>
References: <CAJE_bqe7DMWabw_cnSdKThh-E5A=eM2vD6RruJTp5aGetoLhfw@mail.gmail.com> <201502202119.t1KLJak3082335@givry.fdupont.fr>
Date: Fri, 20 Feb 2015 16:12:55 -0800
X-Google-Sender-Auth: 3P50qzgwoqOrk0eCb_gSNy1nVLM
Message-ID: <CAJE_bqdjzE5aeq5sRQKNLtupn1Ky0wHZBsJLfqCcZiRWGCMbEQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/aHsbY84vwHtYQlk7tMcc5H-Vx3c>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Sat, 21 Feb 2015 00:12:58 -0000

At Fri, 20 Feb 2015 22:19:36 +0100,
Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

> I have to disagree: private/public key mechanisms are strictly more
> secure than shared secret mechanisms. So you can't say the RFC3315
> security is enough.

Mainly for educating me (= not really a security expert), could you
explain exactly how sedhcpv6 (a private/public key mechanism) is
strictly more secure than RFC3315 (a shared secret mechanism) in the
case of client->server authentication?  In that an attacker would have
to compromise all clients it wants to attack while in the case of
shared secret the attacker would only have to break the centralized
"key database" (assuming such a thing is used)?

--
JINMEI, Tatuya


From nobody Fri Feb 20 19:39:28 2015
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 41AF51A1A81; Fri, 20 Feb 2015 19:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 5D1TLJBW_n-o; Fri, 20 Feb 2015 19:39:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A84911A1A72; Fri, 20 Feb 2015 19:39:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Bernie Volz" <volz@cisco.com>
To: <ted.lemon@nominum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150221033925.17537.54352.idtracker@ietfa.amsl.com>
Date: Fri, 20 Feb 2015 19:39:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/JYqLo6rcVNB1OBzPJEimmrQY7b8>
Cc: draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org, volz@cisco.com, dhc-chairs@ietf.org, draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org, dhc-chairs@tools.ietf.org, iesg-secretary@ietf.org, dhcwg@ietf.org, draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org
Subject: [dhcwg] Publication has been requested for draft-ietf-dhc-dynamic-shared-v4allocation-05
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 21 Feb 2015 03:39:27 -0000

Bernie Volz has requested publication of draft-ietf-dhc-dynamic-shared-v4allocation-05 as Proposed Standard on behalf of the DHC working group.

Please verify the document's state at http://datatracker.ietf.org/doc/draft-ietf-dhc-dynamic-shared-v4allocation/


From nobody Fri Feb 20 20:07:18 2015
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 6704C1A1AA3 for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 20:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 bdHhneuMVB0p for <dhcwg@ietfa.amsl.com>; Fri, 20 Feb 2015 20:07:12 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 571DA1A1A60 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 20:07:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8245; q=dns/txt; s=iport; t=1424491632; x=1425701232; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=GcHzFSuhvWp1qBm76/fjCXEnE+HmFYJl0EA0J2InWlg=; b=iUxm05JHkuj+Ni27uXVhWteP4HdszzueXpr6KtXsgmHte3lW+aviQUNw wo6jna/8OCMaMkbIWhx7pdhonUtb9WVDRo8v5fQ38QU7+pbf7t0/4D6y2 Z8oSCVunveL+hfEbYdefUdsGXbSJakbnop1/dTojD3O30/dTzi0ftRuVZ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANBQBPA+hU/4wNJK1bgwaBMMh6AoEZQwEBAQEBAXyEDwEBAQMBOjcNBwQCAQgOAwQBAQEKFAkHMhQJCAIEARIIiB8I00YBAQEBAQEBAQEBAQEBAQEBAQEBAQEXihF+hBcmJhIGgxGBFAWNXoFxhXOEaoMVi0ODPiKBfQICARyBUG+BA0F/AQEB
X-IronPort-AV: E=Sophos;i="5.09,618,1418083200"; d="scan'208";a="394823995"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-1.cisco.com with ESMTP; 21 Feb 2015 04:07:11 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t1L47BZ9025953 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 21 Feb 2015 04:07:11 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Fri, 20 Feb 2015 22:07:11 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Fernando Gont <fgont@si6networks.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
Thread-Index: AQHQS5Vv3GSx57lMxkuSGUlyG1nXUZz6eajA
Date: Sat, 21 Feb 2015 04:07:10 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9B6435@xmb-rcd-x04.cisco.com>
References: <54E47156.3000100@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1C9AC5C1@xmb-rcd-x04.cisco.com> <54E4B956.4090106@si6networks.com>
In-Reply-To: <54E4B956.4090106@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.203]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/I__J-RkPR1O1KdTJGJo-QktqYjA>
Subject: Re: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
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: Sat, 21 Feb 2015 04:07:16 -0000

Some comments below (BV>).

Sorry for the delay.

- Bernie

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com]=20
Sent: Wednesday, February 18, 2015 11:10 AM
To: Bernie Volz (volz); dhcwg@ietf.org
Subject: Re: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on a=
ddress ranges

Hi, Bernie,

Thanks so much for your prompt response! Please find my comments in-line...=
.

On 02/18/2015 11:47 AM, Bernie Volz (volz) wrote:
>=20
> There are servers that use full prefixes (i.e., can assign any=20
> addresses in /64) - and I guess you'd say to use ADDR_HI of=20
> x:x:x:x:FFFF:FFFF:FFFF:FFFF and ADDR_LOW of x:x:x:x:0:0:0:0?

Exactly. Actually, they could use the prefix notation in the configuration =
file, and it would be the DHCPv6 server software converting from prefix not=
ation to low/hi.



> In these
> cases, the extra math is not required.=20

You mean the low/hi thing?

BV> Yes, if a full /x prefix is used, one can just take the lower-order 128=
-x bits from the result. (There may be some cases where certain addresses m=
ay not be assignable, in which case one might have to do another calculatin=
g by increasing the counter.)

> And, for servers that have specific range (low to high), they will=20
> always have to do some "math". Also, I think it would be safe for most=20
> implementations to assume that doing this math with 64-bits is more=20
> than sufficient.

You mean to assume that the upper 64 bits (the prefix) is the same for low =
ad hi?

BV> Yes, I meant a server that was configured to use ::1:20 to ::1:8f (0x6f=
 addresses). Not a server that configured to use an entire /x prefix.



> An interesting question then is whether to change from Prefix to=20
> IPV6_ADDR_HI and IPV6_ADDR_LOW in the first place? Why not just stick=20
> to using the prefix that is in the RA (I would expect servers to know=20
> that since the configuration is probably a prefix with range(s)).
> Then the "range" is only applied at the end.

Because if what you specify is really a range, I'm not sure that the prefix=
 is meaningful anymore?

BV> Well, I guess you could argue but would someone really have 3 links wit=
h such "ranges" for v6. I thought we assumed there would be plenty of addre=
ss space in v6 and one wouldn't have to do that? Also, if some ways does it=
 really matter that much in this case? If Client A moves from Link 1 (range=
 1) to Link 2 (range 2), the algorithm will give it a new address any way y=
ou slice it since the ranges are different.=20

BV> Also, if you have a small address space, you can't really have stable a=
ddresses unless you have a very small client population. There are too many=
 conflicts otherwise (think of a Wifi hotspot that only had 100 addresses -=
 when you visit the hotspot tomorrow, your address has a very likely chance=
 of being in use by someone else so a different one has to be given anyway)=
.

BV> Sure, a /64 allows for many large ranges. But so does splitting the /64=
 into /68s or /72s. And if you do that, you are likely much better off.

> Note also that: - Ranges may not be contiguous. What if there are=20
> multiple ranges (i.e., 10 to 1000, 2000 to 3000)? This is why I think=20
> dropping the idea of start/end range makes the most sense - just use=20
> the prefix. - Ranges like this also have the interesting property that=20
> it breaks the idea of "stable" addresses whenever a change to the=20
> range occurs - increasing or decreasing the range will break=20
> stability.

This later point is very interesting indeed, and makes strong case for usin=
g the Prefix in the hash, rather than the range. How about employing the Pr=
efix in the hash function (as in the previous versions of the I-D), and the=
n "adjusting" the selected address to the hi/lo range as
follows:


if(IID < IID_low){
	IID=3DIID_low + iid % (IID_hi - IID_low + 1); } else if(IID > IID_hi){
	IID=3D IID_low + IID_hi  % (IID_hi - IID_low + 1); }

BV> Yes, I think the prefix should just be used in the hash. Once you get t=
he hash value, you can use this kind of algorithm to determine which entry =
in the "range" to assign to the client (if available).

?


> Also, shouldn't the IA option type be part of the expression? While=20
> today we have IA_NA and IA_TA and you probably don't want to do this=20
> for IA_TA, might not hurt to include this in case there are other=20
> types developed in the future? It probably isn't a big deal if we=20
> don't since that is less likely to be the case.

In this case it would be kind of redundant, since the spec itself says that=
 it's the IA_NA that we include (i.e., the type is implicit).
However, I agree that this wouldn't hurt.

Please let me know if you think it would be great to apply the suggested ch=
ange, and we'll do it (meanwhile maybe others can weigh in?).

BV> Yes, would be interesting to hear other input on this. I see little har=
m in adding two more bytes to the hash. But, yeah, we may never end up need=
ing it. But if we did, it would avoid defining yet another hash.


> An interesting question that might be asked is whether this work even=20
> needs to be standardized.

Well, you do need a spec if you need to achive the goals set forth in this =
document. Note that e.g., we've specified port-number randomization in RFC6=
056....

BV> Sure, there are some goals that are not achieved by having the server(s=
) remember (such as if the server's data is lost or the server is replaced =
by a completely different one). But how often is that going to happen? And =
collisions are going to occur (especially with smaller ranges), so I don't =
see that this gives you any guarantee that things will be that much better.

> Also, what might happen with a DHCPv6
> failover implementation (in this case, it could be that the resulting=20
> address that is generated by this is not available to that server=20
> (assigned to partner) and so counter would have to be incremented and=20
> regenerate an address ... which could happen multiple times).

Well, since the address space is supposed to be large, collissions should b=
e pretty low.

But... maybe we should add a note regarding the address range? i.e.
"don't make it too small ore collisions might happen".

BV> Yes. I think the statement should be the smaller you make the pool the =
more likely collisions are and the less value this has. A pool of 2^64 addr=
esses has much lower probability of collisions than a pool of 2^32 (probabl=
y 1/2^32 less, but someone might prove that wrong). But of course, if you o=
nly have 1 unique client connecting to your network, a pool of 1 is just fi=
ne. So, this has to be taken in the context of the intended client populati=
on and the intended stability of addresses. The more unique clients and the=
 longer the chance of stability desired, the larger the pool must be. And f=
inally there is always bad luck - You may have no stability with just two c=
lients.


> If DHCPv6 is supposed to provide stable addresses, why not just have=20
> the server remember the addresses that it assigned to a specific=20
> client (or Client & IA)? Servers have to have state, so this is not=20
> that challenging. Sure, you have to limit the time (otherwise you=20
> could build up a large amount of state), but would you really want to=20
> have the same address after many months?

Yes. Why would you want to change it? -- think ACLs, logging, etc.

BV> If you are going to create ACLs and assuming logging information is val=
id over long times, RESERVE addresses for a client. I doubt any administrat=
or would be willing to risk critical resources / logging based on "stable p=
rivacy addresses". They will reserve the addresses for the client. (Yes, th=
is isn't perfect either as if you know the client DUID you can "steal" the =
address; but "stable privacy addresses" has that same issue as well so it d=
oesn't buy you anything better).



Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sat Feb 21 11:28:59 2015
Return-Path: <Francis.Dupont@fdupont.fr>
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 8FB0D1A1B65 for <dhcwg@ietfa.amsl.com>; Sat, 21 Feb 2015 11:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.138
X-Spam-Level: *
X-Spam-Status: No, score=1.138 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 f0CwCBDI60ke for <dhcwg@ietfa.amsl.com>; Sat, 21 Feb 2015 11:28:56 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 091A81A1A6E for <dhcwg@ietf.org>; Sat, 21 Feb 2015 11:28:55 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t1LJOZd9062437; Sat, 21 Feb 2015 20:24:36 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201502211924.t1LJOZd9062437@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-reply-to: Your message of Fri, 20 Feb 2015 17:17:57 EST. <500F4B05-4ADB-4C35-A2A6-BB60373AD4E3@nominum.com> 
Date: Sat, 21 Feb 2015 20:24:35 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/PgWnasMQSGYHPU_3Hw6MifmkaMk>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Sat, 21 Feb 2015 19:28:58 -0000

 In your previous mail you wrote:

>  How can a client impersonate a different client without knowing that
>  client's private key?

=> when you verify the public key and the signature are fine
but not the public key is bound to this particular client
(i.e., per client list of keys vs a global list of keys).

>  > - a supposed benefit of certificate vs. a raw public key is to be
>  >  able to associate the public key to identity, to provide revocation
>  >  list, validity dates, etc. I believe most of these benefits are
>  >  illusion but at least on the paper a PKI is supposed to be easier
>  >  to manage.
>  
>  Sure, but if for some reason the client's private key is compromised,
>  the client can just generate a new key and re-register.   That's not
>  very convenient, but it's no less convenient than pre-emptively signing
>  keys and then revoking them if they are compromised.   The difference is
>  that in the case where you are using certs, the cost is paid regardless
>  of whether the key is ever compromised.

=> I exposed the PKI argument, I didn't say I bought it. Or with
other words I prefer raw public keys but I shan't fight the idea
to use a certificate in place of a public key.

>  > - the computing power, permanent/high bandwidth network access,
>  >  management facilities, etc, are clearly by default on the server
>  >  side.
>  
>  What does that have to do with anything?   Are you saying that the
>  client shouldn't have to generate its key?

=> I expect key pair generation to be a rare event so it is a
second order concern. Here my concern is about the cost of validating
a certificate (get the chain, verify signature, check CRLs, check
attributes, etc) vs the cost of membership in a short list.

>  > So I am not against a certificate on the client->server way,
>  > at the important condition it is not required, i.e., one can use
>  > a raw public key. Note it is what I have said from the beginning.
>  
>  I'm not against a certificate on the client either--I just don't think
>  there is a valid use case for it, whereas clearly there is a valid use
>  case for a public key on the client.

=> IMHO we have a better use of our time than to speculate about
future use model, especially when it should delay without a bound
the progress of the specs to use (:-). So agree to disagree and
move forward?

>  So you agree that the server has to maintain a database of client keys?

=> a database of client keys or certificates or both.

>  > => I am afraid this illusion of security is exactly what we don't
>  > want... Adn network connectivity is required for validity dates too.
>  
>  No it's not.   Your device has a clock on it.

=> I am afraid you can't make this assumption, in particular for
a booting device. Please note IMHO it is important the secure DHCPv6
protocol to work with clients without a clock (here a clock is
a piece of hardware which can provide a good UTC date after a long
poweroff state).

>  I don't see a way to associate an infrastructure key with a provider
>  that doesn't involve certs, no, other than a global infrastructure key
>  with the problems I've described.

=> you have some hidden assumptions about what is the infrastructure.
For instance there is no problem when the infrastructure is one DHCP
server. Note I didn't raise a concern about the term provider so
I left you to describe an environment which could be not the most
common one...

>  > => short-lived public keys don't bring an important security
>  > advantage but surely they raise clear operational issues.
>
>  Either the key has to be short-lived, or there has to be a way to
>  prove that it hasn't been revoked.

=> to be honest I don't believe in revocation (and I live in a country
where a 80,000,000 entry CRL was deployed :-).

>  If you have a trust relationship with a provider, the infrastructure key
>  can be signed by a provider key that you have accepted, so the chain is
>  one key deep.

=> in the real world the only reason to get short chains is for the
top level CA to get better control over client CAs/RAs (cf the
maximum depth in Basic Constraints attribute).

>  > => I didn't say it was a hard problem: just add complexity, have
>  > corner cases (e.g., rapid commit), etc.
>  
>  Does anyone use Rapid Commit?

=> anyone which knows what it is and how to configure it...

>  > PS: I prepared the code to support Secure DHCPv6 on the server side.
>  > I provided a way to use per client certificates or raw public keys,
>  > with certificate validation at any time, including before packet
>  > receive, and simple compare between the received option and the
>  > config. BTW I use Botan and OpenSSL backends and for both the
>  > certificate comparison is not the bit to bit one could expect (:-).
>  
>  BTW, one thing we haven't discussed is using public keys to establish
>  shared secrets rather than using the public keys themselves on every
>  transaction.   It is possible that this would be a better solution.

=> it is stateful vs stateless. I believe there was some messages
about this tradeoff and the concensus was to keep no state as
it was done for the DHCPv6 protocol itself.

>  But the bottom line is that right now we are shooting in the dark,
>  and I don't see a way forward that doesn't involve proposing
>  something and seeing if people use it.  The PK->shared secret
>  method would involve a change to the DHCP state machine, so this
>  seems like a better place to start.

=> I agree.

Thanks

Francis.Dupont@fdupont.fr


From nobody Sat Feb 21 12:55:12 2015
Return-Path: <Francis.Dupont@fdupont.fr>
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 17FED1A003A for <dhcwg@ietfa.amsl.com>; Sat, 21 Feb 2015 12:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.262
X-Spam-Level: 
X-Spam-Status: No, score=-1.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 647zqTEdVkTF for <dhcwg@ietfa.amsl.com>; Sat, 21 Feb 2015 12:55:10 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61B31A0010 for <dhcwg@ietf.org>; Sat, 21 Feb 2015 12:55:09 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id t1LKonod067560; Sat, 21 Feb 2015 21:50:50 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201502212050.t1LKonod067560@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
In-reply-to: Your message of Fri, 20 Feb 2015 16:12:55 PST. <CAJE_bqdjzE5aeq5sRQKNLtupn1Ky0wHZBsJLfqCcZiRWGCMbEQ@mail.gmail.com> 
Date: Sat, 21 Feb 2015 21:50:49 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/p1vkcx4pG7rg7tXEU5s5PIYjNx0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Sat, 21 Feb 2015 20:55:11 -0000

 In your previous mail you wrote:

>  At Fri, 20 Feb 2015 22:19:36 +0100,
>  Francis Dupont <Francis.Dupont@fdupont.fr> wrote:
>  
>  > I have to disagree: private/public key mechanisms are strictly more
>  > secure than shared secret mechanisms. So you can't say the RFC3315
>  > security is enough.

=> it is about where is the secret: for a private/public key mechanism
the secret is in one place, for a shared secret mechanism it is in two
places. To summary the term "shared secret" is basically an oxymoron...

Regards

Francis.Dupont@fdupont.fr

PS: in particular applied to long term secrets as for this context.


From nobody Sat Feb 21 16:04:27 2015
Return-Path: <Ted.Lemon@nominum.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 D089B1A0122 for <dhcwg@ietfa.amsl.com>; Sat, 21 Feb 2015 16:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 oZor_q0UxCaj for <dhcwg@ietfa.amsl.com>; Sat, 21 Feb 2015 16:04:24 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE01D1A00F6 for <dhcwg@ietf.org>; Sat, 21 Feb 2015 16:04:23 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 88A74DA00C9 for <dhcwg@ietf.org>; Sun, 22 Feb 2015 00:04:23 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 364DA53E078; Sat, 21 Feb 2015 16:04:23 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sat, 21 Feb 2015 16:04:23 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201502211924.t1LJOZd9062437@givry.fdupont.fr>
Date: Sat, 21 Feb 2015 19:03:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/szNl2qEJiIW37sVVL8UBYtWP7O4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Sun, 22 Feb 2015 00:04:27 -0000

On Feb 21, 2015, at 2:24 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:
> =3D> when you verify the public key and the signature are fine
> but not the public key is bound to this particular client
> (i.e., per client list of keys vs a global list of keys).

Yes, of course, you have to have both authentication and authorization; =
just authentication won't do any good.   I think the document already =
explains this.

> =3D> I exposed the PKI argument, I didn't say I bought it. Or with
> other words I prefer raw public keys but I shan't fight the idea
> to use a certificate in place of a public key.

OK, cool.

> =3D> IMHO we have a better use of our time than to speculate about
> future use model, especially when it should delay without a bound
> the progress of the specs to use (:-). So agree to disagree and
> move forward?

Completely agree.

> =3D> I am afraid you can't make this assumption, in particular for
> a booting device. Please note IMHO it is important the secure DHCPv6
> protocol to work with clients without a clock (here a clock is
> a piece of hardware which can provide a good UTC date after a long
> poweroff state).

I think that such devices will have to accept a more limited assurance =
of the security of the transaction.

> =3D> you have some hidden assumptions about what is the =
infrastructure.
> For instance there is no problem when the infrastructure is one DHCP
> server. Note I didn't raise a concern about the term provider so
> I left you to describe an environment which could be not the most
> common one...

You are correct: for that use case, a cert adds no value.

>> Either the key has to be short-lived, or there has to be a way to
>> prove that it hasn't been revoked.
>=20
> =3D> to be honest I don't believe in revocation (and I live in a =
country
> where a 80,000,000 entry CRL was deployed :-).

In principle the mechanism in RFC 6962 isn't bad.   But I don't think we =
can use it.

> =3D> anyone which knows what it is and how to configure it...

So no-one (rapid commit)?

> =3D> it is stateful vs stateless. I believe there was some messages
> about this tradeoff and the concensus was to keep no state as
> it was done for the DHCPv6 protocol itself.

Yup.

>> But the bottom line is that right now we are shooting in the dark,
>> and I don't see a way forward that doesn't involve proposing
>> something and seeing if people use it.  The PK->shared secret
>> method would involve a change to the DHCP state machine, so this
>> seems like a better place to start.
>=20
> =3D> I agree.

Okay.   I think the discussion is useful, but we have no action item.   =
The question is whether Jinmei-san and Ralph can live with not trying to =
document use cases.   I think that the standard ought to be along the =
lines of what's documented in RFC 7282, though--I don't think we're =
going to get to complete consensus on this.


From nobody Sun Feb 22 13:15:46 2015
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 CDDDF1A0076 for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 13:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.81
X-Spam-Level: 
X-Spam-Status: No, score=-11.81 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 tXjSjVjkyU2i for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 13:15:43 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EE8C1A006F for <dhcwg@ietf.org>; Sun, 22 Feb 2015 13:15:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9372; q=dns/txt; s=iport; t=1424639743; x=1425849343; h=from:to:subject:date:message-id:mime-version; bh=H/WJdK3P56zGXnQIpLtE8KMfuK3Z2cg4vSiHu7fUtH4=; b=LB//+BnhEVtQn5g0x18QV3fgKKALsvF1MKmRKES6LWTBbpmLZBkgv/G5 xeKJ7pE7uyemLyDwbciOr4yEzIPemRqa2KIr8rSe/IQ+l0az/kRA9Y2xx a9+NsNeMw+XtXbQWSZkOdoRuULnfcY7qkpbqZDfUoV70B8sdWkOezJdJ+ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BqCQBvRupU/5JdJa1bgkNDUloEhQ28FIFkAQmFJ0kCgRxDAQEBAQEBfIQRAQQtQR0BKlYmAQQbAYgmDapIpywBAQEBAQUBAQEBAQEBG4xQgmABAQoULYI4TR2BFAWPUoNehwA4gl2INoZNIoNubwGBCjl/AQEB
X-IronPort-AV: E=Sophos;i="5.09,626,1418083200";  d="scan'208,217";a="395074769"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-9.cisco.com with ESMTP; 22 Feb 2015 21:15:42 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t1MLFg8a029373 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 22 Feb 2015 21:15:42 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Sun, 22 Feb 2015 15:15:42 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Adoption Call - draft-dhcwg-dhc-rfc3315bis-04 - Concludes March 9, 2015
Thread-Index: AdBO5MP1eHfeOqHzR1SYoMleg6u0lQ==
Date: Sun, 22 Feb 2015 21:15:41 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9B8FF8@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.203]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1C9B8FF8xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/DemfH7ST_9ymdT4bFSkcNg-bPDo>
Subject: [dhcwg] WG Adoption Call - draft-dhcwg-dhc-rfc3315bis-04 - Concludes March 9, 2015
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: Sun, 22 Feb 2015 21:15:45 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1C9B8FF8xmbrcdx04ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:



As you all know, the work to update the DHCPv6 specs, mainly RFC3315 and RF=
C3633, has been going for some time. The design team involved in this work =
believes that it's a good time to ask for adoption of this work.



The document - draft-dhcwg-dhc-rfc3315bis-04 (https://tools.ietf.org/html/d=
raft-dhcwg-dhc-rfc3315bis) - started from a XMLized copy of RFC3315 (see th=
e -00 draft). Most of the text from RFC3633 was merged (note: there are sti=
ll missing pieces) there. A significant number of corrections, clarificatio=
ns and smaller edits were made. The changes are documented in appendices A =
and B. They often mention ticket numbers. Those tickets can be reviewed and=
 commented at http://wiki.tools.ietf.org/group/dhcpv6bis/.



As both DHC WG chairs, DHC secretary, and current AD are co-authors of this=
 draft, we'll not be able to assess consensus on our own. We will consult w=
ith our AD to determine the best course of action. In any case, the adoptio=
n call consensus will be determined shortly after end of day March 9th. (Th=
ough if there are no objections, the consensus is clear.)



Keep in mind that this is a work well in progress with lots of outstanding =
things to do. The question here is whether this is the direction we, as a w=
orking group, want to take.



There's also an additional question if you support adoption. Every time a t=
icket is added, modified or commented in the issue tracker, there's a mail =
notification. Currently such notifications are sent to the dhcpv6bis mailin=
g list. You can review those here:

http://www.ietf.org/mail-archive/web/dhcpv6bis/current/maillist.html. If yo=
u want those notifications to be sent to the DHC rather than dhcpv6bis list=
, please say so.



-          Bernie & Tomek


--_000_489D13FBFA9B3E41812EA89F188F018E1C9B8FF8xmbrcdx04ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1335451852;
	mso-list-type:hybrid;
	mso-list-template-ids:986207992 -681567834 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Consolas;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">As you all know, the work to update the DHCPv6 sp=
ecs, mainly RFC3315 and RFC3633, has been going for some time. The design t=
eam involved in this work believes that it's a good time to ask for adoptio=
n of this work.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The document - draft-dhcwg-dhc-rfc3315bis-04 (<a =
href=3D"https://tools.ietf.org/html/draft-dhcwg-dhc-rfc3315bis">https://too=
ls.ietf.org/html/draft-dhcwg-dhc-rfc3315bis</a>) - started from a XMLized c=
opy of RFC3315 (see the -00 draft).
 Most of the text from RFC3633 was merged (note: there are still missing pi=
eces) there. A significant number of corrections, clarifications and smalle=
r edits were made. The changes are documented in appendices A and B. They o=
ften mention ticket numbers. Those
 tickets can be reviewed and commented at <a href=3D"http://wiki.tools.ietf=
.org/group/dhcpv6bis/">
http://wiki.tools.ietf.org/group/dhcpv6bis/</a>.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">As both DHC WG chairs, DHC secretary, and current=
 AD are co-authors of this draft, we'll not be able to assess consensus on =
our own. We will consult with our AD to determine the best course of action=
. In any case, the adoption call consensus
 will be determined shortly after end of day March 9th. (Though if there ar=
e no objections, the consensus is clear.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Keep in mind that this is a work well in progress=
 with lots of outstanding things to do. The question here is whether this i=
s the direction we, as a working group, want to take.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There's also an additional question if you suppor=
t adoption. Every time a ticket is added, modified or commented in the issu=
e tracker, there's a mail notification. Currently such notifications are se=
nt to the dhcpv6bis mailing list.
 You can review those here:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"http://www.ietf.org/mail-archive/web/d=
hcpv6bis/current/maillist.html">http://www.ietf.org/mail-archive/web/dhcpv6=
bis/current/maillist.html</a>. If you want those notifications to be sent t=
o the DHC rather than dhcpv6bis list,
 please say so. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>Bernie &amp; Tomek<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1C9B8FF8xmbrcdx04ciscoc_--


From nobody Sun Feb 22 17:20:56 2015
Return-Path: <huitema@microsoft.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 B9E2F1A0011 for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 17:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 eqQG91rSGhBf for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 17:20:52 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0770.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::770]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6992C1A0006 for <dhcwg@ietf.org>; Sun, 22 Feb 2015 17:20:52 -0800 (PST)
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) by DM2PR0301MB0734.namprd03.prod.outlook.com (25.160.97.142) with Microsoft SMTP Server (TLS) id 15.1.93.16; Mon, 23 Feb 2015 01:20:25 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) by DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) with Microsoft SMTP Server (TLS) id 15.1.87.13; Mon, 23 Feb 2015 01:20:24 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) by DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) with mapi id 15.01.0087.013; Mon, 23 Feb 2015 01:20:24 +0000
From: Christian Huitema <huitema@microsoft.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Anonymity profile
Thread-Index: AdBPBm167/VyBXafQ7KwFjENXZM91g==
Date: Mon, 23 Feb 2015 01:20:24 +0000
Message-ID: <DM2PR0301MB065557765FBFD4C6C9C93D22A8290@DM2PR0301MB0655.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.16.156.113]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=huitema@microsoft.com; 
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0655;UriScan:;
x-microsoft-antispam-prvs: <DM2PR0301MB0655A2A10109F94F88B6D5C4CF290@DM2PR0301MB0655.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0655; 
x-forefront-prvs: 0496DF6962
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(66066001)(77156002)(86362001)(50986999)(86612001)(106356001)(105586002)(54356999)(19580395003)(64706001)(99286002)(2656002)(33656002)(97736003)(2351001)(107886001)(62966003)(101416001)(450100001)(229853001)(110136001)(87936001)(46102003)(15975445007)(102836002)(68736005)(2900100001)(40100003)(122556002)(221733001)(92566002)(2501002)(74316001)(76576001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0655; H:DM2PR0301MB0655.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2015 01:20:24.4014 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0655
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0734;
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/BZ25jMIJhP7DCDPLA3TvVgju2kY>
Subject: [dhcwg] Anonymity profile
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, 23 Feb 2015 01:20:54 -0000

Last Friday, I submitted: http://datatracker.ietf.org/doc/draft-huitema-dhc=
-anonymity-profile/, " Anonymity profile for DHCP clients."

Abstract:
   Some DHCP options carry unique identifiers.  These identifiers can
   enable device tracking even if the device administrator takes care of
   randomizing other potential identifications like link-layer addresses
   or IPv6 addresses.  The anonymity profile is designed for clients
   that wish to remain anonymous to the visited network.  The profile
   provides guidelines on the composition of DHCP or DHCPv6 requests,
   designed to minimize disclosure of identifying information.

The profile is really a complement to MAC Address Randomization. It is desi=
gned so that clients who use randomized MAC address and want to remain anon=
ymous avoid leaking identifiers in the DHCP messages. Should not be too con=
troversial, I hope.

-- Christian Huitema


From nobody Sun Feb 22 17:49:00 2015
Return-Path: <huitema@huitema.net>
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 0B8311A000D for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 17:15:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  RCVD_IN_DNSWL_NONE=-0.0001] 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 io_HN3-ULRym for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 17:15:24 -0800 (PST)
Received: from xsmtp04.mail2web.com (xsmtp04.mail2web.com [168.144.250.231]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 325B31A0006 for <dhcwg@ietf.org>; Sun, 22 Feb 2015 17:15:24 -0800 (PST)
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1YPhcF-0004lh-4F for dhcwg@ietf.org; Sun, 22 Feb 2015 20:15:23 -0500
Received: (qmail 2458 invoked from network); 23 Feb 2015 01:15:18 -0000
Received: from unknown (HELO huitema1) (Authenticated-user:_huitema@huitema.net@[24.16.156.113]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dhcwg@ietf.org>; 23 Feb 2015 01:15:18 -0000
From: "Christian Huitema" <huitema@huitema.net>
To: <dhcwg@ietf.org>
Date: Sun, 22 Feb 2015 17:15:19 -0800
Message-ID: <00b001d04f06$30ecae80$92c60b80$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdBPBaF3OXJXtIILS9ekIvbKmNxVIQ==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/oJP1qc87Y_csL1gnyhtxL-MjgsQ>
X-Mailman-Approved-At: Sun, 22 Feb 2015 17:49:00 -0800
Subject: [dhcwg] Anonymity profile
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, 23 Feb 2015 01:15:27 -0000

Friday, I submitted a draft describing an =93anonymity profile=94 for =
DHCP and
DHCPv6:

http://datatracker.ietf.org/doc/draft-huitema-dhc-anonymity-profile/

Abstract:

   Some DHCP options carry unique identifiers.  These identifiers can
   enable device tracking even if the device administrator takes care of
   randomizing other potential identifications like link-layer addresses
   or IPv6 addresses.  The anonymity profile is designed for clients
   that wish to remain anonymous to the visited network.  The profile
   provides guidelines on the composition of DHCP or DHCPv6 requests,
   designed to minimize disclosure of identifying information.

This follows discussions that we had in Honolulu about the need to make =
sure
that devices that use MAC Address Randomization cannot be tracked =
through
unique identifiers leaked by DHCP.=20

-- Christian Huitema








From nobody Sun Feb 22 19:29:11 2015
Return-Path: <fgont@si6networks.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 C1A701A014D for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 19:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.847
X-Spam-Level: *
X-Spam-Status: No, score=1.847 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_12_24=1.049, SPF_HELO_PASS=-0.001, 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 k34TXPHy7Vzw for <dhcwg@ietfa.amsl.com>; Sun, 22 Feb 2015 19:29:08 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878FE1A014A for <dhcwg@ietf.org>; Sun, 22 Feb 2015 19:29:08 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YPjhN-00085S-CS; Mon, 23 Feb 2015 04:28:51 +0100
Message-ID: <54E9CD16.4030501@si6networks.com>
Date: Sun, 22 Feb 2015 09:35:34 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <54E47156.3000100@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1C9AC5C1@xmb-rcd-x04.cisco.com> <54E4B956.4090106@si6networks.com> <489D13FBFA9B3E41812EA89F188F018E1C9B6435@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1C9B6435@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/VkaAmt6J97bWWBOiRe39EILsms0>
Subject: Re: [dhcwg] draft-ietf-dhc-stable-privacy-addresses: Question on address ranges
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, 23 Feb 2015 03:29:10 -0000

Hi, Bernie,

Thanks so much for your feedback! -- Please find my comments in-line....

On 02/21/2015 01:07 AM, Bernie Volz (volz) wrote:
> BV> Also, if you have a small address space, you can't really have
> stable addresses unless you have a very small client population.
> There are too many conflicts otherwise (think of a Wifi hotspot that
> only had 100 addresses - when you visit the hotspot tomorrow, your
> address has a very likely chance of being in use by someone else so a
> different one has to be given anyway).

Fully agreed.


>> Note also that: - Ranges may not be contiguous. What if there are 
>> multiple ranges (i.e., 10 to 1000, 2000 to 3000)? This is why I
>> think dropping the idea of start/end range makes the most sense -
>> just use the prefix. - Ranges like this also have the interesting
>> property that it breaks the idea of "stable" addresses whenever a
>> change to the range occurs - increasing or decreasing the range
>> will break stability.
> 
> This later point is very interesting indeed, and makes strong case
> for using the Prefix in the hash, rather than the range. How about
> employing the Prefix in the hash function (as in the previous
> versions of the I-D), and then "adjusting" the selected address to
> the hi/lo range as follows:
> 
> 
> if(IID < IID_low){ IID=IID_low + iid % (IID_hi - IID_low + 1); } else
> if(IID > IID_hi){ IID= IID_low + IID_hi  % (IID_hi - IID_low + 1); }
> 
> BV> Yes, I think the prefix should just be used in the hash. Once you
> get the hash value, you can use this kind of algorithm to determine
> which entry in the "range" to assign to the client (if available).
> 
> ?

Agreed. I will update the I-D as discussed.



>> Also, shouldn't the IA option type be part of the expression? While
>>  today we have IA_NA and IA_TA and you probably don't want to do
>> this for IA_TA, might not hurt to include this in case there are
>> other types developed in the future? It probably isn't a big deal
>> if we don't since that is less likely to be the case.
> 
> In this case it would be kind of redundant, since the spec itself
> says that it's the IA_NA that we include (i.e., the type is
> implicit). However, I agree that this wouldn't hurt.
> 
> Please let me know if you think it would be great to apply the
> suggested change, and we'll do it (meanwhile maybe others can weigh
> in?).
> 
> BV> Yes, would be interesting to hear other input on this. I see
> little harm in adding two more bytes to the hash. But, yeah, we may
> never end up needing it. But if we did, it would avoid defining yet
> another hash.

Unless there are arguments against this, I'll apply the proposed change.



>> An interesting question that might be asked is whether this work
>> even needs to be standardized.
> 
> Well, you do need a spec if you need to achive the goals set forth in
> this document. Note that e.g., we've specified port-number
> randomization in RFC6056....
> 
> BV> Sure, there are some goals that are not achieved by having the
> server(s) remember (such as if the server's data is lost or the
> server is replaced by a completely different one). But how often is
> that going to happen? And collisions are going to occur (especially
> with smaller ranges), so I don't see that this gives you any
> guarantee that things will be that much better.

This algorithm assumes that you'll employ most of the /64 for selecting
the addresses to be leased (otherwise, from a security standpoint,
randomizing the IID will not buy you much) -- maybe this should be noted
in the I-D?

That said, while I don't have stats regarding the aforementioned
failures in e.g. enterprise networks, I'm sure I'm not the only one who
has experienced his home server's HD die from "night to day".

And you can achieve the aforementioned benefit by simply replacing the
call you'd make to random() -- assuming you want to randomize addresses
-- with the expression specified in this document, and including a
"secret_key" parameter in the configuration file.



>> Also, what might happen with a DHCPv6 failover implementation (in
>> this case, it could be that the resulting address that is generated
>> by this is not available to that server (assigned to partner) and
>> so counter would have to be incremented and regenerate an address
>> ... which could happen multiple times).
> 
> Well, since the address space is supposed to be large, collissions
> should be pretty low.
> 
> But... maybe we should add a note regarding the address range? i.e. 
> "don't make it too small ore collisions might happen".
> 
> BV> Yes. I think the statement should be the smaller you make the
> pool the more likely collisions are and the less value this has. A
> pool of 2^64 addresses has much lower probability of collisions than
> a pool of 2^32 (probably 1/2^32 less, but someone might prove that
> wrong). But of course, if you only have 1 unique client connecting to
> your network, a pool of 1 is just fine. So, this has to be taken in
> the context of the intended client population and the intended
> stability of addresses. The more unique clients and the longer the
> chance of stability desired, the larger the pool must be. And finally
> there is always bad luck - You may have no stability with just two
> clients.

Agreed.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Feb 23 10:51:26 2015
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 232001A1EEC for <dhcwg@ietfa.amsl.com>; Mon, 23 Feb 2015 10:51:25 -0800 (PST)
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 xeBfsJ7Y43b2 for <dhcwg@ietfa.amsl.com>; Mon, 23 Feb 2015 10:51:24 -0800 (PST)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A6EF1A1EFD for <dhcwg@ietf.org>; Mon, 23 Feb 2015 10:51:24 -0800 (PST)
Received: by iecrl12 with SMTP id rl12so25880950iec.2 for <dhcwg@ietf.org>; Mon, 23 Feb 2015 10:51:23 -0800 (PST)
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=h2kuuN1fNxzYK++fe0YS2Fo6IPlNroWVn7UDebLR2w8=; b=GyqG3PHr6RPBlfuPPaQkhJ8HmtSSy6fa67/HC8W5bms4SIZchy3oph3KZz4g5sbwlW w2YBupktjTNON2mrIxq2VOCIWg5cqXwCAhM+IVh7IdKc5e9X6ct26WOmJGjC1xBPZGQh jSbH3dmEt+dwpl2JNdoK5HCpwL6RsmpVZfuFO2phnsEq07Yz2RCe/EVjNvWZliGaYLca sZPpX8tUPNWQw3IpLdwjxGOSv1aY55mlfeJ5NF6vStURdEZWu1dkrOlaa+3xIGLXMrCc O5lSMn4a4y7Poc1KmfGvdYkm7w2Y9AYXFG1BRQKvVMabfGUNGuduM0r+8dgamVGhXccN Og/w==
MIME-Version: 1.0
X-Received: by 10.107.10.74 with SMTP id u71mr16033584ioi.0.1424717483299; Mon, 23 Feb 2015 10:51:23 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Mon, 23 Feb 2015 10:51:23 -0800 (PST)
In-Reply-To: <201502212050.t1LKonod067560@givry.fdupont.fr>
References: <CAJE_bqdjzE5aeq5sRQKNLtupn1Ky0wHZBsJLfqCcZiRWGCMbEQ@mail.gmail.com> <201502212050.t1LKonod067560@givry.fdupont.fr>
Date: Mon, 23 Feb 2015 10:51:23 -0800
X-Google-Sender-Auth: cMfrTsUSqjaNvdMcRlIg-DWbS8M
Message-ID: <CAJE_bqcgDFWAgnNx6m-HRsYf_68HEQ+uBAKTmA7rDD1CbJ2cFA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pIykYVluOn4xBK4lsE2KB93P97Y>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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, 23 Feb 2015 18:51:25 -0000

At Sat, 21 Feb 2015 21:50:49 +0100,
Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

> >  At Fri, 20 Feb 2015 22:19:36 +0100,
> >  Francis Dupont <Francis.Dupont@fdupont.fr> wrote:
> >
> >  > I have to disagree: private/public key mechanisms are strictly more
> >  > secure than shared secret mechanisms. So you can't say the RFC3315
> >  > security is enough.
>
> => it is about where is the secret: for a private/public key mechanism
> the secret is in one place, for a shared secret mechanism it is in two
> places. To summary the term "shared secret" is basically an oxymoron...

It's still vague to me...specifically what kind of attack should we
worry about in the case of client->server authentication when we use
the shared secret mechanism, and in which sense is it more serious
than with the public/private key mechanism?

--
JINMEI, Tatuya


From nobody Mon Feb 23 13:16:15 2015
Return-Path: <mcr@sandelman.ca>
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 0071F1A6F2E for <dhcwg@ietfa.amsl.com>; Mon, 23 Feb 2015 13:16:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level: 
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 shtlz_GXnt8m for <dhcwg@ietfa.amsl.com>; Mon, 23 Feb 2015 13:16:06 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F27D1A6F2A for <dhcwg@ietf.org>; Mon, 23 Feb 2015 13:16:06 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7BAAD203AA; Mon, 23 Feb 2015 16:24:14 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id CBFB563A21; Mon, 23 Feb 2015 16:16:04 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B8DAC637F4; Mon, 23 Feb 2015 16:16:04 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Christian Huitema" <huitema@huitema.net>
In-Reply-To: <00b001d04f06$30ecae80$92c60b80$@huitema.net>
References: <00b001d04f06$30ecae80$92c60b80$@huitema.net>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 23 Feb 2015 16:16:04 -0500
Message-ID: <22729.1424726164@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/elWNymmUslhiDg3OjJgbBsiASVw>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Anonymity profile
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, 23 Feb 2015 21:16:12 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Christian Huitema <huitema@huitema.net> wrote:
    > Friday, I submitted a draft describing an =E2=80=9Canonymity profile=
=E2=80=9D for DHCP and
    > DHCPv6:

    > http://datatracker.ietf.org/doc/draft-huitema-dhc-anonymity-profile/

Re:
http://www.cbc.ca/news/politics/csec-used-airport-wi-fi-to-track-canadian-t=
ravellers-edward-snowden-documents-1.2517881

I followed some of this story, and my understanding is that CSEC didn't
actually have the ability to collect MAC addresses and DHCP data.  My
understanding is that they actually just watched http:// connections to
facebook.com, and collected the cookie info from there.

On my office network, one Android phone has MAC randomization turned on.
The result is that it gets a new address every few minutes, and our
monitoring tools that keep track of machines coming and going go bonkers.
They become unuseable to us, which means that our ability to keep our netwo=
rk
secure becomes difficult.

I'd really like to have hardware MAC "randomization" that is deterministic
based upon ESSID.  Then generate the DHCP DUID from that.
I think that it's really better for everyone if one uses the same MAC addre=
ss
each time one visits the same place.  It's true that this lets the owner of
that network determine that they have the same person back again each time.

Doing this by MAC address is certainly a lot better than having them
intercept HTTP connections (or as Lenovo is doing, intercept HTTPS...).
Having the same MAC address also means that I might get to skip the silly
captive portal.

Of course, I could have an application which changes my "personality", so
that I'd use different inputs to the deterministic MAC permutation algorith=
m,
and assume a different persona.  Or, my ten friends and I could rotate among
a set of 4 addresses to mess up traffic analysis. (Like the way some people
have a loyalty card that a group uses at the grocery store, but only ever b=
uy
apple juice with)

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOuYlICLcPvd0N1lAQKG6wf+MslmJD2g+p1DeHWjC7YXxVQE5Zvp6+0C
P1zmXGKC4v/4q0XAXxZNJME2Et2yhsgBU0wtr31hiW2ZcDQHRz0aPMBFyd+C+v5+
RCkImns+TF2F51TFpiRcX+ydAvjRiUFgnVpaJLTDYg9yGjxLtoIOBiFVzHWk4rfB
UJuWRQ9D8Hzj/5Lchi8b/Xu7ZCaHiJ4dezFJBFopHlFDZ1+luvVXL5a1hoSjZx12
B2rBwpnt+eykyGChGs23J6PbKziXQnmLN+i0DjLvBWxHIHY1XVinLEmezNoTfmpo
P+ijG0B0EcUbtZdD3bpIS1m3UyljdY7i8IGS1kU1ULnmICOmLuIgHw==
=ez/c
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Feb 23 13:41:55 2015
Return-Path: <huitema@microsoft.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 46F0A1A6FE9 for <dhcwg@ietfa.amsl.com>; Mon, 23 Feb 2015 13:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 MlNvzvXEeach for <dhcwg@ietfa.amsl.com>; Mon, 23 Feb 2015 13:41:53 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0120.outbound.protection.outlook.com [65.55.169.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B63FC1A6F10 for <dhcwg@ietf.org>; Mon, 23 Feb 2015 13:41:52 -0800 (PST)
Received: from DM2PR0301MB0653.namprd03.prod.outlook.com (25.160.96.15) by DM2PR0301MB0879.namprd03.prod.outlook.com (25.160.216.141) with Microsoft SMTP Server (TLS) id 15.1.87.18; Mon, 23 Feb 2015 21:41:51 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) by DM2PR0301MB0653.namprd03.prod.outlook.com (25.160.96.15) with Microsoft SMTP Server (TLS) id 15.1.99.9; Mon, 23 Feb 2015 21:41:46 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) by DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) with mapi id 15.01.0099.004; Mon, 23 Feb 2015 21:41:46 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [dhcwg] Anonymity profile
Thread-Index: AdBPBaF3OXJXtIILS9ekIvbKmNxVIQAqEzYAAACWKXA=
Date: Mon, 23 Feb 2015 21:41:46 +0000
Message-ID: <DM2PR0301MB06559349DD7A0E78F064A4E5A8290@DM2PR0301MB0655.namprd03.prod.outlook.com>
References: <00b001d04f06$30ecae80$92c60b80$@huitema.net> <22729.1424726164@sandelman.ca>
In-Reply-To: <22729.1424726164@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [131.107.192.254]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=huitema@microsoft.com; 
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0653; UriScan:; 
x-o365ent-eop-header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
x-microsoft-antispam-prvs: <DM2PR0301MB0653F41E1086DD87B66D1BB3A2290@DM2PR0301MB0653.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005003); SRVR:DM2PR0301MB0653; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0653; 
x-forefront-prvs: 0496DF6962
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(51444003)(199003)(189002)(110136001)(86362001)(86612001)(74316001)(2656002)(87936001)(106356001)(105586002)(99286002)(64706001)(66066001)(68736005)(102836002)(76576001)(50986999)(54356999)(76176999)(92566002)(2950100001)(2900100001)(33656002)(101416001)(97736003)(77156002)(62966003)(46102003)(122556002)(40100003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0653; H:DM2PR0301MB0655.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Feb 2015 21:41:46.2548 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0653
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0879;
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/cr2cjlwaTSmTd73qkRuwfbH-hjY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Anonymity profile
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, 23 Feb 2015 21:41:54 -0000

PiBPbiBteSBvZmZpY2UgbmV0d29yaywgb25lIEFuZHJvaWQgcGhvbmUgaGFzIE1BQyByYW5kb21p
emF0aW9uIHR1cm5lZA0KPiBvbi4NCj4gVGhlIHJlc3VsdCBpcyB0aGF0IGl0IGdldHMgYSBuZXcg
YWRkcmVzcyBldmVyeSBmZXcgbWludXRlcywgYW5kIG91cg0KPiBtb25pdG9yaW5nIHRvb2xzIHRo
YXQga2VlcCB0cmFjayBvZiBtYWNoaW5lcyBjb21pbmcgYW5kIGdvaW5nIGdvIGJvbmtlcnMuDQo+
IFRoZXkgYmVjb21lIHVudXNlYWJsZSB0byB1cywgd2hpY2ggbWVhbnMgdGhhdCBvdXIgYWJpbGl0
eSB0byBrZWVwIG91cg0KPiBuZXR3b3JrIHNlY3VyZSBiZWNvbWVzIGRpZmZpY3VsdC4NCg0KQSBu
ZXcgYWRkcmVzcyBldmVyeSBmZXcgbWludXRlcyBJIHByb2JhYmx5IGEgbG90IHRvbyBhZ2dyZXNz
aXZlLiBUaGVyZSBhcmUgbG90cyBvZiB1bmRlc2lyYWJsZSBzaWRlIGVmZmVjdHMuIEZvciBleGFt
cGxlLCBpZiB5b3UgYXJlIGF0IGEgaG90IHNwb3QgdGhhdCB1c2VzIHRoZSAiY2FwdGl2ZSBwb3J0
YWwiIGFwcHJvYWNoLCBjaGFuZ2luZyBNQUMgYWRkcmVzcyBicmluZ3MgeW91IGJhY2sgdG8gdGhl
IGNhcHRpdmUgcG9ydGFsLCBhbmQgdGhhdCdzIHJlYWxseSBhIHBhaW4gZm9yIHRoZSB1c2VyLiBB
bHNvLCBjaGFuZ2luZyBNQUMgYWRkcmVzcyBwcmV0dHkgbXVjaCBmb3JjZXMgeW91IHRvIGNoYW5n
ZSBJUCBhZGRyZXNzLiBJZiB5b3UgYXJlIGJlaGluZCBhIE5BVCwgdGhhdCBtZWFucyBoYXZpbmcg
dG8gcmVuZWdvdGlhdGUgYWxsIHRoZSBOQVQgdHJhdmVyc2FsIG1hcHBpbmdzLg0KDQo+IEknZCBy
ZWFsbHkgbGlrZSB0byBoYXZlIGhhcmR3YXJlIE1BQyAicmFuZG9taXphdGlvbiIgdGhhdCBpcyBk
ZXRlcm1pbmlzdGljDQo+IGJhc2VkIHVwb24gRVNTSUQuICBUaGVuIGdlbmVyYXRlIHRoZSBESENQ
IERVSUQgZnJvbSB0aGF0Lg0KDQpDb3JyZWN0LiBZb3Ugd2FudCBhdCBhIG1pbmltdW0gdG8ga2Vl
cCB0aGUgc2FtZSBNQUMgYmV0d2VlbiB0aGUgdGltZSB5b3UgY29ubmVjdCB0byB0aGUgV2ktRmkg
bmV0d29yayBhbmQgdGhlIHRpbWUgeW91IGRpc2Nvbm5lY3QuDQoNCj4gSSB0aGluayB0aGF0IGl0
J3MgcmVhbGx5IGJldHRlciBmb3IgZXZlcnlvbmUgaWYgb25lIHVzZXMgdGhlIHNhbWUgTUFDIGFk
ZHJlc3MNCj4gZWFjaCB0aW1lIG9uZSB2aXNpdHMgdGhlIHNhbWUgcGxhY2UuICBJdCdzIHRydWUg
dGhhdCB0aGlzIGxldHMgdGhlIG93bmVyIG9mIHRoYXQNCj4gbmV0d29yayBkZXRlcm1pbmUgdGhh
dCB0aGV5IGhhdmUgdGhlIHNhbWUgcGVyc29uIGJhY2sgYWdhaW4gZWFjaCB0aW1lLg0KDQpUaGF0
J3MgYSB0cmFkZW9mZiwgYmV0d2VlbiBzdGFiaWxpdHkgYW5kIHByaXZhY3kuIFRoZSBzdGFibGUg
cHJpdmFjeSBhZGRyZXNzZXMgZHJhZnQgY292ZXJzIHNvbWUgb2YgdGhlIHNhbWUgaXNzdWVzLiAN
Cg0KSSB3b25kZXIgaG93IG11Y2ggb2YgdGhlIE1BQyBhZGRyZXNzIHJhbmRvbWl6YXRpb24gc3Ry
YXRlZ3kgc2hvdWxkIGJlIGluY2x1ZGVkIGluIHRoZSBESENQIGFub255bWl0eSBkcmFmdC4gWW91
ciBmZWVkYmFjayBsZWFkcyBtZSB0byAibW9yZSB0aGFuIHdlIGhhdmUgbm93Li4uIg0KDQotLSBD
aHJpc3RpYW4gSHVpdGVtYQ0KDQoNCg==


From nobody Tue Feb 24 12:18:05 2015
Return-Path: <huitema@huitema.net>
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 F1E8E1A1E0F for <dhcwg@ietfa.amsl.com>; Tue, 24 Feb 2015 11:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable
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 tKawhYIbhwFE for <dhcwg@ietfa.amsl.com>; Tue, 24 Feb 2015 11:29:05 -0800 (PST)
Received: from xsmtp04.mail2web.com (xsmtp04.mail2web.com [168.144.250.231]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91A181A6F13 for <dhcwg@ietf.org>; Tue, 24 Feb 2015 11:29:05 -0800 (PST)
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1YQLAC-0003Np-IF for dhcwg@ietf.org; Tue, 24 Feb 2015 14:29:04 -0500
Received: (qmail 18311 invoked from network); 24 Feb 2015 19:28:59 -0000
Received: from unknown (HELO huitema1) (Authenticated-user:_huitema@huitema.net@[131.107.192.114]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dhcwg@ietf.org>; 24 Feb 2015 19:28:58 -0000
From: "Christian Huitema" <huitema@huitema.net>
To: "'Stephen Farrell'" <stephen.farrell@cs.tcd.ie>, <privsec-program@iab.org>
References: <014101d04d75$b7396a10$25ac3e30$@huitema.net> <54EC7A34.4030903@cs.tcd.ie>
In-Reply-To: <54EC7A34.4030903@cs.tcd.ie>
Date: Tue, 24 Feb 2015 11:28:57 -0800
Message-ID: <02ea01d05068$2327dbe0$697793a0$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQK6bLAz23ktUIju6x4r7YdzygxNgAJm9+D7mxizz6A=
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/ImUjYq-5uqx2EP6bizt62pDbelI>
X-Mailman-Approved-At: Tue, 24 Feb 2015 12:18:03 -0800
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] [Privsec-program] DHCP privacy
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: Tue, 24 Feb 2015 19:29:08 -0000

On Tuesday, February 24, 2015, at 5:19 AM, Stephen Farrell wrote
> To: Christian Huitema; privsec-program@iab.org
> Subject: Re: [Privsec-program] DHCP privacy
>=20
>=20
> And now having had a chance to read this properly:-) I still like
> the idea, but do have comments/questions...
>=20
> - How does this fit with the DHC work presented in Hawaii? [1] (Bear =
in
> mind I wasn't present, so the answer may be obvious to those who were
> there.)

I will answer the questions on the DHCP mailing list. The short answer =
is that I should have referenced the problem statement drafts that are =
worked on in the DHC WG.

> - Why not try a profile for servers too or instead?

Because I believe that client profile is much more urgent. The server =
part will be covered by the general mitigation work going on in DHC. I =
guess I should change the title to make it obvious that this is client =
specific.=20

Also, privacy issues really only apply to mobile servers. If the server =
is static, the privacy issues are not so important. In the case of =
mobile servers, such as your phone acting as a mini Wi-Fi hot spot, you =
get a lot of protection by just implementing something like WPA2, =
effectively making the whole network private.

> - If the client wishes to remain anonymous (or less identified =
perhaps)
> then wouldn't it be good if the client told the server about that in
> case the server is willing to co-operate?

We can have a philosophical debate about that. If you want to be =
anonymous in the street, do you walk around with a Guy Fawkes mask? Or =
do you just dress up like the average Joe? I don't like the idea that =
anonymous users would "stick out" by putting a special option in their =
requests.=20

Of course, there is a use case in which the server may want to =
cooperate. Suppose that an organization rents a suite in an office =
building, but does not want people on the other floors to monitor who is =
or is not in the office. They will instruct employees to use MAC Address =
Randomization on their devices. But then, they probably also want to =
control who has or has not access to the network. They could use for =
example something like 802.1x with PEAP TLS to control access to the =
network without providing observable identities in clear text.  So now =
you have a private network with observable identity on the outside. I am =
not sure that the anonymity profile applies, although I can see how the =
DHCP server should be instructed to provide, for example, randomized =
IPv6 addresses.

> - Intro: You mention fingerprinting. I think that either deserves a
> full section (or RFC) of it's own or else should only be mentioned as
> not something where we're saying how to mitigate it. RF fingerprinting
> would work ok for a DHCP server and WiFi client I guess and cannot be
> mitigated by anything here I think.

MAC address randomization solves the trivial monitoring problem in which =
someone just uses a Wi-Fi scanner and records the MAC addresses seen on =
the air. DHCP anonymity solves the more elaborated scenario in which =
someone monitor MAC addresses and identities at the access point or DHCP =
server. If you have a good way to solve RF fingerprinting, I am happy to =
look at it. But that is a bit far from DHCP.

> - section 2, 3rd last para: shouldn't there be some relationship
> between the (average) random address use-time and the DHCP lease
> duration?  Or at least shouldn't we propose something. That is tricky
> maybe but worth at least a mention even if only to say that there is =
no
> beneficial relationship that can help here.

I realize that the draft is missing a section explaining our hypotheses =
for MAC Address Randomization. I know of several possible strategies:

* Draw an address at the time of connecting to a network (e.g. to =
specific Wi-Fi SSID) and keep it for the duration of the connection.
    - Variant 1: always use the same MAC address for the same network
    - Variant 2: regularly change the address, so that a new connection =
to the same SSID may use a different MAC Address.

* Change the MAC address at regular time intervals.
   - On a Wi-Fi network, that causes a network =
disconnection/reconnection, and is thus pretty much equivalent to the =
variant 2 above.

In practice, there are many reasons to keep the MAC address constant for =
the time of a physical connection. Lots of annoying stuff happens if you =
change it. But yes, that should probably be explained in the draft.

> - s2, 2nd last para: privacy "more important than" n/w mgmt isn't the
> right way to put it I think (and would turn off a bunch of folks). I
> think what we want is that this is something for clients who care and
> servers who are ok that clients care.

I can change the wording to "when using the anonymity profile," and then =
add a section defining when to use it.

> - 3.1: I think you need to be clearer that you MUST NOT send this just
> after you change MAC address.

OK.

> - 3.4 (or 3.5 or 3.6): You could create a convention here to use these
> fields to tell the server the client wants to be less identified, e.g.
> if the values start with "PRIVATEPLEASE" or some such. (Same for some
> 4.x sections.)

I am really not sure about this kind of option. Reminds me of HTTP "Do =
not track" option...

> - MAC address change (and other) timing: say most clients using this
> change MAC address and other info every 90 minutes. And say that I do
> that at 7 minutes past the hour and you do it at 22 minutes past the
> hour. That timing could expose which of us is which. I think you need
> some guidance on such timing.

See discussion of address change strategies. One of the reasons I =
believe the MAC should stay constant during a connected session is =
precisely that it is very easy to detect that the same client is =
reconnecting, for example because it will reestablish pretty much the =
same set of TCP connections. So you get a lot of complexity and pain for =
not a lot of benefits.

> - section 6: shouldn't you say something about logging here? What is =
it
> safe for the server to log for clients like this?

The draft is pretty much a profile for clients, so I am not sure it =
should incorporate advice for servers. But if you have text...


> On 21/02/15 01:28, Christian Huitema wrote:
> > This might be of interest for the privacy program:
> >
> > http://datatracker.ietf.org/doc/draft-huitema-dhc-anonymity-profile/
> >
> >
> >
> > The idea there is to plug the DHCP hole, so that devices that use =
MAC
> > Address Randomization cannot be tracked through unique identifiers =
leaked
> by
> > DHCP.
> >
> >
> >
> > There is similar work going on IPv6 address privacy.
> >
> >
> >
> > I think of this kind of work as complementary to encryption. =
Encryption
> > protects the data between device and services, but does not protect =
the
> > =E2=80=9Cmetadata,=E2=80=9D such as IP addresses and other clear =
text headers. The most
> > obvious pieces of such metadata are the IP addresses, the link layer
> > addresses of wireless systems, and the DHCP information that links =
them.
> But
> > I am pretty sure that there are more sources of leakage, which I =
believe we
> > should track, analyze and fix. DHCP is just a first step.
> >
> >
> >
> > -- Christian Huitema
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Privsec-program mailing list
> > Privsec-program@iab.org
> > https://www.iab.org/mailman/listinfo/privsec-program
> >
>=20
> _______________________________________________
> Privsec-program mailing list
> Privsec-program@iab.org
> https://www.iab.org/mailman/listinfo/privsec-program


From nobody Tue Feb 24 15:14:22 2015
Return-Path: <stephen.farrell@cs.tcd.ie>
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 955D51A0076 for <dhcwg@ietfa.amsl.com>; Tue, 24 Feb 2015 15:14:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 dc8-WNuH8_qq for <dhcwg@ietfa.amsl.com>; Tue, 24 Feb 2015 15:14:17 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB1351A0058 for <dhcwg@ietf.org>; Tue, 24 Feb 2015 15:14:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6DFC3BEB0; Tue, 24 Feb 2015 23:14:15 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMXvusL8OudS; Tue, 24 Feb 2015 23:14:13 +0000 (GMT)
Received: from [10.87.48.73] (unknown [86.46.27.159]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D975ABE83; Tue, 24 Feb 2015 23:14:12 +0000 (GMT)
Message-ID: <54ED05C4.9050909@cs.tcd.ie>
Date: Tue, 24 Feb 2015 23:14:12 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Christian Huitema <huitema@huitema.net>, privsec-program@iab.org
References: <014101d04d75$b7396a10$25ac3e30$@huitema.net> <54EC7A34.4030903@cs.tcd.ie> <02ea01d05068$2327dbe0$697793a0$@huitema.net>
In-Reply-To: <02ea01d05068$2327dbe0$697793a0$@huitema.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/qdpzjQxtFmVGHamlYVGjFjx_ZqE>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] [Privsec-program] DHCP privacy
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: Tue, 24 Feb 2015 23:14:19 -0000

Hiya,

Most of your responses are just fine, a few responses below.

On 24/02/15 19:28, Christian Huitema wrote:
> On Tuesday, February 24, 2015, at 5:19 AM, Stephen Farrell wrote
>> To: Christian Huitema; privsec-program@iab.org Subject: Re:
>> [Privsec-program] DHCP privacy
>> 
>> 
>> And now having had a chance to read this properly:-) I still like 
>> the idea, but do have comments/questions...
>> 
>> - How does this fit with the DHC work presented in Hawaii? [1]
>> (Bear in mind I wasn't present, so the answer may be obvious to
>> those who were there.)
> 
> I will answer the questions on the DHCP mailing list. The short
> answer is that I should have referenced the problem statement drafts
> that are worked on in the DHC WG.
> 
>> - Why not try a profile for servers too or instead?
> 
> Because I believe that client profile is much more urgent. The server
> part will be covered by the general mitigation work going on in DHC.
> I guess I should change the title to make it obvious that this is
> client specific.
> 
> Also, privacy issues really only apply to mobile servers. If the
> server is static, the privacy issues are not so important.

I agree mobile servers have special privacy issues. I don't agree
that static servers don't create privacy issues for their clients.
Addressing that latter elsewhere is perhaps correct, but it needs
to not be forgotten. (So I think " privacy issues really only apply
to mobile servers" isn't correctly stated.)

> In the
> case of mobile servers, such as your phone acting as a mini Wi-Fi hot
> spot, you get a lot of protection by just implementing something like
> WPA2, effectively making the whole network private.

Well, presumably the (B|E)SSID chosen should be random-ish too. Maybe
that specific case should be in its own RFC though - folks coding
that up are probably not the usual DHCP server developer and might
need different/more guidance.

> 
>> - If the client wishes to remain anonymous (or less identified
>> perhaps) then wouldn't it be good if the client told the server
>> about that in case the server is willing to co-operate?
> 
> We can have a philosophical debate about that. If you want to be
> anonymous in the street, do you walk around with a Guy Fawkes mask?
> Or do you just dress up like the average Joe? I don't like the idea
> that anonymous users would "stick out" by putting a special option in
> their requests.

Yeah, fair enough.

> 
> Of course, there is a use case in which the server may want to
> cooperate. Suppose that an organization rents a suite in an office
> building, but does not want people on the other floors to monitor who
> is or is not in the office. They will instruct employees to use MAC
> Address Randomization on their devices. But then, they probably also
> want to control who has or has not access to the network. They could
> use for example something like 802.1x with PEAP TLS to control access
> to the network without providing observable identities in clear text.
> So now you have a private network with observable identity on the
> outside. I am not sure that the anonymity profile applies, although I
> can see how the DHCP server should be instructed to provide, for
> example, randomized IPv6 addresses.

Right. There are ways in which the DHCP server can help or hinder
in terms of making the client more or less trackable. Even if the
guidance on how to help wasn't at all normative, it might be worth
including somewhere.

> 
>> - Intro: You mention fingerprinting. I think that either deserves
>> a full section (or RFC) of it's own or else should only be
>> mentioned as not something where we're saying how to mitigate it.
>> RF fingerprinting would work ok for a DHCP server and WiFi client I
>> guess and cannot be mitigated by anything here I think.
> 
> MAC address randomization solves the trivial monitoring problem in
> which someone just uses a Wi-Fi scanner and records the MAC addresses
> seen on the air. DHCP anonymity solves the more elaborated scenario
> in which someone monitor MAC addresses and identities at the access
> point or DHCP server. If you have a good way to solve RF
> fingerprinting, I am happy to look at it. But that is a bit far from
> DHCP.

I don't have a solution no, but I think acking that nothing we're
doing here can overcome RF fingerprinting would seem right.

> 
>> - section 2, 3rd last para: shouldn't there be some relationship 
>> between the (average) random address use-time and the DHCP lease 
>> duration?  Or at least shouldn't we propose something. That is
>> tricky maybe but worth at least a mention even if only to say that
>> there is no beneficial relationship that can help here.
> 
> I realize that the draft is missing a section explaining our
> hypotheses for MAC Address Randomization. I know of several possible
> strategies:
> 
> * Draw an address at the time of connecting to a network (e.g. to
> specific Wi-Fi SSID) and keep it for the duration of the connection. 
> - Variant 1: always use the same MAC address for the same network -
> Variant 2: regularly change the address, so that a new connection to
> the same SSID may use a different MAC Address.
> 
> * Change the MAC address at regular time intervals. - On a Wi-Fi
> network, that causes a network disconnection/reconnection, and is
> thus pretty much equivalent to the variant 2 above.
> 
> In practice, there are many reasons to keep the MAC address constant
> for the time of a physical connection. Lots of annoying stuff happens
> if you change it. But yes, that should probably be explained in the
> draft.

So a stupid question: say if I use MAC-1 to get IP1 from server1
with lease1. Before lease1 is (half) over, I use a newly randomly
chosen MAC-2 to get IP2 from server1 using the same radio (say).
What'd break? What'd break that couldn't be handled via clever
client coding?

I suspect you're right that one random-MAC per e.g. WiFi session
is probably correct, but I think some more text saying that and
why might be needed. And I'm curious as to whether other options
may also work or not.

> 
>> - s2, 2nd last para: privacy "more important than" n/w mgmt isn't
>> the right way to put it I think (and would turn off a bunch of
>> folks). I think what we want is that this is something for clients
>> who care and servers who are ok that clients care.
> 
> I can change the wording to "when using the anonymity profile," and
> then add a section defining when to use it.
> 
>> - 3.1: I think you need to be clearer that you MUST NOT send this
>> just after you change MAC address.
> 
> OK.
> 
>> - 3.4 (or 3.5 or 3.6): You could create a convention here to use
>> these fields to tell the server the client wants to be less
>> identified, e.g. if the values start with "PRIVATEPLEASE" or some
>> such. (Same for some 4.x sections.)
> 
> I am really not sure about this kind of option. Reminds me of HTTP
> "Do not track" option...

Eek! But yes. If you do end up adding anything like that we should
call the flag "pretty please do not track, but I know you will" and
refer to RFC6919 :-)

> 
>> - MAC address change (and other) timing: say most clients using
>> this change MAC address and other info every 90 minutes. And say
>> that I do that at 7 minutes past the hour and you do it at 22
>> minutes past the hour. That timing could expose which of us is
>> which. I think you need some guidance on such timing.
> 
> See discussion of address change strategies. One of the reasons I
> believe the MAC should stay constant during a connected session is
> precisely that it is very easy to detect that the same client is
> reconnecting, for example because it will reestablish pretty much the
> same set of TCP connections. 

Yeah, there's an interesting study to be done there that I've not
seen I think. And a set of browser bookmarks would re-identify
pretty well too I guess, even if all are https, given SNI. However,
one problem at a time...

> So you get a lot of complexity and pain
> for not a lot of benefits.
> 
>> - section 6: shouldn't you say something about logging here? What
>> is it safe for the server to log for clients like this?
> 
> The draft is pretty much a profile for clients, so I am not sure it
> should incorporate advice for servers. But if you have text...

Nothing great but assuming there's some way for the server to
see a signal that the client would prefer to not be easily
tracked...

"Servers dealing with clients using this profile who want to
honour the client's wishes, ought minimise logging because
that may assist the client."

Cheers,
S.

> 
> 
>> On 21/02/15 01:28, Christian Huitema wrote:
>>> This might be of interest for the privacy program:
>>> 
>>> http://datatracker.ietf.org/doc/draft-huitema-dhc-anonymity-profile/
>>>
>>>
>>>
>>>
>>> 
The idea there is to plug the DHCP hole, so that devices that use MAC
>>> Address Randomization cannot be tracked through unique
>>> identifiers leaked
>> by
>>> DHCP.
>>> 
>>> 
>>> 
>>> There is similar work going on IPv6 address privacy.
>>> 
>>> 
>>> 
>>> I think of this kind of work as complementary to encryption.
>>> Encryption protects the data between device and services, but
>>> does not protect the “metadata,” such as IP addresses and other
>>> clear text headers. The most obvious pieces of such metadata are
>>> the IP addresses, the link layer addresses of wireless systems,
>>> and the DHCP information that links them.
>> But
>>> I am pretty sure that there are more sources of leakage, which I
>>> believe we should track, analyze and fix. DHCP is just a first
>>> step.
>>> 
>>> 
>>> 
>>> -- Christian Huitema
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________ Privsec-program
>>> mailing list Privsec-program@iab.org 
>>> https://www.iab.org/mailman/listinfo/privsec-program
>>> 
>> 
>> _______________________________________________ Privsec-program
>> mailing list Privsec-program@iab.org 
>> https://www.iab.org/mailman/listinfo/privsec-program
> 
> _______________________________________________ Privsec-program
> mailing list Privsec-program@iab.org 
> https://www.iab.org/mailman/listinfo/privsec-program
> 


From nobody Wed Feb 25 11:09:44 2015
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 AB7C01A1BF6 for <dhcwg@ietfa.amsl.com>; Wed, 25 Feb 2015 11:09:41 -0800 (PST)
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 uCvy_wNeG0-G for <dhcwg@ietfa.amsl.com>; Wed, 25 Feb 2015 11:09:40 -0800 (PST)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84B991A1B69 for <dhcwg@ietf.org>; Wed, 25 Feb 2015 11:09:40 -0800 (PST)
Received: by mail-ig0-f177.google.com with SMTP id z20so8445534igj.4 for <dhcwg@ietf.org>; Wed, 25 Feb 2015 11:09:39 -0800 (PST)
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=HBSKai4m6W8PIIcHrOLtCnHwzRezQP0O18G62T+Z3cY=; b=0FSP+X1kpUDuCoNWGHU7qdP0fCnRGdnCMkzvS1W+YMAbCMAsrUVMPVcQJzY+HO1aXy R2v0uxz+ceTe9PbLrFl94vix9M+xgc+9vbB6d3JpHQt1doh5tpIS+xHaiRz1Ju3uwFk/ 6/fD8DbQatvYPBVVNJSaA5r1NZITv9+ixO38OijAcrIDR5W2WI6xrEr8Z56g6ozRUG09 BvdrbOUgCa0D0mUHaeLX8tNpbXBb5RH0Gu0YjB9HGh5bNwagRypJ+n2zLJXF36uxCW9P Vi0LkK0Chwm9uI6o8pkdXvtz8BFganOmZwhqfhc4Vr5x5D3w2kw2VxS5iE10IlPY3rIs kXog==
MIME-Version: 1.0
X-Received: by 10.107.10.74 with SMTP id u71mr6910991ioi.0.1424891379725; Wed, 25 Feb 2015 11:09:39 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Wed, 25 Feb 2015 11:09:39 -0800 (PST)
In-Reply-To: <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com>
Date: Wed, 25 Feb 2015 11:09:39 -0800
X-Google-Sender-Auth: xdFVq6dCnPiIhCmJgXKoZkyXWD4
Message-ID: <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/JaEeFKmJHamXRkX2dytyZkAAFv4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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, 25 Feb 2015 19:09:41 -0000

At Sat, 21 Feb 2015 19:03:06 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> Okay.   I think the discussion is useful, but we have no action
> item.   The question is whether Jinmei-san and Ralph can live with
> not trying to document use cases.   I think that the standard ought
> to be along the lines of what's documented in RFC 7282, though--I
> don't think we're going to get to complete consensus on this.

As (I believe) I stated before, I'm okay with not documenting specific
use cases per se.  But that's because describing use cases are just an
attempt to explain why we need this mechanism (and why the existing
mechanism does not answer it), especially for the case of
client->server authentication.  I'm totally okay with removing the use
case discussion if we can reasonably answer this question in some
other way, but I'm not yet okay with completely ignoring the question.

In that sense I'd still love to see an answer to my specific question:
http://www.ietf.org/mail-archive/web/dhcwg/current/msg16268.html
(aside from whether to include that answer in the final document).

I can see how a public-key based authentication is "strictly more
secure" (while reducing deployment cost) in the case of
"server->client" authentication.  But it's not at all clear to me for
the case of "client->server".  Maybe this is too obvious to some
others, but I hope someone could clarify this for some non-security
experts like me.

--
JINMEI, Tatuya


From nobody Wed Feb 25 11:30:48 2015
Return-Path: <Ted.Lemon@nominum.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 8DE7F1A700A for <dhcwg@ietfa.amsl.com>; Wed, 25 Feb 2015 11:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 TpnBvHpOQ89q for <dhcwg@ietfa.amsl.com>; Wed, 25 Feb 2015 11:30:44 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B66971A1EB7 for <dhcwg@ietf.org>; Wed, 25 Feb 2015 11:30:44 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 9BCA6DA01F2 for <dhcwg@ietf.org>; Wed, 25 Feb 2015 19:30:44 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 7225053E0AB; Wed, 25 Feb 2015 11:30:44 -0800 (PST)
Received: from CAS-04.WIN.NOMINUM.COM (64.89.235.67) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 25 Feb 2015 11:30:44 -0800
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 25 Feb 2015 11:30:43 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com>
Date: Wed, 25 Feb 2015 14:30:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Y0SQQO52bIXR1PFvJKZfzXcVPo0>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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, 25 Feb 2015 19:30:46 -0000

On Feb 25, 2015, at 2:09 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> In that sense I'd still love to see an answer to my specific question:
> http://www.ietf.org/mail-archive/web/dhcwg/current/msg16268.html
> (aside from whether to include that answer in the final document).

Here's the question:

> It's still vague to me...specifically what kind of attack should we
> worry about in the case of client->server authentication when we use
> the shared secret mechanism, and in which sense is it more serious
> than with the public/private key mechanism?

What we are trying to do with the public key is to identify a client and =
authenticate the client's identity.   If you want to phrase it in terms =
of preventing an attack, the attack it prevents is one client presenting =
another client's identity and getting access to the second client's =
resources because the credential it presents is never authenticated.

But in practice, as a general rule we simply don't ever bother to treat =
clients as having meaningful identities, because there is no way to =
authenticate them.   So we aren't trying to prevent an attack, really.   =
We are trying to provide an enabling technology that allows the network =
infrastructure to do something new, that it couldn't previously do.


From nobody Thu Feb 26 10:04:49 2015
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 4DF5E1A9083 for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 10:04:46 -0800 (PST)
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 krfR_7bQFHbE for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 10:04:45 -0800 (PST)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 358DD1A90AD for <dhcwg@ietf.org>; Thu, 26 Feb 2015 10:04:45 -0800 (PST)
Received: by iecrd18 with SMTP id rd18so18656446iec.8 for <dhcwg@ietf.org>; Thu, 26 Feb 2015 10:04:44 -0800 (PST)
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=BKli+hSoCoAq4qXt7fL3BoENYez4zlhPlyr8J+hrj5g=; b=bwtdMfmHj83E/BaIADyvwYTcLOERWumacbcjKIXYMzoy/QvbmVN2ggG/x1esexYZUB WtkURaAfrOJRabwfX+dnpGNrjoXSFR0KQYH+OQhU3/AXZFPEgv99cT3Vd5hZxhVCu0Ep ious9O9O+O97cFOGfP/03GpHQduJi2xMUMeqWMftoN9P7B60QJyj/xa8PZ3kvmpk4Dby RiWxZ0FP/1R4SOIcJb8uat3mk1wZQaorttZgDUGMXNsO+q+7lx5eYxtgqgkCyfAd6p3S +oTDhMIym7OCo1rJSD5g+5DsYByVF0LGZEF5jr7jMU3S5ggk3sS0PYZqsWuJlGRzQOeG Y6Zg==
MIME-Version: 1.0
X-Received: by 10.43.44.69 with SMTP id uf5mr2178438icb.6.1424973884464; Thu, 26 Feb 2015 10:04:44 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Thu, 26 Feb 2015 10:04:44 -0800 (PST)
In-Reply-To: <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com>
Date: Thu, 26 Feb 2015 10:04:44 -0800
X-Google-Sender-Auth: mbSu5xLKbd-8nbjyMyn4dOHACkM
Message-ID: <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/AZlVcL4MW5fxb4DgoFubNCWAnNY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 26 Feb 2015 18:04:46 -0000

At Wed, 25 Feb 2015 14:30:36 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > It's still vague to me...specifically what kind of attack should we
> > worry about in the case of client->server authentication when we use
> > the shared secret mechanism, and in which sense is it more serious
> > than with the public/private key mechanism?
>
> What we are trying to do with the public key is to identify a client and =
authenticate the client's identity.   If you want to phrase it in terms of =
preventing an attack, the attack it prevents is one client presenting anoth=
er client's identity and getting access to the second client's resources be=
cause the credential it presents is never authenticated.
>
> But in practice, as a general rule we simply don't ever bother to treat c=
lients as having meaningful identities, because there is no way to authenti=
cate them.   So we aren't trying to prevent an attack, really.   We are try=
ing to provide an enabling technology that allows the network infrastructur=
e to do something new, that it couldn't previously do.

I guess the point of my question is what's the "something new, that it
couldn't previously do."?  Can you be a bit more specific about it?
Or, did you mean "we don't know what it is"?

--
JINMEI, Tatuya


From nobody Thu Feb 26 10:47:39 2015
Return-Path: <Ted.Lemon@nominum.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 4E7E81A1A7F for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 10:47:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 ApwDU2BA6jzy for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 10:47:37 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 924F21A19F4 for <dhcwg@ietf.org>; Thu, 26 Feb 2015 10:47:37 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 6F82BDA0229 for <dhcwg@ietf.org>; Thu, 26 Feb 2015 18:47:37 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 3A3E553E0B1; Thu, 26 Feb 2015 10:47:37 -0800 (PST)
Received: from CAS-04.WIN.NOMINUM.COM (64.89.235.67) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 26 Feb 2015 10:47:36 -0800
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 26 Feb 2015 10:47:36 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com>
Date: Thu, 26 Feb 2015 13:47:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/7yicAw4RY9U2VwxDQnASqPgy4zs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 26 Feb 2015 18:47:38 -0000

On Feb 26, 2015, at 1:04 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> Can you be a bit more specific about it?
> Or, did you mean "we don't know what it is"?

>> What we are trying to do with the public key is to identify a client =
and authenticate the client's identity.


From nobody Thu Feb 26 11:27:57 2015
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 B550B1A049C for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 11:27:55 -0800 (PST)
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 DnWE3tDFPoTe for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 11:27:55 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF3201AC3AE for <dhcwg@ietf.org>; Thu, 26 Feb 2015 11:27:54 -0800 (PST)
Received: by iecrp18 with SMTP id rp18so19827399iec.9 for <dhcwg@ietf.org>; Thu, 26 Feb 2015 11:27:54 -0800 (PST)
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=KAHW34+z3TbihqgCj6GNRn1m0HYS67WPS+FiOtEMwCA=; b=ZJ+wnnqsVLErA6ET68mjVhkPa1fGCQsnRrpOQQHphh9GfdhnqvzPhanW3RGt2IJaOM Lkc9okXwwm8ZwTGvIYljBb0B5cWDfpuDjKzLc6fBNjVEi79boWyNg7mX1fEC38vUmNZM 7EWxgm4M5jKGmK+6Gs3eqy0a8BA784SEhW3FCY+wzsGN/B8YH8mCkjFet/itwKNxufxw IVdDJONavfD7OQZvP16iOmVY3Wa5Bff1StRLHeAhfnm55t0GJ+oB4aT9JhmXRkb4ImJL 4H7CfAcTL7tYZXGSmntXb5hi3ty+pj0CnnnNgXlNZZVsf6mbvl3BMBoI6sefs3/gdsRR +ctQ==
MIME-Version: 1.0
X-Received: by 10.50.18.49 with SMTP id t17mr13740011igd.3.1424978873983; Thu, 26 Feb 2015 11:27:53 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Thu, 26 Feb 2015 11:27:53 -0800 (PST)
In-Reply-To: <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com>
Date: Thu, 26 Feb 2015 11:27:53 -0800
X-Google-Sender-Auth: K7Bj21hKwCx0tSjRPG3zP4d3bQU
Message-ID: <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/kpxVa74P4MeBpghM5ku97UyRCvM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 26 Feb 2015 19:27:55 -0000

At Thu, 26 Feb 2015 13:47:27 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > Can you be a bit more specific about it?
> > Or, did you mean "we don't know what it is"?
>
> >> What we are trying to do with the public key is to identify a client and authenticate the client's identity.

But can't we do this with the RFC3315-based shared secret mechanism
with a comparable operational cost and security level?  I still don't
see what's essentially new with the public key based mechanism...

--
JINMEI, Tatuya


From nobody Thu Feb 26 12:36:43 2015
Return-Path: <Ted.Lemon@nominum.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 14C491A70FE for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 12:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 n5ny_g9bs_kT for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 12:36:41 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 589371A1B6B for <dhcwg@ietf.org>; Thu, 26 Feb 2015 12:36:41 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id C180EDA021B for <dhcwg@ietf.org>; Thu, 26 Feb 2015 20:36:40 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 9506F53E0B1; Thu, 26 Feb 2015 12:36:40 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 26 Feb 2015 12:36:40 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com>
Date: Thu, 26 Feb 2015 15:36:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Mw1QgzrTqvLKP5L5ZVCjXqndfCY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Thu, 26 Feb 2015 20:36:42 -0000

On Feb 26, 2015, at 2:27 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> But can't we do this with the RFC3315-based shared secret mechanism
> with a comparable operational cost and security level?

No, because it uses shared secrets, and doesn't provide a way to =
establish the shared secret.


From nobody Thu Feb 26 16:52:24 2015
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 08CAD1A0074 for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 16:52:19 -0800 (PST)
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 yIu-Nf093LSS for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 16:52:18 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F201D1A0066 for <dhcwg@ietf.org>; Thu, 26 Feb 2015 16:52:17 -0800 (PST)
Received: by iecrl12 with SMTP id rl12so23646062iec.2 for <dhcwg@ietf.org>; Thu, 26 Feb 2015 16:52:17 -0800 (PST)
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=IEqO5MUc/3Z84WijXAwgo7ZFW25gBC/bdV6r7lY4y38=; b=H2VxsoC6kT/6uyY8OplXoAE7UkiteVutr8nsZ4UpWs01WBaZS0G1/WFCN7cGfrWjOw 1f95rwVBshBt467J54MndLvk6yhUXt06lKvNplG3KCyzQGYBgq4SbUpiFOQxWRQSQL/X BgzIqPJFFi6UrMJuqL0RBSzlRVNH/BOEGQN+udLF2UlRSZpBiUxC2vv0HauPTtotcaNv epmibK5zv1OXLeJ1zIxnleri+/a8l/84HU6Y8I4hIjwxb5y3ufqZ0TGeBZ3u3R5/UBnF bYsfgnd0XGx9EZeBNzx01ALXotAzh1QJf/tsZFngAJK1N95qqJLu4tnxO/zzcW4femN5 X8wA==
MIME-Version: 1.0
X-Received: by 10.50.142.38 with SMTP id rt6mr965739igb.17.1424998337040; Thu, 26 Feb 2015 16:52:17 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Thu, 26 Feb 2015 16:52:16 -0800 (PST)
In-Reply-To: <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com>
Date: Thu, 26 Feb 2015 16:52:16 -0800
X-Google-Sender-Auth: HH4c1magOG0d2xo8VpoeJalUN8Q
Message-ID: <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/yLSEow5ISP2u-9kK9XOK4OD186Y>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 00:52:19 -0000

At Thu, 26 Feb 2015 15:36:30 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > But can't we do this with the RFC3315-based shared secret mechanism
> > with a comparable operational cost and security level?
>
> No, because it uses shared secrets, and doesn't provide a way to establish the shared secret.

But we don't have a secure and practical way of installing clients'
public keys on the server, either, right?  We could manually copy the
clients' public keys to the server, but we could do so for clients'
shared secrets.

So, in the practical sense I still don't see a fundamental difference
between the public key based mechanism and shared secret based one.
I'm afraid I'm sounding too dumb and may look someone who can't
understand something too obvious to others, but could you, or someone
else, show a very specific example that can explain how exactly the
public key based mechanism is safer and less operationally expensive
than the shared secret mechanism for client authentication?

--
JINMEI, Tatuya


From nobody Thu Feb 26 18:51:55 2015
Return-Path: <Ted.Lemon@nominum.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 287771A1A4F for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 18:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 FIjhno7SPfvz for <dhcwg@ietfa.amsl.com>; Thu, 26 Feb 2015 18:51:53 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D4771A004A for <dhcwg@ietf.org>; Thu, 26 Feb 2015 18:51:53 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 40237DA01EF for <dhcwg@ietf.org>; Fri, 27 Feb 2015 02:51:53 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id E924753E0B1; Thu, 26 Feb 2015 18:51:52 -0800 (PST)
Received: from CAS-04.WIN.NOMINUM.COM (64.89.235.67) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 26 Feb 2015 18:51:53 -0800
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 26 Feb 2015 18:51:52 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com>
Date: Thu, 26 Feb 2015 21:51:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/G5DaN_0GQzjkvZJ12MZTYwsY348>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 02:51:54 -0000

On Feb 26, 2015, at 7:52 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> But we don't have a secure and practical way of installing clients'
> public keys on the server, either, right?  We could manually copy the
> clients' public keys to the server, but we could do so for clients'
> shared secrets.

The client sends its public key in the DHCP message, so the key is on =
the server the first time the client communicates with it.  There is no =
equivalent flow for shared secrets.


From nobody Fri Feb 27 07:47:18 2015
Return-Path: <niall.oreilly@ucd.ie>
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 343C61ACD61 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 07:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 d4ZT2MHqg2QL for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 07:47:15 -0800 (PST)
Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED2EC1ACD59 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 07:47:14 -0800 (PST)
Received: by wghk14 with SMTP id k14so21245978wgh.3 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 07:47:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:message-id:to:cc:subject:in-reply-to :references:user-agent:mime-version:content-type; bh=A2a/+rEgvVosSm8qFsX1wapnH/g7T37TLC3VhC7qGzE=; b=GoXW5dArNaaTebYvhjJ/bUb2quVimGl1p5+V4uubsi8tG3SFe6Tqhy22CgyRpNQ1p9 wi+KXTo3VD+DGiLb373cmFKXiKcUgQg56C8vR5Jo2QVYi29lLVsSbHwV32mp4rridZUI HlaSJOLU5lZ7IfMXdRUAsW4cdpIoM/Z2YIn9kVG86/6GZ50U8tuluFDgbPqlB9Caz38O w4WbFZe9lpUiKgo5CMWgsNSsnP14NOQ5ayV2MX9EX9aTS/HM0T6YITo8ME0evi7I1XpK 8Nnbz9M3nal1BvdKTA2VMVLaMjBTNGNlA+dB7nU1KHI1X4PanBvveZ99qFCelJljyaCv wdxQ==
X-Gm-Message-State: ALoCoQnyyG/JLm4ZFfPcbu7Xgd66E2GqPsChq+jgfxy1N0QAePFmTTRrJBjC383Ap0ccqAIk9Goi
X-Received: by 10.194.79.226 with SMTP id m2mr28960062wjx.60.1425052033716; Fri, 27 Feb 2015 07:47:13 -0800 (PST)
Received: from dhcp-179.wlan.no8.be.ucd.ie ([2001:770:13f:1:9844:703d:11b6:4d5b]) by mx.google.com with ESMTPSA id dt7sm3305882wib.19.2015.02.27.07.47.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Feb 2015 07:47:12 -0800 (PST)
From: "Niall O'Reilly" <niall.oreilly@ucd.ie>
X-Google-Original-From: Niall O'Reilly <Niall.oReilly@ucd.ie>
Date: Fri, 27 Feb 2015 15:47:10 +0000
Message-ID: <m2vbinz79d.wl-Niall.oReilly@ucd.ie>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.4 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/231TJjwr2Wa2mS5oRzI5c66lBLg>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>, =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 15:47:16 -0000

On Fri, 27 Feb 2015 02:51:37 +0000,
Ted Lemon wrote:
> 
> The client sends its public key in the DHCP message, so the key is
> on the server the first time the client communicates with it.

  So, TOFU?

  That should be fine, provided that the process for creating each
  distinct (physical or virtual) client results in a distinct
  identity.

  Best regards,
  Niall O'Reilly
  


From nobody Fri Feb 27 08:24:44 2015
Return-Path: <Ted.Lemon@nominum.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 860381ACDBA for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 08:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 Bws6qdq8-ZPA for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 08:24:39 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 353FF1ACDBC for <dhcwg@ietf.org>; Fri, 27 Feb 2015 08:24:37 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 1E53BDA01DB for <dhcwg@ietf.org>; Fri, 27 Feb 2015 16:24:37 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id EB6F253E0AC; Fri, 27 Feb 2015 08:24:36 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 08:24:36 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <m2vbinz79d.wl-Niall.oReilly@ucd.ie>
Date: Fri, 27 Feb 2015 11:24:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <m2vbinz79d.wl-Niall.oReilly@ucd.ie>
To: Niall O'Reilly <niall.oreilly@ucd.ie>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pB92idq3hl0VMnNySEb_6fE7qBU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 16:24:42 -0000

On Feb 27, 2015, at 10:47 AM, Niall O'Reilly <niall.oreilly@ucd.ie> =
wrote:
>  So, TOFU?

Depends on what you are trying to do.   If you just want to make sure =
that client A doesn't swipe client B's resources, TOFU is all you need.  =
 If you want to do some kind of RADIUS transaction, as we talked about =
previously, there's probably some sort of captive portal registration =
process.


From nobody Fri Feb 27 09:14:43 2015
Return-Path: <stenc@s-carlsen.dk>
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 4965D1ACDBB for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 09:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.892
X-Spam-Level: 
X-Spam-Status: No, score=-0.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DK=1.009, 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 7bZLZ4LF72jl for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 09:14:41 -0800 (PST)
Received: from mail2.s-carlsen.dk (0134100024.2.fullrate.dk [90.184.223.34]) by ietfa.amsl.com (Postfix) with ESMTP id C2A0A1ACE99 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 09:14:40 -0800 (PST)
Received: from silver4-wire.s-carlsen.dk (silver4-wire.s-carlsen.dk [192.168.16.157]) by mail2.s-carlsen.dk (Postfix) with ESMTPA id EFD481BB88 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 18:14:05 +0100 (CET)
Message-ID: <54F0A5DD.1060906@s-carlsen.dk>
Date: Fri, 27 Feb 2015 18:14:05 +0100
From: Sten Carlsen <stenc@s-carlsen.dk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <m2vbinz79d.wl-Niall.oReilly@ucd.ie> <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com>
In-Reply-To: <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/8M7r2Ubhvf3KRM8MgFmpomHGATU>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 17:14:42 -0000

On 27/02/15 17:24, Ted Lemon wrote:
> On Feb 27, 2015, at 10:47 AM, Niall O'Reilly <niall.oreilly@ucd.ie> wrote:
>>  So, TOFU?
> 
> Depends on what you are trying to do.   If you just want to make sure that client A doesn't swipe client B's resources, TOFU is all you need.   If you want to do some kind of RADIUS transaction, as we talked about previously, there's probably some sort of captive portal registration process.
Would signing the client cert with a particular root cert allow another
level of control? If the client cert is signed by the correct party, it
is admitted - if not, it is rejected.

Just a thought.
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"


From nobody Fri Feb 27 09:33:12 2015
Return-Path: <niall.oreilly@ucd.ie>
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 3718D1ACDE4 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 09:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 cVLuO02GLjaJ for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 09:33:09 -0800 (PST)
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0ABB1A0264 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 09:33:08 -0800 (PST)
Received: by wesw55 with SMTP id w55so21727164wes.4 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 09:33:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:message-id:to:cc:subject:in-reply-to :references:user-agent:mime-version:content-type; bh=6zgU1Hbg5zYWqF2mfg1djbW7WYs/h4J5Jg7w5ovLIms=; b=PE9REuVUDgY9AoXC3ocHSoP/8yXXpkDshBqQMO3hmJfIVaBzqThNJc/QVYIA2Pnwxp X5dJA8k8NPLndFJYM1D9tH2ZPvvxEeQsgP2EN+QnuKsVOJjfvGgjEztUkzRt0IlrBp1b Ciif8cH46XY9G+egW/zWH9tES4CJPFgSOnOHTFuE376c/bIM6vEcCfMWzN75npbRg4e8 63QoHLwQYulaRhQDWIhEqZLy6hKtH8LyWFdv7oQ0HEfWNvC/VPIry2oXwXR1S/vSD7W7 Fj9ylXjDL4hWJg4qO3R7r+jqpAzrQszsV/kX9j0lR1lQqmnvXPfFgcQFbYTqlVBW90Rt /gtA==
X-Gm-Message-State: ALoCoQnRsvVSjxtkaKDGI7Z0DeCQxLoTyO6CdoiEo08d0TGGoVg2oYbCkoziLn2qg4UU8yqDoC64
X-Received: by 10.194.61.51 with SMTP id m19mr30203333wjr.39.1425058387694; Fri, 27 Feb 2015 09:33:07 -0800 (PST)
Received: from dhcp-179.wlan.no8.be.ucd.ie ([2001:770:13f:1:9844:703d:11b6:4d5b]) by mx.google.com with ESMTPSA id gf11sm3704612wic.18.2015.02.27.09.33.06 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Feb 2015 09:33:06 -0800 (PST)
From: "Niall O'Reilly" <niall.oreilly@ucd.ie>
X-Google-Original-From: Niall O'Reilly <Niall.oReilly@ucd.ie>
Date: Fri, 27 Feb 2015 17:33:05 +0000
Message-ID: <m2sidrz2cu.wl-Niall.oReilly@ucd.ie>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <m2vbinz79d.wl-Niall.oReilly@ucd.ie> <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.4 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/uktMFU8wSOEz5ORExRzLfPlPkNQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>, =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 17:33:11 -0000

On Fri, 27 Feb 2015 16:24:31 +0000,
Ted Lemon wrote:
> 
> On Feb 27, 2015, at 10:47 AM, Niall O'Reilly <niall.oreilly@ucd.ie> wrote:
> >  So, TOFU?
> 
> Depends on what you are trying to do.  If you just want to make sure
> that client A doesn't swipe client B's resources, TOFU is all you
> need.

  That's what I thought you meant.
  Thanks for confirming.


  Best regards,
  Niall O'Reilly


From nobody Fri Feb 27 11:13:17 2015
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 88A6F1AD0CB for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:13:16 -0800 (PST)
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 qpXPYh-jErLj for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:13:15 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54EB91AD0B7 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:13:15 -0800 (PST)
Received: by iecar1 with SMTP id ar1so33365028iec.11 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:13:14 -0800 (PST)
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=2tTodX5z+r6XnMx0o7r9zjHYVnqgoR9D1KKgU4CBZgY=; b=sbd9OyejYJV4yxJ6b8ntCgEfT6di/2QM/xpc3OKl0f8fOSc7R1bJttXly8MA2oKjK3 lqTJz0A0W1wnvRX6PBvfKvpX6elWSNrTKQVV3PBpHLbL28tptAQfzCtFSIIiFrJ1cK/q oTxp524I7WcB+zuAsNWtOspZUQlLg4dW6ZAO1LTRHHF1OaAbuVD4RaLTsV+BVRQ7AEsH CftbEVsrjaFdgZQfXxStqbVCUg96y8Z/EpCtcDp9qcM2SBGLvyrESuAr1UlmCJp+nQOp 24iQjXC+aqw1uT+gjOGPMbZ/nKh8tJbPvZkMhqtVUGG/9xjQUEAVGRIpIiKT9Ej9WJRM Zlgw==
MIME-Version: 1.0
X-Received: by 10.107.10.74 with SMTP id u71mr21061100ioi.0.1425064394631; Fri, 27 Feb 2015 11:13:14 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Fri, 27 Feb 2015 11:13:14 -0800 (PST)
In-Reply-To: <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com>
Date: Fri, 27 Feb 2015 11:13:14 -0800
X-Google-Sender-Auth: AluXv5It8f5uh-jHmt7B-ocVQTM
Message-ID: <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/vsRsyrtzTnAy2a1eS37SoUEJ2bI>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 19:13:16 -0000

At Thu, 26 Feb 2015 21:51:37 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > But we don't have a secure and practical way of installing clients'
> > public keys on the server, either, right?  We could manually copy the
> > clients' public keys to the server, but we could do so for clients'
> > shared secrets.
>
> The client sends its public key in the DHCP message, so the key is
> on the server the first time the client communicates with it.  There
> is no equivalent flow for shared secrets.
[...]
At Fri, 27 Feb 2015 11:24:31 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:
> >  So, TOFU?
>
> Depends on what you are trying to do.   If you just want to make
> sure that client A doesn't swipe client B's resources, TOFU is all
> you need.

In this case, it doesn't even have to be TOFU (in its usual sense);
the server only needs to remember the client's public key during the
specific DHCPv6 session.  But, yes, I see the advantage of the public
key based mechanism in this case, although I'm personally not sure if
this is really a serous threat that we want to prevent by introducing
a new protocol.

> If you want to do some kind of RADIUS transaction, as we
> talked about previously, there's probably some sort of captive
> portal registration process.

And, in this case, it could also be a shared secret-based mechanism
without any essential difference in terms of operational cost and
security level, correct?  The client would create a secret, and
register it at the portal.  The server would retrieve the secret from
the portal and they can securely share the secret.

Am I understanding it correctly so far?

--
JINMEI, Tatuya


From nobody Fri Feb 27 11:17:36 2015
Return-Path: <Ted.Lemon@nominum.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 86C6D1AC3C0 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 icMBJUrUxgh7 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:17:31 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87E251AC3BC for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:17:31 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 3B40CDA022C for <dhcwg@ietf.org>; Fri, 27 Feb 2015 19:17:31 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 10CE453E0AC; Fri, 27 Feb 2015 11:17:31 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 11:17:31 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <54F0A5DD.1060906@s-carlsen.dk>
Date: Fri, 27 Feb 2015 14:17:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A5C69FCC-77DB-427F-ABFA-C33E8D7F3138@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <m2vbinz79d.wl-Niall.oReilly@ucd.ie> <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com> <54F0A5DD.1060906@s-carlsen.dk>
To: Sten Carlsen <stenc@s-carlsen.dk>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Dce1dwd9YQl06rruGllDJDrzHsc>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 19:17:35 -0000

On Feb 27, 2015, at 12:14 PM, Sten Carlsen <stenc@s-carlsen.dk> wrote:
> Would signing the client cert with a particular root cert allow =
another
> level of control? If the client cert is signed by the correct party, =
it
> is admitted - if not, it is rejected.

We already discussed that.   I don't think it's a very useful flow.   =
Generally speaking, if you want access control for clients, signing =
their public key just adds an extra step.   You could have a flow a lot =
like the flow we have now where the MAC address is added to a database =
in the receiving department, and then the key for that device is =
connected to the MAC address the first time the DHCP server sees it.


From nobody Fri Feb 27 11:24:22 2015
Return-Path: <Ted.Lemon@nominum.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 C05661AC3BC for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 lgc_F0NM_XfF for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:24:20 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BA761A92DD for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:24:19 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id E12D7DA0202 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 19:24:19 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id CA83053E0AC; Fri, 27 Feb 2015 11:24:19 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 11:24:19 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com>
Date: Fri, 27 Feb 2015 14:24:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <C64E7F5E-82C5-4A80-804E-78912F4CC514@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/lap2vbjhYT8hjmBJTJjIfPUyweM>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 19:24:20 -0000

On Feb 27, 2015, at 2:13 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> And, in this case, it could also be a shared secret-based mechanism
> without any essential difference in terms of operational cost and
> security level, correct?  The client would create a secret, and
> register it at the portal.  The server would retrieve the secret from
> the portal and they can securely share the secret.

There would be a shared secret in the RADIUS transaction, but not in the =
DHCP transaction.   Who generates the secret is out of scope (indeed, =
the whole RADIUS part of the flow is out of scope) but you are probably =
right that it's done through some kind of user registration process =
where the user enters a password.

Of course, this flow is actually a really bad idea--it would be much =
better to use the public key for the whole thing, so that there is no =
shared secret and no risk of the end user choosing a weak password, so =
if I were designing such a flow from scratch I would not used a shared =
secret at all.   The only reason to support this flow is that it would =
work with existing installations and is better than what we have now.


From nobody Fri Feb 27 11:41:24 2015
Return-Path: <huitema@microsoft.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 40F6C1AD1BA for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:41:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 2sullVj4iBYY for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:41:19 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0116.outbound.protection.outlook.com [65.55.169.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 165781AD0AF for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:41:03 -0800 (PST)
Received: from DM2PR0301MB0653.namprd03.prod.outlook.com (25.160.96.15) by DM2PR0301MB1216.namprd03.prod.outlook.com (25.160.219.17) with Microsoft SMTP Server (TLS) id 15.1.93.16; Fri, 27 Feb 2015 19:41:01 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (25.160.96.17) by DM2PR0301MB0653.namprd03.prod.outlook.com (25.160.96.15) with Microsoft SMTP Server (TLS) id 15.1.99.9; Fri, 27 Feb 2015 19:41:00 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) by DM2PR0301MB0655.namprd03.prod.outlook.com ([25.160.96.17]) with mapi id 15.01.0099.004; Fri, 27 Feb 2015 19:41:00 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Sten Carlsen <stenc@s-carlsen.dk>
Thread-Topic: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
Thread-Index: AQHQUS6aY8w/I0QT1kqdJ+k6Czrc0J0BwLEAgAF6VwCAAAvwgIAAC0yAgAATKwCAAEd2AIAAIVmAgADYrwCAAApwgIAADdmAgAAieICAAAG4YA==
Date: Fri, 27 Feb 2015 19:41:00 +0000
Message-ID: <DM2PR0301MB065541C0B4CDD4D371F07D2AA8150@DM2PR0301MB0655.namprd03.prod.outlook.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <m2vbinz79d.wl-Niall.oReilly@ucd.ie> <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com> <54F0A5DD.1060906@s-carlsen.dk> <A5C69FCC-77DB-427F-ABFA-C33E8D7F3138@nominum.com>
In-Reply-To: <A5C69FCC-77DB-427F-ABFA-C33E8D7F3138@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ed31::2]
authentication-results: nominum.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0653; UriScan:; 
x-microsoft-antispam-prvs: <DM2PR0301MB0653EE067F223DBC783F993FB9150@DM2PR0301MB0653.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006); SRVR:DM2PR0301MB0653; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0653; 
x-forefront-prvs: 05009853EF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(51704005)(377454003)(62966003)(92566002)(33656002)(76176999)(2950100001)(93886004)(102836002)(50986999)(76576001)(122556002)(40100003)(77156002)(46102003)(2900100001)(87936001)(19580395003)(19580405001)(2656002)(74316001)(86612001)(86362001)(230783001)(54356999)(99286002)(106116001)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0653; H:DM2PR0301MB0655.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2015 19:41:00.3485 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0653
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB1216;
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/DoeBKw9JGZ6ZyxyuIXrX24rU3g8>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 19:41:22 -0000

On Friday, February 27, at 2015 11:17 AM, Ted Lemon wrote
=20
> On Feb 27, 2015, at 12:14 PM, Sten Carlsen <stenc@s-carlsen.dk> wrote:
> > Would signing the client cert with a particular root cert allow
> > another level of control? If the client cert is signed by the correct
> > party, it is admitted - if not, it is rejected.
>=20
> We already discussed that.   I don't think it's a very useful flow.   Gen=
erally
> speaking, if you want access control for clients, signing their public ke=
y just
> adds an extra step.   You could have a flow a lot like the flow we have n=
ow
> where the MAC address is added to a database in the receiving department,
> and then the key for that device is connected to the MAC address the firs=
t
> time the DHCP server sees it.

Second that.

Please consider the "anonymity" (or privacy) use case, in which the client =
does not want to disclose a long term identity.

You want to counter a specific Denial Of Service threat, in which someone s=
poofs an existing DHCP session and messes up with existing leases. Associat=
ing a public key with the session is sufficient. But you don't want a full =
blown certificate mechanism that would compel client identity disclosure in=
side the DHCP exchange. If some identity has to be disclosed, it is better =
to leave that to another mechanism, like maybe a captive portal.

-- Christian Huitema



From nobody Fri Feb 27 11:54:15 2015
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 E1B001AD358 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:54:13 -0800 (PST)
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 bY3InQfvJq74 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 11:54:12 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB16F1AC3C0 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:54:05 -0800 (PST)
Received: by igbhn18 with SMTP id hn18so3273142igb.2 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 11:54:05 -0800 (PST)
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=nFXjeh8R539pyxgRLxjnIFWu/BMU4yFgIxUjDVmuJCc=; b=Zmp8QpcVuUejmyxYIjV6jg10y0O2YZ/fVOSTmDzgxHLAl+pBI8TKRQk/OPdlYFmSH8 NPtvguDgmnkuVtGhVS47VbXfVJUSarKYYgI6dDGLI/mJoc42sPq+GbHgjto/qHdesxR8 0xwToXY0FS8PbtVbnF9R3+QxOYDdIiTZc2gPg2yjdlYJgcxpMWj2j7d/Su2wdYxa2PcZ 2axuwqyZYAQCytGvffr8slgRx/rj88NUbbboBkdHfMIuG+qm6QTQEg0K2touDpk0NSn7 7P/eiMkEAdVVUGDbp3q1bP+gOfD7CqFFrXLyG3kteU8NAyRBTyLMhQwHLJgmULsiUZhw xBrg==
MIME-Version: 1.0
X-Received: by 10.107.13.144 with SMTP id 138mr20984690ion.24.1425066844969; Fri, 27 Feb 2015 11:54:04 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Fri, 27 Feb 2015 11:54:04 -0800 (PST)
In-Reply-To: <C64E7F5E-82C5-4A80-804E-78912F4CC514@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com> <C64E7F5E-82C5-4A80-804E-78912F4CC514@nominum.com>
Date: Fri, 27 Feb 2015 11:54:04 -0800
X-Google-Sender-Auth: QHlgR5noBzQQN23fS50F4XoH-J4
Message-ID: <CAJE_bqesXLsKYGxnCwJOK_YsiKf+cJURa3u_8215_E4VQNnSmA@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/hNA5QwPZFIhv-1tqL8QmRvL8ZKs>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 19:54:14 -0000

At Fri, 27 Feb 2015 14:24:16 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > And, in this case, it could also be a shared secret-based mechanism
> > without any essential difference in terms of operational cost and
> > security level, correct?  The client would create a secret, and
> > register it at the portal.  The server would retrieve the secret from
> > the portal and they can securely share the secret.
>
> There would be a shared secret in the RADIUS transaction, but not in
> the DHCP transaction.   Who generates the secret is out of scope
> (indeed, the whole RADIUS part of the flow is out of scope) but you
> are probably right that it's done through some kind of user
> registration process where the user enters a password.
>
> Of course, this flow is actually a really bad idea--it would be much
> better to use the public key for the whole thing, so that there is
> no shared secret and no risk of the end user choosing a weak
> password, so if I were designing such a flow from scratch I would
> not used a shared secret at all.   The only reason to support this
> flow is that it would work with existing installations and is better
> than what we have now.

I don't understand how it's better than what we have now.  In the
above flow I didn't expect the shared secret for DHCPv6 is something
like a (human) user-generated password.  It would probably be
generated by a backend system of the OS or DHCP client, and should be
generally unpredictable.  I don't see any difference between creating
a secure public-private key pair and creating a secure secret (to be
shared) in this scenario.  So the security level of this framework
depends on some details of the yet-to-be-seen "portal", and that level
of security equally applies to a publickey-based DHCPv6 security
mechanism and to a shared-secret based DHCPv6 mechanism.  Am I right?

--
JINMEI, Tatuya


From nobody Fri Feb 27 12:24:49 2015
Return-Path: <Ted.Lemon@nominum.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 7DDA31A0068 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 12:24:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 hJqjynKRpS19 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 12:24:46 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6F251A0067 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 12:24:46 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTP id 833B4DA01E1 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 20:24:46 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 60ED353E0AC; Fri, 27 Feb 2015 12:19:43 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 12:19:43 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqesXLsKYGxnCwJOK_YsiKf+cJURa3u_8215_E4VQNnSmA@mail.gmail.com>
Date: Fri, 27 Feb 2015 15:19:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <60266235-1C31-453A-98A8-CD489841C59A@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com> <C64E7F5E-82C5-4A80-804E-78912F4CC514@nominum.com> <CAJE_bqesXLsKYGxnCwJOK_YsiKf+cJURa3u_8215_E4VQNnSmA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/dGrobSTBqru59JZni6pWCWljG_k>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 20:24:47 -0000

On Feb 27, 2015, at 2:54 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> I don't understand how it's better than what we have now.

I think this is the heart of the matter.   I do not understand how you =
can have doubts about this.   It is clearly better than what we have =
now.   There is a reason why kerberos is almost never used, and TLS is =
ubiquitous: shared secrets are much harder to use securely than public =
key encryption.   We have seen _zero_ deployment of shared secret =
authentication in DHCP.   There is no question that it doesn't work in =
practice.   It's possible that we will see zero deployment of this =
mechanism as well, but if so that'll be because there is no demand for =
secure DHCP, not because it's hard to deploy.

We've had a long discussion about various flows that the mechanism =
defined in the draft can support.   I don't think there's any question =
but that the mechanism could be useful.   We don't know that it will be =
used, and I think that is your core objection.   But if that objection =
were a valid objection, we would never have developed DNSSEC.   This is =
a _much_ easier lift than DNSSEC.   So if your argument was wrong for =
DNS, I think it's also wrong for DHCP.

It's possible that there is some technical flaw in the current proposal =
that means it won't work for the flows we've discussed.   If so, we =
should fix that technical flaw.   If you think such a flaw exists, I =
hope you will point it out.   But I think that further debates about =
hypothetical flows that we don't actually know will be used should be =
out of scope, because it's not getting to the core of your objection.


From nobody Fri Feb 27 13:29:07 2015
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 07F041A026E for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 13:29:05 -0800 (PST)
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 Y84QmNBCxbmg for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 13:29:02 -0800 (PST)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80D5D1A00FE for <dhcwg@ietf.org>; Fri, 27 Feb 2015 13:29:02 -0800 (PST)
Received: by iecrd18 with SMTP id rd18so34265213iec.8 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 13:29:01 -0800 (PST)
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=NLN7yqc6uACeJszNFpTt7zhmoeFV+CjXBbhf9h5cs8U=; b=pR/iYQsucEQYlByabnjv4YWAbeCLkVSwLmAwuhbC6GEKnsTvMbHzX4An1M8xe3f+4v IaMcGAl8qRpsAfsFiGz1hFER8X+x3AkhBjW4HPzf0jlG3THaGe4CeJDFDEk+RYfp7h4s QFyUiE6GJbfyYvvZq9R4tL6Fg0uuYCca5MtGVt5suPgT+0NddWsTig2sEL0HXhT4QAFQ GSi4iN/FFPrcdu7rLLmvslWQvUolaHcflJRFK18yAt3HiOUobCu7d8A4BLEjoSQxcuCn 2/ebS5jwZpPNmUFIzzlT7DvxKNXYnHO9vY6YfFeiJJmn7jk8dcugW2LA+UFdra67NFyN TSLw==
MIME-Version: 1.0
X-Received: by 10.42.189.132 with SMTP id de4mr1360298icb.21.1425072541641; Fri, 27 Feb 2015 13:29:01 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.11.154 with HTTP; Fri, 27 Feb 2015 13:29:01 -0800 (PST)
In-Reply-To: <60266235-1C31-453A-98A8-CD489841C59A@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com> <C64E7F5E-82C5-4A80-804E-78912F4CC514@nominum.com> <CAJE_bqesXLsKYGxnCwJOK_YsiKf+cJURa3u_8215_E4VQNnSmA@mail.gmail.com> <60266235-1C31-453A-98A8-CD489841C59A@nominum.com>
Date: Fri, 27 Feb 2015 13:29:01 -0800
X-Google-Sender-Auth: UkPsFENc2lQ9AOaq5Wku_ij_y7E
Message-ID: <CAJE_bqcXhQx+i5bNnyti9y4p-5GNaJtDtGZvEpaUdHtMTXF4Yw@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/KZNZ1sLRUrUor-MfWzvNZvczOoY>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Fri, 27 Feb 2015 21:29:05 -0000

At Fri, 27 Feb 2015 15:19:39 -0500,
Ted Lemon <Ted.Lemon@nominum.com> wrote:

> > I don't understand how it's better than what we have now.
>
> I think this is the heart of the matter.

Perhaps, and although you may not be comfortable with saying anything
about this specific case, could you answer my question to the specific
case?  That is, in the following scenario:

>> If you want to do some kind of RADIUS transaction, as we
>> talked about previously, there's probably some sort of captive
>> portal registration process.

no one has a specific idea of how a public-key based DHCPv6
authentication is better than shared secret based one, beyond the
general principle that public key based things are generally better
than shared secret things.  Is this correct?

I'm not trying to say we don't need sedhcpv6 just because of that, but
I'd like to understand exactly where we are.  Also, if the answer to
that question is "no", I'd like to understand any specific counter
example, even if it's hypothetical.

--
JINMEI, Tatuya


From nobody Fri Feb 27 16:46:36 2015
Return-Path: <Ted.Lemon@nominum.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 60B141A1AC6 for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 16:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level: 
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 4F8NgK4qMjCQ for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 16:46:33 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07BD11A1AB3 for <dhcwg@ietf.org>; Fri, 27 Feb 2015 16:46:32 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id A0A56DA01DF for <dhcwg@ietf.org>; Sat, 28 Feb 2015 00:46:31 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 61F4A53E0AC; Fri, 27 Feb 2015 16:46:31 -0800 (PST)
Received: from CAS-04.WIN.NOMINUM.COM (64.89.235.67) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 16:46:31 -0800
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 16:46:25 -0800
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqcXhQx+i5bNnyti9y4p-5GNaJtDtGZvEpaUdHtMTXF4Yw@mail.gmail.com>
Date: Fri, 27 Feb 2015 19:46:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <CB0D2999-404B-4381-94A1-0C15B26D4F27@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <CAJE_bqd8icqzjrucRjKe7WMdA-pUZ8Y_4cbUtEJkwVXBvLOs1Q@mail.gmail.com> <C64E7F5E-82C5-4A80-804E-78912F4CC514@nominum.com> <CAJE_bqesXLsKYGxnCwJOK_YsiKf+cJURa3u_8215_E4VQNnSmA@mail.gmail.com> <60266235-1C31-453A-98A8-CD489841C59A@nominum.com> <CAJE_bqcXhQx+i5bNnyti9y4p-5GNaJtDtGZvEpaUdHtMTXF4Yw@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/OiaqGzU1rNGMOH3nkiKMIATOpao>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
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: Sat, 28 Feb 2015 00:46:34 -0000

On Feb 27, 2015, at 4:29 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
> no one has a specific idea of how a public-key based DHCPv6
> authentication is better than shared secret based one, beyond the
> general principle that public key based things are generally better
> than shared secret things.  Is this correct?

No, it is not correct.   Public key authentication in the case of the =
radius or captive portal flow is better because DHCP doesn't need a =
shared secret.  Essentially you just do DHCP with the identity that you =
have, and either you are already known, or you aren't.   If you are =
already known, then you are just automatically online, with no =
additional transaction.   If you are not already known then you have to =
map the key to some kind of identity, which may indeed be password =
protected, but could also be a credit card or something.   This process =
is completely orthogonal to DHCP; indeed, it isn't even the case that it =
is necessary.   As we've discussed elsewhere in this conversation, it =
could be that the DHCP server just uses public keys to positively =
differentiate between clients, without requiring registration.

None of the scenarios I've described just now work with DHCP shared =
secret authentication.

> Also, if the answer to
> that question is "no", I'd like to understand any specific counter
> example, even if it's hypothetical.

Numerous examples have been mentioned.   E.g.:

- client sends public key, server associates resources with that public =
key, other clients can't spoof the first client because they don't have =
its private key
- client sends public key, server recognizes the key, server grants =
client access to network according to some pre-existing arrangement
- client sends public key, server does not recognize key, server sends =
client to captive portal, client makes arrangements for access, server =
records key and associates it with that arrangement

The RADIUS flow we've talked about is an example of a way that =
arrangements could be made to grant network access for the client, but =
other examples include a credit card transaction, some other sort of =
login, etc.


From nobody Sat Feb 28 04:51:28 2015
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: expand-draft-ietf-dhc-dhcpv6-stateful-issues.all@virtual.ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 81F7C1A1A3C; Sat, 28 Feb 2015 03:53:54 -0800 (PST)
X-Original-To: xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 619491A1A2F for <xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com>; Sat, 28 Feb 2015 03:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.333
X-Spam-Level: 
X-Spam-Status: No, score=-1.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] 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 04xgnBNE2byK for <xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com>; Sat, 28 Feb 2015 03:53:52 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16641A1A3C for <draft-ietf-dhc-dhcpv6-stateful-issues.all@ietf.org>; Sat, 28 Feb 2015 03:53:49 -0800 (PST)
Received: from mail-wi0-x236.google.com ([2a00:1450:400c:c05::236]:44648) by zinfandel.tools.ietf.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <ron.even.tlv@gmail.com>) id 1YRfxs-0005kM-A4 for draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org; Sat, 28 Feb 2015 03:53:49 -0800
Received: by wiwl15 with SMTP id l15so5467250wiw.3 for <draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org>; Sat, 28 Feb 2015 03:53:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=bSsohceNyNh6mkWN15leZRGa1QLelHhQBDKFuG0kzh8=; b=PhZ4cEPmxOr6YJlJbdwAson+G4pB4JmEbG1yijbTc1nGVfhE7O0J059QDMkFmtkLvd V1QSU22WN6n/9YOkpmA3Uk+rAnh027yf8pgT1zzv/I3tYTt0HfFK0AsexJ2FfMCNw/JQ teoVSr15Xq5zui3NI0OMZxAg3wa6eo1s96DfRhnyaVYezbpC0as9Peo09uwo67eHLfU1 LzcDofPBsJ6qCkSRvgkUpMI5O9EouOYhJ3O7LXsVBoBQiDFaCeRrb/upwmTgHLW7AWSw NodjX0j0j07oLj0PZE471qsMjZYxsdPu8IEKKEOVWUn1Fnq3rX1tzlf4Wc2FgQa5umKz CbDw==
X-Received: by 10.180.108.177 with SMTP id hl17mr15747802wib.35.1425124418961;  Sat, 28 Feb 2015 03:53:38 -0800 (PST)
Received: from RoniE (bzq-79-177-192-183.red.bezeqint.net. [79.177.192.183]) by mx.google.com with ESMTPSA id hi6sm9891020wjc.34.2015.02.28.03.53.36 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 28 Feb 2015 03:53:37 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org>
Date: Sat, 28 Feb 2015 13:53:29 +0200
Message-ID: <01ba01d0534d$2eeb3ca0$8cc1b5e0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BB_01D0535D.F274CFF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdBTTSsKDoBUtzL4TvC595jYUNTaKQ==
Content-Language: en-us
X-SA-Exim-Connect-IP: 2a00:1450:400c:c05::236
X-SA-Exim-Rcpt-To: draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org
X-SA-Exim-Mail-From: ron.even.tlv@gmail.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Resent-To: draft-ietf-dhc-dhcpv6-stateful-issues.all@ietf.org
Resent-Message-Id: <20150228115352.C16641A1A3C@ietfa.amsl.com>
Resent-Date: Sat, 28 Feb 2015 03:53:49 -0800 (PST)
Resent-From: ron.even.tlv@gmail.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-dhc-dhcpv6-stateful-issues.all@tools/mY-NXKltRrCXK-QRaj5Ql3BfW8g>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pX-a-9iqqCMFLVnFaIDeDxIRIX8>
X-Mailman-Approved-At: Sat, 28 Feb 2015 04:51:26 -0800
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [dhcwg] Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-issues-11
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: Sat, 28 Feb 2015 11:53:54 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01BB_01D0535D.F274CFF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document:  draft-ietf-dhc-dhcpv6-stateful-issues-11

Reviewer: Roni Even

Review Date:2015-2-28

IETF LC End Date: 2015-3-4

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Standard Track  RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	The document defines the terms "Identity association (IA)" and "IA
option types" different from RFC3315 yet in the document sometimes this
terms are as specified in RFC3315 including the IA_TA option. An example is
for section with text changes.
2.	For clarification: Is this document going to be obsolete by
draft-dhcwg-dhc-rfc3315bis, there are some sections that include changes to
RFC3315 and RFC3633 and my reading is that this changes will be incorporated
un the rfc3315bis draft. I am not sure about sections that provides
clarifications and do not propose text changes. 

 

 


------=_NextPart_000_01BB_01D0535D.F274CFF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1836416174;
	mso-list-type:hybrid;
	mso-list-template-ids:-581664096 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document:&n=
bsp; </span><span style=3D'font-family:"Courier =
New"'>draft-ietf-dhc-dhcpv6-stateful-issues-11</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2015&#8211;2-28<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2015&#8211;3-4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Standard Track&nbsp; =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal =
style=3D'margin-bottom:10.0pt;line-height:115%;mso-list:l0 level1 =
lfo1'>The document defines the terms &#8220;Identity association =
(IA)&#8221; and &#8220;IA option types&#8221; different from RFC3315 yet =
in the document sometimes this terms are as specified in RFC3315 =
including the IA_TA option. An example is for section with text =
changes.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'color:black;margin-bottom:10.0pt;line-height:115%;mso-list:l0 =
level1 lfo1'><span style=3D'color:windowtext'>For clarification: Is this =
document going to be obsolete by draft-dhcwg-dhc-rfc3315bis, there are =
some sections that include changes to RFC3315 and RFC3633 and my reading =
is that this changes will be incorporated un the rfc3315bis draft. I am =
not sure about sections that provides clarifications and do not propose =
text changes. </span><span =
style=3D'font-size:12.0pt;line-height:115%;font-family:"Courier =
New"'><o:p></o:p></span></li></ol><p class=3DMsoNormal =
style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_01BB_01D0535D.F274CFF0--


From nobody Sat Feb 28 09:45:07 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: expand-draft-ietf-dhc-dhcpv6-stateful-issues.all@virtual.ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id C99B01A1A72; Sat, 28 Feb 2015 06:22:50 -0800 (PST)
X-Original-To: xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38A21A1A58 for <xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com>; Sat, 28 Feb 2015 06:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 olKlaZvmBMfx for <xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com>; Sat, 28 Feb 2015 06:22:49 -0800 (PST)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [IPv6:2607:f170:8000:1500::de]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 750731A1A5E for <draft-ietf-dhc-dhcpv6-stateful-issues.all@ietf.org>; Sat, 28 Feb 2015 06:22:49 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com ([64.89.234.25]:43319) by gamay.tools.ietf.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <Ted.Lemon@nominum.com>) id 1YRiI1-0004IC-QG for draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org; Sat, 28 Feb 2015 09:22:47 -0500
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 92618DA0125 for <draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org>; Sat, 28 Feb 2015 13:40:20 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A565C53E078; Sat, 28 Feb 2015 05:40:19 -0800 (PST)
Received: from CAS-04.WIN.NOMINUM.COM (64.89.235.67) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sat, 28 Feb 2015 05:40:19 -0800
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sat, 28 Feb 2015 05:40:13 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <01ba01d0534d$2eeb3ca0$8cc1b5e0$@gmail.com>
Date: Sat, 28 Feb 2015 08:40:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <5A1EDA05-B6DF-441F-8ECE-828CAF671135@nominum.com>
References: <01ba01d0534d$2eeb3ca0$8cc1b5e0$@gmail.com>
To: <draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
X-SA-Exim-Connect-IP: 64.89.234.25
X-SA-Exim-Rcpt-To: draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org
X-SA-Exim-Mail-From: Ted.Lemon@nominum.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:57:07 +0000)
X-SA-Exim-Scanned: Yes (on gamay.tools.ietf.org)
Resent-To: draft-ietf-dhc-dhcpv6-stateful-issues.all@ietf.org
Resent-Message-Id: <20150228142249.750731A1A5E@ietfa.amsl.com>
Resent-Date: Sat, 28 Feb 2015 06:22:49 -0800 (PST)
Resent-From: Ted.Lemon@nominum.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-dhc-dhcpv6-stateful-issues.all@tools/syRN1hfiV1DIIFDY9MiHROPhRrs>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/V51mtHxbU6d2ds0uxCyPUS-jvvY>
X-Mailman-Approved-At: Sat, 28 Feb 2015 09:45:07 -0800
Cc: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: [dhcwg] Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-issues-11
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: Sat, 28 Feb 2015 14:22:50 -0000

On Feb 28, 2015, at 6:53 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
>=20
> 	=95 The document defines the terms =93Identity association (IA)=94=
 and =93IA option types=94 different from RFC3315 yet in the document =
sometimes this terms are as specified in RFC3315 including the IA_TA =
option. An example is for section with text changes.

Authors, can you look into this and see if there's a way to fix it?

> 	=95 For clarification: Is this document going to be obsolete by =
draft-dhcwg-dhc-rfc3315bis, there are some sections that include changes =
to RFC3315 and RFC3633 and my reading is that this changes will be =
incorporated un the rfc3315bis draft. I am not sure about sections that =
provides clarifications and do not propose text changes.

I think this is an action item to carry forward to 3315bis.   We have at =
least been attempting to do this, but a final pass through this document =
before submitting 3315bis for publication should be one of the action =
items for that document.=


From nobody Sat Feb 28 15:03:33 2015
Return-Path: <volz@cisco.com>
X-Original-To: expand-draft-ietf-dhc-dhcpv6-stateful-issues.all@virtual.ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id BFDA81A0097; Sat, 28 Feb 2015 15:02:47 -0800 (PST)
X-Original-To: xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A313E1A0076 for <xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com>; Sat, 28 Feb 2015 15:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.5
X-Spam-Level: 
X-Spam-Status: No, score=-9.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 5a3GFyvcyh0q for <xfilter-draft-ietf-dhc-dhcpv6-stateful-issues.all@ietfa.amsl.com>; Sat, 28 Feb 2015 15:02:44 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ECC31A008F for <draft-ietf-dhc-dhcpv6-stateful-issues.all@ietf.org>; Sat, 28 Feb 2015 15:02:44 -0800 (PST)
Received: from alln-iport-5.cisco.com ([173.37.142.92]:36768) by zinfandel.tools.ietf.org with esmtps (TLS1.0:RSA_ARCFOUR_128_SHA1:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <volz@cisco.com>) id 1YRqPC-0007sS-Kx for draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org; Sat, 28 Feb 2015 15:02:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4244; q=dns/txt; s=iport; t=1425164563; x=1426374163; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=yhj2Kezjl8xj60QI0hh6SIgJoWk0kAsZlsxCpnYhGKU=; b=VJ27Hub7ZJlnIfRgz9k4P85qxMxZ3TvnqmSbRQKGYAiFoK8K1cD0epZH m5xOcgAmhEr4XtU9ODCD0GsrzGeadxcV2WZbB6fZsBNv1EePsAOpHzE7s faepA3CnRjvr2HbtHd7Lo1xa0VaoGDYsgsLmFZTeOGuBMbIlPR09tLBG1 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AVBQCCSPJU/4sNJK1RCYMCgSwEyBQCgRlNAQEBAQEBfIQPAQEBBDotEgwEAgEIEQQBAQEKFAkHIREUCQgCBAENBQiIEwMRzzQNhTMBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixKCRIFPKiYLBwaDEYEUAQSPeId+jxSGCyOCAhyBUG8BgQEkHn8BAQE
X-IronPort-AV: E=Sophos;i="5.09,669,1418083200"; d="scan'208";a="127879154"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-5.cisco.com with ESMTP; 28 Feb 2015 23:02:36 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t1SN2Z0L031215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 28 Feb 2015 23:02:36 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.248]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Sat, 28 Feb 2015 17:02:35 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, "draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org>
Thread-Topic: [dhcwg] Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-issues-11
Thread-Index: AQHQU2ILxV6xba/lDk6mA1E12MmYpZ0Gpfww
Date: Sat, 28 Feb 2015 23:02:35 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1C9CC999@xmb-rcd-x04.cisco.com>
References: <01ba01d0534d$2eeb3ca0$8cc1b5e0$@gmail.com> <5A1EDA05-B6DF-441F-8ECE-828CAF671135@nominum.com>
In-Reply-To: <5A1EDA05-B6DF-441F-8ECE-828CAF671135@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.98.1.205]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 173.37.142.92
X-SA-Exim-Rcpt-To: draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org
X-SA-Exim-Mail-From: volz@cisco.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Resent-To: draft-ietf-dhc-dhcpv6-stateful-issues.all@ietf.org
Resent-Message-Id: <20150228230244.0ECC31A008F@ietfa.amsl.com>
Resent-Date: Sat, 28 Feb 2015 15:02:44 -0800 (PST)
Resent-From: volz@cisco.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-dhc-dhcpv6-stateful-issues.all@tools/-eIgHmZTNQqr0RUGvbhFq2f5dFQ>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/Rm1p3gLInomikPUGAXT1Owq1Eag>
X-Mailman-Approved-At: Sat, 28 Feb 2015 15:03:31 -0800
Cc: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: [dhcwg] Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-issues-11
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: Sat, 28 Feb 2015 23:02:47 -0000

Ted, et al:

> 	* The document defines the terms "Identity association (IA)" and "IA opt=
ion types" different from RFC3315 yet in the document sometimes this terms =
are as specified in RFC3315 including the IA_TA option. An example is for s=
ection with text changes.

I don't believe RFC 3315 has "IA option types".

The problem with the RFC 3315 definition of "Identity association (IA)" is =
that it is just for addresses. And, prior to the 08 version (Oct 2014), we =
had extended the definition to include prefix delegation, but in the 08 dra=
ft (I believe primarily based on comments from Jinmei) we restricted it to =
IA_NA and IA_PD because that is primarily what this document deals with. We=
 left out IA_TA because as stated in the Introduction, IA_TAs are really a =
bit different as they generally have their own lifecycle (and thus are less=
 likely to be obtained together - except perhaps initially). Also, while it=
 is possible that Customer Edge Routers use temporary addresses, it is less=
 likely that they generally would as they aren't as likely to "move" around=
 the Internet (to various access points) and even if they did, they general=
ly wouldn't be used for web browsing and the like that might require tempor=
ary addresses.

In looking at the usage of "IA" (as opposed to "IA_xx" or "IA option types"=
), I really don't see any harm if we went with something that covered IA_TA=
 as well (in fact a few of the uses of "IA" imply this). So:

   Identity association (IA):      Throughout this document, "IA" is
                                   used to refer to the Identity
                                   Association containing addresses or
                                   prefixes assigned to a client and
                                   carried in the IA_NA, IA_TA, or IA_PD
                                   options.

Again, even this is different from RFC 3315 since RFC 3315 did not include =
prefix delegation or IA_PD.

> 	* For clarification: Is this document going to be obsolete by draft-dhcw=
g-dhc-rfc3315bis, there are some sections that include changes to RFC3315 a=
nd RFC3633 and my reading is that this changes will be incorporated un the =
rfc3315bis draft. I am not sure about sections that provides clarifications=
 and do not propose text changes.

Yes, the intent is for this to be incorporated into draft-dhcwg-dhc-rfc3315=
bis, but that document is still a work in progress and will take a while be=
fore it is "done", and we'd rather get these changes into the DHCPv6 standa=
rd well before then. We have not yet done these changes to draft-dhcwg-dhc-=
rfc3315bis as we are awaiting them to be approved before assuming we can ma=
ke those changes (draft-dhcwg-dhc-rfc3315bis is a revised standards documen=
t and we are not trying to introduce new or different capabilities in that =
document).

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Saturday, February 28, 2015 8:40 AM
To: draft-ietf-dhc-dhcpv6-stateful-issues.all@tools.ietf.org
Cc: Roni Even; Jari Arkko
Subject: Re: [dhcwg] Gen-ART LC review of draft-ietf-dhc-dhcpv6-stateful-is=
sues-11

On Feb 28, 2015, at 6:53 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
>=20
> 	* The document defines the terms "Identity association (IA)" and "IA opt=
ion types" different from RFC3315 yet in the document sometimes this terms =
are as specified in RFC3315 including the IA_TA option. An example is for s=
ection with text changes.

Authors, can you look into this and see if there's a way to fix it?

> 	* For clarification: Is this document going to be obsolete by draft-dhcw=
g-dhc-rfc3315bis, there are some sections that include changes to RFC3315 a=
nd RFC3633 and my reading is that this changes will be incorporated un the =
rfc3315bis draft. I am not sure about sections that provides clarifications=
 and do not propose text changes.

I think this is an action item to carry forward to 3315bis.   We have at le=
ast been attempting to do this, but a final pass through this document befo=
re submitting 3315bis for publication should be one of the action items for=
 that document.

