TEAS Working Group                                             V. Beeram
Internet-Draft                                          Juniper Networks                                                   T. Saad
Intended status: Standards Track                            T. Saad, Ed.                        Juniper Networks
Expires: August 22, 2019 January 5, 2020                                       R. Gandhi
                                                     Cisco Systems, Inc.
                                                                  X. Liu
                                                                   Jabil
                                                              I. Bryskin
                                                     Huawei Technologies
                                                                 H. Shah
                                                                   Ciena
                                                       February 18,
                                                           July 04, 2019

       A YANG Data Model for Resource Reservation Protocol (RSVP)
                      draft-ietf-teas-yang-rsvp-10
                      draft-ietf-teas-yang-rsvp-11

Abstract

   This document defines a YANG data model for the configuration and
   management of RSVP Protocol.  The model covers the building blocks of
   the RSVP protocol that can be augmented and used by other RSVP
   extension models such as RVSP RSVP extensions to Traffic-Engineering
   (RSVP-TE).  The model covers the configuration, operational state,
   remote procedural procedure calls, and event notifications data.

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 August 22, 2019. January 5, 2020.

Copyright Notice

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

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Model Tree Diagram  . . . . . . . . . . . . . . . . . . .   3
     1.3.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   3
   2.  Model Overview  . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Module(s) Relationship  . . . . . . . . . . . . . . . . .   4
     2.2.  Design Considerations . . . . . . . . . . . . . . . . . .   4
     2.3.  Model Notifications . . . . . . . . . . . . . . . . . . .   5
     2.4.  RSVP Base YANG Model  . . . . . . . . . . . . . . . . . .   5
       2.3.1.
       2.4.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . .   7
       2.3.2.
       2.4.2.  YANG Module . . . . . . . . . . . . . . . . . . . . .  12
     2.4.  11
     2.5.  RSVP Extended YANG Model  . . . . . . . . . . . . . . . .  30
       2.4.1.  31
       2.5.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . .  30
       2.4.2.  31
       2.5.2.  YANG Module . . . . . . . . . . . . . . . . . . . . .  32  33
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  43  44
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  43  45
   5.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  44  46
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  44  46
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .  44  46
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  46  49

1.  Introduction

   YANG [RFC6020] is a data definition language that was introduced to
   define the contents of a conceptual data store that allows networked
   devices to be managed using NETCONF [RFC6241].  YANG is proving
   relevant beyond its initial confines, as bindings to other interfaces
   (e.g.  ReST) and encoding other than XML (e.g.  JSON) are being
   defined.  Furthermore, YANG data models can be used as the basis of
   implementation for other interfaces, such as CLI and programmatic
   APIs.

   This document defines a YANG data model that can be used to configure
   and manage the RSVP protocol [RFC2205].  This model covers RSVP
   protocol building blocks that can be augmented and used by other RSVP
   extension models- such as for signaling RSVP-TE MPLS (or other
   technology specific) Label Switched Paths (LSP)s.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   The terminology for describing YANG data models is found in
   [RFC7950].

1.2.  Model Tree Diagram

   A full tree diagram of the module(s) defined in this document is
   given in subsequent sections as per the syntax defined in [RFC8340].

1.3.  Prefixes in Data Node Names

   In this document, names of data nodes and other data model objects
   are prefixed using the standard prefix associated with the
   corresponding YANG imported modules, as shown in Table 1.

               +-----------+--------------------+-----------+
               | Prefix    | YANG module        | Reference |
               +-----------+--------------------+-----------+
               | yang      | ietf-yang-types    | [RFC6991] |
               | inet      | ietf-inet-types    | [RFC6991] |
               | rt-type   | ietf-routing-types | XX        |
               | key-chain | ietf-key-chain     | XX        |
               +---------+----------------------+-----------+

               Table 1: Prefixes and corresponding YANG modules

2.  Model Overview

   The RSVP base YANG module augments the "control-plane-protocol" list
   in ietf-routing [RFC8349] module with specific RSVP parameters in an
   "rsvp" container.  It also defines an extensiion extension identity "rsvp" of
   base "rt:routing-protocol" to identify the RSVP protocol.

   The augmentation of the RSVP model by other models (e.g.  RSVP-TE for
   MPLS or other technologies) are outside the scope of this document
   and are discussed in separate document(s), e.g.
   [I-D.ietf-teas-yang-rsvp-te].

2.1.  Module(s) Relationship

   This document divides the RSVP model into two modules: base and
   extended RSVP modules.  Some RSVP features are categorized as core to
   the function of the protocol that and are supported by most vendors
   claiming the support for RSVP protocol.  Such features configuration
   and state are grouped in the RSVP base module.

   Other extended RSVP features are categorized as either optional or
   providing knobs ability to better tune the basic functionality of the RSVP
   protocol.  The support for extended RSVP features by all vendors is
   considered optional.  Such features are grouped in a separate RSVP
   extended module.

   The relationship between the base and extended RSVP YANG model and
   the IETF routing YANG model is shown in Figure 1.

                   +--------------+
          Routing  | ietf-routing |
                   +--------------+
                         o
                         |
                    +-----------+
     RSVP module    | ietf-rsvp |
                    +-----------+
                         o
                         |                    o: augment relationship
     RSVP extended       |
       module       +--------------------+
                    | ietf-rsvp-extended |
                    +--------------------+

    Figure 1: Relationship of RSVP and RSVP extended modules with other
                             protocol modules

2.2.  Design Considerations

   The RSVP base model does not aim to be feature complete.  The primary
   intent is to cover a set of standard core features that are commonly
   in use.  For example:

   o  Authentication ([RFC2747])

   o  Refresh Reduction ([RFC2961])

   o  Hellos ([RFC3209])

   o  Graceful Restart ([RFC3473], [RFC5063])
   The extended RSVP YANG model covers non-basic configuration(s) the configuration for
   RSVP feature(s) as well as optional RSVP feature
   features that are not a must for basic RSVP protocol operation.

   The defined data model supports configuration inheritance for
   neighbors, and interfaces.  Data elements defined in the main
   container (e.g. the container that encompasses the list of
   interfaces, or neighbors) are assumed to apply equally to all
   elements of the list, unless overridden explicitly for a certain
   element (e.g. interface).  Vendors are expected to augment the above
   container(s) to provide the list of inheritance command for their
   implementations.

2.3.  Model Notifications

   Notifications data modeling is key in any defined data model.

   [I-D.ietf-netconf-subscribed-notifications] and
   [I-D.ietf-netconf-yang-push] define a subscription and push mechanism
   for YANG datastores.  This mechanism currently allows the user to:

   o  Subscribe notifications on a per client basis

   o  Specify subtree filters or xpath filters so that only interested
      contents will be sent.

   o  Specify either periodic or on-demand notifications.

2.4.  RSVP Base YANG Model

   The RSVP base YANG data model defines the container "rsvp" as the top
   level container in this data model.  The presence of this container
   enables the RSVP protocol functionality.

   Derived

   The derived state data is contained in "read-only" nodes directly
   under a "state" container of the intended object as shown in Figure 2.

   module: ietf-rsvp
      +--rw rsvp!
         +--rw globals
            .
            .
         +--rw interfaces
               .
               +-- ro state <<derived state associated with interfaces>>
            .
            .
         +--rw neighbors
               .
               +-- ro state <<derived state associated with the tunnel>>
            .
            .
         +--rw sessions
               .
               +-- ro state <<derived state associated with the tunnel>>
            .
      rpcs:
         +--x global-rpc
         +--x interfaces-rpc clear-session
         +--x neighbors-rpc
         +--x sessions-rpc
      notifications:
         +--n global-notif
         +--n interfaces-notif
         +--n neighbors-notif
         +--n sessions-notif clear-neighbor

                 Figure 2: RSVP high-level tree model view

   The following subsections provide overview of the parts of the model
   pertaining to configuration and state data.

   Configuration and state data are organized into grouped to those applicable
   globally (node scope), on per
   node (global), per interface, per neighbor, or per session.

   Global Data:

      The global data branch of cover the model covers configuration and state that are is
      applicable the RSVP protocol behavior.

   Interface Data:

      The interface data branch of the data model covers configuration and state elements model relevant
      attributes applicable to one or all RSVP interfaces.  Any data
   configuration applied or
      state at the "interfaces" container level are is equally applicable to
      all interfaces - unless overridden by explicit configuration or
      state under a specific interface.

   Neighbor Data:

      The neighbor data branch of the data model covers cover configuration and state elements relevant to RSVP
      neighbors.  Neighbors can be dynamically discovered using RSVP
      signaling or explicitly configured.

   Session Data:

      The sessions data branch covers configuration of elements and state relevant
      to RSVP sessions.

