NETCONF Working Group                                          K. Watsen
Internet-Draft                                           Watsen Networks
Intended status: Standards Track                            May 20,                             8 July 2020
Expires: November 21, 2020 9 January 2021

                   RESTCONF Client and Server Models
              draft-ietf-netconf-restconf-client-server-19
              draft-ietf-netconf-restconf-client-server-20

Abstract

   This document defines two YANG modules, one module to configure a
   RESTCONF client and the other module to configure a RESTCONF server.
   Both modules support the TLS transport protocol with both standard
   RESTCONF and RESTCONF 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):

   o

   *  "AAAA" --> the assigned RFC value for draft-ietf-netconf-crypto-
      types

   o

   *  "BBBB" --> the assigned RFC value for draft-ietf-netconf-trust-
      anchors

   o

   *  "CCCC" --> the assigned RFC value for draft-ietf-netconf-keystore

   o

   *  "DDDD" --> the assigned RFC value for draft-ietf-netconf-tcp-
      client-server

   o

   *  "EEEE" --> the assigned RFC value for draft-ietf-netconf-ssh-
      client-server

   o

   *  "FFFF" --> the assigned RFC value for draft-ietf-netconf-tls-
      client-server

   o

   *  "GGGG" --> the assigned RFC value for draft-ietf-netconf-http-
      client-server

   o

   *  "HHHH" --> the assigned RFC value for draft-ietf-netconf-netconf-
      client-server

   o

   *  "IIII" --> the assigned RFC value for this draft

   Artwork in this document contains placeholder values for the date of
   publication of this draft.  Please apply the following replacement:

   o  "2020-05-20"

   *  "2020-07-08" --> the publication date of this draft

   The following Appendix section is to be removed prior to publication:

   o

   *  Appendix B.  Change Log

Note to Reviewers (To be removed by RFC Editor)

   This document presents a YANG module or modules that is/are part of a
   collection of drafts that work together to produce the ultimate goal
   of the NETCONF WG: to define configuration modules for NETCONF client
   and servers, and RESTCONF client and servers.

   The relationship between the various drafts in the collection is
   presented in the below diagram.

                                  crypto-types
                                    ^      ^
                                   /        \
                                  /          \
                       trust-anchors        keystore
                         ^     ^              ^  ^
                         |     +---------+    |  |
                         |               |    |  |
                         |       +------------+  |
   tcp-client-server     |      /        |       |
      ^    ^        ssh-client-server    |       |
      |    |           ^            tls-client-server
      |    |           |              ^     ^        http-client-server
      |    |           |              |     |                 ^
      |    |           |        +-----+     +---------+       |
      |    |           |        |                     |       |
      |    +-----------|--------|--------------+      |       |
      |                |        |              |      |       |
      +-----------+    |        |              |      |       |
                  |    |        |              |      |       |
                  |    |        |              |      |       |
               netconf-client-server       restconf-client-server

   Full draft names and link to drafts:

   o  draft-ietf-netconf-crypto-types (html [1])

   o  draft-ietf-netconf-trust-anchors (html [2])

   o  draft-ietf-netconf-keystore (html [3])

   o  draft-ietf-netconf-tcp-client-server (html [4])

   o  draft-ietf-netconf-ssh-client-server (html [5])

   o  draft-ietf-netconf-tls-client-server (html [6])

   o  draft-ietf-netconf-http-client-server (html [7])

   o  draft-ietf-netconf-netconf-client-server (html [8])

   o  draft-ietf-netconf-restconf-client-server (html [9])

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 21, 2020. 9 January 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5   4
     1.1.  Terminology  Relation to other RFCs  . . . . . . . . . . . . . . . . .   4
     1.2.  Specification Language  . . . . . . . . . . . . . . . . .   5
   2.  The RESTCONF Client Model
     1.3.  Adherence to the NMDA . . . . . . . . . . . . . . . . . .   5
     2.1.  Tree Diagram
   2.  The "ietf-restconf-client" Module . . . . . . . . . . . . . .   5
     2.1.  Data Model Overview . . . . . . . . .   5 . . . . . . . . . .   6
     2.2.  Example Usage . . . . . . . . . . . . . . . . . . . . . .   7  10
     2.3.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .  10  14
   3.  The RESTCONF Server Model . . . . "ietf-restconf-server" Module . . . . . . . . . . . . . .  21  24
     3.1.  Tree Diagram  . . .  Data Model Overview . . . . . . . . . . . . . . . . . . .  21  24
     3.2.  Example Usage . . . . . . . . . . . . . . . . . . . . . .  23  29
     3.3.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .  27  33
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  39  45
     4.1.  The "ietf-restconf-client" YANG Module  . . . . . . . . .  45
     4.2.  The "ietf-restconf-server" YANG Module  . . . . . . . . .  45
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  40  46
     5.1.  The IETF XML Registry . . . . . . . . . . . . . . . . . .  40  46
     5.2.  The YANG Module Names Registry  . . . . . . . . . . . . .  40  46
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  41  47
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  41  47
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  42
     6.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  42  48
   Appendix A.  Expanded Tree Diagrams . . . . . . . . . . . . . . .  44  49
     A.1.  Expanded Tree Diagram for 'ietf-restconf-client'  . . . .  44  50
     A.2.  Expanded Tree Diagram for 'ietf-restconf-server'  . . . .  76  50
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  89  50
     B.1.  00 to 01  . . . . . . . . . . . . . . . . . . . . . . . .  89  50
     B.2.  01 to 02  . . . . . . . . . . . . . . . . . . . . . . . .  89  50
     B.3.  02 to 03  . . . . . . . . . . . . . . . . . . . . . . . .  89  50
     B.4.  03 to 04  . . . . . . . . . . . . . . . . . . . . . . . .  90  51
     B.5.  04 to 05  . . . . . . . . . . . . . . . . . . . . . . . .  90  51
     B.6.  05 to 06  . . . . . . . . . . . . . . . . . . . . . . . .  90  51
     B.7.  06 to 07  . . . . . . . . . . . . . . . . . . . . . . . .  90  51
     B.8.  07 to 08  . . . . . . . . . . . . . . . . . . . . . . . .  91  52
     B.9.  08 to 09  . . . . . . . . . . . . . . . . . . . . . . . .  91  52
     B.10. 09 to 10  . . . . . . . . . . . . . . . . . . . . . . . .  91  52
     B.11. 10 to 11  . . . . . . . . . . . . . . . . . . . . . . . .  91  52
     B.12. 11 to 12  . . . . . . . . . . . . . . . . . . . . . . . .  91  52
     B.13. 12 to 13  . . . . . . . . . . . . . . . . . . . . . . . .  92  53
     B.14. 13 to 14  . . . . . . . . . . . . . . . . . . . . . . . .  92  53
     B.15. 14 to 15  . . . . . . . . . . . . . . . . . . . . . . . .  92  53
     B.16. 15 to 16  . . . . . . . . . . . . . . . . . . . . . . . .  93  54
     B.17. 16 to 17  . . . . . . . . . . . . . . . . . . . . . . . .  93  54
     B.18. 17 to 18  . . . . . . . . . . . . . . . . . . . . . . . .  93  54
     B.19. 18 to 19  . . . . . . . . . . . . . . . . . . . . . . . .  93  54
     B.20. 19 to 20  . . . . . . . . . . . . . . . . . . . . . . . .  54
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  93  55
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  93  55

1.  Introduction

   This document defines two YANG [RFC7950] modules, one module to
   configure a RESTCONF client and the other module to configure a
   RESTCONF server [RFC8040].  Both modules support the TLS [RFC8446]
   transport protocol with both standard RESTCONF and RESTCONF Call Home
   connections [RFC8071].

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this  Relation to other RFCs

   This document presents one or more YANG modules [RFC7950] that are
   part of a collection of RFCs that work together to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, define
   configuration modules for clients and servers of both the NETCONF
   [RFC6241] and only when, they appear in all
   capitals, as shown here.

2.  The RESTCONF Client Model [RFC8040] protocols.

   The RESTCONF client model presented modules have been defined in this section supports both
   clients initiating connections to servers, as well as clients
   listening for connections from servers calling home.

   YANG feature statements are used a modular fashion to enable implementations to
   advertise which potentially uncommon parts their
   use by other efforts, some of which are known to be in progress at
   the model the RESTCONF
   client supports.

2.1.  Tree Diagram

   The following tree diagram [RFC8340] provides an overview time of this writing, with many more expected to be defined in
   time.

   The relationship between the data
   model for various RFCs in the "ietf-restconf-client" module.

   This tree diagram only shows collection is
   presented in the nodes defined below diagram.  The labels in this module; it
   does show the nodes defined by "grouping" statements used by this
   module.

   Please see Appendix A.1 for a tree diagram that illustrates what represent
   the
   module looks like with all primary purpose provided by each RFC.  Links the "grouping" statements expanded.

   module: ietf-restconf-client
     +--rw restconf-client
        +---u restconf-client-app-grouping

     grouping restconf-client-grouping
     grouping restconf-client-initiate-stack-grouping
       +-- (transport)
          +--:(https) {https-initiate}?
             +-- https
                +-- tcp-client-parameters each RFC are
   provided below the diagram.

                                  crypto-types
                                    ^      ^
                                   /        \
                                  /          \
                         truststore         keystore
                          ^     ^             ^  ^
                          |  +---u tcpc:tcp-client-grouping
                +-- tls-client-parameters     +---------+   |  +---u tlsc:tls-client-grouping
                +-- http-client-parameters  |  +---u httpc:http-client-grouping
                +-- restconf-client-parameters
     grouping restconf-client-listen-stack-grouping
       +-- (transport)
          +--:(http) {http-listen}?
                          |  +-- http               |     +-- tcp-server-parameters   |  |  +---u tcps:tcp-server-grouping
                          |     +-- http-client-parameters      +------------+  |
   tcp-client-server      |  +---u httpc:http-client-grouping     /         |     +-- restconf-client-parameters
          +--:(https) {https-listen}?
             +-- https
                +-- tcp-server-parameters      |  +---u tcps:tcp-server-grouping
                +-- tls-client-parameters
      ^    ^        ssh-client-server     |  +---u tlsc:tls-client-grouping
                +-- http-client-parameters      |  +---u httpc:http-client-grouping
                +-- restconf-client-parameters
     grouping restconf-client-app-grouping
       +-- initiate! {https-initiate}?
      |  +-- restconf-server* [name]    |     +-- name?                 string           ^            tls-client-server
      |     +-- endpoints    |           |  +-- endpoint* [name]              ^     ^        http-client-server
      |    |     +-- name?                                      string           |              |     +---u restconf-client-initiate-stack-grouping     |     +-- connection-type                 ^
      |    |  +-- (connection-type)           |        +-----+     +---------+       |     +--:(persistent-connection)
      |    |           |  +-- persistent!        |                     |     +--:(periodic-connection)       |
      |        +-- periodic!    +-----------|--------|--------------+      |       |           +-- period?         uint16
      |                |           +-- anchor-time?    yang:date-and-time        |              |           +-- idle-timeout?   uint16      |     +-- reconnect-strategy       |        +-- start-with?     enumeration
      +-----------+    |        +-- max-attempts?   uint8
       +-- listen! {http-listen or https-listen}?
          +-- idle-timeout?   uint16
          +-- endpoint* [name]
             +-- name?                                    string
             +---u restconf-client-listen-stack-grouping

2.2.  Example Usage

   The following example illustrates configuring a RESTCONF client to
   initiate connections, as well as listening for call-home connections.

   This example is consistent with the examples presented        |              |      |       |
                  |    |        |              |      |       |
                  |    |        |              |      |       |
               netconf-client-server       restconf-client-server

   +=======================+===========================================+
   | Label in Section 2
   of Diagram      | Originating RFC                           |
   +=======================+===========================================+
   | crypto-types          | [I-D.ietf-netconf-crypto-types]           |
   +-----------------------+-------------------------------------------+
   | truststore            | [I-D.ietf-netconf-trust-anchors] and Section 3.2 of
   [I-D.ietf-netconf-keystore].

   ========== NOTE: '\' line wrapping per BCP XXX (RFC XXXX) ===========

   <restconf-client
     xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-client"
     xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">

     <!-- RESTCONF servers to initiate connections to -->
     <initiate>
       <restconf-server>
         <name>corp-fw1</name>
         <endpoints>
           <endpoint>
             <name>corp-fw1.example.com</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>corp-fw1.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-client-parameters>
                 <client-identity>
                   <certificate>
                     <local-definition>
                       <public-key-format>ct:subject-public-key-info-fo\
   rmat</public-key-format>
                       <public-key>base64encodedvalue==</public-key>
                       <private-key-format>ct:rsa-private-key-format</p\
   rivate-key-format>
                       <private-key>base64encodedvalue==</private-key>
                       <cert>base64encodedvalue==</cert>
                     </local-definition>
                   </certificate>

                 </client-identity>
                 <server-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-server-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-server-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </server-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-client-parameters>
               <http-client-parameters>
                 <client-identity>
                   <basic>
                     <user-id>bob</user-id>
                     <password>secret</password>
                   </basic>
                 </client-identity>
               </http-client-parameters>
             </https>
           </endpoint>
           <endpoint>
             <name>corp-fw2.example.com</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>corp-fw2.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-client-parameters>
                 <client-identity>
                   <certificate>
                     <local-definition>
                       <public-key-format>ct:subject-public-key-info-fo\
   rmat</public-key-format>
                       <public-key>base64encodedvalue==</public-key>
                       <private-key-format>ct:rsa-private-key-format</p\
   rivate-key-format>
                       <private-key>base64encodedvalue==</private-key>
                       <cert>base64encodedvalue==</cert>
                     </local-definition>
                   </certificate>
                 </client-identity>
                 <server-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-server-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-server-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </server-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-client-parameters>
               <http-client-parameters>
                 <client-identity>
                   <basic>
                     <user-id>bob</user-id>
                     <password>secret</password>
                   </basic>
                 </client-identity>
               </http-client-parameters>
             </https>
           </endpoint>
         </endpoints>
         <connection-type>
           <persistent/>
         </connection-type>
       </restconf-server>
     </initiate>

     <!-- endpoints          |
   +-----------------------+-------------------------------------------+
   | keystore              | [I-D.ietf-netconf-keystore]               |
   +-----------------------+-------------------------------------------+
   | tcp-client-server     | [I-D.ietf-netconf-tcp-client-server]      |
   +-----------------------+-------------------------------------------+
   | ssh-client-server     | [I-D.ietf-netconf-ssh-client-server]      |
   +-----------------------+-------------------------------------------+
   | tls-client-server     | [I-D.ietf-netconf-tls-client-server]      |
   +-----------------------+-------------------------------------------+
   | http-client-server    | [I-D.ietf-netconf-http-client-server]     |
   +-----------------------+-------------------------------------------+
   | netconf-client-server | [I-D.ietf-netconf-netconf-client-server]  |
   +-----------------------+-------------------------------------------+
   |restconf-client-server | [I-D.ietf-netconf-restconf-client-server] |
   +-----------------------+-------------------------------------------+

                       Table 1: Label to listen for RESTCONF Call Home connections on -->
     <listen>
       <endpoint>
         <name>Intranet-facing listener</name>
         <https>
           <tcp-server-parameters>
             <local-address>11.22.33.44</local-address>
           </tcp-server-parameters>
           <tls-client-parameters>
             <client-identity>
               <certificate>
                 <local-definition>
                   <public-key-format>ct:subject-public-key-info-format\
   </public-key-format>
                   <public-key>base64encodedvalue==</public-key>
                   <private-key-format>ct:rsa-private-key-format</priva\
   te-key-format>
                   <private-key>base64encodedvalue==</private-key>
                   <cert>base64encodedvalue==</cert>
                 </local-definition>
               </certificate>
             </client-identity>
             <server-authentication>
               <ca-certs>
                 <truststore-reference>trusted-server-ca-certs</trustst\
   ore-reference>
               </ca-certs>
               <ee-certs>
                 <truststore-reference>trusted-server-ee-certs</trustst\
   ore-reference>
               </ee-certs>
             </server-authentication>
             <keepalives>
               <peer-allowed-to-send/>
             </keepalives>
           </tls-client-parameters>
           <http-client-parameters>
             <client-identity>
               <basic>
                 <user-id>bob</user-id>
                 <password>secret</password>
               </basic>
             </client-identity>
           </http-client-parameters>
         </https>
       </endpoint>
     </listen>
   </restconf-client>

2.3.  YANG Module

   This YANG module has normative references RFC Mapping

1.2.  Specification Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to [RFC6991], [RFC8040], be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and [RFC8071], [I-D.kwatsen-netconf-tcp-client-server],
   [I-D.ietf-netconf-tls-client-server], only when, they appear in all
   capitals, as shown here.

