IETF Logo Mail Archive

Re: [dhcwg] Stephen Farrell's Discuss on draft-ietf-dhc-dynamic-shared-v4allocation-07: (with DISCUSS and COMMENT)

Christian Huitema <huitema@microsoft.com> Thu, 28 May 2015 17:28 UTC

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 98EC41A1C02; Thu, 28 May 2015 10:28:21 -0700 (PDT)
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 XwCZJpNQrnKw; Thu, 28 May 2015 10:28:19 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0725.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:725]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 413C11A1B67; Thu, 28 May 2015 10:28:19 -0700 (PDT)
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (10.160.96.17) by DM2PR0301MB0656.namprd03.prod.outlook.com (10.160.96.18) with Microsoft SMTP Server (TLS) id 15.1.172.22; Thu, 28 May 2015 17:27:58 +0000
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com ([10.160.96.17]) by DM2PR0301MB0655.namprd03.prod.outlook.com ([10.160.96.17]) with mapi id 15.01.0172.012; Thu, 28 May 2015 17:27:58 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Bernie Volz (volz)" <volz@cisco.com>, "sthaug@nethelp.no" <sthaug@nethelp.no>
Thread-Topic: [dhcwg] Stephen Farrell's Discuss on draft-ietf-dhc-dynamic-shared-v4allocation-07: (with DISCUSS and COMMENT)
Thread-Index: AQHQmUCUtOp9D5GwxUyA81hYETDWfp2RT3GAgABSnxA=
Date: Thu, 28 May 2015 17:27:57 +0000
Message-ID: <DM2PR0301MB06551796B9F2139144A69036A8CA0@DM2PR0301MB0655.namprd03.prod.outlook.com>
References: <489D13FBFA9B3E41812EA89F188F018E1CAF5DA3@xmb-rcd-x04.cisco.com> <55670179.8030400@cs.tcd.ie> <489D13FBFA9B3E41812EA89F188F018E1CAF5EC1@xmb-rcd-x04.cisco.com> <20150528.141105.74661164.sthaug@nethelp.no> <489D13FBFA9B3E41812EA89F188F018E1CAF6142@xmb-rcd-x04.cisco.com> <55670889.30503@cs.tcd.ie>
In-Reply-To: <55670889.30503@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=huitema@microsoft.com;
x-originating-ip: [2001:4898:80e0:ee43::2]
x-microsoft-exchange-diagnostics: 1; DM2PR0301MB0656; 3:yL7zw90uK6Ajh/33KhnVKukfJA1tiXlGB1aFGvtFb4r8J7YBfeigD780dRnh5HHQYtNuWTPGh1InjXYYyds1+TbcAbHAPdur1oIIcCIKmNfAuqOTYl/cD7r+XmftK+FQecXDXiKdvbD2PpwfC3LEfQ==; 10:78pZZxdW7D39zgCaYenAVLXelTdUnkZCpti9g6BFuyvmmX/Wy2GORIrWVG/Q2yvBcwDmUQQ//DQZqS9+OVmuoOwqfOWsEAxzwR4TmxfQ4Cw=; 6:DqWXwtcbR4ZBpfGcqt9r4fENd1gnfTWYqV9o4M2vJc7MfVeB530Xc1sgQAvGfeP/
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0656;
x-microsoft-antispam-prvs: <DM2PR0301MB0656C9B1AF9B25ED31860550A8CA0@DM2PR0301MB0656.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401001)(5005006)(520003)(3002001); SRVR:DM2PR0301MB0656; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0656;
x-forefront-prvs: 0590BBCCBC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(479174004)(24454002)(51704005)(199003)(377454003)(74316001)(64706001)(2501003)(2950100001)(2656002)(81156007)(87936001)(33656002)(5001770100001)(106356001)(101416001)(86362001)(77096005)(5001830100001)(102836002)(68736005)(5001860100001)(2900100001)(93886004)(4001540100001)(40100003)(97736004)(189998001)(54356999)(230783001)(76176999)(106116001)(62966003)(105586002)(76576001)(92566002)(86612001)(5001920100001)(50986999)(77156002)(5001960100002)(99286002)(5002640100001)(46102003)(122556002)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0656; 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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 May 2015 17:27:58.0618 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0656
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/HgsKkRJ27tbo_ROCzgsnrMFXErw>
X-Mailman-Approved-At: Thu, 28 May 2015 10:41:19 -0700
Cc: "draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org" <draft-ietf-dhc-dynamic-shared-v4allocation.shepherd@ietf.org>, "dhc-chairs@ietf.org" <dhc-chairs@ietf.org>, "draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org" <draft-ietf-dhc-dynamic-shared-v4allocation@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org" <draft-ietf-dhc-dynamic-shared-v4allocation.ad@ietf.org>, "Ted.Lemon@nominum.com" <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Stephen Farrell's Discuss on draft-ietf-dhc-dynamic-shared-v4allocation-07: (with DISCUSS and COMMENT)
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, 28 May 2015 17:28:21 -0000

On May 28, 2015 5:23 AM, Stephen Farrell wrote: 
> 
> On 28/05/15 13:19, Bernie Volz (volz) wrote:
> > Note also that there is work going on in the DHC WG to address privacy
> > issues - see draft-ietf-dhc-anonymity-profile-00. And one of the
> > authors (the primary author) is from Microsoft so I am sure this is on
> > their radar.
> 
> So just to be clear: the reason I'm asking about this is mainly that I want to be
> sure that this draft doesn't make deploying the privacy one harder/impossible.

How about adding something like that to the security considerations:

The purpose of the "client identifier option" is to ensure that the same client retains the same parameters over time. This interferes with the client's privacy, as it allows the server to track the client. Clients can manage their privacy exposure by controlling the value of the client identifier, trading off stability of parameter allocation for privacy. We expect that guidance on this tradeoff will be discussed in a future version of [draft-ietf-dhc-anonymity-profile].

-- Christian Huitema

v2.23.0 | Report a Bug | By Email