2.3.1.  This is usually derived state that is result of
      signaling.  This model defines attributes related to IP RSVP
      sessions as defined in [RFC2205].

2.4.1.  Tree Diagram

   Figure 3 shows the YANG tree representation for configuration and
   state data that is augmenting the RSVP basic module:

 module: ietf-rsvp
   augment /rt:routing/rt:control-plane-protocols
             /rt:control-plane-protocol:
     +--rw rsvp!
        +--rw globals
        |  +--rw sessions
        |  |  +--ro session* [local-index]
        |  |     +--ro local-index    -> ../state/local-index session-ip*
        |  |     +--ro state          [destination protocol-id destination-port]
        |  |     +--ro local-index?        uint64 destination-port    inet:port-number
        |  |     +--ro destination-port?   inet:port-number protocol-id         uint8
        |  |     +--ro source?             inet:ip-address
        |  |     +--ro destination? destination         inet:ip-address
        |  |     +--ro session-name?       string
        |  |     +--ro session-state?      enumeration
        |  |     +--ro session-type?       identityref
        |  |     +--ro psbs
        |  |     |  +--ro psb* []
        |  |     |     +--ro source-port?   inet:port-number
        |  |     |     +--ro expires-in?    uint32
        |  |     +--ro rsbs
        |  |        +--ro rsb* []
        |  |           +--ro source-port?         inet:port-number
        |  |           +--ro reservation-style?   identityref
        |  |           +--ro expires-in?          uint32
        |  +--rw statistics
        |  |  +--ro state statistics
        |  |  +--ro messages
        |  |  |  +--ro ack-sent?                       yang:counter64
        |  |  |  +--ro ack-received?                   yang:counter64
        |  |  |  +--ro bundle-sent?                    yang:counter64
        |  |  |  +--ro bundle-received?                yang:counter64
        |  |  |  +--ro hello-sent?                     yang:counter64
        |  |  |  +--ro hello-received?                 yang:counter64
        |  |  |  +--ro integrity-challenge-sent?       yang:counter64
        |  |  |  +--ro integrity-challenge-received?   yang:counter64
        |  |  |  +--ro integrity-response-sent?        yang:counter64
        |  |  |  +--ro integrity-response-received?    yang:counter64
        |  |  |  +--ro notify-sent?                    yang:counter64
        |  |  |  +--ro notify-received?                yang:counter64
        |  |  |  +--ro path-sent?                      yang:counter64
        |  |  |  +--ro path-received?                  yang:counter64
        |  |  |  +--ro path-err-sent?                  yang:counter64
        |  |  |  +--ro path-err-received?              yang:counter64
        |  |  |  +--ro path-tear-sent?                 yang:counter64
        |  |  |  +--ro path-tear-received?             yang:counter64
        |  |  |  +--ro resv-sent?                      yang:counter64
        |  |  |  +--ro resv-received?                  yang:counter64
        |  |  |  +--ro resv-confirm-sent?              yang:counter64
        |  |  |  +--ro resv-confirm-received?          yang:counter64
        |  |  |  +--ro resv-err-sent?                  yang:counter64
        |  |  |  +--ro resv-err-received?              yang:counter64
        |  |  |  +--ro resv-tear-sent?                 yang:counter64
        |  |  |  +--ro resv-tear-received?             yang:counter64
        |  |  |  +--ro summary-refresh-sent?           yang:counter64
        |  |  |  +--ro summary-refresh-received?       yang:counter64
        |  |  |  +--ro unknown-messages-received?      yang:counter64
        |  |  +--ro packets
        |  |  |  +--ro sent?       yang:counter64
        |  |  |  +--ro received?   yang:counter64
        |  |  +--ro errors
        |  |     +--ro authenticate?    yang:counter64
        |  |     +--ro checksum?        yang:counter64
        |  |     +--ro packet-len? packet-length?   yang:counter64
        |  +--rw graceful-restart
        |     +--rw enabled?   boolean
        +--rw interfaces
        |  +--rw refresh-reduction
        |  |  +--rw enabled?   boolean
        |  +--rw hellos
        |  |  +--rw enabled?   boolean
        |  +--rw authentication
        |  |  +--rw enabled?              boolean
        |  |  +--rw authentication-key?   string
        |  |  +--rw crypto-algorithm      identityref
        |  +--rw statistics
        |  |  +--ro state statistics
        |  |  +--ro messages
        |  |  |  +--ro ack-sent?                       yang:counter64
        |  |  |  +--ro ack-received?                   yang:counter64
        |  |  |  +--ro bundle-sent?                    yang:counter64
        |  |  |  +--ro bundle-received?                yang:counter64
        |  |  |  +--ro hello-sent?                     yang:counter64
        |  |  |  +--ro hello-received?                 yang:counter64
        |  |  |  +--ro integrity-challenge-sent?       yang:counter64
        |  |  |  +--ro integrity-challenge-received?   yang:counter64
        |  |  |  +--ro integrity-response-sent?        yang:counter64
        |  |  |  +--ro integrity-response-received?    yang:counter64
        |  |  |  +--ro notify-sent?                    yang:counter64
        |  |  |  +--ro notify-received?                yang:counter64
        |  |  |  +--ro path-sent?                      yang:counter64
        |  |  |  +--ro path-received?                  yang:counter64
        |  |  |  +--ro path-err-sent?                  yang:counter64
        |  |  |  +--ro path-err-received?              yang:counter64
        |  |  |  +--ro path-tear-sent?                 yang:counter64
        |  |  |  +--ro path-tear-received?             yang:counter64
        |  |  |  +--ro resv-sent?                      yang:counter64
        |  |  |  +--ro resv-received?                  yang:counter64
        |  |  |  +--ro resv-confirm-sent?              yang:counter64
        |  |  |  +--ro resv-confirm-received?          yang:counter64
        |  |  |  +--ro resv-err-sent?                  yang:counter64
        |  |  |  +--ro resv-err-received?              yang:counter64
        |  |  |  +--ro resv-tear-sent?                 yang:counter64
        |  |  |  +--ro resv-tear-received?             yang:counter64
        |  |  |  +--ro summary-refresh-sent?           yang:counter64
        |  |  |  +--ro summary-refresh-received?       yang:counter64
        |  |  |  +--ro unknown-messages-received?      yang:counter64
        |  |  +--ro packets
        |  |  |  +--ro sent?       yang:counter64
        |  |  |  +--ro received?   yang:counter64
        |  |  +--ro errors
        |  |     +--ro authenticate?    yang:counter64
        |  |     +--ro checksum?        yang:counter64
        |  |     +--ro packet-len? packet-length?   yang:counter64
        |  +--rw interface* [interface]
        |     +--rw interface            if:interface-ref
        |     +--rw refresh-reduction
        |     |  +--rw enabled?   boolean
        |     +--rw hellos
        |     |  +--rw enabled?   boolean
        |     +--rw authentication
        |     |  +--rw enabled?              boolean
        |     |  +--rw authentication-key?   string
        |     |  +--rw crypto-algorithm      identityref
        |     +--rw statistics
        |     +--ro state statistics
        |        +--ro messages
        |        |  +--ro ack-sent?
        |           |  |                       yang:counter64
        |        |  +--ro ack-received?
        |           |  |                   yang:counter64
        |        |  +--ro bundle-sent?
        |           |  |                    yang:counter64
        |        |  +--ro bundle-received?
        |           |  |                yang:counter64
        |        |  +--ro hello-sent?
        |           |  |                     yang:counter64
        |        |  +--ro hello-received?
        |           |  |                 yang:counter64
        |        |  +--ro integrity-challenge-sent?
        |           |  |       yang:counter64
        |        |  +--ro integrity-challenge-received?
        |           |  |   yang:counter64
        |        |  +--ro integrity-response-sent?
        |           |  |        yang:counter64
        |        |  +--ro integrity-response-received?
        |           |  |    yang:counter64
        |        |  +--ro notify-sent?
        |           |  |       yang:counter64                    yang:counter64
        |        |  +--ro notify-received?
        |           |  |                yang:counter64
        |        |  +--ro path-sent?
        |           |  |                      yang:counter64
        |        |  +--ro path-received?
        |           |  |                  yang:counter64
        |        |  +--ro path-err-sent?
        |           |  |                  yang:counter64
        |        |  +--ro path-err-received?
        |           |  |              yang:counter64
        |        |  +--ro path-tear-sent?
        |           |  |                 yang:counter64
        |        |  +--ro path-tear-received?
        |           |  |             yang:counter64
        |        |  +--ro resv-sent?
        |           |  |                      yang:counter64
        |        |  +--ro resv-received?
        |           |  |                  yang:counter64
        |        |  +--ro resv-confirm-sent?
        |           |  |              yang:counter64
        |        |  +--ro resv-confirm-received?
        |           |  |          yang:counter64
        |        |  +--ro resv-err-sent?
        |           |  |                  yang:counter64
        |        |  +--ro resv-err-received?
        |           |  |              yang:counter64
        |        |  +--ro resv-tear-sent?
        |           |  |                 yang:counter64
        |        |  +--ro resv-tear-received?
        |           |  |             yang:counter64
        |        |  +--ro summary-refresh-sent?
        |           |  |           yang:counter64
        |        |  +--ro summary-refresh-received?
        |           |  |       yang:counter64
        |        |  +--ro unknown-messages-received?
        |           |      yang:counter64
        |        +--ro packets
        |        |  +--ro sent?       yang:counter64
        |        |  +--ro received?   yang:counter64
        |        +--ro errors
        |           +--ro authenticate?    yang:counter64
        |           +--ro checksum?        yang:counter64
        |           +--ro packet-len? packet-length?   yang:counter64
        +--rw neighbors
           +--rw neighbor* [address]
              +--rw address                      inet:ip-address
              +--ro state
                 +--ro address?                     inet:ip-address
                 +--ro
              +--rw epoch?                       uint32
                 +--ro
              +--rw expiry-time?                 uint32
                 +--ro
              +--rw graceful-restart
              |  +--ro  +--rw enabled?                  boolean
              |  +--ro  +--rw local-restart-time?       uint32
              |  +--ro  +--rw local-recovery-time?      uint32
              |  +--ro  +--rw neighbor-restart-time?    uint32
              |  +--ro  +--rw neighbor-recovery-time?   uint32
              |  +--ro  +--rw helper-mode
              |     +--ro     +--rw enabled?                            boolean
              |     +--ro     +--rw max-helper-restart-time?            uint32
              |     +--ro     +--rw max-helper-recovery-time?           uint32
              |     +--ro     +--rw neighbor-restart-time-remaining?    uint32
              |     +--ro     +--rw neighbor-recovery-time-remaining?   uint32
                 +--ro
              +--rw hello-status?                enumeration
                 +--ro
              +--rw interface?                   if:interface-ref
                 +--ro
              +--rw neighbor-state?              enumeration
                 +--ro
              +--rw refresh-reduction-capable?   boolean
                 +--ro
              +--rw restart-count?               yang:counter32
                 +--ro
              +--rw restart-time?                yang:date-and-time

   rpcs:
     +---x clear-session
     |  +---w input
     |     +---w routing-protocol-instance-name    leafref
     |     +---w (filter-type)
     |        +--:(match-all)
     |        |  +---w all                         empty
     |        +--:(match-one)
     |           +---w session-info
     |              +---w (session-type)
     |                 +--:(rsvp-session-ip)
     |                    +---w destination         leafref
     |                    +---w protocol-id         uint8
     |                    +---w destination-port    inet:ip-address
     +---x clear-neighbor
        +---w input
           +---w routing-protocol-instance-name    leafref
           +---w (filter-type)
              +--:(match-all)
              |  +---w all                         empty
              +--:(match-one)
                 +---w neighbor-address            leafref

                     Figure 3: RSVP model tree diagram

