Hi Eric,
Discussing with our AD Mahesh, another IESG ballot is not on the table.
This one week WG Last Call (and Mahesh might run another one week IETF
Last Call) is for the community to have a chance the review the
extensive changes from the IESG review.
Regards, Benoit
On 8/28/2024 3:21 PM, Eric Vyncke (evyncke) wrote:
Bonjour Benoît, dear chairs/authors,
I have reviewed the diffs:
- with my IESG/AD hat, the diffs are extensive but do not really
change the core of the document, i.e., another IESG ballot does not
seem required even for the vast amount of changes
- thanks for addressing many of the COMMENTs in my own ballot,
including the mDNS new section
- as individual and interested engineer, I think the I-D is better.
As already written, I still regret that this document restricts itself
to MUD while it could be used for any layer-3 ACL (e.g., plain
firewalls) and many shipping products are doing so for many years.
Regards
-éric
*From: *Benoit Claise <benoit.claise=40huawei....@dmarc.ietf.org>
*Date: *Monday, 26 August 2024 at 19:23
*To: *opsawg <opsawg@ietf.org>
*Cc: *The IESG <i...@ietf.org>
*Subject: *[OPSAWG]One week WG Last Call:
draft-ietf-opsawg-mud-iot-dns-considerations-17.txt
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
<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-dra...@ietf.org
*Reply-To: *
opsawg@ietf.org
*To: *
i-d-annou...@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-le...@ietf.org
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org
