[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-saad-teas-yang-rsvp) 00 01 02 03 04 05 06 07 08 09

TEAS Working Group                                             V. Beeram
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                            T. Saad, Ed.
Expires: November 9, 2018                                      R. Gandhi
                                                     Cisco Systems, Inc.
                                                                  X. Liu
                                                                   Jabil
                                                              I. Bryskin
                                                     Huawei Technologies
                                                                 H. Shah
                                                                   Ciena
                                                            May 08, 2018


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

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 extensions to Traffic-Engineering
   (RSVP-TE).  The model covers the configuration, operational state,
   remote procedural 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 November 9, 2018.

Copyright Notice

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




Beeram, et al.          Expires November 9, 2018                [Page 1]


Internet-Draft            RSVP YANG Data Model                  May 2018


   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.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   4
   2.  Design Considerations . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Module Hierarchy  . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Configuration Inheritance . . . . . . . . . . . . . . . .   6
   3.  Model Organization  . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  RSVP Base YANG Model  . . . . . . . . . . . . . . . . . .   7
       3.1.1.  Global Data . . . . . . . . . . . . . . . . . . . . .   8
       3.1.2.  Interface Data  . . . . . . . . . . . . . . . . . . .   9
       3.1.3.  Neighbor Data . . . . . . . . . . . . . . . . . . . .   9
       3.1.4.  Session Data  . . . . . . . . . . . . . . . . . . . .   9
       3.1.5.  Tree Diagram  . . . . . . . . . . . . . . . . . . . .   9
       3.1.6.  YANG Module . . . . . . . . . . . . . . . . . . . . .  14
     3.2.  RSVP Extended YANG Model  . . . . . . . . . . . . . . . .  32
       3.2.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . .  32
       3.2.2.  YANG Module . . . . . . . . . . . . . . . . . . . . .  34
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  44
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  44
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  45
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  45
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  45
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  45
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  47
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  47

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




Beeram, et al.          Expires November 9, 2018                [Page 2]


Internet-Draft            RSVP YANG Data Model                  May 2018


   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

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

1.2.  Tree Diagram

   A simplified graphical representation of the data model is presented
   in each section of the model.  The following notations are used for
   the YANG model data tree representation.






























Beeram, et al.          Expires November 9, 2018                [Page 3]


Internet-Draft            RSVP YANG Data Model                  May 2018


   <status> <flags> <name> <opts> <type>

    <status> is one of:
      +  for current
      x  for deprecated
      o  for obsolete

    <flags> is one of:
      rw  for read-write configuration data
      ro  for read-only non-configuration data
      -x  for execution rpcs
      -n  for notifications

    <name> is the name of the node

   If the node is augmented into the tree from another module, its name
   is printed as <prefix>:<name>

    <opts> is one of:
      ? for an optional leaf or node
      ! for a presence container
      * for a leaf-list or list
      Brackets [<keys>] for a list's keys
      Curly braces {<condition>} for optional feature that make node
   conditional
      Colon : for marking case nodes
      Ellipses ("...") subtree contents not shown

      Parentheses enclose choice and case nodes, and case nodes are also
      marked with a colon (":").

    <type> is the name of the type for leafs and leaf-lists.

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.













Beeram, et al.          Expires November 9, 2018                [Page 4]


Internet-Draft            RSVP YANG Data Model                  May 2018


               +-----------+--------------------+-----------+
               | 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.  Design Considerations

2.1.  Module Hierarchy

   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 identity "rsvp" of
   base "rt:routing-protocol" to identify the RSVP protocol.

   Some RSVP features are categorized as core to the function of the
   protocol that are supported by most vendors claiming 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 to better tune 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 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].
















Beeram, et al.          Expires November 9, 2018                [Page 5]


Internet-Draft            RSVP YANG Data Model                  May 2018


                   +--------------+
          Routing  | ietf-routing |
                   +--------------+
                         o
                         |
                    +-----------+
     RSVP module    | ietf-rsvp |
                    +-----------+
                         o
                         |
     RSVP extended       |
       module       +--------------------+
                    | ietf-rsvp-extended |
                    +--------------------+

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

   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) for
   RSVP feature(s) as well as optional RSVP feature that are not a must
   for basic RSVP operation.

