Re: [Madinas] Call for adoption: draft-henry-madinas-framework

Qin Wu <bill.wu@huawei.com> Fri, 26 November 2021 08:47 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 269663A0B81 for <madinas@ietfa.amsl.com>; Fri, 26 Nov 2021 00:47:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 pC0axGK5RqHV for <madinas@ietfa.amsl.com>; Fri, 26 Nov 2021 00:47: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 DB0433A0C2D for <madinas@ietf.org>; Fri, 26 Nov 2021 00:47:43 -0800 (PST)
Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4J0pJn0R6jz67rsP for <madinas@ietf.org>; Fri, 26 Nov 2021 16:47:05 +0800 (CST)
Received: from dggeml702-chm.china.huawei.com (10.3.17.135) by fraeml714-chm.china.huawei.com (10.206.15.33) 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 09:47:39 +0100
Received: from dggeml753-chm.china.huawei.com (10.1.199.152) by dggeml702-chm.china.huawei.com (10.3.17.135) 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 16:47: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 16:47:38 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>, "madinas@ietf.org" <madinas@ietf.org>
CC: Juan Carlos Zuniga <j.c.zuniga@ieee.org>, CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Thread-Topic: Call for adoption: draft-henry-madinas-framework
Thread-Index: AdfioHSNUgbs34jgT8CP97w7dORpzw==
Date: Fri, 26 Nov 2021 08:47:37 +0000
Message-ID: <4d563d35a1084661944621ffe5c05b1b@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: multipart/alternative; boundary="_000_4d563d35a1084661944621ffe5c05b1bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/T5lI1leDzNbl7y6vZnOR-Hb7bIg>
Subject: Re: [Madinas] Call for adoption: draft-henry-madinas-framework
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 08:47:51 -0000

Hi, WG:
I have read the latest version and support adoption of draft-henry-madinas-framework as informational RFC,
I am hoping this draft could also document some IoT related use cases, whether it is residential use case or campus, enterprise use cases.

I envision there are some good use cases in the residential setting, e.g, Only MAC address was needed to open some Smart Locks (https://cybersecuritynext.org/only-mac-address-was-needed-to-open-some-smart-locks-report/)

I am wondering how IoT device (e.g., smart lock) in the residential setting can be affected by device’s mac address sniff? Is RCM scheme better solution for them? How smart lock vendors implement RCM? Given the bad user experience to get on the home network with RCM scheme on, whether they will move away from MAC and IP address based access control and moving towards identity based access control.



When we say “To reduce the risks of correlation between a device activity and its owner, multiple vendors have started to implement Randomized and

Changing MAC addresses (RCM). ”, I want to make sure it is Mobile device vendors or OS vendors not IoT device vendor who start implement RCM, correct me, if I am wrong.



Regarding “such address change may affect the user experience and the efficiency of legitimate network operations.  ” I agree such changes will affect a lot the user experience. It is good to see privacy for end user has been improved, but it is at the cost of user experience deteriorating. I am wondering whether many of users will go through this painful onboarding process rather than abandon logging on some kind of guest network.



Last, I want to make sure there is no overlapping with use cases documented in WBA since we now position this document as use case document.

Thanks for taking my comments into consideration.



-Qin
发件人: Madinas [mailto:madinas-bounces@ietf.org] 代表 Juan Carlos Zuniga
发送时间: 2021年11月10日 21:56
收件人: madinas@ietf.org
抄送: Juan Carlos Zuniga <j.c.zuniga@ieee.org>; CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
主题: [Madinas] Call for adoption: draft-henry-madinas-framework

Dear all,

Confirming what was said at the meeting, we are starting a Call for Adoption of https://datatracker.ietf.org/doc/html/draft-henry-madinas-framework-03

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

Best,

Juan-Carlos & Carlos
MADINAS chairs


Your privacy is important to us. Please see our Privacy Notice<https://www.sigfox.com/en/privacy-and-cookies-policy> for further details. The information contained in this Message is confidential. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this Message in error, please delete it and all copies from your system and notify the sender immediately by return message. Any use of information contained in this Message not in accordance with its intended purpose, any dissemination or disclosure (either whole or partial), is prohibited unless expressly authorized. Email communication cannot be guaranteed to be timely secure, error or virus-free. The sender cannot be held responsible for any alteration, errors or omissions, which arise as a result.

..................................................................................................................

La protection de vos données personnelles est primordiale pour notre établissement. Merci de consulter notre notice sur la protection des données personnelles <https://www.sigfox.com/en/privacy-and-cookies-policy> pour plus d’informations. Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires. Les informations qui y figurent sont confidentielles. Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Veuillez également en avertir immédiatement l'expéditeur par retour du Message. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, soient sécurisées ou dénuées de toute erreur ou virus. L'expéditeur ne peut être tenu responsable des modifications, erreurs ou omissions qui pourraient en résulter.