1.3.  Adherence to the NMDA

   This document in compliant with the Network Management Datastore
   Architecture (NMDA) [RFC8342].  For instance, as described in
   [I-D.ietf-netconf-trust-anchors] and
   [I-D.kwatsen-netconf-http-client-server].

   <CODE BEGINS> file "ietf-restconf-client@2020-05-20.yang"
   module ietf-restconf-client {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-client";
     prefix rcc;

     import ietf-yang-types {
       prefix yang;
       reference
         "RFC 6991: Common YANG Data Types";
     }

     import ietf-tcp-client {
       prefix tcpc;
       reference
         "RFC DDDD: YANG Groupings for TCP Clients and TCP Servers";
     }

     import ietf-tcp-server {
       prefix tcps;
       reference
         "RFC DDDD: YANG Groupings for TCP Clients [I-D.ietf-netconf-keystore],
   trust anchors and TCP Servers";
     }

     import ietf-tls-client {
       prefix tlsc;
       reference
         "RFC FFFF: YANG Groupings keys installed during manufacturing are expected to
   appear in <operational>.

2.  The "ietf-restconf-client" Module

   The RESTCONF client model presented in this section supports both
   clients initiating connections to servers, as well as clients
   listening for TLS Clients and TLS Servers";
     }

     import ietf-http-client {
       prefix httpc;
       reference
         "RFC GGGG: connections from servers calling home.

   YANG Groupings for HTTP Clients and HTTP Servers";
     }

     organization
       "IETF NETCONF (Network Configuration) Working Group";

     contact
       "WG Web:   <http://datatracker.ietf.org/wg/netconf/>
        WG List:  <mailto:netconf@ietf.org>
        Author:   Kent Watsen <mailto:kent+ietf@watsen.net>
        Author:   Gary Wu <mailto:garywu@cisco.com>";

     description
       "This module contains a collection feature statements are used to enable implementations to
   advertise which potentially uncommon parts of YANG definitions
        for configuring RESTCONF clients.

        Copyright (c) 2020 IETF Trust and the persons identified
        as authors of model the code. All rights reserved.

        Redistribution and use RESTCONF
   client supports.

2.1.  Data Model Overview

2.1.1.  Features

   The following diagram lists all the "feature" statements defined in source and binary forms, with
        or without modification, is permitted pursuant to, and
        subject to
   the license terms contained in, "ietf-restconf-client" module:

   Features:
     +-- https-initiate
     +-- http-listen
     +-- https-listen

2.1.2.  Groupings

   The following diagram lists all the Simplified
        BSD License set forth "grouping" statements defined in Section 4.c
   the "ietf-restconf-client" module:

   Groupings:
     +-- restconf-client-grouping
     +-- restconf-client-initiate-stack-grouping
     +-- restconf-client-listen-stack-grouping
     +-- restconf-client-app-grouping

   Each of these groupings are presented in the IETF Trust's
        Legal Provisions Relating to IETF Documents
        (https://trustee.ietf.org/license-info). following subsections.

2.1.2.1.  The "restconf-client-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the "restconf-
   client-grouping" grouping:

     grouping restconf-client-grouping ---> <empty>

   Comments:

   *  This version of this YANG module grouping does not define any nodes, but is maintained so that
      downstream modules can augment nodes into it if needed.

   *  The "restconf-client-grouping" defines, if it can be called that,
      the configuration for just "RESTCONF" part of RFC IIII
        (https://www.rfc-editor.org/info/rfcIIII); a protocol stack.
      It does not, for instance, define any configuration for the "TCP",
      "TLS", or "HTTP" protocol layers (for that, see Section 2.1.2.2
      and Section 2.1.2.3).

2.1.2.2.  The "restconf-client-initiate-stack-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the RFC
        itself "restconf-
   client-initiate-stack-grouping" grouping:

     grouping restconf-client-initiate-stack-grouping
       +-- (transport)
          +--:(https) {https-initiate}?
             +-- https
                +-- tcp-client-parameters
                |  +---u tcpc:tcp-client-grouping
                +-- tls-client-parameters
                |  +---u tlsc:tls-client-grouping
                +-- http-client-parameters
                |  +---u httpc:http-client-grouping
                +-- restconf-client-parameters
                   +---u rcc:restconf-client-grouping

   Comments:

   *  The "restconf-client-initiate-stack-grouping" defines the
      configuration for a full legal notices.

        The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
        'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
        'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
        are to be interpreted as described in BCP 14 (RFC 2119)
        (RFC 8174) when, and only when, they appear in all
        capitals, as shown here.";

     revision 2020-05-20 {
       description
         "Initial version";
       reference
         "RFC IIII: RESTCONF Client and Server Models";
     }

     // Features

     feature https-initiate {
       description
         "The 'https-initiate' feature indicates that the protocol stack, for RESTCONF
          client supports initiating HTTPS
      clients that initiate connections to RESTCONF
          servers. This feature exists servers, as HTTPS might not be a
          mandatory to implement transport in the future.";
       reference
         "RFC 8040: RESTCONF Protocol";
     }

     feature http-listen {
       description
         "The 'https-listen' feature indicates that the RESTCONF client
          supports opening a port opposed
      to listen for incoming RESTCONF
          server receiving call-home [RFC8071] connections.

   *  The "transport" choice node enables transport options to be
      configured.  This feature exists as not
          all RESTCONF clients may support RESTCONF call home.";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";

     }

     feature https-listen {
       description
         "The 'https-listen' feature indicates that document only defines an "https" option, but
      other options MAY be augmented in.

   *  For the RESTCONF client
          supports opening a port to listen for incoming RESTCONF
          server call-home connections.  This feature exists as not
          all RESTCONF clients may support RESTCONF call home.";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
     }

     // Groupings referenced grouping restconf-client-grouping {
       description
         "A reusable statement(s):

      -  The "tcp-client-grouping" grouping for configuring a RESTCONF client
          without any consideration for how underlying transport
          sessions are established.

          This is discussed in
         Section 3.1.2.1 of [I-D.ietf-netconf-tcp-client-server].
      -  The "tls-client-grouping" grouping currently doesn't define any nodes.";
     } is discussed in
         Section 3.1.2.1 of [I-D.ietf-netconf-tls-client-server].
      -  The "http-client-grouping" grouping restconf-client-initiate-stack-grouping {
       description
         "A reusable is discussed in
         Section 2.1.2.2 of [I-D.ietf-netconf-http-client-server].
      -  The "restconf-client-grouping" grouping is discussed in
         Section 2.1.2.1 in this document.

2.1.2.3.  The "restconf-client-listen-stack-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the "restconf-
   client-listen-stack-grouping" grouping:

     grouping restconf-client-listen-stack-grouping
       +-- (transport)
          +--:(http) {http-listen}?
          |  +-- http
          |     +-- tcp-server-parameters
          |     |  +---u tcps:tcp-server-grouping
          |     +-- http-client-parameters
          |     |  +---u httpc:http-client-grouping
          |     +-- restconf-client-parameters
          |        +---u rcc:restconf-client-grouping
          +--:(https) {https-listen}?
             +-- https
                +-- tcp-server-parameters
                |  +---u tcps:tcp-server-grouping
                +-- tls-client-parameters
                |  +---u tlsc:tls-client-grouping
                +-- http-client-parameters
                |  +---u httpc:http-client-grouping
                +-- restconf-client-parameters
                   +---u rcc:restconf-client-grouping

   Comments:

   *  The "restconf-client-listen-stack-grouping" defines the
      configuration for configuring a full RESTCONF client
          'initiate' protocol stack stack, for a single connection."; RESTCONF
      clients that receive call-home [RFC8071] connections from RESTCONF
      servers.

   *  The "transport" choice transport {
         mandatory true;
         description
           "Selects between available transports. This is node enables both the HTTP and HTTPS
      transports to be configured, with each option enabled by a
            'choice' statement so as
      "feature" statement.  Note that RESTCONF requires HTTPS, the HTTP
      option is provided to support additional
            transport options to be augmented in.";
         case https {
           if-feature "https-initiate";
           container https {
             description
               "Specifies HTTPS-specific 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 "443";
                   description
                     "The RESTCONF client will attempt to
                      connect to the IANA-assigned well-known
                      port value for 'https' (443) if no value cases where a TLS-terminator 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 http-client-parameters {
               description
                 "A wrapper around
      deployed in front of the HTTP client parameters
                  to avoid name collisions.";
               uses httpc:http-client-grouping;
             }
             container restconf-client-parameters {
               description
                 "A wrapper around RESTCONF-client.

   *  For the HTTP client parameters
                  to avoid name collisions.";
               uses rcc:restconf-client-grouping;
             }
           }
         }
       }
     } // restconf-client-initiate-stack-grouping referenced grouping restconf-client-listen-stack-grouping {
       description
         "A reusable statement(s):

      -  The "tcp-server-grouping" grouping for configuring a RESTCONF client
          'listen' protocol stack for a single connection. is discussed in
         Section 4.1.2.1 of [I-D.ietf-netconf-tcp-client-server].
      -  The
          'listen' stack supports call home connections, as
          described "tls-client-grouping" grouping is discussed in RFC 8071";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
       choice transport {
         mandatory true;
         description
           "Selects between available transports. This
         Section 3.1.2.1 of [I-D.ietf-netconf-tls-client-server].
      -  The "http-client-grouping" grouping is a
            'choice' statement so as to support additional
            transport options to be augmented in.";
         case http {
           if-feature "http-listen";
           container http {
             description
               "HTTP-specific listening configuration for inbound
                connections.

                This transport option discussed in
         Section 2.1.2.2 of [I-D.ietf-netconf-http-client-server].
      -  The "restconf-client-grouping" grouping is made available to support
                deployments where discussed in
         Section 2.1.2.1 in this document.

2.1.2.4.  The "restconf-client-app-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the TLS connections are terminated
                by another system (e.g., a load balanacer) fronting
                the client.";
             container tcp-server-parameters {
               description
                 "A wrapper around "restconf-
   client-app-grouping" grouping:

     grouping restconf-client-app-grouping
       +-- initiate! {https-initiate}?
       |  +-- restconf-server* [name]
       |     +-- name?                 string
       |     +-- endpoints
       |     |  +-- endpoint* [name]
       |     |     +-- name?                                      string
       |     |     +---u restconf-client-initiate-stack-grouping
       |     +-- connection-type
       |     |  +-- (connection-type)
       |     |     +--:(persistent-connection)
       |     |     |  +-- persistent!
       |     |     +--:(periodic-connection)
       |     |        +-- periodic!
       |     |           +-- period?         uint16
       |     |           +-- anchor-time?    yang:date-and-time
       |     |           +-- idle-timeout?   uint16
       |     +-- reconnect-strategy
       |        +-- start-with?     enumeration
       |        +-- max-attempts?   uint8
       +-- listen! {http-listen or https-listen}?
          +-- idle-timeout?   uint16
          +-- endpoint* [name]
             +-- name?                                    string
             +---u restconf-client-listen-stack-grouping

   Comments:

   *  The "restconf-client-app-grouping" defines the TCP configuration for a
      RESTCONF client parameters that supports both initiating connections to avoid name collisions.";
               uses tcps:tcp-server-grouping {
                 refine "local-port" {
                   default "4336";
                   description
                     "The
      RESTCONF client will listen on servers as well as receiving call-home connections from
      RESTCONF servers.

   *  Both the IANA-
                      assigned well-known port for 'restconf-ch-tls'
                      (4336) if no value is specified.";
                 }
               }
             }
             container http-client-parameters {
               description
                 "A wrapper around "initiate" and "listen" subtrees must be enabled by
      "feature" statements.

   *  For the HTTP client parameters
                  to avoid name collisions.";
               uses httpc:http-client-grouping;
             }
             container restconf-client-parameters {
               description
                 "A wrapper around referenced grouping statement(s):

      -  The "restconf-client-initiate-stack-grouping" grouping is
         discussed in Section 2.1.2.2 in this document.
      -  The "restconf-client-listen-stack-grouping" grouping is
         discussed in Section 2.1.2.3 in this document.

2.1.3.  Protocol-accessible Nodes

   The following diagram lists all the RESTCONF client parameters
                  to avoid name collisions.";
               uses rcc:restconf-client-grouping;
             }
           }
         }
         case https {
           if-feature "https-listen";
           container https {
             description
               "HTTPS-specific listening configuration for inbound
                connections.";
             container tcp-server-parameters {
               description
                 "A wrapper around protocol-accessible nodes defined
   in the TCP client parameters
                  to avoid name collisions.";
               uses tcps:tcp-server-grouping {
                 refine "local-port" {
                   default "4336";
                   description
                     "The RESTCONF client will listen on "ietf-restconf-client" module:

   module: ietf-restconf-client
     +--rw restconf-client
        +---u restconf-client-app-grouping

   Comments:

   *  Protocol-accessible nodes are those nodes that are accessible when
      the IANA-
                      assigned well-known port for 'restconf-ch-tls'
                      (4336) if no value module is specified.";
                 }
               }
             }
             container tls-client-parameters {
               must 'client-identity' {
                 description
                   "NETCONF/TLS clients MUST pass some
                    authentication credentials.";
               }
               description
                 "A wrapper around "implemented", as described in Section 5.6.5 of
      [RFC7950].

   *  For the TLS client parameters
                  to avoid name collisions.";
               uses tlsc:tls-client-grouping;
             }
             container http-client-parameters {
               description
                 "A wrapper around "ietf-restconf-client" module, the HTTP client parameters
                  to avoid name collisions.";
               uses httpc:http-client-grouping;
             }
             container restconf-client-parameters {
               description
                 "A wrapper around protocol-accessible
      nodes are an instance of the RESTCONF client parameters "restconf-client-app-grouping"
      discussed in Section 2.1.2.4 grouping.

   *  The reason for why "restconf-client-app-grouping" exists separate
      from the protocol-accessible nodes definition is so as to avoid name collisions.";
               uses rcc:restconf-client-grouping;
             }
           }
         }
       }
     } // restconf-client-listen-stack-grouping

     grouping enable
      instances of restconf-client-app-grouping {
       description
         "A reusable grouping for to be instantiated in
      other locations, as may be needed or desired by some modules.

2.2.  Example Usage

   The following example illustrates configuring a RESTCONF client
          application that supports both 'initiate' and 'listen'
          protocol stacks for a multiplicity of connections.";
       container initiate {
         if-feature "https-initiate";
         presence "Enables client to
   initiate TCP connections";
         description
           "Configures client initiating underlying TCP connections.";
         list restconf-server {
           key "name";
           min-elements 1;
           description
             "List connections, as well as to listen for call-home connections.

   This example is consistent with the examples presented in Section 2.2
   of [I-D.ietf-netconf-trust-anchors] and Section 2.2 of
   [I-D.ietf-netconf-keystore].

   =============== NOTE: '\' line wrapping per RFC 8792 ================

   <restconf-client
     xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-client"
     xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">

     <!-- RESTCONF servers the RESTCONF client is to
              maintain simultaneous initiate connections with.";
           leaf name {
             type string;
             description
               "An arbitrary name for the RESTCONF server.";
           }
           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 to -->
     <initiate>
       <restconf-server>
         <name>corp-fw1</name>
         <endpoints>
           <endpoint>
             <name>corp-fw1.example.com</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>corp-fw1.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-client-parameters>
                 <client-identity>
                   <certificate>
                     <keystore-reference>
                       <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
   ey>
                       <certificate>ex-rsa-cert</certificate>
                     </keystore-reference>
                   </certificate>
                 </client-identity>
                 <server-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-server-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-server-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </server-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-client-parameters>
               <http-client-parameters>
                 <client-identity>
                   <basic>
                     <user-id>bob</user-id>
                     <password>secret</password>
                   </basic>
                 </client-identity>
               </http-client-parameters>
             </https>
           </endpoint>
           <endpoint>
             <name>corp-fw2.example.com</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>corp-fw2.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-client-parameters>
                 <client-identity>
                   <certificate>
                     <keystore-reference>
                       <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
   ey>
                       <certificate>ex-rsa-cert</certificate>
                     </keystore-reference>
                   </certificate>
                 </client-identity>
                 <server-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-server-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-server-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </server-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-client-parameters>
               <http-client-parameters>
                 <client-identity>
                   <basic>
                     <user-id>bob</user-id>
                     <password>secret</password>
                   </basic>
                 </client-identity>
               </http-client-parameters>
             </https>
           </endpoint>
         </endpoints>
         <connection-type>
           <persistent/>
         </connection-type>

       </restconf-server>
     </initiate>

     <!-- endpoints to listen for this RESTCONF client to try to connect Call Home connections on -->
     <listen>
       <endpoint>
         <name>Intranet-facing listener</name>
         <https>
           <tcp-server-parameters>
             <local-address>11.22.33.44</local-address>
           </tcp-server-parameters>
           <tls-client-parameters>
             <client-identity>
               <certificate>
                 <keystore-reference>
                   <asymmetric-key>rsa-asymmetric-key</asymmetric-key>
                   <certificate>ex-rsa-cert</certificate>
                 </keystore-reference>
               </certificate>
             </client-identity>
             <server-authentication>
               <ca-certs>
                 <truststore-reference>trusted-server-ca-certs</trustst\
   ore-reference>
               </ca-certs>
               <ee-certs>
                 <truststore-reference>trusted-server-ee-certs</trustst\
   ore-reference>
               </ee-certs>
             </server-authentication>
             <keepalives>
               <peer-allowed-to-send/>
             </keepalives>
           </tls-client-parameters>
           <http-client-parameters>
             <client-identity>
               <basic>
                 <user-id>bob</user-id>
                 <password>secret</password>
               </basic>
             </client-identity>
           </http-client-parameters>
         </https>
       </endpoint>
     </listen>
   </restconf-client>

2.3.  YANG Module

   This YANG module has normative references to in sequence.
                  Defining more than one enables high-availability.";
               leaf name [RFC6991], [RFC8040],
   and [RFC8071], [I-D.ietf-netconf-tcp-client-server],
   [I-D.ietf-netconf-tls-client-server], and
   [I-D.ietf-netconf-http-client-server].

   <CODE BEGINS> file "ietf-restconf-client@2020-07-08.yang"

   module ietf-restconf-client {
                 type string;
                 description
                   "An arbitrary name for this endpoint.";
               }
               uses restconf-client-initiate-stack-grouping;
             }
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-client";
     prefix rcc;

     import ietf-yang-types {
       prefix yang;
       reference
         "RFC 6991: Common YANG Data Types";
     }
           container connection-type

     import ietf-tcp-client {
             description
               "Indicates the RESTCONF client's preference
       prefix tcpc;
       reference
         "RFC DDDD: YANG Groupings for how
                the RESTCONF connection is maintained.";
             choice connection-type TCP Clients and TCP Servers";
     }

     import ietf-tcp-server {
               mandatory true;
               description
                 "Selects between available connection types.";
               case persistent-connection
       prefix tcps;
       reference
         "RFC DDDD: YANG Groupings for TCP Clients and TCP Servers";
     }

     import ietf-tls-client {
                 container persistent
       prefix tlsc;
       reference
         "RFC FFFF: YANG Groupings for TLS Clients and TLS Servers";
     }

     import ietf-http-client {
                   presence "Indicates that a persistent connection
                             is to be maintained.";
       prefix httpc;
       reference
         "RFC GGGG: YANG Groupings for HTTP Clients and HTTP Servers";
     }

     organization
       "IETF NETCONF (Network Configuration) Working Group";

     contact
       "WG Web:   <http://datatracker.ietf.org/wg/netconf/>
        WG List:  <mailto:netconf@ietf.org>
        Author:   Kent Watsen <mailto:kent+ietf@watsen.net>
        Author:   Gary Wu <mailto:garywu@cisco.com>";

     description
                     "Maintain
       "This module contains a persistent connection to the
                      RESTCONF server. If the connection goes down,
                      immediately start trying to reconnect to the
                      RESTCONF server, using the reconnection strategy.

                      This connection type minimizes any RESTCONF server
                      to collection of YANG definitions
        for configuring RESTCONF client data-transfer delay, albeit
                      at clients.

        Copyright (c) 2020 IETF Trust and the expense persons identified
        as authors of holding resources longer.";
                 }
               }
               case periodic-connection {
                 container periodic {
                   presence "Indicates that a periodic connection is
                             to be maintained.";
                   description
                     "Periodically connect to the RESTCONF server.

                      This connection type increases resource
                      utilization, albeit with increased delay code. All rights reserved.

        Redistribution and use in RESTCONF server source and binary forms, with
        or without modification, is permitted pursuant to, and
        subject to RESTCONF client
                      interactions.

                      The RESTCONF client SHOULD gracefully close the underlying TLS connection upon completing
                      planned activities.

                      In license terms contained in, the case that Simplified
        BSD License set forth in Section 4.c of 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 IETF Trust's
        Legal Provisions Relating 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 IETF Documents
        (https://trustee.ietf.org/license-info).

        This version of periodic connections are
                        determined.  The periodic connections occur
                        at a whole multiple interval from the anchor
                        time.  For example, for an anchor time this YANG module 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 part of seconds
                        that RFC IIII
        (https://www.rfc-editor.org/info/rfcIIII); see the underlying TCP session may remain
                        idle. A TCP session will be dropped if it
                        is idle RFC
        itself for an interval longer than full legal notices.

        The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
        'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
        'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this
                        number of seconds If set document
        are to zero, then the be interpreted as described in BCP 14 (RFC 2119)
        (RFC 8174) when, and only when, they appear in all
        capitals, as shown here.";

     revision 2020-07-08 {
       description
         "Initial version";
       reference
         "RFC IIII: RESTCONF client will never drop a session
                        because it is idle.";
                   }
                 }
               } // periodic-connection
             } // connection-type Client and Server Models";
     }

     // connection-type
           container reconnect-strategy Features

     feature https-initiate {
       description
         "The reconnection strategy directs how a RESTCONF
                client reconnects to a RESTCONF server, after
                discovering its connection to 'https-initiate' feature indicates that the server has
                dropped, even if due to a reboot.  The RESTCONF
          client starts with the specified endpoint and
                tries to connect supports initiating HTTPS connections 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. RESTCONF clients
                      SHOULD
          servers. This feature exists as HTTPS might not be able a
          mandatory to remember implement transport in the last
                      endpoint connected to across reboots."; future.";
       reference
         "RFC 8040: RESTCONF Protocol";
     }
                 enum random-selection
     feature http-listen {
       description
                     "Indicates
         "The 'https-listen' feature indicates that reconnections should start with
                      a random endpoint.";
                 }
               }
               default "first-listed";
               description
                 "Specifies which of the RESTCONF server's
                  endpoints the RESTCONF client should start
                  with when trying to connect
          supports opening a port to the listen for incoming RESTCONF
                  server.";
          server call-home connections.  This feature exists as not
          all RESTCONF clients may support RESTCONF call home.";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
     }
             leaf max-attempts {
               type uint8

     feature https-listen {
                 range "1..max";
               }
               default "3";
       description
                 "Specifies the number times
         "The 'https-listen' feature indicates that the RESTCONF client
                  tries to connect to
          supports opening a specific endpoint before
                  moving on port to the next endpoint in the list
                  (round robin).";
             }
           }
         }
       } // initiate
       container listen {
         if-feature "http-listen or https-listen";
         presence "Enables client to accept for incoming RESTCONF
          server call-home connections"; connections.  This feature exists as not
          all RESTCONF clients may support RESTCONF call home.";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
     }

     // Groupings

     grouping restconf-client-grouping {
       description
           "Configures the
         "A reusable grouping for configuring a RESTCONF client to accept call-home TCP connections.";
         leaf idle-timeout
          without any consideration for how underlying transport
          sessions are established.

          This grouping currently doesn't define any nodes.";
     }

     grouping restconf-client-initiate-stack-grouping {
           type uint16;
           units "seconds";
           default 3600; // one hour
       description
             "Specifies the maximum number of seconds that an
              underlying TCP session may remain idle. A TCP session
              will be dropped if it is idle
         "A reusable grouping for an interval longer
              then this number of seconds.  If set to zero, then
              the server will never drop configuring a session because it RESTCONF client
          'initiate' protocol stack for a single connection.";

       choice transport {
         mandatory true;
         description
           "Selects between available transports. This is
              idle.  Sessions that have a notification subscription
              active are never dropped.";
         }
         list endpoint
            'choice' statement so as to support additional
            transport options to be augmented in.";
         case https {
           key "name";
           min-elements 1;
           if-feature "https-initiate";
           container https {
             must 'tls-client-parameters/client-identity
                   or http-client-parameters/client-identity';
             description
             "List of endpoints
               "Specifies HTTPS-specific transport
                configuration.";
             container tcp-client-parameters {
               description
                 "A wrapper around the TCP client parameters
                  to listen for RESTCONF connections.";

           leaf avoid name collisions.";
               uses tcpc:tcp-client-grouping {
             type string;
                 refine "remote-port" {
                   default "443";
                   description
               "An arbitrary name for the
                     "The RESTCONF listen endpoint.";
           }
           uses restconf-client-listen-stack-grouping; client will attempt to
                      connect to the IANA-assigned well-known
                      port value for 'https' (443) if no value
                      is specified.";
                 }
               }
             } // restconf-client-app-grouping

     // Protocol accessible node, for servers that implement
     // this module.
             container restconf-client tls-client-parameters {
               description
                 "A wrapper around the TLS client parameters
                  to avoid name collisions.";
               uses restconf-client-app-grouping; tlsc:tls-client-grouping;
             }
             container http-client-parameters {
               description
         "Top-level
                 "A wrapper around the HTTP client parameters
                  to avoid name collisions.";
               uses httpc:http-client-grouping;
             }
             container for RESTCONF restconf-client-parameters {
               description
                 "A wrapper around the HTTP client configuration."; parameters
                  to avoid name collisions.";
               uses rcc:restconf-client-grouping;
             }
           }

   <CODE ENDS>

3.  The
         }
       }
     } // restconf-client-initiate-stack-grouping

     grouping restconf-client-listen-stack-grouping {
       description
         "A reusable grouping for configuring a RESTCONF Server Model client
          'listen' protocol stack for a single connection.  The RESTCONF server model presented in this section
          'listen' stack supports both
   listening for connections call home connections, as well
          described in RFC 8071";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";

       choice transport {
         mandatory true;
         description
           "Selects between available transports. This is a
            'choice' statement so as initiating call-home
   connections.

   YANG feature statements are used to enable implementations support additional
            transport options to
   advertise which potentially uncommon parts of the model the RESTCONF
   server supports.

3.1.  Tree Diagram

   The following tree diagram [RFC8340] provides an overview of the data
   model be augmented in.";
         case http {
           if-feature "http-listen";
           container http {
             description
               "HTTP-specific listening configuration for the "ietf-restconf-server" module. inbound
                connections.

                This tree diagram only shows the nodes defined in this module; it
   does show transport option is made available to support
                deployments where the nodes defined by "grouping" statements used TLS connections are terminated
                by this
   module.

   Please see Appendix A.2 for another system (e.g., a tree diagram that illustrates what the
   module looks like with all load balanacer) fronting
                the "grouping" statements expanded.

   module: ietf-restconf-server
     +--rw restconf-server
        +---u restconf-server-app-grouping

     grouping restconf-server-grouping
       +-- client-identity-mappings
          +---u x509c2n:cert-to-name
     grouping restconf-server-listen-stack-grouping
       +-- (transport)
          +--:(http) {http-listen}?
          |  +-- http
          |     +-- external-endpoint!
          |     |  +-- address    inet:ip-address
          |     |  +-- port?      inet:port-number
          |     +-- tcp-server-parameters
          |     |  +---u tcps:tcp-server-grouping
          |     +-- http-server-parameters
          |     |  +---u https:http-server-grouping
          |     +-- restconf-server-parameters
          |        +---u rcs:restconf-server-grouping
          +--:(https) {https-listen}?
             +-- https
                +-- client.";
             container tcp-server-parameters
                |  +---u {
               description
                 "A wrapper around the TCP client parameters
                  to avoid name collisions.";
               uses tcps:tcp-server-grouping
                +-- tls-server-parameters
                |  +---u tlss:tls-server-grouping
                +-- http-server-parameters
                |  +---u https:http-server-grouping
                +-- restconf-server-parameters
                   +---u rcs:restconf-server-grouping
     grouping restconf-server-callhome-stack-grouping
       +-- (transport)
          +--:(https) {https-listen}?
             +-- https
                +-- tcp-client-parameters
                |  +---u tcpc:tcp-client-grouping
                +-- tls-server-parameters
                |  +---u tlss:tls-server-grouping
                +-- http-server-parameters
                |  +---u https:http-server-grouping
                +-- restconf-server-parameters
                   +---u rcs:restconf-server-grouping
     grouping restconf-server-app-grouping
       +-- listen! {http-listen or https-listen}?
       |  +-- endpoint* [name]
       |     +-- name?                                    string
       |     +---u restconf-server-listen-stack-grouping
       +-- call-home! {https-call-home}?
          +-- restconf-client* [name]
             +-- name?                 string
             +-- endpoints
             |  +-- endpoint* [name]
             |     +-- name?                                      string
             |     +---u restconf-server-callhome-stack-grouping
             +-- connection-type
             |  +-- (connection-type)
             |     +--:(persistent-connection)
             |     |  +-- persistent!
             |     +--:(periodic-connection)
             |        +-- periodic!
             |           +-- period?         uint16
             |           +-- anchor-time?    yang:date-and-time
             |           +-- idle-timeout?   uint16
             +-- reconnect-strategy
                +-- start-with?     enumeration
                +-- max-attempts?   uint8

3.2.  Example Usage

   The following example illustrates configuring a {
                 refine "local-port" {
                   default "4336";
                   description
                     "The RESTCONF server to client will listen on the IANA-
                      assigned well-known port for RESTCONF client connections, as well as configuring call-
   home to one RESTCONF client.

   This example 'restconf-ch-tls'
                      (4336) if no value is consistent with specified.";
                 }
               }
             }
             container http-client-parameters {
               description
                 "A wrapper around the examples presented in Section 2
   of [I-D.ietf-netconf-trust-anchors] and Section 3.2 of
   [I-D.ietf-netconf-keystore].

   ========== NOTE: '\' line wrapping per BCP XXX (RFC XXXX) ===========

   <restconf-server
     xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-server"
     xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"
     xmlns:x509c2n="urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name">

     <!-- endpoints HTTP client parameters
                  to listen avoid name collisions.";
               uses httpc:http-client-grouping;
             }
             container restconf-client-parameters {
               description
                 "A wrapper around the RESTCONF client parameters
                  to avoid name collisions.";
               uses rcc:restconf-client-grouping;
             }
           }
         }
         case https {
           if-feature "https-listen";
           container https {
             must 'tls-client-parameters/client-identity
                   or http-client-parameters/client-identity';
             description
               "HTTPS-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 "4336";
                   description
                     "The RESTCONF connections client will listen on -->
     <listen>
       <endpoint>
         <name>netconf/tls</name>
         <https>
           <tcp-server-parameters>
             <local-address>11.22.33.44</local-address>
           </tcp-server-parameters>
           <tls-server-parameters>
             <server-identity>
               <certificate>
                 <local-definition>
                   <public-key-format>ct:subject-public-key-info-format\
   </public-key-format>
                   <public-key>base64encodedvalue==</public-key>
                   <private-key-format>ct:rsa-private-key-format</priva\
   te-key-format>
                   <private-key>base64encodedvalue==</private-key>
                   <cert>base64encodedvalue==</cert>
                 </local-definition>
               </certificate>
             </server-identity>
             <client-authentication>
               <ca-certs>
                 <truststore-reference>trusted-client-ca-certs</trustst\
   ore-reference>
               </ca-certs>
               <ee-certs>
                 <truststore-reference>trusted-client-ee-certs</trustst\
   ore-reference>
               </ee-certs>
             </client-authentication>
             <keepalives>
               <peer-allowed-to-send/>
             </keepalives>
           </tls-server-parameters>
           <http-server-parameters>
             <server-name>foo.example.com</server-name>
           </http-server-parameters>
           <restconf-server-parameters>
             <client-identity-mappings>
               <cert-to-name>
                 <id>1</id>
                 <fingerprint>11:0A:05:11:00</fingerprint>
                 <map-type>x509c2n:specified</map-type>
                 <name>scooby-doo</name>
               </cert-to-name>
                 <cert-to-name>
                 <id>2</id>
                 <map-type>x509c2n:san-any</map-type>
               </cert-to-name>
             </client-identity-mappings>
           </restconf-server-parameters>
         </https>
       </endpoint>
     </listen>

     <!-- call home the IANA-
                      assigned well-known port for 'restconf-ch-tls'
                      (4336) if no value is specified.";
                 }
               }
             }
             container tls-client-parameters {
               description
                 "A wrapper around the TLS client parameters
                  to avoid name collisions.";
               uses tlsc:tls-client-grouping;
             }
             container http-client-parameters {
               description
                 "A wrapper around the HTTP client parameters
                  to avoid name collisions.";
               uses httpc:http-client-grouping;
             }
             container restconf-client-parameters {
               description
                 "A wrapper around the RESTCONF client parameters
                  to avoid name collisions.";
               uses rcc:restconf-client-grouping;
             }
           }
         }
       }
     } // restconf-client-listen-stack-grouping

     grouping restconf-client-app-grouping {
       description
         "A reusable grouping for configuring a RESTCONF client with two endpoints -->
     <call-home>
       <restconf-client>
         <name>config-manager</name>
         <endpoints>
           <endpoint>
             <name>east-data-center</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>east.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-server-parameters>
                 <server-identity>
                   <certificate>
                     <local-definition>
                       <public-key-format>ct:subject-public-key-info-fo\
   rmat</public-key-format>
                       <public-key>base64encodedvalue==</public-key>
                       <private-key-format>ct:rsa-private-key-format</p\
   rivate-key-format>
                       <private-key>base64encodedvalue==</private-key>
                       <cert>base64encodedvalue==</cert>
                     </local-definition>
                   </certificate>
                 </server-identity>
                 <client-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-client-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-client-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </client-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-server-parameters>
               <http-server-parameters>
                 <server-name>foo.example.com</server-name>
               </http-server-parameters>
               <restconf-server-parameters>
                 <client-identity-mappings>
                   <cert-to-name>
                     <id>1</id>
                     <fingerprint>11:0A:05:11:00</fingerprint>
                     <map-type>x509c2n:specified</map-type>
                     <name>scooby-doo</name>
                   </cert-to-name>
                   <cert-to-name>
                     <id>2</id>
                     <map-type>x509c2n:san-any</map-type>
                   </cert-to-name>
                 </client-identity-mappings>
               </restconf-server-parameters>
             </https>
           </endpoint>
           <endpoint>
             <name>west-data-center</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>west.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-server-parameters>
                 <server-identity>
                   <certificate>
                     <local-definition>
                       <public-key-format>ct:subject-public-key-info-fo\
   rmat</public-key-format>
                       <public-key>base64encodedvalue==</public-key>
                       <private-key-format>ct:rsa-private-key-format</p\
   rivate-key-format>
                       <private-key>base64encodedvalue==</private-key>
                       <cert>base64encodedvalue==</cert>
                     </local-definition>
                   </certificate>
                 </server-identity>
                 <client-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-client-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-client-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </client-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-server-parameters>
               <http-server-parameters>
                 <server-name>foo.example.com</server-name>
               </http-server-parameters>
               <restconf-server-parameters>
                 <client-identity-mappings>
                   <cert-to-name>
                     <id>1</id>
                     <fingerprint>11:0A:05:11:00</fingerprint>
                     <map-type>x509c2n:specified</map-type>
                     <name>scooby-doo</name>
                   </cert-to-name>
                   <cert-to-name>
                     <id>2</id>
                     <map-type>x509c2n:san-any</map-type>
                   </cert-to-name>
                 </client-identity-mappings>
               </restconf-server-parameters>
             </https>
           </endpoint>
         </endpoints>
         <connection-type>
           <periodic>
             <idle-timeout>300</idle-timeout>
             <period>60</period>
           </periodic>
         </connection-type>
         <reconnect-strategy>
           <start-with>last-connected</start-with>
           <max-attempts>3</max-attempts>
         </reconnect-strategy>
       </restconf-client>
     </call-home>
   </restconf-server>

3.3.  YANG Module

   This YANG module has normative references to [RFC6991], [RFC7407],
   [RFC8040], [RFC8071], [I-D.kwatsen-netconf-tcp-client-server],
   [I-D.ietf-netconf-tls-client-server],
          application that supports both 'initiate' and
   [I-D.kwatsen-netconf-http-client-server].

   <CODE BEGINS> file "ietf-restconf-server@2020-05-20.yang"

   module ietf-restconf-server {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-server";
     prefix rcs;

     import ietf-yang-types 'listen'
          protocol stacks for a multiplicity of connections.";
       container initiate {
       prefix yang;
       reference
         "RFC 6991: Common YANG Data Types";
     }

     import ietf-inet-types
         if-feature "https-initiate";
         presence "Enables client to initiate TCP connections";
         description
           "Configures client initiating underlying TCP connections.";
         list restconf-server {
       prefix inet;
       reference
         "RFC 6991: Common YANG Data Types";
     }

     import ietf-x509-cert-to-name
           key "name";
           min-elements 1;
           description
             "List of RESTCONF servers the RESTCONF client is to
              maintain simultaneous connections with.";
           leaf name {
       prefix x509c2n;
       reference
         "RFC 7407: A YANG Data Model
             type string;
             description
               "An arbitrary name for SNMP Configuration"; the RESTCONF server.";
           }

     import ietf-tcp-client
           container endpoints {
       prefix tcpc;
       reference
         "RFC DDDD: YANG Groupings
             description
               "Container for TCP Clients and TCP Servers";
     }

     import ietf-tcp-server the list of endpoints.";
             list endpoint {
       prefix tcps;
       reference
         "RFC DDDD: YANG Groupings
               key "name";
               min-elements 1;
               ordered-by user;
               description
                 "A non-empty user-ordered list of endpoints for TCP Clients and TCP Servers";
     }

     import ietf-tls-server this
                  RESTCONF client to try to connect to in sequence.
                  Defining more than one enables high-availability.";
               leaf name {
       prefix tlss;
       reference
         "RFC FFFF: YANG Groupings
                 type string;
                 description
                   "An arbitrary name for TLS Clients and TLS Servers"; this endpoint.";
               }

     import ietf-http-server {
       prefix https;
       reference
         "RFC GGGG: YANG Groupings for HTTP Clients and HTTP Servers";
               uses restconf-client-initiate-stack-grouping;
             }

     organization
       "IETF NETCONF (Network Configuration) Working Group";

     contact
       "WG Web:   <http://datatracker.ietf.org/wg/netconf/>
        WG List:  <mailto:netconf@ietf.org>
        Author:   Kent Watsen <mailto:kent+ietf@watsen.net>
        Author:   Gary Wu <mailto:garywu@cisco.com>
        Author:   Juergen Schoenwaelder
                  <mailto:j.schoenwaelder@jacobs-university.de>";
           }
           container connection-type {
             description
       "This module contains a collection of YANG definitions
        for configuring RESTCONF servers.

        Copyright (c) 2020 IETF Trust and
               "Indicates the persons identified
        as authors of RESTCONF client's preference for how
                the code. All rights reserved.

        Redistribution and use in source and binary forms, with
        or without modification, RESTCONF 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 permitted pursuant to, and
        subject to be maintained.";
                   description
                     "Maintain a persistent connection to the license terms contained in, the Simplified
        BSD License set forth in Section 4.c of
                      RESTCONF server. If the IETF Trust's
        Legal Provisions Relating connection goes down,
                      immediately start trying to IETF Documents
        (https://trustee.ietf.org/license-info). reconnect to the
                      RESTCONF server, using the reconnection strategy.

                      This version connection type minimizes any RESTCONF server
                      to RESTCONF client data-transfer delay, albeit
                      at the expense of this YANG module is part of RFC IIII
        (https://www.rfc-editor.org/info/rfcIIII); see the RFC
        itself for full legal notices.

        The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
        'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
        'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
        are to be interpreted as described in BCP 14 (RFC 2119)
        (RFC 8174) when, and only when, they appear in all
        capitals, as shown here.";

     revision 2020-05-20 {
       description
         "Initial version";
       reference
         "RFC IIII: RESTCONF Client and Server Models"; holding resources longer.";
                 }

     // Features

     feature http-listen
               }
               case periodic-connection {
       description
         "The 'http-listen' feature indicates
                 container periodic {
                   presence "Indicates that the RESTCONF server
          supports opening a port periodic connection is
                             to listen for incoming RESTCONF over
          TPC client connections, whereby the TLS connections are
          terminated by an external system.";

       reference
         "RFC 8040: RESTCONF Protocol";
     }

     feature https-listen { be maintained.";
                   description
         "The 'https-listen' feature indicates that
                     "Periodically connect to the RESTCONF server.

                      This connection type increases resource
                      utilization, albeit with increased delay
                      in RESTCONF server
          supports opening a port to listen for incoming RESTCONF over
          TLS client connections, whereby
                      interactions.

                      The RESTCONF client SHOULD gracefully close
                      the underlying TLS connections are
          terminated by connection upon completing
                      planned activities.

                      In the server itself.";
       reference
         "RFC 8040: RESTCONF Protocol";
     }

     feature https-call-home {
       description
         "The 'https-call-home' feature indicates case that the RESTCONF
          server supports initiating connections to RESTCONF clients.";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
     }

     // Groupings

     grouping restconf-server-grouping previous connection is
                      still active, establishing a new connection
                      is NOT RECOMMENDED.";
                   leaf period {
                     type uint16;
                     units "minutes";
                     default "60";
                     description
         "A reusable grouping for configuring a RESTCONF server
          without any consideration for how underlying transport
          sessions
                       "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 established.

          Note that this grouping uses
                        determined.  The periodic connections occur
                        at a fairly typical descendent
          node name such that whole multiple interval from the anchor
                        time.  For example, for an anchor time is 15
                        minutes past midnight and a stack period interval
                        of 'uses' statements 24 hours, then a periodic connection will
          have name conflicts.  It is intended
                        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 the consuming
          data model underlying TCP session may remain
                        idle. A TCP session will resolve the issue by wrapping the 'uses'
          statement in a container called, e.g.,
          'restconf-server-parameters'.  This model purposely does
          not do be dropped if it
                        is idle for an interval longer than this itself so as to provide maximum flexibility
                        number of seconds If set to consuming models."; zero, then the
                        RESTCONF client will never drop a session
                        because it is idle.";
                   }
                 }
               } // periodic-connection
             } // connection-type
           } // connection-type
           container client-identity-mappings reconnect-strategy {
             description
           "Specifies mappings through which
               "The reconnection strategy directs how a RESTCONF
                client X.509
            certificates are used reconnects to determine a RESTCONF username.
            If no matching and valid cert-to-name list entry can be
            found, then server, after
                discovering its connection to the RESTCONF server MUST close the connection,
            and MUST NOT accept has
                dropped, even if due to a reboot.  The RESTCONF messages over it.";
         reference
           "RFC 7407: A YANG Data Model for SNMP Configuration.";
         uses x509c2n:cert-to-name
                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 {
           refine "cert-to-name/fingerprint"
               type enumeration {
                 enum first-listed {
             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
                     "Indicates that reconnections should only be present at the end of start
                      with the user-ordered 'cert-to-name' list.";
           }
         }
       } first endpoint listed.";
                 }

     grouping restconf-server-listen-stack-grouping
                 enum last-connected {
                   description
         "A reusable grouping for configuring a
                     "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.   RESTCONF server
          'listen' protocol stack for a single connection.";
       choice transport clients
                      SHOULD be able to remember the last
                      endpoint connected to across reboots.";
                 }
                 enum random-selection {
         mandatory true;
                   description
           "Selects between available transports. This is
                     "Indicates that reconnections should start with
                      a
            'choice' statement so as random endpoint.";
                 }
               }
               default "first-listed";
               description
                 "Specifies which of the RESTCONF server's
                  endpoints the RESTCONF client should start
                  with when trying to support additional
            transport options connect to be augmented in.";
         case http the RESTCONF
                  server.";
             }
             leaf max-attempts {
           if-feature "http-listen";
           container http
               type uint8 {
                 range "1..max";
               }
               default "3";
               description
               "Configures RESTCONF server stack assuming that
                TLS-termination is handled externally.";
             container external-endpoint {
               presence
                 "Specifies configuration for an external endpoint.";
               description
                 "Identifies contact information for the external
                  system that terminates connections before passing
                  them thru number times the RESTCONF client
                  tries to connect to this server (e.g., a network address
                  translator or a load balancer).  These values have
                  no effect specific endpoint before
                  moving on to the local operation of this server, but
                  may be used by next endpoint in the application when needing to
                  inform other systems how to contact this server.";
               leaf address list
                  (round robin).";
             }
           }
         }
       } // initiate
       container listen {
                 type inet:ip-address;
                 mandatory true;
                 description
                   "The IP address
         if-feature "http-listen or hostname of https-listen";
         presence "Enables client to accept call-home connections";
         description
           "Configures the external system
                    that terminates incoming RESTCONF client
                    connections before forwarding them to this
                    server.";
               } accept call-home TCP connections.";
         leaf port idle-timeout {
           type inet:port-number; uint16;
           units "seconds";
           default "443"; 3600; // one hour
           description
                   "The port
             "Specifies the maximum number of seconds that the external system listens
                    on an
              underlying TCP session may remain idle. A TCP session
              will be dropped if it is idle for incoming RESTCONF client connections that
                    are forwarded to an interval longer
              then this server.  The default HTTPS
                    port (443) number of seconds.  If set to zero, then
              the server will never drop a session because it is used, as expected for
              idle.  Sessions that have a RESTCONF
                    connection.";
               } notification subscription
              active are never dropped.";
         }
             container tcp-server-parameters
         list endpoint {
           key "name";
           min-elements 1;
           description
                 "A wrapper around the TCP server parameters
             "List of endpoints to avoid listen for RESTCONF connections.";
           leaf name collisions.";
               uses tcps:tcp-server-grouping {
                 refine "local-port" {
                   default "80";
             type string;
             description
                     "The
               "An arbitrary name for the RESTCONF server will listen on the IANA-
                      assigned well-known port value for 'http'
                      (80) if no value is specified.";
                 }
               }
             }
             container http-server-parameters {
               description
                 "A wrapper around the HTTP server parameters
                  to avoid name collisions.";
               uses https:http-server-grouping; endpoint.";
           }
             container restconf-server-parameters {
               description
                 "A wrapper around the RESTCONF server parameters
                  to avoid name collisions.";
           uses rcs:restconf-server-grouping; restconf-client-listen-stack-grouping;
         }
       }
     }
         case https {
           if-feature "https-listen";
           container https {
             description
               "Configures RESTCONF server stack assuming that
                TLS-termination is handled internally.";
             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 "443";
                   description
                     "The RESTCONF server will listen on the IANA-
                      assigned well-known port value // restconf-client-app-grouping

     // Protocol accessible node, for 'https'
                      (443) if no value is specified.";
                 }
               }
             } servers that implement
     // this module.
     container tls-server-parameters restconf-client {
               description
                 "A wrapper around the TLS server parameters
                  to avoid name collisions.";
       uses tlss:tls-server-grouping;
             }
             container http-server-parameters { restconf-client-app-grouping;
       description
                 "A wrapper around the HTTP server parameters
                  to avoid name collisions.";
               uses https:http-server-grouping;
             }
         "Top-level container restconf-server-parameters {
               description
                 "A wrapper around the for RESTCONF server parameters
                  to avoid name collisions.";
               uses rcs:restconf-server-grouping;
             }
           }
         } client configuration.";
     }
   }

     grouping restconf-server-callhome-stack-grouping {
       description
         "A reusable grouping for configuring a

   <CODE ENDS>

3.  The "ietf-restconf-server" Module

   The RESTCONF server
          'call-home' protocol stack, model presented in this section supports both
   listening for a single connection.";
       choice transport {
         mandatory true;
         description
           "Selects between available transports. This is a
            'choice' statement so connections as well as initiating call-home
   connections.

   YANG feature statements are used to support additional
            transport options enable implementations to be augmented in.";

         case https {
           if-feature "https-listen";
           container https {
             description
               "Configures RESTCONF server stack assuming that
                TLS-termination is handled internally.";
             container tcp-client-parameters {
               description
                 "A wrapper around
   advertise which potentially uncommon parts of the model the TCP client parameters
                  to avoid name collisions.";
               uses tcpc:tcp-client-grouping {
                 refine "remote-port" {
                   default "4336";
                   description
                     "The RESTCONF
   server will attempt to
                      connect to supports.

3.1.  Data Model Overview

3.1.1.  Features

   The following diagram lists all the IANA-assigned well-known
                      port for 'restconf-ch-tls' (4336) if no
                      value is specified.";
                 }
               }
             }
             container tls-server-parameters {
               description
                 "A wrapper around "feature" statements defined in
   the TLS server parameters
                  to avoid name collisions.";
               uses tlss:tls-server-grouping;
             }
             container http-server-parameters {
               description
                 "A wrapper around "ietf-restconf-server" module:

   Features:
     +-- http-listen
     +-- https-listen
     +-- https-call-home

3.1.2.  Groupings

   The following diagram lists all the HTTP server parameters
                  to avoid name collisions.";
               uses https:http-server-grouping;
             }
             container restconf-server-parameters {
               description
                 "A wrapper around "grouping" statements defined in
   the RESTCONF server parameters
                  to avoid name collisions.";
               uses rcs:restconf-server-grouping;
             }
           }
         }
       }
     }

     grouping "ietf-restconf-server" module:

   Groupings:
     +-- restconf-server-grouping
     +-- restconf-server-listen-stack-grouping
     +-- restconf-server-callhome-stack-grouping
     +-- restconf-server-app-grouping {
       description
         "A reusable

   Each of these groupings are presented in the following subsections.

3.1.2.1.  The "restconf-server-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the "restconf-
   server-grouping" grouping:

     grouping restconf-server-grouping
       +-- client-identity-mappings
          +---u x509c2n:cert-to-name

   Comments:

   *  The "restconf-server-grouping" defines the configuration for configuring just
      "RESTCONF" part of a RESTCONF server
          application that supports both 'listen' and 'call-home' protocol stacks stack.  It does not, for instance,
      define any configuration for a multiplicity of connections.";
       container listen {
         if-feature "http-listen or https-listen";
         presence
           "Enables the RESTCONF server "TCP", "TLS", or "HTTP" protocol
      layers (for that, see Section 3.1.2.2 and Section 3.1.2.3).

   *  The "client-identity-mappings" node, which must be enabled by
      "feature" statements, defines a mapping from certificate fields to listen for
      RESTCONF
            client connections.";
         description "Configures listen behavior";
         list endpoint {
           key "name";
           min-elements 1;
           description
             "List of endpoints to listen for user names.

   *  For the referenced grouping statement(s):

      -  The "cert-to-name" grouping is discussed in Section 4.1 of
         [RFC7407].

3.1.2.2.  The "restconf-server-listen-stack-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the "restconf-
   server-listen-stack-grouping" grouping:

     grouping restconf-server-listen-stack-grouping
       +-- (transport)
          +--:(http) {http-listen}?
          |  +-- http
          |     +-- external-endpoint!
          |     |  +-- address    inet:ip-address
          |     |  +-- port?      inet:port-number
          |     +-- tcp-server-parameters
          |     |  +---u tcps:tcp-server-grouping
          |     +-- http-server-parameters
          |     |  +---u https:http-server-grouping
          |     +-- restconf-server-parameters
          |        +---u rcs:restconf-server-grouping
          +--:(https) {https-listen}?
             +-- https
                +-- tcp-server-parameters
                |  +---u tcps:tcp-server-grouping
                +-- tls-server-parameters
                |  +---u tlss:tls-server-grouping
                +-- http-server-parameters
                |  +---u https:http-server-grouping
                +-- restconf-server-parameters
                   +---u rcs:restconf-server-grouping

   Comments:

   *  The "restconf-server-listen-stack-grouping" defines the
      configuration for a full RESTCONF connections.";
           leaf name {
             type string;
             description
               "An arbitrary name protocol stack for the RESTCONF
      servers that listen endpoint.";
           }
           uses restconf-server-listen-stack-grouping;
         }
       }
       container call-home {
         if-feature "https-call-home";
         presence
           "Enables the for standard connections from RESTCONF server to initiate the underlying
            transport connection
      clients, as opposed to RESTCONF clients.";
         description "Configures initiating call-home behavior";
         list restconf-client {
           key "name";
           min-elements 1;
           description
             "List of RESTCONF clients [RFC8071] connections.

   *  The "transport" choice node enables both the RESTCONF server HTTP and HTTPS
      transports to be configured, with each option enabled by a
      "feature" statement.  The HTTP option is provided to
              maintain simultaneous call-home connections with.";
           leaf name {
             type string;
             description
               "An arbitrary name for support cases
      where a TLS-terminator is deployed in front of the remote RESTCONF client.";
           }
           container endpoints {
             description
               "Container for RESTCONF-
      server.

   *  For the list referenced grouping statement(s):

      -  The "tcp-server-grouping" grouping is discussed in
         Section 4.1.2.1 of endpoints.";
             list endpoint {
               key "name";
               min-elements 1;
               ordered-by user;
               description
                 "User-ordered list [I-D.ietf-netconf-tcp-client-server].
      -  The "tls-server-grouping" grouping is discussed in
         Section 4.1.2.1 of [I-D.ietf-netconf-tls-client-server].
      -  The "http-server-grouping" grouping is discussed in
         Section 3.1.2.1 of [I-D.ietf-netconf-http-client-server].
      -  The "restconf-server-grouping" is discussed in Section 3.1.2.1
         of endpoints for this RESTCONF
                  client.  Defining more than one enables high-
                  availability.";
               leaf name {
                 type string;
                 description
                   "An arbitrary name for this endpoint.";
               }
               uses restconf-server-callhome-stack-grouping;
             }
           }
           container connection-type {
             description
               "Indicates document.

3.1.2.3.  The "restconf-server-callhome-stack-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the "restconf-
   server-callhome-stack-grouping" grouping:

     grouping restconf-server-callhome-stack-grouping
       +-- (transport)
          +--:(https) {https-listen}?
             +-- https
                +-- tcp-client-parameters
                |  +---u tcpc:tcp-client-grouping
                +-- tls-server-parameters
                |  +---u tlss:tls-server-grouping
                +-- http-server-parameters
                |  +---u https:http-server-grouping
                +-- restconf-server-parameters
                   +---u rcs:restconf-server-grouping

   Comments:

   *  The "restconf-server-callhome-stack-grouping" defines the
      configuration for a full RESTCONF server's preference protocol stack, for how the RESTCONF connection is maintained.";
             choice connection-type {
               mandatory true;
               description
                 "Selects between available connection types.";
               case persistent-connection {
                 container persistent {
                   presence "Indicates
      servers that a persistent connection is
                             to be maintained.";
                   description
                     "Maintain a persistent connection initiate call-home [RFC8071] connections to the RESTCONF
                      client. If the connection goes down, immediately
                      start trying to reconnect
      clients.

   *  The "transport" choice node enables transport options to the RESTCONF server,
                      using the reconnection strategy. be
      configured.  This connection type minimizes any RESTCONF
                      client to RESTCONF server data-transfer delay,
                      albeit at document only defines an "https" option, but
      other options MAY be augmented in.

   *  For the expense referenced grouping statement(s):

      -  The "tcp-client-grouping" grouping is discussed in
         Section 3.1.2.1 of holding resources
                      longer.";
                 }
               }
               case periodic-connection {
                 container periodic {
                   presence "Indicates that a periodic connection [I-D.ietf-netconf-tcp-client-server].
      -  The "tls-server-grouping" grouping is
                             to be maintained.";
                   description
                     "Periodically connect to the RESTCONF client.

                      This connection type increases resource
                      utilization, albeit with increased delay discussed in
                      RESTCONF client to RESTCONF client interactions.
         Section 4.1.2.1 of [I-D.ietf-netconf-tls-client-server].
      -  The RESTCONF client SHOULD gracefully close
                      the underlying TLS connection upon completing
                      planned activities.  If the underlying TLS
                      connection "http-server-grouping" grouping is not closed gracefully, the
                      RESTCONF server MUST immediately attempt
                      to reestablish the connection.

                      In the case that the previous connection is
                      still active (i.e., the RESTCONF client has not
                      closed it yet), establishing a new connection discussed in
         Section 3.1.2.1 of [I-D.ietf-netconf-http-client-server].
      -  The "restconf-server-grouping" is NOT RECOMMENDED.";

                   leaf period {
                     type uint16;
                     units "minutes";
                     default "60";
                     description
                       "Duration discussed in Section 3.1.2.1
         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 this document.

3.1.2.4.  The "restconf-server-app-grouping" Grouping

   The following tree diagram [RFC8340] illustrates the "restconf-
   server-app-grouping" grouping:

     grouping restconf-server-app-grouping
       +-- listen! {http-listen or after which a
                        series of periodic connections are determined. https-listen}?
       |  +-- endpoint* [name]
       |     +-- name?                                    string
       |     +---u restconf-server-listen-stack-grouping
       +-- call-home! {https-call-home}?
          +-- restconf-client* [name]
             +-- name?                 string
             +-- endpoints
             |  +-- endpoint* [name]
             |     +-- name?                                      string
             |     +---u restconf-server-callhome-stack-grouping
             +-- connection-type
             |  +-- (connection-type)
             |     +--:(persistent-connection)
             |     |  +-- persistent!
             |     +--:(periodic-connection)
             |        +-- periodic!
             |           +-- period?         uint16
             |           +-- anchor-time?    yang:date-and-time
             |           +-- idle-timeout?   uint16
             +-- reconnect-strategy
                +-- start-with?     enumeration
                +-- max-attempts?   uint8

   Comments:

   *  The periodic connections occur at a whole
                        multiple interval from "restconf-server-app-grouping" defines the anchor time.  For
                        example, configuration 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
      RESTCONF server that supports both listening for connections from
      RESTCONF clients as well as initiatiating call-home connections to
      RESTCONF clients.

   *  Both the underlying TCP session may remain idle.
                        A TCP session will "listen" and "call-home" subtrees must be dropped if it is idle
                        for an interval longer than this number of
                        seconds.  If set to zero, then enabled by
      "feature" statements.

   *  For the server
                        will never drop a session because it referenced grouping statement(s):

      -  The "restconf-server-listen-stack-grouping" grouping is idle.";
                   }
                 }
               }
             }
           }
           container reconnect-strategy {
             description
               "The reconnection strategy directs how a RESTCONF server
                reconnects to a RESTCONF client after discovering its
                connection to the client has dropped, even if due to a
                reboot.
         discussed in Section 3.1.2.2 in this document.
      -  The RESTCONF server starts with the specified
                endpoint and tries to connect to it max-attempts times
                before trying "restconf-server-callhome-stack-grouping" grouping is
         discussed in Section 3.1.2.3 in this document.

3.1.3.  Protocol-accessible Nodes

   The following diagram lists all the next endpoint protocol-accessible nodes defined
   in the list (round
                robin).";
             leaf start-with {
               type enumeration {
                 enum first-listed {
                   description
                     "Indicates "ietf-restconf-server" module:

   module: ietf-restconf-server
     +--rw restconf-server
        +---u restconf-server-app-grouping

   Comments:

   *  Protocol-accessible nodes are those nodes that reconnections should start with are accessible when
      the first endpoint listed.";
                 }
                 enum last-connected {
                   description
                     "Indicates that reconnections should start with module is "implemented", as described in Section 5.6.5 of
      [RFC7950].

   *  For the endpoint last connected to.  If no previous
                      connection has ever been established, then "ietf-restconf-server" module, the
                      first endpoint configured protocol-accessible
      nodes are an instance of the "restconf-server-app-grouping"
      discussed in Section 3.1.2.4 grouping.

   *  The reason for why "restconf-server-app-grouping" exists separate
      from the protocol-accessible nodes definition is used.   RESTCONF
                      servers SHOULD be able so as to remember the last
                      endpoint connected enable
      instances of restconf-server-app-grouping to across reboots.";
                 }
                 enum random-selection {
                   description
                     "Indicates that reconnections should start with be instantiated in
      other locations, as may be needed or desired by some modules.

3.2.  Example Usage

   The following example illustrates configuring a random endpoint.";
                 }
               }
               default "first-listed";
               description
                 "Specifies which of the RESTCONF client's endpoints
                  the RESTCONF server should start with when trying to connect to the RESTCONF client.";
             }
             leaf max-attempts {
               type uint8 {
                 range "1..max";
               }
               default "3";
               description
                 "Specifies the number times the RESTCONF server tries
                  to connect to a specific endpoint before moving on to
                  the next endpoint in the list (round robin).";
             }
           }
         } // restconf-client

       } // call-home
     } // restconf-server-app-grouping

     // Protocol accessible node, for servers that implement
     // this module.
     container restconf-server {
       uses restconf-server-app-grouping;
       description
         "Top-level container
   listen for RESTCONF server configuration.";
     }

   }

   <CODE ENDS>

