IETF Logo Mail Archive

RE: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-01.txt

Christian Huitema <huitema@microsoft.com> Sat, 15 February 2014 00:24 UTC

Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E07A1A0158 for <ipv6@ietfa.amsl.com>; Fri, 14 Feb 2014 16:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 NN9HiqUsn1Zp for <ipv6@ietfa.amsl.com>; Fri, 14 Feb 2014 16:24:37 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0204.outbound.protection.outlook.com [207.46.163.204]) by ietfa.amsl.com (Postfix) with ESMTP id 34EEE1A0140 for <ipv6@ietf.org>; Fri, 14 Feb 2014 16:24:36 -0800 (PST)
Received: from DM2PR03CA007.namprd03.prod.outlook.com (10.141.52.155) by BLUPR03MB589.namprd03.prod.outlook.com (10.255.124.35) with Microsoft SMTP Server (TLS) id 15.0.878.16; Sat, 15 Feb 2014 00:24:32 +0000
Received: from BN1BFFO11FD038.protection.gbl (2a01:111:f400:7c10::1:155) by DM2PR03CA007.outlook.office365.com (2a01:111:e400:2414::27) with Microsoft SMTP Server (TLS) id 15.0.878.16 via Frontend Transport; Sat, 15 Feb 2014 00:24:32 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1BFFO11FD038.mail.protection.outlook.com (10.58.144.101) with Microsoft SMTP Server (TLS) id 15.0.868.13 via Frontend Transport; Sat, 15 Feb 2014 00:24:31 +0000
Received: from TK5EX14MBXC302.redmond.corp.microsoft.com ([169.254.2.226]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0174.002; Sat, 15 Feb 2014 00:23:54 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, Alissa Cooper <alissa@cooperw.in>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-01.txt
Thread-Topic: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-01.txt
Thread-Index: AQHPKbTGum4CxepzqEuRLO1ZYGGEqZq1GL6AgAArHPCAAA3GgIAAIkxg
Date: Sat, 15 Feb 2014 00:23:54 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA3DFC1CB3@TK5EX14MBXC302.redmond.corp.microsoft.com>
References: <20140214184335.29433.45425.idtracker@ietfa.amsl.com> <CF23A554.13ED6%alissa@cooperw.in> <C91E67751B1EFF41B857DE2FE1F68ABA3DFC18C5@TK5EX14MBXC302.redmond.corp.microsoft.com> <52FE95ED.7090900@si6networks.com>
In-Reply-To: <52FE95ED.7090900@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.71]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(199002)(189002)(51704005)(47976001)(50986001)(47736001)(69226001)(49866001)(74706001)(55846006)(74662001)(47446002)(74502001)(76796001)(85306002)(77096001)(31966008)(80976001)(44976005)(87266001)(4396001)(56776001)(59766001)(53806001)(86612001)(95416001)(54316002)(23726002)(76482001)(74366001)(51856001)(95666001)(87936001)(77982001)(46102001)(54356001)(81542001)(50466002)(74876001)(6806004)(56816005)(92566001)(81816001)(90146001)(81342001)(2656002)(81686001)(86362001)(80022001)(33656001)(63696002)(94946001)(93136001)(47776003)(93516002)(79102001)(46406003)(83322001)(20776003)(94316002)(92726001)(83072002)(66066001)(65816001)(85852003)(60764002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB589; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:BFD6C6D1.2F1A479A.41E89F8B.4CC2FC71.201A7; MLV:sfv; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 012349AD1C
X-OriginatorOrg: microsoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/nzPGJ9SVmf2kEEe9yoGiagnnRhQ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Feb 2014 00:24:39 -0000

>> Can we add a discussion of the issue to this address privacy draft?
>
> I personally have no issues. My only "concern" is that if we start discussing IDs other than the IPv6 addresses, we might later discuss e.g. layer-7 stuff. Not that layer-2 and layer-7 privacy issues are uninteresting.. but rather than the more focused we stay, the more tractable the problem is.

I would not want to discuss in an IPv6 draft the precise mechanics of changing MAC addresses, or the policy controls to make avoid nasty side effects. I would like to see a simple issue debated: "assuming that the host administrator has programmed the host to change its MAC address before visiting network X, can we guarantee that the IPv6 IID does not leak information about the identity of the host."


-- Christian Huitema

v2.23.0 | Report a Bug | By Email