2.3.2.

2.4.2.  YANG Module

   The ietf-rsvp module imports from the following modules:

   o  ietf-interfaces defined in [RFC8343]

   o  ietf-yang-types and ietf-inet-types defined in [RFC6991]

   o  ietf-routing defined in [RFC8349]

   o  ietf-key-chain defined in [RFC8177]

  <CODE BEGINS> file "ietf-rsvp@2019-02-18.yang" "ietf-rsvp@2019-07-04.yang"
  module ietf-rsvp {
    yang-version 1.1;

    namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp";

    /* Replace with IANA when assigned */
    prefix "rsvp";
    import ietf-interfaces {
      prefix if;
      reference "RFC8343: A YANG Data Model for Interface Management";
    }

    import ietf-inet-types {
      prefix inet;
      reference "RFC6991: Common YANG Data Types";
    }

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

    import ietf-routing {
      prefix "rt";
      reference
        "RFC8349: A YANG Data Model for Routing Management
         (NMDA Version)";
    }

    import ietf-key-chain {
      prefix "key-chain";
      reference "RFC8177: YANG Data Model for Key Chains";
    }

    organization
      "IETF Traffic Engineering Architecture and Signaling (TEAS)
       Working Group";

    contact
      "WG Web:   <http://tools.ietf.org/wg/teas/>
       WG List:  <mailto:teas@ietf.org>

        WG Chair: Lou Berger
                  <mailto:lberger@labn.net>

        WG Chair: Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

       Editor:   Vishnu Pavan Beeram
                 <mailto:vbeeram@juniper.net>

       Editor:   Tarek Saad
                  <mailto:tsaad@cisco.com>
                 <mailto:tsaad@juniper.net>

       Editor:   Rakesh Gandhi
                 <mailto:rgandhi@cisco.com>

       Editor:   Xufeng Liu
                 <mailto: xufeng.liu.ietf@gmail.com>

       Editor:   Igor Bryskin
                 <mailto:Igor.Bryskin@huawei.com>

       Editor:   Himanshu Shah
                 <mailto:hshah@ciena.com>";

    description
      "This module contains the RSVP YANG data model.
       The model fully conforms to the Network Management Datastore
       Architecture (NMDA).

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

       Redistribution and use in source and binary forms, with or
       without modification, is permitted pursuant to, and subject
       to the license terms contained in, the Simplified BSD License
       set forth in Section 4.c of the IETF Trust's Legal Provisions
       Relating to IETF Documents
       (https://trustee.ietf.org/license-info).
       This version of this YANG module is part of RFC XXXX; see
       the RFC itself for full legal notices.";

    // RFC Ed.: replace XXXX with actual RFC number and remove this
    // note.

    // RFC Ed.: update the date below with the date of RFC publication
    // and remove this note.

    revision "2019-02-18" "2019-07-04" {
      description
        "A YANG Data Model for Resource Reservation Protocol";
      reference
        "RFCXXXX: A YANG Data Model for Resource Reservation Protocol
         (RSVP)";
    }

    identity rsvp {
      base "rt:routing-protocol";
      description "RSVP protocol";
    }

    identity rsvp-session-type {
      description "Base RSVP session type";
    }

    identity rsvp-session-ipv4 {
       base rsvp-session-type;
       description "RSVP IPv4 session type";
     }

     identity rsvp-session-ipv6 rsvp-session-ip {
      base rsvp-session-type;
      description "RSVP IPv4 IP session type";

    }

    identity reservation-style {
      description "Base identity for reservation style";
    }

    identity reservation-wildcard-filter {
      base reservation-style;
      description "Wildcard-Filter (WF) Style";
      reference "RFC2205";
    }

    identity reservation-fixed-filter {
      base reservation-style;
      description "Fixed-Filter (FF) Style";
      reference "RFC2205";
    }

    identity reservation-shared-explicit {
      base reservation-style;
      description "Shared Explicit (SE) Style";
      reference "RFC2205";
    }

    grouping graceful-restart-config {
      description
        "Base configuration parameters relating to RSVP
         Graceful-Restart";
      leaf enabled {
        type boolean;
        description
          "'true' if RSVP Graceful Restart is enabled.
           'false' if RSVP Graceful Restart is disabled.";
      }
    }

    grouping graceful-restart {
      description
        "RSVP graceful restart parameters grouping";
      container graceful-restart {
        description
          "RSVP graceful restart parameters container";
        uses graceful-restart-config;
      }
    }

    grouping refresh-reduction-config {
      description
        "Configuration parameters relating to RSVP
         refresh reduction";

      leaf enabled {
        type boolean;
        description
          "'true' if RSVP Refresh Reduction is enabled.
           'false' if RSVP Refresh Reduction is disabled.";
      }
    }

    grouping refresh-reduction {
      description
        "Top level grouping for RSVP refresh reduction
         parameters";
      container refresh-reduction {
        description
          "Top level container for RSVP refresh reduction
           parameters";
        uses refresh-reduction-config;
      }
    }

    grouping authentication-config {
      description
        "Configuration parameters relating to RSVP
         authentication";
      leaf enabled {
        type boolean;
        description
          "'true' if RSVP Authentication is enabled.
           'false' if RSVP Authentication is disabled.";
      }
      leaf authentication-key {
        type string;
        description
          "An authentication key string";
        reference
          "RFC 2747: RSVP Cryptographic Authentication";
      }
      leaf crypto-algorithm {
       type identityref {
         base key-chain:crypto-algorithm;
       }
       mandatory true;
       description
         "Cryptographic algorithm associated with key.";
      }

    }

    grouping authentication {
      description
        "Top level grouping for RSVP authentication parameters";
      container authentication {
        description
          "Top level container for RSVP authentication
           parameters";
        uses authentication-config;
      }
    }

    grouping hellos-config {
      description
        "Configuration parameters relating to RSVP
        hellos";
      leaf enabled {
        type boolean;
        description
          "'true' if RSVP Hello is enabled.
           'false' if RSVP Hello is disabled.";
      }
    }

    grouping hellos {
      description
        "Top level grouping for RSVP hellos parameters";
      container hellos {
        description
          "Top level container for RSVP hello parameters";
        uses hellos-config;
      }
    }

    grouping signaling-parameters-config {
      description
        "Configuration parameters relating to RSVP
        signaling";
    }

    grouping signaling-parameters {
      description
        "Top level grouping for RSVP signaling  parameters";
      uses signaling-parameters-config;
    }

    grouping session-attributes-state {
      description
        "Top level grouping for RSVP session properties";
      leaf local-index {
         type uint64;
         description
           "The index used to identify the RSVP session
            on the local network element. This index is
            generated by the device and is unique only
            to the local network element.";
       }
       leaf destination-port {
        type inet:port-number;
        description "RSVP destination port";
        reference "RFC2205";
      }
      leaf protocol-id {
        type uint8;
        description "The IP protocol ID.";
        reference "RFC2205, section 3.2";
      }
      leaf source {
        type inet:ip-address;
        description "RSVP source address";
        reference "RFC2205";
      }
      leaf destination {
        type inet:ip-address;
        description "RSVP destination address";
        reference "RFC2205";
      }
      leaf session-name {
        type string;
        description
          "The signaled name of this RSVP session.";
      }
      leaf session-state {
        type enumeration {
          enum "up" {
            description
              "RSVP session is up";
          }
          enum "down" {
            description
              "RSVP session is down";
          }
        }
        description
          "Enumeration of RSVP session states";
      }
      leaf session-type {
        type identityref {
          base rsvp-session-type;
        }
        description "RSVP session type";
      }
      container psbs {
        description "Path State Block container";
        list psb {
          description "List of path state blocks";
          leaf source-port {
            type inet:port-number;
            description "RSVP source port";
            reference "RFC2205";
          }
          leaf expires-in {
            type uint32;
            units seconds;
            description "Time to reservation expiry (in seconds)";
          }
        }
      }
      container rsbs {
        description "Reservation State Block container";
        list rsb {
          description "List of reservation state blocks";
          leaf source-port {
            type inet:port-number;
            description "RSVP source port";
            reference "RFC2205";
          }
          leaf reservation-style {
            type identityref {
              base reservation-style;
            }
            description "RSVP reservation style";
          }
          leaf expires-in {
            type uint32;
            units seconds;
            description "Time to reservation expiry (in seconds)";
          }
        }
      }
    }

    grouping neighbor-attributes {
      description
        "Top level grouping for RSVP neighbor properties";
      leaf address {
        type inet:ip-address;
        description
          "Address of RSVP neighbor";
      }
       container state {
         config false;
         description
           "State information associated with RSVP
            neighbor properties";
         uses neighbor-derived-state;
       }
     }

     grouping packets-state {
       description
         "Packet statistics grouping";
       container packets {
         description
           "Packet statistics container";
      leaf sent epoch {
        type yang:counter64; uint32;
        description
             "Packet sent count";
          "Neighbor epoch.";
      }

      leaf received expiry-time {
        type yang:counter64; uint32;
        units seconds;
        description
             "Packet received count";

         }
       }
          "Neighbor expiry time after which the neighbor state
          is purged if no states associated with it";
      }

     grouping protocol-state {
       description
         "RSVP protocol statistics grouping";

      container messages graceful-restart {
        description
           "RSVP protocol statistics container";
          "Graceful restart information.";

        leaf ack-sent enabled {
          type yang:counter64; boolean;
          description
             "Hello sent count";
            "'true' if graceful restart is enabled for the neighbor.";
        }

        leaf ack-received local-restart-time {
          type yang:counter64; uint32;
          units seconds;
          description
             "Hello received count";
            "Local node restart time";
        }

        leaf bundle-sent local-recovery-time {
          type yang:counter64; uint32;
          units seconds;
          description
             "Bundle sent count";
            "Local node recover time";
        }

        leaf bundle-received neighbor-restart-time {
          type yang:counter64; uint32;
          units seconds;
          description
             "Bundle received count";
            "Neighbor restart time";
        }

        leaf hello-sent neighbor-recovery-time {
          type yang:counter64; uint32;
          units seconds;
          description
             "Hello sent count";
            "Neighbor recover time";
        }

         leaf hello-received

        container helper-mode {
           type yang:counter64;
          description
             "Hello received count";
         }
            "Helper mode information ";

          leaf integrity-challenge-sent enabled {
            type yang:counter64; boolean;
            description
             "Integrity Challenge sent count";
              "'true' if helper mode is enabled.";
          }

          leaf integrity-challenge-received max-helper-restart-time {
            type yang:counter64; uint32;
            units seconds;
            description
             "Integrity Challenge received count";
              "The time the router or switch waits after it
               discovers that a neighboring router has gone down
               before it declares the neighbor down";
          }

          leaf integrity-response-sent max-helper-recovery-time {
            type yang:counter64; uint32;
            units seconds;
            description
             "Integrity Response sent count";
              "The amount of time the router retains the state of its
               RSVP neighbors while they undergo a graceful restart";
          }

          leaf integrity-response-received neighbor-restart-time-remaining {
            type yang:counter64; uint32;
            units seconds;
            description
             "Integrity Response received count";
              "Number of seconds remaining for neighbor to send
               Hello message after restart.";
          }

          leaf notify-sent neighbor-recovery-time-remaining {
            type yang:counter64; uint32;
            units seconds;
            description
             "Notify sent count";
              "Number of seconds remaining for neighbor to
               refresh.";
          }
        } // helper-mode
      } // graceful-restart
      leaf notify-received hello-status {
        type yang:counter64; enumeration {
          enum "enabled" {
            description
             "Notify received count";
              "Enabled";
          }

         leaf path-sent
          enum "disabled" {
           type yang:counter64;
            description
             "Path sent count";
              "Disabled";
          }
          enum "restarting" {
            description
              "Restarting";
          }
        }
        description
          "Hello status";
      }

      leaf path-received interface {
        type yang:counter64; if:interface-ref;
        description
             "Path received count";
          "Interface where RSVP neighbor was detected";
      }

      leaf path-err-sent neighbor-state {
        type enumeration {
          enum "up" {
            description
              "up";
          }
          enum "down" {
            description
              "down";
          }
          enum "hello-disable" {
            description
              "hello-disable";
          }
          enum "restarting" {
            description
              "restarting";
          }
        }
        description
          "Neighbor state";
      }
      leaf refresh-reduction-capable {
        type boolean;
        description
          "enables all RSVP refresh reduction message
           bundling, RSVP message ID, reliable message delivery
           and summary refresh";
        reference
          "RFC 2961 RSVP Refresh Overhead Reduction
           Extensions";
      }

      leaf restart-count {
        type yang:counter32;
        description
          "Number of times this neighbor restart";
      }

      leaf restart-time {
        type yang:date-and-time;
        description
          "Last restart time of the neighbor";
      }
    }

    grouping packets-state {
      description
        "Packet statistics grouping";
      container packets {
        description
          "Packet statistics container";
        leaf sent {
          type yang:counter64;
          description
             "Path error
            "Packet sent count";
        }

        leaf path-err-received received {
          type yang:counter64;
          description
             "Path error
            "Packet received count";
        }
      }
    }

    grouping protocol-state {
      description
        "RSVP protocol statistics grouping";
      container messages {
        description
          "RSVP protocol statistics container";
        leaf path-tear-sent ack-sent {
          type yang:counter64;
          description
             "Path tear
            "Hello sent count";
        }

        leaf path-tear-received ack-received {
          type yang:counter64;
          description
             "Path tear
            "Hello received count";
        }

        leaf resv-sent bundle-sent {
          type yang:counter64;
          description
             "Resv
            "Bundle sent count";
        }

        leaf resv-received bundle-received {
          type yang:counter64;
          description
             "Resv
            "Bundle received count";
        }

        leaf resv-confirm-sent hello-sent {
          type yang:counter64;
          description
             "Confirm
            "Hello sent count";
        }

        leaf resv-confirm-received hello-received {
          type yang:counter64;
          description
             "Confirm
            "Hello received count";
        }

        leaf resv-err-sent integrity-challenge-sent {
          type yang:counter64;
          description
             "Resv error
            "Integrity Challenge sent count";
        }

        leaf resv-err-received integrity-challenge-received {
          type yang:counter64;
          description
             "Resv error
            "Integrity Challenge received count";

        }

        leaf resv-tear-sent integrity-response-sent {
          type yang:counter64;
          description
             "Resv tear
            "Integrity Response sent count";
        }

        leaf resv-tear-received integrity-response-received {
          type yang:counter64;
          description
             "Resv tear
            "Integrity Response received count";
        }

        leaf summary-refresh-sent notify-sent {
          type yang:counter64;
          description
             "Summary refresh
            "Notify sent count";
        }

        leaf summary-refresh-received notify-received {
          type yang:counter64;
          description
             "Summary refresh
            "Notify received count";
        }

        leaf unknown-messages-received path-sent {
          type yang:counter64;
          description
             "Unknown packet received
            "Path sent count";
        }
       }
     }

     grouping errors-state {
       description
         "Error statistics state grouping";
       container errors

        leaf path-received {
          type yang:counter64;
          description
           "Error statistics state container";
            "Path received count";
        }

        leaf authenticate path-err-sent {
          type yang:counter64;
          description
             "The total number of
            "Path error sent count";
        }

        leaf path-err-received {
          type yang:counter64;
          description
            "Path error received count";

        }

        leaf path-tear-sent {
          type yang:counter64;
          description
            "Path tear sent count";
        }

        leaf path-tear-received {
          type yang:counter64;
          description
            "Path tear received count";
        }

        leaf resv-sent {
          type yang:counter64;
          description
            "Resv sent count";
        }

        leaf resv-received {
          type yang:counter64;
          description
            "Resv received count";
        }

        leaf resv-confirm-sent {
          type yang:counter64;
          description
            "Confirm sent count";
        }

        leaf resv-confirm-received {
          type yang:counter64;
          description
            "Confirm received count";
        }

        leaf resv-err-sent {
          type yang:counter64;
          description
            "Resv error sent count";
        }

        leaf resv-err-received {
          type yang:counter64;
          description
            "Resv error received count";

        }

        leaf resv-tear-sent {
          type yang:counter64;
          description
            "Resv tear sent count";
        }

        leaf resv-tear-received {
          type yang:counter64;
          description
            "Resv tear received count";
        }

        leaf summary-refresh-sent {
          type yang:counter64;
          description
            "Summary refresh sent count";
        }

        leaf summary-refresh-received {
          type yang:counter64;
          description
            "Summary refresh received count";
        }

        leaf unknown-messages-received {
          type yang:counter64;
          description
            "Unknown packet received count";
        }
      }
    }

    grouping errors-state {
      description
        "Error statistics state grouping";
      container errors {
        description
          "Error statistics state container";
        leaf authenticate {
          type yang:counter64;
          description
            "The total number of packets received with an
            authentication failure.";
        }

        leaf checksum {
          type yang:counter64;
          description
            "The total number of packets received with an invalid
            checksum value.";
        }

        leaf packet-len packet-length {
          type yang:counter64;
          description
            "The total number of packets received with an invalid
            packet length.";
        }
      }
    }

    grouping statistics-state {
      description "RSVP statistic attributes.";
      container statistics {
        config false;
        description
          "statistics state container";
         container state {
           config false;
           description
             "State information associated with RSVP
              hello parameters";
        uses protocol-state;
        uses packets-state;
        uses errors-state;
      }
    }
     }

    grouping neighbor-derived-state {
      description
        "Derived state at neighbor level.";

       leaf address

    }

    grouping global-attributes {
         type inet:ip-address;
      description
           "Address of
        "Top level grouping for RSVP neighbor";

       }

       leaf epoch global properties";
      container sessions {
         type uint32;
        description
           "Neighbor epoch.";
          "RSVP sessions container";
        list session-ip {
          key "destination protocol-id destination-port";
          config false;
          description
            "List of RSVP sessions";

          uses session-attributes-state;
        }

       leaf expiry-time
      }
      uses statistics-state;
    }

    grouping intf-attributes {
         type uint32;
         units seconds;
      description
           "Neighbor expiry time after which the neighbor state
           is purged if no states associated with it";
        "Top level grouping for RSVP interface properties";
      uses signaling-parameters;
      uses refresh-reduction;
      uses hellos;
      uses authentication;
      uses statistics-state;
    }

       container graceful-restart

    augment "/rt:routing/rt:control-plane-protocols/"
      + "rt:control-plane-protocol" {
         description
           "Graceful restart information.";

         leaf enabled
      when "rt:type = 'rsvp:rsvp'" {
           type boolean;
      description
             "'true' if graceful restart
       "This augment is enabled for the neighbor.";
         }

         leaf local-restart-time { only valid when routing protocol
        instance type uint32;
           units seconds;
           description
             "Local node restart time"; is RSVP.";
      }

         leaf local-recovery-time {
           type uint32;
           units seconds;
      description
             "Local node recover time";
         }

         leaf neighbor-restart-time
        "RSVP protocol augmentation";
      container rsvp {
           type uint32;
           units seconds;
        presence "Enable RSVP feature";
        description
             "Neighbor restart time";
         }

         leaf neighbor-recovery-time "RSVP feature container";
        container globals {
           type uint32;
           units seconds;
          description
             "Neighbor recover time"; "RSVP global properties.";
          uses global-attributes;
          uses graceful-restart;
        }

        container helper-mode interfaces {
          description
             "Helper mode information ";

           leaf enabled
            "RSVP interfaces container";
          uses intf-attributes;

          list interface {
             type boolean;
            key "interface";
            description
               "'true' if helper mode is enabled.";
           }
              "RSVP interfaces.";
            leaf max-helper-restart-time interface {
              type uint32;
             units seconds; if:interface-ref;
              description
               "The time the router or switch waits after it
                discovers that a neighboring router has gone down
                before it declares the neighbor down";
                "RSVP interface.";
            }

           leaf max-helper-recovery-time {
             type uint32;
             units seconds;
             description
               "The amount of time the router retains the state of its
                RSVP neighbors while they undergo a graceful restart";
            uses intf-attributes;
          }

           leaf neighbor-restart-time-remaining
        }
        container neighbors {
             type uint32;
             units seconds;
          description
               "Number of seconds remaining for "RSVP neighbors container";
          list neighbor to send
                Hello message after restart.";
           }

           leaf neighbor-recovery-time-remaining {
             type uint32;
             units seconds;
            key "address";
            description
               "Number "List of seconds remaining for neighbor to
                refresh."; RSVP neighbors";
            uses neighbor-attributes;
          }
        } // helper-mode
      } // graceful-restart

       leaf hello-status {
         type enumeration {
           enum "enabled" {
             description
               "Enabled";
    }
           enum "disabled"

    grouping session-ref {
      description
               "Disabled";
           }
           enum "restarting" "Session reference information";
      leaf destination {
             description
               "Restarting";
           }
        type leafref {
          path "/rt:routing/rt:control-plane-protocols" +
               "/rt:control-plane-protocol/rsvp:rsvp/rsvp:globals" +
               "/rsvp:sessions/rsvp:session-ip/destination";
        }
        mandatory true;
        description
           "Hello status"; "RSVP session";
      }
      leaf interface protocol-id {
        type if:interface-ref; uint8;
        mandatory true;
        description
           "Interface where "The RSVP neighbor was detected"; session protocol ID";
      }
      leaf neighbor-state destination-port {
        type enumeration {
           enum "up" { inet:ip-address;
        mandatory true;
        description
               "up"; "The RSVP session destination port";
      }
           enum "down" {
             description
               "down";
    }
           enum "hello-disable"

    rpc clear-session {
      description
               "hello-disable";
           }
           enum "restarting" "Clears RSVP sessions RPC";
      input {
             description
               "restarting";
           }
         }
         description
           "Neighbor state";
       }
        leaf refresh-reduction-capable routing-protocol-instance-name {
          type boolean;
         description
           "enables all RSVP refresh reduction message
            bundling, RSVP message ID, reliable message delivery
            and summary refresh";
         reference
           "RFC 2961 RSVP Refresh Overhead Reduction
            Extensions";
       }

       leaf restart-count leafref {
         type yang:counter32;
         description
           "Number of times this neighbor restart";
            path "/rt:routing/rt:control-plane-protocols/"
               + "rt:control-plane-protocol/rt:name";
          }

       leaf restart-time {
         type yang:date-and-time;
          mandatory "true";
          description
           "Last restart time
            "Name of the neighbor";
       }
     }

     grouping global-attributes {
       description
         "Top level grouping for RSVP global properties";
       container sessions {
         description
           "RSVP sessions container";
         list protocol instance whose session
             is being cleared.

             If the corresponding RSVP instance doesn't exist,
             then the operation will fail with an error-tag of
             'data-missing' and an error-app-tag of
             'routing-protocol-instance-not-found'.";
        }
        choice filter-type {
           key "local-index";
           config false;
          mandatory true;
          description
             "List of RSVP sessions"; "Filter choice";
          case match-all {
            leaf local-index all {
              type leafref {
               path "../state/local-index";
             } empty;
              mandatory true;
              description
               "Reference to the local index for the "Match all RSVP
               session"; sessions";
            }
          }
          case match-one {
            container state session-info {
             config false;
              description
               "State information associated with RSVP
                "Specifies the specific session parameters"; to invoke operation on";
              choice session-type {
                mandatory true;
                description "RSVP session type";
                case rsvp-session-ip {
                  uses session-attributes-state; session-ref;
                }
              }
            }
       uses statistics-state;
          }

     grouping intf-attributes
        }
      }
    }

    rpc clear-neighbor {
      description
         "Top level grouping for
        "RPC to clear the RSVP interface properties";
       uses signaling-parameters;
       uses refresh-reduction;
       uses hellos;
       uses authentication;
       uses statistics-state;
     }

     augment "/rt:routing/rt:control-plane-protocols/"
       + "rt:control-plane-protocol" Hello session to a neighbor";
      input {
       when "rt:type = 'rsvp:rsvp'"
        leaf routing-protocol-instance-name {
       description
        "This augment is only valid when routing protocol
         instance
          type is RSVP."; leafref {
            path "/rt:routing/rt:control-plane-protocols/"
               + "rt:control-plane-protocol/rt:name";
          }
          mandatory "true";
          description
         "RSVP
            "Name of the RSVP protocol augmentation";
       container rsvp {
         presence "Enable instance whose session
             is being cleared.

             If the corresponding RSVP feature";
         description "RSVP feature container";
         container globals {
           description "RSVP global properties.";
           uses global-attributes;
           uses graceful-restart; instance doesn't exist,
             then the operation will fail with an error-tag of
             'data-missing' and an error-app-tag of
             'routing-protocol-instance-not-found'.";
        }

         container interfaces
        choice filter-type {
          mandatory true;
          description
             "RSVP interfaces container";
           uses intf-attributes;

           list interface "Filter choice";
          case match-all {
             key "interface";
             description
               "RSVP interfaces.";
            leaf interface all {
              type if:interface-ref; empty;
              mandatory true;
              description
                 "RSVP interface.";
             }
             uses intf-attributes; "Match all RSVP neighbor sessions";
            }
          }

         container neighbors
          case match-one {
           description "RSVP neighbors container";
           list neighbor
            leaf neighbor-address {
             key "address";
              type leafref {
                path "/rt:routing/rt:control-plane-protocols" +
                     "/rt:control-plane-protocol/rsvp:rsvp" +
                     "/rsvp:neighbors/rsvp:neighbor/address";
              }
              mandatory true;
              description "List of "Match specific RSVP neighbors";
             uses neighbor-attributes; neighbor session";
            }
          }
        }
      }
    }
  }
  <CODE ENDS>

