Re: 64bit MAC addresses and SLAAC

Mark Smith <markzzzsmith@gmail.com> Thu, 18 June 2020 12:04 UTC

Return-Path: <markzzzsmith@gmail.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 A972C3A0CC1 for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 05:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level:
X-Spam-Status: No, score=-0.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8P2f3D-fZrIS for <ipv6@ietfa.amsl.com>; Thu, 18 Jun 2020 05:04:50 -0700 (PDT)
Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EED43A0CC0 for <ipv6@ietf.org>; Thu, 18 Jun 2020 05:04:50 -0700 (PDT)
Received: by mail-oi1-x22e.google.com with SMTP id s21so4814378oic.9 for <ipv6@ietf.org>; Thu, 18 Jun 2020 05:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZOWlJJpKa6dP6fmdn/I9T5YyADVbVPaE32PfC5nU4yw=; b=CnkXCr4sUMQconTwYIL43jz669FYnMtctHuuHmnOcPwgt6Tmg5CStMXrgYdJy1f+mZ 0kgf/BcTTeb0meEttre9HKvNZ6MutL41Neq5CDLRoyZcEHRqOUy4x1veclgujkaCN3lg EtxxqMfvsGF9aruM9b5krKGKAX5P8Pj46fE/+elX1spMvREl9MUcZzAWAiqOYrXe+X/F Yx7KEfamhPmDMoy9IDPyrOVsypsF0EB0bcL/+qKJm4wcsqmo3ZLsu2BBwoLD0OGHw2/F 6hB65gIa/SMq1KZMyOWYX1zNMOU0Imzpio//+QVW3xZLXd9J3osKjshCoszVpHrdv/qC mROQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZOWlJJpKa6dP6fmdn/I9T5YyADVbVPaE32PfC5nU4yw=; b=fB9IEjauHcUBbn959mtdHmOsUsGIeTKoCQhwHCMPzFxMxYctDDH08a5gV+KrsgGeRG UL/u6651WA1+MKL8XvHuIZ2vRKCuH8c4KCNhka3OTUurKHu8ZNsUWwf6T7H2nGrfSGIk GFetVwl38ziL9alIfW/zEpecVbttmlmvCzr1OmhRanLX3Pi/K5nHZInapZgw554FZz3H pGEQQAprOVOYKUvDRrA5L+jBmZQXoUIO17iVTtNwiaT4s5ahzS6Mw2jzwFwF7UCLAe+8 eVWq+DXADj16OaKzW4psRV/VkfE5rL+oabOkTxbMhcNqC5vmm/7SM+bfZeMQulkkQKme Bb2A==
X-Gm-Message-State: AOAM531HzSg3ACzYSB7nhmAQBSbRuVD+KRSMl/ps3S3LvTlTMZUvNxiM QWKHRfyNIP1VNkR9qHpRj9TBE02gxemC+Qv3Lgms5A==
X-Google-Smtp-Source: ABdhPJwUQ6vj398fKIHtllP6fAsf61UU5DZR4FL7lk9JlyOZ8yBz1A44VxLIJJYCcW9rnqASpSuMtR+oUUK2tEnCo0w=
X-Received: by 2002:a54:4406:: with SMTP id k6mr2659168oiw.60.1592481889423; Thu, 18 Jun 2020 05:04:49 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <m1jlrYH-0000LgC@stereo.hq.phicoh.net>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 18 Jun 2020 22:04:23 +1000
Message-ID: <CAO42Z2y1ePUhuUBE6dwaJ836UFQ1O5kn85dJHJnBKw2Hq+vy_w@mail.gmail.com>
Subject: Re: 64bit MAC addresses and SLAAC
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Cc: 6man WG <ipv6@ietf.org>, Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kdPAMio5NzwcqkrChN1bzkT61sQ>
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 12:04:52 -0000

On Thu, 18 Jun 2020 at 20:14, Philip Homburg
<pch-ipv6-ietf-6@u-1.phicoh.com> 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?
>
> Same applies to any org that tries to renumber.
>
> I'm not saying that anything needs to be changed. Just that we should not
> oversell the privacy benefits.
>

I don't think we are. However, we also don't want to fall into the
trap of "it's not perfect, so let's do nothing". We're limited to
within our problem space, however we should try to provide the best
privacy we can without impacting end-user experience, or at least
limit impacting end-user experience to only when it is necessary to
try to assure privacy.

Similar to security, I think privacy is a weakest link problem. We
don't want IPv6 addresses to be the weakest link within the set of
device, OS or application session identifiers that reduce a device's
end-user's privacy.

For end-user devices, IPv6 addresses with privacy properties by
default is the best choice because typical end-users are not going to
have any idea what an IPv6 address is, let alone be able to properly
evaluate the privacy implications of whether or not they should have
IPv6 privacy addresses.

Regards,
Mark.



> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------