Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 19 May 2016 09:10 UTC

Return-Path: <alexandre.petrescu@gmail.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 8BB4912D124 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 02:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.333
X-Spam-Level:
X-Spam-Status: No, score=-4.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZ3hZPkCbM5E for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 02:10:26 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8F3012B00E for <ipv6@ietf.org>; Thu, 19 May 2016 02:10:25 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4J9ANrf016387 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:23 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C4A61206988 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:25 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BAA912069C0 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:25 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4J9ANj4007060 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:23 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com> <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com>
Date: Thu, 19 May 2016 11:10:23 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GsT93papqlKMy5bnC7bLzXNTGBY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 19 May 2016 09:10:27 -0000


Le 19/05/2016 à 11:03, Lorenzo Colitti a écrit :
> On Thu, May 19, 2016 at 5:38 PM, Mark Smith <markzzzsmith@gmail.com
> <mailto:markzzzsmith@gmail.com>> wrote:
>
> So how would the IPv6 layer test that, and if it was tested properly,
> what happens if the test fails?
>
> The code that configures both layer 2 and layer 3 can simply call
> arc4random_buf (or your favourite random function)

I think the question is to decide when to call that random
function.

A 48bit identifier is often there already, but we need to use if it's
random, or generate one if it's not random.  So how to test whether it's
random?

> and then "ifconfig wlan0 hw ether <foo>", and then pick an EUI-64 IID
> based on that. Even if the hardware does not support the hardware
> address and does not return an error, but silently continues to use
> the hardware MAC address, the resulting IPv6 address is still random
> and free from privacy concerns.
>
> I think the testing of layer 2 address randomisation, and coming up
> with a both a user acceptable and friendly scheme to deal with a test
> failure is harder and more complex that just universally applying
> RFC7217 to all past, current and future link layers, regardless of
> how good or bad their link layer addresses are.
>
> This is really not hard to test in any hardware qualification lab.
> Really, it isn't.

On the contrary, I think it is very hard to test a number to see whether
it's random - you need a very expensive lab and out-of-band info.

Alex

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