2.4.

2.5.  RSVP Extended YANG Model

   The RSVP extended YANG model covers non-core RSVP feature(s).  It
   also covers feature(s) that are not necessarily supported by all
   vendors, and hence, can be guarded with "if-feature" checks.

2.4.1.

2.5.1.  Tree Diagram

   Figure 4 shows the YANG tree representation for configuration and
   state data that is augmenting the RSVP extended module:

   module: ietf-rsvp-extended
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:globals
               /rsvp:graceful-restart:
       +--rw restart-time?    uint32
       +--rw recovery-time?   uint32
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:globals
               /rsvp:statistics/rsvp:state/rsvp:packets:
               /rsvp:statistics/rsvp:packets:
       +--ro discontinuity-time?   yang:date-and-time
       +--ro out-dropped?          yang:counter64
       +--ro in-dropped?           yang:counter64
       +--ro out-error? out-errors?           yang:counter64
       +--ro in-error? in-errors?            yang:counter64
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:globals
               /rsvp:statistics/rsvp:state/rsvp:messages:
               /rsvp:statistics/rsvp:messages:
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:globals
               /rsvp:statistics/rsvp:state/rsvp:errors:
               /rsvp:statistics/rsvp:errors:
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces:
       +--rw refresh-interval?        uint32
       +--rw refresh-misses?          uint32
       +--rw checksum?                boolean
       +--rw patherr-state-removal?   empty
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:refresh-reduction:
       +--rw bundle-message-max-size?    uint32
       +--rw reliable-ack-hold-time?     uint32
       +--rw reliable-ack-max-size?      uint32
       +--rw reliable-retransmit-time?   uint32
       +--rw reliable-srefresh?          empty
       +--rw summary-max-size?           uint32
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:hellos:
       +--rw interface-based?   empty
       +--rw hello-interval?    uint32
       +--rw hello-misses?      uint32
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:authentication:
       +--rw lifetime?      uint32
       +--rw window-size?   uint32
       +--rw challenge?     empty
       +--rw retransmits?   uint32
       +--rw key-chain?     key-chain:key-chain-ref
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:interface:
       +--rw refresh-interval?        uint32
       +--rw refresh-misses?          uint32
       +--rw checksum?                boolean
       +--rw patherr-state-removal?   empty

     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:interface/rsvp:refresh-reduction:
       +--rw bundle-message-max-size?    uint32
       +--rw reliable-ack-hold-time?     uint32
       +--rw reliable-ack-max-size?      uint32
       +--rw reliable-retransmit-time?   uint32
       +--rw reliable-srefresh?          empty
       +--rw summary-max-size?           uint32
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:interface/rsvp:hellos:
       +--rw interface-based?   empty
       +--rw hello-interval?    uint32
       +--rw hello-misses?      uint32
     augment /rt:routing/rt:control-plane-protocols
               /rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces
               /rsvp:interface/rsvp:authentication:
       +--rw lifetime?      uint32
       +--rw window-size?   uint32
       +--rw challenge?     empty
       +--rw retransmits?   uint32
       +--rw key-chain?     key-chain:key-chain-ref

                Figure 4: RSVP extended model tree diagram

