Strong Assertions of IoT Network Access Requirements
draft-ietf-suit-mud-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-suit-mud@ietf.org, housley@vigilsec.com, rdd@cert.org, rfc-editor@rfc-editor.org, suit-chairs@ietf.org, suit@ietf.org
Subject: Protocol Action: 'Strong Assertions of IoT Network Access Requirements' to Proposed Standard (draft-ietf-suit-mud-09.txt)

The IESG has approved the following document:
- 'Strong Assertions of IoT Network Access Requirements'
  (draft-ietf-suit-mud-09.txt) as Proposed Standard

This document is the product of the Software Updates for Internet of Things
Working Group.

The IESG contact persons are Paul Wouters, Deb Cooley and Roman Danyliw.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-suit-mud/

Ballot Text

Technical Summary

   The Manufacturer Usage Description (MUD) specification describes the
   access and network functionality required for a device to properly
   function.  The MUD description has to reflect the software running on
   the device and its configuration.  Because of this, the most
   appropriate entity for describing device network access requirements
   is the same as the entity developing the software and its
   configuration.

   A network presented with a MUD file by a device allows detection of
   misbehavior by the device software and configuration of access
   control.

   This document defines a way to link a SUIT manifest to a MUD file
   offering a stronger binding between the two.

Working Group Summary

  The document shepherd did a thorough review of the document during
  WG Last Call.  All issues that were raised during WG Last Call have
  been resolved.  However, there were few comments on the document even
  though there was strong consensus in the WG that inclusion of the MUD 
  file in the SUIT Manifest was a good idea.

  The document incorporated clarifications in the notional workflow during AD Review and IETF LC OPSDIR Review.

Document Quality

Nothing significant to report.

Personnel

   The Document Shepherd for this document is Russ Housley. The Responsible
   Area Director is Roman Danyliw.

RFC Editor Note