Manufacturer Usage Description Specification
draft-ietf-opsawg-mud-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (opsawg WG)
|
|
Last updated |
|
2016-08-19
|
|
Replaces |
|
draft-lear-ietf-netmod-mud
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| 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 R. Droms
Intended status: Standards Track Cisco Systems
Expires: February 20, 2017 D. Romascanu
Avaya
August 19, 2016
Manufacturer Usage Description Specification
draft-ietf-opsawg-mud-00
Abstract
This memo specifies the necessary components to implement
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 20, 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
Lear, et al. Expires February 20, 2017 [Page 1]
Internet-Draft MUD YANG Model August 2016
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. A Simple Example . . . . . . . . . . . . . . . . . . . . 4
1.2. Determining Intended Use . . . . . . . . . . . . . . . . 4
1.3. Finding A Policy: The MUD URL . . . . . . . . . . . . . . 5
1.4. Types of Policies . . . . . . . . . . . . . . . . . . . . 5
1.5. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
1.6. The Manufacturer Usage Description Architecture . . . . . 7
2. The MUD Model and Semantic Meaning . . . . . . . . . . . . . 8
3. Element Definitions . . . . . . . . . . . . . . . . . . . . . 8
3.1. last-update . . . . . . . . . . . . . . . . . . . . . . . 9
3.2. previous-mud-file . . . . . . . . . . . . . . . . . . . . 9
3.3. cache-validity . . . . . . . . . . . . . . . . . . . . . 9
3.4. masa-server . . . . . . . . . . . . . . . . . . . . . . . 9
3.5. is-supported . . . . . . . . . . . . . . . . . . . . . . 9
3.6. packet-direction . . . . . . . . . . . . . . . . . . . . 9
3.7. manufacturer . . . . . . . . . . . . . . . . . . . . . . 10
3.8. same-manufacturer . . . . . . . . . . . . . . . . . . . . 10
3.9. model . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.10. local-networks . . . . . . . . . . . . . . . . . . . . . 10
3.11. controller . . . . . . . . . . . . . . . . . . . . . . . 10
3.12. direction-initiated . . . . . . . . . . . . . . . . . . . 10
4. Processing of the MUD file . . . . . . . . . . . . . . . . . 11
5. What does a MUD URL look like? . . . . . . . . . . . . . . . 11
6. The MUD YANG Model . . . . . . . . . . . . . . . . . . . . . 11
7. The Domain Name Extension to the ACL Model . . . . . . . . . 15
7.1. source-dnsname . . . . . . . . . . . . . . . . . . . . . 15
7.2. destination-dnsname . . . . . . . . . . . . . . . . . . . 15
7.3. The ietf-acldns Model . . . . . . . . . . . . . . . . . . 16
8. MUD File Example . . . . . . . . . . . . . . . . . . . . . . 17
9. The MUD URL DHCP Option . . . . . . . . . . . . . . . . . . . 18
9.1. Client Behavior . . . . . . . . . . . . . . . . . . . . . 19
9.2. Server Behavior . . . . . . . . . . . . . . . . . . . . . 19
9.3. Relay Requirements . . . . . . . . . . . . . . . . . . . 20
10. The Manufacturer Usage Description (MUD) URL X.509 Extension 20
11. The Manufacturer Usage Description LLDP extension . . . . . . 21
Show full document text