4.  Security Considerations

   The YANG module defined in this document uses groupings defined in
   [I-D.kwatsen-netconf-tcp-client-server],
   [I-D.ietf-netconf-tls-client-server], and
   [I-D.kwatsen-netconf-http-client-server].  Please see the Security
   Considerations section in those documents for concerns related those
   groupings.

   The YANG modules defined in this document are designed to be accessed
   via YANG based management protocols, such client connections, as NETCONF [RFC6241] and well as configuring call-
   home to one RESTCONF [RFC8040].  Both of these protocols have mandatory-to-
   implement secure transport layers (e.g., SSH, TLS) client.

   This example is consistent with mutual
   authentication.

   The NETCONF access control model (NACM) [RFC8341] provides the means
   to restrict access for particular users to a pre-configured subset examples presented in Section 2.2
   of
   all available protocol operations [I-D.ietf-netconf-trust-anchors] and content.

   There are a number of data nodes defined in the YANG modules that are
   writable/creatable/deletable (i.e., config true, which is the
   default).  Some Section 2.2 of these data nodes may be considered sensitive or
   vulnerable in some network environments.  Write operations (e.g.,
   edit-config)
   [I-D.ietf-netconf-keystore].

   =============== NOTE: '\' line wrapping per RFC 8792 ================

   <restconf-server
     xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf-server"
     xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"
     xmlns:x509c2n="urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name">

     <!-- endpoints to these data nodes without proper protection can have a
   negative effect listen for RESTCONF connections on network operations.  These are the subtrees and
   data nodes and their sensitivity/vulnerability:

      None of the subtrees or data nodes in the modules defined in this
   document need -->
     <listen>
       <endpoint>
         <name>restconf/https</name>
         <https>
           <tcp-server-parameters>
             <local-address>11.22.33.44</local-address>
           </tcp-server-parameters>
           <tls-server-parameters>
             <server-identity>
               <certificate>
                 <keystore-reference>
                   <asymmetric-key>rsa-asymmetric-key</asymmetric-key>
                   <certificate>ex-rsa-cert</certificate>
                 </keystore-reference>
               </certificate>
             </server-identity>
             <client-authentication>
               <ca-certs>
                 <truststore-reference>trusted-client-ca-certs</trustst\
   ore-reference>
               </ca-certs>
               <ee-certs>
                 <truststore-reference>trusted-client-ee-certs</trustst\
   ore-reference>
               </ee-certs>
             </client-authentication>
             <keepalives>
               <peer-allowed-to-send/>
             </keepalives>
           </tls-server-parameters>
           <http-server-parameters>
             <server-name>foo.example.com</server-name>
           </http-server-parameters>
           <restconf-server-parameters>
             <client-identity-mappings>
               <cert-to-name>
                 <id>1</id>
                 <fingerprint>11:0A:05:11:00</fingerprint>
                 <map-type>x509c2n:specified</map-type>
                 <name>scooby-doo</name>
               </cert-to-name>
                 <cert-to-name>
                 <id>2</id>
                 <map-type>x509c2n:san-any</map-type>
               </cert-to-name>
             </client-identity-mappings>
           </restconf-server-parameters>
         </https>
       </endpoint>
     </listen>

     <!-- call home to be protected from write operations.

   Some of the readable data nodes in the a RESTCONF client with two endpoints -->
     <call-home>
       <restconf-client>
         <name>config-manager</name>
         <endpoints>
           <endpoint>
             <name>east-data-center</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>east.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-server-parameters>
                 <server-identity>
                   <certificate>
                     <keystore-reference>
                       <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
   ey>
                       <certificate>ex-rsa-cert</certificate>
                     </keystore-reference>
                   </certificate>
                 </server-identity>
                 <client-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-client-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-client-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </client-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-server-parameters>
               <http-server-parameters>
                 <server-name>foo.example.com</server-name>
               </http-server-parameters>
               <restconf-server-parameters>
                 <client-identity-mappings>
                   <cert-to-name>
                     <id>1</id>
                     <fingerprint>11:0A:05:11:00</fingerprint>
                     <map-type>x509c2n:specified</map-type>
                     <name>scooby-doo</name>
                   </cert-to-name>
                   <cert-to-name>
                     <id>2</id>
                     <map-type>x509c2n:san-any</map-type>
                   </cert-to-name>
                 </client-identity-mappings>
               </restconf-server-parameters>
             </https>
           </endpoint>
           <endpoint>
             <name>west-data-center</name>
             <https>
               <tcp-client-parameters>
                 <remote-address>west.example.com</remote-address>
                 <keepalives>
                   <idle-time>15</idle-time>
                   <max-probes>3</max-probes>
                   <probe-interval>30</probe-interval>
                 </keepalives>
               </tcp-client-parameters>
               <tls-server-parameters>
                 <server-identity>
                   <certificate>
                     <keystore-reference>
                       <asymmetric-key>rsa-asymmetric-key</asymmetric-k\
   ey>
                       <certificate>ex-rsa-cert</certificate>
                     </keystore-reference>
                   </certificate>
                 </server-identity>
                 <client-authentication>
                   <ca-certs>
                     <truststore-reference>trusted-client-ca-certs</tru\
   ststore-reference>
                   </ca-certs>
                   <ee-certs>
                     <truststore-reference>trusted-client-ee-certs</tru\
   ststore-reference>
                   </ee-certs>
                 </client-authentication>
                 <keepalives>
                   <test-peer-aliveness>
                     <max-wait>30</max-wait>
                     <max-attempts>3</max-attempts>
                   </test-peer-aliveness>
                 </keepalives>
               </tls-server-parameters>
               <http-server-parameters>
                 <server-name>foo.example.com</server-name>
               </http-server-parameters>
               <restconf-server-parameters>
                 <client-identity-mappings>
                   <cert-to-name>
                     <id>1</id>
                     <fingerprint>11:0A:05:11:00</fingerprint>
                     <map-type>x509c2n:specified</map-type>
                     <name>scooby-doo</name>
                   </cert-to-name>
                   <cert-to-name>
                     <id>2</id>
                     <map-type>x509c2n:san-any</map-type>
                   </cert-to-name>
                 </client-identity-mappings>
               </restconf-server-parameters>
             </https>
           </endpoint>
         </endpoints>
         <connection-type>
           <periodic>
             <idle-timeout>300</idle-timeout>
             <period>60</period>
           </periodic>
         </connection-type>
         <reconnect-strategy>
           <start-with>last-connected</start-with>
           <max-attempts>3</max-attempts>
         </reconnect-strategy>
       </restconf-client>
     </call-home>
   </restconf-server>

