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

Fernando Gont <fernando@gont.com.ar> Sun, 13 March 2011 00:23 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 D7B2D3A6A82 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:23:51 -0800 (PST)
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 qlMo-6noPJnc for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:23:51 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id C16923A6A75 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:23:50 -0800 (PST)
Received: by wyb42 with SMTP id 42so3848622wyb.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:25:11 -0800 (PST)
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=HmfClRCO5GE42U6LQQWMaIVifRVCgmE+fWWEK6ty/wA=; b=eie0OHa5NY0Et4oJvtpk0jewVnik5Cmzh3SmIB+OHpfDfERKNZbLJI8PxxYUjBlT1i 2+q2AvQIAnG2C/j6boxcv1ASlzOABE6jv5jYxlaCyfKM7VLCR3H4Y9wL7O70uTSDxBKD HHNoetBvtHxa2UezfPJbCS7DY0rBspbVJOQSc=
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=ciYYa8521hsHdlDReDWHLCzTcAZtHe3kNzZQ7xbu1zNNXepb7fTkRzT9Qsp3Jtltpu ktDyhzCXDP4BewZz67B5m7z0XLbfLppMbwPYBd1ZwWFP2Lwh0a57HdEOHUW3zFKj0RwP LlU7ZkW0dFZOlofsxb0TfBmqtn4uLv6e1YNKc=
Received: by 10.216.9.141 with SMTP id 13mr899549wet.73.1299975911404; Sat, 12 Mar 2011 16:25:11 -0800 (PST)
Received: from [192.168.200.18] ([194.2.150.133]) by mx.google.com with ESMTPS id m2sm3007833wer.13.2011.03.12.16.25.08 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 16:25:10 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7C0EE5.2080405@gont.com.ar>
Date: Sat, 12 Mar 2011 21:25:09 -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: Dan Wing <dwing@cisco.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> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com>
In-Reply-To: <262f01cbdf5d$607c69f0$21753dd0$@com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: 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: Sun, 13 Mar 2011 00:23:51 -0000

Hi, Dan,

On 10/03/2011 04:57 p.m., Dan Wing wrote:
>> Doesn't a combination of RFC4941 and NPTv6 produce the necessary
>> privacy over both parts of the IPv6 address?
>> (BTW thats a question from an interested observer new to this topic,
>> not a statement - I started following this thread and ended up digging
>> around in the RFCs and drafts the thread uncovered)
> 
> RFC4941 by itself does the trick.
> 
> But draft-gont-6man-managing-privacy-extensions (the subject of
> this thread) says "you can't use RFC4941".

It doesn't. The I-D aims at allowing routers specify which policy they
want hosts to employ when generating their IPv6 addresses.

Version -01 of the document probably makes this even more clear: the
router can actually advice nodes to use privacy addresses. -- As an
example, please note that while some stacks implement "privacy
extensions", they do not enable them by default. Thus, use of the
mechanism specified in this document could result in those boxes
*enabling*¨privacy addresses (if desired).

This document aims to improve the ability of the network administrator
of managing the generation of IPv6 addresses. It is not mean, per se, to
disable privacy addresses.

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