6lo Working Group M. Richardson
Internet-Draft Sandelman Software Works
Intended status: Standards Track M. Ranganathan
Expires: January 9, 2020 NIST
July 08, 2019

Manufacturer Usuage Description for quarantined access to firmware


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.

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 January 9, 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 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

The document details an extension to the Manufacturer Usage Description (MUD) mechanism to be able to mark one or more ACLs as being enabled even though the device has quaranteed.

2. Requirements Language

In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 [RFC2119] and indicate requirement levels for compliant STuPiD implementations.

3. MUD file extensions

3.1. Tree Diagram

module: cira-shg-mud
  augment /m:mud:
    +--rw quaranteed-device-policy
       +--rw enabled-ace-names* [ace-name]
          +--rw ace-name    -> /acl:acls/acl/aces/ace/name


<CODE BEGINS> file "cira-shg-mud@2019-07-08.yang"
module cira-shg-mud {
  yang-version 1.1;

  prefix "shg";

  import ietf-mud {
    prefix m;
    description "This module defines the format for a MUD description";
    reference "RFC YYYY: MUD YANG";

  organization "CIRALabs Secure Home Gateway project.";

   "WG Web:   <http://securehomegateway.ca/>
    WG List:  <mailto:securehomegateway@cira.ca>
    Author:   Michael Richardson

   "This module extends the RFC8520 MUD format to two
    facilities: definition of an Access Control List appropriate
    to enable device upgrade only, and provide for a history of
    modifications by third-parties to the MUD file";

  revision "2019-07-08" {
     "Initial version";
     "RFC XXXX: MUD profile for Secure Home Gateway Project";

  augment "/m:mud" {
       "Adds leaf nodes appropriate MUD usage in the
        Secure Home Gateway";

    container quaranteed-device-policy {
        "The policies that should be enforced on traffic
         coming from the device when it is under quaranteen.
         These policies are usually a subset of operational policies
         and are intended to permit firmware updates only.
         They are intended to keep the device safe (and the network safe
         from the device) when the device is suspected of being
         out-of-date, but still considered sufficiently intact to be
         able to do a firmware update";
      list enabled-ace-names {
        key ace-name;
        leaf ace-name {
          type leafref {
            path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name";


4. Security Considerations


5. Privacy Considerations


6. IANA Considerations


There are no IANA actions created by this document.

7. Acknowledgements

8. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.
[RFC8520] Lear, E., Droms, R. and D. Romascanu, "Manufacturer Usage Description Specification", RFC 8520, DOI 10.17487/RFC8520, March 2019.

Authors' Addresses

Michael Richardson Sandelman Software Works EMail: mcr+ietf@sandelman.ca
M. Ranganathan NIST EMail: mranga@gmail.com