[OPSAWG] encoding MUD URLs in QR codes
Michael Richardson <mcr+ietf@sandelman.ca> Mon, 13 January 2020 16:18 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 4124012084C for <opsawg@ietfa.amsl.com>; Mon, 13 Jan 2020 08:18:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 ehkRLeK04VwI for <opsawg@ietfa.amsl.com>; Mon, 13 Jan 2020 08:18:05 -0800 (PST)
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 43D72120840 for <opsawg@ietf.org>; Mon, 13 Jan 2020 08:18:05 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 570B63897D for <opsawg@ietf.org>; Mon, 13 Jan 2020 11:17:39 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 62A4ACFE for <opsawg@ietf.org>; Mon, 13 Jan 2020 11:18:04 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: opsawg@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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-sha256"; protocol="application/pgp-signature"
Date: Mon, 13 Jan 2020 11:18:04 -0500
Message-ID: <8080.1578932284@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/w22FWi_D5586H_LK2UXtzXLhx88>
Subject: [OPSAWG] encoding MUD URLs in QR codes
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: Mon, 13 Jan 2020 16:18:07 -0000
Hi, I have written https://datatracker.ietf.org/doc/draft-richardson-opsawg-securehomegateway-mud/ It details how to store MUD URLs in a QRcode. I would like the OPS Area WG to consider adopting this document. (I am anticipating some additional co-authors from academia, who have been working with MUD and device profiling) There are a number of questions: 1) Is this Standards Track or Informational? Informational because I'm describing something a project has done. Standards Track maybe. 2) This is not transported over the Internet, but is about things that are transported over the Internet, some might argue it's inappropriate for the IETF. Except that MUD is ours. 3) I'm amending a WiFi Alliance format, but I've heard that they are okay with this. We probably need a formal statement. I'm creating an IANA Registry here. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [OPSAWG] encoding MUD URLs in QR codes Michael Richardson