< draft-richardson-shg-mud-quarantined-access-00.txt   draft-richardson-shg-mud-quarantined-access-01.txt >
6lo Working Group M. Richardson 6lo Working Group M. Richardson
Internet-Draft Sandelman Software Works Internet-Draft Sandelman Software Works
Intended status: Standards Track January 31, 2019 Intended status: Standards Track M. Ranganathan
Expires: August 4, 2019 Expires: January 9, 2020 NIST
July 08, 2019
Manufacturer Usuage Description for quarantined access to firmware Manufacturer Usuage Description for quarantined access to firmware
draft-richardson-shg-mud-quarantined-access-00 draft-richardson-shg-mud-quarantined-access-01
Abstract Abstract
The Manufacturer Usage Description is a tool to describe the limited The Manufacturer Usage Description is a tool to describe the limited
access that a single function device such as an Internet of Things access that a single function device such as an Internet of Things
device might need. device might need.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 33
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 August 4, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 11 skipping to change at page 2, line 11
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
3. MUD file extensions . . . . . . . . . . . . . . . . . . . . . 2 3. MUD file extensions . . . . . . . . . . . . . . . . . . . . . 2
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 2 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 2
3.2. YANG FILE . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. YANG FILE . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Protocol Definition . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
4.1. Protocol Example . . . . . . . . . . . . . . . . . . . . 4 5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 8. Normative References . . . . . . . . . . . . . . . . . . . . 4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
9.1. Normative References . . . . . . . . . . . . . . . . . . 4
9.2. Informative References . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
The document details an extension to the Manufacturer Usage The document details an extension to the Manufacturer Usage
Description (MUD) mechanism to be able to mark one or more ACLs as Description (MUD) mechanism to be able to mark one or more ACLs as
being enabled even though the device has quaranteed. being enabled even though the device has quaranteed.
2. Requirements Language 2. Requirements Language
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
skipping to change at page 2, line 44 skipping to change at page 2, line 40
[RFC2119] and indicate requirement levels for compliant STuPiD [RFC2119] and indicate requirement levels for compliant STuPiD
implementations. implementations.
3. MUD file extensions 3. MUD file extensions
3.1. Tree Diagram 3.1. Tree Diagram
module: cira-shg-mud module: cira-shg-mud
augment /m:mud: augment /m:mud:
+--rw quaranteed-device-policy +--rw quaranteed-device-policy
+--rw access-lists +--rw enabled-ace-names* [ace-name]
+--rw access-list* [name] +--rw ace-name -> /acl:acls/acl/aces/ace/name
+--rw name -> /acl:acls/acl/name
3.2. YANG FILE 3.2. YANG FILE
<CODE BEGINS> file "cira-shg-mud@2017-12-11.yang" <CODE BEGINS> file "cira-shg-mud@2019-07-08.yang"
module cira-shg-mud { module cira-shg-mud {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-shg-mud"; "urn:ietf:params:xml:ns:yang:ietf-shg-mud";
prefix "shg"; prefix "shg";
import ietf-mud { import ietf-mud {
prefix m; prefix m;
description "This module defines the format for a MUD description"; description "This module defines the format for a MUD description";
reference "RFC YYYY: MUD YANG"; reference "RFC YYYY: MUD YANG";
} }
organization "CIRALabs Secure Home Gateway project."; organization "CIRALabs Secure Home Gateway project.";
contact contact
"WG Web: <http://securehomegateway.ca/> "WG Web: <http://securehomegateway.ca/>
skipping to change at page 3, line 30 skipping to change at page 3, line 19
organization "CIRALabs Secure Home Gateway project."; organization "CIRALabs Secure Home Gateway project.";
contact contact
"WG Web: <http://securehomegateway.ca/> "WG Web: <http://securehomegateway.ca/>
WG List: <mailto:securehomegateway@cira.ca> WG List: <mailto:securehomegateway@cira.ca>
Author: Michael Richardson Author: Michael Richardson
<mailto:mcr+ietf@sandelman.ca>"; <mailto:mcr+ietf@sandelman.ca>";
description description
"This module extends the RFCXXXX MUD format to include two "This module extends the RFC8520 MUD format to two
facilities: definition of an Access Control List appropriate facilities: definition of an Access Control List appropriate
to enable device upgrade only, and provide for a history of to enable device upgrade only, and provide for a history of
modifications by third-parties to the MUD file"; modifications by third-parties to the MUD file";
revision "2017-12-11" { revision "2019-07-08" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: MUD profile for Secure Home Gateway Project"; "RFC XXXX: MUD profile for Secure Home Gateway Project";
} }
augment "/m:mud" { augment "/m:mud" {
description description
"Adds leaf nodes appropriate MUD usage in the "Adds leaf nodes appropriate MUD usage in the
Secure Home Gateway"; Secure Home Gateway";
container quaranteed-device-policy { container quaranteed-device-policy {
description description
"The policies that should be enforced on traffic "The policies that should be enforced on traffic
coming from the device when it is under quaranteen. coming from the device when it is under quaranteen.
These policies are usually a subset of operational policies These policies are usually a subset of operational policies
and are intended to permit firmware updates only. and are intended to permit firmware updates only.
They are intended to keep the device safe (and the network safe They are intended to keep the device safe (and the network safe
from the device) when the device is suspected of being from the device) when the device is suspected of being
out-of-date, but still considered sufficiently intact to be out-of-date, but still considered sufficiently intact to be
able to do a firmware update"; able to do a firmware update";
uses m:access-lists; list enabled-ace-names {
key ace-name;
leaf ace-name {
type leafref {
path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name";
}
}
}
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4. Protocol Definition 4. Security Considerations
4.1. Protocol Example
5. Security Considerations TBD
6. Privacy Considerations 5. Privacy Considerations
7. IANA Considerations TBD
There are no IANA actions created by this document. 6. IANA Considerations
8. Acknowledgements TBD
9. References There are no IANA actions created by this document.
9.1. Normative References 7. Acknowledgements
[I-D.ietf-opsawg-mud] 8. Normative References
Lear, E., Droms, R., and D. Romascanu, "Manufacturer Usage
Description Specification", draft-ietf-opsawg-mud-25 (work
in progress), June 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
9.2. Informative References [RFC8520] Lear, E., Droms, R., and D. Romascanu, "Manufacturer Usage
Description Specification", RFC 8520,
[I-D.ietf-6tisch-dtsecurity-secure-join] DOI 10.17487/RFC8520, March 2019,
Richardson, M., "6tisch Secure Join protocol", draft-ietf- <https://www.rfc-editor.org/info/rfc8520>.
6tisch-dtsecurity-secure-join-01 (work in progress),
February 2017.
[RFC8180] Vilajosana, X., Ed., Pister, K., and T. Watteyne, "Minimal
IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH)
Configuration", BCP 210, RFC 8180, DOI 10.17487/RFC8180,
May 2017, <https://www.rfc-editor.org/info/rfc8180>.
Author's Address Authors' Addresses
Michael Richardson Michael Richardson
Sandelman Software Works Sandelman Software Works
Email: mcr+ietf@sandelman.ca Email: mcr+ietf@sandelman.ca
M. Ranganathan
NIST
Email: mranga@gmail.com
 End of changes. 25 change blocks. 
56 lines changed or deleted 45 lines changed or added

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