3.3.  YANG modules may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control read access (e.g., via get, get-config, or
   notification) Module

   This YANG module has normative references to these data nodes.  These are the subtrees and data
   nodes [RFC6991], [RFC7407],
   [RFC8040], [RFC8071], [I-D.ietf-netconf-tcp-client-server],
   [I-D.ietf-netconf-tls-client-server], and their sensitivity/vulnerability:

      None of the subtrees or data nodes in the modules defined in this
   document need to be protected from read operations.

   Some of the RPC operations in the YANG modules may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control access to these operations.  These are the
   operations and their sensitivity/vulnerability:

      The modules defined in this document do not define any 'RPC' or
   'action' statements.

5.  IANA Considerations

5.1.  The IETF XML Registry

   This document registers two URIs in the "ns" subregistry of the IETF
   XML Registry [RFC3688].  Following the format in [RFC3688], the
   following registrations are requested:

      URI: urn:ietf:params:xml:ns:yang:ietf-restconf-client
      Registrant Contact: The NETCONF WG of the IETF.
      XML: N/A, the requested URI is an XML namespace.

      URI: urn:ietf:params:xml:ns:yang:ietf-restconf-server
      Registrant Contact: The NETCONF WG of the IETF.
      XML: N/A, the requested URI is an XML namespace.

