IETF Logo Mail Archive

[OPSAWG]Re: BCP 241, RFC 9726 on Operational Considerations for Use of DNS in Internet of Things (IoT) Devices

Benoit Claise <benoit.claise@huawei.com> Tue, 01 April 2025 06:31 UTC

Return-Path: <benoit.claise@huawei.com>
X-Original-To: opsawg@mail2.ietf.org
Delivered-To: opsawg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3A705159A669; Mon, 31 Mar 2025 23:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zow8IYcZCgkr; Mon, 31 Mar 2025 23:31:56 -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 mail2.ietf.org (Postfix) with ESMTPS id 42301159A638; Mon, 31 Mar 2025 23:31:56 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4ZRdNl2c3Tz6K9GH; Tue, 1 Apr 2025 14:28:23 +0800 (CST)
Received: from frapeml500001.china.huawei.com (unknown [7.182.85.94]) by mail.maildlp.com (Postfix) with ESMTPS id A50BA1406AF; Tue, 1 Apr 2025 14:31:54 +0800 (CST)
Received: from [10.126.170.142] (10.126.170.142) 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; Tue, 1 Apr 2025 08:31:50 +0200
Message-ID: <d5192258-fac8-4789-82c0-5eb2d662e86f@huawei.com>
Date: Tue, 01 Apr 2025 08:31:45 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: rfc-editor@rfc-editor.org, ietf-announce@ietf.org, rfc-dist@rfc-editor.org
References: <20250331193723.96AC61F58E9@rfcpa.rfc-editor.org>
Content-Language: en-US
From: Benoit Claise <benoit.claise@huawei.com>
In-Reply-To: <20250331193723.96AC61F58E9@rfcpa.rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.126.170.142]
X-ClientProxiedBy: dggems703-chm.china.huawei.com (10.3.19.180) To frapeml500001.china.huawei.com (7.182.85.94)
Message-ID-Hash: X6DIOSE5NXBWKKXQJ4552UUEH6C2CLAI
X-Message-ID-Hash: X6DIOSE5NXBWKKXQJ4552UUEH6C2CLAI
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: drafts-update-ref@iana.org, opsawg@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OPSAWG]Re: BCP 241, RFC 9726 on Operational Considerations for Use of DNS in Internet of Things (IoT) Devices
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/MYZ06qKbX2xzUeLbXiwccUiRxWE>
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>

Congrats Michael, Wei, and Tirumaleswar
And thanks to everybody who has been helping with this RFC

Regards, Joe and Benoit


On 3/31/2025 9:37 PM, rfc-editor@rfc-editor.org wrote:
> A new Request for Comments is now available in online RFC libraries.
>
>          BCP 241
>          RFC 9726
>
>          Title:      Operational Considerations for Use of DNS
>                      in Internet of Things (IoT) Devices
>          Author:     M. Richardson,
>                      W. Pan
>          Status:     Best Current Practice
>          Stream:     IETF
>          Date:       March 2025
>          Mailbox:    mcr+ietf@sandelman.ca,
>                      william.panwei@huawei.com
>          Pages:      17
>          See Also:   BCP 241
>
>          I-D Tag:    draft-ietf-opsawg-mud-iot-dns-considerations-19.txt
>
>          URL:        https://www.rfc-editor.org/info/rfc9726
>
>          DOI:        10.17487/RFC9726
>
> 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 Manufacturer Usage
> Descriptions (MUD), as specified in RFC 8520, to control device
> access.
>
> Also, this document makes recommendations on when and how to use DNS
> names in MUD files.
>
> This document is a product of the Operations and Management Area Working Group Working Group of the IETF.
>
>
> BCP: This document specifies an Internet Best Current Practices for the
> Internet Community, and requests discussion and suggestions for
> improvements. Distribution of this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>    https://www.ietf.org/mailman/listinfo/ietf-announce
>    https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
>
> _______________________________________________
> OPSAWG mailing list -- opsawg@ietf.org
> To unsubscribe send an email to opsawg-leave@ietf.org

v2.45.0 | Report a Bug | By Email | System Status