2.4.2.

2.5.2.  YANG Module

   The ietf-rsvp-extended module imports from the following modules:

   o  ietf-rsvp defined in this document

   o  ietf-routing defined in [RFC8349]

   o  ietf-yang-types and ietf-inet-types defined in [RFC6991]

   o  ietf-key-chain defined in [RFC8177]

   Figure 5 shows the RSVP extended YANG module:

   <CODE BEGINS> file "ietf-rsvp-extended@2019-02-18.yang" "ietf-rsvp-extended@2019-07-04.yang"
   module ietf-rsvp-extended {
     yang-version 1.1;

     namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-extended";

     prefix "rsvp-ext";
     import ietf-rsvp {
       prefix "rsvp";
       reference
         "RFCXXXX:  A YANG Data Model for Resource Reservation Protocol
          (RSVP)";
     }

     import ietf-routing {
       prefix "rt";
       reference
         "RFC8349: A YANG Data Model for Routing Management
          (NMDA Version)";
     }

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

     import ietf-key-chain {
       prefix "key-chain";
       reference "RFC8177: YANG Data Model for Key Chains";
     }

     organization
       "IETF Traffic Engineering Architecture and Signaling (TEAS)
        Working Group";

     contact
       "WG Web:   <http://tools.ietf.org/wg/teas/>
        WG List:  <mailto:teas@ietf.org>

        WG Chair: Lou Berger
                  <mailto:lberger@labn.net>

        WG Chair: Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

        Editor:   Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

        Editor:   Tarek Saad
                  <mailto:tsaad@cisco.com>
                  <mailto:tsaad@juniper.net>

        Editor:   Rakesh Gandhi
                  <mailto:rgandhi@cisco.com>

        Editor:   Himanshu Shah
                  <mailto:hshah@ciena.com>

        Editor:   Xufeng Liu
                  <mailto:Xufeng_Liu@jabil.com>

        Editor:   Xia Chen
                  <mailto:jescia.chenxia@huawei.com>

        Editor:   Raqib Jones
                  <mailto:raqib@Brocade.com>

        Editor:   Bin Wen
                  <mailto:Bin_Wen@cable.comcast.com>";

     description
       "This module contains the Extended RSVP YANG data model.
        The model fully conforms to the Network Management Datastore
        Architecture (NMDA).

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

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject
        to the license terms contained in, the Simplified BSD License
        set forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (https://trustee.ietf.org/license-info).
        This version of this YANG module is part of RFC XXXX; see
        the RFC itself for full legal notices.";

     // RFC Ed.: replace XXXX with actual RFC number and remove this
     // note.

     // RFC Ed.: update the date below with the date of RFC publication
     // and remove this note.

     revision "2019-02-18" "2019-07-04" {
       description
         "A YANG Data Model for Extended Resource Reservation
          Protocol";
       reference
         "RFCXXXX: A YANG Data Model for Extended Resource Reservation Protocol
          (RSVP)";
     }

     /* RSVP features */
     feature authentication {
       description
         "Indicates support for RSVP authentication";
     }

     feature error-statistics {
       description
         "Indicates support for error statistics";
     }

     feature global-statistics {
       description
         "Indicates support for global statistics";
     }

     feature graceful-restart {
       description
         "Indicates support for RSVP graceful restart";
     }

     feature hellos {
       description
         "Indicates support for RSVP hellos (RFC3209).";
     }

     feature notify {
       description
         "Indicates support for RSVP notify message (RFC3473).";
     }

     feature refresh-reduction {
       description
         "Indicates support for RSVP refresh reduction (RFC2961).";
     }

     feature refresh-reduction-extended {
       description
         "Indicates support for RSVP refresh reduction (RFC2961).";
     }

     feature per-interface-statistics {
       description
         "Indicates support for per interface statistics";
     }

     grouping graceful-restart-extended-config {
       description
         "Configuration parameters relating to RSVP
          Graceful-Restart";
       leaf restart-time {
         type uint32;
         units seconds;
         description
           "Graceful restart time (seconds).";
         reference
           "RFC 5495: Description of the Resource
            Reservation Protocol - Traffic-Engineered
            (RSVP-TE) Graceful Restart Procedures";
       }
       leaf recovery-time {
         type uint32;
         units seconds;
         description
           "RSVP state recovery time";
       }
     }

     grouping authentication-extended-config {
       description
         "Configuration parameters relating to RSVP
         authentication";
       leaf lifetime {
         type uint32 {
           range "30..86400";
         }
         units seconds;
         description
           "Life time for each security association";
         reference
           "RFC 2747: RSVP Cryptographic
           Authentication";
       }
       leaf window-size {
         type uint32 {
           range "1..64";
         }
         description
           "Window-size to limit number of out-of-order
            messages.";
         reference
           "RFC 2747: RSVP Cryptographic
            Authentication";
       }
       leaf challenge {
         type empty;
         description
           "Enable challenge messages.";
         reference
           "RFC 2747: RSVP Cryptographic
            Authentication";
       }
       leaf retransmits {
         type uint32 {
           range "1..10000";
         }
         description
           "Number of retransmits when messages are
            dropped.";
         reference
           "RFC 2747: RSVP Cryptographic
            Authentication";
       }
       leaf key-chain {
         type key-chain:key-chain-ref;
         description
           "Key chain name to authenticate RSVP
            signaling messages.";
         reference
           "RFC 2747: RSVP Cryptographic
            Authentication";
       }
     }

     grouping hellos-extended-config {
       description
         "Configuration parameters relating to RSVP
          hellos";
       leaf interface-based {
         type empty;
         description
           "Enable interface-based Hello adjacency if present.";
       }
       leaf hello-interval {
         type uint32;
         units milliseconds;
         description
           "Configure interval between successive Hello
            messages in milliseconds.";
         reference
           "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels.
            RFC 5495: Description of the Resource
            Reservation Protocol - Traffic-Engineered
            (RSVP-TE) Graceful Restart Procedures";
       }
       leaf hello-misses {
         type uint32 {
           range "1..10";
         }
         description
           "Configure max number of consecutive missed
            Hello messages.";

         reference
           "RFC 3209: RSVP-TE: Extensions to RSVP for
            LSP Tunnels RFC 5495: Description of the
            Resource Reservation Protocol - Traffic-
            Engineered (RSVP-TE) Graceful Restart
            Procedures";
       }
     }

     grouping signaling-parameters-extended-config {
       description
         "Configuration parameters relating to RSVP
          signaling";
       leaf refresh-interval {
         type uint32;
         description
           "Set interval between successive refreshes";
       }
       leaf refresh-misses {
         type uint32;
         description
           "Set max number of consecutive missed
           messages for state expiry";
       }
       leaf checksum {
         type boolean;
         description
           "Enable RSVP message checksum computation";
       }
       leaf patherr-state-removal {
         type empty;
         description
           "State-Removal flag in Path Error message
           if present.";
       }
     }

     grouping refresh-reduction-extended-config {
       description
         "Configuration parameters relating to RSVP
         refresh reduction";

       leaf bundle-message-max-size {
         type uint32 {
           range "512..65000";
         }
         description
           "Configure maximum size (bytes) of a
           single RSVP Bundle message.";
       }
       leaf reliable-ack-hold-time {
         type uint32;
         units milliseconds;
         description
           "Configure hold time in milliseconds for
           sending RSVP ACK message(s).";
       }
       leaf reliable-ack-max-size {
         type uint32;
         description
           "Configure max size of a single RSVP ACK
           message.";
       }
       leaf reliable-retransmit-time {
         type uint32;
         units milliseconds;
         description
           "Configure min delay in milliseconds to
           wait for an ACK before a retransmit.";
       }
       leaf reliable-srefresh {
         type empty;
         description
           "Configure use of reliable messaging for
           summary refresh if present.";
       }
       leaf summary-max-size {
         type uint32 {
           range "20..65000";
         }
         description
           "Configure max size (bytes) of a single
           RSVP summary refresh message.";
       }
     }

     grouping packets-extended-state {
       description
         "Packet statistics.";
       leaf discontinuity-time {
         type yang:date-and-time;
         description
           "The time on the most recent occasion at which any one
           or more of the statistic counters suffered a
           discontinuity. If no such discontinuities have occurred
           since the last re-initialization of the local
           management subsystem, then this node contains the time
           the local management subsystem re-initialized itself.";
       }
       leaf out-dropped {
         type yang:counter64;
         description
           "Out packet drop count";
       }

       leaf in-dropped {
         type yang:counter64;
         description
           "In packet drop count";
       }

       leaf out-error out-errors {
         type yang:counter64;
         description
           "Out packet error errors count";
       }

       leaf in-error in-errors {
         type yang:counter64;
         description
           "In packet rx error errors count";
       }
     }

     grouping protocol-extended-state {
       description "RSVP protocol statistics.";
     }

     grouping errors-extended-state {
       description
         "Error statistics.";
     }

     grouping extended-state {
       description "RSVP statistic attributes.";
       uses packets-extended-state;
       uses protocol-extended-state;
       uses errors-extended-state;
     }

     /**
      * RSVP extensions augmentations
      */

     /* RSVP globals graceful restart*/
     augment "/rt:routing/rt:control-plane-protocols/" +
             "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
             "rsvp:graceful-restart" {
       description
         "RSVP globals configuration extensions";
       uses graceful-restart-extended-config;
     }

     /* RSVP statistics augmentation */
     augment "/rt:routing/rt:control-plane-protocols/" +
             "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
             "rsvp:statistics/rsvp:state/rsvp:packets"
             "rsvp:statistics/rsvp:packets" {
       description
         "RSVP packet stats extensions";
       uses packets-extended-state;
     }
     augment "/rt:routing/rt:control-plane-protocols/" +
             "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
             "rsvp:statistics/rsvp:state/rsvp:messages"
             "rsvp:statistics/rsvp:messages" {
       description
         "RSVP protocol message stats extensions";
       uses protocol-extended-state;
     }
     augment "/rt:routing/rt:control-plane-protocols/" +
             "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
             "rsvp:statistics/rsvp:state/rsvp:errors"
             "rsvp:statistics/rsvp:errors" {
       description
         "RSVP errors stats extensions";
       uses errors-extended-state;
     }

     /**
      * RSVP all interfaces extensions
      */

     /* RSVP interface signaling extensions */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces" {
       description
         "RSVP signaling all interfaces configuration extensions";
       uses signaling-parameters-extended-config;
     }

     /* RSVP refresh reduction extension */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
         + "rsvp:refresh-reduction" {

       description
         "RSVP refresh-reduction all interface configuration
          extensions";
       uses refresh-reduction-extended-config;
     }

     /* RSVP hellos extension */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
         + "rsvp:hellos" {
       description
         "RSVP hello all interfaces configuration extensions";
       uses hellos-extended-config;
     }

     /* RSVP authentication extension */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
         + "rsvp:authentication" {
       description
         "RSVP authentication all interfaces configuration extensions";
       uses authentication-extended-config;
     }

     /**
      * RSVP interface extensions
      */

     /* RSVP interface signaling extensions */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
         "rsvp:interface" {
       description
         "RSVP signaling interface configuration extensions";
       uses signaling-parameters-extended-config;
     }

     /* RSVP refresh reduction extension */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
         "rsvp:interface/rsvp:refresh-reduction" {
       description
         "RSVP refresh-reduction interface configuration extensions";
       uses refresh-reduction-extended-config;
     }

     /* RSVP hellos extension */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
         "rsvp:interface/rsvp:hellos" {
       description
         "RSVP hello interface configuration extensions";
       uses hellos-extended-config;
     }

     /* RSVP authentication extension */
     augment "/rt:routing/rt:control-plane-protocols/"
         + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
         "rsvp:interface/rsvp:authentication" {
       description
         "RSVP authentication interface configuration extensions";
       uses authentication-extended-config;
     }
   }
   <CODE ENDS>

                    Figure 5: RSVP extended YANG module