5.2.  The YANG Module Names Registry

   This document registers two
   [I-D.ietf-netconf-http-client-server].

   <CODE BEGINS> file "ietf-restconf-server@2020-07-08.yang"

   module ietf-restconf-server {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-server";
     prefix rcs;

     import ietf-yang-types {
       prefix yang;
       reference
         "RFC 6991: Common YANG modules in the Data Types";

     }

     import ietf-inet-types {
       prefix inet;
       reference
         "RFC 6991: Common YANG Module Names
   registry [RFC6020].  Following the format in [RFC6020], the the
   following registrations are requested:

      name:         ietf-restconf-client
      namespace:    urn:ietf:params:xml:ns:yang:ietf-restconf-client
      prefix:       ncc
      reference:    RFC IIII

      name:         ietf-restconf-server
      namespace:    urn:ietf:params:xml:ns:yang:ietf-restconf-server
      prefix:       ncs
      reference:    RFC IIII

6.  References

6.1.  Normative References

   [I-D.ietf-netconf-keystore]
              Watsen, K., "A Data Types";
     }

     import ietf-x509-cert-to-name {
       prefix x509c2n;
       reference
         "RFC 7407: A YANG Data Model for a Keystore", draft-
              ietf-netconf-keystore-16 (work in progress), March 2020.

   [I-D.ietf-netconf-tls-client-server]
              Watsen, K., Wu, G., and L. Xia, "YANG SNMP Configuration";
     }

     import ietf-tcp-client {
       prefix tcpc;
       reference
         "RFC DDDD: YANG Groupings for TLS TCP Clients and TLS Servers", draft-ietf-netconf-tls-client-
              server-18 (work in progress), March 2020.

   [I-D.kwatsen-netconf-http-client-server]
              Watsen, K., "YANG Groupings for HTTP TCP Servers";
     }

     import ietf-tcp-server {
       prefix tcps;
       reference
         "RFC DDDD: YANG Groupings for TCP Clients and HTTP
              Servers", draft-kwatsen-netconf-http-client-server-05
              (work in progress), November 2019.

   [I-D.kwatsen-netconf-tcp-client-server]
              Watsen, K. TCP Servers";
     }

     import ietf-tls-server {
       prefix tlss;
       reference
         "RFC FFFF: YANG Groupings for TLS Clients and M. Scharf, "YANG TLS Servers";
     }

     import ietf-http-server {
       prefix https;
       reference
         "RFC GGGG: YANG Groupings for TCP HTTP Clients and TCP Servers", draft-kwatsen-netconf-tcp-client-
              server-02 (work in progress), April 2019.

   [RFC2119]  Bradner, S., "Key words HTTP Servers";
     }

     organization
       "IETF NETCONF (Network Configuration) Working Group";

     contact
       "WG Web:   <http://datatracker.ietf.org/wg/netconf/>
        WG List:  <mailto:netconf@ietf.org>
        Author:   Kent Watsen <mailto:kent+ietf@watsen.net>
        Author:   Gary Wu <mailto:garywu@cisco.com>
        Author:   Juergen Schoenwaelder
                  <mailto:j.schoenwaelder@jacobs-university.de>";

     description
       "This module contains a collection of YANG definitions
        for configuring RESTCONF servers.

        Copyright (c) 2020 IETF Trust and the persons identified
        as authors of the code. All rights reserved.

        Redistribution and use in RFCs source and binary forms, with
        or without modification, is permitted pursuant to, and
        subject to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <https://www.rfc-editor.org/info/rfc6020>.

   [RFC6991]  Schoenwaelder, J., Ed., "Common YANG Data Types",
              RFC 6991, DOI 10.17487/RFC6991, July 2013,
              <https://www.rfc-editor.org/info/rfc6991>.

   [RFC7407]  Bjorklund, M. and J. Schoenwaelder, "A license terms contained in, the Simplified
        BSD License set forth in Section 4.c of the IETF Trust's
        Legal Provisions Relating to IETF Documents
        (https://trustee.ietf.org/license-info).

        This version of this YANG Data Model for
              SNMP Configuration", module is part of RFC 7407, DOI 10.17487/RFC7407,
              December 2014, <https://www.rfc-editor.org/info/rfc7407>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", IIII
        (https://www.rfc-editor.org/info/rfcIIII); see the RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8071]  Watsen, K., "NETCONF Call Home
        itself for full legal notices.

        The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
        'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
        'NOT RECOMMENDED', 'MAY', and RESTCONF Call Home",
              RFC 8071, DOI 10.17487/RFC8071, February 2017,
              <https://www.rfc-editor.org/info/rfc8071>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase 'OPTIONAL' in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

6.2.  Informative References

   [I-D.ietf-netconf-trust-anchors]
              Watsen, K., "A YANG Data Model for a Truststore", draft-
              ietf-netconf-trust-anchors-09 (work this document
        are to be interpreted as described in progress), March
              2020.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.

   [RFC8340]  Bjorklund, M. 14 (RFC 2119)
        (RFC 8174) when, and L. Berger, Ed., "YANG Tree Diagrams",
              BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
              <https://www.rfc-editor.org/info/rfc8340>.

   [RFC8341]  Bierman, A. only when, they appear in all
        capitals, as shown here.";

     revision 2020-07-08 {
       description
         "Initial version";
       reference
         "RFC IIII: RESTCONF Client and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, RFC 8341,
              DOI 10.17487/RFC8341, March 2018,
              <https://www.rfc-editor.org/info/rfc8341>.

   [RFC8446]  Rescorla, E., Server Models";
     }

     // Features

     feature http-listen {
       description
         "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/info/rfc8446>.

6.3.  URIs

   [1] https://tools.ietf.org/html/draft-ietf-netconf-crypto-types

   [2] https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors

   [3] https://tools.ietf.org/html/draft-ietf-netconf-keystore

   [4] https://tools.ietf.org/html/draft-ietf-netconf-tcp-client-server

   [5] https://tools.ietf.org/html/draft-ietf-netconf-ssh-client-server

   [6] https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server

   [7] https://tools.ietf.org/html/draft-ietf-netconf-http-client-server

   [8] https://tools.ietf.org/html/draft-ietf-netconf-netconf-client-
       server

   [9] https://tools.ietf.org/html/draft-ietf-netconf-restconf-client- 'http-listen' feature indicates that the RESTCONF server

Appendix A.  Expanded Tree Diagrams

A.1.  Expanded Tree Diagram
          supports opening a port to listen for 'ietf-restconf-client'

   The following tree diagram [RFC8340] provides incoming RESTCONF over
          TPC client connections, whereby the TLS connections are
          terminated by an overview external system.";
       reference
         "RFC 8040: RESTCONF Protocol";
     }

     feature https-listen {
       description
         "The 'https-listen' feature indicates that the RESTCONF server
          supports opening a port to listen for incoming RESTCONF over
          TLS client connections, whereby the TLS connections are
          terminated by the server itself.";
       reference
         "RFC 8040: RESTCONF Protocol";
     }

     feature https-call-home {
       description
         "The 'https-call-home' feature indicates that the RESTCONF
          server supports initiating connections to RESTCONF clients.";
       reference
         "RFC 8071: NETCONF Call Home and RESTCONF Call Home";
     }

     // Groupings

     grouping restconf-server-grouping {
       description
         "A reusable grouping for configuring a RESTCONF server
          without any consideration for how underlying transport
          sessions are established.

          Note that this grouping uses a fairly typical descendent
          node name such that a stack of 'uses' statements will
          have name conflicts.  It is intended that the consuming
          data model for will resolve the "ietf-restconf-client" module.

   This tree diagram shows all issue by wrapping the nodes defined 'uses'
          statement in a container called, e.g.,
          'restconf-server-parameters'.  This model purposely does
          not do this module,
   including those defined by "grouping" statements itself so as to provide maximum flexibility
          to consuming models.";

       container client-identity-mappings {
         description
           "Specifies mappings through which RESTCONF client X.509
            certificates are used by this module.

   Please see Section 2.1 for to determine a tree diagram that illustrates what RESTCONF username.
            If no matching and valid cert-to-name list entry can be
            found, then the
   module looks like without all RESTCONF server MUST close the "grouping" statements expanded.

   ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ==========

   module: ietf-restconf-client
     +--rw restconf-client
        +--rw initiate! {https-initiate}?
        |  +--rw restconf-server* [name]
        |     +--rw name                  string
        |     +--rw endpoints
        |     |  +--rw endpoint* [name]
        |     |     +--rw name           string
        |     |     +--rw (transport)
        |     |        +--:(https) {https-initiate}?
        |     |           +--rw https
        |     |              +--rw tcp-client-parameters
        |     |              |  +--rw remote-address    inet:host
        |     |              |  +--rw remote-port?      inet:port-number
        |     |              |  +--rw local-address?    inet:ip-address
        |     |              |  |       {local-binding-supported}?
        |     |              |  +--rw local-port?       inet:port-number
        |     |              |  |       {local-binding-supported}?
        |     |              |  +--rw keepalives!
        |     |              |          {keepalives-supported}?
        |     |              |     +--rw idle-time         uint16
        |     |              |     +--rw max-probes        uint16
        |     |              |     +--rw probe-interval    uint16
        |     |              +--rw tls-client-parameters
        |     |              |  +--rw client-identity
        |     |              |  |  +--rw (auth-type)?
        |     |              |  |     +--:(certificate)
        |     |              |  |     |        {x509-certificate-auth}?
        |     |              |  |     |  +--rw connection,
            and MUST NOT accept RESTCONF messages over it.";
         reference
           "RFC 7407: A YANG Data Model for SNMP Configuration.";
         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
        |     |              |  |     |     +--rw (local-or-keystore)
        |     |              |  |     |        +--:(local)
        |     |              |  |     |        |        {local-definiti\
   \ons-supported}?
        |     |              |  |     |        |  +--rw local-definition
        |     |              |  |     |        |     +--rw public-key-f\
   \ormat
        |     |              |  |     |        |     |       identityref
        |     |              |  |     |        |     +--rw public-key
        |     |              |  |     |        |     |       binary
        |     |              |  |     |        |     +--rw private-key-\
   \format?
        |     |              |  |     |        |     |       identityref
        |     |              |  |     |        |     +--rw (private-key\
   \-type)
        |     |              |  |     |        |     |  +--:(private-ke\
   \y)
        |     |              |  |     |        |     |  |  +--rw privat\
   \e-key?
        |     |              |  |     |        |     |  |          bina\
   \ry
        |     |              |  |     |        |     |  +--:(hidden-pri\
   \vate-key)
        |     |              |  |     |        |     |  |  +--rw hidden\
   \-private-key?
        |     |              |  |     |        |     |  |          empty
        |     |              |  |     |        |     |  +--:(encrypted-\
   \private-key)
        |     |              |  |     |        |     |     +--rw encryp\
   \ted-private-key
        |     |              |  |     |        |     |        +--rw (ke\
   \y-type)
        |     |              |  |     |        |     |        |  +--:(s\
   \ymmetric-key-ref)
        |     |              |  |     |        |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
        |     |              |  |     |        |     |        |  |     \
   \     {keystore-supported}?
        |     |              |  |     |        |     |        |  +--:(a\
   \symmetric-key-ref)
        |     |              |  |     |        |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
        |     |              |  |     |        |     |        |        \
   \     {keystore-supported}?
        |     |              |  |     |        |     |        +--rw val\
   \ue?
        |     |              |  |     |        |     |                b\
   \inary
        |     |              |  |     |        |     +--rw cert?
        |     |              |  |     |        |     |       end-entity\
   \-cert-cms
        |     |              |  |     |        |     +---n certificate-\

   \expiration
        |     |              |  |     |        |     |  +-- expiration-\
   \date
        |     |              |  |     |        |     |          yang:da\
   \te-and-time
        |     |              |  |     |        |     +---x generate-cer\
   \tificate-signing-request
        |     |              |  |     |        |             {certifica\
   \te-signing-request-generation}?
        |     |              |  |     |        |        +---w input
        |     |              |  |     |        |        |  +---w subject
        |     |              |  |     |        |        |  |       bina\
   \ry
        |     |              |  |     |        |        |  +---w attrib\
   \utes?
        |     |              |  |     |        |        |          bina\
   \ry
        |     |              |  |     |        |        +--ro output
        |     |              |  |     |        |           +--ro certif\
   \icate-signing-request
        |     |              |  |     |        |                   ct:c\
   \sr
        |     |              |  |     |        +--:(keystore)
        |     |              |  |     |                 {keystore-suppo\
   \rted}?
        |     |              |  |     |           +--rw keystore-refere\
   \nce
        |     |              |  |     |              +--rw asymmetric-k\
   \ey?
        |     |              |  |     |              |       ks:asymmet\
   \ric-key-ref
        |     |              |  |     |              +--rw certificate?\
   \      leafref
        |     |              |  |     +--:(raw-public-key)
        |     |              |  |     |        {raw-public-key-auth}?
        |     |              |  |     |  +--rw raw-private-key
        |     |              |  |     |     +--rw (local-or-keystore)
        |     |              |  |     |        +--:(local)
        |     |              |  |     |        |        {local-definiti\
   \ons-supported}?
        |     |              |  |     |        |  +--rw local-definition
        |     |              |  |     |        |     +--rw public-key-f\
   \ormat
        |     |              |  |     |        |     |       identityref
        |     |              |  |     |        |     +--rw public-key
        |     |              |  |     |        |     |       binary
        |     |              |  |     |        |     +--rw private-key-\
   \format?
        |     |              |  |     |        |     |       identityref
        |     |              |  |     |        |     +--rw (private-key\
   \-type)
        |     |              |  |     |        |        +--:(private-ke\
   \y)
        |     |              |  |     |        |        |  +--rw privat\
   \e-key?
        |     |              |  |     |        |        |          bina\
   \ry
        |     |              |  |     |        |        +--:(hidden-pri\
   \vate-key)
        |     |              |  |     |        |        |  +--rw hidden\
   \-private-key?
        |     |              |  |     |        |        |          empty
        |     |              |  |     |        |        +--:(encrypted-\
   \private-key)
        |     |              |  |     |        |           +--rw encryp\
   \ted-private-key
        |     |              |  |     |        |              +--rw (ke\
   \y-type)
        |     |              |  |     |        |              |  +--:(s\
   \ymmetric-key-ref)
        |     |              |  |     |        |              |  |  +--\
   \rw symmetric-key-ref?    leafref
        |     |              |  |     |        |              |  |     \
   \     {keystore-supported}?
        |     |              |  |     |        |              |  +--:(a\
   \symmetric-key-ref)
        |     |              |  |     |        |              |     +--\
   \rw asymmetric-key-ref?   leafref
        |     |              |  |     |        |              |        \
   \     {keystore-supported}?
        |     |              |  |     |        |              +--rw val\
   \ue?
        |     |              |  |     |        |                      b\
   \inary
        |     |              |  |     |        +--:(keystore)
        |     |              |  |     |                 {keystore-suppo\
   \rted}?
        |     |              |  |     |           +--rw keystore-refere\
   \nce?
        |     |              |  |     |                   ks:asymmetric\
   \-key-ref
        |     |              |  |     +--:(psk) {psk-auth}?
        |     |              |  |        +--rw psk
        |     |              |  |           +--rw (local-or-keystore)
        |     |              |  |              +--:(local)
        |     |              |  |              |        {local-definiti\

   \ons-supported}?
        |     |              |  |              |  +--rw local-definition
        |     |              |  |              |     +--rw key-format?
        |     |              |  |              |     |       identityref
        |     |              |  |              |     +--rw (key-type)
        |     |              |  |              |     |  +--:(key)
        |     |              |  |              |     |  |  +--rw key?
        |     |              |  |              |     |  |          bina\
   \ry
        |     |              |  |              |     |  +--:(hidden-key)
        |     |              |  |              |     |  |  +--rw hidden\
   \-key?
        |     |              |  |              |     |  |          empty
        |     |              |  |              |     |  +--:(encrypted-\
   \key)
        |     |              |  |              |     |     +--rw encryp\
   \ted-key
        |     |              |  |              |     |        +--rw (ke\
   \y-type)
        |     |              |  |              |     |        |  +--:(s\
   \ymmetric-key-ref)
        |     |              |  |              |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
        |     |              |  |              |     |        |  |     \
   \     {keystore-supported}?
        |     |              |  |              |     |        |  +--:(a\
   \symmetric-key-ref)
        |     |              |  |              |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
        |     |              |  |              |     |        |        \
   \     {keystore-supported}?
        |     |              |  |              |     |        +--rw val\
   \ue?
        |     |              |  |              |     |                b\
   \inary
        |     |              |  |              |     +--rw id?
        |     |              |  |              |             string
        |     |              |  |              |             {ks:local-\
   \definitions-supported}?
        |     |              |  |              +--:(keystore)
        |     |              |  |                       {keystore-suppo\
   \rted}?
        |     |              |  |                 +--rw keystore-refere\
   \nce?
        |     |              |  |                         ks:symmetric-\
   \key-ref
        |     |              |  +--rw server-authentication
        |     |              |  |  +--rw ca-certs!
        |     |              |  |  |       {x509-certificate-auth}?
        |     |              |  |  |  +--rw (local-or-truststore)
        |     |              |  |  |     +--:(local)
        |     |              |  |  |     |        {local-definitions-su\
   \pported}?
        |     |              |  |  |     |  +--rw local-definition
        |     |              |  |  |     |     +--rw cert*
        |     |              |  |  |     |     |       trust-anchor-cer\
   \t-cms
        |     |              |  |  |     |     +---n certificate-expira\
   \tion
        |     |              |  |  |     |        +-- expiration-date
        |     |              |  |  |     |                yang:date-and\
   \-time
        |     |              |  |  |     +--:(truststore)
        |     |              |  |  |              {truststore-supported\
   \,certificates}?
        |     |              |  |  |        +--rw truststore-reference?
        |     |              |  |  |                ts:certificate-bag-\
   \ref
        |     |              |  |  +--rw ee-certs!
        |     |              |  |  |       {x509-certificate-auth}?
        |     |              |  |  |  +--rw (local-or-truststore)
        |     |              |  |  |     +--:(local)
        |     |              |  |  |     |        {local-definitions-su\
   \pported}?
        |     |              |  |  |     |  +--rw local-definition
        |     |              |  |  |     |     +--rw cert*
        |     |              |  |  |     |     |       trust-anchor-cer\
   \t-cms
        |     |              |  |  |     |     +---n certificate-expira\
   \tion
        |     |              |  |  |     |        +-- expiration-date
        |     |              |  |  |     |                yang:date-and\
   \-time
        |     |              |  |  |     +--:(truststore)
        |     |              |  |  |              {truststore-supported\
   \,certificates}?
        |     |              |  |  |        +--rw truststore-reference?
        |     |              |  |  |                ts:certificate-bag-\
   \ref
        |     |              |  |  +--rw raw-public-keys!
        |     |              |  |  |       {raw-public-key-auth}?
        |     |              |  |  |  +--rw (local-or-truststore)
        |     |              |  |  |     +--:(local)
        |     |              |  |  |     |        {local-definitions-su\
   \pported}?
        |     |              |  |  |     |  +--rw local-definition
        |     |              |  |  |     |     +--rw public-key* [name]
        |     |              |  |  |     |        +--rw name
        |     |              |  |  |     |        |       string
        |     |              |  |  |     |        +--rw public-key-form\
   \at
        |     |              |  |  |     |        |       identityref
        |     |              |  |  |     |        +--rw public-key
        |     |              |  |  |     |                binary
        |     |              |  |  |     +--:(truststore)
        |     |              |  |  |              {truststore-supported\
   \,public-keys}?
        |     |              |  |  |        +--rw truststore-reference?
        |     |              |  |  |                ts:public-key-bag-r\
   \ef
        |     |              |  |  +--rw psks! {psk-auth}?
        |     |              |  +--rw hello-params
        |     |              |  |       {tls-client-hello-params-config\
   \}?
        |     |              |  |  +--rw tls-versions
        |     |              |  |  |  +--rw tls-version*   identityref
        |     |              |  |  +--rw cipher-suites
        |     |              |  |     +--rw cipher-suite*   identityref
        |     |              |  +--rw keepalives
        |     |              |          {tls-client-keepalives}?
        |     |              |     +--rw peer-allowed-to-send?   empty
        |     |              |     +--rw test-peer-aliveness!
        |     |              |        +--rw max-wait?       uint16
        |     |              |        +--rw max-attempts?   uint8
        |     |              +--rw http-client-parameters
        |     |              |  +--rw client-identity!
        |     |              |  |  +--rw (auth-type)?
        |     |              |  |     +--:(basic)
        |     |              |  |        +--rw basic {basic-auth}?
        |     |              |  |           +--rw user-id     string
        |     |              |  |           +--rw password    string
        |     |              |  +--rw proxy-server! {proxy-connect}?
        |     |              |     +--rw tcp-client-parameters
        |     |              |     |  +--rw remote-address    inet:host
        |     |              |     |  +--rw remote-port?
        |     |              |     |  |       inet:port-number
        |     |              |     |  +--rw local-address?
        |     |              |     |  |       inet:ip-address
        |     |              |     |  |       {local-binding-supported}?
        |     |              |     |  +--rw local-port?
        |     |              |     |  |       inet:port-number
        |     |              |     |  |       {local-binding-supported}?
        |     |              |     |  +--rw keepalives!
        |     |              |     |          {keepalives-supported}?
        |     |              |     |     +--rw idle-time         uint16
        |     |              |     |     +--rw max-probes        uint16
        |     |              |     |     +--rw probe-interval    uint16
        |     |              |     +--rw tls-client-parameters
        |     |              |     |  +--rw client-identity
        |     |              |     |  |  +--rw (auth-type)?
        |     |              |     |  |     +--:(certificate)
        |     |              |     |  |     |        {x509-certificate-\
   \auth}?
        |     |              |     |  |     |  +--rw certificate
        |     |              |     |  |     |     +--rw (local-or-keyst\
   \ore)
        |     |              |     |  |     |        +--:(local)
        |     |              |     |  |     |        |        {local-de\
   \finitions-supported}?
        |     |              |     |  |     |        |  +--rw local-def\
   \inition
        |     |              |     |  |     |        |     +--rw public\
   \-key-format
        |     |              |     |  |     |        |     |       iden\
   \tityref
        |     |              |     |  |     |        |     +--rw public\
   \-key
        |     |              |     |  |     |        |     |       bina\
   \ry
        |     |              |     |  |     |        |     +--rw privat\
   \e-key-format?
        |     |              |     |  |     |        |     |       iden\
   \tityref
        |     |              |     |  |     |        |     +--rw (priva\
   \te-key-type)
        |     |              |     |  |     |        |     |  +--:(priv\
   \ate-key)
        |     |              |     |  |     |        |     |  |  +--rw \
   \private-key?
        |     |              |     |  |     |        |     |  |        \
   \  binary
        |     |              |     |  |     |        |     |  +--:(hidd\
   \en-private-key)
        |     |              |     |  |     |        |     |  |  +--rw \
   \hidden-private-key?
        |     |              |     |  |     |        |     |  |        \
   \  empty
        |     |              |     |  |     |        |     |  +--:(encr\
   \ypted-private-key)
        |     |              |     |  |     |        |     |     +--rw \
   \encrypted-private-key
        |     |              |     |  |     |        |     |        +--\

   \rw (key-type)
        |     |              |     |  |     |        |     |        |  \
   \+--:(symmetric-key-ref)
        |     |              |     |  |     |        |     |        |  \
   \|  +--rw symmetric-key-ref?    leafref
        |     |              |     |  |     |        |     |        |  \
   \|          {keystore-supported}?
        |     |              |     |  |     |        |     |        |  \
   \+--:(asymmetric-key-ref)
        |     |              |     |  |     |        |     |        |  \
   \   +--rw asymmetric-key-ref?   leafref
        |     |              |     |  |     |        |     |        |  \
   \           {keystore-supported}?
        |     |              |     |  |     |        |     |        +--\
   \rw value?
        |     |              |     |  |     |        |     |           \
   \     binary
        |     |              |     |  |     |        |     +--rw cert?
        |     |              |     |  |     |        |     |       end-\
   \entity-cert-cms
        |     |              |     |  |     |        |     +---n certif\
   \icate-expiration
        |     |              |     |  |     |        |     |  +-- expir\
   \ation-date
        |     |              |     |  |     |        |     |          y\
   \ang:date-and-time
        |     |              |     |  |     |        |     +---x genera\
   \te-certificate-signing-request
        |     |              |     |  |     |        |             {cer\
   \tificate-signing-request-generation}?
        |     |              |     |  |     |        |        +---w inp\
   \ut
        |     |              |     |  |     |        |        |  +---w \
   \subject
        |     |              |     |  |     |        |        |  |     \
   \  binary
        |     |              |     |  |     |        |        |  +---w \
   \attributes?
        |     |              |     |  |     |        |        |        \
   \  binary
        |     |              |     |  |     |        |        +--ro out\
   \put
        |     |              |     |  |     |        |           +--ro \
   \certificate-signing-request
        |     |              |     |  |     |        |                 \
   \  ct:csr
        |     |              |     |  |     |        +--:(keystore)
        |     |              |     |  |     |                 {keystore\

   \-supported}?
        |     |              |     |  |     |           +--rw keystore-\
   \reference
        |     |              |     |  |     |              +--rw asymme\
   \tric-key?
        |     |              |     |  |     |              |       ks:a\
   \symmetric-key-ref
        |     |              |     |  |     |              +--rw certif\
   \icate?      leafref
        |     |              |     |  |     +--:(raw-public-key)
        |     |              |     |  |     |        {raw-public-key-au\
   \th}?
        |     |              |     |  |     |  +--rw raw-private-key
        |     |              |     |  |     |     +--rw (local-or-keyst\
   \ore)
        |     |              |     |  |     |        +--:(local)
        |     |              |     |  |     |        |        {local-de\
   \finitions-supported}?
        |     |              |     |  |     |        |  +--rw local-def\
   \inition
        |     |              |     |  |     |        |     +--rw public\
   \-key-format
        |     |              |     |  |     |        |     |       iden\
   \tityref
        |     |              |     |  |     |        |     +--rw public\
   \-key
        |     |              |     |  |     |        |     |       bina\
   \ry
        |     |              |     |  |     |        |     +--rw privat\
   \e-key-format?
        |     |              |     |  |     |        |     |       iden\
   \tityref
        |     |              |     |  |     |        |     +--rw (priva\
   \te-key-type)
        |     |              |     |  |     |        |        +--:(priv\
   \ate-key)
        |     |              |     |  |     |        |        |  +--rw \
   \private-key?
        |     |              |     |  |     |        |        |        \
   \  binary
        |     |              |     |  |     |        |        +--:(hidd\
   \en-private-key)
        |     |              |     |  |     |        |        |  +--rw \
   \hidden-private-key?
        |     |              |     |  |     |        |        |        \
   \  empty
        |     |              |     |  |     |        |        +--:(encr\
   \ypted-private-key)
        |     |              |     |  |     |        |           +--rw \
   \encrypted-private-key
        |     |              |     |  |     |        |              +--\
   \rw (key-type)
        |     |              |     |  |     |        |              |  \
   \+--:(symmetric-key-ref)
        |     |              |     |  |     |        |              |  \
   \|  +--rw symmetric-key-ref?    leafref
        |     |              |     |  |     |        |              |  \
   \|          {keystore-supported}?
        |     |              |     |  |     |        |              |  \
   \+--:(asymmetric-key-ref)
        |     |              |     |  |     |        |              |  \
   \   +--rw asymmetric-key-ref?   leafref
        |     |              |     |  |     |        |              |  \
   \           {keystore-supported}?
        |     |              |     |  |     |        |              +--\
   \rw value?
        |     |              |     |  |     |        |                 \
   \     binary
        |     |              |     |  |     |        +--:(keystore)
        |     |              |     |  |     |                 {keystore\
   \-supported}?
        |     |              |     |  |     |           +--rw keystore-\
   \reference?
        |     |              |     |  |     |                   ks:asym\
   \metric-key-ref
        |     |              |     |  |     +--:(psk) {psk-auth}?
        |     |              |     |  |        +--rw psk
        |     |              |     |  |           +--rw (local-or-keyst\
   \ore)
        |     |              |     |  |              +--:(local)
        |     |              |     |  |              |        {local-de\
   \finitions-supported}?
        |     |              |     |  |              |  +--rw local-def\
   \inition
        |     |              |     |  |              |     +--rw key-fo\
   \rmat?
        |     |              |     |  |              |     |       iden\
   \tityref
        |     |              |     |  |              |     +--rw (key-t\
   \ype)
        |     |              |     |  |              |     |  +--:(key)
        |     |              |     |  |              |     |  |  +--rw \
   \key?
        |     |              |     |  |              |     |  |        \
   \  binary
        |     |              |     |  |              |     |  +--:(hidd\

   \en-key)
        |     |              |     |  |              |     |  |  +--rw \
   \hidden-key?
        |     |              |     |  |              |     |  |        \
   \  empty
        |     |              |     |  |              |     |  +--:(encr\
   \ypted-key)
        |     |              |     |  |              |     |     +--rw \
   \encrypted-key
        |     |              |     |  |              |     |        +--\
   \rw (key-type)
        |     |              |     |  |              |     |        |  \
   \+--:(symmetric-key-ref)
        |     |              |     |  |              |     |        |  \
   \|  +--rw symmetric-key-ref?    leafref
        |     |              |     |  |              |     |        |  \
   \|          {keystore-supported}?
        |     |              |     |  |              |     |        |  \
   \+--:(asymmetric-key-ref)
        |     |              |     |  |              |     |        |  \
   \   +--rw asymmetric-key-ref?   leafref
        |     |              |     |  |              |     |        |  \
   \           {keystore-supported}?
        |     |              |     |  |              |     |        +--\
   \rw value?
        |     |              |     |  |              |     |           \
   \     binary
        |     |              |     |  |              |     +--rw id?
        |     |              |     |  |              |             stri\
   \ng
        |     |              |     |  |              |             {ks:\
   \local-definitions-supported}?
        |     |              |     |  |              +--:(keystore)
        |     |              |     |  |                       {keystore\
   \-supported}?
        |     |              |     |  |                 +--rw keystore-\
   \reference?
        |     |              |     |  |                         ks:symm\
   \etric-key-ref
        |     |              |     |  +--rw server-authentication
        |     |              |     |  |  +--rw ca-certs!
        |     |              |     |  |  |       {x509-certificate-auth\
   \}?
        |     |              |     |  |  |  +--rw (local-or-truststore)
        |     |              |     |  |  |     +--:(local)
        |     |              |     |  |  |     |        {local-definiti\
   \ons-supported}?
        |     |              |     |  |  |     |  +--rw local-definition
        |     |              |     |  |  |     |     +--rw cert*
        |     |              |     |  |  |     |     |       trust-anch\
   \or-cert-cms
        |     |              |     |  |  |     |     +---n certificate-\
   \expiration
        |     |              |     |  |  |     |        +-- expiration-\
   \date
        |     |              |     |  |  |     |                yang:da\
   \te-and-time
        |     |              |     |  |  |     +--:(truststore)
        |     |              |     |  |  |              {truststore-sup\
   \ported,certificates}?
        |     |              |     |  |  |        +--rw truststore-refe\
   \rence?
        |     |              |     |  |  |                ts:certificat\
   \e-bag-ref
        |     |              |     |  |  +--rw ee-certs!
        |     |              |     |  |  |       {x509-certificate-auth\
   \}?
        |     |              |     |  |  |  +--rw (local-or-truststore)
        |     |              |     |  |  |     +--:(local)
        |     |              |     |  |  |     |        {local-definiti\
   \ons-supported}?
        |     |              |     |  |  |     |  +--rw local-definition
        |     |              |     |  |  |     |     +--rw cert*
        |     |              |     |  |  |     |     |       trust-anch\
   \or-cert-cms
        |     |              |     |  |  |     |     +---n certificate-\
   \expiration
        |     |              |     |  |  |     |        +-- expiration-\
   \date
        |     |              |     |  |  |     |                yang:da\
   \te-and-time
        |     |              |     |  |  |     +--:(truststore)
        |     |              |     |  |  |              {truststore-sup\
   \ported,certificates}?
        |     |              |     |  |  |        +--rw truststore-refe\
   \rence?
        |     |              |     |  |  |                ts:certificat\
   \e-bag-ref
        |     |              |     |  |  +--rw raw-public-keys!
        |     |              |     |  |  |       {raw-public-key-auth}?
        |     |              |     |  |  |  +--rw (local-or-truststore)
        |     |              |     |  |  |     +--:(local)
        |     |              |     |  |  |     |        {local-definiti\
   \ons-supported}?
        |     |              |     |  |  |     |  +--rw local-definition
        |     |              |     |  |  |     |     +--rw public-key*
        |     |              |     |  |  |     |             [name]
        |     |              |     |  |  |     |        +--rw name
        |     |              |     |  |  |     |        |       string
        |     |              |     |  |  |     |        +--rw public-ke\
   \y-format
        |     |              |     |  |  |     |        |       identit\
   \yref
        |     |              |     |  |  |     |        +--rw public-key
        |     |              |     |  |  |     |                binary
        |     |              |     |  |  |     +--:(truststore)
        |     |              |     |  |  |              {truststore-sup\
   \ported,public-keys}?
        |     |              |     |  |  |        +--rw truststore-refe\
   \rence?
        |     |              |     |  |  |                ts:public-key\
   \-bag-ref
        |     |              |     |  |  +--rw psks! {psk-auth}?
        |     |              |     |  +--rw hello-params
        |     |              |     |  |       {tls-client-hello-params-\
   \config}?
        |     |              |     |  |  +--rw tls-versions
        |     |              |     |  |  |  +--rw tls-version*
        |     |              |     |  |  |          identityref
        |     |              |     |  |  +--rw cipher-suites
        |     |              |     |  |     +--rw cipher-suite*
        |     |              |     |  |             identityref
        |     |              |     |  +--rw keepalives
        |     |              |     |          {tls-client-keepalives}?
        |     |              |     |     +--rw peer-allowed-to-send?
        |     |              |     |     |       empty
        |     |              |     |     +--rw test-peer-aliveness!
        |     |              |     |        +--rw max-wait?       uint16
        |     |              |     |        +--rw max-attempts?   uint8
        |     |              |     +--rw http-client-parameters
        |     |              |        +--rw client-identity!
        |     |              |           +--rw (auth-type)?
        |     |              |              +--:(basic)
        |     |              |                 +--rw basic {basic-auth}?
        |     |              |                    +--rw user-id
        |     |              |                    |       string
        |     |              |                    +--rw password
        |     |              |                            string
        |     |              +--rw restconf-client-parameters
        |     +--rw connection-type
        |     |  +--rw (connection-type)
        |     |     +--:(persistent-connection)
        |     |     |  +--rw persistent!
        |     |     +--:(periodic-connection)
        |     |        +--rw periodic!
        |     |           +--rw period?         uint16
        |     |           +--rw anchor-time?    yang:date-and-time
        |     |           +--rw idle-timeout?   uint16
        |     +--rw reconnect-strategy
        |        +--rw start-with?     enumeration
        |        +--rw max-attempts?   uint8
        +--rw listen! {http-listen or https-listen}?
           +--rw idle-timeout?   uint16
           +--rw endpoint* [name]
              +--rw name           string
              +--rw (transport)
                 +--:(http) {http-listen}?
                 |  +--rw http
                 |     +--rw tcp-server-parameters
                 |     |  +--rw local-address    inet:ip-address
                 |     |  +--rw local-port?      inet:port-number
                 |     |  +--rw keepalives! {keepalives-supported}?
                 |     |     +--rw idle-time         uint16
                 |     |     +--rw max-probes        uint16
                 |     |     +--rw probe-interval    uint16
                 |     +--rw http-client-parameters
                 |     |  +--rw client-identity!
                 |     |  |  +--rw (auth-type)?
                 |     |  |     +--:(basic)
                 |     |  |        +--rw basic {basic-auth}?
                 |     |  |           +--rw user-id     string
                 |     |  |           +--rw password    string
                 |     |  +--rw proxy-server! {proxy-connect}?
                 |     |     +--rw tcp-client-parameters
                 |     |     |  +--rw remote-address    inet:host
                 |     |     |  +--rw remote-port?      inet:port-number
                 |     |     |  +--rw local-address?    inet:ip-address
                 |     |     |  |       {local-binding-supported}?
                 |     |     |  +--rw local-port?       inet:port-number
                 |     |     |  |       {local-binding-supported}?
                 |     |     |  +--rw keepalives!
                 |     |     |          {keepalives-supported}?
                 |     |     |     +--rw idle-time         uint16
                 |     |     |     +--rw max-probes        uint16
                 |     |     |     +--rw probe-interval    uint16
                 |     |     +--rw tls-client-parameters
                 |     |     |  +--rw client-identity
                 |     |     |  |  +--rw (auth-type)?
                 |     |     |  |     +--:(certificate)
                 |     |     |  |     |        {x509-certificate-auth}?
                 |     |     |  |     |  +--rw certificate
                 |     |     |  |     |     +--rw (local-or-keystore)
                 |     |     |  |     |        +--:(local)
                 |     |     |  |     |        |        {local-definiti\
   \ons-supported}?
                 |     |     |  |     |        |  +--rw local-definition
                 |     |     |  |     |        |     +--rw public-key-f\
   \ormat
                 |     |     |  |     |        |     |       identityref
                 |     |     |  |     |        |     +--rw public-key
                 |     |     |  |     |        |     |       binary
                 |     |     |  |     |        |     +--rw private-key-\
   \format?
                 |     |     |  |     |        |     |       identityref
                 |     |     |  |     |        |     +--rw (private-key\
   \-type)
                 |     |     |  |     |        |     |  +--:(private-ke\
   \y)
                 |     |     |  |     |        |     |  |  +--rw privat\
   \e-key?
                 |     |     |  |     |        |     |  |          bina\
   \ry
                 |     |     |  |     |        |     |  +--:(hidden-pri\
   \vate-key)
                 |     |     |  |     |        |     |  |  +--rw hidden\
   \-private-key?
                 |     |     |  |     |        |     |  |          empty
                 |     |     |  |     |        |     |  +--:(encrypted-\
   \private-key)
                 |     |     |  |     |        |     |     +--rw encryp\
   \ted-private-key
                 |     |     |  |     |        |     |        +--rw (ke\
   \y-type)
                 |     |     |  |     |        |     |        |  +--:(s\
   \ymmetric-key-ref)
                 |     |     |  |     |        |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
                 |     |     |  |     |        |     |        |  |     \
   \     {keystore-supported}?
                 |     |     |  |     |        |     |        |  +--:(a\
   \symmetric-key-ref)
                 |     |     |  |     |        |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
                 |     |     |  |     |        |     |        |        \
   \     {keystore-supported}?
                 |     |     |  |     |        |     |        +--rw val\
   \ue?
                 |     |     |  |     |        |     |                b\
   \inary
                 |     |     |  |     |        |     +--rw cert?
                 |     |     |  |     |        |     |       end-entity\
   \-cert-cms
                 |     |     |  |     |        |     +---n certificate-\
   \expiration
                 |     |     |  |     |        |     |  +-- expiration-\
   \date
                 |     |     |  |     |        |     |          yang:da\
   \te-and-time
                 |     |     |  |     |        |     +---x generate-cer\
   \tificate-signing-request
                 |     |     |  |     |        |             {certifica\
   \te-signing-request-generation}?
                 |     |     |  |     |        |        +---w input
                 |     |     |  |     |        |        |  +---w subject
                 |     |     |  |     |        |        |  |       bina\
   \ry
                 |     |     |  |     |        |        |  +---w attrib\
   \utes?
                 |     |     |  |     |        |        |          bina\
   \ry
                 |     |     |  |     |        |        +--ro output
                 |     |     |  |     |        |           +--ro certif\
   \icate-signing-request
                 |     |     |  |     |        |                   ct:c\
   \sr
                 |     |     |  |     |        +--:(keystore)
                 |     |     |  |     |                 {keystore-suppo\
   \rted}?
                 |     |     |  |     |           +--rw keystore-refere\
   \nce
                 |     |     |  |     |              +--rw asymmetric-k\
   \ey?
                 |     |     |  |     |              |       ks:asymmet\
   \ric-key-ref
                 |     |     |  |     |              +--rw certificate?\
   \      leafref
                 |     |     |  |     +--:(raw-public-key)
                 |     |     |  |     |        {raw-public-key-auth}?
                 |     |     |  |     |  +--rw raw-private-key
                 |     |     |  |     |     +--rw (local-or-keystore)
                 |     |     |  |     |        +--:(local)
                 |     |     |  |     |        |        {local-definiti\
   \ons-supported}?
                 |     |     |  |     |        |  +--rw local-definition
                 |     |     |  |     |        |     +--rw public-key-f\
   \ormat
                 |     |     |  |     |        |     |       identityref
                 |     |     |  |     |        |     +--rw public-key
                 |     |     |  |     |        |     |       binary
                 |     |     |  |     |        |     +--rw private-key-\
   \format?
                 |     |     |  |     |        |     |       identityref
                 |     |     |  |     |        |     +--rw (private-key\
   \-type)
                 |     |     |  |     |        |        +--:(private-ke\
   \y)
                 |     |     |  |     |        |        |  +--rw privat\
   \e-key?
                 |     |     |  |     |        |        |          bina\
   \ry
                 |     |     |  |     |        |        +--:(hidden-pri\
   \vate-key)
                 |     |     |  |     |        |        |  +--rw hidden\
   \-private-key?
                 |     |     |  |     |        |        |          empty
                 |     |     |  |     |        |        +--:(encrypted-\
   \private-key)
                 |     |     |  |     |        |           +--rw encryp\
   \ted-private-key
                 |     |     |  |     |        |              +--rw (ke\
   \y-type)
                 |     |     |  |     |        |              |  +--:(s\
   \ymmetric-key-ref)
                 |     |     |  |     |        |              |  |  +--\
   \rw symmetric-key-ref?    leafref
                 |     |     |  |     |        |              |  |     \
   \     {keystore-supported}?
                 |     |     |  |     |        |              |  +--:(a\
   \symmetric-key-ref)
                 |     |     |  |     |        |              |     +--\
   \rw asymmetric-key-ref?   leafref
                 |     |     |  |     |        |              |        \
   \     {keystore-supported}?
                 |     |     |  |     |        |              +--rw val\
   \ue?
                 |     |     |  |     |        |                      b\
   \inary
                 |     |     |  |     |        +--:(keystore)
                 |     |     |  |     |                 {keystore-suppo\
   \rted}?
                 |     |     |  |     |           +--rw keystore-refere\
   \nce?
                 |     |     |  |     |                   ks:asymmetric\
   \-key-ref
                 |     |     |  |     +--:(psk) {psk-auth}?
                 |     |     |  |        +--rw psk
                 |     |     |  |           +--rw (local-or-keystore)
                 |     |     |  |              +--:(local)
                 |     |     |  |              |        {local-definiti\
   \ons-supported}?
                 |     |     |  |              |  +--rw local-definition
                 |     |     |  |              |     +--rw key-format?
                 |     |     |  |              |     |       identityref
                 |     |     |  |              |     +--rw (key-type)
                 |     |     |  |              |     |  +--:(key)
                 |     |     |  |              |     |  |  +--rw key?
                 |     |     |  |              |     |  |          bina\
   \ry
                 |     |     |  |              |     |  +--:(hidden-key)
                 |     |     |  |              |     |  |  +--rw hidden\
   \-key?
                 |     |     |  |              |     |  |          empty
                 |     |     |  |              |     |  +--:(encrypted-\
   \key)
                 |     |     |  |              |     |     +--rw encryp\
   \ted-key
                 |     |     |  |              |     |        +--rw (ke\
   \y-type)
                 |     |     |  |              |     |        |  +--:(s\
   \ymmetric-key-ref)
                 |     |     |  |              |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
                 |     |     |  |              |     |        |  |     \
   \     {keystore-supported}?
                 |     |     |  |              |     |        |  +--:(a\
   \symmetric-key-ref)
                 |     |     |  |              |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
                 |     |     |  |              |     |        |        \
   \     {keystore-supported}?
                 |     |     |  |              |     |        +--rw val\
   \ue?
                 |     |     |  |              |     |                b\
   \inary
                 |     |     |  |              |     +--rw id?
                 |     |     |  |              |             string
                 |     |     |  |              |             {ks:local-\
   \definitions-supported}?
                 |     |     |  |              +--:(keystore)
                 |     |     |  |                       {keystore-suppo\
   \rted}?
                 |     |     |  |                 +--rw keystore-refere\
   \nce?
                 |     |     |  |                         ks:symmetric-\

   \key-ref
                 |     |     |  +--rw server-authentication
                 |     |     |  |  +--rw ca-certs!
                 |     |     |  |  |       {x509-certificate-auth}?
                 |     |     |  |  |  +--rw (local-or-truststore)
                 |     |     |  |  |     +--:(local)
                 |     |     |  |  |     |        {local-definitions-su\
   \pported}?
                 |     |     |  |  |     |  +--rw local-definition
                 |     |     |  |  |     |     +--rw cert*
                 |     |     |  |  |     |     |       trust-anchor-cer\
   \t-cms
                 |     |     |  |  |     |     +---n certificate-expira\
   \tion
                 |     |     |  |  |     |        +-- expiration-date
                 |     |     |  |  |     |                yang:date-and\
   \-time
                 |     |     |  |  |     +--:(truststore)
                 |     |     |  |  |              {truststore-supported\
   \,certificates}?
                 |     |     |  |  |        +--rw truststore-reference?
                 |     |     |  |  |                ts:certificate-bag-\
   \ref
                 |     |     |  |  +--rw ee-certs!
                 |     |     |  |  |       {x509-certificate-auth}?
                 |     |     |  |  |  +--rw (local-or-truststore)
                 |     |     |  |  |     +--:(local)
                 |     |     |  |  |     |        {local-definitions-su\
   \pported}?
                 |     |     |  |  |     |  +--rw local-definition
                 |     |     |  |  |     |     +--rw cert*
                 |     |     |  |  |     |     |       trust-anchor-cer\
   \t-cms
                 |     |     |  |  |     |     +---n certificate-expira\
   \tion
                 |     |     |  |  |     |        +-- expiration-date
                 |     |     |  |  |     |                yang:date-and\
   \-time
                 |     |     |  |  |     +--:(truststore)
                 |     |     |  |  |              {truststore-supported\
   \,certificates}?
                 |     |     |  |  |        +--rw truststore-reference?
                 |     |     |  |  |                ts:certificate-bag-\
   \ref
                 |     |     |  |  +--rw raw-public-keys!
                 |     |     |  |  |       {raw-public-key-auth}?
                 |     |     |  |  |  +--rw (local-or-truststore)
                 |     |     |  |  |     +--:(local)
                 |     |     |  |  |     |        {local-definitions-su\
   \pported}?
                 |     |     |  |  |     |  +--rw local-definition
                 |     |     |  |  |     |     +--rw public-key* [name]
                 |     |     |  |  |     |        +--rw name
                 |     |     |  |  |     |        |       string
                 |     |     |  |  |     |        +--rw public-key-form\
   \at
                 |     |     |  |  |     |        |       identityref
                 |     |     |  |  |     |        +--rw public-key
                 |     |     |  |  |     |                binary
                 |     |     |  |  |     +--:(truststore)
                 |     |     |  |  |              {truststore-supported\
   \,public-keys}?
                 |     |     |  |  |        +--rw truststore-reference?
                 |     |     |  |  |                ts:public-key-bag-r\
   \ef
                 |     |     |  |  +--rw psks! {psk-auth}?
                 |     |     |  +--rw hello-params
                 |     |     |  |       {tls-client-hello-params-config\
   \}?
                 |     |     |  |  +--rw tls-versions
                 |     |     |  |  |  +--rw tls-version*   identityref
                 |     |     |  |  +--rw cipher-suites
                 |     |     |  |     +--rw cipher-suite*   identityref
                 |     |     |  +--rw keepalives
                 |     |     |          {tls-client-keepalives}?
                 |     |     |     +--rw peer-allowed-to-send?   empty
                 |     |     |     +--rw test-peer-aliveness!
                 |     |     |        +--rw max-wait?       uint16
                 |     |     |        +--rw max-attempts?   uint8
                 |     |     +--rw http-client-parameters
                 |     |        +--rw client-identity!
                 |     |           +--rw (auth-type)?
                 |     |              +--:(basic)
                 |     |                 +--rw basic {basic-auth}?
                 |     |                    +--rw user-id     string
                 |     |                    +--rw password    string
                 |     +--rw restconf-client-parameters
                 +--:(https) {https-listen}?
                    +--rw https
                       +--rw tcp-server-parameters
                       |  +--rw local-address    inet:ip-address
                       |  +--rw local-port?      inet:port-number
                       |  +--rw keepalives! {keepalives-supported}?
                       |     +--rw idle-time         uint16
                       |     +--rw max-probes        uint16
                       |     +--rw probe-interval    uint16
                       +--rw tls-client-parameters
                       |  +--rw client-identity
                       |  |  +--rw (auth-type)?
                       |  |     +--:(certificate)
                       |  |     |        {x509-certificate-auth}?
                       |  |     |  +--rw certificate
                       |  |     |     +--rw (local-or-keystore)
                       |  |     |        +--:(local)
                       |  |     |        |        {local-definitions-su\
   \pported}?
                       |  |     |        |  +--rw local-definition
                       |  |     |        |     +--rw public-key-format
                       |  |     |        |     |       identityref
                       |  |     |        |     +--rw public-key
                       |  |     |        |     |       binary
                       |  |     |        |     +--rw private-key-format?
                       |  |     |        |     |       identityref
                       |  |     |        |     +--rw (private-key-type)
                       |  |     |        |     |  +--:(private-key)
                       |  |     |        |     |  |  +--rw private-key?
                       |  |     |        |     |  |          binary
                       |  |     |        |     |  +--:(hidden-private-k\
   \ey)
                       |  |     |        |     |  |  +--rw hidden-priva\
   \te-key?
                       |  |     |        |     |  |          empty
                       |  |     |        |     |  +--:(encrypted-privat\
   \e-key)
                       |  |     |        |     |     +--rw encrypted-pr\
   \ivate-key
                       |  |     |        |     |        +--rw (key-type)
                       |  |     |        |     |        |  +--:(symmetr\
   \ic-key-ref)
                       |  |     |        |     |        |  |  +--rw sym\
   \metric-key-ref?    leafref
                       |  |     |        |     |        |  |          {\
   \keystore-supported}?
                       |  |     |        |     |        |  +--:(asymmet\
   \ric-key-ref)
                       |  |     |        |     |        |     +--rw asy\
   \mmetric-key-ref?   leafref
                       |  |     |        |     |        |             {\
   \keystore-supported}?
                       |  |     |        |     |        +--rw value?
                       |  |     |        |     |                binary
                       |  |     |        |     +--rw cert?
                       |  |     |        |     |       end-entity-cert-\
   \cms
                       |  |     |        |     +---n certificate-expira\
   \tion
                       |  |     |        |     |  +-- expiration-date
                       |  |     |        |     |          yang:date-and\
   \-time
                       |  |     |        |     +---x generate-certifica\
   \te-signing-request
                       |  |     |        |             {certificate-sig\
   \ning-request-generation}?
                       |  |     |        |        +---w input
                       |  |     |        |        |  +---w subject
                       |  |     |        |        |  |       binary
                       |  |     |        |        |  +---w attributes?
                       |  |     |        |        |          binary
                       |  |     |        |        +--ro output
                       |  |     |        |           +--ro certificate-\
   \signing-request
                       |  |     |        |                   ct:csr
                       |  |     |        +--:(keystore)
                       |  |     |                 {keystore-supported}?
                       |  |     |           +--rw keystore-reference
                       |  |     |              +--rw asymmetric-key?
                       |  |     |              |       ks:asymmetric-ke\
   \y-ref
                       |  |     |              +--rw certificate?      \
   \leafref
                       |  |     +--:(raw-public-key)
                       |  |     |        {raw-public-key-auth}?
                       |  |     |  +--rw raw-private-key
                       |  |     |     +--rw (local-or-keystore)
                       |  |     |        +--:(local)
                       |  |     |        |        {local-definitions-su\
   \pported}?
                       |  |     |        |  +--rw local-definition
                       |  |     |        |     +--rw public-key-format
                       |  |     |        |     |       identityref
                       |  |     |        |     +--rw public-key
                       |  |     |        |     |       binary
                       |  |     |        |     +--rw private-key-format?
                       |  |     |        |     |       identityref
                       |  |     |        |     +--rw (private-key-type)
                       |  |     |        |        +--:(private-key)
                       |  |     |        |        |  +--rw private-key?
                       |  |     |        |        |          binary
                       |  |     |        |        +--:(hidden-private-k\
   \ey)
                       |  |     |        |        |  +--rw hidden-priva\
   \te-key?
                       |  |     |        |        |          empty
                       |  |     |        |        +--:(encrypted-privat\
   \e-key)
                       |  |     |        |           +--rw encrypted-pr\
   \ivate-key
                       |  |     |        |              +--rw (key-type)
                       |  |     |        |              |  +--:(symmetr\
   \ic-key-ref)
                       |  |     |        |              |  |  +--rw sym\
   \metric-key-ref?    leafref
                       |  |     |        |              |  |          {\
   \keystore-supported}?
                       |  |     |        |              |  +--:(asymmet\
   \ric-key-ref)
                       |  |     |        |              |     +--rw asy\
   \mmetric-key-ref?   leafref
                       |  |     |        |              |             {\
   \keystore-supported}?
                       |  |     |        |              +--rw value?
                       |  |     |        |                      binary
                       |  |     |        +--:(keystore)
                       |  |     |                 {keystore-supported}?
                       |  |     |           +--rw keystore-reference?
                       |  |     |                   ks:asymmetric-key-r\
   \ef
                       |  |     +--:(psk) {psk-auth}?
                       |  |        +--rw psk
                       |  |           +--rw (local-or-keystore)
                       |  |              +--:(local)
                       |  |              |        {local-definitions-su\
   \pported}?
                       |  |              |  +--rw local-definition
                       |  |              |     +--rw key-format?
                       |  |              |     |       identityref
                       |  |              |     +--rw (key-type)
                       |  |              |     |  +--:(key)
                       |  |              |     |  |  +--rw key?
                       |  |              |     |  |          binary
                       |  |              |     |  +--:(hidden-key)
                       |  |              |     |  |  +--rw hidden-key?
                       |  |              |     |  |          empty
                       |  |              |     |  +--:(encrypted-key)
                       |  |              |     |     +--rw encrypted-key
                       |  |              |     |        +--rw (key-type)
                       |  |              |     |        |  +--:(symmetr\
   \ic-key-ref)
                       |  |              |     |        |  |  +--rw sym\
   \metric-key-ref?    leafref
                       |  |              |     |        |  |          {\
   \keystore-supported}?
                       |  |              |     |        |  +--:(asymmet\
   \ric-key-ref)
                       |  |              |     |        |     +--rw asy\
   \mmetric-key-ref?   leafref
                       |  |              |     |        |             {\
   \keystore-supported}?
                       |  |              |     |        +--rw value?
                       |  |              |     |                binary
                       |  |              |     +--rw id?
                       |  |              |             string
                       |  |              |             {ks:local-defini\
   \tions-supported}?
                       |  |              +--:(keystore)
                       |  |                       {keystore-supported}?
                       |  |                 +--rw keystore-reference?
                       |  |                         ks:symmetric-key-ref
                       |  +--rw server-authentication
                       |  |  +--rw ca-certs! {x509-certificate-auth}?
                       |  |  |  +--rw (local-or-truststore)
                       |  |  |     +--:(local)
                       |  |  |     |        {local-definitions-supporte\
   \d}?
                       |  |  |     |  +--rw local-definition
                       |  |  |     |     +--rw cert*
                       |  |  |     |     |       trust-anchor-cert-cms
                       |  |  |     |     +---n certificate-expiration
                       |  |  |     |        +-- expiration-date
                       |  |  |     |                yang:date-and-time
                       |  |  |     +--:(truststore)
                       |  |  |              {truststore-supported,certi\
   \ficates}?
                       |  |  |        +--rw truststore-reference?
                       |  |  |                ts:certificate-bag-ref
                       |  |  +--rw ee-certs! {x509-certificate-auth}?
                       |  |  |  +--rw (local-or-truststore)
                       |  |  |     +--:(local)
                       |  |  |     |        {local-definitions-supporte\
   \d}?
                       |  |  |     |  +--rw local-definition
                       |  |  |     |     +--rw cert*
                       |  |  |     |     |       trust-anchor-cert-cms
                       |  |  |     |     +---n certificate-expiration
                       |  |  |     |        +-- expiration-date
                       |  |  |     |                yang:date-and-time
                       |  |  |     +--:(truststore)
                       |  |  |              {truststore-supported,certi\

   \ficates}?
                       |  |  |        +--rw truststore-reference?
                       |  |  |                ts:certificate-bag-ref
                       |  |  +--rw raw-public-keys!
                       |  |  |       {raw-public-key-auth}?
                       |  |  |  +--rw (local-or-truststore)
                       |  |  |     +--:(local)
                       |  |  |     |        {local-definitions-supporte\
   \d}?
                       |  |  |     |  +--rw local-definition
                       |  |  |     |     +--rw public-key* [name]
                       |  |  |     |        +--rw name
                       |  |  |     |        |       string
                       |  |  |     |        +--rw public-key-format
                       |  |  |     |        |       identityref
                       |  |  |     |        +--rw public-key
                       |  |  |     |                binary
                       |  |  |     +--:(truststore)
                       |  |  |              {truststore-supported,publi\
   \c-keys}?
                       |  |  |        +--rw truststore-reference?
                       |  |  |                ts:public-key-bag-ref
                       |  |  +--rw psks! {psk-auth}?
                       |  +--rw hello-params
                       |  |       {tls-client-hello-params-config}?
                       |  |  +--rw tls-versions
                       |  |  |  +--rw tls-version*   identityref
                       |  |  +--rw cipher-suites
                       |  |     +--rw cipher-suite*   identityref
                       |  +--rw keepalives {tls-client-keepalives}?
                       |     +--rw peer-allowed-to-send?   empty
                       |     +--rw test-peer-aliveness!
                       |        +--rw max-wait?       uint16
                       |        +--rw max-attempts?   uint8
                       +--rw http-client-parameters
                       |  +--rw client-identity!
                       |  |  +--rw (auth-type)?
                       |  |     +--:(basic)
                       |  |        +--rw basic {basic-auth}?
                       |  |           +--rw user-id     string
                       |  |           +--rw password    string
                       |  +--rw proxy-server! {proxy-connect}?
                       |     +--rw tcp-client-parameters
                       |     |  +--rw remote-address    inet:host
                       |     |  +--rw remote-port?      inet:port-number
                       |     |  +--rw local-address?    inet:ip-address
                       |     |  |       {local-binding-supported}?
                       |     |  +--rw local-port?       inet:port-number
                       |     |  |       {local-binding-supported}?
                       |     |  +--rw keepalives!
                       |     |          {keepalives-supported}?
                       |     |     +--rw idle-time         uint16
                       |     |     +--rw max-probes        uint16
                       |     |     +--rw probe-interval    uint16
                       |     +--rw tls-client-parameters
                       |     |  +--rw client-identity
                       |     |  |  +--rw (auth-type)?
                       |     |  |     +--:(certificate)
                       |     |  |     |        {x509-certificate-auth}?
                       |     |  |     |  +--rw certificate
                       |     |  |     |     +--rw (local-or-keystore)
                       |     |  |     |        +--:(local)
                       |     |  |     |        |        {local-definiti\
   \ons-supported}?
                       |     |  |     |        |  +--rw local-definition
                       |     |  |     |        |     +--rw public-key-f\
   \ormat
                       |     |  |     |        |     |       identityref
                       |     |  |     |        |     +--rw public-key
                       |     |  |     |        |     |       binary
                       |     |  |     |        |     +--rw private-key-\
   \format?
                       |     |  |     |        |     |       identityref
                       |     |  |     |        |     +--rw (private-key\
   \-type)
                       |     |  |     |        |     |  +--:(private-ke\
   \y)
                       |     |  |     |        |     |  |  +--rw privat\
   \e-key?
                       |     |  |     |        |     |  |          bina\
   \ry
                       |     |  |     |        |     |  +--:(hidden-pri\
   \vate-key)
                       |     |  |     |        |     |  |  +--rw hidden\
   \-private-key?
                       |     |  |     |        |     |  |          empty
                       |     |  |     |        |     |  +--:(encrypted-\
   \private-key)
                       |     |  |     |        |     |     +--rw encryp\
   \ted-private-key
                       |     |  |     |        |     |        +--rw (ke\
   \y-type)
                       |     |  |     |        |     |        |  +--:(s\
   \ymmetric-key-ref)
                       |     |  |     |        |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
                       |     |  |     |        |     |        |  |     \
   \     {keystore-supported}?
                       |     |  |     |        |     |        |  +--:(a\
   \symmetric-key-ref)
                       |     |  |     |        |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
                       |     |  |     |        |     |        |        \
   \     {keystore-supported}?
                       |     |  |     |        |     |        +--rw val\
   \ue?
                       |     |  |     |        |     |                b\
   \inary
                       |     |  |     |        |     +--rw cert?
                       |     |  |     |        |     |       end-entity\
   \-cert-cms
                       |     |  |     |        |     +---n certificate-\
   \expiration
                       |     |  |     |        |     |  +-- expiration-\
   \date
                       |     |  |     |        |     |          yang:da\
   \te-and-time
                       |     |  |     |        |     +---x generate-cer\
   \tificate-signing-request
                       |     |  |     |        |             {certifica\
   \te-signing-request-generation}?
                       |     |  |     |        |        +---w input
                       |     |  |     |        |        |  +---w subject
                       |     |  |     |        |        |  |       bina\
   \ry
                       |     |  |     |        |        |  +---w attrib\
   \utes?
                       |     |  |     |        |        |          bina\
   \ry
                       |     |  |     |        |        +--ro output
                       |     |  |     |        |           +--ro certif\
   \icate-signing-request
                       |     |  |     |        |                   ct:c\
   \sr
                       |     |  |     |        +--:(keystore)
                       |     |  |     |                 {keystore-suppo\
   \rted}?
                       |     |  |     |           +--rw keystore-refere\
   \nce
                       |     |  |     |              +--rw asymmetric-k\
   \ey?
                       |     |  |     |              |       ks:asymmet\
   \ric-key-ref
                       |     |  |     |              +--rw certificate?\

   \      leafref
                       |     |  |     +--:(raw-public-key)
                       |     |  |     |        {raw-public-key-auth}?
                       |     |  |     |  +--rw raw-private-key
                       |     |  |     |     +--rw (local-or-keystore)
                       |     |  |     |        +--:(local)
                       |     |  |     |        |        {local-definiti\
   \ons-supported}?
                       |     |  |     |        |  +--rw local-definition
                       |     |  |     |        |     +--rw public-key-f\
   \ormat
                       |     |  |     |        |     |       identityref
                       |     |  |     |        |     +--rw public-key
                       |     |  |     |        |     |       binary
                       |     |  |     |        |     +--rw private-key-\
   \format?
                       |     |  |     |        |     |       identityref
                       |     |  |     |        |     +--rw (private-key\
   \-type)
                       |     |  |     |        |        +--:(private-ke\
   \y)
                       |     |  |     |        |        |  +--rw privat\
   \e-key?
                       |     |  |     |        |        |          bina\
   \ry
                       |     |  |     |        |        +--:(hidden-pri\
   \vate-key)
                       |     |  |     |        |        |  +--rw hidden\
   \-private-key?
                       |     |  |     |        |        |          empty
                       |     |  |     |        |        +--:(encrypted-\
   \private-key)
                       |     |  |     |        |           +--rw encryp\
   \ted-private-key
                       |     |  |     |        |              +--rw (ke\
   \y-type)
                       |     |  |     |        |              |  +--:(s\
   \ymmetric-key-ref)
                       |     |  |     |        |              |  |  +--\
   \rw symmetric-key-ref?    leafref
                       |     |  |     |        |              |  |     \
   \     {keystore-supported}?
                       |     |  |     |        |              |  +--:(a\
   \symmetric-key-ref)
                       |     |  |     |        |              |     +--\
   \rw asymmetric-key-ref?   leafref
                       |     |  |     |        |              |        \
   \     {keystore-supported}?
                       |     |  |     |        |              +--rw val\
   \ue?
                       |     |  |     |        |                      b\
   \inary
                       |     |  |     |        +--:(keystore)
                       |     |  |     |                 {keystore-suppo\
   \rted}?
                       |     |  |     |           +--rw keystore-refere\
   \nce?
                       |     |  |     |                   ks:asymmetric\
   \-key-ref
                       |     |  |     +--:(psk) {psk-auth}?
                       |     |  |        +--rw psk
                       |     |  |           +--rw (local-or-keystore)
                       |     |  |              +--:(local)
                       |     |  |              |        {local-definiti\
   \ons-supported}?
                       |     |  |              |  +--rw local-definition
                       |     |  |              |     +--rw key-format?
                       |     |  |              |     |       identityref
                       |     |  |              |     +--rw (key-type)
                       |     |  |              |     |  +--:(key)
                       |     |  |              |     |  |  +--rw key?
                       |     |  |              |     |  |          bina\
   \ry
                       |     |  |              |     |  +--:(hidden-key)
                       |     |  |              |     |  |  +--rw hidden\
   \-key?
                       |     |  |              |     |  |          empty
                       |     |  |              |     |  +--:(encrypted-\
   \key)
                       |     |  |              |     |     +--rw encryp\
   \ted-key
                       |     |  |              |     |        +--rw (ke\
   \y-type)
                       |     |  |              |     |        |  +--:(s\
   \ymmetric-key-ref)
                       |     |  |              |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
                       |     |  |              |     |        |  |     \
   \     {keystore-supported}?
                       |     |  |              |     |        |  +--:(a\
   \symmetric-key-ref)
                       |     |  |              |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
                       |     |  |              |     |        |        \
   \     {keystore-supported}?
                       |     |  |              |     |        +--rw val\

   \ue?
                       |     |  |              |     |                b\
   \inary
                       |     |  |              |     +--rw id?
                       |     |  |              |             string
                       |     |  |              |             {ks:local-\
   \definitions-supported}?
                       |     |  |              +--:(keystore)
                       |     |  |                       {keystore-suppo\
   \rted}?
                       |     |  |                 +--rw keystore-refere\
   \nce?
                       |     |  |                         ks:symmetric-\
   \key-ref
                       |     |  +--rw server-authentication
                       |     |  |  +--rw ca-certs!
                       |     |  |  |       {x509-certificate-auth}?
                       |     |  |  |  +--rw (local-or-truststore)
                       |     |  |  |     +--:(local)
                       |     |  |  |     |        {local-definitions-su\
   \pported}?
                       |     |  |  |     |  +--rw local-definition
                       |     |  |  |     |     +--rw cert*
                       |     |  |  |     |     |       trust-anchor-cer\
   \t-cms
                       |     |  |  |     |     +---n certificate-expira\
   \tion
                       |     |  |  |     |        +-- expiration-date
                       |     |  |  |     |                yang:date-and\
   \-time
                       |     |  |  |     +--:(truststore)
                       |     |  |  |              {truststore-supported\
   \,certificates}?
                       |     |  |  |        +--rw truststore-reference?
                       |     |  |  |                ts:certificate-bag-\
   \ref
                       |     |  |  +--rw ee-certs!
                       |     |  |  |       {x509-certificate-auth}?
                       |     |  |  |  +--rw (local-or-truststore)
                       |     |  |  |     +--:(local)
                       |     |  |  |     |        {local-definitions-su\
   \pported}?
                       |     |  |  |     |  +--rw local-definition
                       |     |  |  |     |     +--rw cert*
                       |     |  |  |     |     |       trust-anchor-cer\
   \t-cms
                       |     |  |  |     |     +---n certificate-expira\
   \tion
                       |     |  |  |     |        +-- expiration-date
                       |     |  |  |     |                yang:date-and\
   \-time
                       |     |  |  |     +--:(truststore)
                       |     |  |  |              {truststore-supported\
   \,certificates}?
                       |     |  |  |        +--rw truststore-reference?
                       |     |  |  |                ts:certificate-bag-\
   \ref
                       |     |  |  +--rw raw-public-keys!
                       |     |  |  |       {raw-public-key-auth}?
                       |     |  |  |  +--rw (local-or-truststore)
                       |     |  |  |     +--:(local)
                       |     |  |  |     |        {local-definitions-su\
   \pported}?
                       |     |  |  |     |  +--rw local-definition
                       |     |  |  |     |     +--rw public-key* [name]
                       |     |  |  |     |        +--rw name
                       |     |  |  |     |        |       string
                       |     |  |  |     |        +--rw public-key-form\
   \at
                       |     |  |  |     |        |       identityref
                       |     |  |  |     |        +--rw public-key
                       |     |  |  |     |                binary
                       |     |  |  |     +--:(truststore)
                       |     |  |  |              {truststore-supported\
   \,public-keys}?
                       |     |  |  |        +--rw truststore-reference?
                       |     |  |  |                ts:public-key-bag-r\
   \ef
                       |     |  |  +--rw psks! {psk-auth}?
                       |     |  +--rw hello-params
                       |     |  |       {tls-client-hello-params-config\
   \}?
                       |     |  |  +--rw tls-versions
                       |     |  |  |  +--rw tls-version*   identityref
                       |     |  |  +--rw cipher-suites
                       |     |  |     +--rw cipher-suite*   identityref
                       |     |  +--rw keepalives
                       |     |          {tls-client-keepalives}?
                       |     |     +--rw peer-allowed-to-send?   empty
                       |     |     +--rw test-peer-aliveness!
                       |     |        +--rw max-wait?       uint16
                       |     |        +--rw max-attempts?   uint8
                       |     +--rw http-client-parameters
                       |        +--rw client-identity!
                       |           +--rw (auth-type)?
                       |              +--:(basic)
                       |                 +--rw basic {basic-auth}?
                       |                    +--rw user-id     string
                       |                    +--rw password    string
                       +--rw restconf-client-parameters

A.2.  Expanded Tree Diagram for 'ietf-restconf-server'

   The following tree diagram [RFC8340] provides an overview of the data
   model for the "ietf-restconf-server" module.

   This tree diagram shows all the nodes defined in this module,
   including those defined by "grouping" statements used by this module.

   Please see Section 3.1 for a tree diagram that illustrates what the
   module looks like without all the "grouping" statements expanded.

   ========== NOTE: '\\' line wrapping per BCP XXX (RFC XXXX) ==========

   module: ietf-restconf-server
     +--rw restconf-server
        +--rw listen! {http-listen or https-listen}?
        |  +--rw endpoint* [name]
        |     +--rw name           string
        |     +--rw (transport)
        |        +--:(http) {http-listen}?
        |        |  +--rw http
        |        |     +--rw external-endpoint!
        |        |     |  +--rw address    inet:ip-address
        |        |     |  +--rw port?      inet:port-number
        |        |     +--rw tcp-server-parameters
        |        |     |  +--rw local-address    inet:ip-address
        |        |     |  +--rw local-port?      inet:port-number
        |        |     |  +--rw keepalives! {keepalives-supported}?
        |        |     |     +--rw idle-time         uint16
        |        |     |     +--rw max-probes        uint16
        |        |     |     +--rw probe-interval    uint16
        |        |     +--rw http-server-parameters
        |        |     |  +--rw server-name?             string
        |        |     |  +--rw client-authentication!
        |        |     |          {client-auth-config-supported}?
        |        |     |     +--rw users
        |        |     |        +--rw user* [user-id]
        |        |     |           +--rw user-id        string
        |        |     |           +--rw (auth-type)?
        |        |     |              +--:(basic)
        |        |     |                 +--rw basic {basic-auth}?
        |        |     |                    +--rw user-id?    string
        |        |     |                    +--rw password?
        |        |     |                            ianach:crypt-hash
        |        |     +--rw restconf-server-parameters
        |        |        +--rw client-identity-mappings
        |        |           +--rw cert-to-name* [id]
        |        |              +--rw id             uint32
        |        |              +--rw fingerprint?
        |        |              |       x509c2n:tls-fingerprint
        |        |              +--rw map-type       identityref
        |        |              +--rw name           string
        |        +--:(https) {https-listen}?
        |           +--rw https
        |              +--rw tcp-server-parameters
        |              |  +--rw local-address    inet:ip-address
        |              |  +--rw local-port?      inet:port-number
        |              |  +--rw keepalives! {keepalives-supported}?
        |              |     +--rw idle-time         uint16
        |              |     +--rw max-probes        uint16
        |              |     +--rw probe-interval    uint16
        |              +--rw tls-server-parameters
        |              |  +--rw server-identity
        |              |  |  +--rw (auth-type)
        |              |  |     +--:(certificate)
        |              |  |     |        {x509-certificate-auth}?
        |              |  |     |  +--rw certificate
        |              |  |     |     +--rw (local-or-keystore)
        |              |  |     |        +--:(local)
        |              |  |     |        |        {local-definitions-su\
   \pported}?
        |              |  |     |        |  +--rw local-definition
        |              |  |     |        |     +--rw public-key-format
        |              |  |     |        |     |       identityref
        |              |  |     |        |     +--rw public-key
        |              |  |     |        |     |       binary
        |              |  |     |        |     +--rw private-key-format?
        |              |  |     |        |     |       identityref
        |              |  |     |        |     +--rw (private-key-type)
        |              |  |     |        |     |  +--:(private-key)
        |              |  |     |        |     |  |  +--rw private-key?
        |              |  |     |        |     |  |          binary
        |              |  |     |        |     |  +--:(hidden-private-k\
   \ey)
        |              |  |     |        |     |  |  +--rw hidden-priva\
   \te-key?
        |              |  |     |        |     |  |          empty
        |              |  |     |        |     |  +--:(encrypted-privat\
   \e-key)
        |              |  |     |        |     |     +--rw encrypted-pr\
   \ivate-key
        |              |  |     |        |     |        +--rw (key-type)
        |              |  |     |        |     |        |  +--:(symmetr\
   \ic-key-ref)
        |              |  |     |        |     |        |  |  +--rw sym\
   \metric-key-ref?    leafref
        |              |  |     |        |     |        |  |          {\
   \keystore-supported}?
        |              |  |     |        |     |        |  +--:(asymmet\
   \ric-key-ref)
        |              |  |     |        |     |        |     +--rw asy\
   \mmetric-key-ref?   leafref
        |              |  |     |        |     |        |             {\
   \keystore-supported}?
        |              |  |     |        |     |        +--rw value?
        |              |  |     |        |     |                binary
        |              |  |     |        |     +--rw cert?
        |              |  |     |        |     |       end-entity-cert-\
   \cms
        |              |  |     |        |     +---n certificate-expira\
   \tion
        |              |  |     |        |     |  +-- expiration-date
        |              |  |     |        |     |          yang:date-and\
   \-time
        |              |  |     |        |     +---x generate-certifica\
   \te-signing-request
        |              |  |     |        |             {certificate-sig\
   \ning-request-generation}?
        |              |  |     |        |        +---w input
        |              |  |     |        |        |  +---w subject
        |              |  |     |        |        |  |       binary
        |              |  |     |        |        |  +---w attributes?
        |              |  |     |        |        |          binary
        |              |  |     |        |        +--ro output
        |              |  |     |        |           +--ro certificate-\
   \signing-request
        |              |  |     |        |                   ct:csr
        |              |  |     |        +--:(keystore)
        |              |  |     |                 {keystore-supported}?
        |              |  |     |           +--rw keystore-reference
        |              |  |     |              +--rw asymmetric-key?
        |              |  |     |              |       ks:asymmetric-ke\
   \y-ref
        |              |  |     |              +--rw certificate?      \
   \leafref
        |              |  |     +--:(raw-private-key)
        |              |  |     |        {raw-public-key-auth}?
        |              |  |     |  +--rw raw-private-key
        |              |  |     |     +--rw (local-or-keystore)
        |              |  |     |        +--:(local)
        |              |  |     |        |        {local-definitions-su\
   \pported}?
        |              |  |     |        |  +--rw local-definition
        |              |  |     |        |     +--rw public-key-format
        |              |  |     |        |     |       identityref
        |              |  |     |        |     +--rw public-key
        |              |  |     |        |     |       binary
        |              |  |     |        |     +--rw private-key-format?
        |              |  |     |        |     |       identityref
        |              |  |     |        |     +--rw (private-key-type)
        |              |  |     |        |        +--:(private-key)
        |              |  |     |        |        |  +--rw private-key?
        |              |  |     |        |        |          binary
        |              |  |     |        |        +--:(hidden-private-k\
   \ey)
        |              |  |     |        |        |  +--rw hidden-priva\
   \te-key?
        |              |  |     |        |        |          empty
        |              |  |     |        |        +--:(encrypted-privat\
   \e-key)
        |              |  |     |        |           +--rw encrypted-pr\
   \ivate-key
        |              |  |     |        |              +--rw (key-type)
        |              |  |     |        |              |  +--:(symmetr\
   \ic-key-ref)
        |              |  |     |        |              |  |  +--rw sym\
   \metric-key-ref?    leafref
        |              |  |     |        |              |  |          {\
   \keystore-supported}?
        |              |  |     |        |              |  +--:(asymmet\
   \ric-key-ref)
        |              |  |     |        |              |     +--rw asy\
   \mmetric-key-ref?   leafref
        |              |  |     |        |              |             {\
   \keystore-supported}?
        |              |  |     |        |              +--rw value?
        |              |  |     |        |                      binary
        |              |  |     |        +--:(keystore)
        |              |  |     |                 {keystore-supported}?
        |              |  |     |           +--rw keystore-reference?
        |              |  |     |                   ks:asymmetric-key-r\
   \ef
        |              |  |     +--:(psk) {psk-auth}?
        |              |  |        +--rw psk
        |              |  |           +--rw (local-or-keystore)
        |              |  |              +--:(local)
        |              |  |              |        {local-definitions-su\

   \pported}?
        |              |  |              |  +--rw local-definition
        |              |  |              |     +--rw key-format?
        |              |  |              |     |       identityref
        |              |  |              |     +--rw (key-type)
        |              |  |              |     |  +--:(key)
        |              |  |              |     |  |  +--rw key?
        |              |  |              |     |  |          binary
        |              |  |              |     |  +--:(hidden-key)
        |              |  |              |     |  |  +--rw hidden-key?
        |              |  |              |     |  |          empty
        |              |  |              |     |  +--:(encrypted-key)
        |              |  |              |     |     +--rw encrypted-key
        |              |  |              |     |        +--rw (key-type)
        |              |  |              |     |        |  +--:(symmetr\
   \ic-key-ref)
        |              |  |              |     |        |  |  +--rw sym\
   \metric-key-ref?    leafref
        |              |  |              |     |        |  |          {\
   \keystore-supported}?
        |              |  |              |     |        |  +--:(asymmet\
   \ric-key-ref)
        |              |  |              |     |        |     +--rw asy\
   \mmetric-key-ref?   leafref
        |              |  |              |     |        |             {\
   \keystore-supported}?
        |              |  |              |     |        +--rw value?
        |              |  |              |     |                binary
        |              |  |              |     +--rw id?
        |              |  |              |             string
        |              |  |              |             {ks:local-defini\
   \tions-supported}?
        |              |  |              +--:(keystore)
        |              |  |                       {keystore-supported}?
        |              |  |                 +--rw keystore-reference?
        |              |  |                         ks:symmetric-key-ref
        |              |  +--rw client-authentication!
        |              |  |       {client-auth-config-supported}?
        |              |  |  +--rw ca-certs! {x509-certificate-auth}?
        |              |  |  |  +--rw (local-or-truststore)
        |              |  |  |     +--:(local)
        |              |  |  |     |        {local-definitions-supporte\
   \d}?
        |              |  |  |     |  +--rw local-definition
        |              |  |  |     |     +--rw cert*
        |              |  |  |     |     |       trust-anchor-cert-cms
        |              |  |  |     |     +---n certificate-expiration
        |              |  |  |     |        +-- expiration-date
        |              |  |  |     |                yang:date-and-time
        |              |  |  |     +--:(truststore)
        |              |  |  |              {truststore-supported,certi\
   \ficates}?
        |              |  |  |        +--rw truststore-reference?
        |              |  |  |                ts:certificate-bag-ref
        |              |  |  +--rw ee-certs! {x509-certificate-auth}?
        |              |  |  |  +--rw (local-or-truststore)
        |              |  |  |     +--:(local)
        |              |  |  |     |        {local-definitions-supporte\
   \d}?
        |              |  |  |     |  +--rw local-definition
        |              |  |  |     |     +--rw cert*
        |              |  |  |     |     |       trust-anchor-cert-cms
        |              |  |  |     |     +---n certificate-expiration
        |              |  |  |     |        +-- expiration-date
        |              |  |  |     |                yang:date-and-time
        |              |  |  |     +--:(truststore)
        |              |  |  |              {truststore-supported,certi\
   \ficates}?
        |              |  |  |        +--rw truststore-reference?
        |              |  |  |                ts:certificate-bag-ref
        |              |  |  +--rw raw-public-keys!
        |              |  |  |       {raw-public-key-auth}?
        |              |  |  |  +--rw (local-or-truststore)
        |              |  |  |     +--:(local)
        |              |  |  |     |        {local-definitions-supporte\
   \d}?
        |              |  |  |     |  +--rw local-definition
        |              |  |  |     |     +--rw public-key* [name]
        |              |  |  |     |        +--rw name
        |              |  |  |     |        |       string
        |              |  |  |     |        +--rw public-key-format
        |              |  |  |     |        |       identityref
        |              |  |  |     |        +--rw public-key
        |              |  |  |     |                binary
        |              |  |  |     +--:(truststore)
        |              |  |  |              {truststore-supported,publi\
   \c-keys}?
        |              |  |  |        +--rw truststore-reference?
        |              |  |  |                ts:public-key-bag-ref
        |              |  |  +--rw psks! {psk-auth}?
        |              |  +--rw hello-params
        |              |  |       {tls-server-hello-params-config}?
        |              |  |  +--rw tls-versions
        |              |  |  |  +--rw tls-version*   identityref
        |              |  |  +--rw cipher-suites
        |              |  |     +--rw cipher-suite*   identityref
        |              |  +--rw keepalives {tls-server-keepalives}?
        |              |     +--rw peer-allowed-to-send?   empty
        |              |     +--rw test-peer-aliveness!
        |              |        +--rw max-wait?       uint16
        |              |        +--rw max-attempts?   uint8
        |              +--rw http-server-parameters
        |              |  +--rw server-name?             string
        |              |  +--rw client-authentication!
        |              |          {client-auth-config-supported}?
        |              |     +--rw users
        |              |        +--rw user* [user-id]
        |              |           +--rw user-id        string
        |              |           +--rw (auth-type)?
        |              |              +--:(basic)
        |              |                 +--rw basic {basic-auth}?
        |              |                    +--rw user-id?    string
        |              |                    +--rw password?
        |              |                            ianach:crypt-hash
        |              +--rw restconf-server-parameters
        |                 +--rw client-identity-mappings
        |                    +--rw cert-to-name* [id]
        |                       +--rw id             uint32
        |                       +--rw fingerprint?
        |                       |       x509c2n:tls-fingerprint
        |                       +--rw map-type       identityref
        |                       +--rw name           string
        +--rw call-home! {https-call-home}?
           +--rw restconf-client* [name]
              +--rw name                  string
              +--rw endpoints
              |  +--rw endpoint* [name]
              |     +--rw name           string
              |     +--rw (transport)
              |        +--:(https) {https-listen}?
              |           +--rw https
              |              +--rw tcp-client-parameters
              |              |  +--rw remote-address    inet:host
              |              |  +--rw remote-port?      inet:port-number
              |              |  +--rw local-address?    inet:ip-address
              |              |  |       {local-binding-supported}?
              |              |  +--rw local-port?       inet:port-number
              |              |  |       {local-binding-supported}?
              |              |  +--rw keepalives!
              |              |          {keepalives-supported}?
              |              |     +--rw idle-time         uint16
              |              |     +--rw max-probes        uint16
              |              |     +--rw probe-interval    uint16
              |              +--rw tls-server-parameters
              |              |  +--rw server-identity
              |              |  |  +--rw (auth-type)
              |              |  |     +--:(certificate)
              |              |  |     |        {x509-certificate-auth}?
              |              |  |     |  +--rw certificate
              |              |  |     |     +--rw (local-or-keystore)
              |              |  |     |        +--:(local)
              |              |  |     |        |        {local-definiti\
   \ons-supported}?
              |              |  |     |        |  +--rw local-definition
              |              |  |     |        |     +--rw public-key-f\
   \ormat
              |              |  |     |        |     |       identityref
              |              |  |     |        |     +--rw public-key
              |              |  |     |        |     |       binary
              |              |  |     |        |     +--rw private-key-\
   \format?
              |              |  |     |        |     |       identityref
              |              |  |     |        |     +--rw (private-key\
   \-type)
              |              |  |     |        |     |  +--:(private-ke\
   \y)
              |              |  |     |        |     |  |  +--rw privat\
   \e-key?
              |              |  |     |        |     |  |          bina\
   \ry
              |              |  |     |        |     |  +--:(hidden-pri\
   \vate-key)
              |              |  |     |        |     |  |  +--rw hidden\
   \-private-key?
              |              |  |     |        |     |  |          empty
              |              |  |     |        |     |  +--:(encrypted-\
   \private-key)
              |              |  |     |        |     |     +--rw encryp\
   \ted-private-key
              |              |  |     |        |     |        +--rw (ke\
   \y-type)
              |              |  |     |        |     |        |  +--:(s\
   \ymmetric-key-ref)
              |              |  |     |        |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
              |              |  |     |        |     |        |  |     \
   \     {keystore-supported}?
              |              |  |     |        |     |        |  +--:(a\
   \symmetric-key-ref)
              |              |  |     |        |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
              |              |  |     |        |     |        |        \

   \     {keystore-supported}?
              |              |  |     |        |     |        +--rw val\
   \ue?
              |              |  |     |        |     |                b\
   \inary
              |              |  |     |        |     +--rw cert?
              |              |  |     |        |     |       end-entity\
   \-cert-cms
              |              |  |     |        |     +---n certificate-\
   \expiration
              |              |  |     |        |     |  +-- expiration-\
   \date
              |              |  |     |        |     |          yang:da\
   \te-and-time
              |              |  |     |        |     +---x generate-cer\
   \tificate-signing-request
              |              |  |     |        |             {certifica\
   \te-signing-request-generation}?
              |              |  |     |        |        +---w input
              |              |  |     |        |        |  +---w subject
              |              |  |     |        |        |  |       bina\
   \ry
              |              |  |     |        |        |  +---w attrib\
   \utes?
              |              |  |     |        |        |          bina\
   \ry
              |              |  |     |        |        +--ro output
              |              |  |     |        |           +--ro certif\
   \icate-signing-request
              |              |  |     |        |                   ct:c\
   \sr
              |              |  |     |        +--:(keystore)
              |              |  |     |                 {keystore-suppo\
   \rted}?
              |              |  |     |           +--rw keystore-refere\
   \nce
              |              |  |     |              +--rw asymmetric-k\
   \ey?
              |              |  |     |              |       ks:asymmet\
   \ric-key-ref
              |              |  |     |              +--rw certificate?\
   \      leafref
              |              |  |     +--:(raw-private-key)
              |              |  |     |        {raw-public-key-auth}?
              |              |  |     |  +--rw raw-private-key
              |              |  |     |     +--rw (local-or-keystore)
              |              |  |     |        +--:(local)
              |              |  |     |        |        {local-definiti\

   \ons-supported}?
              |              |  |     |        |  +--rw local-definition
              |              |  |     |        |     +--rw public-key-f\
   \ormat
              |              |  |     |        |     |       identityref
              |              |  |     |        |     +--rw public-key
              |              |  |     |        |     |       binary
              |              |  |     |        |     +--rw private-key-\
   \format?
              |              |  |     |        |     |       identityref
              |              |  |     |        |     +--rw (private-key\
   \-type)
              |              |  |     |        |        +--:(private-ke\
   \y)
              |              |  |     |        |        |  +--rw privat\
   \e-key?
              |              |  |     |        |        |          bina\
   \ry
              |              |  |     |        |        +--:(hidden-pri\
   \vate-key)
              |              |  |     |        |        |  +--rw hidden\
   \-private-key?
              |              |  |     |        |        |          empty
              |              |  |     |        |        +--:(encrypted-\
   \private-key)
              |              |  |     |        |           +--rw encryp\
   \ted-private-key
              |              |  |     |        |              +--rw (ke\
   \y-type)
              |              |  |     |        |              |  +--:(s\
   \ymmetric-key-ref)
              |              |  |     |        |              |  |  +--\
   \rw symmetric-key-ref?    leafref
              |              |  |     |        |              |  |     \
   \     {keystore-supported}?
              |              |  |     |        |              |  +--:(a\
   \symmetric-key-ref)
              |              |  |     |        |              |     +--\
   \rw asymmetric-key-ref?   leafref
              |              |  |     |        |              |        \
   \     {keystore-supported}?
              |              |  |     |        |              +--rw val\
   \ue?
              |              |  |     |        |                      b\
   \inary
              |              |  |     |        +--:(keystore)
              |              |  |     |                 {keystore-suppo\
   \rted}?
              |              |  |     |           +--rw keystore-refere\
   \nce?
              |              |  |     |                   ks:asymmetric\
   \-key-ref
              |              |  |     +--:(psk) {psk-auth}?
              |              |  |        +--rw psk
              |              |  |           +--rw (local-or-keystore)
              |              |  |              +--:(local)
              |              |  |              |        {local-definiti\
   \ons-supported}?
              |              |  |              |  +--rw local-definition
              |              |  |              |     +--rw key-format?
              |              |  |              |     |       identityref
              |              |  |              |     +--rw (key-type)
              |              |  |              |     |  +--:(key)
              |              |  |              |     |  |  +--rw key?
              |              |  |              |     |  |          bina\
   \ry
              |              |  |              |     |  +--:(hidden-key)
              |              |  |              |     |  |  +--rw hidden\
   \-key?
              |              |  |              |     |  |          empty
              |              |  |              |     |  +--:(encrypted-\
   \key)
              |              |  |              |     |     +--rw encryp\
   \ted-key
              |              |  |              |     |        +--rw (ke\
   \y-type)
              |              |  |              |     |        |  +--:(s\
   \ymmetric-key-ref)
              |              |  |              |     |        |  |  +--\
   \rw symmetric-key-ref?    leafref
              |              |  |              |     |        |  |     \
   \     {keystore-supported}?
              |              |  |              |     |        |  +--:(a\
   \symmetric-key-ref)
              |              |  |              |     |        |     +--\
   \rw asymmetric-key-ref?   leafref
              |              |  |              |     |        |        \
   \     {keystore-supported}?
              |              |  |              |     |        +--rw val\
   \ue?
              |              |  |              |     |                b\
   \inary
              |              |  |              |     +--rw id?
              |              |  |              |             string
              |              |  |              |             {ks:local-\
   \definitions-supported}?
              |              |  |              +--:(keystore)
              |              |  |                       {keystore-suppo\
   \rted}?
              |              |  |                 +--rw keystore-refere\
   \nce?
              |              |  |                         ks:symmetric-\
   \key-ref
              |              |  +--rw client-authentication!
              |              |  |       {client-auth-config-supported}?
              |              |  |  +--rw ca-certs!
              |              |  |  |       {x509-certificate-auth}?
              |              |  |  |  +--rw (local-or-truststore)
              |              |  |  |     +--:(local)
              |              |  |  |     |        {local-definitions-su\
   \pported}?
              |              |  |  |     |  +--rw local-definition
              |              |  |  |     |     +--rw cert*
              |              |  |  |     |     |       trust-anchor-cer\
   \t-cms
              |              |  |  |     |     +---n certificate-expira\
   \tion
              |              |  |  |     |        +-- expiration-date
              |              |  |  |     |                yang:date-and\
   \-time
              |              |  |  |     +--:(truststore)
              |              |  |  |              {truststore-supported\
   \,certificates}?
              |              |  |  |        +--rw truststore-reference?
              |              |  |  |                ts:certificate-bag-\
   \ref
              |              |  |  +--rw ee-certs!
              |              |  |  |       {x509-certificate-auth}?
              |              |  |  |  +--rw (local-or-truststore)
              |              |  |  |     +--:(local)
              |              |  |  |     |        {local-definitions-su\
   \pported}?
              |              |  |  |     |  +--rw local-definition
              |              |  |  |     |     +--rw cert*
              |              |  |  |     |     |       trust-anchor-cer\
   \t-cms
              |              |  |  |     |     +---n certificate-expira\
   \tion
              |              |  |  |     |        +-- expiration-date
              |              |  |  |     |                yang:date-and\
   \-time
              |              |  |  |     +--:(truststore)
              |              |  |  |              {truststore-supported\
   \,certificates}?
              |              |  |  |        +--rw truststore-reference?
              |              |  |  |                ts:certificate-bag-\
   \ref
              |              |  |  +--rw raw-public-keys!
              |              |  |  |       {raw-public-key-auth}?
              |              |  |  |  +--rw (local-or-truststore)
              |              |  |  |     +--:(local)
              |              |  |  |     |        {local-definitions-su\
   \pported}?
              |              |  |  |     |  +--rw local-definition
              |              |  |  |     |     +--rw public-key* [name]
              |              |  |  |     |        +--rw
                and therefore should only be present at the end of
                the user-ordered 'cert-to-name' list.";
           }
         }
       }
     }

     grouping restconf-server-listen-stack-grouping {
       description
         "A reusable grouping for configuring a RESTCONF server
          'listen' protocol stack for a single connection.";
       choice transport {
         mandatory true;
         description
           "Selects between available transports. This is a
            'choice' statement so as to support additional
            transport options to be augmented in.";
         case http {
           if-feature "http-listen";
           container http {
             description
               "Configures RESTCONF server stack assuming that
                TLS-termination is handled externally.";
             container external-endpoint {
               presence
                 "Specifies configuration for an external endpoint.";
               description
                 "Identifies contact information for the external
                  system that terminates connections before passing
                  them thru to this server (e.g., a network address
                  translator or a load balancer).  These values have
                  no effect on the local operation of this server, but
                  may be used by the application when needing to
                  inform other systems how to contact this server.";
               leaf address {
                 type inet:ip-address;
                 mandatory true;
                 description
                   "The IP address or hostname of the external system
                    that terminates incoming RESTCONF client
                    connections before forwarding them to this
                    server.";
               }
               leaf port {
                 type inet:port-number;
                 default "443";
                 description
                   "The port number that the external system listens
                    on for incoming RESTCONF client connections that
                    are forwarded to this server.  The default HTTPS
                    port (443) is used, as expected for a RESTCONF
                    connection.";
               }
             }
             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 "80";
                   description
                     "The RESTCONF server will listen on the IANA-
                      assigned well-known port value for 'http'
                      (80) if no value is specified.";
                 }
               }
             }
             container http-server-parameters {
               description
                 "A wrapper around the HTTP server parameters
                  to avoid name collisions.";
               uses https:http-server-grouping;
             }
             container restconf-server-parameters {
               description
                 "A wrapper around the RESTCONF server parameters
                  to avoid name collisions.";
               uses rcs:restconf-server-grouping;
             }
           }
         }
         case https {
           if-feature "https-listen";
           container https {
             description
               "Configures RESTCONF server stack assuming that
                TLS-termination is handled internally.";
             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 "443";
                   description
                     "The RESTCONF server will listen on the IANA-
                      assigned well-known port value for 'https'
                      (443) 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;
             }
             container http-server-parameters {
               description
                 "A wrapper around the HTTP server parameters
                  to avoid name collisions.";
               uses https:http-server-grouping;
             }
             container restconf-server-parameters {
               description
                 "A wrapper around the RESTCONF server parameters
                  to avoid name collisions.";
               uses rcs:restconf-server-grouping;
             }
           }
         }
       }
     }

     grouping restconf-server-callhome-stack-grouping {
       description
         "A reusable grouping for configuring a RESTCONF server
          'call-home' protocol stack, for a single connection.";
       choice transport {
         mandatory true;
         description
           "Selects between available transports. This is a
            'choice' statement so as to support additional
            transport options to be augmented in.";
         case https {
           if-feature "https-listen";
           container https {
             description
               "Configures RESTCONF server stack assuming that
                TLS-termination is handled internally.";
             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 "4336";
                   description
                     "The RESTCONF server will attempt to
                      connect to the IANA-assigned well-known
                      port for 'restconf-ch-tls' (4336) 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;
             }
             container http-server-parameters {
               description
                 "A wrapper around the HTTP server parameters
                  to avoid name collisions.";
               uses https:http-server-grouping;
             }
             container restconf-server-parameters {
               description
                 "A wrapper around the RESTCONF server parameters
                  to avoid name collisions.";
               uses rcs:restconf-server-grouping;
             }
           }
         }
       }
     }

     grouping restconf-server-app-grouping {
       description
         "A reusable grouping for configuring a RESTCONF server
          application that supports both 'listen' and 'call-home'
          protocol stacks for a multiplicity of connections.";
       container listen {
         if-feature "http-listen or https-listen";
         presence
           "Enables the RESTCONF server to listen for RESTCONF
            client connections.";
         description "Configures listen behavior";
         list endpoint {
           key "name";
           min-elements 1;
           description
             "List of endpoints to listen for RESTCONF connections.";
           leaf name {
             type string;
             description
               "An arbitrary name for the RESTCONF listen endpoint.";
           }
           uses restconf-server-listen-stack-grouping;
         }
       }
       container call-home {
         if-feature "https-call-home";
         presence
           "Enables the RESTCONF server to initiate the underlying
            transport connection to RESTCONF clients.";
         description "Configures call-home behavior";
         list restconf-client {
           key "name";
           min-elements 1;
           description
             "List of RESTCONF clients the RESTCONF server is to
              maintain simultaneous call-home connections with.";
           leaf name {
             type string;
             description
               "An arbitrary name for the remote RESTCONF client.";
           }
           container endpoints {
             description
               "Container for the list of endpoints.";
             list endpoint {
               key "name";
               min-elements 1;
               ordered-by user;
               description
                 "User-ordered list of endpoints for this RESTCONF
                  client.  Defining more than one enables high-
                  availability.";
               leaf name {
                 type string;
                 description
                   "An arbitrary name
              |              |  |  |     |        |       string
              |              |  |  |     |        +--rw public-key-form\
   \at
              |              |  |  |     |        |       identityref
              |              |  |  |     |        +--rw public-key
              |              |  |  |     |                binary
              |              |  |  |     +--:(truststore)
              |              |  |  |              {truststore-supported\
   \,public-keys}?
              |              |  |  |        +--rw truststore-reference?
              |              |  |  |                ts:public-key-bag-r\
   \ef
              |              |  |  +--rw psks! {psk-auth}?
              |              |  +--rw hello-params
              |              |  |       {tls-server-hello-params-config\
   \}?
              |              |  |  +--rw tls-versions
              |              |  |  |  +--rw tls-version*   identityref
              |              |  |  +--rw cipher-suites
              |              |  |     +--rw cipher-suite*   identityref
              |              |  +--rw keepalives
              |              |          {tls-server-keepalives}?
              |              |     +--rw peer-allowed-to-send?   empty
              |              |     +--rw test-peer-aliveness!
              |              |        +--rw max-wait?       uint16
              |              |        +--rw max-attempts? for this endpoint.";
               }
               uses restconf-server-callhome-stack-grouping;
             }

           }
           container connection-type {
             description
               "Indicates the RESTCONF server's preference for how the
                RESTCONF 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 RESTCONF
                      client. If the connection goes down, immediately
                      start trying to reconnect to the RESTCONF server,
                      using the reconnection strategy.

                      This connection type minimizes any RESTCONF
                      client to RESTCONF 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 RESTCONF client.

                      This connection type increases resource
                      utilization, albeit with increased delay in
                      RESTCONF client to RESTCONF client interactions.

                      The RESTCONF client SHOULD gracefully close
                      the underlying TLS connection upon completing
                      planned activities.  If the underlying TLS
                      connection is not closed gracefully, the
                      RESTCONF server MUST immediately attempt
                      to reestablish the connection.

                      In the case that the previous connection is
                      still active (i.e., the RESTCONF 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
                        the underlying TCP session may remain idle.
                        A TCP 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.";
                   }
                 }
               }
             }
           }
           container reconnect-strategy {
             description
               "The reconnection strategy directs how a RESTCONF server
                reconnects to a RESTCONF client after discovering its
                connection to the client has dropped, even if due to a
                reboot.  The RESTCONF 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.   RESTCONF
                      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 RESTCONF client's endpoints
                  the RESTCONF server should start with when trying
                  to connect to the RESTCONF client.";
             }
             leaf max-attempts {
               type uint8
              |              +--rw http-server-parameters
              |              |  +--rw server-name?             string
              |              |  +--rw client-authentication!
              |              |          {client-auth-config-supported}?
              |              |     +--rw {
                 range "1..max";
               }
               default "3";
               description
                 "Specifies the number times the RESTCONF server tries
                  to connect to a specific endpoint before moving on to
                  the next endpoint in the list (round robin).";
             }
           }
         } // restconf-client
       } // call-home
     } // restconf-server-app-grouping

     // Protocol accessible node, for servers that implement
     // this module.
     container restconf-server {
       uses restconf-server-app-grouping;
       description
         "Top-level container for RESTCONF server configuration.";
     }

   }

   <CODE ENDS>