2.2.  Configuration Inheritance

   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.







Beeram, et al.          Expires November 9, 2018                [Page 6]


Internet-Draft            RSVP YANG Data Model                  May 2018


3.  Model Organization

   This document divides the RSVP model into two modules: base and
   extended RSVP modules.  Each module covers configuration, state,
   notifications and RPCs data.  The relationship between the different
   modules is depicted in Figure 1.

3.1.  RSVP Base YANG Model

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

   Data for such state is contained under the respective "state" sub-
   container of the intended object (e.g. interface) as shown in
   Figure 2.



































Beeram, et al.          Expires November 9, 2018                [Page 7]


Internet-Draft            RSVP YANG Data Model                  May 2018


   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
         +--x neighbors-rpc
         +--x sessions-rpc
      notifications:
         +--n global-notif
         +--n interfaces-notif
         +--n neighbors-notif
         +--n sessions-notif


                 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 those applicable
   globally (node scope), per interfaces, per neighbors, or per session.

3.1.1.  Global Data

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





Beeram, et al.          Expires November 9, 2018                [Page 8]


Internet-Draft            RSVP YANG Data Model                  May 2018


3.1.2.  Interface Data

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

3.1.3.  Neighbor Data

   The neighbor data branch of the data model covers configuration and
   state elements relevant to RSVP neighbors.

3.1.4.  Session Data

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

3.1.5.  Tree Diagram

 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
        |  |     +--ro state
        |  |        +--ro local-index?        uint64
        |  |        +--ro destination-port?   inet:port-number
        |  |        +--ro source?             inet:ip-address
        |  |        +--ro 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
        |  |     +--ro messages



Beeram, et al.          Expires November 9, 2018                [Page 9]


Internet-Draft            RSVP YANG Data Model                  May 2018


        |  |     |  +--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?     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



Beeram, et al.          Expires November 9, 2018               [Page 10]


Internet-Draft            RSVP YANG Data Model                  May 2018


        |  |  +--ro state
        |  |     +--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?     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



Beeram, et al.          Expires November 9, 2018               [Page 11]


Internet-Draft            RSVP YANG Data Model                  May 2018


        |     +--rw statistics
        |        +--ro state
        |           +--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?



Beeram, et al.          Expires November 9, 2018               [Page 12]


Internet-Draft            RSVP YANG Data Model                  May 2018


        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?     yang:counter64
        +--rw neighbors
           +--rw neighbor* [address]
              +--rw address    inet:ip-address
              +--ro state
                 +--ro address?                     inet:ip-address
                 +--ro epoch?                       uint32
                 +--ro expiry-time?                 uint32
                 +--ro graceful-restart
                 |  +--ro enabled?                  boolean
                 |  +--ro local-restart-time?       uint32
                 |  +--ro local-recovery-time?      uint32
                 |  +--ro neighbor-restart-time?    uint32
                 |  +--ro neighbor-recovery-time?   uint32
                 |  +--ro helper-mode
                 |     +--ro enabled?                            boolean
                 |     +--ro max-helper-restart-time?            uint32
                 |     +--ro max-helper-recovery-time?           uint32
                 |     +--ro neighbor-restart-time-remaining?    uint32
                 |     +--ro neighbor-recovery-time-remaining?   uint32
                 +--ro hello-status?                enumeration
                 +--ro interface?                   if:interface-ref
                 +--ro neighbor-state?              enumeration
                 +--ro refresh-reduction-capable?   boolean
                 +--ro restart-count?               yang:counter32
                 +--ro restart-time?                yang:date-and-time

                     Figure 3: RSVP model tree diagram




Beeram, et al.          Expires November 9, 2018               [Page 13]


Internet-Draft            RSVP YANG Data Model                  May 2018


