Manufacturer Usuage Description for quarantined access to firmware
draft-richardson-shg-mud-quarantined-access-00

Document Type Active Internet-Draft (individual)
Last updated 2019-01-31
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 2 warnings.
Additional URLs
- Yang catalog entry for cira-shg-mud@2017-12-11.yang
- Yang impact analysis for draft-richardson-shg-mud-quarantined-access
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)
6lo Working Group                                          M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Standards Track                        January 31, 2019
Expires: August 4, 2019

   Manufacturer Usuage Description for quarantined access to firmware
             draft-richardson-shg-mud-quarantined-access-00

Abstract

   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 August 4, 2019.

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.

Richardson               Expires August 4, 2019                 [Page 1]
Internet-Draft               MUD-Quaranatine                January 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  MUD file extensions . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   2
     3.2.  YANG FILE . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Definition . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Protocol Example  . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

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 access-lists
             +--rw access-list* [name]
                +--rw name    -> /acl:acls/acl/name

Richardson               Expires August 4, 2019                 [Page 2]
Internet-Draft               MUD-Quaranatine                January 2019

3.2.  YANG FILE

<CODE BEGINS> file "cira-shg-mud@2017-12-11.yang"
module cira-shg-mud {
  yang-version 1.1;

  namespace
    "urn:ietf:params:xml:ns:yang:ietf-shg-mud";
  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.";

  contact
   "WG Web:   <http://securehomegateway.ca/>
    WG List:  <mailto:securehomegateway@cira.ca>
    Author:   Michael Richardson
              <mailto:mcr+ietf@sandelman.ca>";

  description
   "This module extends the RFCXXXX MUD format to include 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";
Show full document text