4.  Security Considerations

4.1.  The "ietf-restconf-client" YANG Module

   The "ietf-restconf-client" YANG module defines data nodes that are
   designed to be accessed via YANG based management protocols, such as
   NETCONF [RFC6241] and RESTCONF [RFC8040].  Both of these protocols
   have mandatory-to-implement secure transport layers (e.g., SSH, TLS)
   with mutual authentication.

   The NETCONF access control model (NACM) [RFC8341] provides the means
   to restrict access for particular users
              |              |        +--rw user* [user-id]
              |              |           +--rw user-id        string
              |              |           +--rw (auth-type)?
              |              |              +--:(basic)
              |              |                 +--rw basic {basic-auth}?
              |              |                    +--rw user-id?
              |              |                    |       string
              |              |                    +--rw password?
              |              |                            ianach:crypt-\
   \hash
              |              +--rw restconf-server-parameters
              |                 +--rw client-identity-mappings
              |                    +--rw cert-to-name* [id]
              |                       +--rw id             uint32
              |                       +--rw fingerprint?
              |                       |       x509c2n:tls-fingerprint
              |                       +--rw map-type       identityref
              |                       +--rw name           string
              +--rw connection-type
              |  +--rw (connection-type)
              |     +--:(persistent-connection)
              |     |  +--rw persistent!
              |     +--:(periodic-connection)
              |        +--rw periodic!
              |           +--rw period?         uint16
              |           +--rw anchor-time?    yang:date-and-time
              |           +--rw idle-timeout?   uint16
              +--rw reconnect-strategy
                 +--rw start-with?     enumeration
                 +--rw max-attempts?   uint8 to a pre-configured subset of
   all available protocol operations and content.

   None of the readable data nodes 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 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.

