draft-ietf-netconf-keystore-08.txt   draft-ietf-netconf-keystore-09.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Watsen Networks Internet-Draft Watsen Networks
Intended status: Standards Track March 9, 2019 Intended status: Standards Track April 29, 2019
Expires: September 10, 2019 Expires: October 31, 2019
YANG Data Model for a Centralized Keystore Mechanism YANG Data Model for a Centralized Keystore Mechanism
draft-ietf-netconf-keystore-08 draft-ietf-netconf-keystore-09
Abstract Abstract
This document defines a YANG 1.1 module called "ietf-keystore" that This document defines a YANG 1.1 module called "ietf-keystore" that
enables centralized configuration of asymmetric keys and their enables centralized configuration of asymmetric keys and their
associated certificates, and notification for when configured associated certificates, and notification for when configured
certificates are about to expire. certificates are about to expire.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Editor instructions are specified elsewhere in this document. Editor instructions are specified elsewhere in this document.
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements: progress. Please apply the following replacements:
o "VVVV" --> the assigned RFC value for this draft o "VVVV" --> the assigned RFC value for this draft
Artwork in this document contains placeholder values for the date of Artwork in this document contains placeholder values for the date of
publication of this draft. Please apply the following replacement: publication of this draft. Please apply the following replacement:
o "2019-03-09" --> the publication date of this draft o "2019-04-29" --> the publication date of this draft
The following Appendix section is to be removed prior to publication: The following Appendix section is to be removed prior to publication:
o Appendix A. Change Log o Appendix A. Change Log
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 September 10, 2019. This Internet-Draft will expire on October 31, 2019.
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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. The Keystore Model . . . . . . . . . . . . . . . . . . . . . 4 3. The Keystore Model . . . . . . . . . . . . . . . . . . . . . 4
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 6
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 11 3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 16 4. Security Considerations . . . . . . . . . . . . . . . . . . . 17
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 17 5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 18
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 17 5.2. The YANG Module Names Registry . . . . . . . . . . . . . 18
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.1. Normative References . . . . . . . . . . . . . . . . . . 17 6.1. Normative References . . . . . . . . . . . . . . . . . . 18
6.2. Informative References . . . . . . . . . . . . . . . . . 18 6.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 20 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 20
A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 20 A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 20
A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 20 A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 20
A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 20 A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 20
A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 20 A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 20
A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 21 A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 21
A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 21 A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 21
A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 21 A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 21
A.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 21 A.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 21
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 21 A.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 21
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 22
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 22 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
This document defines a YANG 1.1 [RFC7950] module called "ietf- This document defines a YANG 1.1 [RFC7950] module called "ietf-
keystore" that enables centralized configuration of asymmetric keys keystore" that enables centralized configuration of asymmetric keys
and their associated certificates, and notification for when and their associated certificates, and notification for when
configured certificates are about to expire. configured certificates are about to expire.
This module also defines Six groupings designed for maximum reuse. This module also defines Six groupings designed for maximum reuse.
skipping to change at page 6, line 28 skipping to change at page 6, line 33
3.2. Example Usage 3.2. Example Usage
The following example illustrates what a fully configured keystore The following example illustrates what a fully configured keystore
might look like in <operational>, as described by Section 5.3 in might look like in <operational>, as described by Section 5.3 in
[RFC8342]. This datastore view illustrates data set by the [RFC8342]. This datastore view illustrates data set by the
manufacturing process alongside conventional configuration. This manufacturing process alongside conventional configuration. This
keystore instance has four keys, two having one associated keystore instance has four keys, two having one associated
certificate, one having two associated certificates, and one empty certificate, one having two associated certificates, and one empty
key. key.
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) =========== =========== NOTE: '\' line wrapping per BCP XX (RFC XXXX) ===========
<keystore xmlns="urn:ietf:params:xml:ns:yang:ietf-keystore" <keystore xmlns="urn:ietf:params:xml:ns:yang:ietf-keystore"
xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin" xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin"
xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"
or:origin="or:intended"> or:origin="or:intended">
<asymmetric-keys> <asymmetric-keys>
<asymmetric-key> <asymmetric-key>
<name>ex-rsa-key</name> <name>ex-rsa-key</name>
<algorithm>ct:rsa2048</algorithm> <algorithm>ct:rsa2048</algorithm>
skipping to change at page 7, line 20 skipping to change at page 7, line 26
<cert>base64encodedvalue==</cert> <cert>base64encodedvalue==</cert>
</certificate> </certificate>
</certificates> </certificates>
</asymmetric-key> </asymmetric-key>
--> -->
<asymmetric-key> <asymmetric-key>
<name>tpm-protected-key</name> <name>tpm-protected-key</name>
<algorithm or:origin="or:system">ct:rsa2048</algorithm> <algorithm or:origin="or:system">ct:rsa2048</algorithm>
<private-key or:origin="or:system">permanently-hidden</private\ <private-key or:origin="or:system">permanently-hidden</private\
\-key> -key>
<public-key or:origin="or:system">base64encodedvalue==</public\ <public-key or:origin="or:system">base64encodedvalue==</public\
\-key> -key>
<certificates> <certificates>
<certificate or:origin="or:system"> <certificate or:origin="or:system">
<name>builtin-idevid-cert</name> <name>builtin-idevid-cert</name>
<cert or:origin="or:system">base64encodedvalue==</cert> <cert or:origin="or:system">base64encodedvalue==</cert>
</certificate> </certificate>
<certificate> <certificate>
<name>my-ldevid-cert</name> <name>my-ldevid-cert</name>
<cert>base64encodedvalue==</cert> <cert>base64encodedvalue==</cert>
</certificate> </certificate>
</certificates> </certificates>
skipping to change at page 9, line 46 skipping to change at page 9, line 50
} }
} }
} }
The following example illustrates what two configured keys, one local The following example illustrates what two configured keys, one local
and the other remote, might look like. This example consistent with and the other remote, might look like. This example consistent with
other examples above (i.e., the referenced key is in an example other examples above (i.e., the referenced key is in an example
above). above).
========== NOTE: '\\' line wrapping per BCP XX (RFC XXXX) =========== =========== NOTE: '\' line wrapping per BCP XX (RFC XXXX) ===========
<keystore-usage xmlns="http://example.com/ns/example-keystore-usage"> <keystore-usage xmlns="http://example.com/ns/example-keystore-usage">
<!-- ks:local-or-keystore-asymmetric-key-grouping --> <!-- ks:local-or-keystore-asymmetric-key-grouping -->
<just-a-key> <just-a-key>
<name>a locally-defined key</name> <name>a locally-defined key</name>
<local-definition> <local-definition>
<algorithm <algorithm
xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">
ct:rsa2048 ct:rsa2048
</algorithm> </algorithm>
<private-key>base64encodedvalue==</private-key> <private-key>base64encodedvalue==</private-key>
<public-key>base64encodedvalue==</public-key> <public-key>base64encodedvalue==</public-key>
</local-definition> </local-definition>
skipping to change at page 11, line 15 skipping to change at page 11, line 19
ct:rsa2048 ct:rsa2048
</algorithm> </algorithm>
<private-key>base64encodedvalue==</private-key> <private-key>base64encodedvalue==</private-key>
<public-key>base64encodedvalue==</public-key> <public-key>base64encodedvalue==</public-key>
<cert>base64encodedvalue==</cert> <cert>base64encodedvalue==</cert>
</local-definition> </local-definition>
</end-entity-cert-with-key> </end-entity-cert-with-key>
<end-entity-cert-with-key> <end-entity-cert-with-key>
<name>a keystore-defined certificate (and its associated key)</n\ <name>a keystore-defined certificate (and its associated key)</n\
\ame> ame>
<keystore-reference>ex-rsa-cert</keystore-reference> <keystore-reference>ex-rsa-cert</keystore-reference>
</end-entity-cert-with-key> </end-entity-cert-with-key>
</keystore-usage> </keystore-usage>
3.3. YANG Module 3.3. YANG Module
This YANG module has normative references to [RFC8341] and This YANG module has normative references to [RFC8341] and
[I-D.ietf-netconf-crypto-types], and an informative reference to [I-D.ietf-netconf-crypto-types], and an informative reference to
[RFC8342]. [RFC8342].
<CODE BEGINS> file "ietf-keystore@2019-03-09.yang" <CODE BEGINS> file "ietf-keystore@2019-04-29.yang"
module ietf-keystore { module ietf-keystore {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-keystore"; namespace "urn:ietf:params:xml:ns:yang:ietf-keystore";
prefix ks; prefix ks;
import ietf-crypto-types { import ietf-crypto-types {
prefix ct; prefix ct;
reference reference
"RFC CCCC: Common YANG Data Types for Cryptography"; "RFC CCCC: Common YANG Data Types for Cryptography";
} }
skipping to change at page 12, line 9 skipping to change at page 12, line 14
contact contact
"WG Web: <http://datatracker.ietf.org/wg/netconf/> "WG Web: <http://datatracker.ietf.org/wg/netconf/>
WG List: <mailto:netconf@ietf.org> WG List: <mailto:netconf@ietf.org>
Author: Kent Watsen <mailto:kent+ietf@watsen.net>"; Author: Kent Watsen <mailto:kent+ietf@watsen.net>";
description description
"This module defines a keystore to centralize management "This module defines a keystore to centralize management
of security credentials. of security credentials.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all
capitals, as shown here.
Copyright (c) 2019 IETF Trust and the persons identified Copyright (c) 2019 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC VVVV; see This version of this YANG module is part of RFC XXXX
the RFC itself for full legal notices."; (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
itself for full legal notices.;
revision 2019-03-09 { The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all
capitals, as shown here.";
revision 2019-04-29 {
description description
"Initial version"; "Initial version";
reference reference
"RFC VVVV: "RFC VVVV:
YANG Data Model for a Centralized Keystore Mechanism"; YANG Data Model for a Centralized Keystore Mechanism";
} }
// Features /****************/
/* Features */
/****************/
feature keystore-supported { feature keystore-supported {
description description
"The 'keystore-supported' feature indicates that the server "The 'keystore-supported' feature indicates that the server
supports the keystore."; supports the keystore.";
} }
feature local-keys-supported { feature local-keys-supported {
description description
"The 'local-keys-supported' feature indicates that the "The 'local-keys-supported' feature indicates that the
server supports locally-defined keys."; server supports locally-defined keys.";
} }
// Typedefs /****************/
/* Typedefs */
/****************/
typedef asymmetric-key-ref { typedef asymmetric-key-ref {
type leafref { type leafref {
path "/ks:keystore/ks:asymmetric-keys/ks:asymmetric-key" path "/ks:keystore/ks:asymmetric-keys/ks:asymmetric-key"
+ "/ks:name"; + "/ks:name";
} }
description description
"This typedef enables modules to easily define a reference "This typedef enables modules to easily define a reference
to an asymmetric key stored in the keystore."; to an asymmetric key stored in the keystore.";
reference reference
"RFC 8342: Network Management Datastore Architecture (NMDA)"; "RFC 8342: Network Management Datastore Architecture (NMDA)";
skipping to change at page 13, line 29 skipping to change at page 13, line 39
+ "/ks:certificates/ks:certificate/ks:name"; + "/ks:certificates/ks:certificate/ks:name";
} }
description description
"This typedef enables modules to easily define a reference "This typedef enables modules to easily define a reference
to a specific certificate associated with an asymmetric key to a specific certificate associated with an asymmetric key
stored in the keystore."; stored in the keystore.";
reference reference
"RFC 8342: Network Management Datastore Architecture (NMDA)"; "RFC 8342: Network Management Datastore Architecture (NMDA)";
} }
// Groupings /*****************/
/* Groupings */
/*****************/
grouping local-or-keystore-asymmetric-key-grouping { grouping local-or-keystore-asymmetric-key-grouping {
description description
"A grouping that expands to allow the asymmetric key to be "A grouping that expands to allow the asymmetric key to be
either stored locally, within the using data model, or be either stored locally, within the using data model, or be
a reference to an asymmetric key stored in the keystore."; a reference to an asymmetric key stored in the keystore.";
choice local-or-keystore { choice local-or-keystore {
mandatory true; mandatory true;
case local { case local {
if-feature "local-keys-supported"; if-feature "local-keys-supported";
container local-definition { container local-definition {
must '(algorithm and public-key and private-key)
or not (algorithm or public-key or private-key)' {
description
"These descendent nodes are not mandatory because they
MAY be defined in <operational>. Implementations MUST
assert that these values are either configured or that
they exist in <operational>.";
}
description description
"Container to hold the local key definition."; "Container to hold the local key definition.";
uses ct:asymmetric-key-pair-grouping; uses ct:asymmetric-key-pair-grouping;
} }
} }
case keystore { case keystore {
if-feature "keystore-supported"; if-feature "keystore-supported";
leaf keystore-reference { leaf keystore-reference {
type ks:asymmetric-key-ref; type ks:asymmetric-key-ref;
description description
skipping to change at page 14, line 26 skipping to change at page 14, line 46
description description
"A grouping that expands to allow an asymmetric key and its "A grouping that expands to allow an asymmetric key and its
associated certificates to be either stored locally, within associated certificates to be either stored locally, within
the using data model, or be a reference to an asymmetric key the using data model, or be a reference to an asymmetric key
(and its associated certificates) stored in the keystore."; (and its associated certificates) stored in the keystore.";
choice local-or-keystore { choice local-or-keystore {
mandatory true; mandatory true;
case local { case local {
if-feature "local-keys-supported"; if-feature "local-keys-supported";
container local-definition { container local-definition {
must '(algorithm and public-key and private-key)
or not (algorithm or public-key or private-key)' {
description
"These descendent nodes are not mandatory because they
MAY be defined in <operational>. Implementations MUST
assert that these values are either configured or that
they exist in <operational>.";
}
description description
"Container to hold the local key definition."; "Container to hold the local key definition.";
uses ct:asymmetric-key-pair-with-certs-grouping; uses ct:asymmetric-key-pair-with-certs-grouping;
} }
} }
case keystore { case keystore {
if-feature "keystore-supported"; if-feature "keystore-supported";
leaf keystore-reference { leaf keystore-reference {
type ks:asymmetric-key-ref; type ks:asymmetric-key-ref;
description description
skipping to change at page 15, line 8 skipping to change at page 15, line 36
description description
"A grouping that expands to allow an end-entity certificate "A grouping that expands to allow an end-entity certificate
(and its associated private key) to be either stored locally, (and its associated private key) to be either stored locally,
within the using data model, or be a reference to a specific within the using data model, or be a reference to a specific
certificate in the keystore."; certificate in the keystore.";
choice local-or-keystore { choice local-or-keystore {
mandatory true; mandatory true;
case local { case local {
if-feature "local-keys-supported"; if-feature "local-keys-supported";
container local-definition { container local-definition {
must '(algorithm and public-key and private-key)
or not (algorithm or public-key or private-key)' {
description
"These descendent nodes are not mandatory because they
MAY be defined in <operational>. Implementations MUST
assert that these values are either configured or that
they exist in <operational>.";
}
description description
"Container to hold the local key definition."; "Container to hold the local key definition.";
uses ct:asymmetric-key-pair-grouping; uses ct:asymmetric-key-pair-grouping;
uses ct:end-entity-cert-grouping; uses ct:end-entity-cert-grouping;
} }
} }
case keystore { case keystore {
if-feature "keystore-supported"; if-feature "keystore-supported";
leaf keystore-reference { leaf keystore-reference {
type ks:asymmetric-key-certificate-ref; type ks:asymmetric-key-certificate-ref;
skipping to change at page 15, line 29 skipping to change at page 16, line 17
"A reference to a specific certificate, and its "A reference to a specific certificate, and its
associated private key, stored in the keystore."; associated private key, stored in the keystore.";
} }
} }
description description
"A choice between an inlined definition and a definition "A choice between an inlined definition and a definition
that exists in the keystore."; that exists in the keystore.";
} }
} }
// protocol accessible nodes /*********************************/
/* Protocol accessible nodes */
/*********************************/
container keystore { container keystore {
nacm:default-deny-write; nacm:default-deny-write;
description description
"The keystore contains a list of keys."; "The keystore contains a list of keys.";
container asymmetric-keys { container asymmetric-keys {
description description
"A list of asymmetric keys."; "A list of asymmetric keys.";
list asymmetric-key { list asymmetric-key {
must '(algorithm and public-key and private-key) must '(algorithm and public-key and private-key)
or not (algorithm or public-key or private-key)'; or not (algorithm or public-key or private-key)' {
description
"These descendent nodes are not mandatory because they
MAY be defined in <operational>. Implementations MUST
assert that these values are either configured or that
they exist in <operational>.";
}
key "name"; key "name";
description description
"An asymmetric key."; "An asymmetric key.";
leaf name { leaf name {
type string; type string;
description description
"An arbitrary name for the asymmetric key. If the name "An arbitrary name for the asymmetric key. If the name
matches the name of a key that exists independently in matches the name of a key that exists independently in
<operational> (i.e., a 'permanently-hidden' key), then <operational> (i.e., a 'permanently-hidden' key), then
the 'algorithm', 'public-key', and 'private-key' nodes the 'algorithm', 'public-key', and 'private-key' nodes
skipping to change at page 17, line 16 skipping to change at page 18, line 13
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
/keystore/asymmetric-keys/asymmetric-key/private-key: This node /keystore/asymmetric-keys/asymmetric-key/private-key: This node
is additionally sensitive to read operations such that, in is additionally sensitive to read operations such that, in
normal use cases, it should never be returned to a client. The normal use cases, it should never be returned to a client. The
best reason for returning this node is to support backup/ best reason for returning this node is to support backup/
restore type workflows. For this reason, the NACM extension restore type workflows. For this reason, the NACM extension
"default-deny-all" has been set for this data node. Note that "default-deny-all" has been set for this data node.
this extension is inherited from the grouping in the
[I-D.ietf-netconf-crypto-types] module.
5. IANA Considerations 5. IANA Considerations
5.1. The IETF XML Registry 5.1. The IETF XML Registry
This document registers one URI in the "ns" subregistry of the IETF This document registers one URI in the "ns" subregistry of the IETF
XML Registry [RFC3688]. Following the format in [RFC3688], the XML Registry [RFC3688]. Following the format in [RFC3688], the
following registration is requested: following registration is requested:
URI: urn:ietf:params:xml:ns:yang:ietf-keystore URI: urn:ietf:params:xml:ns:yang:ietf-keystore
skipping to change at page 17, line 49 skipping to change at page 18, line 44
namespace: urn:ietf:params:xml:ns:yang:ietf-keystore namespace: urn:ietf:params:xml:ns:yang:ietf-keystore
prefix: ks prefix: ks
reference: RFC VVVV reference: RFC VVVV
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-netconf-crypto-types] [I-D.ietf-netconf-crypto-types]
Watsen, K. and H. Wang, "Common YANG Data Types for Watsen, K. and H. Wang, "Common YANG Data Types for
Cryptography", draft-ietf-netconf-crypto-types-02 (work in Cryptography", draft-ietf-netconf-crypto-types-05 (work in
progress), October 2018. progress), March 2019.
[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>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
skipping to change at page 21, line 44 skipping to change at page 21, line 44
o Improved the keystore-usage examples o Improved the keystore-usage examples
A.8. 07 to 08 A.8. 07 to 08
o Added "local-definition" containers to avoid posibility of the o Added "local-definition" containers to avoid posibility of the
action/notification statements being under a "case" statement. action/notification statements being under a "case" statement.
o Updated copyright date, boilerplate template, affiliation, folding o Updated copyright date, boilerplate template, affiliation, folding
algorithm, and reformatted the YANG module. algorithm, and reformatted the YANG module.
A.9. 08 to 09
o Added a 'description' statement to the 'must' in the /keystore/
asymmetric-key node explaining that the descendent values may
exist in <operational> only, and that implementation MUST assert
that the values are either configured or that they exist in
<operational>.
o Copied above 'must' statement (and description) into the local-or-
keystore-asymmetric-key-grouping, local-or-keystore-asymmetric-
key-with-certs-grouping, and local-or-keystore-end-entity-cert-
with-key-grouping statements.
Acknowledgements Acknowledgements
The authors would like to thank for following for lively discussions The authors would like to thank for following for lively discussions
on list and in the halls (ordered by last name): Andy Bierman, Martin on list and in the halls (ordered by last name): Andy Bierman, Martin
Bjorklund, Benoit Claise, Ramkumar Dhanapal, Mehmet Ersue, Balazs Bjorklund, Benoit Claise, Ramkumar Dhanapal, Mehmet Ersue, Balazs
Kovacs, David Lamparter, Alan Luchuk, Ladislav Lhotka, Mahesh Kovacs, David Lamparter, Ladislav Lhotka, Alan Luchuk, Mahesh
Jethanandani, Radek Krejci, Reshad Rahman, Tom Petch, Juergen Jethanandani, Radek Krejci, Reshad Rahman, Tom Petch, Juergen
Schoenwaelder, Phil Shafer, Sean Turner, Eric Voit, Bert Wijnen, and Schoenwaelder, Phil Shafer, Sean Turner, Eric Voit, Bert Wijnen, and
Liang Xia. Liang Xia.
Author's Address Author's Address
Kent Watsen Kent Watsen
Watsen Networks Watsen Networks
EMail: kent+ietf@watsen.net EMail: kent+ietf@watsen.net
 End of changes. 31 change blocks. 
44 lines changed or deleted 95 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/