<?xml version='1.0'encoding='utf-8'?>encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]><?rfc toc="yes"?> <?rfc symrefs="yes"?> <?rfc sortrefs="yes" ?> <?rfc compact="yes"?> <?rfc subcompact="no"?> <?rfc linkmailto="no" ?> <?rfc editing="no" ?> <?rfc comments="yes" ?> <?rfc inline="yes"?> <?rfc rfcedstyle="yes"?> <?rfc-ext allow-markup-in-artwork="yes" ?> <?rfc-ext include-index="no" ?> <!--<?rfc strict="no"?> --><rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" consensus="true" submissionType="IETF" ipr="trust200902" docName="draft-ietf-netconf-trust-anchors-28" number="9641" updates="" obsoletes="" tocInclude="true" symRefs="true" sortRefs="true"version="3"> <!-- xml2rfc v2v3 conversion 3.17.4 -->version="3" xml:lang="en"> <front><title>A<title abbrev="A YANG Data Model for a Truststore">A YANG Data Model for a Truststore</title> <seriesInfoname="Internet-Draft" value="draft-ietf-netconf-trust-anchors-28"/>name="RFC" value="9641"/> <author initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> <address> <email>kent+ietf@watsen.net</email> </address> </author><date/> <area>Operations</area> <workgroup>NETCONF Working Group</workgroup><date year="2024" month="October"/> <area>OPS</area> <workgroup>netconf</workgroup> <keyword>IETF</keyword> <abstract> <t>This document presents a YANG module for configuring bags of certificates and bags of public keys that can be referenced by other data models for trust. Notifications are sent when certificates are about to expire.</t> </abstract><note> <name>Editorial Note (To be removed by RFC Editor)</name> <t>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.</t> <t>Artwork in this document contains shorthand references to drafts in progress. Please apply the following replacements: </t> <ul spacing="normal"> <li> <tt>AAAA</tt> --> the assigned RFC value for draft-ietf-netconf-crypto-types</li> <li> <tt>BBBB</tt> --> the assigned RFC value for this draft</li> </ul> <t>Artwork in this document contains placeholder values for the date of publication of this draft. Please apply the following replacement: </t> <ul spacing="normal"> <li> <tt>2024-03-16</tt> --> the publication date of this draft</li> </ul> <t>The "Relation to other RFCs" section <xref target="collective-effort"/> contains the text "one or more YANG modules" and, later, "modules". This text is sourced from a file in a context where it is unknown how many modules a draft defines. The text is not wrong as is, but it may be improved by stating more directly how many modules are defined.</t> <t>The "Relation to other RFCs" section <xref target="collective-effort"/> contains a self-reference to this draft, along with a corresponding reference in the Appendix. Please replace the self-reference in this section with "This RFC" (or similar) and remove the self-reference in the "Normative/Informative References" section, whichever it is in.</t> <t>Tree-diagrams in this draft may use the '\' line-folding mode defined in RFC 8792. However, nicer-to-the-eye is when the '\\' line-folding mode is used. The AD suggested suggested putting a request here for the RFC Editor to help convert "ugly" '\' folded examples to use the '\\' folding mode. "Help convert" may be interpreted as, identify what looks ugly and ask the authors to make the adjustment.</t> <t>The following Appendix section is to be removed prior to publication: </t> <ul spacing="normal"> <li> <xref target="change-log"/>. Change Log</li> </ul> </note></front> <middle> <section> <name>Introduction</name> <t>This document presents a YANG 1.1 <xref target="RFC7950"/> modulehavingthat has the following characteristics: </t> <ulempty="true"spacing="normal"> <li>Provide a central truststore for storing raw public keys and/or certificates.</li> <li>Provide support for storing named bags of raw public keys and/or named bags of certificates.</li> <li>Provide types that can be used to reference raw public keys or certificates stored in the central truststore.</li> <li>Provide groupings that enable raw public keys and certificates to be configured inline or as references to truststore instances.</li> <li>Enable the truststore to be instantiated in other data models, in addition to or in lieu of the central truststore instance.</li> </ul> <section anchor="collective-effort"> <name>Relation tootherOther RFCs</name> <t>This document presentsone or morea YANGmodulesmodule <xref target="RFC7950"/> thatareis part of a collection of RFCs that work togetherto, ultimately,to ultimately support the configuration of both the clients and servers of both theNETCONFNetwork Configuration Protocol (NETCONF) <xref target="RFC6241"/> and RESTCONF <xreftarget="RFC8040"/> protocols.</t>target="RFC8040"/>.</t> <t> The dependency relationship between the primary YANG groupings defined in the various RFCs is presented in the below diagram. In some cases, adraftdocument may define secondary groupings that introduce dependencies not illustrated in the diagram. The labels in the diagram areashorthandnamenames for the definingRFC.RFCs. The citationreferencereferences for shorthandname isnames are provided below the diagram.</t> <t>Please note that the arrows in the diagram point from referencer to referenced. For example, the "crypto-types" RFC does not have any dependencies, whilst the "keystore" RFC depends on the "crypto-types" RFC.</t> <artwork><![CDATA[ crypto-types ^ ^ / \ / \ truststore keystore ^ ^ ^ ^ | +---------+ | | | | | | | +------------+ | tcp-client-server | / | | ^ ^ ssh-client-server | | | | ^ tls-client-server | | | ^ ^ http-client-server | | | | | ^ | | | +-----+ +---------+ | | | | | | | | +-----------|--------|--------------+ | | | | | | | | +-----------+ | | | | | | | | | | | | | | | | | netconf-client-server restconf-client-server ]]></artwork><!-- RFC Editor: is there anyway to flush-left the table in PDF/HTML views? --> <table><table align="left"> <name>Label in Diagram to RFC Mapping</name> <tbody> <tr> <th>Label in Diagram</th><th>Originating RFC</th><th>Reference</th> </tr> <tr> <td>crypto-types</td> <td> <xreftarget="I-D.ietf-netconf-crypto-types"/></td>target="RFC9640"/></td> </tr> <tr> <td>truststore</td> <td><xref target="I-D.ietf-netconf-trust-anchors"/></td>RFC 9641</td> </tr> <tr> <td>keystore</td> <td> <xreftarget="I-D.ietf-netconf-keystore"/></td>target="RFC9642"/></td> </tr> <tr> <td>tcp-client-server</td> <td> <xreftarget="I-D.ietf-netconf-tcp-client-server"/></td>target="RFC9643"/></td> </tr> <tr> <td>ssh-client-server</td> <td> <xreftarget="I-D.ietf-netconf-ssh-client-server"/></td>target="RFC9644"/></td> </tr> <tr> <td>tls-client-server</td> <td> <xreftarget="I-D.ietf-netconf-tls-client-server"/></td>target="RFC9645"/></td> </tr> <tr> <td>http-client-server</td> <td> <xref target="I-D.ietf-netconf-http-client-server"/></td> </tr> <tr> <td>netconf-client-server</td> <td> <xref target="I-D.ietf-netconf-netconf-client-server"/></td> </tr> <tr> <td>restconf-client-server</td> <td> <xref target="I-D.ietf-netconf-restconf-client-server"/></td> </tr> </tbody> </table> </section> <section> <name>Specification Language</name><t>The<t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> </section> <section> <name>Adherence to the NMDA</name> <t>This document is compliant with the Network Management Datastore Architecture (NMDA) <xref target="RFC8342"/>. For instance, trust anchors installed during manufacturing (e.g., fortrustedtrusted, well-knownservices),services) are expected to appear in <operational> (see <xref target="built-ins"/>).</t> </section> <section> <name>Conventions</name> <t>Various examples in this document use "BASE64VALUE=" as a placeholder value for binary data that has been base64 encoded (seeSection 4 in<xreftarget="RFC4648"/>).target="RFC7950" sectionFormat="of" section="9.8"/>). This placeholder value is used because realbase64 encodedbase64-encoded structures are often many lines long and hence distracting to the example being presented.</t> <t> Various examples in this document use the XML <xref target="W3C.REC-xml-20081126"/> encoding. Other encodings, such as JSON <xref target="RFC8259"/>, could alternatively be used.</t> <t>Various examples in this document contain long lines that may be folded, as described in <xref target="RFC8792"/>.</t> <t>This document uses the adjective "central"towith the word "truststore" to refer to the top-level instance of the"truststore-grouping","truststore-grouping" grouping when the "central-truststore-supported" feature is enabled. Please be aware that consuming YANG modulesMAY<bcp14>MAY</bcp14> instantiate the "truststore-grouping" grouping in other locations. All such other instances are not the "central" instance.</t> </section> </section> <section> <name>The "ietf-truststore" Module</name> <t>This section defines a YANG 1.1 <xref target="RFC7950"/> module called "ietf-truststore". A high-level overview of the module is provided in <xref target="truststore-verview"/>. Examples illustrating the module's use are provided in <xreftarget="truststore-examples">Examples</xref>.target="truststore-examples"/> ("Example Usage"). The YANG module itself is defined in <xref target="truststore-yang-module"/>.</t> <section anchor="truststore-verview"> <name>Data Model Overview</name> <t>This section provides an overview of the "ietf-truststore" module in terms of its features, typedefs, groupings, and protocol-accessible nodes.</t> <section anchor="features" toc="exclude"> <name>Features</name> <t>The following diagram lists all the "feature" statements defined in the "ietf-truststore" module:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ Features: +-- central-truststore-supported +-- inline-definitions-supported +-- certificates +-- public-keys]]></artwork> <!--<aside>-->]]></sourcecode> <t>The diagram above uses syntax that is similar to but not defined in <xref target="RFC8340"/>.</t><!--</aside>--></section> <section anchor="typedefs" toc="exclude"> <name>Typedefs</name> <t>The following diagram lists the "typedef" statements defined in the "ietf-truststore" module:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ Typedefs: leafref +-- central-certificate-bag-ref +-- central-certificate-ref +-- central-public-key-bag-ref +-- central-public-key-ref]]></artwork> <!--<aside>-->]]></sourcecode> <t>The diagram above uses syntax that is similar to but not defined in <xref target="RFC8340"/>.</t><!--</aside>--><t>Comments:</t> <ul> <li>All the typedefs defined in the "ietf-truststore" module extend the base "leafref" type defined in <xref target="RFC7950"/>.</li> <li>The leafrefs refer to certificates, public keys, and bags in the centraltruststore,truststore when this module is implemented.</li> <li>These typedefs are providedas an aidto aid consuming modules that import the "ietf-truststore" module.</li> </ul> </section> <section toc="exclude"> <name>Groupings</name> <t>The "ietf-truststore" module defines the following "grouping" statements:</t> <ulspacing="compact">spacing="normal"> <li>central-certificate-ref-grouping</li> <li>central-public-key-ref-grouping</li> <li>inline-or-truststore-certs-grouping</li> <li>inline-or-truststore-public-keys-grouping</li> <li>truststore-grouping</li> </ul> <t>Each of these groupings are presented in the following subsections.</t> <section anchor="central-certificate-ref-grouping"> <name>The "central-certificate-ref-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "central-certificate-ref-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ grouping central-certificate-ref-grouping: +-- certificate-bag? ts:central-certificate-bag-ref | {central-truststore-supported,certificates}? +-- certificate? ts:central-certificate-ref {central-truststore-supported,certificates}?]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "central-certificate-ref-grouping" grouping is provided solely as a convenience to consuming modules that wish to enable the configuration of a reference to a certificate in a certificate-bag in the truststore.</li> <li>The "certificate-bag" leaf uses the "central-certificate-bag-ref" typedef defined in <xref target="typedefs"/>.</li> <li>The "certificate" leaf uses the "central-certificate-ref" typedef defined in <xref target="typedefs"/>.</li> </ul> </section> <section anchor="central-public-key-ref-grouping"> <name>The "central-public-key-ref-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "central-public-key-ref-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ grouping central-public-key-ref-grouping: +-- public-key-bag? ts:central-public-key-bag-ref | {central-truststore-supported,public-keys}? +-- public-key? ts:central-public-key-ref {central-truststore-supported,public-keys}?]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "central-public-key-ref-grouping" grouping is provided solely as a convenience to consuming modules that wish to enable the configuration of a reference to a public-key in a public-key-bag in the truststore.</li> <li>The "public-key-bag" leaf uses the"public-key-bag-ref""central-public-key-bag-ref" typedef defined in <xref target="typedefs"/>.</li> <li>The "public-key" leaf uses the"public-key-ref""central-public-key-ref" typedef defined in <xref target="typedefs"/>.</li> </ul> </section> <section anchor="inline-or-truststore-certs-grouping"> <name>The "inline-or-truststore-certs-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "inline-or-truststore-certs-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ grouping inline-or-truststore-certs-grouping: +-- (inline-or-truststore) +--:(inline) {inline-definitions-supported}? | +-- inline-definition | +-- certificate* [name] | +--name?name string | +---u ct:trust-anchor-cert-grouping +--:(central-truststore) {central-truststore-supported,certificates}? +-- central-truststore-reference? ts:central-certificate-bag-ref]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "inline-or-truststore-certs-grouping" grouping is provided solely as a convenience to consuming modules that wish to offer an option whether a bag of certificates can be defined inline or as a reference to a bag in the truststore.</li> <li>A "choice" statement is used to expose the various options. Each option is enabled by a "feature" statement. Additional "case" statementsMAY<bcp14>MAY</bcp14> be augmented in if, e.g., there is a need to reference a bag in an alternate location.</li> <li>For the "inline-definition" option, the "certificate" node uses the "trust-anchor-cert-grouping" grouping discussed in <xrefsection="2.1.4.7" target="I-D.ietf-netconf-crypto-types"/>.</li>section="2.1.4.8" sectionFormat="of" target="RFC9640"/>.</li> <li>For the "central-truststore" option, the "central-truststore-reference" node is an instance of the"certificate-bag-ref""central-certificate-bag-ref" discussed in <xref target="typedefs"/>.</li> </ul> </section> <section anchor="inline-or-truststore-public-keys-grouping"> <name>The "inline-or-truststore-public-keys-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "inline-or-truststore-public-keys-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ grouping inline-or-truststore-public-keys-grouping: +-- (inline-or-truststore) +--:(inline) {inline-definitions-supported}? | +-- inline-definition | +-- public-key* [name] | +--name?name string | +---u ct:public-key-grouping +--:(central-truststore) {central-truststore-supported,public-keys}? +-- central-truststore-reference? ts:central-public-key-bag-ref]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "inline-or-truststore-public-keys-grouping" grouping is provided solely as a convenience to consuming modules that wish to offer an option whether a bag of public keys can be defined inline or as a reference to a bag in the truststore.</li> <li>A "choice" statement is used to expose the various options. Each option is enabled by a "feature" statement. Additional "case" statementsMAY<bcp14>MAY</bcp14> be augmented in if, e.g., there is a need to reference a bag in an alternate location.</li> <li>For the "inline-definition" option, the "public-key" node uses the "public-key-grouping" grouping discussed in <xref section="2.1.4.4"target="I-D.ietf-netconf-crypto-types"/>.</li>sectionFormat="of" target="RFC9640"/>.</li> <li>For the "central-truststore" option, the "central-truststore-reference" is an instance of the "certificate-bag-ref" discussed in <xref target="typedefs"/>.</li> </ul> </section> <section anchor="truststore-grouping"> <name>The "truststore-grouping" Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the "truststore-grouping" grouping:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ grouping truststore-grouping: +-- certificate-bags {certificates}? | +-- certificate-bag* [name] | +--name?name string | +-- description? string | +-- certificate* [name] | +--name?name string | +---u ct:trust-anchor-cert-grouping +-- public-key-bags {public-keys}? +-- public-key-bag* [name] +--name?name string +-- description? string +-- public-key* [name] +--name?name string +---u ct:public-key-grouping]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>The "truststore-grouping" grouping defines a truststore instance as being composed of certificates and/or public keys, both of which are enabled by "feature" statements. Thestructurestructures supporting certificates and public keysisare essentially the same, having an outer list of "bags" containing an inner list of objects(certificates(i.e., certificates or public keys). The bags enable trust anchors serving a common purpose to be grouped and referenced together.</li> <li>For certificates, each certificate is defined by the "trust-anchor-cert-grouping" grouping<xref section="2.1.4.7" target="I-D.ietf-netconf-crypto-types"/>.(<xref section="2.1.4.8" sectionFormat="of" target="RFC9640"/>). The "cert-data" node is aCMSCryptographic Message Syntax (CMS) structure that can be composed of a chain of one or more certificates. Additionally, the "certificate-expiration" notification enables the server to alert clients when certificates are nearing expiration or have already expired.</li> <li>For public keys, each public key is defined by the "public-key-grouping" grouping<xref(<xref section="2.1.4.4"target="I-D.ietf-netconf-crypto-types"/>.sectionFormat="of" target="RFC9640"/>). The "public-key" node can be one of any number of structures specified by the "public-key-format" identity node.</li> </ul> </section> </section> <section anchor="proto-access-nodes" toc="exclude"><name>Protocol-accessible<name>Protocol-Accessible Nodes</name> <t>The following tree diagram <xref target="RFC8340"/> lists all the protocol-accessible nodes defined in the "ietf-truststore"module,module without expanding the "grouping" statements:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ module: ietf-truststore +--rw truststore {central-truststore-supported}? +---u truststore-grouping]]></artwork>]]></sourcecode> <t>The following tree diagram <xref target="RFC8340"/> lists all the protocol-accessible nodes defined in the "ietf-truststore"module,module with all "grouping" statements expanded, enabling the truststore's full structure to be seen:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ module: ietf-truststore +--rw truststore {central-truststore-supported}? +--rw certificate-bags {certificates}? | +--rw certificate-bag* [name] | +--rw name string | +--rw description? string | +--rw certificate* [name] | +--rw name string | +--rw cert-data trust-anchor-cert-cms | +---n certificate-expiration | {certificate-expiration-notification}? | +-- 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]]></artwork>]]></sourcecode> <t>Comments:</t> <ul> <li>Protocol-accessible nodes are those nodes that are accessible when the module is "implemented", as described in <xref section="5.6.5" sectionFormat="of" target="RFC7950"/>.</li> <li>The protocol-accessible nodes for the "ietf-truststore" module arean instanceinstances of the "truststore-grouping" grouping discussed in <xref target="truststore-grouping"/>.</li> <li>The top-levelnode"truststore" node is additionally constrained by thefeature "central-truststore-supported".</li>"central-truststore-supported" feature.</li> <li>The "truststore-grouping" grouping is discussed in <xref target="truststore-grouping"/>.</li> <li>The reason for why the "truststore-grouping" grouping exists separate from the protocol-accessible nodes definition is to enable instances of the truststore to be instantiated in other locations, as may be needed or desired by some modules.</li> </ul> </section> </section> <section anchor="truststore-examples"> <name>Example Usage</name> <t>The examples in this section are encoded using XML, such as might be the case when using the NETCONF protocol. Other encodingsMAY<bcp14>MAY</bcp14> be used, such as JSON when using the RESTCONF protocol.</t> <section anchor="ts-inst" toc="exclude"> <name>A Truststore Instance</name> <t>This section presents an example illustrating trust anchors in <intended>, as per <xref target="proto-access-nodes"/>. Please see <xref target="built-ins"/> for an example illustrating built-in values in <operational>.</t> <t>The example contained in this section defines eight bags of trust anchors. There are four certificate-based bags and fourpublic key basedpublic-key-based bags. The following diagram provides an overview of the contents in the example:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ Certificate Bags +-- Trust anchor certs for authenticating a set of remote servers +-- End entity certs for authenticating a set of remote servers +-- Trust anchor certs for authenticating a set of remote clients +-- End entity certs for authenticating a set of remote clients Public Key Bags +-- SSH keys to authenticate a set of remote SSHserverservers +-- SSH keys to authenticate a set of remote SSH clients +-- Raw public keys to authenticate a set of remote SSHserverservers +-- Raw public keys to authenticate a set of remote SSH clients]]></artwork> <t>Following is the full example:</t> <artwork><![CDATA[]]></sourcecode> <sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <truststore xmlns="urn:ietf:params:xml:ns:yang:ietf-truststore" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> <!-- A bag of Certificate Bags --> <certificate-bags> <!-- Trust Anchor Certs for Authenticating Servers --> <certificate-bag> <name>trusted-server-ca-certs</name> <description> Trust anchors(i.e.(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. </description> <certificate> <name>Server Cert Issuer #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Server Cert Issuer #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> <!-- End Entity Certs for Authenticating Servers --> <certificate-bag> <name>trusted-server-ee-certs</name> <description> Specific end-entity certificates used to authenticate server certificates. A server certificate is authenticated if its end-entity certificate is an exact match to one of these certificates. </description> <certificate> <name>My Application #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>My Application #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> <!-- Trust Anchor Certs for Authenticating Clients --> <certificate-bag> <name>trusted-client-ca-certs</name> <description> Trust anchors(i.e.(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. </description> <certificate> <name>Client Identity Issuer #1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Client Identity Issuer #2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> <!-- End Entity Certs for Authenticating Clients --> <certificate-bag> <name>trusted-client-ee-certs</name> <description> 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. </description> <certificate> <name>George Jetson</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Fred Flintstone</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> </certificate-bags> <!-- A List of Public Key Bags --> <public-key-bags> <!-- Public Keys for Authenticating SSH Servers --> <public-key-bag> <name>trusted-ssh-public-keys</name> <description> 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. </description> <public-key> <name>corp-fw1</name> <public-key-format>ct:ssh-public-key-format</public-key-form\ at> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>corp-fw2</name> <public-key-format>ct:ssh-public-key-format</public-key-form\ at> <public-key>BASE64VALUE=</public-key> </public-key> </public-key-bag> <!-- SSH Public Keys for Authenticating Application A --> <public-key-bag> <name>SSH Public Keys for Application A</name> <description> SSH public keys used to authenticate application A's SSH public keys. An SSH public key is authenticated if it is an exact match to one of these public keys. </description> <public-key> <name>Application Instance #1</name> <public-key-format>ct:ssh-public-key-format</public-key-form\ at> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>Application Instance #2</name> <public-key-format>ct:ssh-public-key-format</public-key-form\ at> <public-key>BASE64VALUE=</public-key> </public-key> </public-key-bag> <!-- Raw Public Keys for TLS Servers --> <public-key-bag> <name>Raw Public Keys for TLS Servers</name> <public-key> <name>Raw Public Key #1</name> <public-key-format>ct:subject-public-key-info-format</public\ -key-format> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>Raw Public Key #2</name> <public-key-format>ct:subject-public-key-info-format</public\ -key-format> <public-key>BASE64VALUE=</public-key> </public-key> </public-key-bag> <!-- Raw Public Keys for TLS Clients --> <public-key-bag> <name>Raw Public Keys for TLS Clients</name> <public-key> <name>Raw Public Key #1</name> <public-key-format>ct:subject-public-key-info-format</public\ -key-format> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>Raw Public Key #2</name> <public-key-format>ct:subject-public-key-info-format</public\ -key-format> <public-key>BASE64VALUE=</public-key> </public-key> </public-key-bag> </public-key-bags> </truststore>]]></artwork>]]></sourcecode> </section> <section toc="exclude"> <name>A Certificate Expiration Notification</name> <t>The following example illustrates the "certificate-expiration" notification (per <xrefsection="2.1.4.6" target="I-D.ietf-netconf-crypto-types"/>)section="2.1.4.7" sectionFormat="of" target="RFC9640"/>) for a certificate configured in the truststore described in <xref target="ts-inst"/>.</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> <eventTime>2018-05-25T00:01:00Z</eventTime> <truststore xmlns="urn:ietf:params:xml:ns:yang:ietf-truststore"> <certificate-bags> <certificate-bag> <name>trusted-client-ee-certs</name> <certificate> <name>George Jetson</name> <certificate-expiration> <expiration-date>2024-01-05T14:18:53-05:00</expiration-d\ ate> </certificate-expiration> </certificate> </certificate-bag> </certificate-bags> </truststore> </notification>]]></artwork>]]></sourcecode> </section> <section toc="exclude"> <name>The"Local"Inline or Truststore" Groupings</name> <t>This section illustrates the various "inline-or-truststore" groupings defined in the "ietf-truststore" module, specifically the "inline-or-truststore-certs-grouping" (<xref target="inline-or-truststore-certs-grouping"/>) and "inline-or-truststore-public-keys-grouping" (<xref target="inline-or-truststore-public-keys-grouping"/>) groupings.</t> <t>These examples assume the existence of an example module called "ex-truststore-usage"havingthat has the namespace "https://example.com/ns/example-truststore-usage".</t> <t>Theex-truststore-usage"ex-truststore-usage" module is first presented using tree diagrams <xref target="RFC8340"/>, followed by an instance example illustrating all the "inline-or-truststore" groupings in use, followed by the YANG module itself.</t> <t>The following tree diagram illustrates the "ex-truststore-usage" module without expanding the "grouping" statements:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ module: ex-truststore-usage +--rw truststore-usage +--rw cert* [name] | +--rw name string | +---u ts:inline-or-truststore-certs-grouping +--rw public-key* [name] +--rw name string +---u ts:inline-or-truststore-public-keys-grouping]]></artwork>]]></sourcecode> <t>The following tree diagram illustrates the "ex-truststore-usage"module,module with all "grouping" statements expanded, enabling the truststore's full structure to be seen:</t><artwork><![CDATA[<sourcecode type="yangtree"><![CDATA[ module: ex-truststore-usage +--rw truststore-usage +--rw cert* [name] | +--rw name string | +--rw (inline-or-truststore) | +--:(inline) {inline-definitions-supported}? | | +--rw inline-definition | | +--rw certificate* [name] | | +--rw name string | | +--rw cert-data | | | trust-anchor-cert-cms | | +---n certificate-expiration | | {certificate-expiration-notification}? | | +-- expiration-date yang:date-and-time | +--:(central-truststore) | {central-truststore-supported,certificates}? | +--rw central-truststore-reference? | ts:central-certificate-bag-ref +--rw public-key* [name] +--rw name string +--rw (inline-or-truststore) +--:(inline) {inline-definitions-supported}? | +--rw inline-definition | +--rw public-key* [name] | +--rw name string | +--rw public-key-format identityref | +--rw public-key binary +--:(central-truststore) {central-truststore-supported,public-keys}? +--rw central-truststore-reference? ts:central-public-key-bag-ref]]></artwork>]]></sourcecode> <t>The following example provides two equivalent instances of each grouping, the first being a reference to a truststore and the second being defined inline. The instance having a reference to a truststore is consistent with the truststore defined in <xref target="ts-inst"/>. The two instances are equivalent, as the inlined instance example contains the same values defined by the truststore instance referenced by its sibling example.</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ =============== NOTE: '\' line wrapping per RFC 8792 ================ <truststore-usage xmlns="https://example.com/ns/example-truststore-usage" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> <!-- The following two equivalent examples illustrate --> <!-- the "inline-or-truststore-certs-grouping" grouping: --> <cert> <name>example 1a</name> <central-truststore-reference>trusted-client-ca-certs</central-t\ ruststore-reference> </cert> <cert> <name>example 1b</name> <inline-definition><name>my-trusted-client-ca-certs</name><certificate> <name>Client Identity Issuer #1</name><cert>BASE64VALUE=</cert><cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Client Identity Issuer #2</name><cert>BASE64VALUE=</cert><cert-data>BASE64VALUE=</cert-data> </certificate> </inline-definition> </cert> <!-- The following two equivalent examples illustrate the --> <!-- "inline-or-truststore-public-keys-grouping" grouping: --> <public-key> <name>example 2a</name> <central-truststore-reference>trusted-ssh-public-keys</central-t\ ruststore-reference> </public-key> <public-key> <name>example 2b</name> <inline-definition><name>trusted-ssh-public-keys</name><public-key> <name>corp-fw1</name><public-key-format> ct:ssh-public-key-format </public-key-format><public-key-format>ct:ssh-public-key-format</public-key-form\ at> <public-key>BASE64VALUE=</public-key> </public-key> <public-key> <name>corp-fw2</name><public-key-format> ct:ssh-public-key-format </public-key-format><public-key-format>ct:ssh-public-key-format</public-key-form\ at> <public-key>BASE64VALUE=</public-key> </public-key> </inline-definition> </public-key> </truststore-usage>]]></artwork>]]></sourcecode> <t>Following is the "ex-truststore-usage" module's YANG definition:</t><artwork><![CDATA[<sourcecode type="yang"><![CDATA[ module ex-truststore-usage { yang-version 1.1; namespace "https://example.com/ns/example-truststore-usage"; prefix etu; import ietf-truststore { prefix ts; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; } organization "Example Corporation"; contact "Author: YANG Designer <mailto:yang.designer@example.com>"; description "This example module illustrates notable groupings defined in the 'ietf-truststore' module."; revision 2024-03-16 { description "Initialversion";version."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; } container truststore-usage { description "An illustration of the various truststore groupings."; list cert { key "name"; leaf name { type string; description "An arbitrary name for this cert."; } uses ts:inline-or-truststore-certs-grouping; description "A cert that may be configured locally or be a reference to a cert in the truststore."; } list public-key { key "name"; leaf name { type string; description "An arbitrary name for this cert."; } uses ts:inline-or-truststore-public-keys-grouping; description "A public key that may be configured locally or be a reference to a public key in the truststore."; } } }]]></artwork>]]></sourcecode> </section> </section> <section anchor="truststore-yang-module"> <name>YANG Module</name> <t>This YANG module imports modules from <xref target="RFC8341"/> and <xreftarget="I-D.ietf-netconf-crypto-types"/>.</t> <t keepWithNext="true"><CODE BEGINS> file "ietf-truststore@2024-03-16.yang"</t> <artwork><![CDATA[target="RFC9640"/>.</t> <sourcecode type="yang" name="ietf-truststore@2024-03-16.yang" markers="true"><![CDATA[ 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 "RFCAAAA:9640: YANG Data Types and Groupings for Cryptography"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WGWeb :Web: https://datatracker.ietf.org/wg/netconf WGList :List: NETCONF WG list <mailto:netconf@ietf.org>Author :Author: Kent Watsen <kent+ietf@watsen.net>"; description "This module defines a 'truststore' to centralize management of trustanchorsanchors, including certificates and public keys. 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. Copyright (c) 2024 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 Revised 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 RFCBBBB (https://www.rfc-editor.org/info/rfcBBBB);9641 (https://www.rfc-editor.org/info/rfc9641); see the RFC itself for full legalnotices. 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.";notices."; revision 2024-03-16 { description "Initialversion";version."; reference "RFCBBBB:9641: A YANG Data Model for a Truststore"; } /****************/ /* Features */ /****************/ feature central-truststore-supported { description "The 'central-truststore-supported' feature indicates that the server supports the truststore (i.e., implements the 'ietf-truststore' module)."; } feature inline-definitions-supported { description "The 'inline-definitions-supported' feature indicates that the server supportslocally-definedlocally 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 */ /****************/ typedef central-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 in the central truststore."; } typedef central-certificate-ref { type leafref { path "/ts:truststore/ts:certificate-bags/ts:certificate-bag" + "[ts:name = current()/../certificate-bag]/" + "ts:certificate/ts:name"; } description "This typedef defines a reference to a specific certificate in a certificate bag in the central truststore. This typedef requires that there exist a sibling 'leaf' node called 'certificate-bag' that SHOULD have thetypedef 'central-certificate-bag-ref'.";'central-certificate-bag-ref' typedef."; } typedef central-public-key-bag-ref { type leafref { path "/ts:truststore/ts:public-key-bags/" + "ts:public-key-bag/ts:name"; } description "This typedef defines a reference to a public key bag in the central truststore."; } typedef central-public-key-ref { type leafref { path "/ts:truststore/ts:public-key-bags/ts:public-key-bag" + "[ts:name = current()/../public-key-bag]/" + "ts:public-key/ts:name"; } description "This typedef defines a reference to a specific public key in a public key bag in the truststore. This typedef requires that there exist a sibling 'leaf' node called 'public-key-bag'thatSHOULD have thetypedef 'central-public-key-bag-ref'.";'central-public-key-bag-ref' typedef."; } /*****************/ /* Groupings */ /*****************/ // *-ref groupings grouping central-certificate-ref-grouping { description "Grouping for the reference to a certificate in a certificate-bag in the central truststore."; leaf certificate-bag { nacm:default-deny-write; if-feature "central-truststore-supported"; if-feature "certificates"; type ts:central-certificate-bag-ref; must"../certificate";'../certificate'; description "Reference to a certificate-bag in the truststore."; } leaf certificate { nacm:default-deny-write; if-feature "central-truststore-supported"; if-feature "certificates"; type ts:central-certificate-ref; must"../certificate-bag";'../certificate-bag'; description "Reference to a specific certificate in the referenced certificate-bag."; } } grouping central-public-key-ref-grouping { description "Grouping for the reference to a public key in a public-key-bag in the central truststore."; leaf public-key-bag { nacm:default-deny-write; if-feature "central-truststore-supported"; if-feature "public-keys"; type ts:central-public-key-bag-ref; description "Reference of a public key bag in thetruststoretruststore, including the certificate to authenticate the TLS client."; } leaf public-key { nacm:default-deny-write; if-feature "central-truststore-supported"; if-feature "public-keys"; type ts:central-public-key-ref; description "Reference to a specific public key in the referenced public-key-bag."; } } // inline-or-truststore-* groupings grouping inline-or-truststore-certs-grouping { description "A grouping for the configuration of a list of certificates. The list ofcertificatecertificates may be defined inline or as a reference to a certificate bag in the central truststore. Servers that wish to define alternate truststore locations MUST augment in custom 'case'statementsstatements, enabling references to those alternate truststore locations."; choice inline-or-truststore { nacm:default-deny-write; mandatory true; description "A choice between an inlined definition and a definition that exists in the truststore."; case inline { if-feature "inline-definitions-supported"; container inline-definition { description "A container for locally configured trust anchor certificates."; list certificate { key "name"; min-elements 1; description "A trust anchor certificate or chain of certificates."; leaf name { type string; description "An arbitrary name for this certificate."; } uses ct:trust-anchor-cert-grouping { refine "cert-data" { mandatory true; } } } } } case central-truststore { if-feature "central-truststore-supported"; if-feature "certificates"; leaf central-truststore-reference { type ts:central-certificate-bag-ref; description "A reference to a certificate bag that exists in the central truststore."; } } } } grouping inline-or-truststore-public-keys-grouping { description "A grouping that allows the public keys tobeeither be configured locally, within theusingdatamodel,model being used, or be a reference to a public key bag stored in the truststore. Servers that wish to define alternate truststore locations SHOULD augment in custom 'case'statementsstatement, enabling references to those alternate truststore locations."; choice inline-or-truststore { nacm:default-deny-write; mandatory true; description "A choice between an inlined definition and a definition that exists in the truststore."; case inline { if-feature "inline-definitions-supported"; container inline-definition { description "A 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 central-truststore { if-feature "central-truststore-supported"; if-feature "public-keys"; leaf central-truststore-reference { type ts:central-public-key-bag-ref; description "A reference to a bag of public keys that exists in the central truststore."; } } } } // the truststore grouping grouping truststore-grouping { description "A grouping definition that enables use in other contexts. Where used, implementations MUST augment new 'case' statements into the various inline-or-truststore 'choice' statements to supply leafrefs to the model-specific location(s)."; container certificate-bags { nacm:default-deny-write; if-feature "certificates"; description "A collection of certificate bags."; list certificate-bag { key "name"; description "A bag of certificates. Each bag of certificates should be for a specific purpose. For instance, one bag could 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"; description "A trust anchor certificate or chain of certificates."; leaf name { type string; description "An arbitrary name for this certificate."; } uses ct:trust-anchor-cert-grouping { refine "cert-data" { mandatory true; } } } } } container public-key-bags { nacm:default-deny-write; if-feature "public-keys"; description "A collection of public key bags."; list public-key-bag { key "name"; description "A bag of public keys. Each bag of keys SHOULD be for a specific purpose. For instance, one bag could 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 public keys."; } leaf description { type string; description "A description for this bag of public keys. The intended purpose for the bag MUST be described."; } list public-key { key "name"; description "A public key."; leaf name { type string; description "An arbitrary name for this public key."; } uses ct:public-key-grouping; } } } } /*********************************/ /*Protocol accessibleProtocol-accessible nodes */ /*********************************/ container truststore { if-featurecentral-truststore-supported;"central-truststore-supported"; nacm:default-deny-write; description "The truststore contains bags of certificates and public keys."; uses truststore-grouping; } }]]></artwork> <t keepWithPrevious="true"><CODE ENDS></t>]]></sourcecode> </section> </section> <section anchor="built-ins"> <name>Support forBuilt-inBuilt-In Trust Anchors</name> <t>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 SZTPa Secure Zero-Touch Provisioning (SZTP) <xref target="RFC8572"/> bootstrap server) or publicCACertification Authority (CA) certificates to connect to arbitraryWebweb services usingpublicPKI.</t> <t>Built-in trust anchors are expected to be set by a vendor-specific process. Any ability for operators to set and/or modify built-in trust anchors is outside the scope of this document.</t> <t>The primary characteristic of the built-in trust anchors is that they are provided by the server, as opposed to configuration. As such, they are present in <operational> (<xref section="5.3"target="RFC8342"/>),sectionFormat="of" target="RFC8342"/>) and <system> <xref target="I-D.ietf-netmod-system-config"/>, if implemented.</t> <t>The example below illustrates what the truststore in <operational> might look like for a server in its factory default state. Note that the built-in trust anchor bags have the "or:origin" annotation value "or:system".</t><artwork><![CDATA[<sourcecode type="xml"><![CDATA[ <truststore xmlns="urn:ietf:params:xml:ns:yang:ietf-truststore" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types" xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin" or:origin="or:intended"> <certificate-bags> <certificate-bag or:origin="or:system"> <name>Built-In Manufacturer Trust Anchor Certificates</name> <description> Certificates built into the device for authenticating manufacturer-signed objects, such as TLS server certificates, vouchers, etc. </description> <certificate> <name>Manufacturer Root CA Cert</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> <certificate-bag or:origin="or:system"> <name>Built-In Public Trust Anchor Certificates</name> <description> Certificates built into the device for authenticating certificates issued by public certificate authorities, such as the end-entity certificate for web servers. </description> <certificate> <name>Public Root CA Cert 1</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Public Root CA Cert 2</name> <cert-data>BASE64VALUE=</cert-data> </certificate> <certificate> <name>Public Root CA Cert 3</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> </certificate-bags> </truststore>]]></artwork> <!-- <t>Built-in bags of trust anchors and/or specific trust anchors, that are referenced by configuration (e.g., a "leafref"), MUST be present in a datastore in order for the datastore to be valid.</t> <t>Built-in bags and/or their trust anchors MAY be copied into other parts of the configuration but, by doing so, they lose their association to the built-in entries and any assurances afforded by knowing they are/were built-in.</t> <t>The following example illustrates how a single built-in public CA certificate from the previous example has been propagated to <intended>:</t> <t> <figure> <artwork><![CDATA[ <truststore xmlns="urn:ietf:params:xml:ns:yang:ietf-truststore" xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> <certificate-bags> <certificate-bag> <name>Built-In Public Trust Anchor Certificates</name> <description> 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. </description> <certificate> <name>Public Root CA Cert 3</name> <cert-data>BASE64VALUE=</cert-data> </certificate> </certificate-bag> </certificate-bags> </truststore> ]]></artwork> </figure> </t> -->]]></sourcecode> </section> <section> <name>Security Considerations</name> <section> <name>Security of Data at Rest</name> <t>The YANG moduledefinedspecified in this document defines a mechanism called a "truststore" that, by its name, suggests that its contents are protected from unauthorized modification.</t> <t>Security controls for the API (i.e., data in motion) are discussed in <xref target="sec-mod"/>, but controls for the data at rest (e.g., on disk) cannot be specified by the YANG module.</t> <t>In order to satisfy the expectations of a "truststore", server implementationsMUST<bcp14>MUST</bcp14> ensure that the truststore contents are protected from unauthorized modifications when at rest.</t> </section> <section> <name>Unconstrained Public Key Usage</name> <t>This module enables the configuration of public keys without constraints on their usage, e.g., what operations the key is allowed to be used for (encryption, verification, or both).</t> <t>Trust anchors configured via this module are implicitly trusted to validate certification paths that may include any name, be used for any purpose, or be subject to constraints imposed by an intermediate CA or by context in which the truststore is used. Implementations are free to use alternative or auxiliary structures and validation rules to define constraints that limit the applicability of a trust anchor.</t> </section> <section anchor="sec-mod"> <name>Considerations for the "ietf-truststore" YANG Module</name> <t>This sectionfollowsis modeled after the template defined in <xref section="3.7.1" sectionFormat="of" target="RFC8407"/>.</t> <t>The "ietf-truststore" YANG moduledefined in this document isdefines "grouping" and "container" statements that are designed to be accessed viaYANG basedYANG-based management protocols, such as NETCONF <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>.Both of theseThese protocols have mandatory-to-implement secure transport layers (e.g.,SSH, TLS) withSecure Shell (SSH) <xref target="RFC4252"/>, TLS <xref target="RFC8446"/>, and QUIC <xref target="RFC9000"/>) and mandatory-to-implement mutual authentication.</t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular users to apre-configuredpreconfigured subset of all available protocol operations and content.</t> <t>Please be aware that this YANG module uses groupings from other YANG modules that define nodes that may be considered sensitive or vulnerable in network environments. Please review theSecurity Considerationssecurity considerations for dependent YANG modules for information as to which nodes may be considered sensitive or vulnerable in network environments.</t> <t>Most of the readable data nodes defined in this YANG module are not considered sensitive or vulnerable in network environments. However, the "cert-data" node uses the NACM "default-deny-all"extension,extension for reasons described in <xrefsection="3.9" target="I-D.ietf-netconf-crypto-types"/>.</t>section="3.8" sectionFormat="of" target="RFC9640"/>.</t> <t>All the writable data nodes defined by this module, both in the "grouping" statements as well as the protocol-accessible "truststore" instance, may be considered sensitive or vulnerable in some network environments. For instance, any modification to a trust anchor or reference to a trust anchor may dramatically alter the implemented security policy. For this reason, the NACMextension"default-deny-write" extension has been set for all data nodes defined in this module.</t> <t>This module does not define any "rpc" or "action" statements, andthusthus, the security considerations for suchisare not provided here.</t> </section> </section> <section> <name>IANA Considerations</name> <section> <name>The"IETF XML"IETF XML Registry</name><t>This document registers one<t>IANA has registered the following URI in the "ns"subregistryregistry defined of theIETF"IETF XMLRegistryRegistry" <xreftarget="RFC3688"/>. Following the format in <xref target="RFC3688"/>, the following registration is requested:</t> <artwork><![CDATA[ URI: urn:ietf:params:xml:ns:yang:ietf-truststore Registrant Contact: The IESG XML: N/A,target="RFC3688"/>.</t> <dl newline="false" spacing="compact"> <dt>URI:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-truststore</dd> <dt>Registrant Contact:</dt> <dd>The IESG</dd> <dt>XML:</dt> <dd>N/A; the requested URI is an XMLnamespace. ]]></artwork>namespace.</dd> </dl> </section> <section> <name>The"YANGYANG ModuleNames"Names Registry</name><t>This document registers one<t>IANA has registered the following YANG module in theYANG"YANG ModuleNamesNames" registry<xref target="RFC6020"/>. Following the formatdefined in <xreftarget="RFC6020"/>, the following registration is requested:</t> <artwork><![CDATA[ name: ietf-truststore namespace: urn:ietf:params:xml:ns:yang:ietf-truststore prefix: ts reference: RFC BBBB ]]></artwork>target="RFC6020"/>.</t> <dl newline="false" spacing="compact"> <dt>Name:</dt> <dd>ietf-truststore</dd> <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-truststore</dd> <dt>Prefix:</dt> <dd>ts</dd> <dt>Reference:</dt> <dd>RFC 9641</dd> </dl> </section> </section> </middle> <back> <displayreference target="I-D.ietf-netconf-http-client-server" to="HTTP-CLIENT-SERVER"/> <displayreference target="I-D.ietf-netconf-netconf-client-server" to="NETCONF-CLIENT-SERVER"/> <displayreference target="I-D.ietf-netconf-restconf-client-server" to="RESTCONF-CLIENT-SERVER"/> <displayreference target="I-D.ietf-netmod-system-config" to="NETMOD-SYSTEM-CONFIG"/> <references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4252.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9000.xml"/> <referenceanchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <front> <title>Key words for use in RFCs to Indicate Requirement Levels</title> <author fullname="S. Bradner" initials="S." surname="Bradner"/> <date month="March" year="1997"/> <abstract> <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/> </reference> <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml">anchor="RFC9640" target="https://www.rfc-editor.org/info/rfc9640"> <front><title>The YANG 1.1<title>YANG DataModeling Language</title> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <date month="August" year="2016"/> <abstract> <t>YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls,Types andnotificationsGroupings fornetwork management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t> </abstract> </front> <seriesInfo name="RFC" value="7950"/> <seriesInfo name="DOI" value="10.17487/RFC7950"/> </reference> <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <front> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title> <author fullname="B. Leiba" initials="B." surname="Leiba"/> <date month="May" year="2017"/> <abstract> <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t> </abstract> </front> <seriesInfo name="BCP" value="14"/> <seriesInfo name="RFC" value="8174"/> <seriesInfo name="DOI" value="10.17487/RFC8174"/> </reference> <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"> <front> <title>Network Configuration Access Control Model</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/>Cryptography</title> <authorfullname="M. Bjorklund" initials="M." surname="Bjorklund"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <datemonth="March" year="2018"/> <abstract> <t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t> <t>This document obsoletes RFC 6536.</t> </abstract>month="October" year="2024"/> </front> <seriesInfoname="STD" value="91"/> <seriesInfoname="RFC"value="8341"/>value="9640"/> <seriesInfo name="DOI"value="10.17487/RFC8341"/>value="10.17487/RFC9640"/> </reference><xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-crypto-types.xml"/></references> <references> <name>Informative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8572.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8792.xml"/> <referenceanchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"> <front> <title>The IETF XML Registry</title> <author fullname="M. Mealling" initials="M." surname="Mealling"/> <date month="January" year="2004"/> <abstract> <t>This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t> </abstract> </front> <seriesInfo name="BCP" value="81"/> <seriesInfo name="RFC" value="3688"/> <seriesInfo name="DOI" value="10.17487/RFC3688"/> </reference> <reference anchor="RFC4648" target="https://www.rfc-editor.org/info/rfc4648" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml">anchor="RFC9642" target="https://www.rfc-editor.org/info/rfc9642"> <front><title>The Base16, Base32, and Base64<title>A YANG DataEncodings</title>Model for a Keystore</title> <authorfullname="S. Josefsson" initials="S." surname="Josefsson"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <date month="October"year="2006"/> <abstract> <t>This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds in encoded data, use of padding in encoded data, use of non-alphabet characters in encoded data, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK]</t> </abstract>year="2024"/> </front> <seriesInfo name="RFC"value="4648"/>value="9642"/> <seriesInfo name="DOI"value="10.17487/RFC4648"/>value="10.17487/RFC9642"/> </reference> <referenceanchor="RFC6020" target="https://www.rfc-editor.org/info/rfc6020" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml">anchor="RFC9643" target="https://www.rfc-editor.org/info/rfc9643"> <front> <title>YANG- A Data Modeling LanguageGroupings forthe Network Configuration Protocol (NETCONF)</title> <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/> <date month="October" year="2010"/> <abstract> <t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls,TCP Clients andNETCONF notifications. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6020"/> <seriesInfo name="DOI" value="10.17487/RFC6020"/> </reference> <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"> <front> <title>Network Configuration Protocol (NETCONF)</title>TCP Servers</title> <authorfullname="R. Enns" initials="R." role="editor" surname="Enns"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <authorfullname="M. Bjorklund"initials="M."role="editor" surname="Bjorklund"/> <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/> <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/> <date month="June" year="2011"/> <abstract> <t>The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configurationsurname="Scharf" fullname="Michael Scharf"> <organization>Hochschule Esslingen - University ofnetwork devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t> </abstract> </front> <seriesInfo name="RFC" value="6241"/> <seriesInfo name="DOI" value="10.17487/RFC6241"/> </reference> <reference anchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"> <front> <title>RESTCONF Protocol</title> <author fullname="A. Bierman" initials="A." surname="Bierman"/> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="K. Watsen" initials="K." surname="Watsen"/>Applied Sciences</organization> </author> <datemonth="January" year="2017"/> <abstract> <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t> </abstract>month="October" year="2024"/> </front> <seriesInfo name="RFC"value="8040"/>value="9643"/> <seriesInfo name="DOI"value="10.17487/RFC8040"/>value="10.17487/RFC9643"/> </reference> <referenceanchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml">anchor="RFC9644" target="https://www.rfc-editor.org/info/rfc9644"> <front> <title>YANGTree Diagrams</title> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/> <date month="March" year="2018"/> <abstract> <t>This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single locationGroupings forthis definition. This syntax may be updated from time to time based on the evolution of the YANG language.</t> </abstract> </front> <seriesInfo name="BCP" value="215"/> <seriesInfo name="RFC" value="8340"/> <seriesInfo name="DOI" value="10.17487/RFC8340"/> </reference> <reference anchor="RFC8342" target="https://www.rfc-editor.org/info/rfc8342" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"> <front> <title>Network Management Datastore Architecture (NMDA)</title> <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/> <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/> <author fullname="P. Shafer" initials="P." surname="Shafer"/>SSH Clients and SSH Servers</title> <authorfullname="K. Watsen"initials="K."surname="Watsen"/> <author fullname="R. Wilton" initials="R." surname="Wilton"/>surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <datemonth="March" year="2018"/> <abstract> <t>Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.</t> </abstract>month="October" year="2024"/> </front> <seriesInfo name="RFC"value="8342"/>value="9644"/> <seriesInfo name="DOI"value="10.17487/RFC8342"/>value="10.17487/RFC9644"/> </reference> <referenceanchor="RFC8407" target="https://www.rfc-editor.org/info/rfc8407" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8407.xml">anchor="RFC9645" target="https://www.rfc-editor.org/info/rfc9645"> <front><title>Guidelines<title>YANG Groupings forAuthorsTLS Clients andReviewers of Documents Containing YANG Data Models</title>TLS Servers</title> <authorfullname="A. Bierman" initials="A." surname="Bierman"/>initials="K." surname="Watsen" fullname="Kent Watsen"> <organization>Watsen Networks</organization> </author> <date month="October"year="2018"/> <abstract> <t>This memo provides guidelines for authors and reviewers of specifications containing YANG modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 6087.</t> </abstract>year="2024"/> </front> <seriesInfoname="BCP" value="216"/> <seriesInfoname="RFC"value="8407"/>value="9645"/> <seriesInfo name="DOI"value="10.17487/RFC8407"/>value="10.17487/RFC9645"/> </reference> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-http-client-server"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-netconf-client-server"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-restconf-client-server"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netmod-system-config.xml"/> <referenceanchor="RFC8572" target="https://www.rfc-editor.org/info/rfc8572" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8572.xml">anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/REC-xml-20081126/"> <front><title>Secure Zero Touch Provisioning (SZTP)</title><title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title> <authorfullname="K. Watsen" initials="K." surname="Watsen"/>initials="T." surname="Bray" fullname="Tim Bray"/> <authorfullname="I. Farrer" initials="I." surname="Farrer"/>initials="J." surname="Paoli" fullname="Jean Paoli"/> <authorfullname="M. Abrahamsson" initials="M." surname="Abrahamsson"/>initials="C.M." surname="Sperberg-McQueen" fullname="C. M. Sperberg-McQueen"/> <author initials="E." surname="Maler" fullname="Eve Maler"/> <author initials="F." surname="Yergeau" fullname="François Yergeau"/> <datemonth="April" year="2019"/> <abstract> <t>This document presents a technique to securely provision a networking device when it is booting in a factory-default state. Variations in the solution enable it to be used on both public and private networks. The provisioning steps are able to update the boot image, commit an initial configuration, and execute arbitrary scripts to address auxiliary needs. The updated device is subsequently able to establish secure connections with other systems. For instance, a device may establish NETCONF (RFC 6241) and/or RESTCONF (RFC 8040) connections with deployment-specific network management systems.</t> </abstract>month="November" year="2008"/> </front> <seriesInfoname="RFC" value="8572"/> <seriesInfo name="DOI" value="10.17487/RFC8572"/>name="World Wide Web Consortium Recommendation" value="REC-xml-20081126"/> </reference><xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-trust-anchors.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-keystore.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-tcp-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-ssh-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-tls-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-http-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-netconf-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-restconf-client-server.xml"/> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netmod-system-config.xml"/></references> </references> <sectionanchor="change-log"> <name>Change Log</name> <section> <name>00 to 01</name> <ul spacing="normal"> <li>Added features "x509-certificates" and "ssh-host-keys".</li> <li>Added nacm:default-deny-write to "trust-anchors" container.</li> </ul> </section> <section> <name>01 to 02</name> <ul spacing="normal"> <li>Switched "list pinned-certificate" to use the "trust-anchor-cert-grouping" from crypto-types. Effectively the same definition as before.</li> </ul> </section> <section> <name>02 to 03</name> <ul spacing="normal"> <li>Updated copyright date, boilerplate template, affiliation, folding algorithm, and reformatted the YANG module.</li> </ul> </section> <section> <name>03 to 04</name> <ul spacing="normal"> <li>Added groupings 'inline-or-truststore-certs-grouping' and 'inline-or-truststore-host-keys-grouping', matching similar definitions in the keystore draft. Note new (and incomplete) "truststore" usage!</li> <li>Related to above, also added features 'truststore-supported' and 'local-trust-anchors-supported'.</li> </ul> </section> <section> <name>04 to 05</name> <ul spacing="normal"> <li>Renamed "trust-anchors" to "truststore"</li> <li>Removed "pinned." prefix everywhere, to match truststore rename</li> <li>Moved everything under a top-level 'grouping' to enable use in other contexts.</li> <li>Renamed feature from 'local-trust-anchors-supported' to 'inline-definitions-supported' (same name used in keystore)</li> <li>Removed the "require-instance false" statement from the "*-ref" typedefs.</li> <li>Added missing "ssh-host-keys" and "x509-certificates" if-feature statements</li> </ul> </section> <section> <name>05 to 06</name> <ul spacing="normal"> <li>Editorial changes only.</li> </ul> </section> <section> <name>06 to 07</name> <ul spacing="normal"> <li>Added Henk Birkholz as a co-author (thanks Henk!)</li> <li>Added PSKs and raw public keys to truststore.</li> </ul> </section> <section> <name>07 to 08</name> <ul spacing="normal"> <li>Added new "Support for Built-in Trust Anchors" section.</li> <li>Removed spurious "uses ct:trust-anchor-certs-grouping" line.</li> <li>Removed PSK from model.</li> </ul> </section> <section> <name>08 to 09</name> <ul spacing="normal"> <li>Removed remaining PSK references from text.</li> <li>Wrapped each top-level list with a container.</li> <li>Introduced "bag" term.</li> <li>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.</li> </ul> </section> <section> <name>09 to 10</name> <ul spacing="normal"> <li>Removed "algorithm" node from examples.</li> <li>Removed the no longer used statements supporting the old "ssh-public-key" and "raw-public-key" nodes.</li> <li>Added a "Note to Reviewers" note to first page.</li> </ul> </section> <section> <name>10 to 11</name> <ul spacing="normal"> <li>Corrected module prefix registered in the IANA Considerations section.</li> <li>Modified 'inline-or-truststore-certs-grouping' to use a list (not a leaf-list).</li> <li>Added new example section "The Local or Truststore Groupings".</li> <li>Clarified expected behavior for "built-in" certificates in <operational></li> <li>Expanded "Data Model Overview section(s) [remove "wall" of tree diagrams].</li> <li>Updated the Security Considerations section.</li> </ul> </section> <section> <name>11 to 12</name> <ul spacing="normal"> <li>Fixed a copy/paste issue in the "Data at Rest" Security Considerations section.</li> </ul> </section> <section> <name>12 to 13</name> <ul spacing="normal"> <li>Fixed issues found by the SecDir review of the "keystore" draft.</li> </ul> </section> <section> <name>13 to 14</name> <ul spacing="normal"> <li>Added an "Unconstrained Public Key Usage" Security Consideration to address concern raised by SecDir.</li> <li>Addressed comments raised by YANG Doctor.</li> </ul> </section> <section> <name>14 to 15</name> <ul spacing="normal"> <li>Added prefixes to 'path' statements per trust-anchors/issues/1</li> <li>Renamed feature "truststore-supported" to "central-truststore-supported".</li> <li>Associated with above, generally moved text to refer to a "central" truststore.</li> <li>Removed two unecessary/unwanted "min-elements 1" and associated "presence" statements.</li> <li>Aligned modules with `pyang -f` formatting.</li> <li>Fixed nits found by YANG Doctor reviews.</li> </ul> </section> <section> <name>15 to 16</name> <ul spacing="normal"> <li>Replaced "base64encodedvalue==" with "BASE64VALUE=" in examples.</li> <li>Minor editorial nits</li> </ul> </section> <section> <name>16 to 17</name> <ul spacing="normal"> <li>fixup the 'WG Web' and 'WG List' lines in YANG module(s)</li> <li>fixup copyright (i.e., s/Simplified/Revised/) in YANG module(s)</li> <li>Added Informative reference to ma-netmod-with-system</li> </ul> </section> <section> <name>17 to 18</name> <ul spacing="normal"> <li>Updated Security Considerations section to address comment received from Carl Wallace.</li> <li>Fixed examples to not have line-returns around "identity" encodings.</li> <li>Fixed a couple tree diagrams to not create diagrams for "groupings" too.</li> <li>Added "if-feature central-truststore-supported" to top-level "trustore" container.</li> </ul> </section> <section> <name>18 to 19</name> <ul spacing="normal"> <li>Updated per Shepherd reviews impacting the suite of drafts.</li> </ul> </section> <section> <name>19 to 20</name> <ul spacing="normal"> <li>Updated per Shepherd reviews impacting the suite of drafts.</li> </ul> </section> <section> <name>20 to 21</name> <ul spacing="normal"> <li>Updated (implicitly) per Tom Petch review.</li> <li>Updated per AD's review.</li> <li>s/local/inline/ in feature names, grouping names, and node names.</li> <li>Updated ref from 'ma-netmod-with-system' to 'ietf-netmod-system-config'.</li> <li>Removed special handling text for built-in certs</li> <li>Updated section on built-in trust anchors to read almost the same as the section in the keystore draft.</li> </ul> </section> <section> <name>21 to 22</name> <ul spacing="normal"> <li>Mostly addresses AD review comments.</li> <li>Also added typedefs and groupings similar to those created by Alto WG.</li> <li>Added note to Editor to fix line foldings.</li> <li>Renamed "truststore" to "central truststore" throughout.</li> <li>Removed "built-in" section text that overlaps with the "system-config" draft.</li> <li>Added "certificate-ref-grouping" and "public-key-ref-grouping"</li> <li>Modified typedef certificate-ref's leafref path to NOT prefix "certificate-bag".</li> <li>Modified typedef public-key-ref's leafref path to NOT prefix "public-key-bag".</li> <li>Added groupings "certificate-ref-grouping" and "public-key-ref-grouping".</li> </ul> </section> <section> <name>22 to 23</name> <ul spacing="normal"> <li>Addresses Gen-ART review by Dale Worley.</li> <li>Addresses review by Tom Petch.</li> </ul> </section> <section> <name>23 to 24</name> <ul spacing="normal"> <li>Addresses 1st-round of IESG reviews.</li> </ul> </section> <section> <name>24 to 26</name> <ul spacing="normal"> <li>Addresses issues found in OpsDir review of the ssh-client-server draft.</li> <li>Renamed Security Considerations section s/Template for/Considerations for/</li> <li>s/defines/presents/ in a few places.</li> <li>Add refs to where the 'operational' and 'system' datastores are defined.</li> <li>Improved Security Consideration for 'cert-data' node.</li> <li>s/should/SHOULD/ is one place</li> </ul> </section> <section> <name>26 to 28</name> <ul spacing="normal"> <li>Nothing changed. Only bumped for automation...</li> </ul> </section> </section> <sectionnumbered="false"> <name>Acknowledgements</name> <t>The authors especially thankHenk Birkholz<contact fullname="Henk Birkholz"/> for contributing YANG to theietf-truststore"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 through Henk's initiative that the WG was able to come to that result.</t> <t>The authors additionally thank the following for helping give shape to this work (ordered by first name):Balázs Kovács, Carl Wallace, Eric Voit, Éric Vyncke, Francesca Palombini, Jensen Zhang, Jürgen Schönwälder, Lars Eggert, Liang Xia, Martin Björklund, Murray Kucherawy, Nick Hancock, Qin Wu, Rob Wilton, Robert Varga, Roman Danyliw, Paul Kyzivat, and Yoav Nir.<contact fullname="Balázs Kovács"/>, <contact fullname="Carl Wallace"/>, <contact fullname="Eric Voit"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Francesca Palombini"/>, <contact fullname="Jensen Zhang"/>, <contact fullname="Jürgen Schönwälder"/>, <contact fullname="Lars Eggert"/>, <contact fullname="Liang Xia"/>, <contact fullname="Martin Björklund"/>, <contact fullname="Murray Kucherawy"/>, <contact fullname="Nick Hancock"/>, <contact fullname="Paul Kyzivat"/>, <contact fullname="Qin Wu"/>, <contact fullname="Rob Wilton"/>, <contact fullname="Robert Varga"/>, <contact fullname="Roman Danyliw"/>, and <contact fullname="Yoav Nir"/>. </t> </section> </back> </rfc>