IETF Logo Mail Archive

Re: [dhcwg] On RFC 7819, privacy considerations for DHCP...

Christian Huitema <huitema@microsoft.com> Thu, 23 June 2016 21:03 UTC

Return-Path: <huitema@microsoft.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC66312D73A for <dhcwg@ietfa.amsl.com>; Thu, 23 Jun 2016 14:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 fxUuVSTNzsbr for <dhcwg@ietfa.amsl.com>; Thu, 23 Jun 2016 14:03:42 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0103.outbound.protection.outlook.com [207.46.100.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B636812D662 for <dhcwg@ietf.org>; Thu, 23 Jun 2016 14:03:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yH6Vc6MmKiVMB8ovngNKzDDZhJeRoP6AbM/a1g37/ts=; b=L+N/zTGBkiLS+y0FBV/foSCIkrDVVezimAoIYzWyCzhDc82lKTq1yKjof2ma5L+gzh36jB9kQmGr8x4ySiemgKuhE+7W8G1IIkRO5wYIY1kn4zOw9la7yhSZkSjIHMo1tsyz5G+6z3lEroFpLb9h3HfhmWxPAXs+/EVSQDFpWng=
Received: from DM2PR0301MB0655.namprd03.prod.outlook.com (10.160.96.17) by DM2PR0301MB0653.namprd03.prod.outlook.com (10.160.96.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.523.12; Thu, 23 Jun 2016 21:03:41 +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.0523.015; Thu, 23 Jun 2016 21:03:41 +0000
From: Christian Huitema <huitema@microsoft.com>
To: David Singer <singer@apple.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] On RFC 7819, privacy considerations for DHCP...
Thread-Index: AQHRyCBG3eGXvIS5ZUu/mMj9b7itlZ/3kdmw
Date: Thu, 23 Jun 2016 21:03:41 +0000
Message-ID: <DM2PR0301MB065533EE95F699D9B9A0859DA82D0@DM2PR0301MB0655.namprd03.prod.outlook.com>
References: <64A0CA2D-C8C1-415B-A532-338E4B62DF14@apple.com>
In-Reply-To: <64A0CA2D-C8C1-415B-A532-338E4B62DF14@apple.com>
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:80e8:9::399]
x-ms-office365-filtering-correlation-id: a3bf4b97-f0ba-4364-f19d-08d39ba9db26
x-microsoft-exchange-diagnostics: 1; DM2PR0301MB0653; 6:t17IUdxluWHoXo/L9eezV8d1W5WIAr8MSk7VslSuz6CtBwFEDbgYly9lzZPjtmIgK9YD9WYojkNOqyv5AgM5RDjru/t1cn9jxBpgUZVjfzRYCY0i6Ja/m7zIr8gSwg4jooT/TVApoT61IAEIXgUqsVRCvUo53WJ+rD2zi5FRHU9TnVznLBlCoFR3cuL5q9drg8F2Ega2eENVYHNsHRVxdQv8rc07yILEj3nCMTmNHBO/4qgjWTDkycpvMiyG2IKHYFtS9KAYvgTC0yZ8bEXe41R2aJKUA9MfC+W5QZWEXj8rmNrRpItpPOvAciQySHSHETSArDte1Vh8ZX5ak4upxUYZodzMN0sweFc2sQ4NUY0=; 5:6agICZL8B2YWpP0kLq37WGb7lmakzJi38HKn6vr57akbWEIZMdR+fI7GAwfp8mC6Pn2iJkL2i82jWFU7pv3WiBbsLfJpmparlVQ9kalCoM5Sc9JqHCugX7cbQyYZ5seL37jb0Da4+MnONcQ5YH3MUA==; 24:PxHqD6Wg6mM7LFwxyEWxgnON+mc5wlORR2dTAPBa+lS6jIrGfpKbsNqHxS2RrxUuIPc7JgIGLQAaAQW2D47qnFWmboiYYWyb0yAHyoje0Fk=; 7:rlsVpDMEaFFMct0mpWJft2BKSBuyR7961pbdBIh/1SnmJdXRDcP2b28AsolGysvU/fc4eoI6EC5Q+kdRE48v09UG0kBTrGSSCUHX0a9nSGp66WX6KH8wh4RXFrKCsUPKzsQdJKaHsmBWAADDQBqF+xC/9EQOMktMJmZb7WwiAWaDsgiUUFUIFCwYIks/p3wTpByZ5CkXxmRxYpGYJSWeA/mr63UwdZsIH78XeGeDNsXgd8DSCS95NcOoyjI93LRTBdr2fOUpd1gQNAFvAkoG+/xgDUHlyTdC8M4ICRQasH0=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0653;
x-microsoft-antispam-prvs: <DM2PR0301MB0653573C2EF058AC30C96242A82D0@DM2PR0301MB0653.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038); SRVR:DM2PR0301MB0653; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0653;
x-forefront-prvs: 098291215C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(24454002)(377454003)(199003)(189002)(81156014)(86612001)(7736002)(106356001)(5001770100001)(101416001)(305945005)(106116001)(11100500001)(105586002)(87936001)(99286002)(77096005)(5005710100001)(3660700001)(76576001)(5002640100001)(8666005)(54356999)(10090500001)(8990500004)(122556002)(7846002)(107886002)(10400500002)(33656002)(74316001)(92566002)(9686002)(10290500002)(8936002)(97736004)(2906002)(8676002)(76176999)(7696003)(2900100001)(50986999)(68736007)(2501003)(2950100001)(586003)(3280700002)(6116002)(189998001)(81166006)(5003600100003)(86362001)(102836003)(7059030)(3826002); 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)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jun 2016 21:03:41.6351 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0653
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/zHRTfPm6Qr_EKKyUUSsXPiY_3CQ>
Subject: Re: [dhcwg] On RFC 7819, privacy considerations for DHCP...
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Jun 2016 21:03:45 -0000

On Thursday, June 16, 2016 3:42 PM, David Singer wrote:
> 
> …has there been any discussion of the possibility of the client asking for a
> specific allocation strategy, specifically, “please give me a DIFFERENT IP
> address from what you would normally give me”?

We considered that in RFC 7844, but we associated it to randomization of the MAC Address, the Client Identifier Option (IPv4) or the DUID (IPv6). The idea being that if a node presents a different identity to the server, the server will mechanically provide a different address.

> One of the easiest ways to fingerprint a system is by IP address; MAC addresses
> are necessary local. If I’m trying to be private, it might be nice to be able to
> change my address on request.

Yes. The simplest way is to pick a new Client Identifier or a new DUID, as suggested in RFC 7844. But if the MAC Address remains constant, some servers could still use that to identify the client and serve the same address.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email