Re: [OPSAWG] 🔔 WG Adoption Call on draft-richardson-opsawg-mud-iot-dns-considerations-03

Qin Wu <bill.wu@huawei.com> Sat, 16 January 2021 11:57 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96DDD3A1712 for <opsawg@ietfa.amsl.com>; Sat, 16 Jan 2021 03:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 zsKQ6ZpVgwoy for <opsawg@ietfa.amsl.com>; Sat, 16 Jan 2021 03:57:02 -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 75FD43A1710 for <opsawg@ietf.org>; Sat, 16 Jan 2021 03:57:02 -0800 (PST)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DHxJ93v07z67ZMt; Sat, 16 Jan 2021 19:52:57 +0800 (CST)
Received: from fraeml701-chm.china.huawei.com (10.206.15.50) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Sat, 16 Jan 2021 12:56:57 +0100
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.2106.2 via Frontend Transport; Sat, 16 Jan 2021 12:56:57 +0100
Received: from DGGEML531-MBS.china.huawei.com ([169.254.5.18]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0509.000; Sat, 16 Jan 2021 19:56:53 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
CC: opsawg <opsawg@ietf.org>
Thread-Topic: =?utf-8?B?W09QU0FXR10gIPCflJQgV0cgQWRvcHRpb24gQ2FsbCBvbiBkcmFmdC1yaWNo?= =?utf-8?Q?ardson-opsawg-mud-iot-dns-considerations-03?=
Thread-Index: Adbr/b2ZEMdVqxerTySpFYHRNybpRw==
Date: Sat, 16 Jan 2021 11:56:53 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADCDB60A@dggeml531-mbs.china.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.101.103]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/VY1_J1EroBRWEYybV_HqEFA6NvQ>
Subject: Re: [OPSAWG] =?utf-8?q?=F0=9F=94=94_WG_Adoption_Call_on_draft-richar?= =?utf-8?q?dson-opsawg-mud-iot-dns-considerations-03?=
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jan 2021 11:57:05 -0000

Support adoption of this document, agree with Eliot.
A few quick comments:
1. I want to make sure these recommendation and guidelines of using DNS are not only applicable to home network but also enterprise network as well.
2. Section 4.2 lack examples of non-deterministic CDN content.
3. Section 4.2 describe control protocol to connect to a known HTTP
  end point, can you provide an example of such control protocol, HTTP protocol, SUIT protocol, or any firmware update protocol.

-Qin
-----邮件原件-----
发件人: OPSAWG [mailto:opsawg-bounces@ietf.org] 代表 Eliot Lear
发送时间: 2021年1月5日 4:36
收件人: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
抄送: opsawg <opsawg@ietf.org>
主题: Re: [OPSAWG] 🔔 WG Adoption Call on draft-richardson-opsawg-mud-iot-dns-considerations-03

Hi!

I’ve read this document and support its adoption.  Michael is doing a really good job here of making use of BCP in the truest sense of the word.  I suspect this would be a good document to involve the dnsops people in as well.

Eliot


> On 4 Jan 2021, at 19:03, Henk Birkholz <henk.birkholz@sit.fraunhofer.de> wrote:
> 
> Dear OPSAWG members,
> 
> this starts a call for Working Group Adoption on https://tools.ietf.org/html/draft-richardson-opsawg-mud-iot-dns-considerations-03 ending on Monday, January 25.
> 
> As a reminder, this I-D describes potential issues and concerns regarding the use of DNS names and IP addressed with RFC8520 Manufacturer Usage Description (MUD) in support of device access.
> 
> Please reply with your support and especially any substantive comments you may have.
> 
> 
> For the OPSAWG co-chairs,
> 
> Henk
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg