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

[Bob Hinden <[e-mail]>]

> On Jan 12, 2024, at 10:10 AM, David Farmer <[e-mail]> wrote:
> 
> 
> 
> On Fri, Jan 12, 2024 at 11:31 AM Behcet Sarikaya <[e-mail] <mailto:[e-mail]>> wrote:
>> Hi Bob,
>> 
>> 
>> On Thu, Jan 11, 2024 at 6:39 PM Bob Hinden <[e-mail] <mailto:[e-mail]>> 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 
> 
> Yes, that seems likely. However, RFC 4941 has been obsoleted by RFC 8981, Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6

+1

Bob


>  
> Thanks
> --
> ===============================================
> David Farmer               Email:[e-mail] <mailto:[e-mail]>
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota   
> 2218 University Ave SE        Phone: [phone]
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================