On loading MUD URLs from QR codes
draft-richardson-mud-qrcode-00
OPS Area Working Group M. Richardson
Internet-Draft Sandelman Software Works
Intended status: Informational J. Latour
Expires: 20 June 2021 CIRA Labs
H. Habibi Gharakheili
UNSW Sydney
17 December 2020
On loading MUD URLs from QR codes
draft-richardson-mud-qrcode-00
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.
RFCEDITOR please remove: Pull requests and edit welcome at:
https://github.com/CIRALabs/securehomegateway-mud/tree/ietf
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 20 June 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
Richardson, et al. Expires 20 June 2021 [Page 1]
Internet-Draft QR-MUD December 2020
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. The SQRL protocol . . . . . . . . . . . . . . . . . . . . 4
3.2. Manufacturer Usage Descriptions in SQRL . . . . . . . . . 5
3.2.1. B000 Company Name . . . . . . . . . . . . . . . . . . 5
3.2.2. B001 Product Name . . . . . . . . . . . . . . . . . . 5
3.2.3. B002 Model Number . . . . . . . . . . . . . . . . . . 5
3.2.4. MUD URL Data Record . . . . . . . . . . . . . . . . . 5
3.2.5. MUD device MAC address . . . . . . . . . . . . . . . 6
4. Generic URL or Version Specific URL . . . . . . . . . . . . . 6
5. Crowd Supply of MUD Files . . . . . . . . . . . . . . . . . . 6
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
10. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
The Manufacturer Usage Description (MUD) [RFC8520] defines a YANG
data model to express what sort of access a device requires to
operate correctly. The document additionally defines three ways for
the device to communicate the URL of the resulting JSON [RFC8259]
format file to a network enforcement point: DHCP, within an X.509
certificate extension, and via LLDP.
Each of the above mechanism conveys the MUD URL in-band, and requires
modifications to the device firmware. Most small IoT devices do not
have LLDP, and often have very restricted DHCP clients. Adding the
LLDP or DHCP options requires at least some minimal configuration
change, and possibly entire new subsystems. Meanwhile, use of the
PKIX certification extension only makes sense as part of a larger
IDevID based [ieee802-1AR] deployment such as
[I-D.ietf-anima-bootstrapping-keyinfra].
Richardson, et al. Expires 20 June 2021 [Page 2]
Show full document text