Re: 64bit MAC addresses and SLAAC

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Thu, 18 June 2020 15:31 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 42C5C3A0898 for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 08:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 E7vbPC4UeCwE for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 08:31:37 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1D0F3A09D6 for <ipv6@ietf.org>; Thu, 18 Jun 2020 08:31:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1jlwVZ-0000RgC; Thu, 18 Jun 2020 17:31:17 +0200
Message-Id: <m1jlwVZ-0000RgC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: 64bit MAC addresses and SLAAC
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <e716dc36b56f4806b4c4dbfbf1ab852a@boeing.com> <04B8995F-7BF9-4DB0-826C-9E4BF95FD169@employees.org> <43ce64f0-3373-ca9a-f83d-40c44c4d5920@gmail.com>
In-reply-to: Your message of "Thu, 18 Jun 2020 16:10:11 +0200 ." <43ce64f0-3373-ca9a-f83d-40c44c4d5920@gmail.com>
Date: Thu, 18 Jun 2020 17:31:16 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9IDN2HUECgImGkWPYdtwzfsDW5o>
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: Thu, 18 Jun 2020 15:31:39 -0000

> 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.

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.