[OPSAWG] changes to draft-richardson-opsawg-mud-acceptable-urls-02.txt

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 23 September 2020 00:12 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1C23A0403 for <opsawg@ietfa.amsl.com>; Tue, 22 Sep 2020 17:12:27 -0700 (PDT)
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 cODpXguo660Y for <opsawg@ietfa.amsl.com>; Tue, 22 Sep 2020 17:12:25 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 658153A03F4 for <opsawg@ietf.org>; Tue, 22 Sep 2020 17:12:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 5824A389B0 for <opsawg@ietf.org>; Tue, 22 Sep 2020 19:44:34 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Toz8vkCB8xKj for <opsawg@ietf.org>; Tue, 22 Sep 2020 19:44:31 -0400 (EDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:103c:9eff:fecb:2eac]) by tuna.sandelman.ca (Postfix) with ESMTP id 9EB5C389AD for <opsawg@ietf.org>; Tue, 22 Sep 2020 19:44:31 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EA65D40A for <opsawg@ietf.org>; Tue, 22 Sep 2020 20:05:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: opsawg@ietf.org
In-Reply-To: <160081804470.17462.16494692758703851063@ietfa.amsl.com>
References: <160081804470.17462.16494692758703851063@ietfa.amsl.com>
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: Tue, 22 Sep 2020 20:05:53 -0400
Message-ID: <29621.1600819553@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/O89HJxL9OX-YkB5gWj-fqYV1G2U>
Subject: [OPSAWG] changes to draft-richardson-opsawg-mud-acceptable-urls-02.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2020 00:12:27 -0000

draft-richardson-opsawg-mud-acceptable-urls-00.txt was first discussed at
IETF107, our "first" virtual IETF.
The slides are at:
https://www.ietf.org/proceedings/interim-2020-opsawg-01/slides/slides-interim-2020-opsawg-01-sessa-authorized-update-to-mud-urls-mud-acceptable-urls-00

I hope that the WG will consider adopting this document.

I had suggested a few different ways to do things.
Eliot suggested that I stick to common prefix of MUD URL, and asked to be an
author, and I did that in -01.  I have just done an editorial pass through
the document.  The diffs make for interesting read, but there are no
significant technical changes.

This document updates RFC8520 is a subtle semantic way: MUD controllers are
being built now which should probably take this into account.
The changes to semantics of the URL need to be taken into account by those
hosting MUD files, but it's an easy and sensible way to organize things.

The abstract could use some wordsmithing, and I would welcome edits.
Dang, I forgot to include the github URL: https://github.com/mcr/iot-mud-acceptable-urls

Name:		draft-richardson-opsawg-mud-acceptable-urls
Revision:	02
Title:		Authorized update to MUD URLs
Document date:	2020-09-22
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/id/draft-richardson-opsawg-mud-acceptable-urls-02.txt
Status:         https://datatracker.ietf.org/doc/draft-richardson-opsawg-mud-acceptable-urls/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-richardson-opsawg-mud-acceptable-urls
Htmlized:       https://tools.ietf.org/html/draft-richardson-opsawg-mud-acceptable-urls-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-richardson-opsawg-mud-acceptable-urls-02

Abstract:
   This document provides a way for an RFC8520 Manufacturer Usage
   Description (MUD) definitions to declare what are acceptable
   replacement URLs for a device.



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