IETF Logo Mail Archive

RE: draft-gont-6man-managing-privacy-extensions-00.txt

Christian Huitema <huitema@microsoft.com> Fri, 11 March 2011 02:31 UTC

Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 569573A6AC2 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 18:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level:
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1HLZe71Ji8KO for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 18:31:16 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 350B33A69B6 for <ipv6@ietf.org>; Thu, 10 Mar 2011 18:31:16 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 10 Mar 2011 18:32:34 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 10 Mar 2011 18:32:34 -0800
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.56]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0270.002; Thu, 10 Mar 2011 18:32:34 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'Paul Chilton' <paul.chilton@nxp.com>, 'james woodyatt' <jhw@apple.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Topic: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Index: AQHL3kEKAbTYw5EzSU+RGMZ29OXheJQlYKSAgAB+ZoCAANWqgIAATRSAgABA0wCAACYHAIAAG7iA///mPyA=
Date: Fri, 11 Mar 2011 02:32:32 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com>
In-Reply-To: <262f01cbdf5d$607c69f0$21753dd0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 02:31:20 -0000

> I'm saying the reasons people are tempted to disable RFC4941 are misplaced.  

+1

Consider that if I want privacy and you won't let me use RFC4941, I might just make up a new MAC address each time I connect.

Consider also the effect of unique identifiers on tracking. The MAC address follows you when you roam. By embedding it in the IPv6 address, we are effectively offering a "super cookie" to all web services. Is it really what we want? In addition to privacy issues, displaying the MAC address allows third parties to track hardware purchase, and enables other attacks by providing the data necessary for MAC spoofing. In short, it looked like a great idea at the time... but wasn't.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email