draft-ietf-opsawg-mud-02.txt   draft-ietf-opsawg-mud-03.txt 
Network Working Group E. Lear Network Working Group E. Lear
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track R. Droms Intended status: Standards Track R. Droms
Expires: June 3, 2017 Expires: July 9, 2017
D. Romascanu D. Romascanu
November 30, 2016 January 05, 2017
Manufacturer Usage Description Specification Manufacturer Usage Description Specification
draft-ietf-opsawg-mud-02 draft-ietf-opsawg-mud-03
Abstract Abstract
This memo specifies the necessary components to implement This memo specifies the necessary components to implement
manufacturer usage descriptions (MUD). This includes two YANG manufacturer usage descriptions (MUD). This includes two YANG
modules, IPv4 and IPv6 DHCP options, an LLDP TLV, a URL suffix modules, IPv4 and IPv6 DHCP options, an LLDP TLV, a URL suffix
specification, an X.509 certificate extension and a means to sign and specification, an X.509 certificate extension and a means to sign and
verify the descriptions. verify the descriptions.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 3, 2017. This Internet-Draft will expire on July 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 17 skipping to change at page 2, line 17
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. A Simple Example . . . . . . . . . . . . . . . . . . . . 4 1.1. A Simple Example . . . . . . . . . . . . . . . . . . . . 4
1.2. Determining Intended Use . . . . . . . . . . . . . . . . 4 1.2. Determining Intended Use . . . . . . . . . . . . . . . . 4
1.3. Finding A Policy: The MUD URL . . . . . . . . . . . . . . 5 1.3. Finding A Policy: The MUD URL . . . . . . . . . . . . . . 5
1.4. Types of Policies . . . . . . . . . . . . . . . . . . . . 5 1.4. Types of Policies . . . . . . . . . . . . . . . . . . . . 5
1.5. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 1.5. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
1.6. The Manufacturer Usage Description Architecture . . . . . 7 1.6. The Manufacturer Usage Description Architecture . . . . . 7
2. The MUD Model and Semantic Meaning . . . . . . . . . . . . . 8 2. The MUD Model and Semantic Meaning . . . . . . . . . . . . . 8
3. Element Definitions . . . . . . . . . . . . . . . . . . . . . 8 3. Element Definitions . . . . . . . . . . . . . . . . . . . . . 9
3.1. last-update . . . . . . . . . . . . . . . . . . . . . . . 9 3.1. last-update . . . . . . . . . . . . . . . . . . . . . . . 9
3.2. previous-mud-file . . . . . . . . . . . . . . . . . . . . 9 3.2. previous-mud-file . . . . . . . . . . . . . . . . . . . . 9
3.3. cache-validity . . . . . . . . . . . . . . . . . . . . . 9 3.3. cache-validity . . . . . . . . . . . . . . . . . . . . . 9
3.4. masa-server . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. masa-server . . . . . . . . . . . . . . . . . . . . . . . 10
3.5. is-supported . . . . . . . . . . . . . . . . . . . . . . 9 3.5. is-supported . . . . . . . . . . . . . . . . . . . . . . 10
3.6. systeminfo . . . . . . . . . . . . . . . . . . . . . . . 9 3.6. systeminfo . . . . . . . . . . . . . . . . . . . . . . . 10
3.7. packet-direction . . . . . . . . . . . . . . . . . . . . 10 3.7. packet-direction . . . . . . . . . . . . . . . . . . . . 10
3.8. manufacturer . . . . . . . . . . . . . . . . . . . . . . 10 3.8. manufacturer . . . . . . . . . . . . . . . . . . . . . . 10
3.9. same-manufacturer . . . . . . . . . . . . . . . . . . . . 10 3.9. same-manufacturer . . . . . . . . . . . . . . . . . . . . 10
3.10. model . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.10. model . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.11. local-networks . . . . . . . . . . . . . . . . . . . . . 10 3.11. local-networks . . . . . . . . . . . . . . . . . . . . . 11
3.12. controller . . . . . . . . . . . . . . . . . . . . . . . 10 3.12. controller . . . . . . . . . . . . . . . . . . . . . . . 11
3.13. direction-initiated . . . . . . . . . . . . . . . . . . . 11 3.13. direction-initiated . . . . . . . . . . . . . . . . . . . 11
4. Processing of the MUD file . . . . . . . . . . . . . . . . . 11 4. Processing of the MUD file . . . . . . . . . . . . . . . . . 11
5. What does a MUD URL look like? . . . . . . . . . . . . . . . 11 5. What does a MUD URL look like? . . . . . . . . . . . . . . . 11
6. The MUD YANG Model . . . . . . . . . . . . . . . . . . . . . 12 6. The MUD YANG Model . . . . . . . . . . . . . . . . . . . . . 12
7. The Domain Name Extension to the ACL Model . . . . . . . . . 15 7. The Domain Name Extension to the ACL Model . . . . . . . . . 16
7.1. source-dnsname . . . . . . . . . . . . . . . . . . . . . 16 7.1. source-dnsname . . . . . . . . . . . . . . . . . . . . . 16
7.2. destination-dnsname . . . . . . . . . . . . . . . . . . . 16 7.2. destination-dnsname . . . . . . . . . . . . . . . . . . . 16
7.3. The ietf-acldns Model . . . . . . . . . . . . . . . . . . 16 7.3. The ietf-acldns Model . . . . . . . . . . . . . . . . . . 16
8. MUD File Example . . . . . . . . . . . . . . . . . . . . . . 17 8. MUD File Example . . . . . . . . . . . . . . . . . . . . . . 18
9. The MUD URL DHCP Option . . . . . . . . . . . . . . . . . . . 19 9. The MUD URL DHCP Option . . . . . . . . . . . . . . . . . . . 19
9.1. Client Behavior . . . . . . . . . . . . . . . . . . . . . 19 9.1. Client Behavior . . . . . . . . . . . . . . . . . . . . . 20
9.2. Server Behavior . . . . . . . . . . . . . . . . . . . . . 20 9.2. Server Behavior . . . . . . . . . . . . . . . . . . . . . 20
9.3. Relay Requirements . . . . . . . . . . . . . . . . . . . 20 9.3. Relay Requirements . . . . . . . . . . . . . . . . . . . 21
10. The Manufacturer Usage Description (MUD) URL X.509 Extension 20 10. The Manufacturer Usage Description (MUD) URL X.509 Extension 21
11. The Manufacturer Usage Description LLDP extension . . . . . . 22 11. The Manufacturer Usage Description LLDP extension . . . . . . 22
12. Creating and Processing of Signed MUD Files . . . . . . . . . 23 12. Creating and Processing of Signed MUD Files . . . . . . . . . 24
12.1. Creating a MUD file signature . . . . . . . . . . . . . 23 12.1. Creating a MUD file signature . . . . . . . . . . . . . 24
12.2. Verifying a MUD file signature . . . . . . . . . . . . . 23 12.2. Verifying a MUD file signature . . . . . . . . . . . . . 24
13. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 24 13. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 25
14. Security Considerations . . . . . . . . . . . . . . . . . . . 24 14. Security Considerations . . . . . . . . . . . . . . . . . . . 25
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
15.1. DHCPv4 and DHCPv6 Options . . . . . . . . . . . . . . . 26 15.1. DHCPv4 and DHCPv6 Options . . . . . . . . . . . . . . . 27
15.2. PKIX Extensions . . . . . . . . . . . . . . . . . . . . 26 15.2. PKIX Extensions . . . . . . . . . . . . . . . . . . . . 27
15.3. Well Known URI Suffix . . . . . . . . . . . . . . . . . 26 15.3. Well Known URI Suffix . . . . . . . . . . . . . . . . . 27
15.4. MIME Media-type Registration for MUD files . . . . . . . 26 15.4. MIME Media-type Registration for MUD files . . . . . . . 27
15.5. LLDP IANA TLV Subtype Registry . . . . . . . . . . . . . 27 15.5. LLDP IANA TLV Subtype Registry . . . . . . . . . . . . . 28
15.6. The MUD Well Known Universal Resource Name (URNs) . . . 28 15.6. The MUD Well Known Universal Resource Name (URNs) . . . 29
16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28 16. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 29
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
17.1. Normative References . . . . . . . . . . . . . . . . . . 28 17.1. Normative References . . . . . . . . . . . . . . . . . . 29
17.2. Informative References . . . . . . . . . . . . . . . . . 30 17.2. Informative References . . . . . . . . . . . . . . . . . 31
Appendix A. Changes from Earlier Versions . . . . . . . . . . . 31 Appendix A. Changes from Earlier Versions . . . . . . . . . . . 33
Appendix B. Default MUD elements . . . . . . . . . . . . . . . . 32 Appendix B. Default MUD elements . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
1. Introduction 1. Introduction
The Internet has largely been constructed on general purpose The Internet has largely been constructed on general purpose
computers; those devices that may be used for a purpose that is computers; those devices that may be used for a purpose that is
specified by those who buy the device. [RFC1984] presumed that an specified by those who buy the device. [RFC1984] presumed that an
end device would be most capable of protecting itself. This made end device would be most capable of protecting itself. This made
sense when the typical device was a workstation or a mainframe, and sense when the typical device was a workstation or a mainframe, and
it continues to make sense for general purpose computing devices it continues to make sense for general purpose computing devices
today, including laptops, smart phones, and tablets. today, including laptops, smart phones, and tablets.
skipping to change at page 5, line 23 skipping to change at page 5, line 23
file. file.
In this memo three means are defined to emit the MUD URL. One is a In this memo three means are defined to emit the MUD URL. One is a
DHCP option[RFC2131],[RFC3315] that the DHCP client uses to inform DHCP option[RFC2131],[RFC3315] that the DHCP client uses to inform
the DHCP server. The DHCP server may take further actions, such as the DHCP server. The DHCP server may take further actions, such as
retrieve the URL or otherwise pass it along to network management retrieve the URL or otherwise pass it along to network management
system or controller. The other method defined is an X.509 system or controller. The other method defined is an X.509
constraint. The IEEE has developed [IEEE8021AR] that provides a constraint. The IEEE has developed [IEEE8021AR] that provides a
certificate-based approach to communicate device characteristics, certificate-based approach to communicate device characteristics,
which itself relies on [RFC5280]. The MUD URL extension is non- which itself relies on [RFC5280]. The MUD URL extension is non-
critical, as required by IEEE 802.1AR. Finally, an LLDP frame is critical, as required by IEEE 802.1AR. Various means may be used to
communicate that certificate, including Tunnel Extensible
Authentication Protocol (TEAP) [RFC7170]. Finally, an LLDP frame is
defined. defined.
1.4. Types of Policies 1.4. Types of Policies
When the MUD URL is resolved, the MUD controller retrieves a file When the MUD URL is resolved, the MUD controller retrieves a file
that describes what sort of communications a device is designed to that describes what sort of communications a device is designed to
have. The manufacturer may specify either specific hosts for cloud have. The manufacturer may specify either specific hosts for cloud
based services or certain classes for access within an operational based services or certain classes for access within an operational
network. An example of a class might be "devices of a specified network. An example of a class might be "devices of a specified
manufacturer type", where the manufacturer type itself is indicated manufacturer type", where the manufacturer type itself is indicated
skipping to change at page 7, line 5 skipping to change at page 7, line 12
MUD file server: a web server that hosts a MUD file. MUD file server: a web server that hosts a MUD file.
MUD controller: the system that requests and receives the MUD file MUD controller: the system that requests and receives the MUD file
from the MUD server. After it has processed a MUD file it may from the MUD server. After it has processed a MUD file it may
direct changes to relevant network elements. direct changes to relevant network elements.
MUD URL: a URL that can be used by the MUD controller to receive the MUD URL: a URL that can be used by the MUD controller to receive the
MUD file. MUD file.
Thing: the end device that emits a MUD URL.
Manufacturer: the entity that configures the Thing to emit the MUD
URL and the one who asserts a recommendation in a MUD file. The
manufacturer might not always be the entity that constructs a
device. It could, for instance, be a systems integrator, or even
a component provider.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
1.6. The Manufacturer Usage Description Architecture 1.6. The Manufacturer Usage Description Architecture
With these components laid out we now have the basis for an With these components laid out we now have the basis for an
archicture. This leads us to ASCII art. archicture. This leads us to ASCII art.
......................................... .........................................
skipping to change at page 7, line 36 skipping to change at page 7, line 51
. |_________| . . |_________| .
......................................... .........................................
Figure 1: MUD Architecture Figure 1: MUD Architecture
In the above diagram, the switch or router collects MUD URLs and In the above diagram, the switch or router collects MUD URLs and
forwards them to the network management system for processing. This forwards them to the network management system for processing. This
happens in different ways, depending on how the URI is communicated. happens in different ways, depending on how the URI is communicated.
For instance, in the case of DHCP, the DHCP server might receive the For instance, in the case of DHCP, the DHCP server might receive the
URI and then process it. In the case of IEEE 802.1X, the switch URI and then process it. In the case of IEEE 802.1X, the switch
would tunnel the URI to the authentication server, who would then would tunnel the URI via a certificate to the authentication server,
process it. who would then process it. One method to do this is TEAP, described
in [RFC7170]. The certificate extension is described below.
The information returned by the web site is valid for the duration of The information returned by the web site is valid for the duration of
the device's connection, or as specified in the description. Thus if the device's connection, or as specified in the description. Thus if
the device is mobile, when it moves on, any configuration in the the device is mobile, when it moves on, any configuration in the
switch is removed. Similarly, from time to time the description may switch is removed. Similarly, from time to time the description may
be refreshed, based on new capabilities or communication patterns or be refreshed, based on new capabilities or communication patterns or
vulnerabilities. vulnerabilities.
The web site is typically run by or on behalf of the manufacturer. The web site is typically run by or on behalf of the manufacturer.
Its domain name is that of the authority found in the MUD URL. For Its domain name is that of the authority found in the MUD URL. For
skipping to change at page 12, line 13 skipping to change at page 12, line 31
Specifically if it has been updated in the field, this is the place Specifically if it has been updated in the field, this is the place
where evidence of that update would appear. The field should be where evidence of that update would appear. The field should be
changed when the intended communication patterns of a device change. changed when the intended communication patterns of a device change.
While from a controller standpoint, only comparison and matching While from a controller standpoint, only comparison and matching
operations are safe, it is envisioned that updates will require some operations are safe, it is envisioned that updates will require some
administrative review. Processing of this URL occurs as specified in administrative review. Processing of this URL occurs as specified in
[RFC2818] and [RFC3986]. [RFC2818] and [RFC3986].
6. The MUD YANG Model 6. The MUD YANG Model
<CODE BEGINS>file "ietf-mud@2016-07-20.yang"; <CODE BEGINS>file "ietf-mud@2016-07-20.yang";
module ietf-mud { module ietf-mud {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-mud"; namespace "urn:ietf:params:xml:ns:yang:ietf-mud";
prefix "ietf-mud"; prefix "ietf-mud";
import ietf-access-control-list { import ietf-access-control-list {
prefix "acl"; prefix "acl";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
organization organization
"IETF OPSAWG (Ops Area) Working Group"; "IETF OPSAWG (Ops Area) Working Group";
contact contact
"WG Web: http://tools.ietf.org/wg/opsawg/ "WG Web: http://tools.ietf.org/wg/opsawg/
WG List: opsawg@ietf.org WG List: opsawg@ietf.org
WG Chair: Warren Kumari WG Chair: Warren Kumari
warren@kumari.net warren@kumari.net
WG Chair: Zhou Tianran WG Chair: Zhou Tianran
zhoutianran@huawei.com zhoutianran@huawei.com
Editor: Eliot Lear Editor: Eliot Lear
lear@cisco.com lear@cisco.com
Editor: Ralph Droms Editor: Ralph Droms
rdroms@cisco.com rdroms@cisco.com
"; ";
description description
"This YANG module defines a component that augments the "This YANG module defines a component that augments the
IETF description of an access list. This specific module IETF description of an access list. This specific module
focuses on additional filters that include local, model, focuses on additional filters that include local, model,
and same-manufacturer. and same-manufacturer.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2016 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2016-07-20" { revision "2016-07-20" {
description "Base version of MUD extensions to ACL model"; description "Base version of MUD extensions to ACL model";
reference "RFC XXXX: Manufacturer Usage Description Specification"; reference "RFC XXXX: Manufacturer Usage Description
} Specification";
}
typedef direction { typedef direction {
type enumeration { type enumeration {
enum to-device { enum to-device {
description "packets or flows destined to the target device"; description "packets or flows destined to the target
} device";
enum from-device { }
description "packets or flows destined from enum from-device {
the target device"; description "packets or flows destined from
} the target device";
} }
description "Which way are we talking about?"; }
} description "Which way are we talking about?";
container metainfo { }
description "Information about when support end(ed), and container metainfo {
when to refresh";
leaf last-update { description "Information about when support end(ed), and
type yang:date-and-time; when to refresh";
description "This is intended to be the time and date that
the MUD file was generated.";
}
leaf previous-mud-file { leaf last-update {
type inet:uri; type yang:date-and-time;
description "Use to find the previous MUD file location description "This is intended to be the time and date that
for auditing purposes."; the MUD file was generated.";
} }
leaf cache-validity {
type uint32;
description "The information retrieved from the MUD server is
valid for these many hours, after which it should
be refreshed.";
}
leaf masa-server { leaf previous-mud-file {
type inet:uri; type inet:uri;
description "The URI of the MASA server that network description "Use to find the previous MUD file location
elements should forward requests to for this device."; for auditing purposes.";
} }
leaf is-supported { leaf cache-validity {
type boolean; type uint32;
description "The element is currently supported description "The information retrieved from the MUD server is
by the manufacturer."; valid for these many hours, after which it should
} be refreshed.";
leaf systeminfo { }
type string;
description "A non-normative name and description of the device
this file is used for.";
}
}
augment "/acl:access-lists/acl:acl" { leaf masa-server {
description "add inbound or outbound. Normally access lists type inet:uri;
are applied in an inbound or outbound direction description "The URI of the MASA server that network
separately from their definition. This is not elements should forward requests to for this device.";
possible with MUD."; }
leaf packet-direction
{
type direction;
description "inbound or outbound ACL.";
}
}
augment "/acl:access-lists/acl:acl/" + leaf is-supported {
"acl:access-list-entries/acl:ace/" + type boolean;
"acl:matches" { description "The element is currently supported
description "adding abstractions to avoid need of IP addresses"; by the manufacturer.";
}
leaf systeminfo {
type string;
description "A non-normative name and description of the device
this file is used for.";
}
}
leaf manufacturer { augment "/acl:access-lists/acl:acl" {
type inet:host; description "add inbound or outbound. Normally access lists
description "authority component of the manufacturer URI"; are applied in an inbound or outbound direction
} separately from their definition. This is not
leaf same-manufacturer { possible with MUD.";
type empty; leaf packet-direction
description "expand to ACEs for each device {
with the same origin"; type direction;
} description "inbound or outbound ACL.";
}
}
leaf model { augment "/acl:access-lists/acl:acl/" +
type string; "acl:access-list-entries/acl:ace/" +
description "specific model (including version) for a "acl:matches" {
given manufacturer"; description "adding abstractions to avoid need of IP addresses";
}
leaf local-networks { leaf manufacturer {
type empty; type inet:host;
description "this string is used to indicate networks description "authority component of the manufacturer URI";
considered local in a given environment."; }
}
leaf controller {
type inet:uri;
description "expands to one or more controllers for a
given service that is codified by inet:uri.";
}
leaf direction-initiated {
type direction;
description "which direction a flow was initiated";
}
}
}
<CODE ENDS> leaf same-manufacturer {
type empty;
description "expand to ACEs for each device
with the same origin";
}
leaf model {
type string;
description "specific model (including version) for a
given manufacturer";
}
leaf local-networks {
type empty;
description "this string is used to indicate networks
considered local in a given environment.";
}
leaf controller {
type inet:uri;
description "expands to one or more controllers for a
given service that is codified by inet:uri.";
}
leaf direction-initiated {
type direction;
description "which direction a flow was initiated";
}
}
}
<CODE ENDS>
7. The Domain Name Extension to the ACL Model 7. The Domain Name Extension to the ACL Model
This module specifies an extension to IETF-ACL model such that domain This module specifies an extension to IETF-ACL model such that domain
names may be referenced by augmenting the "matches" element. names may be referenced by augmenting the "matches" element.
Different implementations may deploy differing methods to maintain Different implementations may deploy differing methods to maintain
the mapping between IP address and domain name, if indeed any are the mapping between IP address and domain name, if indeed any are
needed. However, the intent is that resources that are referred to needed. However, the intent is that resources that are referred to
using a name should be authorized (or not) within an access list. using a name should be authorized (or not) within an access list.
skipping to change at page 16, line 27 skipping to change at page 16, line 45
7.2. destination-dnsname 7.2. destination-dnsname
The argument corresponds to a domain name of a destination as The argument corresponds to a domain name of a destination as
specified by inet:host. Depending on how the model is used, it may specified by inet:host. Depending on how the model is used, it may
or may not be resolved, as required by the implementation and or may not be resolved, as required by the implementation and
circumstances. circumstances.
7.3. The ietf-acldns Model 7.3. The ietf-acldns Model
<CODE BEGINS>file "ietf-acldns@2007-07020.yang"; <CODE BEGINS>file "ietf-acldns@2016-07-20.yang";
module ietf-acldns { module ietf-acldns {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-acldns"; namespace "urn:ietf:params:xml:ns:yang:ietf-acldns";
prefix "ietf-acldns"; prefix "ietf-acldns";
import ietf-access-control-list {
prefix "acl";
}
import ietf-access-control-list { import ietf-inet-types {
prefix "acl"; prefix "inet";
} }
import ietf-inet-types { organization
prefix "inet"; "IETF OPSAWG (Ops Area) Working Group";
}
organization contact
"IETF OPSAWG (Ops Area) Working Group"; "WG Web: http://tools.ietf.org/wg/opsawg/
WG List: opsawg@ietf.org
WG Chair: Warren Kumari
warren@kumari.net
WG Chair: Zhou Tianran
zhoutianran@huawei.com
Editor: Eliot Lear
lear@cisco.com
Editor: Ralph Droms
rdroms@cisco.com
";
contact description
"WG Web: http://tools.ietf.org/wg/opsawg/ "This YANG module defines a component that augments the
WG List: opsawg@ietf.org IETF description of an access list to allow dns names
WG Chair: Warren Kumari as matching criteria.";
warren@kumari.net
WG Chair: Zhou Tianran
zhoutianran@huawei.com
Editor: Eliot Lear
lear@cisco.com
Editor: Ralph Droms
rdroms@cisco.com
";
description revision "2016-07-20" {
"This YANG module defines a component that augments the description "Base version of dnsname extension of ACL model";
IETF description of an access list to allow dns names reference "RFC XXXX: Manufacturer Usage Description
as matching criteria."; Specification";
}
revision "2016-07-20" { augment "/acl:access-lists/acl:acl/" +
description "Base version of dnsname extension of ACL model"; "acl:access-list-entries/acl:ace/" +
reference "RFC XXXX: Manufacturer Usage Description Specification"; "acl:matches/acl:ace-type/acl:ace-ip" {
} description "adding domain names to matching";
augment "/acl:access-lists/acl:acl/" + leaf src-dnsname {
"acl:access-list-entries/acl:ace/" + type inet:host;
"acl:matches/acl:ace-type/acl:ace-ip" { description "domain name to be matched against";
description "adding domain names to matching"; }
leaf dst-dnsname {
type inet:host;
description "domain name to be matched against";
leaf src-dnsname { }
type inet:host;
description "domain name to be matched against";
}
leaf dst-dnsname {
type inet:host;
description "domain name to be matched against";
} }
} }
}
<CODE ENDS> <CODE ENDS>
8. MUD File Example 8. MUD File Example
This example contains two access lists that are intended to provide This example contains two access lists that are intended to provide
outbound access to a cloud service on TCP port 443. outbound access to a cloud service on TCP port 443.
{ {
"ietf-mud:metainfo": { "ietf-mud:metainfo": {
"last-update": "2016-05-18T20:00:50Z", "last-update": "2016-05-18T20:00:50Z",
"cache-validity": 1440 "cache-validity": 1440
skipping to change at page 19, line 28 skipping to change at page 19, line 48
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_MUD_URL_V6 | option-length | | OPTION_MUD_URL_V6 | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MUD URL | | MUD URL |
| ... | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OPTION_MUD_URL_V6 (TBD; assigned by IANA). OPTION_MUD_URL_V6 (112; assigned by IANA).
option-length contains the length of the URL in octets. option-length contains the length of the URL in octets.
The intent of this option is to provide both a new device classifier The intent of this option is to provide both a new device classifier
to the network as well as some recommended configuration to the to the network as well as some recommended configuration to the
routers that implement policy. However, it is entirely the purview routers that implement policy. However, it is entirely the purview
of the network system as managed by the network administrator to of the network system as managed by the network administrator to
decide what to do with this information. The key function of this decide what to do with this information. The key function of this
option is simply to identify the type of device to the network in a option is simply to identify the type of device to the network in a
structured way such that the policy can be easily found with existing structured way such that the policy can be easily found with existing
skipping to change at page 21, line 22 skipping to change at page 22, line 5
[RFC5280]: [RFC5280]:
These extensions may be used to direct applications to on-line These extensions may be used to direct applications to on-line
information about the issuer or the subject. information about the issuer or the subject.
The MUD URL is precisely that: online information about the The MUD URL is precisely that: online information about the
particular subject. particular subject.
The new extension is identified as follows: The new extension is identified as follows:
MUDURLExtnModule-2016 { iso(1) identified-organization(3) dod(6) <CODE BEGINS>
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0)
id-mod-mudURLExtn2016(TBD1) }
DEFINITIONS IMPLICIT TAGS ::= BEGIN MUDURLExtnModule-2016 { iso(1) identified-organization(3) dod(6)
internet(1) security(5) mechanisms(5) pkix(7)
id-mod(0) id-mod-mudURLExtn2016(88) }
-- EXPORTS ALL -- DEFINITIONS IMPLICIT TAGS ::= BEGIN
IMPORTS -- EXPORTS ALL --
EXTENSION
FROM PKIX-CommonTypes-2009
{ iso(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) id-mod(0)
id-mod-pkixCommon-02(57) }
id-pe IMPORTS
FROM PKIX1Explicit-2009 EXTENSION
{ iso(1) identified-organization(3) dod(6) internet(1) FROM PKIX-CommonTypes-2009
security(5) mechanisms(5) pkix(7) id-mod(0) { iso(1) identified-organization(3) dod(6) internet(1)
id-mod-pkix1-explicit-02(51) } ; security(5) mechanisms(5) pkix(7) id-mod(0)
MUDCertExtensions EXTENSION ::= { ext-MUDURL, ... } id-mod-pkixCommon-02(57) }
ext-MUDURL EXTENSION ::= { SYNTAX MUDURLSyntax
IDENTIFIED BY id-pe-mud-url }
id-pe-mud-url OBJECT IDENTIFIER ::= { id-pe TBD2 } id-pe
FROM PKIX1Explicit-2009
{ iso(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) id-mod(0)
id-mod-pkix1-explicit-02(51) } ;
MUDCertExtensions EXTENSION ::= { ext-MUDURL, ... }
ext-MUDURL EXTENSION ::= { SYNTAX MUDURLSyntax
IDENTIFIED BY id-pe-mud-url }
MUDURLSyntax ::= IA5String id-pe-mud-url OBJECT IDENTIFIER ::= { id-pe 25 }
END MUDURLSyntax ::= IA5String
END
<CODE ENDS>
11. The Manufacturer Usage Description LLDP extension 11. The Manufacturer Usage Description LLDP extension
The IEEE802.1AB Link Layer Discovery Protocol (LLDP) [IEEE8021AB] is The IEEE802.1AB Link Layer Discovery Protocol (LLDP) [IEEE8021AB] is
a one hop vendor-neutral link layer protocols used by end hosts a one hop vendor-neutral link layer protocols used by end hosts
network devices for advertising their identity, capabilities, and network devices for advertising their identity, capabilities, and
neighbors on an IEEE 802 local area network. Its Type-Length-Value neighbors on an IEEE 802 local area network. Its Type-Length-Value
(TLV) design allows for 'vendor-specific' extensions to be defined. (TLV) design allows for 'vendor-specific' extensions to be defined.
IANA has a registered IEEE 802 organizationally unique identifier IANA has a registered IEEE 802 organizationally unique identifier
(OUI) defined as documented in [RFC7042]. The MUD LLDP extension (OUI) defined as documented in [RFC7042]. The MUD LLDP extension
skipping to change at page 25, line 44 skipping to change at page 26, line 35
changed, the controller MAY check the WHOIS database to see if changed, the controller MAY check the WHOIS database to see if
registration ownership of a domain has changed. If a change has registration ownership of a domain has changed. If a change has
occured, or if for some reason it is not possible to determine occured, or if for some reason it is not possible to determine
whether ownership has changed, further review may be warranted. whether ownership has changed, further review may be warranted.
Note, this remediation does not take into account the case of a Note, this remediation does not take into account the case of a
device that was produced long ago and only recently fielded, or the device that was produced long ago and only recently fielded, or the
case where a new MUD controller has been installed. case where a new MUD controller has been installed.
The release of a MUD URL by a device reveals what the device is, and The release of a MUD URL by a device reveals what the device is, and
provides an attacker with guidance on what vulnerabilities may be provides an attacker with guidance on what vulnerabilities may be
present. This is a security consideration. present.
While the MUD URL itself is not intended to be unique to a specific While the MUD URL itself is not intended to be unique to a specific
device, the release of the URL may aid an observer in identifying device, the release of the URL may aid an observer in identifying
individuals when combined with other information. This is a privacy individuals when combined with other information. This is a privacy
consideration. consideration.
In addressing both of these concerns, implementors should take into In addressing both of these concerns, implementors should take into
account what other information they are advertising through account what other information they are advertising through
mechanisms such as mDNS[RFC6872], how a device might otherwise be mechanisms such as mDNS[RFC6872], how a device might otherwise be
identified, perhaps through how it behaves when it is connected to identified, perhaps through how it behaves when it is connected to
the network, whether a device is intended to be used by individuals the network, whether a device is intended to be used by individuals
or carry personal identifying information, and then apply appropriate or carry personal identifying information, and then apply appropriate
data minimization techniques. One approach is to make use of EAP-TLS data minimization techniques. One approach is to make use of TEAP
(cited above) as the means to share information with the network. [RFC7170] as the means to share information with authorized
Network devices may also assist in limiting access to the MUD-URL components in the network. Network devices may also assist in
through the use of mechanisms such as DHCPv6-Shield [RFC7610]. limiting access to the MUD-URL through the use of mechanisms such as
DHCPv6-Shield [RFC7610].
15. IANA Considerations 15. IANA Considerations
15.1. DHCPv4 and DHCPv6 Options 15.1. DHCPv4 and DHCPv6 Options
The IANA has allocated option 161 in the Dynamic Host Configuration The IANA has allocated option 161 in the Dynamic Host Configuration
Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters registry Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters registry
for the MUD DHCPv4 option. for the MUD DHCPv4 option.
IANA is requested to allocated the DHCPv4 and v6 options as specified IANA is requested to allocated the DHCPv4 and v6 options as specified
skipping to change at page 27, line 5 skipping to change at page 28, line 5
The IANA has allocated the URL suffix of "mud" as follows: The IANA has allocated the URL suffix of "mud" as follows:
o URI Suffix: "mud" o Specification documents: this document o o URI Suffix: "mud" o Specification documents: this document o
Related information: n/a Related information: n/a
15.4. MIME Media-type Registration for MUD files 15.4. MIME Media-type Registration for MUD files
The following media-type is defined for transfer of MUD file: The following media-type is defined for transfer of MUD file:
o Type name: application o Type name: application
o Subtype name: mud+json o Subtype name: mud+json
o Required parameters: n/a o Required parameters: n/a
o Optional parameters: n/a o Optional parameters: n/a
o Encoding considerations: 8bit; application/mud+json values o Encoding considerations: 8bit; application/mud+json values
are represented as a JSON object; UTF-8 encoding SHOULD be are represented as a JSON object; UTF-8 encoding SHOULD be
employed. employed.
o Security considerations: See {{secon}} of this document. o Security considerations: See {{secon}} of this document.
o Interoperability considerations: n/a o Interoperability considerations: n/a
o Published specification: this document o Published specification: this document
o Applications that use this media type: MUD controllers as o Applications that use this media type: MUD controllers as
specified by this document. specified by this document.
o Fragment identifier considerations: n/a o Fragment identifier considerations: n/a
o Additional information: o Additional information:
Magic number(s): n/a
File extension(s): n/a
Macintosh file type code(s): n/a
o Person & email address to contact for further information: Magic number(s): n/a
Eliot Lear <lear@cisco.com>, Ralph Droms <rdroms@cisco.com> File extension(s): n/a
o Intended usage: COMMON Macintosh file type code(s): n/a
o Restrictions on usage: none
o Author: Eliot Lear <lear@cisco.com>, Ralph Droms <rdroms@cisco.com> o Person & email address to contact for further information:
o Change controller: IESG Eliot Lear <lear@cisco.com>, Ralph Droms <rdroms@cisco.com>
o Provisional registration? (standards tree only): No. o Intended usage: COMMON
o Restrictions on usage: none
o Author:
Eliot Lear <lear@cisco.com>
Ralph Droms <rdroms@cisco.com>
o Change controller: IESG
o Provisional registration? (standards tree only): No.
15.5. LLDP IANA TLV Subtype Registry 15.5. LLDP IANA TLV Subtype Registry
IANA is requested to create a new registry for IANA Link Layer IANA is requested to create a new registry for IANA Link Layer
Discovery Protocol (LLDP) TLV subtype values. The recommended policy Discovery Protocol (LLDP) TLV subtype values. The recommended policy
for this registry is Expert Review. The maximum number of entries in for this registry is Expert Review. The maximum number of entries in
the registry is 256. the registry is 256.
IANA is required to populate the initial registry with the value: IANA is required to populate the initial registry with the value:
skipping to change at page 28, line 10 skipping to change at page 29, line 10
Description = the Manufacturer Usage Description (MUD) Uniform Description = the Manufacturer Usage Description (MUD) Uniform
Resource Locator (URL) Resource Locator (URL)
Reference = < this document > Reference = < this document >
15.6. The MUD Well Known Universal Resource Name (URNs) 15.6. The MUD Well Known Universal Resource Name (URNs)
The following parameter registry is requested to be added in The following parameter registry is requested to be added in
accordance with [RFC3553] accordance with [RFC3553]
Registry name: "urn:ietf:params:mud" is requested. Registry name: "urn:ietf:params:mud" is requested.
Specification: this document Specification: this document
Repository: this document Repository: this document
Index value: Encoded identically to a TCP/UDP port service name, as Index value: Encoded identically to a TCP/UDP port service
specified in Section 5.1 of [RFC6335] name, as specified in Section 5.1 of [RFC6335]
The following entries should be added to the "urn:ietf:params:mud" The following entries should be added to the "urn:ietf:params:mud"
name space: name space:
"urn:ietf:params:mud:dns" refers to the service specified by "urn:ietf:params:mud:dns" refers to the service specified by
[RFC1123]. "urn:ietf:params:mud:ntp" refers to the service specified [RFC1123]. "urn:ietf:params:mud:ntp" refers to the service specified
by [RFC5905]. by [RFC5905].
16. Acknowledgments 16. Acknowledgments
skipping to change at page 31, line 36 skipping to change at page 32, line 36
H., and O. Festor, "The Common Log Format (CLF) for the H., and O. Festor, "The Common Log Format (CLF) for the
Session Initiation Protocol (SIP): Framework and Session Initiation Protocol (SIP): Framework and
Information Model", RFC 6872, DOI 10.17487/RFC6872, Information Model", RFC 6872, DOI 10.17487/RFC6872,
February 2013, <http://www.rfc-editor.org/info/rfc6872>. February 2013, <http://www.rfc-editor.org/info/rfc6872>.
[RFC7042] Eastlake 3rd, D. and J. Abley, "IANA Considerations and [RFC7042] Eastlake 3rd, D. and J. Abley, "IANA Considerations and
IETF Protocol and Documentation Usage for IEEE 802 IETF Protocol and Documentation Usage for IEEE 802
Parameters", BCP 141, RFC 7042, DOI 10.17487/RFC7042, Parameters", BCP 141, RFC 7042, DOI 10.17487/RFC7042,
October 2013, <http://www.rfc-editor.org/info/rfc7042>. October 2013, <http://www.rfc-editor.org/info/rfc7042>.
[RFC7170] Zhou, H., Cam-Winget, N., Salowey, J., and S. Hanna,
"Tunnel Extensible Authentication Protocol (TEAP) Version
1", RFC 7170, DOI 10.17487/RFC7170, May 2014,
<http://www.rfc-editor.org/info/rfc7170>.
[RFC7452] Tschofenig, H., Arkko, J., Thaler, D., and D. McPherson, [RFC7452] Tschofenig, H., Arkko, J., Thaler, D., and D. McPherson,
"Architectural Considerations in Smart Object Networking", "Architectural Considerations in Smart Object Networking",
RFC 7452, DOI 10.17487/RFC7452, March 2015, RFC 7452, DOI 10.17487/RFC7452, March 2015,
<http://www.rfc-editor.org/info/rfc7452>. <http://www.rfc-editor.org/info/rfc7452>.
[RFC7488] Boucadair, M., Penno, R., Wing, D., Patil, P., and T. [RFC7488] Boucadair, M., Penno, R., Wing, D., Patil, P., and T.
Reddy, "Port Control Protocol (PCP) Server Selection", Reddy, "Port Control Protocol (PCP) Server Selection",
RFC 7488, DOI 10.17487/RFC7488, March 2015, RFC 7488, DOI 10.17487/RFC7488, March 2015,
<http://www.rfc-editor.org/info/rfc7488>. <http://www.rfc-editor.org/info/rfc7488>.
Appendix A. Changes from Earlier Versions Appendix A. Changes from Earlier Versions
RFC Editor to remove this section prior to publication. RFC Editor to remove this section prior to publication.
Draft -02 to -03: * Additional IANA updates * Format correction in
YANG. * Add reference to TEAP.
Draft -01 to -02: * Update IANA considerations * Accept Russ Housley Draft -01 to -02: * Update IANA considerations * Accept Russ Housley
rewrite of X.509 text * Include privacy considerations text * Redo rewrite of X.509 text * Include privacy considerations text * Redo
the URL limit. Still 255 bytes, but now stated in the URL the URL limit. Still 255 bytes, but now stated in the URL
definition. * Change URI registration to be under urn:ietf:params definition. * Change URI registration to be under urn:ietf:params
Draft -00 to -01: * Fix cert trust text. * change supportInformation Draft -00 to -01: * Fix cert trust text. * change supportInformation
to meta-info * Add an informaitonal element in. * add urn registry to meta-info * Add an informaitonal element in. * add urn registry
and create first entry * add default elements and create first entry * add default elements
Appendix B. Default MUD elements Appendix B. Default MUD elements
 End of changes. 68 change blocks. 
282 lines changed or deleted 312 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/