Re: [Int-area] Evaluate impact of MAC address randomization to IP applications

Stewart Bryant <stewart.bryant@gmail.com> Wed, 23 September 2020 15:03 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916D83A11A6 for <int-area@ietfa.amsl.com>; Wed, 23 Sep 2020 08:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NagYnVOsviMH for <int-area@ietfa.amsl.com>; Wed, 23 Sep 2020 08:03:25 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 74C6A3A11A5 for <int-area@ietf.org>; Wed, 23 Sep 2020 08:03:25 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id a9so409868wmm.2 for <int-area@ietf.org>; Wed, 23 Sep 2020 08:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=wl7OtVkS6HaoCJl4QyDC6VRw29EcHp7XFBVijtDKMe4=; b=mTUspyii81qgrNHyNXa0BxKo62cGKYjgT0vDokKKr/vN82SdBBFbXq/3oZsUpkY746 5OiTcn/V3QjYvLICsTQL3kaCJ55ZLkPMFCp1pARthCdmqyWSVhuKmtz5TMqenKErPzzm //wRoX5c/QT1yU881CdXULZ49vMyc2Xuuy6eaCOgGOiuuXNbSx646yRFy+zkOFkhqEna 5i0gyHiPU1ne5/R0quIFrVKJnHO6viZlugwcWK4MkgghWJGR/nRPn6h/qfzduhqGwcvt wrjV6oMexYi2YV5b4Zhg4a1yKVFgbHuLu1RMXWLbtTeJyB/YnFKakP7eZlvh+rMaFMXu VZWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=wl7OtVkS6HaoCJl4QyDC6VRw29EcHp7XFBVijtDKMe4=; b=QSMa3HeY8QiggsLgKuSnIK2dXbBDn4WzzpL3UDPRbYJFL4fMKA3LIdzcZWRir/fe4J VnDqUQpb2wxdFua+lc4PCUCur8gNm2iwuE85slX4D+utp/pUhXW5cxj55ABndeUUbPYC dYmf0mje1cGB3N1u/ReA1li6Y/BAOIqA6AB4pSZSisB7PyK4eeS2rpOVXwiu5ahOdEMR k8zTdJa9DqugWFa2Cn6g4+D7sextvU34kkdq1A1cwlwQVdqknJCBnL3Mgx/9h72rel5M ffS1rvfNhUAzoKLt4fezF4m7HR/UK8vCkqZr19U3ONOvI5ksUfMAtGsTuBoONnDosZm9 38Jg==
X-Gm-Message-State: AOAM531DRYA40OnoUZFqrVCqHVDmeEBuAwJ0lLOH7OahuCJW7aZqycDC FvpDQ5UUSjHmd6CbjPZ2/3M=
X-Google-Smtp-Source: ABdhPJycYpO4gvUlCX9xpSoSC1Bfi3UM0X4FYqhqVlqXJ0svmaagIOTYs+S5RGtkmAOzNC4xRTrb9A==
X-Received: by 2002:a1c:f608:: with SMTP id w8mr7329179wmc.161.1600873403737; Wed, 23 Sep 2020 08:03:23 -0700 (PDT)
Received: from [192.168.178.24] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id p1sm10486398wma.0.2020.09.23.08.03.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Sep 2020 08:03:22 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <1F58FC0A-F952-4417-9510-7434D2403814@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DAB21325-1F85-4149-AA19-0CE751D47218"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Wed, 23 Sep 2020 16:02:51 +0100
In-Reply-To: <4749067E-A5E1-4D22-AF80-744FA4EB8679@cisco.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Andy Smith <ajsphila@gmail.com>, "int-area@ietf.org" <int-area@ietf.org>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
References: <A8BB4316-BCAE-4E3C-AC3B-441D2ECB0338@comcast.com> <71B286E5-EAF7-4B66-A637-8EFE061D2451@gmail.com> <0F483D3B-C82B-4D00-8F0E-252CE027AE1C@gmail.com> <4749067E-A5E1-4D22-AF80-744FA4EB8679@cisco.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/IcU-WOw8OOJOM1N_lSIRZ6iqQso>
Subject: Re: [Int-area] Evaluate impact of MAC address randomization to IP applications
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2020 15:03:28 -0000