4.2.  The "ietf-restconf-server" YANG Module

   The "ietf-restconf-server" YANG module defines data nodes that are
   designed to be accessed via YANG based management protocols, such as
   NETCONF [RFC6241] and RESTCONF [RFC8040].  Both of these protocols
   have mandatory-to-implement secure transport layers (e.g., SSH, TLS)
   with mutual authentication.

   The NETCONF access control model (NACM) [RFC8341] provides the means
   to restrict access for particular users to a pre-configured subset of
   all available protocol operations and content.

   None of the readable data nodes 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 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.

5.  IANA Considerations

5.1.  The IETF XML Registry

   This document registers two URIs in the "ns" subregistry of the IETF
   XML Registry [RFC3688].  Following the format in [RFC3688], the
   following registrations are requested:

      URI: urn:ietf:params:xml:ns:yang:ietf-restconf-client
      Registrant Contact: The NETCONF WG of the IETF.
      XML: N/A, the requested URI is an XML namespace.

      URI: urn:ietf:params:xml:ns:yang:ietf-restconf-server
      Registrant Contact: The NETCONF WG of the IETF.
      XML: N/A, the requested URI is an XML namespace.

5.2.  The YANG Module Names Registry

   This document registers two YANG modules in the YANG Module Names
   registry [RFC6020].  Following the format in [RFC6020], the the
   following registrations are requested:

      name:         ietf-restconf-client
      namespace:    urn:ietf:params:xml:ns:yang:ietf-restconf-client
      prefix:       ncc
      reference:    RFC IIII

      name:         ietf-restconf-server
      namespace:    urn:ietf:params:xml:ns:yang:ietf-restconf-server
      prefix:       ncs
      reference:    RFC IIII

