IETF Logo Mail Archive

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

Christian Huitema <huitema@microsoft.com> Sat, 12 March 2011 16:39 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 58D143A6945 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 08:39:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level:
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 cXY0miLBiuyo for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 08:39:38 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id B4BAB3A68F1 for <ipv6@ietf.org>; Sat, 12 Mar 2011 08:39:38 -0800 (PST)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 12 Mar 2011 08:40:59 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.1.270.2; Sat, 12 Mar 2011 08:40:59 -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; Sat, 12 Mar 2011 08:40:58 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Scott W Brim <scott.brim@gmail.com>, Mark Townsley <mark@townsley.net>
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///mPyCAATgCgIABt1eA//+QKvA=
Date: Sat, 12 Mar 2011 16:40:58 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F0C22F4@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> <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <EF3F736B-777F-4F03-8AB5-62D46452B942@townsley.net> <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
In-Reply-To: <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-brim-mobility-and-privacy@tools.ietf.org" <draft-brim-mobility-and-privacy@tools.ietf.org>, "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: Sat, 12 Mar 2011 16:39:40 -0000

> Blue sky: Could the SP allow privacy addresses, at least for global use, and log its own mappings between privacy 
> addressses and MACs or other persistent identifiers?  Then it can always trace back to determine who did what if necessary.

That's more or less what Windows does by default. The persistent address is not derived from the MAC, but from a hash of the prefix and the MAC id. Like a privacy address, it does not expose the MAC. Unlike a privacy address, its lifetime is as long as the routers will allow. This means nodes have a stable address in the corporate network, and can be easily traced within that network. But they get different addresses when they move around, and cannot be easily traced by third parties.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email