IETF Logo Mail Archive

Re: Why /64

Octavio Alvarez <alvarezp@alvarezp.ods.org> Mon, 28 October 2013 16:32 UTC

Return-Path: <alvarezp@alvarezp.ods.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F57011E82BD for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4sF9ondDuAs for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 09:32:18 -0700 (PDT)
Received: from sobre.alvarezp.com (sobre.alvarezp.com [173.230.155.94]) by ietfa.amsl.com (Postfix) with ESMTP id B52E511E8292 for <ipv6@ietf.org>; Mon, 28 Oct 2013 09:32:16 -0700 (PDT)
Received: from [192.168.2.251] (189.220.45.207.cable.dyn.cableonline.com.mx [189.220.45.207]) by sobre.alvarezp.com (Postfix) with ESMTPSA id 5F5C1613D; Mon, 28 Oct 2013 12:32:16 -0400 (EDT)
Message-ID: <526E91A3.8000807@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:32:35 -0700
From: Octavio Alvarez <alvarezp@alvarezp.ods.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130821 Icedove/17.0.8
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Why /64
References: <20131021224346.32495.64932.idtracker@ietfa.amsl.com> <52695DDE.70909@gont.com.ar> <526AA24F.6010609@gmail.com> <526AACA5.7090604@si6networks.com> <E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <EMEW3|9f43bef2fe7433173858819bd0eeee2dp9OKUJ03tjc|ecs.soton.ac.uk|E0F0D3DE-D31B-4CC2-9384-DFEBCCB8F557@ecs.soton.ac.uk> <526AC8AF.4060608@si6networks.com> <8C48B86A895913448548E6D15DA7553BA7B978@xmb-rcd-x09.cisco.com> <CAKD1Yr0q2dY041CMarFfTZZx6=qHC-eJ+74qgiHP-dt7+ga7yg@mail.gmail.com> <526CDC59.4070204@massar.ch> <526D3706.5070409@alvarezp.ods.org> <526E43E8.3080601@gmail.com>
In-Reply-To: <526E43E8.3080601@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: "<ipv6@ietf.org>" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "Fred Baker (fred)" <fred@cisco.com>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 28 Oct 2013 16:32:24 -0000

On 10/28/2013 04:00 AM, Alexandru Petrescu wrote:
> Le 27/10/2013 16:53, Octavio Alvarez a écrit :
>> On 10/27/2013 02:26 AM, Jeroen Massar wrote:
>>>> allows privacy,
>>>
>>> IMHO big nonsense. The company (amongst many others!) you work for uses
>>> amongst others cookies to track their people, and if they really bother
>>> could even use natural language structure, search query types, and other
>>> behavior for breaking this 'privacy'. Also note that even if the last
>>> 64bits are random, your company should be more than able to say "oh,
>>> there are typically X users in there, it likely is Y"...
>>
>> Then why deprecate EUI-64?
> 
> I think there is a problem in naming that draft.

I meant "why deprecate EUI-64 as device-ID in IPv6 addresses". Sorry if
this starts a misconception.

v2.34.0 | Report a Bug | By Email | System Status