Manufacturer Usage Description Specification
draft-ietf-opsawg-mud-13

Document Type Active Internet-Draft (opsawg WG)
Last updated 2017-11-15 (latest revision 2017-10-24)
Replaces draft-lear-ietf-netmod-mud
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
Reviews
Additional URLs
- Yang catalog entry for ietf-acldns@2017-10-07.yang
- Yang catalog entry for ietf-mud-detext-example@2017-09-05.yang
- Yang catalog entry for ietf-mud@2017-10-07.yang
- Yang impact analysis for draft-ietf-opsawg-mud
Stream WG state Submitted to IESG for Publication
Document shepherd Joe Clarke
Shepherd write-up Show (last changed 2017-10-10)
IESG IESG state AD is watching::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Joe Clarke <jclarke@cisco.com>
IANA IANA review state IANA - Not OK
IANA action state None
Network Working Group                                            E. Lear
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                                R. Droms
Expires: April 27, 2018
                                                            D. Romascanu
                                                        October 24, 2017

              Manufacturer Usage Description Specification
                        draft-ietf-opsawg-mud-13

Abstract

   This memo specifies a component-based architecture for manufacturer
   usage descriptions (MUD).  The goal of MUD is to provide a means for
   Things to signal to the network what sort of access and network
   functionality they require to properly function.  The initial focus
   is on access control.  Later work can delve into other aspects.

   This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, an
   LLDP TLV, a URL suffix specification, an X.509 certificate extension
   and a means to sign and verify the descriptions.

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 http://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 April 27, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Lear, et al.             Expires April 27, 2018                 [Page 1]
Internet-Draft       Manufacturer Usage Descriptions        October 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  What MUD doesn't do . . . . . . . . . . . . . . . . . . .   4
     1.2.  A Simple Example  . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Determining Intended Use  . . . . . . . . . . . . . . . .   5
     1.4.  Finding A Policy: The MUD URL . . . . . . . . . . . . . .   5
     1.5.  Types of Policies . . . . . . . . . . . . . . . . . . . .   6
     1.6.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   8
     1.7.  The Manufacturer Usage Description Architecture . . . . .   9
     1.8.  Order of operations . . . . . . . . . . . . . . . . . . .  10
   2.  The MUD Model and Semantic Meaning  . . . . . . . . . . . . .  11
     2.1.  The IETF-MUD YANG Module  . . . . . . . . . . . . . . . .  11
   3.  Data Node Definitions . . . . . . . . . . . . . . . . . . . .  13
     3.1.  to-device-policy and from-device-policy containers  . . .  13
     3.2.  last-update . . . . . . . . . . . . . . . . . . . . . . .  14
     3.3.  cache-validity  . . . . . . . . . . . . . . . . . . . . .  14
     3.4.  is-supported  . . . . . . . . . . . . . . . . . . . . . .  14
     3.5.  systeminfo  . . . . . . . . . . . . . . . . . . . . . . .  14
     3.6.  extensions  . . . . . . . . . . . . . . . . . . . . . . .  14
     3.7.  manufacturer  . . . . . . . . . . . . . . . . . . . . . .  15
     3.8.  same-manufacturer . . . . . . . . . . . . . . . . . . . .  15
     3.9.  model . . . . . . . . . . . . . . . . . . . . . . . . . .  15
     3.10. local-networks  . . . . . . . . . . . . . . . . . . . . .  15
     3.11. controller  . . . . . . . . . . . . . . . . . . . . . . .  15
     3.12. my-controller . . . . . . . . . . . . . . . . . . . . . .  16
     3.13. direction-initiated . . . . . . . . . . . . . . . . . . .  16
   4.  Processing of the MUD file  . . . . . . . . . . . . . . . . .  16
   5.  What does a MUD URL look like?  . . . . . . . . . . . . . . .  17
   6.  The MUD YANG Model  . . . . . . . . . . . . . . . . . . . . .  17
   7.  The Domain Name Extension to the ACL Model  . . . . . . . . .  23
     7.1.  source-dnsname  . . . . . . . . . . . . . . . . . . . . .  24
     7.2.  destination-dnsname . . . . . . . . . . . . . . . . . . .  24
Show full document text