Loading MUD URLs from QR codes
draft-richardson-opsawg-securehomegateway-mud-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-12-27
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
6tisch Working Group                                       M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Informational                                 J. Latour
Expires: 29 June 2020                                          CIRA Labs
                                                        27 December 2019

                     Loading MUD URLs from QR codes
            draft-richardson-opsawg-securehomegateway-mud-02

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.

   The document describes extensions to the WiFi Alliance DPP QR code to
   support the use of MUD URLs.

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 29 June 2020.

Copyright Notice

   Copyright (c) 2019 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
   extracted from this document must include Simplified BSD License text

Richardson & Latour       Expires 29 June 2020                  [Page 1]
Internet-Draft                   SHG-MUD                   December 2019

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

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 inband, and requires
   modifications to the device firmware.  Most small IoT devices do not
   have LLDP, and have very restricted DHCP clients.  Adding the LLDP or
   DHCP options requires at least some minimal configuration change, and
   possibly entire new subsystems.  The X.509 certificateion extension
   only makes sense to deploy as part of a larger IDevID based
   [ieee802-1AR] system such as [I-D.ietf-anima-bootstrapping-keyinfra].

   In all cases these mechanisms can only be implemented by persons with
   access to modify and update the firmware of the device.  The MUD
   system was designed to be implemented by Manufacturers afterall!

   In the meantime there is a chicken or egg problem ([chickenegg]): no
   manufacturers include MUD URLs in their products as there are no
   gateways that use them.  No gateways include code that processes MUD
   URLs as no products produce them.

   The mechanism described here allows any person with physical access
   to the device to affix a reference to a MUD URL that can later be
   scanned by an end user.  This can be done by the (marketing
   department) of the Manufacturer, by an outsourced assembler plant, by
   value added resellers, by a company importing the product (possibly

Richardson & Latour       Expires 29 June 2020                  [Page 2]
Internet-Draft                   SHG-MUD                   December 2019
Show full document text