YANG Data Model for Global Trust AnchorsJuniper Networkskwatsen@juniper.net
Operations
NETCONF Working GroupThis document defines a YANG 1.1 data model for configuring
global sets of X.509 certificates and SSH host-keys that
can be referenced by other data models for trust. While
the SSH host-keys are uniquely for the SSH protocol, the
X.509 certificates may have multiple uses, including
authenticating protocol peers and verifying signatures.This draft contains many 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:
XXXX --> the assigned RFC value for this draftYYYY --> the assigned RFC value for draft-ietf-netconf-crypto-typesArtwork in this document contains placeholder values for the date
of publication of this draft. Please apply the following replacement:
2018-10-22 --> the publication date of this draftThe following Appendix section is to be removed prior to publication:
Appendix A. Change LogThis document defines a YANG 1.1 data
model for configuring global sets of X.509 certificates and SSH
host-keys that can be referenced by other data models for trust.
While the SSH host-keys are uniquely for the SSH protocol, the
X.509 certificates may be used for multiple uses, including
authenticating protocol peers and verifying signatures.This document in compliant with Network Management Datastore Architecture
(NMDA) . For instance, to support trust anchors
installed during manufacturing, it is expected that such data may appear
only in <operational>.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
when, and only when, they appear in all capitals, as shown here.Tree diagrams used in this document follow the notation
defined in .The following tree diagram provides an overview of the
"ietf-trust-anchors" module.The following example illustrates trust anchors in <operational> as described
by Section 5.3 in . This datastore view illustrates
data set by the manufacturing process alongside conventional configuration. This
trust anchors instance has six sets of pinned certificates and one set of pinned
host keys.The following example illustrates the "certificate-expiration"
notification in use with the NETCONF protocol.This YANG module imports modules from
and .The YANG module defined in this document is designed to be accessed via YANG
based management protocols, such as NETCONF and
RESTCONF . Both of these protocols have mandatory-to-implement
secure transport layers (e.g., SSH, TLS) with mutual authentication.The NETCONF access control model (NACM) 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.This document registers one URI in the "ns" subregistry of
the IETF XML Registry . Following the
format in , the following registration
is requested:This document registers one YANG module in the
YANG Module Names registry .
Following the format in , the
the following registration is requested:Added features "x509-certificates" and "ssh-host-keys".Added nacm:default-deny-write to "trust-anchors" container.Switched "list pinned-certificate" to use the
"trust-anchor-cert-grouping" from crypto-types.
Effectively the same definition as before.The authors would like to thank for following for
lively discussions on list and in the halls (ordered
by last name):
Martin Bjorklund,
Balázs Kovács,
Eric Voit,
and Liang Xia.