[OPSAWG]BCP 241, RFC 9726 on Operational Considerations for Use of DNS in Internet of Things (IoT) Devices
rfc-editor@rfc-editor.org Mon, 31 March 2025 19:37 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0E948155FEEE; Mon, 31 Mar 2025 12:37:24 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 96AC61F58E9; Mon, 31 Mar 2025 12:37:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250331193723.96AC61F58E9@rfcpa.rfc-editor.org>
Date: Mon, 31 Mar 2025 12:37:23 -0700
Message-ID-Hash: CHBL7W7X4WZ5VYDTXTJARRPC5LCSWFZP
X-Message-ID-Hash: CHBL7W7X4WZ5VYDTXTJARRPC5LCSWFZP
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
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: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OPSAWG]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/jBTEKxQeOPt27hSre6nz5bnazWw>
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>
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]BCP 241, RFC 9726 on Operational Consider… rfc-editor
- [OPSAWG]Re: BCP 241, RFC 9726 on Operational Cons… Benoit Claise
- [OPSAWG]Re: BCP 241, RFC 9726 on Operational Cons… Michael Richardson