3.  IANA Considerations

   This document registers the following URIs in the IETF XML registry
   [RFC3688].  Following the format in [RFC3688], the following
   registration is requested to be made.

      URI: urn:ietf:params:xml:ns:yang:ietf-rsvp
      XML: N/A, the requested URI is an XML namespace.

      URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-extended
      XML: N/A, the requested URI is an XML namespace.

   This document registers two YANG modules in the YANG Module Names
   registry [RFC6020].

      name:       ietf-rsvp
      namespace:  urn:ietf:params:xml:ns:yang:ietf-rsvp
      prefix:     ietf-rsvp
      reference:  RFCXXXX

      name:       ietf-rsvp-extended
      namespace:  urn:ietf:params:xml:ns:yang:ietf-rsvp-extended
      prefix:     ietf-rsvp-extendeed
      reference:  RFCXXXX

4.  Security Considerations

   The YANG module defined specified in this memo document defines a schema for data
   that is designed to be accessed via
   the network management protocols such
   as NETCONF protocol [RFC6241]. [RFC6241] or RESTCONF [RFC8040].  The lowest NETCONF layer
   is the secure transport layer layer, and the mandatory-to-implement secure
   transport is SSH Secure Shell (SSH) [RFC6242].  The NETCONF access control model lowest RESTCONF layer
   is HTTPS, and the mandatory-to-implement secure transport is TLS
   [RFC8446].

   The Network Configuration Access Control Model (NACM) [RFC8341]
   provides the means to restrict access for particular NETCONF or
   RESTCONF users to a pre-configured preconfigured subset of all available NETCONF or
   RESTCONF protocol operations and content.

   There are a number of data nodes defined in the YANG module which are
   writable/creatable/deletable (i.e., config true, which is the
   default).  These data nodes may be considered sensitive or vulnerable
   in some network environments.  Write operations (e.g., <edit-config>)
   to these data nodes without proper protection can have a negative
   effect on network operations.

   /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
   rsvp:

      The presence of this container enables the RSVP protocol
      functionality on a device.  It alsocontrols the configuration
      settings on data nodes pertaining to RSVP sessions, interfaces and
      neighbors.  All of which are considered sensitive and if access to
      either of these is compromised, it can result in temporary network
      outages or be employed to mount DoS attacks.

   For RSVP authentication, the configuration supported is via the
   specification of key-chains [RFC8177] or the direct specification of
   key and authentication algorithm, and hence security considerations
   of [RFC8177] are inherited.  This includes the considerations with
   respect to the local storage and handling of authentication keys.

   Some of the RPC operations defined in this YANG module may be
   considered sensitive or vulnerable in some network environments.  It
   is thus important to control access to these operations.  The RSVP
   YANG module support the "clear-session" and "clear-neighbor" RPCs.
   If access to either of these is compromised, they can result in
   temporary network outages be employed to mount DoS attacks.

   The security considerations spelled out in the YANG 1.1 specification
   [RFC7950] apply for this document as well.

