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

Mohacsi Janos <mohacsi@niif.hu> Wed, 16 March 2011 12:46 UTC

Return-Path: <mohacsi@niif.hu>
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 77A6B3A6911 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 05:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.041
X-Spam-Level:
X-Spam-Status: No, score=0.041 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
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 FNkHluShReut for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 05:46:56 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by core3.amsl.com (Postfix) with ESMTP id 780023A67FA for <ipv6@ietf.org>; Wed, 16 Mar 2011 05:46:56 -0700 (PDT)
Received: from cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [193.225.14.182]) by mail.ki.iif.hu (Postfix) with ESMTP id 90CF186D3A; Wed, 16 Mar 2011 13:48:21 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at cirkusz.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id ZUeglxSpRG+G; Wed, 16 Mar 2011 13:48:06 +0100 (CET)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 0A5F586D25; Wed, 16 Mar 2011 13:48:06 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 0645386BED; Wed, 16 Mar 2011 13:48:05 +0100 (CET)
Date: Wed, 16 Mar 2011 13:48:05 +0100
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
In-Reply-To: <4D80ADCF.7060409@gont.com.ar>
Message-ID: <alpine.BSF.2.00.1103161337140.87087@mignon.ki.iif.hu>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D80ADCF.7060409@gont.com.ar>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ran Atkinson <ran.atkinson@gmail.com>
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: Wed, 16 Mar 2011 12:46:57 -0000

On Wed, 16 Mar 2011, Fernando Gont wrote:

> On 16/03/2011 03:30 a.m., Christian Huitema wrote:
>>> Then what's all this controversy with
>>> draft-gont-6man-managing-privacy-extensions? :-) -- That aside,
>>> there have been quite a few publications asessing the real
>>> "privacy" provided with the so-called privacy-extensions....
>>
>> Using randomized host identifiers is way more private than sticking a
>> MAC address in the IPv6 address.
>
> Agreed. Also in some scenarios privacy extensions may give a false sense
> of privacy (see e.g. some of the pointers in our I-D).
>
>
>> In fact, rather than your draft
>> proposing to not use privacy addresses, we should pursue the
>> deprecation of using EUI-64 in addresses.
>
> Our draft is not meant to propose "not to use privacy addresses" -- as
> noted a few times, already, the proposed mechanism could be used to turn
> "privacy addresses" on for some systems that have decided not to enable
> them by default (e.g., FreeBSD).
>

As RFC 4941 says:

Changed the default setting for usage of temporary addresses to be 
disabled.

and also:
"
Additionally, sites might wish to selectively enable or disable the
    use of temporary addresses for some prefixes.  For example, a site
    might wish to disable temporary address generation for "Unique local"
    [ULA] prefixes while still generating temporary addresses for all
    other global prefixes.  Another site might wish to enable temporary
    address generation only for the prefixes 2001::/16 and 2002::/16,
    while disabling it for all other prefixes.  To support this behavior,
    implementations SHOULD provide a way to enable and disable generation
    of temporary addresses for specific prefix subranges.  This per-
    prefix setting SHOULD override the global settings on the node with
    respect to the specified prefix subranges.  Note that the pre-prefix
    setting can be applied at any granularity, and not necessarily on a
    per-subnet basis.
"

Best Regards,
 		Jans Mohacsi