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

Bob Hinden <bob.hinden@gmail.com> Fri, 12 January 2024 17:35 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 117A2C14F68C for <madinas@ietfa.amsl.com>; Fri, 12 Jan 2024 09:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 Qm5aGEYl4H5g for <madinas@ietfa.amsl.com>; Fri, 12 Jan 2024 09:35:37 -0800 (PST)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (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 0B3A3C14F616 for <madinas@ietf.org>; Fri, 12 Jan 2024 09:35:36 -0800 (PST)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-5f68af028afso61186587b3.2 for <madinas@ietf.org>; Fri, 12 Jan 2024 09:35:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705080936; x=1705685736; 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=MC9Gnx7auPHCg00tRfxhbq2tlNr1pSDuR2+zB0ZTuVM=; b=hzvsU8tM9Jn2Fsk8TBsm59lpSKer9CL4kO0b4cW4seni6AKvXKL6TmTFgrAB9uwRMf Rrt0kVIGXAFHL0cC0JnHZMH7AGmrdoAP7sApU0LT8hWXcaGOl3GHv30qUOoLwmFtnoiY 6b1j4+LGKKkZzUuR0SbsXu4A49z/qdkUAxJOBKLrUQUS/iCh1NZxjRT6/d4WVDnJbIBx S9owKDOJ1B/fRkFLOeePOTh2rKTz+uHH83KJ/sDuTqZmjCR6aBf8si7vf0Lt6dsPO73h 8GQ5y76OBJkBXGFnn8Nf9QfuDEBfpcMsY/+Sw/c3yI6WxoPo1iboUMKyi5bYad8L15y9 gDKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705080936; x=1705685736; 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=MC9Gnx7auPHCg00tRfxhbq2tlNr1pSDuR2+zB0ZTuVM=; b=hVtMUfDupcqYRceHbw60PFRTe8tNG/BTHkQzYIT+7astlWzDsq/sV+FOjBZraM0vhn tq4gnH5+bAICnXWioLwsWaLLe7alEzKVOrgppcJkI8kwMsFIBTpRpBIEY9Vy0MFuOZVJ ow6EwiTqnCJvQfs/gFCpF1L/R7cNvIIa5IOZ/WDU/gGdpEY67IVU1bh8jz7aYztrqUjO aMVaJA+FBa4XbsFdPJccj7CwAhseMHsBiFWEP7pNhzReqP624tqh2igotp3xAXWrQWwS SClhlrLAyHqFZMUUy/jfSi0+hBu9e1kmfsnDog1JIW5XtNvNJdzAVeYWy8fx9EBnNZ0X cZCA==
X-Gm-Message-State: AOJu0YwNgx4FizXbz7N/7IfJB5SYBtTy2Gh2bnalbwvFTgfPKbivT6/l Fb7KXrdniETwEd228d37W3k=
X-Google-Smtp-Source: AGHT+IGQEJaRCafeCyM8zGqAF1MNCgSoZ8dShLFRbZSBSFTk6CaEE/kyxBvxhjetTRCmG+V25EExVg==
X-Received: by 2002:a0d:d84f:0:b0:5fb:f7c7:a77a with SMTP id a76-20020a0dd84f000000b005fbf7c7a77amr828872ywe.65.1705080935461; Fri, 12 Jan 2024 09:35:35 -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 u8-20020a818408000000b005efed2bb616sm1488745ywf.23.2024.01.12.09.35.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Jan 2024 09:35:35 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <4B12E8F1-B319-4523-BAB2-324681F99C5C@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FCCDC64F-7F27-431E-837B-5C3A1B481B0C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
Date: Fri, 12 Jan 2024 09:35:14 -0800
In-Reply-To: <CAC8QAcec5oU=+xMzw4GFn7gyypLsWy4Eu2ybVE3pg3eGp_5GSg@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, madinas@ietf.org
To: sarikaya@ieee.org
References: <170497095275.13340.12464306135239574020@ietfa.amsl.com> <E8162B32-363A-4B7C-86D6-5D7B2AD1F03E@gmail.com> <CAC8QAcec5oU=+xMzw4GFn7gyypLsWy4Eu2ybVE3pg3eGp_5GSg@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/tMoFdZ6achvJoonnuhJp6jgq-Mc>
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: Fri, 12 Jan 2024 17:35:39 -0000

Behcet,

> On Jan 12, 2024, at 9:31 AM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
> 
> Hi Bob,
> 
> 
> On Thu, Jan 11, 2024 at 6:39 PM 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.
>> 
> 
> 
> It seems like RFC 4191 was a typo, it should have been 
> RFC 4941 Privacy Extensions for Stateless Address Autoconfiguration in IPv6 

:-)

Also good to fix the other items I pointed out.

Bob


> 
> Regards,
> Behcet 
>> 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