Manufacturer Usage Description Specification
draft-lear-ietf-netmod-mud-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-07-29
Replaces draft-lear-ietf-dhc-mud-option, draft-lear-ietf-pkix-mud-extension
Replaced by rfc8520, draft-ietf-opsawg-mud
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                                                  R. Droms
Intended status: Standards Track                           Cisco Systems
Expires: January 30, 2017                                  July 29, 2016

              Manufacturer Usage Description Specification
                     draft-lear-ietf-netmod-mud-03

Abstract

   This memo specifies the necessary components to implement
   manufacturer usage descriptions (MUD).  This includes two YANG
   modules, IPv4 and IPv6 DHCP options, 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 January 30, 2017.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Lear & Droms            Expires January 30, 2017                [Page 1]
Internet-Draft               MUD YANG Model                    July 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  The MUD Model and Semantic Meaning  . . . . . . . . . . . . .   4
   3.  Element Definitions . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  last-update . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  previous-mud-file . . . . . . . . . . . . . . . . . . . .   5
     3.3.  cache-validity  . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  masa-server . . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  is-supported  . . . . . . . . . . . . . . . . . . . . . .   6
     3.6.  packet-direction  . . . . . . . . . . . . . . . . . . . .   6
     3.7.  manufacturer  . . . . . . . . . . . . . . . . . . . . . .   6
     3.8.  same-manufacturer . . . . . . . . . . . . . . . . . . . .   6
     3.9.  model . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.10. local-networks  . . . . . . . . . . . . . . . . . . . . .   6
     3.11. controller  . . . . . . . . . . . . . . . . . . . . . . .   7
     3.12. direction-initiated . . . . . . . . . . . . . . . . . . .   7
   4.  Processing of the MUD file  . . . . . . . . . . . . . . . . .   7
   5.  What does a MUD URL look like?  . . . . . . . . . . . . . . .   7
   6.  The MUD YANG Model  . . . . . . . . . . . . . . . . . . . . .   8
   7.  The Domain Name Extension to the ACL Model  . . . . . . . . .  11
     7.1.  source-dnsname  . . . . . . . . . . . . . . . . . . . . .  12
     7.2.  destination-dnsname . . . . . . . . . . . . . . . . . . .  12
     7.3.  The ietf-acldns Model . . . . . . . . . . . . . . . . . .  12
   8.  MUD File Example  . . . . . . . . . . . . . . . . . . . . . .  13
   9.  The MUD URL DHCP Option . . . . . . . . . . . . . . . . . . .  15
     9.1.  Client Behavior . . . . . . . . . . . . . . . . . . . . .  15
     9.2.  Server Behavior . . . . . . . . . . . . . . . . . . . . .  16
     9.3.  Relay Requirements  . . . . . . . . . . . . . . . . . . .  16
   10. The Manufacturer Usage Description (MUD) URL X.509 Extension   16
   11. The Manufacturer Usage Description LLDP extension . . . . . .  17
   12. Creating and Processing of Signed MUD Files . . . . . . . . .  17
     12.1.  Creating a MUD file signature  . . . . . . . . . . . . .  17
     12.2.  Verifying a MUD file signature . . . . . . . . . . . . .  18
   13. Extensibility . . . . . . . . . . . . . . . . . . . . . . . .  18
   14. Security Considerations . . . . . . . . . . . . . . . . . . .  19
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
     15.1.  DHCPv4 and DHCPv6 Options  . . . . . . . . . . . . . . .  20
     15.2.  PKIX Extensions  . . . . . . . . . . . . . . . . . . . .  20
Show full document text