Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06

Fernando Gont <fgont@si6networks.com> Tue, 23 April 2013 17:40 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E1C21F91B2 for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 10:40:22 -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=[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 q4KvHqQE834z for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 10:40:21 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 4854021F9157 for <ietf@ietf.org>; Tue, 23 Apr 2013 10:40:20 -0700 (PDT)
Received: from [186.134.53.35] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUhCN-0006Yb-69; Tue, 23 Apr 2013 19:40:11 +0200
Message-ID: <5176C774.7080300@si6networks.com>
Date: Tue, 23 Apr 2013 12:40:04 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, RJ Atkinson <rja.lists@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 17:40:22 -0000

Hi, Christian,

On 04/23/2013 12:02 PM, Christian Huitema wrote:
> After reading the document again, the main issue is that the document
> specifies a solution to a problem by detailing a specific
> implementation,

I personally disagree (see below).


> but does not explain the design choices behind that
> solution. As such, we end up with an over constrained specification,
> which at the same time fails to explain the problems at hand.

Could you please elaborate?



> As Mike St-Johns pointed out, the solution is trivial:

Can you post an URL for such comment? -- Because I've not been able to
find anything sent by Mike along those lines.


[....]
> Instead, the draft goes into great details on how to actually
> implement the random number generator. 

I disagree. In the draft, F() is the PRF. Where in the I-D are we trying
to provide details on how to implement F()?


> Apart from not being
> necessary, some of these details are wrong. For example, the
> suggested algorithm includes an "interface index," but different
> operating systems have different ways of enumerating interfaces, and
> the variations in enumeration could end up violating the "stable
> address" property.

Which vaiations are you referring to?

(FWIW, this I-D does not require any particular namespeace fr the
INterface Index).



> I would also explain the inherent issues that have to be solved,
> e.g., swapping interfaces, or enabling multi-homed hosts.

FWIW, constant addreses when swapping interfaces is not really a goal f
tis dcument, but rather a byproduct of it.


> And I would
> observe that the DAD problem cannot be solved ina  reliable way.

Could you please elaborate?

Thanks!

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