RFC 8520 - Manufacturer Usage Description Specification

- Yang catalog entry for ietf-acldns@2018-06-15.yang
- Yang catalog entry for ietf-mud-detext-example@2018-06-15.yang
- Yang catalog entry for ietf-mud@2018-06-15.yang
- Yang impact analysis for draft-ietf-opsawg-mud
- Mailing list discussion

Stream

WG state

Submitted to IESG for Publication

Document shepherd

Joe Clarke

Shepherd write-up

Show (last changed 2017-10-10)

IESG

IESG state

RFC 8520 (Proposed Standard)

Consensus Boilerplate

Yes

Telechat date

Responsible AD

Ignas Bagdonas

Send notices to

Joe Clarke <jclarke@cisco.com>

IANA

IANA review state

IANA OK - Actions Needed

IANA action state

RFC-Ed-Ack

Email authors Email WG IPR 4 References Referenced by Nits

Internet Engineering Task Force (IETF)                           E. Lear
Request for Comments: 8520                                 Cisco Systems
Category: Standards Track                                       R. Droms
ISSN: 2070-1721                                                   Google
                                                            D. Romascanu
                                                              March 2019

              Manufacturer Usage Description Specification

Abstract

   This memo specifies a component-based architecture for Manufacturer
   Usage Descriptions (MUDs).  The goal of MUD is to provide a means for
   end devices 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, a
   Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate
   extension, and a means to sign and verify the descriptions.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8520.

Lear, et al.                 Standards Track                    [Page 1]
RFC 8520             Manufacturer Usage Descriptions          March 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  What MUD Doesn't Do . . . . . . . . . . . . . . . . . . .   5
     1.2.  A Simple Example  . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   6
     1.4.  Determining Intended Use  . . . . . . . . . . . . . . . .   6
     1.5.  Finding a Policy: The MUD URL . . . . . . . . . . . . . .   7
     1.6.  Processing of the MUD URL . . . . . . . . . . . . . . . .   8
     1.7.  Types of Policies . . . . . . . . . . . . . . . . . . . .   8
     1.8.  The Manufacturer Usage Description Architecture . . . . .  10
     1.9.  Order of Operations . . . . . . . . . . . . . . . . . . .  12
   2.  The MUD Model and Semantic Meaning  . . . . . . . . . . . . .  12
     2.1.  The IETF-MUD YANG Module  . . . . . . . . . . . . . . . .  14
   3.  MUD Model Definitions for the Root "mud" Container  . . . . .  15
     3.1.  mud-version . . . . . . . . . . . . . . . . . . . . . . .  15
     3.2.  MUD URL . . . . . . . . . . . . . . . . . . . . . . . . .  15
     3.3.  to-device-policy and from-device-policy Containers  . . .  16
     3.4.  last-update . . . . . . . . . . . . . . . . . . . . . . .  16
     3.5.  cache-validity  . . . . . . . . . . . . . . . . . . . . .  16
     3.6.  is-supported  . . . . . . . . . . . . . . . . . . . . . .  16
     3.7.  systeminfo  . . . . . . . . . . . . . . . . . . . . . . .  16
     3.8.  mfg-name, software-rev, model-name, and firmware-rev  . .  17
     3.9.  extensions  . . . . . . . . . . . . . . . . . . . . . . .  17
   4.  Augmentation to the ACL Model . . . . . . . . . . . . . . . .  17
     4.1.  manufacturer  . . . . . . . . . . . . . . . . . . . . . .  17
     4.2.  same-manufacturer . . . . . . . . . . . . . . . . . . . .  17
     4.3.  documentation . . . . . . . . . . . . . . . . . . . . . .  18
     4.4.  model . . . . . . . . . . . . . . . . . . . . . . . . . .  18
     4.5.  local-networks  . . . . . . . . . . . . . . . . . . . . .  18
     4.6.  controller  . . . . . . . . . . . . . . . . . . . . . . .  18
     4.7.  my-controller . . . . . . . . . . . . . . . . . . . . . .  19
     4.8.  direction-initiated . . . . . . . . . . . . . . . . . . .  19

Lear, et al.                 Standards Track                    [Page 2]
RFC 8520             Manufacturer Usage Descriptions          March 2019

   5.  Processing of the MUD File  . . . . . . . . . . . . . . . . .  19

Show full document text

Manufacturer Usage Description SpecificationRFC 8520

Manufacturer Usage Description Specification
RFC 8520