NETCONF Working Group K. Watsen Internet-Draft Watsen Networks Intended status: Standards Track May 20, 2020 Expires: November 21, 2020 A YANG Data Model for a Truststore draft-ietf-netconf-trust-anchors-10 Abstract This document defines a YANG 1.1 data model for configuring globally- accessible bags of certificates and public keys that can be referenced by other data models for trust. Editorial Note (To be removed by RFC Editor) This draft contains placeholder values that need to be replaced with finalized values at the time of publication. This note summarizes all of the substitutions that are needed. No other RFC Editor instructions are specified elsewhere in this document. Artwork in this document contains shorthand references to drafts in progress. Please apply the following replacements: o "AAAA" --> the assigned RFC value for draft-ietf-netconf-crypto- types o "BBBB" --> the assigned RFC value for this draft Artwork in this document contains placeholder values for the date of publication of this draft. Please apply the following replacement: o "2020-05-20" --> the publication date of this draft The following Appendix section is to be removed prior to publication: o Appendix A. Change Log Note to Reviewers (To be removed by RFC Editor) This document presents a YANG module or modules that is/are part of a collection of drafts that work together to produce the ultimate goal of the NETCONF WG: to define configuration modules for NETCONF client and servers, and RESTCONF client and servers. The relationship between the various drafts in the collection is presented in the below diagram. Watsen Expires November 21, 2020 [Page 1] Internet-Draft A YANG Data Model for a Truststore May 2020 crypto-types ^ ^ / \ / \ trust-anchors keystore ^ ^ ^ ^ | +---------+ | | | | | | | +------------+ | tcp-client-server | / | | ^ ^ ssh-client-server | | | | ^ tls-client-server | | | ^ ^ http-client-server | | | | | ^ | | | +-----+ +---------+ | | | | | | | | +-----------|--------|--------------+ | | | | | | | | +-----------+ | | | | | | | | | | | | | | | | | netconf-client-server restconf-client-server Full draft names and link to drafts: o draft-ietf-netconf-crypto-types (html [1]) o draft-ietf-netconf-trust-anchors (html [2]) o draft-ietf-netconf-keystore (html [3]) o draft-ietf-netconf-tcp-client-server (html [4]) o draft-ietf-netconf-ssh-client-server (html [5]) o draft-ietf-netconf-tls-client-server (html [6]) o draft-ietf-netconf-http-client-server (html [7]) o draft-ietf-netconf-netconf-client-server (html [8]) o draft-ietf-netconf-restconf-client-server (html [9]) Watsen Expires November 21, 2020 [Page 2] Internet-Draft A YANG Data Model for a Truststore May 2020 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 https://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 November 21, 2020. Copyright Notice Copyright (c) 2020 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 (https://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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.2. Tree Diagram Notation . . . . . . . . . . . . . . . . . . 4 2. The Trust Anchors Model . . . . . . . . . . . . . . . . . . . 4 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 6 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 11 3. Support for Built-in Trust Anchors . . . . . . . . . . . . . 17 4. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 21 5.2. The YANG Module Names Registry . . . . . . . . . . . . . 21 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 6.1. Normative References . . . . . . . . . . . . . . . . . . 22 Watsen Expires November 21, 2020 [Page 3] Internet-Draft A YANG Data Model for a Truststore May 2020 6.2. Informative References . . . . . . . . . . . . . . . . . 22 6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24 A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 24 A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 24 A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 24 A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 24 A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 24 A.6. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 25 A.7. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 25 A.8. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 25 A.9. 08 to 09 . . . . . . . . . . . . . . . . . . . . . . . . 25 A.10. 09 to 10 . . . . . . . . . . . . . . . . . . . . . . . . 25 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 25 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 26 1. Introduction This document defines a YANG 1.1 [RFC7950] data model for configuring globally-accessible bags of certificates and public keys that can be referenced by other data models for trust. This document in compliant with Network Management Datastore Architecture (NMDA) [RFC8342]. For instance, trust anchors installed during manufacturing (e.g., for trusted well-known services), are expected to appear in (see Section 3). 1.1. Requirements Language 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. 1.2. Tree Diagram Notation Tree diagrams used in this document follow the notation defined in [RFC8340]. 2. The Trust Anchors Model 2.1. Tree Diagram The following tree diagram provides an overview of the "ietf- truststore" module. module: ietf-truststore Watsen Expires November 21, 2020 [Page 4] Internet-Draft A YANG Data Model for a Truststore May 2020 +--rw truststore +--rw certificate-bags! {certificates}? | +--rw certificate-bag* [name] | +--rw name string | +--rw description? string | +--rw certificate* [name] | +--rw name string | +--rw cert trust-anchor-cert-cms | +---n certificate-expiration | +-- expiration-date yang:date-and-time +--rw public-key-bags! {public-keys}? +--rw public-key-bag* [name] +--rw name string +--rw description? string +--rw public-key* [name] +--rw name string +--rw public-key-format identityref +--rw public-key binary grouping local-or-truststore-certs-grouping +-- (local-or-truststore) +--:(local) {local-definitions-supported}? | +-- local-definition | +-- cert* trust-anchor-cert-cms | +---n certificate-expiration | +-- expiration-date yang:date-and-time +--:(truststore) {truststore-supported,certificates}? +-- truststore-reference? ts:certificate-bag-ref grouping local-or-truststore-public-keys-grouping +-- (local-or-truststore) +--:(local) {local-definitions-supported}? | +-- local-definition | +-- public-key* [name] | +-- name? string | +-- public-key-format identityref | +-- public-key binary +--:(truststore) {truststore-supported,public-keys}? +-- truststore-reference? ts:public-key-bag-ref grouping truststore-grouping +-- certificate-bags! {certificates}? | +-- certificate-bag* [name] | +-- name? string | +-- description? string | +-- certificate* [name] | +-- name? string | +-- cert trust-anchor-cert-cms | +---n certificate-expiration | +-- expiration-date yang:date-and-time Watsen Expires November 21, 2020 [Page 5] Internet-Draft A YANG Data Model for a Truststore May 2020 +-- public-key-bags! {public-keys}? +-- public-key-bag* [name] +-- name? string +-- description? string +-- public-key* [name] +-- name? string +-- public-key-format identityref +-- public-key binary 2.2. Example Usage The following example illustrates trust anchors in . Please see Section 3 for an example illustrating built-in values in . ========== NOTE: '\' line wrapping per BCP XXX (RFC XXXX) =========== trusted-server-ca-certs Trust anchors (i.e. CA certs) used to authenticate server certificates. A server certificate is authenticated if its end-entity certificate has a chain of trust to one of these certificates. Server Cert Issuer #1 base64encodedvalue== Server Cert Issuer #2 base64encodedvalue== trusted-server-ee-certs Specific end-entity certificates used to authenticate server Watsen Expires November 21, 2020 [Page 6] Internet-Draft A YANG Data Model for a Truststore May 2020 certificates. A server certificate is authenticated if its end-entity certificate is an exact match to one of these certificates. My Application #1 base64encodedvalue== My Application #2 base64encodedvalue== trusted-client-ca-certs Trust anchors (i.e. CA certs) used to authenticate client certificates. A client certificate is authenticated if its end-entity certificate has a chain of trust to one of these certificates. Client Identity Issuer #1 base64encodedvalue== Client Identity Issuer #2 base64encodedvalue== trusted-client-ee-certs Specific end-entity certificates used to authenticate client certificates. A client certificate is authenticated if its end-entity certificate is an exact match to one of these certificates. George Jetson base64encodedvalue== Fred Flintstone Watsen Expires November 21, 2020 [Page 7] Internet-Draft A YANG Data Model for a Truststore May 2020 base64encodedvalue== trusted-ssh-public-keys Specific SSH public keys used to authenticate SSH server public keys. An SSH server public key is authenticated if its public key is an exact match to one of these public keys. This list of SSH public keys is analogous to OpenSSH's "/etc/ssh/ssh_known_hosts" file. corp-fw1 ct:ssh-public-key-format base64encodedvalue== corp-fw2 ct:ssh-public-key-format base64encodedvalue== SSH Public Keys for User A SSH public keys used to authenticate a user A's SSH public keys. An SSH public key is authenticated if it is an exact match to one of these public keys. This list of public keys is analogous to OpenSSH's "~A/.ssh/authorized_keys" file. From Source #1 ct:ssh-public-key-format Watsen Expires November 21, 2020 [Page 8] Internet-Draft A YANG Data Model for a Truststore May 2020 base64encodedvalue== From Source #2 ct:ssh-public-key-format base64encodedvalue== SSH Public Keys for User B SSH public keys used to authenticate a user B's SSH public keys. An SSH public key is authenticated if it is an exact match to one of these public keys. This list of public keys is analogous to OpenSSH's "~B/.ssh/authorized_keys" file. From Source #1 ct:ssh-public-key-format base64encodedvalue== From Source #2 ct:ssh-public-key-format base64encodedvalue== Raw Public Keys for TLS Servers Raw Public Key #1 ct:subject-public-key-info-format base64encodedvalue== Raw Public Key #2 ct:subject-public-key-info-format Watsen Expires November 21, 2020 [Page 9] Internet-Draft A YANG Data Model for a Truststore May 2020 base64encodedvalue== Raw Public Keys for TLS Clients Raw Public Key #1 ct:subject-public-key-info-format base64encodedvalue== Raw Public Key #2 ct:subject-public-key-info-format base64encodedvalue== The following example illustrates the "certificate-expiration" notification in use with the NETCONF protocol. ========== NOTE: '\' line wrapping per BCP XXX (RFC XXXX) =========== 2018-05-25T00:01:00Z explicitly-trusted-client-certs George Jetson 2018-08-05T14:18:53-05:00 Watsen Expires November 21, 2020 [Page 10] Internet-Draft A YANG Data Model for a Truststore May 2020 2.3. YANG Module This YANG module imports modules from [RFC8341] and [I-D.ietf-netconf-crypto-types]. file "ietf-truststore@2020-05-20.yang" module ietf-truststore { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-truststore"; prefix ts; import ietf-netconf-acm { prefix nacm; reference "RFC 8341: Network Configuration Access Control Model"; } import ietf-crypto-types { prefix ct; reference "RFC AAAA: Common YANG Data Types for Cryptography"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web : WG List : Author : Kent Watsen Author : Henk Birkholz "; description "This module defines a Truststore to centralize management of trust anchors including certificates and public keys. Copyright (c) 2020 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC BBBB Watsen Expires November 21, 2020 [Page 11] Internet-Draft A YANG Data Model for a Truststore May 2020 (https://www.rfc-editor.org/info/rfcBBBB); see the RFC itself for full legal notices. 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 2020-05-20 { description "Initial version"; reference "RFC BBBB: A YANG Data Model for a Truststore"; } /****************/ /* Features */ /****************/ feature truststore-supported { description "The 'truststore-supported' feature indicates that the server supports the Truststore (i.e., implements the 'ietf-truststore' module)."; } feature local-definitions-supported { description "The 'local-definitions-supported' feature indicates that the server supports locally-defined trust anchors."; } feature certificates { description "The 'certificates' feature indicates that the server implements the /truststore/certificate-bags subtree."; } feature public-keys { description "The 'public-keys' feature indicates that the server implements the /truststore/public-key-bags subtree."; } /****************/ /* Typedefs */ Watsen Expires November 21, 2020 [Page 12] Internet-Draft A YANG Data Model for a Truststore May 2020 /****************/ typedef certificate-bag-ref { type leafref { path "/ts:truststore/ts:certificate-bags/" + "ts:certificate-bag/ts:name"; } description "This typedef defines a reference to a certificate bag defined in the Truststore."; } typedef certificate-ref { type leafref { path "/ts:truststore/certificate-bags/certificate-bag" + "[name = current()/../certificate-bag]/certificate/name"; } description "This typedef define a reference to a specific certificate in a certificate bag defined in the Truststore. This typedef requires that there exist a sibling 'leaf' node called 'certificate-bag' that SHOULD have the typedef 'certificate-bag-ref'."; } typedef public-key-bag-ref { type leafref { path "/ts:truststore/ts:public-key-bags/" + "ts:public-key-bag/ts:name"; } description "This typedef define a reference to a public key bag defined in the Truststore."; } typedef public-key-ref { type leafref { path "/ts:truststore/public-key-bags/public-key-bag" + "[name = current()/../public-key-bag]/" + "public-key/name"; } description "This typedef define a reference to a specific public key in a public key bag defined in the Truststore. This typedef requires that there exist a sibling 'leaf' node called 'public-key-bag' that SHOULD have the typedef 'public-key-bag-ref'."; } Watsen Expires November 21, 2020 [Page 13] Internet-Draft A YANG Data Model for a Truststore May 2020 /*****************/ /* Groupings */ /*****************/ grouping local-or-truststore-certs-grouping { description "A grouping that allows the certificates to be either configured locally, within the using data model, or be a reference to a certificate bag stored in the Truststore."; choice local-or-truststore { mandatory true; case local { if-feature "local-definitions-supported"; container local-definition { description "A container for locally configured trust anchor certificates."; uses ct:trust-anchor-certs-grouping; } } case truststore { if-feature "truststore-supported"; if-feature "certificates"; leaf truststore-reference { type ts:certificate-bag-ref; description "A reference to a certificate bag that exists in the Truststore."; } } description "A choice between an inlined definition and a definition that exists in the Truststore."; } } grouping local-or-truststore-public-keys-grouping { description "A grouping that allows the public keys to be either configured locally, within the using data model, or be a reference to a public key bag stored in the Truststore."; choice local-or-truststore { mandatory true; case local { if-feature "local-definitions-supported"; container local-definition { description Watsen Expires November 21, 2020 [Page 14] Internet-Draft A YANG Data Model for a Truststore May 2020 "Container to hold local public key definitions."; list public-key { key name; description "A public key definition."; leaf name { type string; description "An arbitrary name for this public key."; } uses ct:public-key-grouping; } } } case truststore { if-feature "truststore-supported"; if-feature "public-keys"; leaf truststore-reference { type ts:public-key-bag-ref; description "A reference to a bag of public keys that exist in the Truststore."; } } description "A choice between an inlined definition and a definition that exists in the Truststore."; } } grouping truststore-grouping { description "Grouping definition enables use in other contexts. Where used, implementations SHOULD augment new 'case' statements into the local-or-truststore 'choice' statements to supply leafrefs to the model-specific location."; container certificate-bags { if-feature "certificates"; presence "Indicates that certificate bags have been configured."; description "A collection of certificate bags."; list certificate-bag { key "name"; min-elements 1; description "A bag of certificates. Each bag of certificates SHOULD be for a specific purpose. For instance, one bag could Watsen Expires November 21, 2020 [Page 15] Internet-Draft A YANG Data Model for a Truststore May 2020 be used to authenticate a specific set of servers, while another could be used to authenticate a specific set of clients."; leaf name { type string; description "An arbitrary name for this bag of certificates."; } leaf description { type string; description "A description for this bag of certificates. The intended purpose for the bag SHOULD be described."; } list certificate { key "name"; min-elements 1; description "A trust anchor certificate."; leaf name { type string; description "An arbitrary name for this certificate."; } uses ct:trust-anchor-cert-grouping { refine "cert" { mandatory true; } } } } } container public-key-bags { if-feature "public-keys"; presence "Indicates that public keys have been configured."; description "A collection of public key bags."; list public-key-bag { key "name"; min-elements 1; description "A bag of public keys. Each bag of keys SHOULD be for a specific purpose. For instance, one bag could be used authenticate a specific set of servers, while another could be used to authenticate a specific set of clients."; leaf name { type string; Watsen Expires November 21, 2020 [Page 16] Internet-Draft A YANG Data Model for a Truststore May 2020 description "An arbitrary name for this bag of public keys."; } leaf description { type string; description "A description for this bag public keys. The intended purpose for the bag SHOULD be described."; } list public-key { key "name"; min-elements 1; description "A public key."; leaf name { type string; description "An arbitrary name for this public key."; } uses ct:public-key-grouping; } } } } /*********************************/ /* Protocol accessible nodes */ /*********************************/ container truststore { nacm:default-deny-write; description "The Truststore contains bags of certificates and public keys."; uses truststore-grouping; } } 3. Support for Built-in Trust Anchors In some implementations, a server may define some built-in trust anchors. For instance, there may be built-in trust anchors enabling the server to securely connect to well-known services (e.g., an SZTP [RFC8572] bootstrap server) or public CA certificates to connect to arbitrary services using public PKI. Watsen Expires November 21, 2020 [Page 17] Internet-Draft A YANG Data Model for a Truststore May 2020 Built-in trust anchors are expected to be set by a vendor-specific process. Any ability for operators to modify built-in trust anchors is outside the scope of this document. As built-in trust anchors are provided by the system, they are present in . The example below illustrates what the Truststore in might look like for a server in its factory default state. Watsen Expires November 21, 2020 [Page 18] Internet-Draft A YANG Data Model for a Truststore May 2020 Built-In Manufacturer CA Certificates Certificates built into the device for authenticating manufacturer-signed objects, such as TLS server certificates, vouchers, etc. Manufacturer Root CA Cert base64encodedvalue== Built-In Public CA Certificates Certificates built into the device for authenticating certificates issued by public certificate authorities, such as the end-entity certificate for web servers. Public Root CA Cert 1 base64encodedvalue== Public Root CA Cert 2 base64encodedvalue== Public Root CA Cert 3 base64encodedvalue== In order for the built-in trust anchors to be referenced by configuration, the referenced nodes MUST first be copied into . They SHOULD be copied into using the same "key" values, so that the system can bind the references to the built-in Watsen Expires November 21, 2020 [Page 19] Internet-Draft A YANG Data Model for a Truststore May 2020 entries. Only the referenced nodes need to be copied. When using the same key values as in no new values can be added and no existing values can be changed; that which is in can only be a subset of that which is in . For instance, the following example illustrates how a single built-in public CA certificate from the previous example has been propagated to : Built-In Public CA Certificates Certificates built into the device for authenticating certificates issued by public certificate authorities, such as the end-entity certificate for web servers. Only the subset of the certificates that are referenced by other configuration nodes need to be copied. For instance, only "Public Root CA Cert 3" is present here. No new certificates can be added, nor existing certificate values changed. Missing certificates have no effect on "operational" when the configuration is applied. Public Root CA Cert 3 base64encodedvalue== 4. Security Considerations The YANG module defined in this document is designed to be accessed via YANG based management protocols, such as NETCONF [RFC6241] and RESTCONF [RFC8040]. Both of these protocols have mandatory-to- implement secure transport layers (e.g., SSH, TLS) with mutual authentication. Watsen Expires November 21, 2020 [Page 20] Internet-Draft A YANG Data Model for a Truststore May 2020 The NETCONF access control model (NACM) [RFC8341] provides the means to restrict access for particular users to a pre-configured subset of all available protocol operations and content. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: /: The entire data tree defined by this module is sensitive to write operations. For instance, the addition or removal of any trust anchor may dramatically alter the implemented security policy. For this reason, the NACM extension "default-deny- write" has been set for the entire data tree. None of the readable data nodes in this YANG module are considered sensitive or vulnerable in network environments. This module does not define any RPCs, actions, or notifications, and thus the security consideration for such is not provided here. 5. IANA Considerations 5.1. The IETF XML Registry This document registers one URI in the "ns" subregistry of the IETF XML Registry [RFC3688]. Following the format in [RFC3688], the following registration is requested: URI: urn:ietf:params:xml:ns:yang:ietf-truststore Registrant Contact: The NETCONF WG of the IETF. XML: N/A, the requested URI is an XML namespace. 5.2. The YANG Module Names Registry This document registers one YANG module in the YANG Module Names registry [RFC6020]. Following the format in [RFC6020], the the following registration is requested: name: ietf-truststore namespace: urn:ietf:params:xml:ns:yang:ietf-truststore prefix: ta reference: RFC BBBB Watsen Expires November 21, 2020 [Page 21] Internet-Draft A YANG Data Model for a Truststore May 2020 6. References 6.1. Normative References [I-D.ietf-netconf-crypto-types] Watsen, K. and H. Wang, "Common YANG Data Types for Cryptography", draft-ietf-netconf-crypto-types-14 (work in progress), March 2020. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, March 2018, . 6.2. Informative References [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . Watsen Expires November 21, 2020 [Page 22] Internet-Draft A YANG Data Model for a Truststore May 2020 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . [RFC8572] Watsen, K., Farrer, I., and M. Abrahamsson, "Secure Zero Touch Provisioning (SZTP)", RFC 8572, DOI 10.17487/RFC8572, April 2019, . 6.3. URIs [1] https://tools.ietf.org/html/draft-ietf-netconf-crypto-types [2] https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors [3] https://tools.ietf.org/html/draft-ietf-netconf-keystore [4] https://tools.ietf.org/html/draft-ietf-netconf-tcp-client-server [5] https://tools.ietf.org/html/draft-ietf-netconf-ssh-client-server [6] https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server [7] https://tools.ietf.org/html/draft-ietf-netconf-http-client-server [8] https://tools.ietf.org/html/draft-ietf-netconf-netconf-client- server [9] https://tools.ietf.org/html/draft-ietf-netconf-restconf-client- server Watsen Expires November 21, 2020 [Page 23] Internet-Draft A YANG Data Model for a Truststore May 2020 Appendix A. Change Log A.1. 00 to 01 o Added features "x509-certificates" and "ssh-host-keys". o Added nacm:default-deny-write to "trust-anchors" container. A.2. 01 to 02 o Switched "list pinned-certificate" to use the "trust-anchor-cert- grouping" from crypto-types. Effectively the same definition as before. A.3. 02 to 03 o Updated copyright date, boilerplate template, affiliation, folding algorithm, and reformatted the YANG module. A.4. 03 to 04 o Added groupings 'local-or-truststore-certs-grouping' and 'local- or-truststore-host-keys-grouping', matching similar definitions in the keystore draft. Note new (and incomplete) "truststore" usage! o Related to above, also added features 'truststore-supported' and 'local-trust-anchors-supported'. A.5. 04 to 05 o Renamed "trust-anchors" to "truststore" o Removed "pinned." prefix everywhere, to match truststore rename o Moved everything under a top-level 'grouping' to enable use in other contexts. o Renamed feature from 'local-trust-anchors-supported' to 'local- definitions-supported' (same name used in keystore) o Removed the "require-instance false" statement from the "*-ref" typedefs. o Added missing "ssh-host-keys" and "x509-certificates" if-feature statements Watsen Expires November 21, 2020 [Page 24] Internet-Draft A YANG Data Model for a Truststore May 2020 A.6. 05 to 06 o Editorial changes only. A.7. 06 to 07 o Added Henk Birkholz as a co-author (thanks Henk!) o Added PSKs and raw public keys to Truststore. A.8. 07 to 08 o Added new "Support for Built-in Trust Anchors" section. o Removed spurious "uses ct:trust-anchor-certs-grouping" line. o Removed PSK from model. A.9. 08 to 09 o Removed remaining PSK references from text. o Wrapped each top-level list with a container. o Introduced "bag" term. o Merged "SSH Public Keys" and "Raw Public Keys" in a single "Public Keys" bag. Consuming downstream modules (i.e., "ietf-[ssh/tls]- [client/server]) refine the "public-key-format" to be either SSH or TLS specific as needed. A.10. 09 to 10 o Removed "algorithm" node from examples. o Removed the no longer used statements supporting the old "ssh- public-key" and "raw-public-key" nodes. o Added a "Note to Reviewers" note to first page. Acknowledgements The authors especially thank Henk Birkholz for contributing YANG to the ietf-truststore module supporting raw public keys and PSKs (pre- shared or pairwise-symmetric keys). While these contributions were eventually replaced by reusing the existing support for asymmetric and symmetric trust anchors, respectively, it was only thru Henk's initiative that the WG was able to come to that result. Watsen Expires November 21, 2020 [Page 25] Internet-Draft A YANG Data Model for a Truststore May 2020 The authors additionally thank the following for helping give shape to this work (ordered by last name): Martin Bjorklund, Nick Hancock, Balazs Kovacs, Eric Voit, and Liang Xia. Author's Address Kent Watsen Watsen Networks EMail: kent+ietf@watsen.net Watsen Expires November 21, 2020 [Page 26]