<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-suit-mud" target="https://datatracker.ietf.org/doc/html/draft-ietf-suit-mud-07">
   <front>
      <title>Strong Assertions of IoT Network Access Requirements</title>
      <author initials="B." surname="Moran" fullname="Brendan Moran">
         <organization>Arm Limited</organization>
      </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         </author>
      <date month="December" day="20" year="2023" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-suit-mud-07" />
   
</reference>
