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

David Singer <singer@apple.com> Thu, 16 June 2016 22:41 UTC

Return-Path: <singer@apple.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 1B04B12DD1F for <dhcwg@ietfa.amsl.com>; Thu, 16 Jun 2016 15:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level:
X-Spam-Status: No, score=-5.728 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 LUukbmynkG8z for <dhcwg@ietfa.amsl.com>; Thu, 16 Jun 2016 15:41:37 -0700 (PDT)
Received: from mail-in2.apple.com (mail-out2.apple.com [17.151.62.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15DF212DC16 for <dhcwg@ietf.org>; Thu, 16 Jun 2016 15:41:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1466116896; x=2330030496; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=C8CAl9/4XlUoj27j6+XliWNDCje7IfaI8sEIKobL9rw=; b=dwiOaebsPkWaG+Gy2CGirjVaTI05PoykFNxrffqga0qdXpNvF/DeGU7isA447GYH MprFU3LcbEVjR51Qy7HVsajHFOiOjUtQLFBuEO0zquYUTRsLgU3tJOdb+hcIxVu8 f1UKSvHWdVS0MiFndQuU6XdK4IiGkSnd/66mcQ1jTb9XqlUBoq8poIGzsAuD3dmp BhzY8P0f648jshZXrNavsB99+ej7QqJbJ+K7XDwLohoJddVb8MrZ4CSYX9wMaP/S yJ17uW38GcFvGynDwa/6RqcbiTCvMSPXId51apg2cp0sBEv3EoZbYXr9c10l77N5 N2+Xp64yzmKbzIhzMY1ZFg==;
Received: from relay5.apple.com (relay5.apple.com [17.128.113.88]) by mail-in2.apple.com (Apple Secure Mail Relay) with SMTP id 77.FA.19292.02B23675; Thu, 16 Jun 2016 15:41:36 -0700 (PDT)
X-AuditID: 11973e11-f79356d000004b5c-0a-57632b20e83b
Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) (using TLS with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay5.apple.com (Apple SCV relay) with SMTP id 30.45.29065.02B23675; Thu, 16 Jun 2016 15:41:36 -0700 (PDT)
Received: from singda.apple.com (singda.apple.com [17.212.152.248]) by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0O8V0036WZ1CM120@nwk-mmpp-sz09.apple.com> for dhcwg@ietf.org; Thu, 16 Jun 2016 15:41:36 -0700 (PDT)
Sender: singer@apple.com
From: David Singer <singer@apple.com>
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: quoted-printable
Message-id: <64A0CA2D-C8C1-415B-A532-338E4B62DF14@apple.com>
Date: Thu, 16 Jun 2016 15:41:36 -0700
To: dhcwg@ietf.org
MIME-version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUi2FAYoaugnRxucOi5mcXdjhZGB0aPJUt+ MgUwRnHZpKTmZJalFunbJXBlnN9+iLHgC3PF25637A2MU5i7GDk5JARMJN6+mwRli0lcuLee DcQWEtjLKHFxVS5MzaH7/4BquIDiy5gkLrV3QzkrmST+vjjMCFIlLCAh8fHjZBYQm01AVeLB nGNAcQ4OZgF1iSlTwAYxC2hLPHl3gRWi3ELi5c/9YIt5BWwkLp5/AWazALXOmn+AHcQWERCS 2HL8HRNEjZ7E5KMNbBAHyUo8ObmIBeQGCYGrrBIn+88yT2AUnIWwbhaSdbOQtC9gZF7FKJSb mJmjm5lnpJdYUJCTqpecn7uJERSU0+0EdzAeX2V1iFGAg1GJh3eFaHK4EGtiWXFl7iFGaQ4W JXHeN9MSw4UE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwlh03Pjv7+pLmhv7KT81HCj7rbXmT VG2a7n2qKOrLYcMvrt0H56dkxhRnWR6SvtMht2z6jqfie44fdbDkcjd6VP1KIHqxOvcfM8m5 E5Y32z/R1VReyb3m8YP40O06Hgy/qpUdfkv77VP2TRavzjCM073gXHLSY1OV+rkrHlfadQrD +u44VIsqsRRnJBpqMRcVJwIA9rpX9isCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42IRbCgO0FXQTg43WL3NxOJuRwujA6PHkiU/ mQIYo7hsUlJzMstSi/TtErgyzm8/xFjwhbnibc9b9gbGKcxdjJwcEgImEofu/4OyxSQu3FvP 1sXIxSEksIxJ4lJ7NzOEs5JJ4u+Lw4wgVcICEhIfP05mAbHZBFQlHsw5BhTn4GAWUJeYMiUX JMwsoC3x5N0FVohyC4mXP/eDLeAVsJG4eP4FmM0C1Dpr/gF2EFtEQEhiy/F3TBA1ehKTjzaw QRwkK/Hk5CKWCYx8sxA2zEKyYRaSjgWMzKsYBYpScxIrTfUSCwpyUvWS83M3MYLDqDBiB+P/ ZVaHGAU4GJV4eFeIJocLsSaWFVfmHmKU4GBWEuEtUAMK8aYkVlalFuXHF5XmpBYfYpTmYFES 553nnRguJJCeWJKanZpakFoEk2Xi4JRqYKwNu+LYLXt7m4Z77P3Lv+fsN1S7mbFwWk/zEo1L rL+NRUI8XHYF+vQ8m5q9UyuzzPlKc04ZV/Wu94/2esnOYhPTZn7Gdqj0ONvX8+/XeT/1iCyc /c1fd75WM/us0z/zV7UpLFM5Mf1lgPnyRfF+qhMWGyy24smoUJvEqKH54/q+61o/gnOmfVdi Kc5INNRiLipOBABcWLzXHwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/7w3z1g4H-cWPkIOEZmGCLN6Fp9I>
Subject: [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, 16 Jun 2016 22:41:38 -0000

…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”?

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.

David Singer
Manager, Software Standards, Apple Inc.