Re: [Madinas] Call for adoption: draft-zuniga-madinas-mac-address-randomization-01

Qin Wu <bill.wu@huawei.com> Fri, 26 November 2021 07:20 UTC

Return-Path: <bill.wu@huawei.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 40DF73A0B53 for <madinas@ietfa.amsl.com>; Thu, 25 Nov 2021 23:20:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 jRvcWt-Qlyw1 for <madinas@ietfa.amsl.com>; Thu, 25 Nov 2021 23:20:44 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FFCA3A0B69 for <madinas@ietf.org>; Thu, 25 Nov 2021 23:20:44 -0800 (PST)
Received: from fraeml708-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4J0mNP3gjkz67sVs for <madinas@ietf.org>; Fri, 26 Nov 2021 15:20:05 +0800 (CST)
Received: from dggeml701-chm.china.huawei.com (10.3.17.134) by fraeml708-chm.china.huawei.com (10.206.15.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.20; Fri, 26 Nov 2021 08:20:40 +0100
Received: from dggeml753-chm.china.huawei.com (10.1.199.152) by dggeml701-chm.china.huawei.com (10.3.17.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.20; Fri, 26 Nov 2021 15:20:37 +0800
Received: from dggeml753-chm.china.huawei.com ([10.1.199.152]) by dggeml753-chm.china.huawei.com ([10.1.199.152]) with mapi id 15.01.2308.020; Fri, 26 Nov 2021 15:20:38 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Mathieu Cunche <mathieu.cunche@insa-lyon.fr>, "madinas@ietf.org" <madinas@ietf.org>
CC: Juan Zuniga <j.c.zuniga@ieee.org>, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Thread-Topic: [Madinas] Call for adoption: draft-zuniga-madinas-mac-address-randomization-01
Thread-Index: AdfilPH2oXxLuyV9S0CACOQMN9ck4A==
Date: Fri, 26 Nov 2021 07:20:38 +0000
Message-ID: <395e2484187b40a98828422da6a7ed43@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/KlDjcwb_JeIHxhgJE_JGJFm4If4>
Subject: Re: [Madinas] Call for adoption: draft-zuniga-madinas-mac-address-randomization-01
X-BeenThere: madinas@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Nov 2021 07:20:49 -0000

I Support adoption of draft-zuniga-madinas-mac-address-randomization-01 as informational RFC. I see this document as a good survey document which explore where mac address randomization come from and how it is evolved and developed in many SDOs and device implementation. Very useful documents to track the history and roadmap of this work.

I have a few comments and suggestions I would like authors to take into consideration:
1. MAC addresses can be categorized into universally administered address and locally administrative address, I want to make sure only locally administrative address will be seen as randomized address? Do we need to consider other factors such as lifetime of MAC address, e.g., how about locally administered address with long lifetime, how about universally administered address with short lifetime?
2. Given all relevant work ongoing in different organizations such as IETF, IEEE, WBA, when are we planning to get this work completed or continue update based progress or status update of each relevant work ongoing?
3. Maybe it is too early to ask this, beside documenting the various different behavior of OS which has implemented MAC address randomization, I am curious to know how they change the way network operator manage their network, how IT department deal with these challenges?

-Qin
-----邮件原件-----
发件人: Madinas [mailto:madinas-bounces@ietf.org] 代表 Mathieu Cunche
发送时间: 2021年11月11日 0:23
收件人: madinas@ietf.org
抄送: Juan Zuniga <j.c.zuniga@ieee.org>; CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
主题: [Madinas] Call for adoption: draft-zuniga-madinas-mac-address-randomization-01

Dear all,

I've been appointed to run the Call for Adoption of
draft-zuniga-madinas-mac-address-randomization-01

Confirming what was said at the meeting, we are starting a Call for Adoption of
https://datatracker.ietf.org/doc/html/draft-zuniga-madinas-mac-address-randomization-01

Please let us know if you support or oppose the adoption. Likewise, please let us know if you have any comments or suggestions.

The Call for Adoption will close 2 weeks after the end of the IETF meeting, on the 28th of November.

Regards,

Mathieu Cunche

--
Madinas mailing list
Madinas@ietf.org
https://www.ietf.org/mailman/listinfo/madinas