Yes, but DEC decided that was a bad idea and stopped doing it in phase V.

Phase iV stared pre-bridging where the extend of the LAN was only the directly connected devices.

These days LANs are huge and I am simply asking about where the IEEE who are the design authority for Ethernet approve of MAC address randomisation?

Stewart


> On 23 Sep 2020, at 15:02, Eric Vyncke (evyncke) <evyncke@cisco.com> wrote:
> 
> In another century, DECnet phase 4 was also changing the MAC address (and if not mistaken IBM SNA also) but flipping the universal/local bit of the MAC address
>  
> -éric
>  
> From: Int-area <int-area-bounces@ietf.org <mailto:int-area-bounces@ietf.org>> on behalf of Stewart Bryant <stewart.bryant@gmail.com <mailto:stewart.bryant@gmail.com>>
> Date: Wednesday, 23 September 2020 at 12:38
> To: Andy Smith <ajsphila@gmail.com <mailto:ajsphila@gmail.com>>
> Cc: "int-area@ietf.org <mailto:int-area@ietf.org>" <int-area@ietf.org <mailto:int-area@ietf.org>>
> Subject: Re: [Int-area] Evaluate impact of MAC address randomization to IP applications
>  
> So I am curious, and probably out of touch.
>  
> MAC addresses are supposed to be unique hardware device addresses  that ultimately come from a registry administered by IEEE and are supposed to be allocated exactly once to one hardware entity.
>  
> Is MAC address randomisation something that IEEE approve of, in which case how does the registry work, or are we at risk of working on a problem that results in an interSDO dispute?
>  
> - Stewart
>  
>  
> 
> 
>> On 22 Sep 2020, at 21:22, Andy Smith <ajsphila@gmail.com <mailto:ajsphila@gmail.com>> wrote:
>>  
>> Yiu-
>>  
>> I’d like to help here.   Is the problem that residential devices can’t be reliably tracked for purposes of policy enforcement?     Or is it an IP address depletion issue?  
>>  
>> I noticed iOS 14 does allow for disabling of random MAC addresses.  
>>  
>> Andy
>>  
>>  
>> Sent with emacs for iOS
>> 
>> 
>>> On Sep 22, 2020, at 15:50, Lee, Yiu <Yiu_Lee@comcast.com <mailto:Yiu_Lee@comcast.com>> wrote:
>>> 
>>> Hi team,
>>>  
>>> We proposed a BoF. The agenda is in https://github.com/jlivingood/IETF109BoF/blob/master/109-Agenda.md <https://github.com/jlivingood/IETF109BoF/blob/master/109-Agenda.md> and the proposal is in https://github.com/jlivingood/IETF109BoF/blob/master/BoF-Proposal-20200918.md <https://github.com/jlivingood/IETF109BoF/blob/master/BoF-Proposal-20200918.md>. You can also find the draft here https://tools.ietf.org/html/draft-lee-randomized-macaddr-ps-01 <https://tools.ietf.org/html/draft-lee-randomized-macaddr-ps-01>.
>>>  
>>> At this stage, we are looking for inputs for more use cases and interests of working together in this domain. Please post your comments in the mailing list.
>>>  
>>> Thanks
>>>  
>>>  
>>> _______________________________________________
>>> Int-area mailing list
>>> Int-area@ietf.org <mailto:Int-area@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/int-area <https://www.ietf.org/mailman/listinfo/int-area>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org <mailto:Int-area@ietf.org>
>> https://www.ietf.org/mailman/listinfo/int-area <https://www.ietf.org/mailman/listinfo/int-area>