NETCONF Client and Server ModelsWatsen Networkskent+ietf@watsen.net
Operations
NETCONF Working GroupThis document defines two YANG modules, one module to
configure a NETCONF client and the other module to configure
a NETCONF server. Both modules support both the SSH and
TLS transport protocols, and support both standard NETCONF
and NETCONF Call Home connections.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 (note: not all may be present):
AAAA --> the assigned RFC value for draft-ietf-netconf-crypto-types
BBBB --> the assigned RFC value for draft-ietf-netconf-trust-anchors
CCCC --> the assigned RFC value for draft-ietf-netconf-keystore
DDDD --> the assigned RFC value for draft-ietf-netconf-tcp-client-server
EEEE --> the assigned RFC value for draft-ietf-netconf-ssh-client-server
FFFF --> the assigned RFC value for draft-ietf-netconf-tls-client-server
GGGG --> the assigned RFC value for draft-ietf-netconf-http-client-server
HHHH --> 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:
2022-05-24 --> the publication date of this draft
The following Appendix section is to be removed prior to publication:
. Change Log
IntroductionThis document defines two YANG modules, one module
to configure a NETCONF client and the other module
to configure a NETCONF server. Both modules support both NETCONF over
SSH and NETCONF over TLS
and NETCONF Call Home connections .Relation to other RFCsThis document presents one or more YANG modules
that are part of a collection of RFCs that work together to,
ultimately, enable the configuration of the clients and
servers of both the NETCONF and RESTCONF
protocols.The modules have been defined in a modular fashion to enable
their use by other efforts, some of which are known to be in
progress at the time of this writing, with many more expected
to be defined in time.The normative dependency relationship between the various RFCs in the collection
is presented in the below diagram. The labels in the diagram
represent the primary purpose provided by each RFC. Hyperlinks to
each RFC are provided below the diagram.
Label to RFC Mapping
Label in Diagram
Originating RFC
crypto-types
truststore
keystore
tcp-client-server
ssh-client-server
tls-client-server
http-client-server
netconf-client-server
restconf-client-server
Specification LanguageThe 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.Adherence to the NMDAThis document is compliant with the Network Management Datastore
Architecture (NMDA) . For instance, as
described in and
, trust anchors and keys
installed during manufacturing are expected to appear
in <operational>.ConventionsVarious examples used in this document use a placeholder
value for binary data that has been base64 encoded (e.g.,
"BASE64VALUE="). This placeholder value is used as real
base64 encoded structures are often many lines long and
hence distracting to the example being presented.The "ietf-netconf-client" ModuleThe NETCONF client model presented in this section supports
both clients initiating connections to servers, as well as
clients listening for connections from servers calling home,
using either the SSH and TLS transport protocols.YANG feature statements are used to enable implementations to
advertise which potentially uncommon parts of the model the
NETCONF client supports.Data Model OverviewThis section provides an overview of the "ietf-netconf-client"
module in terms of its features and groupings.FeaturesThe following diagram lists all the "feature" statements
defined in the "ietf-netconf-client" module:GroupingsThe "ietf-netconf-client" module defines the following "grouping" statements:
netconf-client-grouping
netconf-client-initiate-stack-grouping
netconf-client-listen-stack-grouping
netconf-client-app-grouping
Each of these groupings are presented in the following subsections.The "netconf-client-grouping" GroupingThe following tree diagram illustrates the
"netconf-client-grouping" grouping::
]]>Comments:
This grouping does not define any nodes, but is maintained so
that downstream modules can augment nodes into it if needed.
The "netconf-client-grouping" defines, if it can be called
that, the configuration for just "NETCONF" part of a protocol
stack. It does not, for instance, define any configuration
for the "TCP", "SSH" or "TLS" protocol layers (for that, see
and ).
The "netconf-client-initiate-stack-grouping" GroupingThe following tree diagram illustrates the
"netconf-client-initiate-stack-grouping" grouping:Comments:
The "netconf-client-initiate-stack-grouping" defines the
configuration for a full NETCONF protocol stack, for NETCONF
clients that initiate connections to NETCONF servers, as
opposed to receiving call-home
connections.
The "transport" choice node enables both the SSH and
TLS transports to be configured, with each option
enabled by a "feature" statement.
For the referenced grouping statement(s):
The "tcp-client-grouping" grouping is discussed in
.
The "ssh-client-grouping" grouping is discussed in
.
The "tls-client-grouping" grouping is discussed in
.
The "netconf-client-grouping" grouping is discussed in
in this document.
The "netconf-client-listen-stack-grouping" GroupingThe following tree diagram illustrates the
"netconf-client-listen-stack-grouping" grouping:Comments:
The "netconf-client-listen-stack-grouping" defines the
configuration for a full NETCONF protocol stack, for NETCONF
clients that receive call-home
connections from NETCONF servers.
The "transport" choice node enables both the SSH and
TLS transports to be configured, with each option
enabled by a "feature" statement.
For the referenced grouping statement(s):
The "tcp-server-grouping" grouping is discussed in
.
The "ssh-client-grouping" grouping is discussed in
.
The "tls-client-grouping" grouping is discussed in
.
The "netconf-client-grouping" grouping is discussed in
in this document.
The "netconf-client-app-grouping" GroupingThe following tree diagram illustrates the
"netconf-client-app-grouping" grouping:Comments:
The "netconf-client-app-grouping" defines the configuration
for a NETCONF client that supports both initiating connections
to NETCONF servers as well as receiving call-home connections from
NETCONF servers.
Both the "initiate" and "listen" subtrees must be enabled by
"feature" statements.
For the referenced grouping statement(s):
The "netconf-client-initiate-stack-grouping" grouping is discussed in
in this document.
The "netconf-client-listen-stack-grouping" grouping is discussed in
in this document.
Protocol-accessible NodesThe following tree diagram lists all the protocol-accessible nodes
defined in the "ietf-netconf-client" module:Comments:
Protocol-accessible nodes are those nodes that are accessible
when the module is "implemented", as described in .
The top-level node "netconf-client" is additionally constrained
by the feature "central-netconf-client-supported".
The "netconf-client-app-grouping" grouping is discussed in
in this document.
The reason for why "netconf-client-app-grouping" exists separate from
the protocol-accessible nodes definition is so as to enable
instances of netconf-client-app-grouping to be instantiated in other
locations, as may be needed or desired by some modules.
Example UsageThe following example illustrates configuring a NETCONF
client to initiate connections, using both the SSH and TLS
transport protocols, as well as to listen for call-home
connections, again using both the SSH and TLS transport
protocols.This example is consistent with the examples presented in
and
.corp-fw1corp-fw1.example.comcorp-fw1.example.com15330foobarssh-rsa-key
trusted-server-ca-certs
trusted-server-ee-certs
303corp-fw2.example.comcorp-fw2.example.com15330rsa-asymmetric-key
ex-rsa-certtrusted-server-ca-certs
trusted-server-ee-certs
303last-connectedIntranet-facing SSH listener192.0.2.7foobarssh-rsa-keytrusted-server-ca-certs
trusted-server-ee-certs
trusted-ssh-public-keys
Intranet-facing TLS listener192.0.2.7rsa-asymmetric-keyex-rsa-certtrusted-server-ca-certs
trusted-server-ee-certs
]]>YANG ModuleThis YANG module has normative references to ,
, , ,
,
, and
.<CODE BEGINS> file "ietf-netconf-client@2022-05-24.yang"
Author: Kent Watsen
Author: Gary Wu ";
description
"This module contains a collection of YANG definitions
for configuring NETCONF clients.
Copyright (c) 2022 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 RFC HHHH
(https://www.rfc-editor.org/info/rfcHHHH); 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 2022-05-24 {
description
"Initial version";
reference
"RFC HHHH: NETCONF Client and Server Models";
}
// Features
feature ssh-initiate {
description
"The 'ssh-initiate' feature indicates that the NETCONF client
supports initiating SSH connections to NETCONF servers.";
reference
"RFC 6242:
Using the NETCONF Protocol over Secure Shell (SSH)";
}
feature tls-initiate {
description
"The 'tls-initiate' feature indicates that the NETCONF client
supports initiating TLS connections to NETCONF servers.";
reference
"RFC 7589: Using the NETCONF Protocol over Transport
Layer Security (TLS) with Mutual X.509 Authentication";
}
feature ssh-listen {
description
"The 'ssh-listen' feature indicates that the NETCONF client
supports opening a port to listen for incoming NETCONF
server call-home SSH connections.";
reference
"RFC 8071: NETCONF Call Home and RESTCONF Call Home";
}
feature tls-listen {
description
"The 'tls-listen' feature indicates that the NETCONF client
supports opening a port to listen for incoming NETCONF
server call-home TLS connections.";
reference
"RFC 8071: NETCONF Call Home and RESTCONF Call Home";
}
feature central-netconf-client-supported {
description
"The 'central-netconf-client-supported' feature indicates
that the server supports the top-level 'netconf-client'
node.
This feature is needed as some servers may want to use
features defined in this module, which requires this
module to be implemented, without having to support
the top-level 'netconf-client' node.";
}
// Groupings
grouping netconf-client-grouping {
description
"A reusable grouping for configuring a NETCONF client
without any consideration for how underlying transport
sessions are established.
This grouping currently does not define any nodes. It
exists only so the model can be consistent with other
'client-server' models.";
}
grouping netconf-client-initiate-stack-grouping {
description
"A reusable grouping for configuring a NETCONF client
'initiate' protocol stack for a single connection.";
choice transport {
mandatory true;
description
"Selects between available transports.";
case ssh {
if-feature "ssh-initiate";
container ssh {
description
"Specifies IP and SSH specific configuration
for the connection.";
container tcp-client-parameters {
description
"A wrapper around the TCP client parameters
to avoid name collisions.";
uses tcpc:tcp-client-grouping {
refine "remote-port" {
default "830";
description
"The NETCONF client will attempt to connect
to the IANA-assigned well-known port value
for 'netconf-ssh' (830) if no value is
specified.";
}
}
}
container ssh-client-parameters {
description
"A wrapper around the SSH client parameters to
avoid name collisions.";
uses sshc:ssh-client-grouping;
}
container netconf-client-parameters {
description
"A wrapper around the NETCONF client parameters
to avoid name collisions.
This container does not define any nodes. It
exists as a potential augmentation target by
other modules.";
uses ncc:netconf-client-grouping;
}
}
}
case tls {
if-feature "tls-initiate";
container tls {
description
"Specifies IP and TLS specific configuration
for the connection.";
container tcp-client-parameters {
description
"A wrapper around the TCP client parameters
to avoid name collisions.";
uses tcpc:tcp-client-grouping {
refine "remote-port" {
default "6513";
description
"The NETCONF client will attempt to connect
to the IANA-assigned well-known port value
for 'netconf-tls' (6513) if no value is
specified.";
}
}
}
container tls-client-parameters {
must client-identity {
description
"NETCONF/TLS clients MUST pass some
authentication credentials.";
}
description
"A wrapper around the TLS client parameters
to avoid name collisions.";
uses tlsc:tls-client-grouping;
}
container netconf-client-parameters {
description
"A wrapper around the NETCONF client parameters
to avoid name collisions.
This container does not define any nodes. It
exists as a potential augmentation target by
other modules.";
uses ncc:netconf-client-grouping;
}
}
}
}
} // netconf-client-initiate-stack-grouping
grouping netconf-client-listen-stack-grouping {
description
"A reusable grouping for configuring a NETCONF client
'listen' protocol stack for a single connection. The
'listen' stack supports call home connections, as
described in RFC 8071";
reference
"RFC 8071: NETCONF Call Home and RESTCONF Call Home";
choice transport {
mandatory true;
description
"Selects between available transports.";
case ssh {
if-feature "ssh-listen";
container ssh {
description
"SSH-specific listening configuration for inbound
connections.";
container tcp-server-parameters {
description
"A wrapper around the TCP server parameters
to avoid name collisions.";
uses tcps:tcp-server-grouping {
refine "local-port" {
default "4334";
description
"The NETCONF client will listen on the IANA-
assigned well-known port for 'netconf-ch-ssh'
(4334) if no value is specified.";
}
}
}
container ssh-client-parameters {
description
"A wrapper around the SSH client parameters
to avoid name collisions.";
uses sshc:ssh-client-grouping;
}
container netconf-client-parameters {
description
"A wrapper around the NETCONF client parameters
to avoid name collisions.
This container does not define any nodes. It
exists as a potential augmentation target by
other modules.";
uses ncc:netconf-client-grouping;
}
}
}
case tls {
if-feature "tls-listen";
container tls {
description
"TLS-specific listening configuration for inbound
connections.";
container tcp-server-parameters {
description
"A wrapper around the TCP server parameters
to avoid name collisions.";
uses tcps:tcp-server-grouping {
refine "local-port" {
default "4334";
description
"The NETCONF client will listen on the IANA-
assigned well-known port for 'netconf-ch-ssh'
(4334) if no value is specified.";
}
}
}
container tls-client-parameters {
must client-identity {
description
"NETCONF/TLS clients MUST pass some
authentication credentials.";
}
description
"A wrapper around the TLS client parameters
to avoid name collisions.";
uses tlsc:tls-client-grouping;
}
container netconf-client-parameters {
description
"A wrapper around the NETCONF client parameters
to avoid name collisions.
This container does not define any nodes. It
exists as a potential augmentation target by
other modules.";
uses ncc:netconf-client-grouping;
}
}
}
}
} // netconf-client-listen-stack-grouping
grouping netconf-client-app-grouping {
description
"A reusable grouping for configuring a NETCONF client
application that supports both 'initiate' and 'listen'
protocol stacks for a multiplicity of connections.";
container initiate {
if-feature "ssh-initiate or tls-initiate";
presence
"Indicates that client-initiated connections have been
configured. This statement is present so the mandatory
descendant nodes do not imply that this node must be
configured.";
description
"Configures client initiating underlying TCP connections.";
list netconf-server {
key "name";
min-elements 1;
description
"List of NETCONF servers the NETCONF client is to
maintain simultaneous connections with.";
leaf name {
type string;
description
"An arbitrary name for the NETCONF server.";
}
container endpoints {
description
"Container for the list of endpoints.";
list endpoint {
key "name";
min-elements 1;
ordered-by user;
description
"A user-ordered list of endpoints that the NETCONF
client will attempt to connect to in the specified
sequence. Defining more than one enables
high-availability.";
leaf name {
type string;
description
"An arbitrary name for the endpoint.";
}
uses netconf-client-initiate-stack-grouping;
} // list endpoint
} // container endpoints
container connection-type {
description
"Indicates the NETCONF client's preference for how the
NETCONF connection is maintained.";
choice connection-type {
mandatory true;
description
"Selects between available connection types.";
case persistent-connection {
container persistent {
presence
"Indicates that a persistent connection is to be
maintained.";
description
"Maintain a persistent connection to the NETCONF
server. If the connection goes down, immediately
start trying to reconnect to the NETCONF server,
using the reconnection strategy.
This connection type minimizes any NETCONF server
to NETCONF client data-transfer delay, albeit at
the expense of holding resources longer.";
}
}
case periodic-connection {
container periodic {
presence "Indicates that a periodic connection is
to be maintained.";
description
"Periodically connect to the NETCONF server.
This connection type increases resource
utilization, albeit with increased delay in
NETCONF server to NETCONF client interactions.
The NETCONF client should close the underlying
TCP connection upon completing planned activities.
In the case that the previous connection is still
active, establishing a new connection is NOT
RECOMMENDED.";
leaf period {
type uint16;
units "minutes";
default "60";
description
"Duration of time between periodic connections.";
}
leaf anchor-time {
type yang:date-and-time {
// constrained to minute-level granularity
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}'
+ '(Z|[\+\-]\d{2}:\d{2})';
}
description
"Designates a timestamp before or after which a
series of periodic connections are determined.
The periodic connections occur at a whole
multiple interval from the anchor time. For
example, for an anchor time is 15 minutes past
midnight and a period interval of 24 hours, then
a periodic connection will occur 15 minutes past
midnight everyday.";
}
leaf idle-timeout {
type uint16;
units "seconds";
default 120; // two minutes
description
"Specifies the maximum number of seconds that
a NETCONF session may remain idle. A NETCONF
session will be dropped if it is idle for an
interval longer then this number of seconds.
If set to zero, then the NETCONF client will
never drop a session because it is idle.";
}
}
}
}
}
container reconnect-strategy {
description
"The reconnection strategy directs how a NETCONF client
reconnects to a NETCONF server, after discovering its
connection to the server has dropped, even if due to a
reboot. The NETCONF client starts with the specified
endpoint and tries to connect to it max-attempts times
before trying the next endpoint in the list (round
robin).";
leaf start-with {
type enumeration {
enum first-listed {
description
"Indicates that reconnections should start with
the first endpoint listed.";
}
enum last-connected {
description
"Indicates that reconnections should start with
the endpoint last connected to. If no previous
connection has ever been established, then the
first endpoint configured is used. NETCONF
clients SHOULD be able to remember the last
endpoint connected to across reboots.";
}
enum random-selection {
description
"Indicates that reconnections should start with
a random endpoint.";
}
}
default "first-listed";
description
"Specifies which of the NETCONF server's endpoints
the NETCONF client should start with when trying
to connect to the NETCONF server.";
}
leaf max-attempts {
type uint8 {
range "1..max";
}
default "3";
description
"Specifies the number times the NETCONF client tries
to connect to a specific endpoint before moving on
to the next endpoint in the list (round robin).";
}
}
} // netconf-server
} // initiate
container listen {
if-feature "ssh-listen or tls-listen";
presence
"Indicates that client-listening ports have been configured.
This statement is present so the mandatory descendant nodes
do not imply that this node must be configured.";
description
"Configures the client to accept call-home TCP connections.";
leaf idle-timeout {
type uint16;
units "seconds";
default "3600"; // one hour
description
"Specifies the maximum number of seconds that a NETCONF
session may remain idle. A NETCONF session will be
dropped if it is idle for an interval longer than this
number of seconds. If set to zero, then the server
will never drop a session because it is idle. Sessions
that have a notification subscription active are never
dropped.";
}
list endpoint {
key "name";
min-elements 1;
description
"List of endpoints to listen for NETCONF connections.";
leaf name {
type string;
description
"An arbitrary name for the NETCONF listen endpoint.";
}
uses netconf-client-listen-stack-grouping;
} // endpoint
} // listen
} // netconf-client-app-grouping
// Protocol accessible node for clients that implement this module.
container netconf-client {
if-feature central-netconf-client-supported;
uses netconf-client-app-grouping;
description
"Top-level container for NETCONF client configuration.";
}
}
]]><CODE ENDS>The "ietf-netconf-server" ModuleThe NETCONF server model presented in this section supports
both listening for connections as well as initiating call-home
connections, using either the SSH and TLS transport protocols.YANG feature statements are used to enable implementations to
advertise which potentially uncommon parts of the model the
NETCONF server supports.Data Model OverviewThis section provides an overview of the "ietf-netconf-server"
module in terms of its features and groupings.FeaturesThe following diagram lists all the "feature" statements
defined in the "ietf-netconf-server" module:GroupingsThe "ietf-netconf-server" module defines the following "grouping" statements:
netconf-server-grouping
netconf-server-listen-stack-grouping
netconf-server-callhome-stack-grouping
netconf-server-app-grouping
Each of these groupings are presented in the following subsections.The "netconf-server-grouping" GroupingThe following tree diagram illustrates the
"netconf-server-grouping" grouping:Comments:
The "netconf-server-grouping" defines the configuration for just
"NETCONF" part of a protocol stack. It does not, for instance,
define any configuration for the "TCP", "SSH" or "TLS" protocol layers
(for that, see
and ).
The "client-identity-mappings" node, which must be enabled by
"feature" statements, defines a mapping from certificate fields
to NETCONF user names.
For the referenced grouping statement(s):
The "cert-to-name" grouping is discussed in
.
The "netconf-server-listen-stack-grouping" GroupingThe following tree diagram illustrates the
"netconf-server-listen-stack-grouping" grouping:Comments:
The "netconf-server-listen-stack-grouping" defines the
configuration for a full NETCONF protocol stack for NETCONF
servers that listen for standard connections from NETCONF clients,
as opposed to initiating call-home connections.
The "transport" choice node enables both the SSH and
TLS transports to be configured, with each option
enabled by a "feature" statement.
For the referenced grouping statement(s):
The "tcp-server-grouping" grouping is discussed in
.
The "ssh-server-grouping" grouping is discussed in
.
The "tls-server-grouping" grouping is discussed in
.
The "netconf-server-grouping" is discussed in
of this document.
The "netconf-server-callhome-stack-grouping" GroupingThe following tree diagram illustrates the
"netconf-server-callhome-stack-grouping" grouping:Comments:
The "netconf-server-callhome-stack-grouping" defines the
configuration for a full NETCONF protocol stack, for NETCONF
servers that initiate call-home connections
to NETCONF clients.
The "transport" choice node enables both the SSH and
TLS transports to be configured, with each option
enabled by a "feature" statement.
For the referenced grouping statement(s):
The "tcp-client-grouping" grouping is discussed in
.
The "ssh-server-grouping" grouping is discussed in
.
The "tls-server-grouping" grouping is discussed in
.
The "netconf-server-grouping" is discussed in
of this document.
The "netconf-server-app-grouping" GroupingThe following tree diagram illustrates the
"netconf-server-app-grouping" grouping:Comments:
The "netconf-server-app-grouping" defines the configuration
for a NETCONF server that supports both listening for connections
from NETCONF clients as well as initiating call-home connections to
NETCONF clients.
Both the "listen" and "call-home" subtrees must be enabled by
"feature" statements.
For the referenced grouping statement(s):
The "netconf-server-listen-stack-grouping" grouping is discussed in
in this document.
The "netconf-server-callhome-stack-grouping" grouping is discussed in
in this document.
Protocol-accessible NodesThe following tree diagram lists all the protocol-accessible nodes
defined in the "ietf-netconf-server" module:Comments:
Protocol-accessible nodes are those nodes that are accessible
when the module is "implemented", as described in .
The top-level node "netconf-server" is additionally constrained
by the feature "central-netconf-server-supported".
The "netconf-server-app-grouping" grouping is discussed in
in this document.
The reason for why "netconf-server-app-grouping" exists separate from
the protocol-accessible nodes definition is so as to enable
instances of netconf-server-app-grouping to be instantiated in other
locations, as may be needed or desired by some modules.
Example UsageThe following example illustrates configuring a NETCONF server
to listen for NETCONF client connections using both the SSH and
TLS transport protocols, as well as configuring call-home to two
NETCONF clients, one using SSH and the other using TLS.This example is consistent with the examples presented in
and
.netconf/ssh192.0.2.7deployment-specific-certificatessh-rsa-keynetconf/tls192.0.2.7rsa-asymmetric-keyex-rsa-certtrusted-client-ca-certs
trusted-client-ee-certs
111:0A:05:11:00x509c2n:specifiedscooby-doo2x509c2n:san-anyconfig-mgreast-data-centereast.config-mgr.example.com
15330deployment-specific-certificatessh-rsa-key
west-data-centerwest.config-mgr.example.com
deployment-specific-certificatessh-rsa-key
30060last-connected3data-collectoreast-data-centereast.analytics.example.com
15330rsa-asymmetric-key
ex-rsa-certtrusted-client-ca-certs
trusted-client-ee-certs
303111:0A:05:11:00x509c2n:specifiedscooby-doo2x509c2n:san-anywest-data-centerwest.analytics.example.com
15330rsa-asymmetric-key
ex-rsa-certtrusted-client-ca-certs
trusted-client-ee-certs
303111:0A:05:11:00x509c2n:specifiedscooby-doo2x509c2n:san-anyfirst-listed3
]]>YANG ModuleThis YANG module has normative references to ,
, , ,
, ,
, and
.<CODE BEGINS> file "ietf-netconf-server@2022-05-24.yang"
Author: Kent Watsen
Author: Gary Wu
Author: Juergen Schoenwaelder
";
description
"This module contains a collection of YANG definitions
for configuring NETCONF servers.
Copyright (c) 2022 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 RFC HHHH
(https://www.rfc-editor.org/info/rfcHHHH); 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 2022-05-24 {
description
"Initial version";
reference
"RFC HHHH: NETCONF Client and Server Models";
}
// Features
feature ssh-listen {
description
"The 'ssh-listen' feature indicates that the NETCONF server
supports opening a port to accept NETCONF over SSH
client connections.";
reference
"RFC 6242:
Using the NETCONF Protocol over Secure Shell (SSH)";
}
feature tls-listen {
description
"The 'tls-listen' feature indicates that the NETCONF server
supports opening a port to accept NETCONF over TLS
client connections.";
reference
"RFC 7589: Using the NETCONF Protocol over Transport
Layer Security (TLS) with Mutual X.509
Authentication";
}
feature ssh-call-home {
description
"The 'ssh-call-home' feature indicates that the NETCONF
server supports initiating a NETCONF over SSH call
home connection to NETCONF clients.";
reference
"RFC 8071: NETCONF Call Home and RESTCONF Call Home";
}
feature tls-call-home {
description
"The 'tls-call-home' feature indicates that the NETCONF
server supports initiating a NETCONF over TLS call
home connection to NETCONF clients.";
reference
"RFC 8071: NETCONF Call Home and RESTCONF Call Home";
}
feature central-netconf-server-supported {
description
"The 'central-netconf-server-supported' feature indicates
that the server supports the top-level 'netconf-server'
node.
This feature is needed as some servers may want to use
features defined in this module, which requires this
module to be implemented, without having to support
the top-level 'netconf-server' node.";
}
// Groupings
grouping netconf-server-grouping {
description
"A reusable grouping for configuring a NETCONF server
without any consideration for how underlying transport
sessions are established.
Note that this grouping uses a fairly typical descendant
node name such that a stack of 'uses' statements will
have name conflicts. It is intended that the consuming
data model will resolve the issue by wrapping the 'uses'
statement in a container called, e.g.,
'netconf-server-parameters'. This model purposely does
not do this itself so as to provide maximum flexibility
to consuming models.";
container client-identity-mappings {
description
"Specifies mappings through which NETCONF client X.509
certificates are used to determine a NETCONF username,
per RFC 7407.
For TLS-based transports, if no matching and valid
cert-to-name list entry can be found, then the NETCONF
server MUST close the connection, and MUST NOT accept
NETCONF messages over it, per Section 7 in RFC 7589.
For SSH-based transports, a matching cert-to-name
entry overrides the username provided by the SSH
implementation, consistent with the second paragraph
of Section 3 in RFC 6242.";
reference
"RFC 6242:
Using the NETCONF Protocol over Secure Shell (SSH)
RFC 7589:
Using the NETCONF Protocol over Transport Layer
Security (TLS) with Mutual X.509 Authentication";
uses x509c2n:cert-to-name {
refine "cert-to-name/fingerprint" {
mandatory false;
description
"A 'fingerprint' value does not need to be specified
when the 'cert-to-name' mapping is independent of
fingerprint matching. A 'cert-to-name' having no
fingerprint value will match any client certificate
and therefore should only be present at the end of
the user-ordered 'cert-to-name' list.";
}
}
}
}
grouping netconf-server-listen-stack-grouping {
description
"A reusable grouping for configuring a NETCONF server
'listen' protocol stack for a single connection.";
choice transport {
mandatory true;
description
"Selects between available transports.";
case ssh {
if-feature "ssh-listen";
container ssh {
description
"SSH-specific listening configuration for inbound
connections.";
container tcp-server-parameters {
description
"A wrapper around the TCP client parameters
to avoid name collisions.";
uses tcps:tcp-server-grouping {
refine "local-port" {
default "830";
description
"The NETCONF server will listen on the
IANA-assigned well-known port value
for 'netconf-ssh' (830) if no value
is specified.";
}
}
}
container ssh-server-parameters {
description
"A wrapper around the SSH server parameters
to avoid name collisions.";
uses sshs:ssh-server-grouping;
}
container netconf-server-parameters {
description
"A wrapper around the NETCONF server parameters
to avoid name collisions.";
uses ncs:netconf-server-grouping {
refine "client-identity-mappings" {
if-feature "sshcmn:ssh-x509-certs";
description
"Augments in an 'if-feature' statement
ensuring the 'client-identity-mappings'
descendant is enabled only when SSH
supports X.509 certificates.";
}
augment "client-identity-mappings" {
description
"Adds a flag indicating if a cert-to-name
is required.";
leaf mapping-required {
type boolean;
description
"Indicates that the cert-to-name mapping
is required (i.e., the SSH-level username
is ignored).";
}
}
}
}
}
}
case tls {
if-feature "tls-listen";
container tls {
description
"TLS-specific listening configuration for inbound
connections.";
container tcp-server-parameters {
description
"A wrapper around the TCP client parameters
to avoid name collisions.";
uses tcps:tcp-server-grouping {
refine "local-port" {
default "6513";
description
"The NETCONF server will listen on the
IANA-assigned well-known port value
for 'netconf-tls' (6513) if no value
is specified.";
}
}
}
container tls-server-parameters {
description
"A wrapper around the TLS server parameters to
avoid name collisions.";
uses tlss:tls-server-grouping {
refine "client-authentication" {
must 'ca-certs or ee-certs';
description
"NETCONF/TLS servers MUST validate client
certificates. This configures certificates
at the socket-level (i.e. bags), more
discriminating client-certificate checks
SHOULD be implemented by the application.";
reference
"RFC 7589:
Using the NETCONF Protocol over Transport Layer
Security (TLS) with Mutual X.509 Authentication";
}
}
}
container netconf-server-parameters {
description
"A wrapper around the NETCONF server parameters
to avoid name collisions.";
uses ncs:netconf-server-grouping {
refine "client-identity-mappings/cert-to-name" {
min-elements 1;
description
"The TLS transport requires a mapping.";
}
}
}
}
}
}
}
grouping netconf-server-callhome-stack-grouping {
description
"A reusable grouping for configuring a NETCONF server
'call-home' protocol stack, for a single connection.";
choice transport {
mandatory true;
description
"Selects between available transports.";
case ssh {
if-feature "ssh-call-home";
container ssh {
description
"Specifies SSH-specific call-home transport
configuration.";
container tcp-client-parameters {
description
"A wrapper around the TCP client parameters
to avoid name collisions.";
uses tcpc:tcp-client-grouping {
refine "remote-port" {
default "4334";
description
"The NETCONF server will attempt to connect
to the IANA-assigned well-known port for
'netconf-ch-tls' (4334) if no value is
specified.";
}
}
}
container ssh-server-parameters {
description
"A wrapper around the SSH server parameters
to avoid name collisions.";
uses sshs:ssh-server-grouping;
}
container netconf-server-parameters {
description
"A wrapper around the NETCONF server parameters
to avoid name collisions.";
uses ncs:netconf-server-grouping {
refine "client-identity-mappings" {
if-feature "sshcmn:ssh-x509-certs";
description
"Augments in an 'if-feature' statement
ensuring the 'client-identity-mappings'
descendant is enabled only when SSH
supports X.509 certificates.";
}
augment "client-identity-mappings" {
description
"Adds a flag indicating if a cert-to-name
is required.";
leaf mapping-required {
type boolean;
description
"Indicates that the cert-to-name mapping
is required (i.e., the SSH-level username
is ignored).";
}
}
}
}
}
}
case tls {
if-feature "tls-call-home";
container tls {
description
"Specifies TLS-specific call-home transport
configuration.";
container tcp-client-parameters {
description
"A wrapper around the TCP client parameters
to avoid name collisions.";
uses tcpc:tcp-client-grouping {
refine "remote-port" {
default "4335";
description
"The NETCONF server will attempt to connect
to the IANA-assigned well-known port for
'netconf-ch-tls' (4335) if no value is
specified.";
}
}
}
container tls-server-parameters {
description
"A wrapper around the TLS server parameters to
avoid name collisions.";
uses tlss:tls-server-grouping {
refine "client-authentication" {
must 'ca-certs or ee-certs';
description
"NETCONF/TLS servers MUST validate client
certificates. This configures certificates
at the socket-level (i.e. bags), more
discriminating client-certificate checks
SHOULD be implemented by the application.";
reference
"RFC 7589:
Using the NETCONF Protocol over Transport Layer
Security (TLS) with Mutual X.509 Authentication";
}
}
}
container netconf-server-parameters {
description
"A wrapper around the NETCONF server parameters
to avoid name collisions.";
uses ncs:netconf-server-grouping {
refine "client-identity-mappings/cert-to-name" {
min-elements 1;
description
"The TLS transport requires a mapping.";
}
}
}
}
}
}
}
grouping netconf-server-app-grouping {
description
"A reusable grouping for configuring a NETCONF server
application that supports both 'listen' and 'call-home'
protocol stacks for a multiplicity of connections.";
container listen {
if-feature "ssh-listen or tls-listen";
presence
"Indicates that server-listening ports have been configured.
This statement is present so the mandatory descendant
nodes do not imply that this node must be configured.";
description
"Configures listen behavior";
leaf idle-timeout {
type uint16;
units "seconds";
default "3600"; // one hour
description
"Specifies the maximum number of seconds that a NETCONF
session may remain idle. A NETCONF session will be
dropped if it is idle for an interval longer than this
number of seconds. If set to zero, then the server
will never drop a session because it is idle. Sessions
that have a notification subscription active are never
dropped.";
}
list endpoint {
key "name";
min-elements 1;
description
"List of endpoints to listen for NETCONF connections.";
leaf name {
type string;
description
"An arbitrary name for the NETCONF listen endpoint.";
}
uses netconf-server-listen-stack-grouping;
}
}
container call-home {
if-feature "ssh-call-home or tls-call-home";
presence
"Indicates that server-initiated call home connections have
been configured. This statement is present so the mandatory
descendant nodes do not imply that this node must be
configured.";
description
"Configures the NETCONF server to initiate the underlying
transport connection to NETCONF clients.";
list netconf-client {
key "name";
min-elements 1;
description
"List of NETCONF clients the NETCONF server is to
maintain simultaneous call-home connections with.";
leaf name {
type string;
description
"An arbitrary name for the remote NETCONF client.";
}
container endpoints {
description
"Container for the list of endpoints.";
list endpoint {
key "name";
min-elements 1;
ordered-by user;
description
"A non-empty user-ordered list of endpoints for this
NETCONF server to try to connect to in sequence.
Defining more than one enables high-availability.";
leaf name {
type string;
description
"An arbitrary name for this endpoint.";
}
uses netconf-server-callhome-stack-grouping;
}
}
container connection-type {
description
"Indicates the NETCONF server's preference for how the
NETCONF connection is maintained.";
choice connection-type {
mandatory true;
description
"Selects between available connection types.";
case persistent-connection {
container persistent {
presence
"Indicates that a persistent connection is to be
maintained.";
description
"Maintain a persistent connection to the NETCONF
client. If the connection goes down, immediately
start trying to reconnect to the NETCONF client,
using the reconnection strategy.
This connection type minimizes any NETCONF client
to NETCONF server data-transfer delay, albeit at
the expense of holding resources longer.";
}
}
case periodic-connection {
container periodic {
presence "Indicates that a periodic connection is
to be maintained.";
description
"Periodically connect to the NETCONF client.
This connection type increases resource
utilization, albeit with increased delay in
NETCONF client to NETCONF client interactions.
The NETCONF client SHOULD gracefully close the
connection using upon completing
planned activities. If the NETCONF session is
not closed gracefully, the NETCONF server MUST
immediately attempt to reestablish the connection.
In the case that the previous connection is still
active (i.e., the NETCONF client has not closed
it yet), establishing a new connection is NOT
RECOMMENDED.";
leaf period {
type uint16;
units "minutes";
default "60";
description
"Duration of time between periodic connections.";
}
leaf anchor-time {
type yang:date-and-time {
// constrained to minute-level granularity
pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}'
+ '(Z|[\+\-]\d{2}:\d{2})';
}
description
"Designates a timestamp before or after which a
series of periodic connections are determined.
The periodic connections occur at a whole
multiple interval from the anchor time. For
example, for an anchor time is 15 minutes past
midnight and a period interval of 24 hours, then
a periodic connection will occur 15 minutes past
midnight everyday.";
}
leaf idle-timeout {
type uint16;
units "seconds";
default "120"; // two minutes
description
"Specifies the maximum number of seconds that
a NETCONF session may remain idle. A NETCONF
session will be dropped if it is idle for an
interval longer than this number of seconds.
If set to zero, then the server will never
drop a session because it is idle.";
}
}
} // case periodic-connection
} // choice connection-type
} // container connection-type
container reconnect-strategy {
description
"The reconnection strategy directs how a NETCONF server
reconnects to a NETCONF client, after discovering its
connection to the client has dropped, even if due to a
reboot. The NETCONF server starts with the specified
endpoint and tries to connect to it max-attempts times
before trying the next endpoint in the list (round
robin).";
leaf start-with {
type enumeration {
enum first-listed {
description
"Indicates that reconnections should start with
the first endpoint listed.";
}
enum last-connected {
description
"Indicates that reconnections should start with
the endpoint last connected to. If no previous
connection has ever been established, then the
first endpoint configured is used. NETCONF
servers SHOULD be able to remember the last
endpoint connected to across reboots.";
}
enum random-selection {
description
"Indicates that reconnections should start with
a random endpoint.";
}
}
default "first-listed";
description
"Specifies which of the NETCONF client's endpoints
the NETCONF server should start with when trying
to connect to the NETCONF client.";
}
leaf max-attempts {
type uint8 {
range "1..max";
}
default "3";
description
"Specifies the number times the NETCONF server tries
to connect to a specific endpoint before moving on
to the next endpoint in the list (round robin).";
}
} // container reconnect-strategy
} // list netconf-client
} // container call-home
} // grouping netconf-server-app-grouping
// Protocol accessible node for servers that implement this module.
container netconf-server {
if-feature central-netconf-server-supported;
uses netconf-server-app-grouping;
description
"Top-level container for NETCONF server configuration.";
}
}
]]><CODE ENDS>Security ConsiderationsThe "ietf-netconf-client" YANG ModuleThe "ietf-netconf-client" YANG module defines data nodes
that are 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.None of the readable data nodes defined in this YANG module are
considered sensitive or vulnerable in network environments.
The NACM "default-deny-all" extension has not been set for
any data nodes defined in this module.None of the writable data nodes defined in this YANG module are
considered sensitive or vulnerable in network environments.
The NACM "default-deny-write" extension has not been set for
any data nodes defined in this module.This module does not define any RPCs, actions, or notifications,
and thus the security consideration for such is not provided here.Please be aware that this module uses groupings defined in
other RFCs that define data nodes that do set the NACM "default-deny-all"
and "default-deny-write" extensions.The "ietf-netconf-server" YANG ModuleThe "ietf-netconf-server" YANG module defines data nodes
that are 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.None of the readable data nodes defined in this YANG module are
considered sensitive or vulnerable in network environments.
The NACM "default-deny-all" extension has not been set for
any data nodes defined in this module.None of the writable data nodes defined in this YANG module are
considered sensitive or vulnerable in network environments.
The NACM "default-deny-write" extension has not been set for
any data nodes defined in this module.This module does not define any RPCs, actions, or notifications,
and thus the security consideration for such is not provided here.Please be aware that this module uses groupings defined in
other RFCs that define data nodes that do set the NACM "default-deny-all"
and "default-deny-write" extensions.IANA ConsiderationsThe "IETF XML" RegistryThis document registers two URIs in the "ns" subregistry of the IETF XML
Registry . Following the format in
, the following registrations are
requested:The "YANG Module Names" RegistryThis document registers two YANG modules in the
YANG Module Names registry .
Following the format in , the
following registrations are requested:ReferencesNormative ReferencesKey words for use in RFCs to Indicate Requirement LevelsIn 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.YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]Network Configuration Protocol (NETCONF)The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network 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]Using the NETCONF Protocol over Secure Shell (SSH)This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]Common YANG Data TypesThis document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021.A YANG Data Model for SNMP ConfigurationThis document defines a collection of YANG definitions for configuring SNMP engines.Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 AuthenticationThe Network Configuration Protocol (NETCONF) provides mechanisms to install, manipulate, and delete the configuration of network devices. This document describes how to use the Transport Layer Security (TLS) protocol with mutual X.509 authentication to secure the exchange of NETCONF messages. This revision of RFC 5539 documents the new message framing used by NETCONF 1.1 and it obsoletes RFC 5539.The YANG 1.1 Data Modeling LanguageYANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network 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).Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsRFC 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.Informative ReferencesThe IETF XML RegistryThis 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.RESTCONF ProtocolThis 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).NETCONF Call Home and RESTCONF Call HomeThis RFC presents NETCONF Call Home and RESTCONF Call Home, which enable a NETCONF or RESTCONF server to initiate a secure connection to a NETCONF or RESTCONF client, respectively.YANG Tree DiagramsThis document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.Network Configuration Access Control ModelThe 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.This document obsoletes RFC 6536.Network Management Datastore Architecture (NMDA)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.Change Log00 to 01
Renamed "keychain" to "keystore".
01 to 02
Added to ietf-netconf-client ability to connected to a cluster
of endpoints, including a reconnection-strategy.
Added to ietf-netconf-client the ability to configure connection-type
and also keep-alive strategy.
Updated both modules to accommodate new groupings in the ssh/tls
drafts.
02 to 03
Refined use of tls-client-grouping to add a must statement
indicating that the TLS client must specify a client-certificate.
Changed 'netconf-client' to be a grouping (not a container).
03 to 04
Added RFC 8174 to Requirements Language Section.
Replaced refine statement in ietf-netconf-client
to add a mandatory true.
Added refine statement in ietf-netconf-server
to add a must statement.
Now there are containers and groupings, for both the
client and server models.
04 to 05
Now tree diagrams reference ietf-netmod-yang-tree-diagrams
Updated examples to inline key and certificates (no longer
a leafref to keystore)
05 to 06
Fixed change log missing section issue.
Updated examples to match latest updates to the crypto-types,
trust-anchors, and keystore drafts.
Reduced line length of the YANG modules to fit within 69 columns.
06 to 07
Removed "idle-timeout" from "persistent" connection config.
Added "random-selection" for reconnection-strategy's "starts-with" enum.
Replaced "connection-type" choice default (persistent) with "mandatory true".
Reduced the periodic-connection's "idle-timeout" from 5 to 2 minutes.
Replaced reconnect-timeout with period/anchor-time combo.
07 to 08
Modified examples to be compatible with new crypto-types algs
08 to 09
Corrected use of "mandatory true" for "address" leafs.
Updated examples to reflect update to groupings defined in the keystore draft.
Updated to use groupings defined in new TCP and HTTP drafts.
Updated copyright date, boilerplate template, affiliation, and folding algorithm.
09 to 10
Reformatted YANG modules.
10 to 11
Adjusted for the top-level "demux container" added to groupings
imported from other modules.
Added "must" expressions to ensure that keepalives are not configured
for "periodic" connections.
Updated the boilerplate text in module-level "description" statement
to match copyeditor convention.
Moved "expanded" tree diagrams to the Appendix.
11 to 12
Removed the "Design Considerations" section.
Removed the 'must' statement limiting keepalives in periodic
connections.
Updated models and examples to reflect removal of the "demux"
containers in the imported models.
Updated the "periodic-connnection" description statements to be more
like the RESTCONF draft, especially where it described dropping the
underlying TCP connection.
Updated text to better reference where certain examples come from
(e.g., which Section in which draft).
In the server model, commented out the "must 'pinned-ca-certs or
pinned-client-certs'" statement to reflect change made in the
TLS draft whereby the trust anchors MAY be defined externally.
Replaced the 'listen', 'initiate', and 'call-home' features
with boolean expressions.
12 to 13
Updated to reflect changes in trust-anchors drafts
(e.g., s/trust-anchors/truststore/g + s/pinned.//)
13 to 14
Adjusting from change in TLS client model (removing the top-level
'certificate' container), by swapping refining-in a 'mandatory true'
statement with a 'must' statement outside the 'uses' statement.
Updated examples to reflect ietf-crypto-types change
(e.g., identities --> enumerations)
14 to 15
Refactored both the client and server modules similar to how the ietf-restconf-server
module was refactored in -13 of that draft, and the ietf-restconf-client grouping.
15 to 16
Added refinement to make "cert-to-name/fingerprint" be mandatory false.
Commented out refinement to "tls-server-grouping/client-authentication"
until a better "must" expression is defined.
16 to 17
Updated examples to include the "*-key-format" nodes.
Updated examples to remove the "required" nodes.
Updated examples to remove the "client-auth-defined-elsewhere" nodes.
17 to 18
Updated examples to reflect new "bag" addition to truststore.
18 to 19
Updated examples to remove the 'algorithm' nodes.
Updated examples to reflect the new TLS keepalives structure.
Added keepalives to the tcp-client-parameters section in the netconf-server SSH-based call-home example.
Added a TLS-based call-home example to the netconf-client example.
Added a "Note to Reviewers" note to first page.
19 to 20
Expanded "Data Model Overview section(s) [remove "wall" of tree diagrams].
Removed expanded tree diagrams that were listed in the Appendix.
Updated the Security Considerations section.
20 to 21
Cleaned up titles in the IANA Considerations section
Fixed issues found by the SecDir review of the "keystore" draft.
21 to 22
Addressed comments raised by YANG Doctor in the ct/ts/ks drafts.
22 to 23
Floated an 'if-feature' statement in a grouping down to where the grouping is used.
Clarified 'client-identity-mappings' for both the SSH and TLS transports.
For netconf-client, augmented-in a 'mapping-required' flag into 'client-identity-mappings'
only for the SSH transport, and refined-in a 'min-elements 1' only for the TLS transport.
Aligned modules with `pyang -f` formatting.
23 to 24
Replaced "base64encodedvalue==" with "BASE64VALUE=" in examples.
Minor editorial nits
24 to 25
Fixed up the 'WG Web' and 'WG List' lines in YANG module(s)
Fixed up copyright (i.e., s/Simplified/Revised/) in YANG module(s)
25 to 26
Added feature "central-netconf-client-supported" to top-level node "netconf-client".
Added feature "central-netconf-server-supported" to top-level node "netconf-server".
Removed unneccesary "xmlns:x509c2n" NETCONF server configuration example.
AcknowledgementsThe authors would like to thank for following for
lively discussions on list and in the halls (ordered
by first name):
Alan Luchuk,
Andy Bierman,
Balazs Kovacs,
Benoit Claise,
Bert Wijnen,
David Lamparter,
Juergen Schoenwaelder,
Ladislav Lhotka,
Martin Bjoerklund,
Mehmet Ersue,
Phil Shafer,
Radek Krejci,
Ramkumar Dhanapal,
Sean Turner,
and Tom Petch.