Re: [Madinas] I-D Action: draft-ietf-madinas-mac-address-randomization-10.txt

Bob Hinden <bob.hinden@gmail.com> Sat, 13 January 2024 19:46 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: madinas@ietfa.amsl.com
Delivered-To: madinas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B545C14F5E9 for <madinas@ietfa.amsl.com>; Sat, 13 Jan 2024 11:46:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YuDgOsKGCh1S for <madinas@ietfa.amsl.com>; Sat, 13 Jan 2024 11:46:17 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 280B0C14F5EA for <madinas@ietf.org>; Sat, 13 Jan 2024 11:46:17 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id d75a77b69052e-429ca07044eso15070501cf.3 for <madinas@ietf.org>; Sat, 13 Jan 2024 11:46:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705175176; x=1705779976; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=WK0XEFkAbpFg+UQ3jgXrbqTl5xSuO9+2wPlul79V9Xg=; b=WQnHQ1jOatLEBtuBCJQ5fwzoyCfM5ucs/5FPeEtfYyk5eIoHG551az4nuet//7AZIj ITj2WbKLaSd/bSd7Wjtq1PTsjtV1F1uaUfsu2oVQDDorRwjSh86xprwZJf3aFOeh8WIl d/Eq4oh1iFE+qfzMrKeaD/tfHboSNuIHHXoMUYAr4qG2Qo0IMAMS0lvcPaJDJJUCBxuo j6EHh3dXqUaBlt7LpOIC8dM9BMmi5I9pHMF7SMg0BWOLfXEj3PXRrDj62tP0+TOy+XiH qGw/RI8f2lPEQp7SpQR4q1uxOiT81VeOzkbgI0CVuIz6Ex3DXosmvXDXuOwxLXqccGCb IFpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705175176; x=1705779976; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=WK0XEFkAbpFg+UQ3jgXrbqTl5xSuO9+2wPlul79V9Xg=; b=ZFqdJGJS6q3yNxQT1qpyFyHbB8sJI7uihCUZpUYYw22Q0EBbtJIiZ3xLz/acAFbW6w zPkk95qsTomKk9csjGq8MFI7pJAGdQGZT5knT6zClhvRyE7Excv8vtz1BWD+/qRGAAzh 0JYnAKgyFdH3aRJHWVp1GcFTbOn7lYgZ8Oy+TWVReYvWmEO7U8jAbGmRgMaKkA8J10Zr fklmJM7HHZB6rDshipy3huAXN7cryRwiH5Rr6tyDKdfKMUUSK5hjVIB2J2EJApEC3auY 24WYEptJi+352qyCmVR101lp/ikcIZbfiKp8hIe7tANH9CTf2meicsJecJ54ScKwt6Pm Vu+g==
X-Gm-Message-State: AOJu0YzbgCBqR93N2nMMadR7LQMTVu3JxymehXnpXuUs+bOVPVv2GCQ/ mDOJm+CYmn+iOfiKngkE/cc=
X-Google-Smtp-Source: AGHT+IHo6Afz9P0Dj2kn366c/PXyH/u2tbMkMoWhAKYNx0+rfN+mcHe0sbgxWExJmdQevJ9jyTdQ0A==
X-Received: by 2002:a05:622a:11c4:b0:429:8bdc:6433 with SMTP id n4-20020a05622a11c400b004298bdc6433mr3752889qtk.56.1705175176035; Sat, 13 Jan 2024 11:46:16 -0800 (PST)
Received: from smtpclient.apple (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id 20-20020a250b14000000b00dbf335494e2sm2262421ybl.34.2024.01.13.11.46.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 Jan 2024 11:46:15 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <FCE4EEAF-D7BC-49F5-94AA-80D6D9E286B0@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FE0EB9CD-2A40-4719-A070-CA6C82A5FF45"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
Date: Sat, 13 Jan 2024 11:45:54 -0800
In-Reply-To: <CALypLp-2cuBo-4t=Fu6F2y0DqOjsy3_vqhdYfzyJiEraVZi0xQ@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, madinas@ietf.org
To: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
References: <170497095275.13340.12464306135239574020@ietfa.amsl.com> <E8162B32-363A-4B7C-86D6-5D7B2AD1F03E@gmail.com> <CALypLp-2cuBo-4t=Fu6F2y0DqOjsy3_vqhdYfzyJiEraVZi0xQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/jHF7ISiBZ9Gip1NcoVHC0lmnc4I>
Subject: Re: [Madinas] I-D Action: draft-ietf-madinas-mac-address-randomization-10.txt
X-BeenThere: madinas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: MAC Address Device Identification for Network and Application Services <madinas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/madinas>, <mailto:madinas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/madinas/>
List-Post: <mailto:madinas@ietf.org>
List-Help: <mailto:madinas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/madinas>, <mailto:madinas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jan 2024 19:46:21 -0000

Thanks
Bob



> On Jan 12, 2024, at 12:33 PM, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> wrote:
> 
> Hi Bob,
> 
> Sorry, I think I overlooked your previous comment. I'll update the draft next week.
> 
> Thanks!
> 
> Carlos
> 
> On Fri, Jan 12, 2024 at 1:38 AM Bob Hinden <bob.hinden@gmail.com <mailto:bob.hinden@gmail.com>> wrote:
>> I believe I made similar comments a while back.   Repeating myself.
>> 
>> 6. MAC randomization-related activities at the IETF
>> 
>> This title is ambiguous (and Section 4 and 5 the same problem).   “at the IETF” sounds like at an IETF meeting and “activities” isn’t clear.  Protocols are not “activities”   This should be something like:
>> 
>>           MAC randomization in IETF Protocol Standards
>> 
>> The text in this section starts with:
>> 
>> Several IP address assignment mechanisms such as the IPv6 stateless autoconfiguration techniques (SLAAC) [RFC4862] generate the Interface Identifier (IID) of the address from its MAC address (via EUI64), which then becomes visible to all IPv6 communication peers. This potentially allows for global tracking of a device at L3 from any point on the Internet. Besides, the prefix part of the address provides meaningful insights of the physical location of the device in general, which together with the MAC address-based IID, makes it easier to perform global device tracking.
>> 
>> This is wrong and out dated.   RFC 8064 "Recommendation on Stable IPv6 Interface Identifiers” published in 2017 formally updated IPv6 IID selection to prefer RFC 7217 IIDs and recommends against embedding stable link-layer address in IPv6 IIDS.
>> 
>> This section needs a serious rewrite.
>> 
>> Today, I also noted in third paragraph of this section a reference to [RFC4191].  The text is:
>> 
>> [RFC4191] identifies and describes the privacy issues associated with embedding MAC stable addressing information into the IPv6 addresses (as part of the IID) and describes some mechanisms to mitigate the associated problems.
>> 
>> RFC4191 is "Default Router Preferences and More-Specific Routes”.  This has nothing to do with embedding MAC stable addresss.
>> 
>> Bob
>> 
>> 
>>> On Jan 11, 2024, at 3:02 AM, internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> wrote:
>>> 
>>> Internet-Draft draft-ietf-madinas-mac-address-randomization-10.txt is now
>>> available. It is a work item of the MAC Address Device Identification for
>>> Network and Application Services (MADINAS) WG of the IETF.
>>> 
>>>   Title:   Randomized and Changing MAC Address state of affairs
>>>   Authors: Juan Carlos Zuniga
>>>            Carlos J. Bernardos
>>>            Amelia Andersdotter
>>>   Name:    draft-ietf-madinas-mac-address-randomization-10.txt
>>>   Pages:   18
>>>   Dates:   2024-01-11
>>> 
>>> Abstract:
>>> 
>>>   Internet privacy has become a major concern over the past few years.
>>>   Users are becoming more aware that their online activity leaves a
>>>   vast digital footprint, that communications are not always properly
>>>   secured, and that their location and actions can be easily tracked.
>>>   One of the main factors for the location tracking issue is the wide
>>>   use of long-lasting identifiers, such as MAC addresses.
>>> 
>>>   There have been several initiatives at the IETF and the IEEE 802
>>>   standards committees to overcome some of these privacy issues.  This
>>>   document provides an overview of these activities, with the intention
>>>   to inform the technical community about them, and help coordinate
>>>   between present and future standardization activities.
>>> 
>>> The IETF datatracker status page for this Internet-Draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-madinas-mac-address-randomization/
>>> 
>>> There is also an HTMLized version available at:
>>> https://datatracker.ietf.org/doc/html/draft-ietf-madinas-mac-address-randomization-10
>>> 
>>> A diff from the previous version is available at:
>>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-madinas-mac-address-randomization-10
>>> 
>>> Internet-Drafts are also available by rsync at:
>>> rsync.ietf.org::internet-drafts
>>> 
>>> 
>>> -- 
>>> Madinas mailing list
>>> Madinas@ietf.org <mailto:Madinas@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/madinas
>> 
>> -- 
>> Madinas mailing list
>> Madinas@ietf.org <mailto:Madinas@ietf.org>
>> https://www.ietf.org/mailman/listinfo/madinas