6.  References

6.1.  Normative References

   [I-D.ietf-netconf-http-client-server]
              Watsen, K., "YANG Groupings for HTTP Clients and HTTP
              Servers", Work in Progress, Internet-Draft, draft-ietf-
              netconf-http-client-server-03, 20 May 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-http-
              client-server-03>.

   [I-D.ietf-netconf-keystore]
              Watsen, K., "A YANG Data Model for a Keystore", Work in
              Progress, Internet-Draft, draft-ietf-netconf-keystore-17,
              20 May 2020, <https://tools.ietf.org/html/draft-ietf-
              netconf-keystore-17>.

   [I-D.ietf-netconf-tcp-client-server]
              Watsen, K. and M. Scharf, "YANG Groupings for TCP Clients
              and TCP Servers", Work in Progress, Internet-Draft, draft-
              ietf-netconf-tcp-client-server-06, 16 June 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-tcp-
              client-server-06>.

   [I-D.ietf-netconf-tls-client-server]
              Watsen, K. and G. Wu, "YANG Groupings for TLS Clients and
              TLS Servers", Work in Progress, Internet-Draft, draft-
              ietf-netconf-tls-client-server-19, 20 May 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-tls-
              client-server-19>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <https://www.rfc-editor.org/info/rfc6020>.

   [RFC6991]  Schoenwaelder, J., Ed., "Common YANG Data Types",
              RFC 6991, DOI 10.17487/RFC6991, July 2013,
              <https://www.rfc-editor.org/info/rfc6991>.

   [RFC7407]  Bjorklund, M. and J. Schoenwaelder, "A YANG Data Model for
              SNMP Configuration", RFC 7407, DOI 10.17487/RFC7407,
              December 2014, <https://www.rfc-editor.org/info/rfc7407>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8071]  Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
              RFC 8071, DOI 10.17487/RFC8071, February 2017,
              <https://www.rfc-editor.org/info/rfc8071>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

6.2.  Informative References

   [I-D.ietf-netconf-crypto-types]
              Watsen, K., "Common YANG Data Types for Cryptography",
              Work in Progress, Internet-Draft, draft-ietf-netconf-
              crypto-types-15, 20 May 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-crypto-
              types-15>.

   [I-D.ietf-netconf-netconf-client-server]
              Watsen, K., "NETCONF Client and Server Models", Work in
              Progress, Internet-Draft, draft-ietf-netconf-netconf-
              client-server-19, 20 May 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-netconf-
              client-server-19>.

   [I-D.ietf-netconf-restconf-client-server]
              Watsen, K., "RESTCONF Client and Server Models", Work in
              Progress, Internet-Draft, draft-ietf-netconf-restconf-
              client-server-19, 20 May 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-restconf-
              client-server-19>.

   [I-D.ietf-netconf-ssh-client-server]
              Watsen, K. and G. Wu, "YANG Groupings for SSH Clients and
              SSH Servers", Work in Progress, Internet-Draft, draft-
              ietf-netconf-ssh-client-server-19, 20 May 2020,
              <https://tools.ietf.org/html/draft-ietf-netconf-ssh-
              client-server-19>.

   [I-D.ietf-netconf-trust-anchors]
              Watsen, K., "A YANG Data Model for a Truststore", Work in
              Progress, Internet-Draft, draft-ietf-netconf-trust-
              anchors-10, 20 May 2020, <https://tools.ietf.org/html/
              draft-ietf-netconf-trust-anchors-10>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.

   [RFC8340]  Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
              BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
              <https://www.rfc-editor.org/info/rfc8340>.

   [RFC8341]  Bierman, A. and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, RFC 8341,
              DOI 10.17487/RFC8341, March 2018,
              <https://www.rfc-editor.org/info/rfc8341>.

   [RFC8342]  Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
              and R. Wilton, "Network Management Datastore Architecture
              (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
              <https://www.rfc-editor.org/info/rfc8342>.

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/info/rfc8446>.

Appendix A.  Expanded Tree Diagrams
A.1.  Expanded Tree Diagram for 'ietf-restconf-client'

   The following tree diagram [RFC8340] provides an overview of the data
   model for the "ietf-restconf-client" module.

   This tree diagram shows all the nodes defined in this module,
   including those defined by "grouping" statements used by this module.

   Please see Section 2.1 for a tree diagram that illustrates what the
   module looks like without all the "grouping" statements expanded.

   XNSERT_TEXT_FROM_FILE(refs/ietf-restconf-client-tree.txt)

A.2.  Expanded Tree Diagram for 'ietf-restconf-server'

   The following tree diagram [RFC8340] provides an overview of the data
   model for the "ietf-restconf-server" module.

   This tree diagram shows all the nodes defined in this module,
   including those defined by "grouping" statements used by this module.

   Please see Section 3.1 for a tree diagram that illustrates what the
   module looks like without all the "grouping" statements expanded.

   XNSERT_TEXT_FROM_FILE(refs/ietf-restconf-server-tree.txt)

Appendix B.  Change Log

   This section is to be removed before publishing as an RFC.

B.1.  00 to 01

   o

   *  Renamed "keychain" to "keystore".

B.2.  01 to 02

   o

   *  Filled in previously missing 'ietf-restconf-client' module.

   o

   *  Updated the ietf-restconf-server module to accommodate new
      grouping 'ietf-tls-server-grouping'.

B.3.  02 to 03

   o

   *  Refined use of tls-client-grouping to add a must statement
      indicating that the TLS client must specify a client-certificate.

   o

   *  Changed restconf-client??? to be a grouping (not a container).

B.4.  03 to 04

   o

   *  Added RFC 8174 to Requirements Language Section.

   o

   *  Replaced refine statement in ietf-restconf-client to add a
      mandatory true.

   o

   *  Added refine statement in ietf-restconf-server to add a must
      statement.

   o

   *  Now there are containers and groupings, for both the client and
      server models.

   o

   *  Now tree diagrams reference ietf-netmod-yang-tree-diagrams

   o

   *  Updated examples to inline key and certificates (no longer a
      leafref to keystore)

B.5.  04 to 05

   o

   *  Now tree diagrams reference ietf-netmod-yang-tree-diagrams

   o

   *  Updated examples to inline key and certificates (no longer a
      leafref to keystore)

B.6.  05 to 06

   o

   *  Fixed change log missing section issue.

   o

   *  Updated examples to match latest updates to the crypto-types,
      trust-anchors, and keystore drafts.

   o

   *  Reduced line length of the YANG modules to fit within 69 columns.

B.7.  06 to 07

   o

   *  removed "idle-timeout" from "persistent" connection config.

   o

   *  Added "random-selection" for reconnection-strategy's "starts-with"
      enum.

   o

   *  Replaced "connection-type" choice default (persistent) with
      "mandatory true".

   o

   *  Reduced the periodic-connection's "idle-timeout" from 5 to 2
      minutes.

   o

   *  Replaced reconnect-timeout with period/anchor-time combo.

B.8.  07 to 08

   o

   *  Modified examples to be compatible with new crypto-types algs

B.9.  08 to 09

   o

   *  Corrected use of "mandatory true" for "address" leafs.

   o

   *  Updated examples to reflect update to groupings defined in the
      keystore draft.

   o

   *  Updated to use groupings defined in new TCP and HTTP drafts.

   o

   *  Updated copyright date, boilerplate template, affiliation, and
      folding algorithm.

B.10.  09 to 10

   o

   *  Reformatted YANG modules.

B.11.  10 to 11

   o

   *  Adjusted for the top-level "demux container" added to groupings
      imported from other modules.

   o

   *  Added "must" expressions to ensure that keepalives are not
      configured for "periodic" connections.

   o

   *  Updated the boilerplate text in module-level "description"
      statement to match copyeditor convention.

   o

   *  Moved "expanded" tree diagrams to the Appendix.

B.12.  11 to 12

   o

   *  Removed the 'must' statement limiting keepalives in periodic
      connections.

   o

   *  Updated models and examples to reflect removal of the "demux"
      containers in the imported models.

   o

   *  Updated the "periodic-connnection" description statements to
      better describe behavior when connections are not closed
      gracefully.

   o

   *  Updated text to better reference where certain examples come from
      (e.g., which Section in which draft).

   o

   *  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.

   o

   *  Replaced the 'listen', 'initiate', and 'call-home' features with
      boolean expressions.

B.13.  12 to 13

   o

   *  Updated to reflect changes in trust-anchors drafts (e.g., s/trust-
      anchors/truststore/g + s/pinned.//)

   o

   *  In ietf-restconf-server, Added 'http-listen' (not https-listen)
      choice, to support case when server is behind a TLS-terminator.

   o

   *  Refactored server module to be more like other 'server' models.
      If folks like it, will also apply to the client model, as well as
      to both the netconf client/server models.  Now the 'restconf-
      server-grouping' is just the RC-specific bits (i.e., the "demux"
      container minus the container), 'restconf-server-
      [listen|callhome]-stack-grouping' is the protocol stack for a
      single connection, and 'restconf-server-app-grouping' is
      effectively what was before (both listen+callhome for many
      inbound/outbound endpoints).

B.14.  13 to 14

   o

   *  Updated examples to reflect ietf-crypto-types change (e.g.,
      identities --> enumerations)

   o

   *  Adjusting from change in TLS client model (removing the top-level
      'certificate' container).

   o

   *  Added "external-endpoint" to the "http-listen" choice in ietf-
      restconf-server.

B.15.  14 to 15

   o

   *  Added missing "or https-listen" clause in a "must" expression.

   o

   *  Refactored the client module similar to how the server module was
      refactored in -13.  Now the 'restconf-client-grouping' is just the
      RC-specific bits, the 'restconf-client-[initiate|listen]-stack-
      grouping' is the protocol stack for a single connection, and
      'restconf-client-app-grouping' is effectively what was before
      (both listen+callhome for many inbound/outbound endpoints).

B.16.  15 to 16

   o

   *  Added refinement to make "cert-to-name/fingerprint" be mandatory
      false.

   o

   *  Commented out refinement to "tls-server-grouping/client-
      authentication" until a better "must" expression is defined.

   o

   *  Updated restconf-client example to reflect that http-client-
      grouping no longer has a "protocol-version" leaf.

B.17.  16 to 17

   o

   *  Updated examples to include the "*-key-format" nodes.

   o

   *  Updated examples to remove the "required" nodes.

B.18.  17 to 18

   o

   *  Updated examples to reflect new "bag" addition to truststore.

B.19.  18 to 19

   o

   *  Updated examples to remove the 'algorithm' nodes.

   o

   *  Updated examples to reflect the new TLS keepalives structure.

   o

   *  Removed the 'protocol-versions' node from the restconf-server
      examples.

   o

   *  Added a "Note to Reviewers" note to first page.

B.20.  19 to 20

   *  Moved and changed "must" statement so that either TLS *or* HTTP
      auth must be configured.

   *  Expanded "Data Model Overview section(s) [remove "wall" of tree
      diagrams].

   *  Updated the Security Considerations section.

Acknowledgements

   The authors would like to thank for following for lively discussions
   on list and in the halls (ordered by last name): Andy Bierman, Martin
   Bjorklund, Benoit Claise, Mehmet Ersue, Ramkumar Dhanapal, Balazs
   Kovacs, Radek Krejci, David Lamparter, Ladislav Lhotka, Alan Luchuk,
   Tom Petch, Juergen Schoenwaelder, Phil Shafer, Sean Turner, Bert
   Wijnen.

Author's Address

   Kent Watsen
   Watsen Networks

   EMail:

   Email: kent+ietf@watsen.net