Re: 64bit MAC addresses and SLAAC

Fernando Gont <fgont@si6networks.com> Thu, 18 June 2020 10:33 UTC

Return-Path: <fgont@si6networks.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 58C653A08C3 for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 03:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 B4T5MF7xKao2 for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 03:33:07 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99F863A08C9 for <ipv6@ietf.org>; Thu, 18 Jun 2020 03:33:07 -0700 (PDT)
Received: from [IPv6:2800:810:464:1f7:59f5:79ee:c876:5454] (unknown [IPv6:2800:810:464:1f7:59f5:79ee:c876:5454]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id F3FEA2837AD; Thu, 18 Jun 2020 10:32:56 +0000 (UTC)
Subject: Re: 64bit MAC addresses and SLAAC
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
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> <m1jlrYH-0000LgC@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <26ff14b3-5ae8-c14a-8030-30f83930674e@si6networks.com>
Date: Thu, 18 Jun 2020 07:29:49 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1jlrYH-0000LgC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/F7JZIGsR6CTNzwbkzV-ryBUt8Io>
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 10:33:09 -0000

On 18/6/20 07:13, Philip Homburg wrote:
>>> If a host is connected to a subnet that has multiple prefixes, then using
>>> the same IID for all prefixes only has marginally less privacy than
>>> using different IIDs.
>>
>> Well, it does allow correlation of network activities across addresses.
>> In a way, that's kind of the same as when a host moves across networks.
> 
> My home network has a number of prefixes. From reverse DNS you can easily
> figure out that they are the same. How does it help me to have different IIDs
> for different prefixes?

different-per-prefix IIDs cannot, of course, mitigate information 
leakages that happens elsewhere.

FWIW, I use about 7+ GUA prefixes at home, with no reverse DNS mappings. 
RFC7217 prevents activity correlation  among them. Traditional SLAAC 
IIDs would have made it trivial.


> I'm not saying that anything needs to be changed. Just that we should not
> oversell the privacy benefits.

As noted in many discussions we have had on the topic, ipv6 iid 
"randomization" mitigates correlation at the network level. In your 
particular scenario, the information leakage happens elsewhere.

i.e., if you want to mitigate activity correlation as a whole, doing 
something sensible for ipv6 addresses is one bit of the "puzzle".

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492