[Mud] my list of MUD related documents

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 17 December 2020 18:24 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: mud@ietfa.amsl.com
Delivered-To: mud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED9823A0E68; Thu, 17 Dec 2020 10:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OspuAUOec60a; Thu, 17 Dec 2020 10:24:04 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEEF03A1123; Thu, 17 Dec 2020 10:23:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D8A20389AC; Thu, 17 Dec 2020 13:26:15 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ytDGNo53Qibd; Thu, 17 Dec 2020 13:26:15 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6E64A389A8; Thu, 17 Dec 2020 13:26:15 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D1F7F11B4; Thu, 17 Dec 2020 13:23:29 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: mud@ietf.org, opsawg@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 17 Dec 2020 13:23:29 -0500
Message-ID: <27659.1608229409@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/0-sX8U6xQUoBlfoKpQKm-SxqQgQ>
Subject: [Mud] my list of MUD related documents
X-BeenThere: mud@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Manufacturer Ussage Descriptions <mud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mud>, <mailto:mud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mud/>
List-Post: <mailto:mud@ietf.org>
List-Help: <mailto:mud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mud>, <mailto:mud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2020 18:24:06 -0000

1) SBOM Extension for MUD
   draft-lear-opsawg-mud-sbom-00
Abstract
   Software bills of materials (SBOMs) are formal descriptions of what
   pieces of software are included in a product.  This memo specifies a
   means for manufacturers to state how SBOMs may be retrieved through
   an extension to manufacturer usage descriptions (MUD).

2) Authorized update to MUD URLs
   draft-richardson-opsawg-mud-acceptable-urls-03
Abstract
   This document provides a way for an RFC8520 Manufacturer Usage
   Description (MUD) definitions to declare what are acceptable
   replacement MUD URLs for a device.

3) Operational Considerations for use of DNS in IoT devices
   draft-richardson-opsawg-mud-iot-dns-considerations-03
Abstract
   This document details concerns about how Internet of Things devices
   use IP addresses and DNS names.  The issue becomes acute as network
   operators begin deploying RFC8520 Manufacturer Usage Description
   (MUD) definitions to control device access.

   This document explains the problem through a series of examples of
   what can go wrong, and then provides some advice on how a device
   manufacturer can best make deal with these issues.  The
   recommendations have an impact upon device and network protocol
   design.

4) On loading MUD URLs from QR codes
   draft-richardson-opsawg-securehomegateway-mud-05
Abstract
   This informational document details the mechanism used by the CIRA
   Secure Home Gateway (SHG) to load MUD definitions for devices which
   have no integrated MUD (RFC8520) support.

5) Manufacturer Usage Description for quarantined access to firmware
draft-richardson-shg-mud-quarantined-access-02
Abstract
   The Manufacturer Usage Description is a tool to describe the limited
   access that a single function device such as an Internet of Things
   device might need.



--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide