IETF Logo Mail Archive

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

Fernando Gont <fernando@gont.com.ar> Fri, 25 March 2011 04:29 UTC

Return-Path: <fernando.gont.netbook.win@gmail.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 5BD893A6943 for <ipv6@core3.amsl.com>; Thu, 24 Mar 2011 21:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 KuhhmJPhP6ZG for <ipv6@core3.amsl.com>; Thu, 24 Mar 2011 21:29:25 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id EC6153A6946 for <ipv6@ietf.org>; Thu, 24 Mar 2011 21:29:24 -0700 (PDT)
Received: by yxk30 with SMTP id 30so356149yxk.31 for <ipv6@ietf.org>; Thu, 24 Mar 2011 21:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=XR5n4m0L8e6dye2xxexx7Em9tvAvYHMhAhxYAcF0UGs=; b=MJkcSmdVQuD20Vie4+lSuAUgJMj9L54eqbJYfNsylzqQmGdy4GHmb6C4JMFMS98tgy iUvavguiQuiocqEpm7875OJ6LpX9eCsXmc0WY0MrJmqcaIsjvBaPW5NZjxFvR5L1wl3Y +OnVRNXNtCnLJFHmv/zJBqemdgHVImAVO867I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=PaYT4LVfzFGTkQnWE9LiVoyR/7K8oGMSj7Uayqy+PFLR0QyYHHeT74GJnKQUrcd3tp I6cU7T5uLp90VoI4U8O45aQFHmcbw2w0p4CE4prhim0zud0N4EKn11bB4gYREkE1EjPt zzgabFeLIXoOmgtijhhR2UTMizywmyqAN7Yjg=
Received: by 10.101.55.11 with SMTP id h11mr254154ank.52.1301027459696; Thu, 24 Mar 2011 21:30:59 -0700 (PDT)
Received: from [192.168.123.101] ([190.48.254.9]) by mx.google.com with ESMTPS id b28sm654597anb.22.2011.03.24.21.30.53 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 24 Mar 2011 21:30:56 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D8C1A78.4010505@gont.com.ar>
Date: Fri, 25 Mar 2011 01:30:48 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Brian Haley <brian.haley@hp.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D7B5914.6090000@gont.com.ar> <4D80EAAF.6010509@hp.com>
In-Reply-To: <4D80EAAF.6010509@hp.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, 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, 25 Mar 2011 04:29:26 -0000

On 16/03/2011 01:51 p.m., Brian Haley wrote:

> I have an almost off-topic comment, but since I've seen no mention of it
> in any of these privacy threads...
> 
> You have to assume in a large data center that almost every MAC address you
> encounter is going to be randomly generated.  

Are they actually random? i.e., I'm curious about the algorithm used for
generating the Interface IDs.


> This is because there are
> *lots* of virtual machines out there, and the density of them is increasing
> exponentially.  Their MACs could change daily as they are deployed and
> decommissioned, but from their perspective their MAC is hardware-based.
> I know you have this as a "SHOULD" requirement, but figured I should mention
> it since it's one of those places where this bit will be completely ignored.

>From the point of view of the VMs, they would still be using Modified
EUI-64 Interface Identifiers. This is not that different from the case
in which the admin sets the MAC address of an interface to some value
that he wants (other than the *real* address of the interface). IMHO,
this is out-of-scope for this document.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1

v2.23.0 | Report a Bug | By Email