Re: 64bit MAC addresses and SLAAC

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 19 June 2020 08:39 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 219EB3A082F for <ipv6@ietfa.amsl.com>; Fri, 19 Jun 2020 01:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.668
X-Spam-Level:
X-Spam-Status: No, score=0.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 Spt1szkqCi3F for <ipv6@ietfa.amsl.com>; Fri, 19 Jun 2020 01:39:04 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E365A3A0827 for <ipv6@ietf.org>; Fri, 19 Jun 2020 01:39:03 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 05J8d1qJ013524; Fri, 19 Jun 2020 10:39:01 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3A28E203CA6; Fri, 19 Jun 2020 10:39:01 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2C78E203C00; Fri, 19 Jun 2020 10:39:01 +0200 (CEST)
Received: from [10.11.241.6] ([10.11.241.6]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 05J8d0wk024590; Fri, 19 Jun 2020 10:39:00 +0200
Subject: Re: 64bit MAC addresses and SLAAC
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <e716dc36b56f4806b4c4dbfbf1ab852a@boeing.com> <04B8995F-7BF9-4DB0-826C-9E4BF95FD169@employees.org> <43ce64f0-3373-ca9a-f83d-40c44c4d5920@gmail.com> <m1jlwVZ-0000RgC@stereo.hq.phicoh.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e1841bf2-be1f-7699-e3d3-b0abee255c36@gmail.com>
Date: Fri, 19 Jun 2020 10:39:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <m1jlwVZ-0000RgC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8hZr5x9o7HlHOwae1KINEpqmrsI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 19 Jun 2020 08:39:05 -0000



Le 18/06/2020 à 17:31, Philip Homburg a écrit :
>> We looked for the place in linux which forces the 64bit limit in 
>> SLAAC.
> 
> Which make sense, because that is what the RFC says.
> 
>> We found it and we wondered what to put in these - potentially 66 -
>> bits of an IID?   The immediate thought was to put there random
>> numbers. These random numbers seemed natural to several of us.  And
>> they offer privacy.
> 
> I'm sure that if SLAAC is updated to allow other lengths, some
> consideration will be given to generating IIDs. However, at the
> moment SLAAC is 64-bit even if some implementations try to be more
> flexible.
> 
>> If we put random numbers in there then for years again the users 
>> will find it difficult to remember those scrambled numbers when 
>> typing ifconfig.
> 
> That is the nature of SLAAC. You need an IID that has a very high
> probabily of being unique. So you need enough random bits.

Indeed it seems so that nature.  If one wants numbers that are likely to
be unique, probably random numbers are the easiest and safest choice.

Maybe a 14 volume Oxford dictionary indexed by a random pointer would
still issue words likely to be unique.

Probably that kind of generation is more particular to DHCPv6, or so.

Alex

> 
> If you want easy to remember addresses, go for DHCPv6.
> 
>> If we put random numbers in there then for years again people will 
>> look for easy to use, license-free, platform-independent, high 
>> performance, speedy, C standard, less energy consuming,
>> almost-true random, primitives to call; and their seeds.
> 
> It is not to hard to find an SHA2-HMAC implementation.
>