Re: 64bit MAC addresses and SLAAC

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Thu, 18 June 2020 15:41 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 4A6E03A09FB for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 08:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level:
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 60oPMQowu5IG for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 08:41:17 -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 D94FD3A09F8 for <ipv6@ietf.org>; Thu, 18 Jun 2020 08:41:16 -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 m1jlwfC-0000QUC; Thu, 18 Jun 2020 17:41:14 +0200
Message-Id: <m1jlwfC-0000QUC@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: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <a17ae9f3-001c-07f6-84f9-a0ca583e6a00@gmail.com> <7AE5B6D0-AB01-4077-A9EF-5BD86F428681@gmail.com> <CAC8QAcdDjQvonke7hytV8pCYsTAjATNi560v_b32jus_jDW8bw@mail.gmail.com> <b43a00f5-c957-923a-cef4-ed541ebdb39a@gmail.com> <a96f1262-d152-dc09-1c2f-b2604ca21890@si6networks.com> <m1jlb8u-0000JDC@stereo.hq.phicoh.net> <d23c967b-29fc-cf94-d51b-70d200ee195f@si6networks.com> <CABNhwV2+pq9fwWA=X4eN064gdtOV628pgaSMmDEyq3ANX6xZxg@mail.gmail.com> <m1jlg0W-0000LDC@stereo.hq.phicoh.net> <8ffadf93-b250-30ce-c03b-b28ddd161eb3@gmail.com>
In-reply-to: Your message of "Thu, 18 Jun 2020 16:24:32 +0200 ." <8ffadf93-b250-30ce-c03b-b28ddd161eb3@gmail.com>
Date: Thu, 18 Jun 2020 17:41:14 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-EaerRp9rBEo6iZMh7h7gDH1KdQ>
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:41:18 -0000

> If that 'C' is not seeded well enough, or has licenses on it, or
> is IPRed, or is not open source, or bleeds when attacked by a
> distributed.net lucky PC, or is not resisting quantum attacks after
> tomorrow, or was not fully tested against endianness on this new
> IoT platform, or is too slow, or simply does not compile there -
> then we're at risk.

You always write an RFC that discusses which function to use for generating
IIDs.

In this context, SHA2 is safe against quantum attacks. You do need a way
of providing a device with a stable secret. However, you probably need that
for any kind of security. If you cannot do that, then it is probably better
to avoid connecting the device to the internet.