Manufacturer Usage Description Specification
draft-ietf-opsawg-mud-08
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (opsawg WG)
|
|
Last updated |
|
2017-08-11
|
|
Replaces |
|
draft-lear-ietf-netmod-mud
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Additional URLs |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group E. Lear
Internet-Draft Cisco Systems
Intended status: Standards Track R. Droms
Expires: February 10, 2018
D. Romascanu
August 09, 2017
Manufacturer Usage Description Specification
draft-ietf-opsawg-mud-08
Abstract
This memo specifies a component-based architecture for manufacturer
usage descriptions (MUD). This includes 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 February 10, 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
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, et al. Expires February 10, 2018 [Page 1]
Internet-Draft Manufacturer Usage Descriptions August 2017
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 . . . . . . . . . . . . . . . . . . . . 4
1.3. Determining Intended Use . . . . . . . . . . . . . . . . 5
1.4. Finding A Policy: The MUD URL . . . . . . . . . . . . . . 5
1.5. Types of Policies . . . . . . . . . . . . . . . . . . . . 6
1.6. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7
1.7. The Manufacturer Usage Description Architecture . . . . . 8
1.8. Order of operations . . . . . . . . . . . . . . . . . . . 9
2. The MUD Model and Semantic Meaning . . . . . . . . . . . . . 10
3. Element Definitions . . . . . . . . . . . . . . . . . . . . . 12
3.1. last-update . . . . . . . . . . . . . . . . . . . . . . . 12
3.2. cache-validity . . . . . . . . . . . . . . . . . . . . . 12
3.3. masa-server . . . . . . . . . . . . . . . . . . . . . . . 12
3.4. is-supported . . . . . . . . . . . . . . . . . . . . . . 12
3.5. systeminfo . . . . . . . . . . . . . . . . . . . . . . . 12
3.6. extensions . . . . . . . . . . . . . . . . . . . . . . . 12
3.7. packet-direction . . . . . . . . . . . . . . . . . . . . 13
3.8. manufacturer . . . . . . . . . . . . . . . . . . . . . . 13
3.9. same-manufacturer . . . . . . . . . . . . . . . . . . . . 13
3.10. model . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.11. local-networks . . . . . . . . . . . . . . . . . . . . . 13
3.12. controller . . . . . . . . . . . . . . . . . . . . . . . 13
3.13. my-controller . . . . . . . . . . . . . . . . . . . . . . 14
3.14. direction-initiated . . . . . . . . . . . . . . . . . . . 14
4. Processing of the MUD file . . . . . . . . . . . . . . . . . 14
5. What does a MUD URL look like? . . . . . . . . . . . . . . . 14
6. The MUD YANG Model . . . . . . . . . . . . . . . . . . . . . 15
7. The Domain Name Extension to the ACL Model . . . . . . . . . 21
7.1. source-dnsname . . . . . . . . . . . . . . . . . . . . . 21
7.2. destination-dnsname . . . . . . . . . . . . . . . . . . . 21
7.3. The ietf-acldns Model . . . . . . . . . . . . . . . . . . 21
8. MUD File Example . . . . . . . . . . . . . . . . . . . . . . 23
9. The MUD URL DHCP Option . . . . . . . . . . . . . . . . . . . 25
9.1. Client Behavior . . . . . . . . . . . . . . . . . . . . . 26
9.2. Server Behavior . . . . . . . . . . . . . . . . . . . . . 26
Show full document text