Re: 64bit MAC addresses and SLAAC

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Fri, 19 June 2020 13:35 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 7A9C23A09D7 for <ipv6@ietfa.amsl.com>; Fri, 19 Jun 2020 06:35:04 -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 Ziv-f9iUVwXK for <ipv6@ietfa.amsl.com>; Fri, 19 Jun 2020 06:35:02 -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 7DF0F3A0954 for <ipv6@ietf.org>; Fri, 19 Jun 2020 06:35:01 -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 m1jmHAN-0000OcC; Fri, 19 Jun 2020 15:34:47 +0200
Message-Id: <m1jmHAN-0000OcC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: "Pascal Thubert (pthubert)" <pthubert@cisco.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> <m1jlwVZ-0000RgC@stereo.hq.phicoh.net> <MN2PR11MB356561378679A6AD1CA895B4D8980@MN2PR11MB3565.namprd11.prod.outlook.com>
In-reply-to: Your message of "Fri, 19 Jun 2020 09:09:15 +0000 ." <MN2PR11MB356561378679A6AD1CA895B4D8980@MN2PR11MB3565.namprd11.prod.outlook.com>
Date: Fri, 19 Jun 2020 15:34:45 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/C-o8bn4PRvPOYYAQY_ggWv5kIJ4>
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 13:35:04 -0000

> > 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.
> >
> Is this really, deep down, the nature of SLAAC? Or the consequence
> of not having a very fast and reliable DAD? Arguably one could
> autoconfig even IPv4 within a /24 if there's a broker that serializes
> the requests and rejects the duplicates.  

We have that broker, it is called DHCPv6.

Absent such a centralized service, a host would have a hard time proving that
a address unique, for example, there might be a network split.

Current DAD is certainly not good enough if there are regular address
collisions and I doubt anybody is willing to come up with a better DAD
just to have nicer looking addresses in SLAAC.