Manufacturer Usage Description YANG Model
draft-lear-ietf-netmod-mud-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-03-04
Replaced by RFC 8520, RFC 8520
Stream (None)
Intended RFC status (None)
Formats pdf 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)
Network Working Group                                            E. Lear
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                          March 04, 2016
Expires: September 5, 2016

               Manufacturer Usage Description YANG Model
                     draft-lear-ietf-netmod-mud-01

Abstract

   This memo specifies a YANG model to be used to generate and parse
   manufacturer usage descriptions.  These descriptions are retrieved by
   network management systems in order to instantiate policies
   associated with those devices.  This memo also specifies a well known
   URI suffix to indicate that a file contains XML derived from this
   model.

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 September 5, 2016.

Copyright Notice

   Copyright (c) 2016 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
   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

Lear                    Expires September 5, 2016               [Page 1]
Internet-Draft               MUD YANG Model                   March 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The MUD Model and Semantic Meaning  . . . . . . . . . . . . .   3
   3.  Element Definitions . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  last-update . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  cache-validity  . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  masa-server . . . . . . . . . . . . . . . . . . . . . . .   4
     3.4.  is-supported  . . . . . . . . . . . . . . . . . . . . . .   4
     3.5.  manufacturer  . . . . . . . . . . . . . . . . . . . . . .   4
     3.6.  same-manufacturer . . . . . . . . . . . . . . . . . . . .   4
     3.7.  model . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.8.  local-networks  . . . . . . . . . . . . . . . . . . . . .   4
     3.9.  controller  . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  What does a MUD URI look like?  . . . . . . . . . . . . . . .   5
   5.  The MUD YANG Model  . . . . . . . . . . . . . . . . . . . . .   6
   6.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Manufacturer Usage Descriptions (MUDs) provide advice to end networks
   on how to treat specific classes of devices.  The MUD architecture is
   explained in [I-D.lear-mud-framework].  The files that are retrieved
   are intended to be closely aligned to existing network architectures
   so that they are easy to deploy.  We make use of YANG [RFC6020] and
   XML because many network vendors have focused their network
   management efforts through this interface.

   The YANG model specified here is an extension of
   [I-D.ietf-netmod-acl-model].  The extensions in this model allow for
   a manufacturer to express classes of systems that a manufacturer
   would find necessary for the proper function of the device.  These
   classes are then instantiated into actual IP addresses through local
   processing.

   Because manufacturers do not know who will be using their devices, it
   is important for functionality referenced in usage descriptions to be

Lear                    Expires September 5, 2016               [Page 2]
Internet-Draft               MUD YANG Model                   March 2016
Show full document text