RE: Why /64

Wuyts Carl <Carl.Wuyts@technicolor.com> Mon, 28 October 2013 08:30 UTC

Return-Path: <Carl.Wuyts@technicolor.com>
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 D02DB11E822E for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level:
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OS-38MCZtWGK for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 01:30:50 -0700 (PDT)
Received: from na3sys009aog113.obsmtp.com (na3sys009aog113.obsmtp.com [74.125.149.209]) by ietfa.amsl.com (Postfix) with ESMTP id 3D05411E822D for <ipv6@ietf.org>; Mon, 28 Oct 2013 01:30:34 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob113.postini.com ([74.125.148.12]) with SMTP ID DSNKUm4goZWMrCQ5MgjSQYNClPDbKtfop0AK@postini.com; Mon, 28 Oct 2013 01:30:39 PDT
Received: from MOPESMAILHC02.eu.thmulti.com (141.11.100.29) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 28 Oct 2013 09:28:05 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.71]) by MOPESMAILHC02.eu.thmulti.com ([141.11.100.29]) with mapi; Mon, 28 Oct 2013 09:28:05 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Jeroen Massar <jeroen@massar.ch>, Octavio Alvarez <alvarezp@alvarezp.ods.org>
Date: Mon, 28 Oct 2013 09:28:03 +0100
Subject: RE: Why /64
Thread-Topic: Why /64
Thread-Index: Ac7Tt1g3Lo1LesjSRUqunVFAFSxg5QAABgIQ
Message-ID: <3135C2851EB6764BACEF35D8B495596806FAC25D4E@MOPESMBX01.eu.thmulti.com>
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> <526E1F5A.2070901@massar.ch>
In-Reply-To: <526E1F5A.2070901@massar.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
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.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 08:30:56 -0000

+1 for the /64 on the link and /48 for enterprise, 

but "at least" a /56 for home (with /60 too tiny) ??
Can you elaborate on why you would need more than 4 bits subnets @ home?

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Jeroen Massar
Sent: maandag 28 oktober 2013 9:25
To: Octavio Alvarez
Cc: <ipv6@ietf.org>
Subject: Re: Why /64

On 2013-10-27 16:53, Octavio Alvarez wrote:
> 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 did not state anything like that. I have only raised concern about stating that "IPv6 privacy addresses" are a real thing.

I am pro /64 per link and a /48 for Enterprise and at least /56 for Home-user sites. (/60 is too tiny and not flexible enough)

Greets,
 Jeroen

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------