Re: 3484bis and privacy addresses

Fernando Gont <fgont@si6networks.com> Tue, 27 March 2012 17:42 UTC

Return-Path: <fgont@si6networks.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 4961C21F8666 for <ipv6@ietfa.amsl.com>; Tue, 27 Mar 2012 10:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 w3GObTtQ1o0h for <ipv6@ietfa.amsl.com>; Tue, 27 Mar 2012 10:42:35 -0700 (PDT)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id A7FB021F864C for <ipv6@ietf.org>; Tue, 27 Mar 2012 10:42:35 -0700 (PDT)
Received: from [2001:df8:0:16:1e65:9dff:febe:7f88] by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1SCaPZ-0006l7-4K; Tue, 27 Mar 2012 19:42:25 +0200
Message-ID: <4F71FC03.90403@si6networks.com>
Date: Tue, 27 Mar 2012 19:42:27 +0200
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20
MIME-Version: 1.0
To: Ray Hunter <Ray.Hunter@globis.net>
Subject: Re: 3484bis and privacy addresses
References: <4F716D5C.40402@innovationslab.net> <4F71F217.7000209@globis.net>
In-Reply-To: <4F71F217.7000209@globis.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, 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: Tue, 27 Mar 2012 17:42:36 -0000

On 03/27/2012 07:00 PM, Ray Hunter wrote:
> My take on this is that a set of a few hundred individual persons who
> are worried about privacy are more likely to be able to control their
> own particular machines to correctly override the "default off" setting
> than a single corporate network manager is to be able to guarantee
> overriding a "default on" setting on 100% of 10000 machines attached to
> their network.

Well, that's because we should probably do something like this:
<http://tools.ietf.org/id/draft-gont-6man-managing-slaac-policy-00.txt>

While I understand the "procedural constraints" (i.e., document in
WGLC), I think that much of the discussion that we're having is because
we have limited choices in a number of areas. Namely:

1) Inability to convey address-generation policy in RA messages.
2) Stable privacy-enhanced addresses

So we worry about selecting the right default because:

1) We have no mechanism to change that default dynamically
2) If we were to use stable addresses, in msot cases that implies
"privacy-harmful" addresses.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492