3.1.6.  YANG Module

   <CODE BEGINS> file "ietf-rsvp@2017-10-29.yang"
   module ietf-rsvp {

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

     /* Replace with IANA when assigned */
     prefix "rsvp";

     import ietf-interfaces {
       prefix "if";
     }

     import ietf-inet-types {
       prefix inet;
     }

     import ietf-yang-types {
       prefix "yang";
     }

     import ietf-routing {
       prefix "rt";
     }

     import ietf-key-chain {
       prefix "key-chain";
     }

     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



Beeram, et al.          Expires November 9, 2018               [Page 14]


Internet-Draft            RSVP YANG Data Model                  May 2018


                  <mailto:tsaad@cisco.com>

        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 RSVP YANG data model.";

     revision "2017-10-29" {
       description "Latest revision of RSVP yang module.";
       reference "RFC2205";
     }

     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 {
       base rsvp-session-type;
       description "RSVP IPv4 session type";
     }

     identity reservation-style {



Beeram, et al.          Expires November 9, 2018               [Page 15]


Internet-Draft            RSVP YANG Data Model                  May 2018


       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";




Beeram, et al.          Expires November 9, 2018               [Page 16]


Internet-Draft            RSVP YANG Data Model                  May 2018


       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 {



Beeram, et al.          Expires November 9, 2018               [Page 17]


Internet-Draft            RSVP YANG Data Model                  May 2018


       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 {



Beeram, et al.          Expires November 9, 2018               [Page 18]


Internet-Draft            RSVP YANG Data Model                  May 2018


         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 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 {



Beeram, et al.          Expires November 9, 2018               [Page 19]


Internet-Draft            RSVP YANG Data Model                  May 2018


         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 {



Beeram, et al.          Expires November 9, 2018               [Page 20]


Internet-Draft            RSVP YANG Data Model                  May 2018


         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 {
           type yang:counter64;
           description
             "Packet sent count";
         }

         leaf received {
           type yang:counter64;
           description
             "Packet received count";
         }
       }
     }

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

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

         leaf bundle-sent {
           type yang:counter64;



Beeram, et al.          Expires November 9, 2018               [Page 21]


Internet-Draft            RSVP YANG Data Model                  May 2018


           description
             "Bundle sent count";
         }

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

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

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

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

         leaf integrity-challenge-received {
           type yang:counter64;
           description
             "Integrity Challenge received count";
         }

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

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

         leaf notify-sent {
           type yang:counter64;



Beeram, et al.          Expires November 9, 2018               [Page 22]


Internet-Draft            RSVP YANG Data Model                  May 2018


           description
             "Notify sent count";
         }

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

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

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

         leaf path-err-sent {
           type yang:counter64;
           description
             "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;



Beeram, et al.          Expires November 9, 2018               [Page 23]


Internet-Draft            RSVP YANG Data Model                  May 2018


           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;



Beeram, et al.          Expires November 9, 2018               [Page 24]


Internet-Draft            RSVP YANG Data Model                  May 2018


           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 {
           type yang:counter64;
           description
             "The total number of packets received with an invalid
             packet length.";
         }
       }
     }

     grouping statistics_state {



Beeram, et al.          Expires November 9, 2018               [Page 25]


Internet-Draft            RSVP YANG Data Model                  May 2018


       description "RSVP statistic attributes.";
       container statistics {
         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 {
         type inet:ip-address;
         description
           "Address of RSVP neighbor";
       }

       leaf epoch {
         type uint32;
         description
           "Neighbor epoch.";
       }

       leaf expiry-time {
         type uint32;
         units seconds;
         description
           "Neighbor expiry time after which the neighbor state
           is purged if no states associated with it";
       }

       container graceful-restart {
         description
           "Graceful restart information.";

         leaf enabled {
           type boolean;
           description
             "'true' if graceful restart is enabled for the



Beeram, et al.          Expires November 9, 2018               [Page 26]


Internet-Draft            RSVP YANG Data Model                  May 2018


             neighbor.";
         }

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

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

         leaf neighbor-restart-time {
           type uint32;
           units seconds;
           description
             "Neighbor restart time";
         }

         leaf neighbor-recovery-time {
           type uint32;
           units seconds;
           description
             "Neighbor recover time";
         }

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

           leaf enabled {
             type boolean;
             description
               "'true' if helper mode is enabled.";
           }

           leaf max-helper-restart-time {
             type uint32;
             units seconds;
             description
               "The time the router or switch waits after it
                discovers that a neighboring router has gone down
                before it declares the neighbor down";



Beeram, et al.          Expires November 9, 2018               [Page 27]


Internet-Draft            RSVP YANG Data Model                  May 2018


           }

           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";
           }

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

           leaf neighbor-recovery-time-remaining {
             type uint32;
             units seconds;
             description
               "Number of seconds remaining for neighbor to
               refresh.";
           }
         } // helper-mode
       } // graceful-restart

       leaf hello-status {
         type enumeration {
           enum "enabled" {
             description
               "Enabled";
           }
           enum "disabled" {
             description
               "Disabled";
           }
           enum "restarting" {
             description
               "Restarting";
           }
         }
         description
           "Hello status";
       }

       leaf interface {



Beeram, et al.          Expires November 9, 2018               [Page 28]


Internet-Draft            RSVP YANG Data Model                  May 2018


         type if:interface-ref;
         description
           "Interface where RSVP neighbor was detected";
       }

       leaf 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



Beeram, et al.          Expires November 9, 2018               [Page 29]


Internet-Draft            RSVP YANG Data Model                  May 2018


           "Last restart time of the neighbor";
       }
     }

     grouping global-attributes {
       description
         "Top level grouping for RSVP global properties";
       container sessions {
         description
           "RSVP sessions container";
         list session {
           key "local-index";
           config false;
           description
             "List of RSVP sessions";

           leaf local-index {
             type leafref {
               path "../state/local-index";
             }
             description
               "Reference to the local index for the RSVP
               session";
           }
           container state {
             config false;
             description
               "State information associated with RSVP
                session parameters";
             uses session-attributes_state;
           }
         }
       }
       uses statistics_state;
     }

     grouping intf-attributes {
       description
         "Top level grouping for 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" {



Beeram, et al.          Expires November 9, 2018               [Page 30]


Internet-Draft            RSVP YANG Data Model                  May 2018


       when "rt:type = 'rsvp:rsvp'" {
       description
        "This augment is only valid when routing protocol
         instance type is RSVP.";
       }
       description
         "RSVP protocol augmentation";
       container rsvp {
         presence "Enable RSVP feature";
         description "RSVP feature container";
         container globals {
           description "RSVP global properties.";
           uses global-attributes;
           uses graceful-restart;
         }

         container interfaces {
           description
             "RSVP interfaces container";
           uses intf-attributes;

           list interface {
             key "interface";
             description
               "RSVP interfaces.";
             leaf interface {
               type if:interface-ref;
               description
                 "RSVP interface.";
             }
             uses intf-attributes;
           }
         }

         container neighbors {
           description "RSVP neighbors container";
           list neighbor {
             key "address";
             description "List of RSVP neighbors";
             uses neighbor-attributes;
           }
         }
       }
     }
   }
   <CODE ENDS>





Beeram, et al.          Expires November 9, 2018               [Page 31]


Internet-Draft            RSVP YANG Data Model                  May 2018


3.2.  RSVP Extended YANG Model

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

3.2.1.  Tree Diagram

   Figure 4 shows the YANG tree representation for configuration and
   state data that is augmenting the RSVP basic 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:
       +--ro discontinuity-time?   yang:date-and-time
       +--ro out-dropped?          yang:counter64
       +--ro in-dropped?           yang:counter64
       +--ro out-error?            yang:counter64
       +--ro in-error?             yang:counter64
     augment
     /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
     rsvp:rsvp/rsvp:globals/rsvp:statistics/rsvp:state/rsvp:messages:
     augment
     /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
     rsvp:rsvp/rsvp:globals/rsvp:statistics/rsvp:state/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



Beeram, et al.          Expires November 9, 2018               [Page 32]


Internet-Draft            RSVP YANG Data Model                  May 2018


     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





Beeram, et al.          Expires November 9, 2018               [Page 33]


Internet-Draft            RSVP YANG Data Model                  May 2018


3.2.2.  YANG Module

   Figure 5 shows the RSVP extended YANG module:

   <CODE BEGINS> file "ietf-rsvp-extended@2017-10-29.yang"
   module ietf-rsvp-extended {

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

     prefix "rsvp-ext";

     import ietf-rsvp {
       prefix "rsvp";
     }

     import ietf-routing {
       prefix "rt";
     }

     import ietf-yang-types {
       prefix "yang";
     }

     import ietf-key-chain {
       prefix "key-chain";
     }

     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>




Beeram, et al.          Expires November 9, 2018               [Page 34]


Internet-Draft            RSVP YANG Data Model                  May 2018


        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.";

     revision "2017-10-29" {
       description "Latest revision of RSVP extended yang module.";
       reference "RFC2205";
     }

     /* 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 {



Beeram, et al.          Expires November 9, 2018               [Page 35]


Internet-Draft            RSVP YANG Data Model                  May 2018


       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";
       }
     }




Beeram, et al.          Expires November 9, 2018               [Page 36]


Internet-Draft            RSVP YANG Data Model                  May 2018


     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



Beeram, et al.          Expires November 9, 2018               [Page 37]


Internet-Draft            RSVP YANG Data Model                  May 2018


           "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



Beeram, et al.          Expires November 9, 2018               [Page 38]


Internet-Draft            RSVP YANG Data Model                  May 2018


          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



Beeram, et al.          Expires November 9, 2018               [Page 39]


Internet-Draft            RSVP YANG Data Model                  May 2018


           "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



Beeram, et al.          Expires November 9, 2018               [Page 40]


Internet-Draft            RSVP YANG Data Model                  May 2018


           "In packet drop count";
       }

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

       leaf in-error {
         type yang:counter64;
         description
           "In packet rx error 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/" +



Beeram, et al.          Expires November 9, 2018               [Page 41]


Internet-Draft            RSVP YANG Data Model                  May 2018


             "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
             "rsvp:statistics/rsvp:state/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" {
       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" {
       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



Beeram, et al.          Expires November 9, 2018               [Page 42]


Internet-Draft            RSVP YANG Data Model                  May 2018


         "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" {



Beeram, et al.          Expires November 9, 2018               [Page 43]


Internet-Draft            RSVP YANG Data Model                  May 2018


       description
         "RSVP authentication interface configuration extensions";
       uses authentication-extended_config;
     }
   }
   <CODE ENDS>

                    Figure 5: RSVP extended YANG module

4.  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 a YANG module in the YANG Module Names
   registry [RFC6020].

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

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

5.  Security Considerations

   The YANG module defined in this memo is designed to be accessed via
   the NETCONF protocol [RFC6241].  The lowest NETCONF layer is the
   secure transport layer and the mandatory-to-implement secure
   transport is SSH [RFC6242].  The NETCONF access control model
   [RFC8341] provides means to restrict access for particular NETCONF

   users to a pre-configured subset of all available NETCONF 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.




Beeram, et al.          Expires November 9, 2018               [Page 44]


Internet-Draft            RSVP YANG Data Model                  May 2018


6.  Acknowledgement

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

7.  Contributors

      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


8.  References

8.1.  Normative References

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




Beeram, et al.          Expires November 9, 2018               [Page 45]


Internet-Draft            RSVP YANG Data Model                  May 2018


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

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

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




Beeram, et al.          Expires November 9, 2018               [Page 46]


Internet-Draft            RSVP YANG Data Model                  May 2018


8.2.  Informative References

   [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-03 (work in progress), February 2018.

Authors' Addresses

   Vishnu Pavan Beeram
   Juniper Networks

   Email: vbeeram@juniper.net


   Tarek Saad (editor)
   Cisco Systems, Inc.

   Email: tsaad@cisco.com


   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








Beeram, et al.          Expires November 9, 2018               [Page 47]


Html markup produced by rfcmarkup 1.127, available from https://tools.ietf.org/tools/rfcmarkup/