[OPSAWG]Re: One week WG Last Call: draft-ietf-opsawg-mud-iot-dns-considerations-17.txt

Benoit Claise <benoit.claise@huawei.com> Tue, 10 September 2024 22:02 UTC

Return-Path: <benoit.claise@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 EB3B0C1840F8; Tue, 10 Sep 2024 15:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.262
X-Spam-Level:
X-Spam-Status: No, score=-7.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.355, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sW3e2rDye3p; Tue, 10 Sep 2024 15:02:05 -0700 (PDT)
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 DB6FBC1840E4; Tue, 10 Sep 2024 15:02:04 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4X3HdZ10ccz6L72q; Wed, 11 Sep 2024 05:58:26 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id 53897140A70; Wed, 11 Sep 2024 06:02:02 +0800 (CST)
Received: from [10.206.138.58] (10.206.138.58) by frapeml500001.china.huawei.com (7.182.85.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Wed, 11 Sep 2024 00:02:00 +0200
Content-Type: multipart/alternative; boundary="------------sc7Lwxlx3Ura2yKjnX0cFDse"
Message-ID: <a4e2c185-ebc5-d0d1-002b-8bff456dee62@huawei.com>
Date: Tue, 10 Sep 2024 23:01:55 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>, opsawg <opsawg@ietf.org>
References: <172374263526.1272457.13152153254554808178@dt-datatracker-6df4c9dcf5-t2x2k> <f1cac398-533a-4d41-9fcc-3fcc4481a011@huawei.com>
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <f1cac398-533a-4d41-9fcc-3fcc4481a011@huawei.com>
X-Originating-IP: [10.206.138.58]
X-ClientProxiedBy: dggems703-chm.china.huawei.com (10.3.19.180) To frapeml500001.china.huawei.com (7.182.85.94)
Message-ID-Hash: S5WMPXBYUJ3CXXKZNF364GSEI2OFYMZY
X-Message-ID-Hash: S5WMPXBYUJ3CXXKZNF364GSEI2OFYMZY
X-MailFrom: benoit.claise@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-opsawg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [OPSAWG]Re: One week WG Last Call: draft-ietf-opsawg-mud-iot-dns-considerations-17.txt
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/45LRInVQ7cfvspnKFkJYFEscxq4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Owner: <mailto:opsawg-owner@ietf.org>
List-Post: <mailto:opsawg@ietf.org>
List-Subscribe: <mailto:opsawg-join@ietf.org>
List-Unsubscribe: <mailto:opsawg-leave@ietf.org>

Dear all,

This ends the WG Last Call.

Only one comment, made by Eric Vyncke, but it was a verbal comment 
during the IESG telechat.
Quoting Eric: "feel free to ignore especially now that it is really too 
late IMHO."

What's the next step for this draft?
Quoting our AD Mahesh: There is however, one lingering comment from 
Murray that needs to be addressed in the document (see this thread 
[OPSAWG]Re: process forward for draft-ietf-opsawg… 
<https://mailarchive.ietf.org/arch/msg/opsawg/IM0X4kfj8biqYrOTCqxVQrl0tD8/>)

So, once addressed, Mahesh will send this draft to IETF Last Call

Regards, Benoit



On 8/26/2024 6:22 PM, Benoit Claise wrote:
> Dear all,
>
> This email starts a one week WG Last Call on 
> draft-ietf-opsawg-mud-iot-dns-considerations-17, before publication.
> The last call will finish on Sept 2nd.
>
> Some history on this draft:
> - v12 was sent to the IESG, sometime in April
> - based on the IESG feedback, multiple draft revisions were posted
> - v17 was posted on Aug 15th, addressing/resolving all the IESG DISCUSS'es
>
> The changes that were suggested and accepted by the authors resulted 
> in large parts of the document to be rewritten.
> As suggested by our AD, since those changes are extensive, the new 
> revision deserves a final check before it's sent for publication to 
> the RFC Editor.
>
> Here are the diff between version 12 and version 17.
> https://author-tools.ietf.org/iddiff?url1=draft-ietf-opsawg-mud-iot-dns-considerations-12&url2=draft-ietf-opsawg-mud-iot-dns-considerations-17&difftype=--html
>
> Regards, Joe & Benoit
>
>
> -------- Forwarded Message --------
> Subject: 	[OPSAWG]I-D Action: 
> draft-ietf-opsawg-mud-iot-dns-considerations-17.txt
> Date: 	Thu, 15 Aug 2024 10:23:55 -0700
> From: 	internet-drafts@ietf.org
> Reply-To: 	opsawg@ietf.org
> To: 	i-d-announce@ietf.org
> CC: 	opsawg@ietf.org
>
>
>
> Internet-Draft draft-ietf-opsawg-mud-iot-dns-considerations-17.txt is now
> available. It is a work item of the Operations and Management Area Working
> Group (OPSAWG) WG of the IETF.
>
> Title: Operational Considerations for Use of DNS in IoT Devices
> Authors: Michael Richardson
> Wei Pan
> Name: draft-ietf-opsawg-mud-iot-dns-considerations-17.txt
> Pages: 21
> Dates: 2024-08-15
>
> Abstract:
>
> This document details considerations about how Internet of Things
> (IoT) devices use IP addresses and DNS names. These concerns become
> acute as network operators begin deploying RFC 8520 Manufacturer
> Usage Description (MUD) definitions to control device access.
>
> Also, this document makes recommendations on when and how to use DNS
> names in MUD files.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud-iot-dns-considerations/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-opsawg-mud-iot-dns-considerations-17.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-mud-iot-dns-considerations-17
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> OPSAWG mailing list -- opsawg@ietf.org
> To unsubscribe send an email to opsawg-leave@ietf.org
>
> _______________________________________________
> OPSAWG mailing list --opsawg@ietf.org
> To unsubscribe send an email toopsawg-leave@ietf.org