Re: [EXTERNAL] Re: 64bit MAC addresses and SLAAC

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Thu, 18 June 2020 09:43 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 401D03A11BA for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 02:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 L5-q4A5mtUOh for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 02:43:42 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D1543A0FC9 for <ipv6@ietf.org>; Thu, 18 Jun 2020 02:43:41 -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 m1jlr4w-0000TyC; Thu, 18 Jun 2020 11:43:26 +0200
Message-Id: <m1jlr4w-0000TyC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: Re: [EXTERNAL] 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: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <a17ae9f3-001c-07f6-84f9-a0ca583e6a00@gmail.com> <7AE5B6D0-AB01-4077-A9EF-5BD86F428681@gmail.com> <7a3b839f-099e-8fd3-35a2-4625df3c369e@gmail.com> <76e8bd7a-4333-480f-de0f-dcc775418739@si6networks.com> <79d494caa7874696b787aadb80cc322b@boeing.com> <MN2PR11MB35654EDB29696C2C33412691D89B0@MN2PR11MB3565.namprd11.prod.outlook.com> <m1jlpmX-0000IXC@stereo.hq.phicoh.net> <MN2PR11MB35659C6CB3BD16CDF423CD59D89B0@MN2PR11MB3565.namprd11.prod.outlook.com>
In-reply-to: Your message of "Thu, 18 Jun 2020 08:41:08 +0000 ." <MN2PR11MB35659C6CB3BD16CDF423CD59D89B0@MN2PR11MB3565.namprd11.prod.outlook.com>
Date: Thu, 18 Jun 2020 11:43:24 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Clku1-IHW7yN1JNIBPLpad0Z-iQ>
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 09:43:44 -0000

> In the case of IPv6 over IEEE 802.15.4, there is a centralized
> assignment of the short MAC address, and then SLAAC can derive the
> IP address from that MAC address to enable stateless compression.
> Nothing wrong with that if that serves the purpose.

If the MAC address is dynamically assigned by the network, then we can
assume that having the IID based on the MAC address is safe from the point
of view of tracking.

This is very far from the original concept of using a globally unique MAC
address as IID.

We should avoid using tracking identifiers as IIDs. However, that does not
rule out using other dynamically generated identifiers as part of IIDs.

> When people want the address to be known by the management
> system and associated to the role / position of the device, the
> easiest is usually the pre-provisioning, and forcing DHCP in that
> picture is a hard sell.

How is pre-provisioning related to SLAAC? Lot's of servers get addresses from
out of band configuration systems.