5.  Acknowledgement

   The authors would like to thank Lou Berger for reviewing and
   providing valuable feedback on this document.

6.  Contributors

      Himanshu Shah
      Ciena

      Email: hshah@ciena.com

      Xia Chen
      Huawei Technologies

      Email: jescia.chenxia@huawei.com

      Raqib Jones
      Brocade

      Email: raqib@Brocade.com

      Bin Wen
      Comcast

      Email: Bin_Wen@cable.comcast.com

7.  Normative References

   [I-D.ietf-netconf-subscribed-notifications]
              Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and
              A. Tripathy, "Subscription to YANG Event Notifications",
              draft-ietf-netconf-subscribed-notifications-26 (work in
              progress), May 2019.

   [I-D.ietf-netconf-yang-push]
              Clemm, A. and E. Voit, "Subscription to YANG Datastores",
              draft-ietf-netconf-yang-push-25 (work in progress), May
              2019.

   [I-D.ietf-teas-yang-rsvp-te]
              Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I.,
              and H. Shah, "A YANG Data Model for RSVP-TE", draft-ietf-
              teas-yang-rsvp-te-04 RSVP-TE Protocol",
              draft-ietf-teas-yang-rsvp-te-06 (work in progress), October 2018. April
              2019.

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

   [RFC2205]  Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
              Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
              Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
              September 1997, <https://www.rfc-editor.org/info/rfc2205>.

   [RFC2747]  Baker, F., Lindell, B., and M. Talwar, "RSVP Cryptographic
              Authentication", RFC 2747, DOI 10.17487/RFC2747, January
              2000, <https://www.rfc-editor.org/info/rfc2747>.

   [RFC2961]  Berger, L., Gan, D., Swallow, G., Pan, P., Tommasi, F.,
              and S. Molendini, "RSVP Refresh Overhead Reduction
              Extensions", RFC 2961, DOI 10.17487/RFC2961, April 2001,
              <https://www.rfc-editor.org/info/rfc2961>.

   [RFC3209]  Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
              and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
              Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
              <https://www.rfc-editor.org/info/rfc3209>.

   [RFC3473]  Berger, L., Ed., "Generalized Multi-Protocol Label
              Switching (GMPLS) Signaling Resource ReserVation Protocol-
              Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
              DOI 10.17487/RFC3473, January 2003,
              <https://www.rfc-editor.org/info/rfc3473>.

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

   [RFC5063]  Satyanarayana, A., Ed. and R. Rahman, Ed., "Extensions to
              GMPLS Resource Reservation Protocol (RSVP) Graceful
              Restart", RFC 5063, DOI 10.17487/RFC5063, October 2007,
              <https://www.rfc-editor.org/info/rfc5063>.

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

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

   [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
              Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
              <https://www.rfc-editor.org/info/rfc6242>.

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

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

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

   [RFC8177]  Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
              Zhang, "YANG Data Model for Key Chains", RFC 8177,
              DOI 10.17487/RFC8177, June 2017,
              <https://www.rfc-editor.org/info/rfc8177>.

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

   [RFC8343]  Bjorklund, M., "A YANG Data Model for Interface
              Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
              <https://www.rfc-editor.org/info/rfc8343>.

   [RFC8349]  Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
              Routing Management (NMDA Version)", RFC 8349,
              DOI 10.17487/RFC8349, March 2018,
              <https://www.rfc-editor.org/info/rfc8349>.

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

Authors' Addresses

   Vishnu Pavan Beeram
   Juniper Networks

   Email: vbeeram@juniper.net

   Tarek Saad (editor)
   Cisco Systems, Inc.
   Juniper Networks

   Email: tsaad@cisco.com tsaad@juniper.net

   Rakesh Gandhi
   Cisco Systems, Inc.

   Email: rgandhi@cisco.com

   Xufeng Liu
   Jabil

   Email: Xufeng_Liu@jabil.com

   Igor Bryskin
   Huawei Technologies

   Email: Igor.Bryskin@huawei.com

   Himanshu Shah
   Ciena

   Email: hshah@ciena.com