draft-ietf-teas-yang-rsvp-06.txt   draft-ietf-teas-yang-rsvp-07.txt 
TEAS Working Group V. Beeram TEAS Working Group V. Beeram
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track T. Saad, Ed. Intended status: Standards Track T. Saad, Ed.
Expires: May 3, 2017 R. Gandhi Expires: September 11, 2017 R. Gandhi
Cisco Systems Inc Cisco Systems, Inc.
X. Liu X. Liu
Ericsson Jabil
I. Bryskin
Huawei Technologies
H. Shah H. Shah
Ciena Ciena
X. Chen March 10, 2017
Huawei Technologies
R. Jones
Brocade
B. Wen
Comcast
October 30, 2016
A YANG Data Model for Resource Reservation Protocol (RSVP) A YANG Data Model for Resource Reservation Protocol (RSVP)
draft-ietf-teas-yang-rsvp-06 draft-ietf-teas-yang-rsvp-07
Abstract Abstract
This document defines a YANG data model for the configuration and This document defines a YANG data model for the configuration and
management of RSVP Protocol. The model defines generic RSVP protocol management of RSVP Protocol. The model covers the building blocks of
building blocks that can be augmented and used by other RSVP the RSVP protocol that can be augmented and used by other RSVP
extension models such as RVSP extensions to Traffic-Engineering extension models such as RVSP extensions to Traffic-Engineering
(RSVP-TE). The model covers the RSVP protocol configuration, (RSVP-TE). The model covers the configuration, operational state,
operational state, remote procedural calls, and event notifications remote procedural calls, and event notifications data.
data.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 3, 2017. This Internet-Draft will expire on September 11, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
1.4. Open Issues and Next Steps . . . . . . . . . . . . . . . 5 2. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
1.4.1. Module Hierarchy . . . . . . . . . . . . . . . . . . 5 2.1. Module Hierarchy . . . . . . . . . . . . . . . . . . . . 5
1.4.2. Model Data Organization . . . . . . . . . . . . . . . 5 2.2. Data Organization . . . . . . . . . . . . . . . . . . . . 6
1.4.3. State Data . . . . . . . . . . . . . . . . . . . . . 5
2. Design Considerations . . . . . . . . . . . . . . . . . . . . 6
2.1. Base Model(s) . . . . . . . . . . . . . . . . . . . . . . 6
2.2. Extended Model(s) . . . . . . . . . . . . . . . . . . . . 7
2.3. Configuration Inheritance . . . . . . . . . . . . . . . . 7 2.3. Configuration Inheritance . . . . . . . . . . . . . . . . 7
2.4. Routing Instance Support . . . . . . . . . . . . . . . . 8 3. Model Organization . . . . . . . . . . . . . . . . . . . . . 7
3. Model Organization . . . . . . . . . . . . . . . . . . . . . 8 3.1. RSVP Base YANG Model . . . . . . . . . . . . . . . . . . 7
3.1. RSVP Base YANG Model . . . . . . . . . . . . . . . . . . 8 3.1.1. Global Data . . . . . . . . . . . . . . . . . . . . . 9
3.1.1. Configuration and State Data . . . . . . . . . . . . 10 3.1.2. Interface Data . . . . . . . . . . . . . . . . . . . 9
3.1.2. RPC and Notification Data . . . . . . . . . . . . . . 15 3.1.3. Neighbor Data . . . . . . . . . . . . . . . . . . . . 9
3.1.3. YANG Module . . . . . . . . . . . . . . . . . . . . . 15 3.1.4. Session Data . . . . . . . . . . . . . . . . . . . . 9
3.2. RSVP Extended YANG Model . . . . . . . . . . . . . . . . 32 3.1.5. Tree Diagram . . . . . . . . . . . . . . . . . . . . 9
3.2.1. Configuration and State Data . . . . . . . . . . . . 32 3.1.6. YANG Module . . . . . . . . . . . . . . . . . . . . . 14
3.2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 35 3.2. RSVP Extended YANG Model . . . . . . . . . . . . . . . . 33
3.3. RSVP-TE Generic YANG Model . . . . . . . . . . . . . . . 46 3.2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . 34
3.3.1. Configuration and State Data . . . . . . . . . . . . 47 3.2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 40
3.3.2. RPC and Notification Data . . . . . . . . . . . . . . 50 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52
3.3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . 50 5. Security Considerations . . . . . . . . . . . . . . . . . . . 52
3.4. RSVP-TE MPLS Model . . . . . . . . . . . . . . . . . . . 58 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 52
3.4.1. Configuration and State Data . . . . . . . . . . . . 58 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 53
3.4.2. RPC and Notification Data . . . . . . . . . . . . . . 62 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.4.3. YANG Module . . . . . . . . . . . . . . . . . . . . . 62 8.1. Normative References . . . . . . . . . . . . . . . . . . 53
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 75 8.2. Informative References . . . . . . . . . . . . . . . . . 54
5. Security Considerations . . . . . . . . . . . . . . . . . . . 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 55
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 76
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.1. Normative References . . . . . . . . . . . . . . . . . . 76
7.2. Informative References . . . . . . . . . . . . . . . . . 77
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 78
1. Introduction 1. Introduction
YANG [RFC6020] is a data definition language that was introduced to YANG [RFC6020] is a data definition language that was introduced to
define the contents of a conceptual data store that allows networked define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG is proving devices to be managed using NETCONF [RFC6241]. YANG is proving
relevant beyond its initial confines, as bindings to other interfaces relevant beyond its initial confines, as bindings to other interfaces
(e.g. ReST) and encoding other than XML (e.g. JSON) are being (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 defined. Furthermore, YANG data models can be used as the basis of
implementation for other interface, such as CLI and programmatic implementation for other interfaces, such as CLI and programmatic
APIs. APIs.
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage the RSVP protocol. This model covers generic protocol and manage the RSVP protocol [RFC2205]. This model covers RSVP
building blocks that can be augmented and used by other RSVP protocol building blocks that can be augmented and used by other RSVP
extension models- such as extensions for signaling RSVP-TE MPLS (or extension models- such as for signaling RSVP-TE MPLS (or other
other technology specific) Label Switched Paths (LSP)s. technology specific) Label Switched Paths (LSP)s.
1.1. Terminology 1.1. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
1.2. Tree Diagram 1.2. Tree Diagram
skipping to change at page 4, line 44 skipping to change at page 5, line 5
marked with a colon (":"). marked with a colon (":").
<type> is the name of the type for leafs and leaf-lists. <type> is the name of the type for leafs and leaf-lists.
1.3. Prefixes in Data Node Names 1.3. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1. corresponding YANG imported modules, as shown in Table 1.
+--------+-----------------+-----------+ +-----------+--------------------+-----------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+--------+-----------------+-----------+ +-----------+--------------------+-----------+
| yang | ietf-yang-types | [RFC6991] | | yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-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 Table 1: Prefixes and corresponding YANG modules
1.4. Open Issues and Next Steps
This document covers YANG models for data pertaining to the base
RSVP, the generic RSVP-TE, and the MPLS RSVP-TE. The current
revision of this draft covers configuration and state data, but
future revisions are expected to cover data for RPCs, and
notifications.
1.4.1. Module Hierarchy
During discussions, some of the RSVP features were debated whether
they should be present in the base RSVP model or in extension RSVP
model (e.g. RSVP-TE model) especially that some features were
defined in RSVP extension drafts for GMPLS or RSVP-TE states. For
example, the RSVP Hello extensions defined in [RFC3209] with
extensions to RSVP for TE states. However, RSVP Hellos extension can
also apply to non RSVP-TE states, and some vendor implementations,
allow it to be enabled independent of RSVP-TE features.
1.4.2. Model Data Organization
Throughout the model, the approach described in
[I-D.openconfig-netmod-opstate] is adopted to represent data
pertaining to configuration intended state, applied state and derived
state data elements. Each container in the model hold a "config" and
"state" sub-container. The "config" sub-container is used to
represent the intended configurable parameters, and the state sub-
container is used to represent both the applied configurable
parameters and any derived state, such as counters or statistical
information.
The decision to use this approach was made to better align with the
MPLS consolidated model in [I-D.openconfig-mpls-consolidated-model],
and maximize reusability of groupings defined in this document and
allow for possible convergence between the two models.
1.4.3. State Data
Pure state data (for example, protocol derived data) can be modeled
using two options:
o Contained inside the read-write container, under the "state" sub-
container, as shown in Figure 2
o Contained inside a separate read-only container
The first option allows for reusing the same containers that hold
configuration read-write data under a "config" sub-container, and by
adding the state data under the read-only "state" sub-container of
the container. For ephemeral or purely derived states (e.g. RSVP
sessions), and since in this case the state would hang off a read-
write parent container, it will be possible to delete the parent
container and removing such state.
The second option entails defining a new read-only parent container
in the model (e.g. neighbors-state) that holds the data.
This revision of the draft adopts the first option. Further
discussions on this topic are expected to close on the best choice to
adopt.
2. Design Considerations 2. Design Considerations
2.1. Base Model(s) 2.1. Module Hierarchy
The base RSVP model covers core features with the minimal set of The RSVP base YANG module augments the "control-plane-protocol" list
configuration parameters needed to operate them. Additional core in ietf-routing [RFC8022] module with specific RSVP parameters in an
RSVP parameter configuration(s) as well as extended RSVP feature(s) "rsvp" container. It also defines an extensiion identity "rsvp" of
are covered in a separate RSVP extended model. base "rt:routing-protocol" to identify the RSVP protocol.
The RSVP-TE [RFC3209] and other traffic-engineering specific During modeling discussion, some RSVP features are categorized as
enhancements are also addressed in separate module(s). The generic core to the functionality of the protocol, and hence, are supported
and MPLS RSVP traffic-engineering models are augmentations to the by all vendors claiming the support for RSVP. These features'
RSVP base model and are discussed in this revision of the document in configuration and state were grouped in the RSVP base module.
Section 3.3.
Currently, the RSVP-TE module is presented as part of this draft, and Other extended RSVP features are categorized as either optional or
is mostly packet centric. It is expected that the RSVP-TE YANG model providing additional knobs to provide better tune basic functionality
will move to a separate document in the next revision. of the RSVP protocol. The support for extended RSVP features by all
vendors was considered optional. Such features were grouped in a
separate RSVP extended module.
TE basic +---------+ ^: import The augmentation of the RSVP model by other models (e.g. RSVP-TE for
module | ietf-te | o: augment MPLS or other technologies) are considered outside the scope of this
+---------+ document and discussed in separate document(s).
| o
| | +--------------+
v | Routing | ietf-routing |
+--------------+ +--------------+
RSVP-TE module | ietf-rsvp-te |o . . . o
+--------------+ \ |
^ | \ +-----------+
| o +-------------------+ RSVP module | ietf-rsvp |
+-----------+ | ietf-rsvp-otn-te | +-----------+
RSVP module | ietf-rsvp | +-------------------+ o
+-----------+ RSVP-TE with OTN |
o extensions RSVP extended |
| (shown for illustration
RSVP extended | not in this document)
module +--------------------+ module +--------------------+
| ietf-rsvp-extended | | ietf-rsvp-extended |
+--------------------+ +--------------------+
Figure 1: Relationship of RSVP and RSVP-TE modules with other Figure 1: Relationship of RSVP and RSVP extended modules with other
protocol modules protocol modules
The RSVP base model in this revision of the document does not aim to The RSVP base model does not aim to be feature complete. The primary
be feature complete. The primary intent is to cover a set of intent is to cover a set of standard core features (listed below)
standard core features (listed below) that are commonly in use. that are commonly in use.
o Authentication ([RFC2747]) o Authentication ([RFC2747])
o Refresh Reduction ([RFC2961]) o Refresh Reduction ([RFC2961])
o Hellos ([RFC3209]) o Hellos ([RFC3209])
o Graceful Restart ([RFC3473], [RFC5063]) o Graceful Restart ([RFC3473], [RFC5063])
2.2. Extended Model(s)
The extended RSVP YANG model covers non-basic configuration(s) for The extended RSVP YANG model covers non-basic configuration(s) for
RSVP core feature(s) as well as optional RSVP feature that are not a RSVP feature(s) as well as optional RSVP feature that are not a must
must for basic RSVP operation. for basic RSVP operation.
2.2. Data Organization
Throughout the model, the approach described in
[I-D.openconfig-netmod-opstate] is adopted to represent data
pertaining to configuration intended state, applied state and derived
state data elements. Each container in the model hold a "config" and
"state" sub-container.
The "config" sub-container is used to represent the intended
configurable parameters, and the state sub-container is used to
represent both the applied configurable parameters and any derived
state, such as counters or statistical information.
The decision to use this approach was made to better align with the
MPLS consolidated model in [I-D.openconfig-mpls-consolidated-model],
and maximize reusability of groupings defined in this document and
allow for possible convergence between the two models.
The approach described in [I-D.openconfig-netmod-opstate] allows for
modeling the respective intended and applied configuration and
derived state. The state data can be categorized into one of the
following:
o State corresponding to applied configuration
o State corresponding to derived state, counters, stats, etc.
Pure state data (for example, protocol derived data) is placed inside
the "state" sub-container, as shown in Figure 2.
2.3. Configuration Inheritance 2.3. Configuration Inheritance
The defined data model supports configuration inheritance for The defined data model supports configuration inheritance for
neighbors, and interfaces. Data elements defined in the main neighbors, and interfaces. Data elements defined in the main
container (e.g. the container that encompasses the list of container (e.g. the container that encompasses the list of
interfaces, or neighbors) are assumed to apply equally to all interfaces, or neighbors) are assumed to apply equally to all
elements of the list, unless overridden explicitly for a certain elements of the list, unless overridden explicitly for a certain
element (e.g. interface). Vendors are expected to augment the above element (e.g. interface). Vendors are expected to augment the above
container(s) to provide the list of inheritance command for their container(s) to provide the list of inheritance command for their
implementations. implementations.
2.4. Routing Instance Support
There two main popular types of routing protocol configuration that
vendors may support:
o protocol centric - all the protocol related configuration is
contained within the protocol itself. Configuration belonging to
multiple instances of the protocol running in different routing-
instances (e.g. VRFs) are contained under the default routing
instance [I-D.ietf-netmod-routing-cfg]:
o VRF centric - all the protocol related configuration for a
routing- instance is contained within this routing-instance.
On-going discussions within the IETF community have converged on
adopting the VRF centric approach. The proposed model in this
document adheres to this conclusion.
3. Model Organization 3. Model Organization
This document defines YANG data models for RSVP base, RSVP extended, This document divides the RSVP model into two modules: the RSVP base
RSVP-TE generic, and RSVP-TE MPLS configuration, state, notification and extended. Each module covers the configuration, state,
and RPCs. The relationship between the different modules is depicted notification and RPCs of data. The relationship between the
in Figure 1. different modules is depicted in Figure 1.
3.1. RSVP Base YANG Model 3.1. RSVP Base YANG Model
This section describes the RSVP base YANG data model. It covers base This section describes the RSVP base YANG data model. The container
RSVP protocol data defined by RSVP [RFC2205], and enhancements that "rsvp" is the top level container in this data model. The presence
pertain to the base protocol operation. of this container enables the RSVP protocol functionality.
The container "rsvp" is the top level container in this data model.
The presence of this container is expected to enable RSVP protocol
functionality.
The approach described in [I-D.openconfig-netmod-opstate] allows for
modeling the intended and respective applied and derived state. The
TE state data in this model falls into one of the following
categpries:
o State corresponding to applied configuration
o State corrsponding to derived state, counters, stats, etc.
Data for such state is contained under the respective "state" sub- Data for such state is contained under the respective "state" sub-
container of the intended object (e.g. interface) as shown in container of the intended object (e.g. interface) as shown in
Figure 2. Figure 2.
module: ietf-rsvp module: ietf-rsvp
+--rw rsvp! +--rw rsvp!
+--rw globals +--rw globals
+-- rw config +-- rw config
<<intended configuration>> <<intended configuration>>
skipping to change at page 10, line 8 skipping to change at page 8, line 49
+--x global-rpc +--x global-rpc
+--x interfaces-rpc +--x interfaces-rpc
+--x neighbors-rpc +--x neighbors-rpc
+--x sessions-rpc +--x sessions-rpc
notifications: notifications:
+--n global-notif +--n global-notif
+--n interfaces-notif +--n interfaces-notif
+--n neighbors-notif +--n neighbors-notif
+--n sessions-notif +--n sessions-notif
Figure 2: RSVP highlevel model view Figure 2: RSVP high-level tree model view
The following subsections provide overview of the parts of the model The following subsections provide overview of the parts of the model
pertaining to configuration and state data. pertaining to configuration and state data.
3.1.1. 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.1. Global Data 3.1.1. Global Data
This branch of the data model covers global configuration and states This branch of the data model covers global configuration and states
that control RSVP protocol behavior. that control RSVP protocol behavior.
module: ietf-rsvp 3.1.2. Interface Data
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol:
+--rw rsvp!
+--rw globals
| +--rw config
| | +--rw graceful-restart
| | +--rw enabled? boolean
| +--ro state
| +--ro graceful-restart
| | +--ro enabled? boolean
| +--ro packets-stats
| | +--ro sent? yang:counter32
| | +--ro rcvd? yang:counter32
| +--ro protocol-stats
| | +--ro ack-sent? yang:counter32
| | +--ro ack-rcvd? yang:counter32
| | +--ro bundle-sent? yang:counter32
| | +--ro bundle-rcvd? yang:counter32
| | +--ro hello-sent? yang:counter32
| | +--ro hello-rcvd? yang:counter32
| | +--ro integrity-challenge-sent? yang:counter32
| | +--ro integrity-challenge-rcvd? yang:counter32
| | +--ro integrity-response-sent? yang:counter32
| | +--ro integrity-response-rcvd? yang:counter32
| | +--ro notify-sent? yang:counter32
| | +--ro notify-rcvd? yang:counter32
| | +--ro path-sent? yang:counter32
| | +--ro path-rcvd? yang:counter32
| | +--ro path-err-sent? yang:counter32
| | +--ro path-err-rcvd? yang:counter32
| | +--ro path-tear-sent? yang:counter32
| | +--ro path-tear-rcvd? yang:counter32
| | +--ro resv-sent? yang:counter32
| | +--ro resv-rcvd? yang:counter32
| | +--ro resv-confirm-sent? yang:counter32
| | +--ro resv-confirm-rcvd? yang:counter32
| | +--ro resv-err-sent? yang:counter32
| | +--ro resv-err-rcvd? yang:counter32
| | +--ro resv-tear-sent? yang:counter32
| | +--ro resv-tear-rcvd? yang:counter32
| | +--ro summary-refresh-sent? yang:counter32
| | +--ro summary-refresh-rcvd? yang:counter32
| | +--ro unknown-recv? yang:counter32
| +--ro errors-stats
| +--ro authenticate? yang:counter64
| +--ro checksum? yang:counter64
| +--ro packet-len? yang:counter64
3.1.1.2. Interface Data
This branch of the data model covers configuration and state elements This branch of the data model covers configuration and state elements
relevant to one or all RSVP interfaces. Any data configuration relevant to one or all RSVP interfaces. Any data configuration
applied at the "interfaces" container level are equally applicable to applied at the "interfaces" container level are equally applicable to
all interfaces - unless overridden by explicit configuration under a all interfaces - unless overridden by explicit configuration under a
specific interface. specific interface.
+--rw interfaces 3.1.3. Neighbor Data
| +--rw config
| | +--rw refresh-reduction
| | | +--rw enabled? boolean
| | +--rw rsvp-hellos
| | | +--rw enabled? boolean
| | +--rw authentication
| | +--rw enabled? boolean
| | +--rw password? string
| | +--rw algorithm? identityref
| +--ro state
| | +--ro refresh-reduction
| | | +--ro enabled? boolean
| | +--ro rsvp-hellos
| | | +--ro enabled? boolean
| | +--ro authentication
| | | +--ro enabled? boolean
| | | +--ro password? string
| | | +--ro algorithm? identityref
| | +--ro packets-stats
| | | +--ro sent? yang:counter32
| | | +--ro rcvd? yang:counter32
| | +--ro protocol-stats
| | | +--ro ack-sent? yang:counter32
| | | +--ro ack-rcvd? yang:counter32
| | | +--ro bundle-sent? yang:counter32
| | | +--ro bundle-rcvd? yang:counter32
| | | +--ro hello-sent? yang:counter32
| | | +--ro hello-rcvd? yang:counter32
| | | +--ro integrity-challenge-sent? yang:counter32
| | | +--ro integrity-challenge-rcvd? yang:counter32
| | | +--ro integrity-response-sent? yang:counter32
| | | +--ro integrity-response-rcvd? yang:counter32
| | | +--ro notify-sent? yang:counter32
| | | +--ro notify-rcvd? yang:counter32
| | | +--ro path-sent? yang:counter32
| | | +--ro path-rcvd? yang:counter32
| | | +--ro path-err-sent? yang:counter32
| | | +--ro path-err-rcvd? yang:counter32
| | | +--ro path-tear-sent? yang:counter32
| | | +--ro path-tear-rcvd? yang:counter32
| | | +--ro resv-sent? yang:counter32
| | | +--ro resv-rcvd? yang:counter32
| | | +--ro resv-confirm-sent? yang:counter32
| | | +--ro resv-confirm-rcvd? yang:counter32
| | | +--ro resv-err-sent? yang:counter32
| | | +--ro resv-err-rcvd? yang:counter32
| | | +--ro resv-tear-sent? yang:counter32
| | | +--ro resv-tear-rcvd? yang:counter32
| | | +--ro summary-refresh-sent? yang:counter32
| | | +--ro summary-refresh-rcvd? yang:counter32
| | | +--ro unknown-recv? yang:counter32
| | +--ro errors-stats
| | +--ro authenticate? yang:counter64
| | +--ro checksum? yang:counter64
| | +--ro packet-len? yang:counter64
| +--rw interface* [interface]
| +--rw interface if:interface-ref
| +--rw config
| | +--rw refresh-reduction
| | | +--rw enabled? boolean
| | +--rw rsvp-hellos
| | | +--rw enabled? boolean
| | +--rw authentication
| | +--rw enabled? boolean
| | +--rw password? string
| | +--rw algorithm? identityref
| +--ro state
| +--ro refresh-reduction
| | +--ro enabled? boolean
| +--ro rsvp-hellos
| | +--ro enabled? boolean
| +--ro authentication
| | +--ro enabled? boolean
| | +--ro password? string
| | +--ro algorithm? identityref
| +--ro packets-stats
| | +--ro sent? yang:counter32
| | +--ro rcvd? yang:counter32
| +--ro protocol-stats
| | +--ro ack-sent? yang:counter32
| | +--ro ack-rcvd? yang:counter32
| | +--ro bundle-sent? yang:counter32
| | +--ro bundle-rcvd? yang:counter32
| | +--ro hello-sent? yang:counter32
| | +--ro hello-rcvd? yang:counter32
| | +--ro integrity-challenge-sent? yang:counter32
| | +--ro integrity-challenge-rcvd? yang:counter32
| | +--ro integrity-response-sent? yang:counter32
| | +--ro integrity-response-rcvd? yang:counter32
| | +--ro notify-sent? yang:counter32
| | +--ro notify-rcvd? yang:counter32
| | +--ro path-sent? yang:counter32
| | +--ro path-rcvd? yang:counter32
| | +--ro path-err-sent? yang:counter32
| | +--ro path-err-rcvd? yang:counter32
| | +--ro path-tear-sent? yang:counter32
| | +--ro path-tear-rcvd? yang:counter32
| | +--ro resv-sent? yang:counter32
| | +--ro resv-rcvd? yang:counter32
| | +--ro resv-confirm-sent? yang:counter32
| | +--ro resv-confirm-rcvd? yang:counter32
| | +--ro resv-err-sent? yang:counter32
| | +--ro resv-err-rcvd? yang:counter32
| | +--ro resv-tear-sent? yang:counter32
| | +--ro resv-tear-rcvd? yang:counter32
| | +--ro summary-refresh-sent? yang:counter32
| | +--ro summary-refresh-rcvd? yang:counter32
| | +--ro unknown-recv? yang:counter32
| +--ro errors-stats
| +--ro authenticate? yang:counter64
| +--ro checksum? yang:counter64
| +--ro packet-len? yang:counter64
3.1.1.3. Session Data
This branch of the data model covers configuration of elements This branch of the data model covers configuration of elements
relevant to RSVP neighbors. This would be discussed in detail in relevant to RSVP neighbors. This would be discussed in detail in
future revisions. future revisions.
module: ietf-rsvp 3.1.4. Session Data
+--rw rsvp!
+--rw sessions
| +--rw session* [dst_port source destination]
| +--rw dst_port uint16
| +--rw source inet:ip-address
| +--rw destination inet:ip-address
| +--rw config
| +--ro state
3.1.1.4. Neighbor Data
This branch of the data model covers configuration of elements This branch of the data model covers configuration of elements
relevant to RSVP sessions. This would be discussed in detail in relevant to RSVP sessions. This would be discussed in detail in
future revisions. future revisions.
module: ietf-rsvp 3.1.5. Tree Diagram
module: ietf-rsvp
augment
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:
+--rw rsvp! +--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
| | | +--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 config
| | +--rw enabled? boolean
| +--ro state
| +--ro enabled? boolean
+--rw interfaces
| +--rw config
| +--ro state
| +--rw refresh-reduction
| | +--rw config
| | | +--rw enabled? boolean
| | +--ro state
| | +--ro enabled? boolean
| +--rw hellos
| | +--rw config
| | | +--rw enabled? boolean
| | +--ro state
| | +--ro enabled? boolean
| +--rw authentication
| | +--rw config
| | | +--rw enabled? boolean
| | | +--rw authentication-key? string
| | | +--rw crypto-algorithm identityref
| | +--ro state
| | +--ro enabled? boolean
| | +--ro authentication-key? string
| | +--ro crypto-algorithm identityref
| +--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? 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 config
| +--ro state
| +--rw refresh-reduction
| | +--rw config
| | | +--rw enabled? boolean
| | +--ro state
| | +--ro enabled? boolean
| +--rw hellos
| | +--rw config
| | | +--rw enabled? boolean
| | +--ro state
| | +--ro enabled? boolean
| +--rw authentication
| | +--rw config
| | | +--rw enabled? boolean
| | | +--rw authentication-key? string
| | | +--rw crypto-algorithm identityref
| | +--ro state
| | +--ro enabled? boolean
| | +--ro authentication-key? string
| | +--ro crypto-algorithm identityref
| +--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? 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 neighbors
+--rw neighbor* [address] +--rw neighbor* [address]
+--rw address inet:ip-address +--rw address -> ../config/address
+--rw neighbor-attributes +--rw config
+--rw config | +--rw address? inet:ip-address
+--ro state +--ro state
+--ro epoch? uint32 +--ro address? inet:ip-address
+--ro expiry-time? uint32 +--ro epoch? uint32
+--ro graceful-restart +--ro expiry-time? uint32
| +--ro enabled? boolean +--ro graceful-restart
| +--ro local-restart-time? uint32 | +--ro enabled? boolean
| +--ro local-recovery-time? uint32 | +--ro local-restart-time? uint32
| +--ro nbr-restart-time? uint32 | +--ro local-recovery-time? uint32
| +--ro nbr-recovery-time? uint32 | +--ro neighbor-restart-time? uint32
| +--ro helper-mode | +--ro neighbor-recovery-time? uint32
| +--ro helper-mode? boolean | +--ro helper-mode
| +--ro max-helper-restart-time? uint32 | +--ro enabled? boolean
| +--ro max-helper-recovery-time? uint32 | +--ro max-helper-restart-time? uint32
| +--ro nbr-restart-ttd? uint32 | +--ro max-helper-recovery-time? uint32
| +--ro nbr-recovery-ttd? uint32 | +--ro neighbor-restart-time-remaining? uint32
+--ro hello-status? enumeration {hellos}? | +--ro neighbor-recovery-time-remaining? uint32
+--ro interface? if:interface-ref +--ro hello-status? enumeration
+--ro neighbor-state? enumeration +--ro interface? if:interface-ref
+--ro psb-count? uint32 +--ro neighbor-state? enumeration
+--ro rsb-count? uint32 +--ro refresh-reduction-capable? boolean
+--ro refresh-reduction-capable? boolean +--ro restart-count? yang:counter32
+--ro restart-count? uint32 +--ro restart-time? yang:date-and-time
+--ro restart-time? yang:date-and-time
3.1.2. RPC and Notification Data
TBD.
3.1.3. YANG Module Figure 3: RSVP model tree diagram
<CODE BEGINS> file "ietf-rsvp@2016-10-29.yang" 3.1.6. YANG Module
<CODE BEGINS> file "ietf-rsvp@2017-03-10.yang"
module ietf-rsvp { module ietf-rsvp {
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp";
/* Replace with IANA when assigned */ /* Replace with IANA when assigned */
prefix "rsvp"; prefix "rsvp";
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
skipping to change at page 16, line 19 skipping to change at page 14, line 45
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
import ietf-key-chain {
prefix "key-chain";
}
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
WG Chair: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
skipping to change at page 16, line 46 skipping to change at page 15, line 28
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xliu@kuatrotech.com> <mailto:Xufeng_Liu@jabil.com>
Editor: Xia Chen Editor: Xia Chen
<mailto:jescia.chenxia@huawei.com> <mailto:jescia.chenxia@huawei.com>
Editor: Raqib Jones Editor: Raqib Jones
<mailto:raqib@Brocade.com> <mailto:raqib@Brocade.com>
Editor: Bin Wen Editor: Bin Wen
<mailto:Bin_Wen@cable.comcast.com>"; <mailto:Bin_Wen@cable.comcast.com>";
description description
"This module contains the RSVP YANG data model."; "This module contains the RSVP YANG data model.";
revision "2016-10-29" { revision "2017-03-10" {
description "Latest revision of RSVP yang module."; description "Latest revision of RSVP yang module.";
reference "RFC2205"; reference "RFC2205";
} }
identity rsvp { identity rsvp {
base "rt:routing-protocol"; base "rt:routing-protocol";
description "RSVP protocol"; description "RSVP protocol";
} }
identity hash-algorithm { identity rsvp-session-type {
description description "Base RSVP session type";
"Base identity for message-digest algorithm";
} }
identity MD5 { identity rsvp-session-ipv4 {
base hash-algorithm; base rsvp-session-type;
description description "RSVP IPv4 session type";
"MD5 hash algorithm";
reference "RFC1321";
} }
identity SHA-1 { identity rsvp-session-ipv6 {
base hash-algorithm; base rsvp-session-type;
description description "RSVP IPv4 session type";
"SHA-1 hash algorithm"; }
reference "NIST, FIPS PUB 180-1: Secure Hash Standard";
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 { grouping graceful-restart_config {
description description
"Base configuration parameters relating to RSVP "Base configuration parameters relating to RSVP
Graceful-Restart"; Graceful-Restart";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if RSVP Graceful Restart is enabled. "'true' if RSVP Graceful Restart is enabled.
skipping to change at page 18, line 4 skipping to change at page 16, line 50
description description
"Base configuration parameters relating to RSVP "Base configuration parameters relating to RSVP
Graceful-Restart"; Graceful-Restart";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if RSVP Graceful Restart is enabled. "'true' if RSVP Graceful Restart is enabled.
'false' if RSVP Graceful Restart is disabled."; 'false' if RSVP Graceful Restart is disabled.";
} }
} }
grouping graceful-restart { grouping graceful-restart {
description description
"Top level grouping for RSVP graceful-restart "RSVP graceful restart parameters grouping";
parameters";
container graceful-restart { container graceful-restart {
description description
"Top level container for RSVP graceful-restart"; "RSVP graceful restart parameters container";
uses graceful-restart_config; container config {
description
"Configuration parameters for graceful restart
properties";
uses graceful-restart_config;
}
container state {
config false;
description
"State parameters for graceful restart
properties";
uses graceful-restart_config;
}
} }
} }
grouping refresh-reduction_config { grouping refresh-reduction_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
refresh reduction"; refresh reduction";
leaf enabled { leaf enabled {
type boolean; type boolean;
skipping to change at page 18, line 36 skipping to change at page 17, line 46
} }
grouping refresh-reduction { grouping refresh-reduction {
description description
"Top level grouping for RSVP refresh reduction "Top level grouping for RSVP refresh reduction
parameters"; parameters";
container refresh-reduction { container refresh-reduction {
description description
"Top level container for RSVP refresh reduction "Top level container for RSVP refresh reduction
parameters"; parameters";
uses refresh-reduction_config; container config {
description
"Configuration parameters relating to
RSVP refresh reduction parameters";
uses refresh-reduction_config;
}
container state {
config false;
description
"State information associated with RSVP
refresh reduction parameters";
uses refresh-reduction_config;
}
} }
} }
grouping authentication_config { grouping authentication_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
authentication"; authentication";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if RSVP Authenticaiton is enabled. "'true' if RSVP Authentication is enabled.
'false' if RSVP Authenticaiton is disabled."; 'false' if RSVP Authentication is disabled.";
} }
leaf password { leaf authentication-key {
type string; type string;
description description
"An authentication key string"; "An authentication key string";
reference
"RFC 2747: RSVP Cryptographic Authentication";
} }
leaf algorithm { leaf crypto-algorithm {
type identityref { type identityref {
base hash-algorithm; base key-chain:crypto-algorithm;
} }
description mandatory true;
"Cryptographic hash algorithm"; description
"Cryptographic algorithm associated with key.";
} }
} }
grouping authentication { grouping authentication {
description description
"Top level grouping for RSVP authentication parameters"; "Top level grouping for RSVP authentication parameters";
container authentication { container authentication {
description description
"Top level container for RSVP authentication "Top level container for RSVP authentication
parameters"; parameters";
uses authentication_config; container config {
description
"Configuration parameters relating to
RSVP authentication parameters";
uses authentication_config;
}
container state {
config false;
description
"State information associated with RSVP
authentication parameters";
uses authentication_config;
}
} }
} }
grouping rsvp-hellos_config { grouping hellos_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
hellos"; hellos";
leaf enabled { leaf enabled {
type boolean; type boolean;
description description
"'true' if RSVP Hello is enabled. "'true' if RSVP Hello is enabled.
'false' if RSVP Hello is disabled."; 'false' if RSVP Hello is disabled.";
} }
} }
grouping rsvp-hellos { grouping hellos {
description description
"Top level grouping for RSVP hellos parameters"; "Top level grouping for RSVP hellos parameters";
container rsvp-hellos { container hellos {
description description
"Top level container for RSVP hello parameters"; "Top level container for RSVP hello parameters";
uses rsvp-hellos_config; container config {
description
"Configuration parameters relating to
RSVP hello parameters";
uses hellos_config;
}
container state {
config false;
description
"State information associated with RSVP
hello parameters";
uses hellos_config;
}
} }
} }
grouping signaling-parameters_config { grouping signaling-parameters_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
signaling"; signaling";
} }
grouping signaling-parameters { grouping signaling-parameters {
description description
"Top level grouping for RSVP signaling parameters"; "Top level grouping for RSVP signaling parameters";
uses signaling-parameters_config;
}
grouping session-attributes {
description
"Top level grouping for RSVP session properties";
container config { container config {
description description
"Configuration for session properties"; "Configuration parameters relating to
RSVP signaling parameters";
uses signaling-parameters_config;
} }
container state { container state {
config false; config false;
description description
"State information associated with RSVP "State information associated with RSVP
session properties"; 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 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 { grouping neighbor-attributes {
description description
"Top level grouping for RSVP neighbor properties"; "Top level grouping for RSVP neighbor properties";
container neighbor-attributes { container config {
description description
"Top level container for RSVP neighbor properties"; "Configuration for neighbor properties";
container config { leaf address {
description type inet:ip-address;
"Configuration for neighbor properties";
}
container state {
config false;
description description
"State information associated with RSVP "Address of RSVP neighbor";
neighbor properties";
uses neighbor-derived_state;
} }
} }
container state {
config false;
description
"State information associated with RSVP
neighbor properties";
uses neighbor-derived_state;
}
} }
grouping statistics-packets_state { grouping packets_state {
description description
"Packet statistics grouping"; "Packet statistics grouping";
container packets-stats { container packets {
description description
"Packet statistics container"; "Packet statistics container";
leaf sent { leaf sent {
type yang:counter32; type yang:counter64;
description description
"Packet sent count"; "Packet sent count";
} }
leaf rcvd { leaf received {
type yang:counter32; type yang:counter64;
description description
"Packet received count"; "Packet received count";
} }
} }
} }
grouping statistics-protocol_state { grouping protocol_state {
description description
"RSVP protocol statistics grouping"; "RSVP protocol statistics grouping";
container protocol-stats { container messages {
description description
"RSVP protocol statistics container"; "RSVP protocol statistics container";
leaf ack-sent { leaf ack-sent {
type yang:counter32; type yang:counter64;
description description
"Hello sent count"; "Hello sent count";
} }
leaf ack-rcvd { leaf ack-received {
type yang:counter32; type yang:counter64;
description description
"Hello received count"; "Hello received count";
} }
leaf bundle-sent { leaf bundle-sent {
type yang:counter32; type yang:counter64;
description description
"Bundle sent count"; "Bundle sent count";
} }
leaf bundle-rcvd { leaf bundle-received {
type yang:counter32; type yang:counter64;
description description
"Bundle received count"; "Bundle received count";
} }
leaf hello-sent { leaf hello-sent {
type yang:counter32; type yang:counter64;
description description
"Hello sent count"; "Hello sent count";
} }
leaf hello-rcvd { leaf hello-received {
type yang:counter32; type yang:counter64;
description description
"Hello received count"; "Hello received count";
} }
leaf integrity-challenge-sent { leaf integrity-challenge-sent {
type yang:counter32; type yang:counter64;
description description
"Integrity Challenge sent count"; "Integrity Challenge sent count";
} }
leaf integrity-challenge-rcvd { leaf integrity-challenge-received {
type yang:counter32; type yang:counter64;
description description
"Integrity Challenge received count"; "Integrity Challenge received count";
} }
leaf integrity-response-sent { leaf integrity-response-sent {
type yang:counter32; type yang:counter64;
description description
"Integrity Response sent count"; "Integrity Response sent count";
} }
leaf integrity-response-rcvd { leaf integrity-response-received {
type yang:counter32; type yang:counter64;
description description
"Integrity Response received count"; "Integrity Response received count";
} }
leaf notify-sent { leaf notify-sent {
type yang:counter32; type yang:counter64;
description description
"Notify sent count"; "Notify sent count";
} }
leaf notify-rcvd { leaf notify-received {
type yang:counter32; type yang:counter64;
description description
"Notify received count"; "Notify received count";
} }
leaf path-sent { leaf path-sent {
type yang:counter32; type yang:counter64;
description description
"Path sent count"; "Path sent count";
} }
leaf path-rcvd { leaf path-received {
type yang:counter32; type yang:counter64;
description description
"Path received count"; "Path received count";
} }
leaf path-err-sent { leaf path-err-sent {
type yang:counter32; type yang:counter64;
description description
"Path error sent count"; "Path error sent count";
} }
leaf path-err-rcvd { leaf path-err-received {
type yang:counter32; type yang:counter64;
description description
"Path error received count"; "Path error received count";
} }
leaf path-tear-sent { leaf path-tear-sent {
type yang:counter32; type yang:counter64;
description description
"Path tear sent count"; "Path tear sent count";
} }
leaf path-tear-rcvd { leaf path-tear-received {
type yang:counter32; type yang:counter64;
description description
"Path tear received count"; "Path tear received count";
} }
leaf resv-sent { leaf resv-sent {
type yang:counter32; type yang:counter64;
description description
"Resv sent count"; "Resv sent count";
} }
leaf resv-rcvd { leaf resv-received {
type yang:counter32; type yang:counter64;
description description
"Resv received count"; "Resv received count";
} }
leaf resv-confirm-sent { leaf resv-confirm-sent {
type yang:counter32; type yang:counter64;
description description
"Confirm sent count"; "Confirm sent count";
} }
leaf resv-confirm-rcvd { leaf resv-confirm-received {
type yang:counter32; type yang:counter64;
description description
"Confirm received count"; "Confirm received count";
} }
leaf resv-err-sent { leaf resv-err-sent {
type yang:counter32; type yang:counter64;
description description
"Resv error sent count"; "Resv error sent count";
} }
leaf resv-err-rcvd { leaf resv-err-received {
type yang:counter32; type yang:counter64;
description description
"Resv error received count"; "Resv error received count";
} }
leaf resv-tear-sent { leaf resv-tear-sent {
type yang:counter32; type yang:counter64;
description description
"Resv tear sent count"; "Resv tear sent count";
} }
leaf resv-tear-rcvd { leaf resv-tear-received {
type yang:counter32; type yang:counter64;
description description
"Resv tear received count"; "Resv tear received count";
} }
leaf summary-refresh-sent { leaf summary-refresh-sent {
type yang:counter32; type yang:counter64;
description description
"Summary refresh sent count"; "Summary refresh sent count";
} }
leaf summary-refresh-rcvd { leaf summary-refresh-received {
type yang:counter32; type yang:counter64;
description description
"Summary refresh received count"; "Summary refresh received count";
} }
leaf unknown-recv { leaf unknown-messages-received {
type yang:counter32; type yang:counter64;
description description
"Unknown packet received count"; "Unknown packet received count";
} }
} }
} }
grouping errors_state {
grouping statistics-errors_state {
description description
"Error statistics state grouping"; "Error statistics state grouping";
container errors-stats { container errors {
description description
"Error statistics state container"; "Error statistics state container";
leaf authenticate { leaf authenticate {
type yang:counter64; type yang:counter64;
description description
"The total number of packets received with an "The total number of packets received with an
authentication failure."; authentication failure.";
} }
leaf checksum { leaf checksum {
skipping to change at page 25, line 37 skipping to change at page 27, line 31
checksum value."; checksum value.";
} }
leaf packet-len { leaf packet-len {
type yang:counter64; type yang:counter64;
description description
"The total number of packets received with an invalid "The total number of packets received with an invalid
packet length."; packet length.";
} }
} }
} // statistics_state }
grouping statistics_state { grouping statistics_state {
description "RSVP statistic attributes."; description "RSVP statistic attributes.";
uses statistics-packets_state; container statistics {
uses statistics-protocol_state; description
uses statistics-errors_state; "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 { grouping neighbor-derived_state {
description description
"Derived state at neighbor level."; "Derived state at neighbor level.";
leaf address {
type inet:ip-address;
description
"Address of RSVP neighbor";
}
leaf epoch { leaf epoch {
type uint32; type uint32;
description description
"Neighbor epoch."; "Neighbor epoch.";
} }
leaf expiry-time { leaf expiry-time {
type uint32; type uint32;
units seconds; units seconds;
description description
skipping to change at page 26, line 41 skipping to change at page 28, line 51
"Local node restart time"; "Local node restart time";
} }
leaf local-recovery-time { leaf local-recovery-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"Local node recover time"; "Local node recover time";
} }
leaf nbr-restart-time { leaf neighbor-restart-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"Neighbor restart time"; "Neighbor restart time";
} }
leaf nbr-recovery-time { leaf neighbor-recovery-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"Neighbor recover time"; "Neighbor recover time";
} }
container helper-mode { container helper-mode {
description description
"Helper mode information "; "Helper mode information ";
leaf helper-mode { leaf enabled {
type boolean; type boolean;
description description
"'true' if helper mode is enabled."; "'true' if helper mode is enabled.";
} }
leaf max-helper-restart-time { leaf max-helper-restart-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"The time the router or switch waits after it "The time the router or switch waits after it
skipping to change at page 27, line 34 skipping to change at page 29, line 44
} }
leaf max-helper-recovery-time { leaf max-helper-recovery-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"The amount of time the router retains the state of its "The amount of time the router retains the state of its
RSVP neighbors while they undergo a graceful restart"; RSVP neighbors while they undergo a graceful restart";
} }
leaf nbr-restart-ttd { leaf neighbor-restart-time-remaining {
type uint32; type uint32;
units seconds; units seconds;
description description
"Number of seconds remaining for neighbor to send "Number of seconds remaining for neighbor to send
Hello message after restart."; Hello message after restart.";
} }
leaf neighbor-recovery-time-remaining {
leaf nbr-recovery-ttd {
type uint32; type uint32;
units seconds; units seconds;
description description
"Number of seconds remaining for neighbor to "Number of seconds remaining for neighbor to
refresh."; refresh.";
} }
} // helper-mode } // helper-mode
} // graceful-restart } // graceful-restart
leaf hello-status { leaf hello-status {
type enumeration { type enumeration {
enum "enabled" { enum "enabled" {
description description
"Enabled"; "Enabled";
} }
enum "disabled" { enum "disabled" {
description description
"Disabled"; "Disabled";
} }
skipping to change at page 28, line 26 skipping to change at page 30, line 36
"Restarting"; "Restarting";
} }
} }
description description
"Hello status"; "Hello status";
} }
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description description
"Interface to this neighbor."; "Interface where RSVP neighbor was detected";
} }
leaf neighbor-state { leaf neighbor-state {
type enumeration { type enumeration {
enum "up" { enum "up" {
description description
"up"; "up";
} }
enum "down" { enum "down" {
description description
skipping to change at page 28, line 42 skipping to change at page 31, line 4
description description
"up"; "up";
} }
enum "down" { enum "down" {
description description
"down"; "down";
} }
enum "hello-disable" { enum "hello-disable" {
description description
"hello-disable"; "hello-disable";
} }
enum "restarting" { enum "restarting" {
description description
"restarting"; "restarting";
} }
} }
description description
"Neighbor state"; "Neighbor state";
} }
leaf psb-count {
type uint32;
description
"Number of PSB state currently referencing the
neighbor.";
}
leaf rsb-count {
type uint32;
description
"Number of RSB state currently referencing the
neighbor.";
}
leaf refresh-reduction-capable { leaf refresh-reduction-capable {
type boolean; type boolean;
description description
"Whether neighbor is refresh reduction capable."; "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 { leaf restart-count {
type uint32; type yang:counter32;
description description
"Number of times this neighbor restart"; "Number of times this neighbor restart";
} }
leaf restart-time { leaf restart-time {
type yang:date-and-time; type yang:date-and-time;
description description
"Last restart time of the neighbor"; "Last restart time of the neighbor";
} }
} // neighbor-derived_state }
grouping global-attributes { grouping global-attributes {
description description
"Top level grouping for RSVP global properties"; "Top level grouping for RSVP global properties";
container config { container sessions {
description
"Configuration globals properties";
uses graceful-restart;
}
container state {
config false;
description description
"State information associated with RSVP "RSVP sessions container";
global properties"; list session {
uses graceful-restart; key "local-index";
uses statistics_state; 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 { grouping intf-attributes {
description description
"Top level grouping for RSVP interface properties"; "Top level grouping for RSVP interface properties";
container config { uses signaling-parameters;
description uses refresh-reduction;
"Configuration parameters relating to uses hellos;
RSVP interface parameters"; uses authentication;
uses signaling-parameters; uses statistics_state;
uses refresh-reduction;
uses rsvp-hellos;
uses authentication;
}
container state {
config false;
description
"State information associated with RSVP
interface parameters";
uses signaling-parameters;
uses refresh-reduction;
uses rsvp-hellos;
uses authentication;
uses statistics_state;
}
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol" { + "rt:control-plane-protocol" {
when "rt:type = 'rsvp:rsvp'" { when "rt:type = 'rsvp:rsvp'" {
description description
"This augment is only valid when routing protocol "This augment is only valid when routing protocol
instance type is RSVP."; instance type is RSVP.";
} }
description description
"RSVP protocol augmentation"; "RSVP protocol augmentation";
container rsvp { container rsvp {
presence "Enable RSVP feature"; presence "Enable RSVP feature";
description "RSVP feature container"; description "RSVP feature container";
container globals { container globals {
description "RSVP global properties."; description "RSVP global properties.";
uses global-attributes; uses global-attributes;
uses graceful-restart;
} }
container interfaces { container interfaces {
description description
"RSVP interfaces container"; "RSVP interfaces container";
uses intf-attributes; uses intf-attributes;
list interface { list interface {
key "interface"; key "interface";
description description
"RSVP interfaces."; "RSVP interfaces.";
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description description
"RSVP interface."; "RSVP interface.";
skipping to change at page 31, line 20 skipping to change at page 33, line 20
"RSVP interfaces."; "RSVP interfaces.";
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description description
"RSVP interface."; "RSVP interface.";
} }
uses intf-attributes; uses intf-attributes;
} }
} }
container sessions {
description
"RSVP sessions container";
list session {
key "dst_port source destination";
description
"List of RSVP sessions";
leaf dst_port {
type uint16;
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";
}
uses session-attributes;
}
}
container neighbors { container neighbors {
description description
"RSVP neighbors container"; "RSVP neighbors container";
list neighbor { list neighbor {
key "address"; key "address";
description description
"List of RSVP neighbors"; "List of RSVP neighbors";
leaf address { leaf address {
type inet:ip-address; type leafref {
path "../config/address";
}
description description
"Neighbor address"; "Address of RSVP neighbor";
} }
uses neighbor-attributes; uses neighbor-attributes;
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
3.2. RSVP Extended YANG Model 3.2. RSVP Extended YANG Model
The RSVP extended YANG model covers optional configuration(s) for The RSVP extended YANG model covers optional or non-core RSVP
RSVP core feature(s). It also covers non-core RSVP feature(s) that feature(s). It also covers feature(s) that are not necessarily
are negotiated with "if-feature" checks. supported by all vendors, and hence, guarded with "if-feature"
checks.
3.2.1. Configuration and State Data 3.2.1. Tree Diagram
Figure 3 shows the YANG tree representation for configuration and Figure 4 shows the YANG tree representation for configuration and
state data that is augmenting the RSVP basic module: state data that is augmenting the RSVP basic module:
module: ietf-rsvp-extended module: ietf-rsvp
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol augment
/rsvp:rsvp/rsvp:globals/rsvp:config/rsvp:graceful-restart: /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol:
+--rw restart-time? uint32 +--rw rsvp!
+--rw recovery-time? uint32 +--rw globals
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | +--rw sessions
/rsvp:rsvp/rsvp:globals/rsvp:state/rsvp:graceful-restart: | | +--ro session* [local-index]
+--ro restart-time? uint32 | | +--ro local-index -> ../state/local-index
+--ro recovery-time? uint32 | | +--ro state
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro local-index? uint64
/rsvp:rsvp/rsvp:globals/rsvp:state/rsvp:packets-stats: | | +--ro destination-port? inet:port-number
+--ro discontinuity-time? yang:date-and-time | | +--ro source? inet:ip-address
+--ro tx-dropped? yang:counter32 | | +--ro destination? inet:ip-address
+--ro rx-dropped? yang:counter32 | | +--ro session-name? string
+--ro tx-error? yang:counter32 | | +--ro session-state? enumeration
+--ro rx-error? yang:counter32 | | +--ro session-type? identityref
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro psbs
/rsvp:rsvp/rsvp:globals/rsvp:state/rsvp:protocol-stats: | | | +--ro psb*
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--ro source-port? inet:port-number
/rsvp:rsvp/rsvp:globals/rsvp:state/rsvp:errors-stats: | | | +--ro expires-in? uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro rsbs
/rsvp:rsvp/rsvp:interfaces/rsvp:config: | | +--ro rsb*
+--rw refresh-interval? uint32 | | +--ro source-port? inet:port-number
+--rw refresh-misses? uint32 | | +--ro reservation-style? identityref
+--rw checksum? uint32 | | +--ro expires-in? uint32
+--rw patherr-state-removal? empty | +--rw statistics
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro state
/rsvp:rsvp/rsvp:interfaces/rsvp:state: | | +--ro messages
+--ro refresh-interval? uint32 | | | +--ro ack-sent? yang:counter64
+--ro refresh-misses? uint32 | | | +--ro ack-received? yang:counter64
+--ro checksum? uint32 | | | +--ro bundle-sent? yang:counter64
+--ro patherr-state-removal? empty | | | +--ro bundle-received? yang:counter64
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--ro hello-sent? yang:counter64
/rsvp:rsvp/rsvp:interfaces/rsvp:config/rsvp:refresh-reduction: | | | +--ro hello-received? yang:counter64
+--rw bundle-message-max-size? uint32 | | | +--ro integrity-challenge-sent? yang:counter64
+--rw reliable-ack-hold-time? uint32 | | | +--ro integrity-challenge-received? yang:counter64
+--rw reliable-ack-max-size? uint32 | | | +--ro integrity-response-sent? yang:counter64
+--rw reliable-retransmit-time? uint32 | | | +--ro integrity-response-received? yang:counter64
+--rw reliable-srefresh? empty | | | +--ro notify-sent? yang:counter64
+--rw summary-max-size? uint32 | | | +--ro notify-received? yang:counter64
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--ro path-sent? yang:counter64
/rsvp:rsvp/rsvp:interfaces/rsvp:state/rsvp:refresh-reduction: | | | +--ro path-received? yang:counter64
+--ro bundle-message-max-size? uint32 | | | +--ro path-err-sent? yang:counter64
+--ro reliable-ack-hold-time? uint32 | | | +--ro path-err-received? yang:counter64
+--ro reliable-ack-max-size? uint32 | | | +--ro path-tear-sent? yang:counter64
+--ro reliable-retransmit-time? uint32 | | | +--ro path-tear-received? yang:counter64
+--ro reliable-srefresh? empty | | | +--ro resv-sent? yang:counter64
+--ro summary-max-size? uint32 | | | +--ro resv-received? yang:counter64
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--ro resv-confirm-sent? yang:counter64
/rsvp:rsvp/rsvp:interfaces/rsvp:config/rsvp:rsvp-hellos: | | | +--ro resv-confirm-received? yang:counter64
+--rw interface-based? empty | | | +--ro resv-err-sent? yang:counter64
+--rw hello-interval? uint32 | | | +--ro resv-err-received? yang:counter64
+--rw hello-misses? uint32 | | | +--ro resv-tear-sent? yang:counter64
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--ro resv-tear-received? yang:counter64
/rsvp:rsvp/rsvp:interfaces/rsvp:state/rsvp:rsvp-hellos: | | | +--ro summary-refresh-sent? yang:counter64
+--ro interface-based? empty | | | +--ro summary-refresh-received? yang:counter64
+--ro hello-interval? uint32 | | | +--ro unknown-messages-received? yang:counter64
+--ro hello-misses? uint32 | | +--ro packets
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--ro sent? yang:counter64
/rsvp:rsvp/rsvp:interfaces/rsvp:config/rsvp:authentication: | | | +--ro received? yang:counter64
+--rw lifetime? uint32 | | | +--ro rsvp-ext:discontinuity-time? yang:date-and-time
+--rw window-size? uint32 | | | +--ro rsvp-ext:out-dropped? yang:counter64
+--rw challenge? empty | | | +--ro rsvp-ext:in-dropped? yang:counter64
+--rw retransmits? uint32 | | | +--ro rsvp-ext:out-error? yang:counter64
+--rw key-chain? string | | | +--ro rsvp-ext:in-error? yang:counter64
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro errors
/rsvp:rsvp/rsvp:interfaces/rsvp:state/rsvp:authentication: | | +--ro authenticate? yang:counter64
+--ro lifetime? uint32 | | +--ro checksum? yang:counter64
+--ro window-size? uint32 | | +--ro packet-len? yang:counter64
+--ro challenge? empty | +--rw graceful-restart
+--ro retransmits? uint32 | +--rw config
+--ro key-chain? string | | +--rw enabled? boolean
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--rw rsvp-ext:restart-time? uint32
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:config: | | +--rw rsvp-ext:recovery-time? uint32
+--rw refresh-interval? uint32 | +--ro state
+--rw refresh-misses? uint32 | +--ro enabled? boolean
+--rw checksum? uint32 | +--ro rsvp-ext:restart-time? uint32
+--rw patherr-state-removal? empty | +--ro rsvp-ext:recovery-time? uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol +--rw interfaces
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:state: | +--rw config
+--ro refresh-interval? uint32 | | +--rw rsvp-ext:refresh-interval? uint32
+--ro refresh-misses? uint32 | | +--rw rsvp-ext:refresh-misses? uint32
+--ro checksum? uint32 | | +--rw rsvp-ext:checksum? boolean
+--ro patherr-state-removal? empty | | +--rw rsvp-ext:patherr-state-removal? empty
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | +--ro state
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:config/ | | +--ro rsvp-ext:refresh-interval? uint32
rsvp:refresh-reduction: | | +--ro rsvp-ext:refresh-misses? uint32
+--rw bundle-message-max-size? uint32 | | +--ro rsvp-ext:checksum? boolean
+--rw reliable-ack-hold-time? uint32 | | +--ro rsvp-ext:patherr-state-removal? empty
+--rw reliable-ack-max-size? uint32 | +--rw refresh-reduction
+--rw reliable-retransmit-time? uint32 | | +--rw config
+--rw reliable-srefresh? empty | | | +--rw enabled? boolean
+--rw summary-max-size? uint32 | | | +--rw rsvp-ext:bundle-message-max-size? uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--rw rsvp-ext:reliable-ack-hold-time? uint32
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:state/ | | | +--rw rsvp-ext:reliable-ack-max-size? uint32
rsvp:refresh-reduction: | | | +--rw rsvp-ext:reliable-retransmit-time? uint32
+--ro bundle-message-max-size? uint32 | | | +--rw rsvp-ext:reliable-srefresh? empty
+--ro reliable-ack-hold-time? uint32 | | | +--rw rsvp-ext:summary-max-size? uint32
+--ro reliable-ack-max-size? uint32 | | +--ro state
+--ro reliable-retransmit-time? uint32 | | +--ro enabled? boolean
+--ro reliable-srefresh? empty | | +--ro rsvp-ext:bundle-message-max-size? uint32
+--ro summary-max-size? uint32 | | +--ro rsvp-ext:reliable-ack-hold-time? uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro rsvp-ext:reliable-ack-max-size? uint32
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:config/rsvp:rsvp-hellos: | | +--ro rsvp-ext:reliable-retransmit-time? uint32
+--rw interface-based? empty | | +--ro rsvp-ext:reliable-srefresh? empty
+--rw hello-interval? uint32 | | +--ro rsvp-ext:summary-max-size? uint32
+--rw hello-misses? uint32 | +--rw hellos
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--rw config
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:state/rsvp:rsvp-hellos: | | | +--rw enabled? boolean
+--ro interface-based? empty | | | +--rw rsvp-ext:interface-based? empty
+--ro hello-interval? uint32 | | | +--rw rsvp-ext:hello-interval? uint32
+--ro hello-misses? uint32 | | | +--rw rsvp-ext:hello-misses? uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | +--ro state
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:config/ | | +--ro enabled? boolean
rsvp:authentication: | | +--ro rsvp-ext:interface-based? empty
+--rw lifetime? uint32 | | +--ro rsvp-ext:hello-interval? uint32
+--rw window-size? uint32 | | +--ro rsvp-ext:hello-misses? uint32
+--rw challenge? empty | +--rw authentication
+--rw retransmits? uint32 | | +--rw config
+--rw key-chain? string | | | +--rw enabled? boolean
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | | | +--rw authentication-key? string
/rsvp:rsvp/rsvp:interfaces/rsvp:interface/rsvp:state/rsvp:authentication | | | +--rw crypto-algorithm identityref
+--ro lifetime? uint32 | | | +--rw rsvp-ext:lifetime? uint32
+--ro window-size? uint32 | | | +--rw rsvp-ext:window-size? uint32
+--ro challenge? empty | | | +--rw rsvp-ext:challenge? empty
+--ro retransmits? uint32 | | | +--rw rsvp-ext:retransmits? uint32
| | | +--rw rsvp-ext:key-chain? key-chain:key-chain-ref
| | +--ro state
| | +--ro enabled? boolean
| | +--ro authentication-key? string
| | +--ro crypto-algorithm identityref
| | +--ro rsvp-ext:lifetime? uint32
| | +--ro rsvp-ext:window-size? uint32
| | +--ro rsvp-ext:challenge? empty
| | +--ro rsvp-ext:retransmits? uint32
| | +--ro rsvp-ext:key-chain? key-chain:key-chain-ref
| +--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? 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 config
| | +--rw rsvp-ext:refresh-interval? uint32
| | +--rw rsvp-ext:refresh-misses? uint32
| | +--rw rsvp-ext:checksum? boolean
| | +--rw rsvp-ext:patherr-state-removal? empty
| +--ro state
| | +--ro rsvp-ext:refresh-interval? uint32
| | +--ro rsvp-ext:refresh-misses? uint32
| | +--ro rsvp-ext:checksum? boolean
| | +--ro rsvp-ext:patherr-state-removal? empty
| +--rw refresh-reduction
| | +--rw config
| | | +--rw enabled? boolean
| | | +--rw rsvp-ext:bundle-message-max-size? uint32
| | | +--rw rsvp-ext:reliable-ack-hold-time? uint32
| | | +--rw rsvp-ext:reliable-ack-max-size? uint32
| | | +--rw rsvp-ext:reliable-retransmit-time? uint32
| | | +--rw rsvp-ext:reliable-srefresh? empty
| | | +--rw rsvp-ext:summary-max-size? uint32
| | +--ro state
| | +--ro enabled? boolean
| | +--ro rsvp-ext:bundle-message-max-size? uint32
| | +--ro rsvp-ext:reliable-ack-hold-time? uint32
| | +--ro rsvp-ext:reliable-ack-max-size? uint32
| | +--ro rsvp-ext:reliable-retransmit-time? uint32
| | +--ro rsvp-ext:reliable-srefresh? empty
| | +--ro rsvp-ext:summary-max-size? uint32
| +--rw hellos
| | +--rw config
| | | +--rw enabled? boolean
| | | +--rw rsvp-ext:interface-based? empty
| | | +--rw rsvp-ext:hello-interval? uint32
| | | +--rw rsvp-ext:hello-misses? uint32
| | +--ro state
| | +--ro enabled? boolean
| | +--ro rsvp-ext:interface-based? empty
| | +--ro rsvp-ext:hello-interval? uint32
| | +--ro rsvp-ext:hello-misses? uint32
| +--rw authentication
| | +--rw config
| | | +--rw enabled? boolean
| | | +--rw authentication-key? string
| | | +--rw crypto-algorithm identityref
| | | +--rw rsvp-ext:lifetime? uint32
| | | +--rw rsvp-ext:window-size? uint32
| | | +--rw rsvp-ext:challenge? empty
| | | +--rw rsvp-ext:retransmits? uint32
| | | +--rw rsvp-ext:key-chain? key-chain:key-chain-ref
| | +--ro state
| | +--ro enabled? boolean
| | +--ro authentication-key? string
| | +--ro crypto-algorithm identityref
| | +--ro rsvp-ext:lifetime? uint32
| | +--ro rsvp-ext:window-size? uint32
| | +--ro rsvp-ext:challenge? empty
| | +--ro rsvp-ext:retransmits? uint32
| | +--ro rsvp-ext:key-chain? key-chain:key-chain-ref
| +--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? 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 -> ../config/address
+--rw config
| +--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 extended YANG Tree representation Figure 4: RSVP extended model tree diagram
3.2.2. YANG Module 3.2.2. YANG Module
Figure 4 shows the RSVP extended YANG module: Figure 5 shows the RSVP extended YANG module:
<CODE BEGINS> file "ietf-rsvp-extended@2016-10-29.yang"
<CODE BEGINS> file "ietf-rsvp-extended@2017-03-10.yang"
module ietf-rsvp-extended { module ietf-rsvp-extended {
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-extended"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-extended";
prefix "rsvp-ext"; prefix "rsvp-ext";
import ietf-rsvp { import ietf-rsvp {
prefix "rsvp"; prefix "rsvp";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-key-chain {
prefix "key-chain";
}
organization organization
"IETF Traffic Engineering Architecture and Signaling (TEAS) "IETF Traffic Engineering Architecture and Signaling (TEAS)
Working Group"; Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/teas/> "WG Web: <http://tools.ietf.org/wg/teas/>
WG List: <mailto:teas@ietf.org> WG List: <mailto:teas@ietf.org>
WG Chair: Lou Berger WG Chair: Lou Berger
<mailto:lberger@labn.net> <mailto:lberger@labn.net>
WG Chair: Vishnu Pavan Beeram WG Chair: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
skipping to change at page 36, line 18 skipping to change at page 41, line 31
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xliu@kuatrotech.com> <mailto:Xufeng_Liu@jabil.com>
Editor: Xia Chen Editor: Xia Chen
<mailto:jescia.chenxia@huawei.com> <mailto:jescia.chenxia@huawei.com>
Editor: Raqib Jones Editor: Raqib Jones
<mailto:raqib@Brocade.com> <mailto:raqib@Brocade.com>
Editor: Bin Wen Editor: Bin Wen
<mailto:Bin_Wen@cable.comcast.com>"; <mailto:Bin_Wen@cable.comcast.com>";
description description
"This module contains the Extended RSVP YANG data model."; "This module contains the Extended RSVP YANG data model.";
revision "2016-10-29" { revision "2017-03-10" {
description "Latest revision of RSVP extended yang module."; description "Latest revision of RSVP extended yang module.";
reference "RFC2205"; reference "RFC2205";
} }
/* RSVP features */ /* RSVP features */
feature authentication { feature authentication {
description description
"Indicates support for RSVP authentication"; "Indicates support for RSVP authentication";
} }
skipping to change at page 37, line 22 skipping to change at page 42, line 36
} }
feature notify { feature notify {
description description
"Indicates support for RSVP notify message (RFC3473)."; "Indicates support for RSVP notify message (RFC3473).";
} }
feature refresh-reduction { feature refresh-reduction {
description description
"Indicates support for RSVP refresh reduction "Indicates support for RSVP refresh reduction
(RFC2961)."; (RFC2961).";
} }
feature refresh-reduction-extended { feature refresh-reduction-extended {
description description
"Indicates support for RSVP refresh reduction "Indicates support for RSVP refresh reduction
(RFC2961)."; (RFC2961).";
} }
feature per-interface-statistics { feature per-interface-statistics {
description description
"Indicates support for per interface statistics"; "Indicates support for per interface statistics";
} }
grouping graceful-restart-extended_config { grouping graceful-restart-extended_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
Graceful-Restart"; Graceful-Restart";
leaf restart-time { leaf restart-time {
type uint32; type uint32;
units seconds; units seconds;
description description
"Graceful restart time (seconds)."; "Graceful restart time (seconds).";
reference reference
"RFC 5495: Description of the Resource "RFC 5495: Description of the Resource
Reservation Protocol - Traffic-Engineered Reservation Protocol - Traffic-Engineered
(RSVP-TE) Graceful Restart Procedures"; (RSVP-TE) Graceful Restart Procedures";
} }
leaf recovery-time { leaf recovery-time {
type uint32; type uint32;
units seconds;
description description
"RSVP state recovery time"; "RSVP state recovery time";
} }
} }
grouping authentication-extended_config { grouping authentication-extended_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
authentication"; authentication";
leaf lifetime { leaf lifetime {
type uint32 { type uint32 {
range "30..86400"; range "30..86400";
} }
units seconds;
description description
"Life time for each security association"; "Life time for each security association";
reference reference
"RFC 2747: RSVP Cryptographic "RFC 2747: RSVP Cryptographic
Authentication"; Authentication";
} }
leaf window-size { leaf window-size {
type uint32 { type uint32 {
range "1..64"; range "1..64";
} }
description description
"Window-size to limit number of out-of-order "Window-size to limit number of out-of-order
messages."; messages.";
reference reference
"RFC 2747: RSVP Cryptographic "RFC 2747: RSVP Cryptographic
Authentication"; Authentication";
} }
leaf challenge { leaf challenge {
type empty; type empty;
description description
"Enable challenge messages."; "Enable challenge messages.";
reference reference
"RFC 2747: RSVP Cryptographic "RFC 2747: RSVP Cryptographic
Authentication"; Authentication";
} }
leaf retransmits { leaf retransmits {
type uint32 { type uint32 {
range "1..10000"; range "1..10000";
} }
description description
"Number of retransmits when messages are "Number of retransmits when messages are
dropped."; dropped.";
reference reference
"RFC 2747: RSVP Cryptographic "RFC 2747: RSVP Cryptographic
Authentication"; Authentication";
} }
leaf key-chain { leaf key-chain {
type string { type key-chain:key-chain-ref;
length "1..32";
}
description description
"Key chain name to authenticate RSVP "Key chain name to authenticate RSVP
signaling messages."; signaling messages.";
reference reference
"RFC 2747: RSVP Cryptographic "RFC 2747: RSVP Cryptographic
Authentication"; Authentication";
} }
} }
grouping rsvp-hellos-extended_config { grouping hellos-extended_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
hellos"; hellos";
leaf interface-based { leaf interface-based {
type empty; type empty;
description "Enable interface-based description
Hello adjacency if present."; "Enable interface-based Hello adjacency if present.";
} }
leaf hello-interval { leaf hello-interval {
type uint32; type uint32;
units milliseconds; units milliseconds;
description description
"Configure interval between successive Hello "Configure interval between successive Hello
messages in milliseconds."; messages in milliseconds.";
reference reference
"RFC 3209: RSVP-TE: Extensions to RSVP for "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels.
LSP Tunnels. RFC 5495: Description of the Resource
RFC 5495: Description of the Resource Reservation Protocol - Traffic-Engineered
Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart Procedures";
(RSVP-TE) Graceful Restart Procedures";
} }
leaf hello-misses { leaf hello-misses {
type uint32 { type uint32 {
range "1..10"; range "1..10";
} }
description description
"Configure max number of consecutive missed "Configure max number of consecutive missed
Hello messages."; Hello messages.";
reference reference
"RFC 3209: RSVP-TE: Extensions to RSVP for "RFC 3209: RSVP-TE: Extensions to RSVP for
LSP Tunnels RFC 5495: Description of the LSP Tunnels RFC 5495: Description of the
Resource Reservation Protocol - Traffic- Resource Reservation Protocol - Traffic-
Engineered (RSVP-TE) Graceful Restart Engineered (RSVP-TE) Graceful Restart
Procedures"; Procedures";
} }
} }
grouping signaling-parameters-extended_config { grouping signaling-parameters-extended_config {
description description
"Configuration parameters relating to RSVP "Configuration parameters relating to RSVP
signaling"; signaling";
leaf refresh-interval { leaf refresh-interval {
type uint32; type uint32;
description description
"Set interval between successive refreshes"; "Set interval between successive refreshes";
} }
leaf refresh-misses { leaf refresh-misses {
type uint32; type uint32;
description description
"Set max number of consecutive missed "Set max number of consecutive missed
messages for state expiry"; messages for state expiry";
} }
leaf checksum { leaf checksum {
type uint32; type boolean;
description description
"Enable RSVP message checksum computation"; "Enable RSVP message checksum computation";
} }
leaf patherr-state-removal { leaf patherr-state-removal {
type empty; type empty;
description description
"State-Removal flag in Path Error message "State-Removal flag in Path Error message
if present."; if present.";
} }
} }
skipping to change at page 41, line 37 skipping to change at page 46, line 50
leaf summary-max-size { leaf summary-max-size {
type uint32 { type uint32 {
range "20..65000"; range "20..65000";
} }
description description
"Configure max size (bytes) of a single "Configure max size (bytes) of a single
RSVP summary refresh message."; RSVP summary refresh message.";
} }
} }
grouping statistics-packets-extended_state { grouping packets-extended_state {
description description
"Packet statistics."; "Packet statistics.";
leaf discontinuity-time { leaf discontinuity-time {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which any one "The time on the most recent occasion at which any one
or more of the statistic counters suffered a or more of the statistic counters suffered a
discontinuity. If no such discontinuities have occurred discontinuity. If no such discontinuities have occurred
since the last re-initialization of the local since the last re-initialization of the local
management subsystem, then this node contains the time management subsystem, then this node contains the time
the local management subsystem re-initialized itself."; the local management subsystem re-initialized itself.";
} }
leaf tx-dropped { leaf out-dropped {
type yang:counter32; type yang:counter64;
description description
"Packet tx dropped count"; "Out packet drop count";
} }
leaf rx-dropped { leaf in-dropped {
type yang:counter32; type yang:counter64;
description description
"Packet rx dropped count"; "In packet drop count";
} }
leaf tx-error { leaf out-error {
type yang:counter32; type yang:counter64;
description description
"Packet tx error count"; "Out packet error count";
} }
leaf rx-error { leaf in-error {
type yang:counter32; type yang:counter64;
description description
"Packet rx error count"; "In packet rx error count";
} }
} }
grouping statistics-protocol-extended_state { grouping protocol-extended_state {
description description
"RSVP protocol statistics."; "RSVP protocol statistics.";
} }
grouping statistics-errors-extended_state { grouping errors-extended_state {
description description
"Error statistics."; "Error statistics.";
} }
grouping statistics-extended_state { grouping extended_state {
description "RSVP statistic attributes."; description "RSVP statistic attributes.";
uses statistics-packets-extended_state; uses packets-extended_state;
uses statistics-protocol-extended_state; uses protocol-extended_state;
uses statistics-errors-extended_state; uses errors-extended_state;
} }
/** /**
* RSVP extensions augmentations * RSVP extensions augmentations
*/ */
/* RSVP globals graceful restart*/ /* RSVP globals graceful restart*/
augment "/rt:routing/rt:control-plane-protocols/" + augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
"rsvp:config/rsvp:graceful-restart" { "rsvp:graceful-restart/rsvp:config" {
description description
"RSVP globals configuration extensions"; "RSVP globals configuration extensions";
uses graceful-restart-extended_config; uses graceful-restart-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" + augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
"rsvp:state/rsvp:graceful-restart" { "rsvp:graceful-restart/rsvp:state" {
description description
"RSVP globals state extensions"; "RSVP globals configuration extensions";
uses graceful-restart-extended_config; uses graceful-restart-extended_config;
} }
/* RSVP statistics augmentation */ /* RSVP statistics augmentation */
augment "/rt:routing/rt:control-plane-protocols/" + augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
"rsvp:state/rsvp:packets-stats" { "rsvp:statistics/rsvp:state/rsvp:packets" {
description description
"RSVP packet stats extensions"; "RSVP packet stats extensions";
uses statistics-packets-extended_state; uses packets-extended_state;
} }
augment "/rt:routing/rt:control-plane-protocols/" + augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
"rsvp:state/rsvp:protocol-stats" { "rsvp:statistics/rsvp:state/rsvp:messages" {
description description
"RSVP protocol message stats extensions"; "RSVP protocol message stats extensions";
uses statistics-protocol-extended_state; uses protocol-extended_state;
} }
augment "/rt:routing/rt:control-plane-protocols/" + augment "/rt:routing/rt:control-plane-protocols/" +
"rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" +
"rsvp:state/rsvp:errors-stats" { "rsvp:statistics/rsvp:state/rsvp:errors" {
description description
"RSVP errors stats extensions"; "RSVP errors stats extensions";
uses statistics-errors-extended_state; uses errors-extended_state;
} }
/** /**
* RSVP all interfaces extensions * RSVP all interfaces extensions
*/ */
/* RSVP interface signaling extensions */ /* RSVP interface signaling extensions */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:config" { + "rsvp:config" {
skipping to change at page 44, line 15 skipping to change at page 49, line 30
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:state" { + "rsvp:state" {
description description
"RSVP signaling all interfaces state extensions"; "RSVP signaling all interfaces state extensions";
uses signaling-parameters-extended_config; uses signaling-parameters-extended_config;
} }
/* RSVP refresh reduction extension */ /* RSVP refresh reduction extension */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:config/rsvp:refresh-reduction" { + "rsvp:refresh-reduction/rsvp:config" {
description description
"RSVP refresh-reduction all interface configuration "RSVP refresh-reduction all interface configuration
extensions"; extensions";
uses refresh-reduction-extended_config; uses refresh-reduction-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:state/rsvp:refresh-reduction" { + "rsvp:refresh-reduction/rsvp:state" {
description description
"RSVP refresh-reduction all interfaces state extensions"; "RSVP refresh-reduction all interfaces state extensions";
uses refresh-reduction-extended_config; uses refresh-reduction-extended_config;
} }
/* RSVP hellos extension */ /* RSVP hellos extension */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:config/rsvp:rsvp-hellos" { + "rsvp:hellos/rsvp:config" {
description description
"RSVP hello all interfaces configuration extensions"; "RSVP hello all interfaces configuration extensions";
uses rsvp-hellos-extended_config; uses hellos-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:state/rsvp:rsvp-hellos" { + "rsvp:hellos/rsvp:state" {
description description
"RSVP hello all interfaces state extensions"; "RSVP hello all interfaces state extensions";
uses rsvp-hellos-extended_config; uses hellos-extended_config;
} }
/* RSVP authentication extension */ /* RSVP authentication extension */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:config/rsvp:authentication" { + "rsvp:authentication/rsvp:config" {
description description
"RSVP authentication all interfaces configuration extensions"; "RSVP authentication all interfaces configuration extensions";
uses authentication-extended_config; uses authentication-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/"
+ "rsvp:state/rsvp:authentication" { + "rsvp:authentication/rsvp:state" {
description description
"RSVP authentication all interfaces state extensions"; "RSVP authentication all interfaces state extensions";
uses authentication-extended_config; uses authentication-extended_config;
} }
/** /**
* RSVP interface extensions * RSVP interface extensions
*/ */
/* RSVP interface signaling extensions */ /* RSVP interface signaling extensions */
skipping to change at page 45, line 37 skipping to change at page 50, line 50
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:state" { "rsvp:interface/rsvp:state" {
description description
"RSVP signaling interface state extensions"; "RSVP signaling interface state extensions";
uses signaling-parameters-extended_config; uses signaling-parameters-extended_config;
} }
/* RSVP refresh reduction extension */ /* RSVP refresh reduction extension */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:config/rsvp:refresh-reduction" { "rsvp:interface/rsvp:refresh-reduction/rsvp:config" {
description description
"RSVP refresh-reduction interface configuration extensions"; "RSVP refresh-reduction interface configuration extensions";
uses refresh-reduction-extended_config; uses refresh-reduction-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:state/rsvp:refresh-reduction" { "rsvp:interface/rsvp:refresh-reduction/rsvp:state" {
description description
"RSVP refresh-reduction interface state extensions"; "RSVP refresh-reduction interface state extensions";
uses refresh-reduction-extended_config; uses refresh-reduction-extended_config;
} }
/* RSVP hellos extension */ /* RSVP hellos extension */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:config/rsvp:rsvp-hellos" { "rsvp:interface/rsvp:hellos/rsvp:config" {
description description
"RSVP hello interface configuration extensions"; "RSVP hello interface configuration extensions";
uses rsvp-hellos-extended_config; uses hellos-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:state/rsvp:rsvp-hellos" { "rsvp:interface/rsvp:hellos/rsvp:state" {
description description
"RSVP hello interface state extensions"; "RSVP hello interface state extensions";
uses rsvp-hellos-extended_config; uses hellos-extended_config;
} }
/* RSVP authentication extension */ /* RSVP authentication extension */
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:config/rsvp:authentication" { "rsvp:interface/rsvp:authentication/rsvp:config" {
description description
"RSVP authentication interface configuration extensions"; "RSVP authentication interface configuration extensions";
uses authentication-extended_config; uses authentication-extended_config;
} }
augment "/rt:routing/rt:control-plane-protocols/" augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" + + "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface/rsvp:state/rsvp:authentication" { "rsvp:interface/rsvp:authentication/rsvp:state" {
description description
"RSVP authentication interface state extensions"; "RSVP authentication interface state extensions";
uses authentication-extended_config; uses authentication-extended_config;
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 4: RSVP extended YANG module Figure 5: RSVP extended YANG module
3.3. RSVP-TE Generic YANG Model
This section contains the augmentation of the RSVP base YANG model
for signalling Traffic-Engineering (RSVP-TE) Label Switched Paths
(LSPs). New module is introduced that augment the RSVP-TE generic
module to cover data items that are technology agnostic.
This model imports and augments the base RSVP YANG model (presented
in Section 3.1.3). It also imports and augments the TE YANG model
defined in [I-D.ietf-teas-yang-te] to enable configuration of RSVP-TE
attributes on TE tunnels.
The following subsections provide overview of the parts of the RSVP-
TE generic model pertaining to configuration and state data.
3.3.1. Configuration and State Data
There are three types of configuration and state data nodes in this
module:
o those augmenting or extending the base RSVP module
o those augmenting or extending the base TE generic module
o those that are specific to the RSVP-TE module
Below is a YANG tree representation for data items defined in the
RSVP-TE generic module:
module: ietf-rsvp-te
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/rsvp:rsvp/rsvp:globals:
+--rw global-soft-preemption!
+--rw config
| +--rw soft-preemption-timeout? uint16
+--rw state
+--rw soft-preemption-timeout? uint16
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/rsvp:rsvp/rsvp:interfaces:
+--rw rsvp-te-interface-attributes
+--rw config
+--ro state
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/rsvp:rsvp/rsvp:interfaces/rsvp:interface:
+--rw rsvp-te-interface-attributes
+--rw config
+--ro state
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/rsvp:rsvp/rsvp:sessions:
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/rsvp:rsvp/rsvp:neighbors:
augment /te:te/te:tunnels/te:tunnel:
+--rw config
| +--rw lsp-signaled-name? string
| +--rw local-recording-desired? boolean
| +--rw se-style-desired? boolean
| +--rw path-reevaluation-request? boolean
| +--rw soft-preemption-desired? boolean
| +--rw lsp-rerouting? enumeration
| +--rw lsp-integrety-required? boolean
| +--rw lsp-contiguous? boolean
| +--rw lsp-stitching-desired? boolean
| +--rw lsp-preplanned? boolean
| +--rw lsp-oob-mapping? boolean
+--ro state
+--ro lsp-signaled-name? string
+--ro local-recording-desired? boolean
+--ro se-style-desired? boolean
+--ro path-reevaluation-request? boolean
+--ro soft-preemption-desired? boolean
+--ro lsp-rerouting? enumeration
+--ro lsp-integrety-required? boolean
+--ro lsp-contiguous? boolean
+--ro lsp-stitching-desired? boolean
+--ro lsp-preplanned? boolean
+--ro lsp-oob-mapping? boolean
augment /te:te/te:lsps-state/te:lsp:
+--ro lsp-signaled-name? string
+--ro local-recording-desired? boolean
+--ro se-style-desired? boolean
+--ro path-reevaluation-request? boolean
+--ro soft-preemption-desired? boolean
+--ro lsp-rerouting? enumeration
+--ro lsp-integrety-required? boolean
+--ro lsp-contiguous? boolean
+--ro lsp-stitching-desired? boolean
+--ro lsp-preplanned? boolean
+--ro lsp-oob-mapping? boolean
+--ro explicit-route-object
| +--ro incoming-explicit-route-subobjects* [subobject-index]
| | +--ro subobject-index uint32
| | +--ro (type)?
| | +--:(ipv4-address)
| | | +--ro v4-address? inet:ipv4-address
| | | +--ro v4-prefix-length? uint8
| | | +--ro v4-loose? boolean
| | +--:(ipv6-address)
| | | +--ro v6-address? inet:ipv6-address
| | | +--ro v6-prefix-length? uint8
| | | +--ro v6-loose? boolean
| | +--:(as-number)
| | | +--ro as-number? uint16
| | +--:(unnumbered-link)
| | | +--ro router-id? inet:ip-address
| | | +--ro interface-id? uint32
| | +--:(label)
| | +--ro value? uint32
| +--ro outgoing-explicit-route-subobjects* [subobject-index]
| +--ro subobject-index uint32
| +--ro (type)?
| +--:(ipv4-address)
| | +--ro v4-address? inet:ipv4-address
| | +--ro v4-prefix-length? uint8
| | +--ro v4-loose? boolean
| +--:(ipv6-address)
| | +--ro v6-address? inet:ipv6-address
| | +--ro v6-prefix-length? uint8
| | +--ro v6-loose? boolean
| +--:(as-number)
| | +--ro as-number? uint16
| +--:(unnumbered-link)
| | +--ro router-id? inet:ip-address
| | +--ro interface-id? uint32
| +--:(label)
| +--ro value? uint32
+--ro record-route-object
+--ro path-record-route-subobjects* [subobject-index]
| +--ro subobject-index uint32
| +--ro (type)?
| +--:(ipv4-address)
| | +--ro v4-address? inet:ipv4-address
| | +--ro v4-prefix-length? uint8
| | +--ro v4-flags? uint8
| +--:(ipv6-address)
| | +--ro v6-address? inet:ipv6-address
| | +--ro v6-prefix-length? uint8
| | +--ro v6-flags? uint8
| +--:(unnumbered-link)
| | +--ro router-id? inet:ip-address
| | +--ro interface-id? uint32
| +--:(label)
| +--ro value? uint32
| +--ro flags? uint8
+--ro resv-record-route-subobjects* [subobject-index]
+--ro subobject-index uint32
+--ro (type)?
+--:(ipv4-address)
| +--ro v4-address? inet:ipv4-address
| +--ro v4-prefix-length? uint8
| +--ro v4-flags? uint8
+--:(ipv6-address)
| +--ro v6-address? inet:ipv6-address
| +--ro v6-prefix-length? uint8
| +--ro v6-flags? uint8
+--:(unnumbered-link)
| +--ro router-id? inet:ip-address
| +--ro interface-id? uint32
+--:(label)
+--ro value? uint32
+--ro flags? uint8
augment /te:te/te-dev:interfaces/te-dev:interface:
Figure 5: RSVP-TE YANG Tree representation
3.3.2. RPC and Notification Data
TBD.
3.3.3. YANG Module
<CODE BEGINS> file "ietf-rsvp-te@2016-10-29.yang"
module ietf-rsvp-te {
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te";
prefix "rsvp-te";
import ietf-rsvp {
prefix rsvp;
}
import ietf-routing {
prefix "rt";
}
import ietf-te {
prefix te;
}
import ietf-te-device {
prefix te-dev;
}
/* Import TE generic types */
import ietf-te-types {
prefix te-types;
}
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>
Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Xufeng Liu
<mailto:xliu@kuatrotech.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-TE YANG generic data model.";
revision "2016-10-29" {
description "Latest revision to RSVP-TE generic YANG module";
reference "RFC2205, RFC3209, etc.";
}
/**
* RSVP-TE LSPs groupings.
*/
grouping lsp-record-route-information_state {
description "recorded route information grouping";
container record-route-object {
description "RSVP recorded route object information";
list path-record-route-subobjects {
when "../../te:origin-type != 'ingress'" {
description "Applicable on non-ingress LSPs only";
}
key "subobject-index";
description
"List of RSVP Path record-route objects";
leaf subobject-index {
type uint32;
description "RRO subobject index";
}
uses te-types:record-route-subobject;
}
list resv-record-route-subobjects {
when "../../te:origin-type != 'egress'" {
description "Applicable on non-egress LSPs only";
}
key "subobject-index";
description
"List of RSVP Resv record-route objects";
leaf subobject-index {
type uint32;
description "RRO subobject index";
}
uses te-types:record-route-subobject;
}
}
}
grouping lsp-explicit-route-information_state {
description "RSVP-TE LSP explicit-route information";
container explicit-route-object {
description "Explicit route object information";
list incoming-explicit-route-subobjects {
when "../../te:origin-type != 'ingress'" {
description "Applicable on non-ingress LSPs only";
}
key "subobject-index";
description
"List of incoming RSVP Path explicit-route objects";
leaf subobject-index {
type uint32;
description "ERO subobject index";
}
uses te-types:explicit-route-subobject;
}
list outgoing-explicit-route-subobjects {
when "../../te:origin-type != 'egress'" {
description "Applicable on non-egress LSPs only";
}
key "subobject-index";
description
"List of outgoing RSVP Path explicit-route objects";
leaf subobject-index {
type uint32;
description "ERO subobject index";
}
uses te-types:explicit-route-subobject;
}
}
}
grouping lsp-attributes-flags_config {
description
"Configuration parameters relating to RSVP-TE LSP
attribute flags";
leaf lsp-rerouting {
type enumeration {
enum end-to-end-routing {
description
"End-to-end routing desired";
reference "RFC4920, RFC5420";
}
enum boundary-rerouting {
description
"Boundary rerouting desired";
reference "RFC4920, RFC5420";
}
enum segment-based-rerouting {
description
"Segment-based rerouting desired";
reference "RFC4920, RFC5420";
}
}
description "LSP rerouting types";
}
leaf lsp-integrety-required {
type boolean;
description "LSP integrity desired";
reference "RFC4875";
}
leaf lsp-contiguous {
type boolean;
description "Contiguous LSP";
reference "RFC5151";
}
leaf lsp-stitching-desired {
type boolean;
description "Stitched LSP";
reference "RFC5150";
}
leaf lsp-preplanned {
type boolean;
description "Preplanned LSP";
reference "RFC6001";
}
leaf lsp-oob-mapping {
type boolean;
description
"Mapping is done out-of-band";
reference "RFC6511";
}
}
grouping lsp-session-attributes-obj-flags_config {
description
"Configuration parameters relating to RSVP-TE LSP
session attribute flags";
reference
"RFC4859: Registry for RSVP-TE Session Flags";
leaf local-recording-desired {
type boolean;
description "Path recording is desired.";
reference "RFC3209";
}
leaf se-style-desired {
type boolean;
description "SE Style desired";
reference "RFC3209";
}
leaf path-reevaluation-request {
type boolean;
description "Path re-evaluation request";
reference "RFC4736";
}
leaf soft-preemption-desired {
type boolean;
description "Soft-preemption is desired";
reference "RFC5712";
}
}
grouping lsp-properties_config {
description
"Configuration parameters relating to RSVP-TE LSP
session attribute flags";
leaf lsp-signaled-name {
type string;
description
"Sets the session name to use in the session
attribute object.";
}
uses lsp-session-attributes-obj-flags_config;
uses lsp-attributes-flags_config;
}
grouping tunnel-properties {
description
"Top level grouping for LSP properties.";
container config {
description
"Configuration parameters relating to
LSP properties";
uses lsp-properties_config;
}
container state {
config false;
description
"State information associated with LSP
properties";
uses lsp-properties_config;
}
}
/*** End of RSVP-TE LSP groupings ***/
/**
* RSVP-TE generic global properties.
*/
grouping global-soft-preemption_config {
description
"Configuration for global RSVP-TE soft preemption";
leaf soft-preemption-timeout {
type uint16 {
range 0..300;
}
default 0;
description
"Timeout value for soft preemption to revert
to hard preemption";
}
}
grouping global-soft-preemption {
description
"Top level group for RSVP-TE soft-preemption";
container global-soft-preemption {
presence "Enables soft preemption on a node.";
description
"Top level container for RSVP-TE soft-preemption";
container config {
description
"Configuration parameters relating to RSVP
soft preemption support";
uses global-soft-preemption_config;
}
container state {
description "State parameters relating to RSVP
soft preemption support";
uses global-soft-preemption_config;
}
}
}
/*** End of RSVP-TE generic global properties. ***/
/**
* RSVP-TE interface generic groupings.
*/
grouping rsvp-te-interface-attributes {
description
"Top level grouping for RSVP-TE interface properties.";
container rsvp-te-interface-attributes {
description
"Top level container for RSVP-TE interface
properties";
container config {
description
"Configuration parameters relating to RSVP-TE
bandwidth";
}
container state {
config false;
description
"State information associated with RSVP-TE
bandwidth";
}
}
}
/*** End of RSVP-TE generic groupings ***/
/* RSVP-TE global propeerties */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals" {
description
"RSVP-TE augmentation to RSVP globals";
uses global-soft-preemption;
}
/* Linkage to the base RSVP all links */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces" {
description
"RSVP-TE generic data augmentation pertaining to interfaces";
uses rsvp-te-interface-attributes;
}
/* Linkage to per RSVP interface */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface" {
description
"RSVP-TE generic data augmentation pertaining to specific
interface";
uses rsvp-te-interface-attributes;
}
/* add augmentation for sessions neighbors */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:sessions" {
description
"RSVP-TE generic data augmentation pertaining to session";
/* To be added */
}
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors" {
description
"RSVP-TE generic data augmentation pertaining to neighbors";
/* To be added */
}
/**
* RSVP-TE generic augmentations of generic TE model.
*/
/* TE tunnel augmentation */
augment "/te:te/te:tunnels/te:tunnel" {
description
"RSVP-TE generic data augmentation pertaining to TE tunnels";
uses tunnel-properties;
}
/* TE LSP augmentation */
augment "/te:te/te:lsps-state/te:lsp" {
description
"RSVP-TE generic data augmentation pertaining to specific TE
LSP";
uses lsp-properties_config;
uses lsp-explicit-route-information_state;
uses lsp-record-route-information_state;
}
/* TE interface augmentation */
augment "/te:te/te-dev:interfaces/te-dev:interface" {
description
"RSVP-TE generic data augmentation pertaining to specific TE
interface";
}
}
<CODE ENDS>
3.4. RSVP-TE MPLS Model
This section describes the MPLS RSVP-TE YANG module that augments the
RSVP-TE generic module to signal MPLS LSPs. RSVP-TE YANG modules for
other dataplane technologies (e.g. OTN or WDM) will be defined in
separate modules and in other drafts.
The following subsections describe the configuration and state data .
pertaining to RSVP-TE MPLS YANG data model.
3.4.1. Configuration and State Data
The following are possible types of configuration and state data
nodes in this module:
o those augmenting or extending the generic RSVP-TE module
o those augmenting or extending the base TE generic module
o those that are specific to the RSVP-TE MPLS module
Below is a YANG tree representation for data items defined in the
RSVP-TE MPLS module:
module: ietf-rsvp-te-mpls
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/rsvp:rsvp:
+--rw config
| +--rw rsvp-frr-local-revert!
| +--rw rsvp-frr-local-revert-delay? uint32
+--ro state
+--ro rsvp-frr-local-revert!
+--ro rsvp-frr-local-revert-delay? uint32
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/rsvp:interface:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:sessions:
augment /rt:routing/rt:control-plane-protocols/
rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors:
augment /te:te/te:tunnels/te:tunnel:
+--rw config
| +--rw static-bandwidth? uint32
| +--rw auto-bandwidth
| | +--rw enabled? boolean
| | +--rw min-bw? uint32
| | +--rw max-bw? uint32
| | +--rw adjust-interval? uint32
| | +--rw adjust-threshold? uint32
| | +--rw overflow
| | | +--rw enabled? boolean
| | | +--rw overflow-threshold? uint32
| | | +--rw trigger-event-count? uint16
| | +--rw underflow
| | +--rw enabled? boolean
| | +--rw underflow-threshold? uint32
| | +--rw trigger-event-count? uint16
| +--rw local-protection-desired? empty
| +--rw bandwidth-protection-desired? empty
| +--rw node-protection-desired? empty
| +--rw non-php-desired? empty
| +--rw entropy-label-cap? empty
| +--rw oam-mep-entities-desired? empty
| +--rw oam-mip-entities-desired? empty
+--rw state
+--rw static-bandwidth? uint32
+--rw auto-bandwidth
| +--rw enabled? boolean
| +--rw min-bw? uint32
| +--rw max-bw? uint32
| +--rw adjust-interval? uint32
| +--rw adjust-threshold? uint32
| +--rw overflow
| | +--rw enabled? boolean
| | +--rw overflow-threshold? uint32
| | +--rw trigger-event-count? uint16
| +--rw underflow
| +--rw enabled? boolean
| +--rw underflow-threshold? uint32
| +--rw trigger-event-count? uint16
+--rw local-protection-desired? empty
+--rw bandwidth-protection-desired? empty
+--rw node-protection-desired? empty
+--rw non-php-desired? empty
+--rw entropy-label-cap? empty
+--rw oam-mep-entities-desired? empty
+--rw oam-mip-entities-desired? empty
augment /te:te/te:lsps-state/te:lsp:
+--ro static-bandwidth? uint32
+--ro auto-bandwidth
| +--ro enabled? boolean
| +--ro min-bw? uint32
| +--ro max-bw? uint32
| +--ro adjust-interval? uint32
| +--ro adjust-threshold? uint32
| +--ro overflow
| | +--ro enabled? boolean
| | +--ro overflow-threshold? uint32
| | +--ro trigger-event-count? uint16
| +--ro underflow
| +--ro enabled? boolean
| +--ro underflow-threshold? uint32
| +--ro trigger-event-count? uint16
+--ro local-protection-desired? empty
+--ro bandwidth-protection-desired? empty
+--ro node-protection-desired? empty
+--ro non-php-desired? empty
+--ro entropy-label-cap? empty
+--ro oam-mep-entities-desired? empty
+--ro oam-mip-entities-desired? empty
+--ro backup-info
+--ro backup-tunnel-name? string
+--ro backup-frr-on? uint8
+--ro backup-protected-lsp-num? uint32
augment /te:te/te-dev:interfaces/te-dev:interface:
+--rw config
| +--rw (bandwidth-value)?
| | +--:(absolute)
| | | +--rw absolute-value? uint32
| | +--:(precentage)
| | +--rw percent-value? uint32
| +--rw (bc-model-type)?
| +--:(bc-model-rdm)
| | +--rw bc-model-rdm
| | +--rw bandwidth-mpls-constraints
| | +--rw maximum-reservable? uint32
| | +--rw bc-value* uint32
| +--:(bc-model-mam)
| | +--rw bc-model-mam
| | +--rw bandwidth-mpls-constraints
| | +--rw maximum-reservable? uint32
| | +--rw bc-value* uint32
| +--:(bc-model-mar)
| +--rw bc-model-mar
| +--rw bandwidth-mpls-constraints
| +--rw maximum-reservable? uint32
| +--rw bc-value* uint32
+--ro state
| +--ro (bandwidth-value)?
| | +--:(absolute)
| | | +--ro absolute-value? uint32
| | +--:(precentage)
| | +--ro percent-value? uint32
| +--ro (bc-model-type)?
| | +--:(bc-model-rdm)
| | | +--ro bc-model-rdm
| | | +--ro bandwidth-mpls-constraints
| | | +--ro maximum-reservable? uint32
| | | +--ro bc-value* uint32
| | +--:(bc-model-mam)
| | | +--ro bc-model-mam
| | | +--ro bandwidth-mpls-constraints
| | | +--ro maximum-reservable? uint32
| | | +--ro bc-value* uint32
| | +--:(bc-model-mar)
| | +--ro bc-model-mar
| | +--ro bandwidth-mpls-constraints
| | +--ro maximum-reservable? uint32
| | +--ro bc-value* uint32
| +--ro interface-softpreemption-state
| | +--ro soft-preempted-bandwidth? uint32
| | +--ro lsps*
[source destination tunnel-id lsp-id extended-tunnel-id]
| | +--ro source -> /te:te/lsps-state/lsp/source
| | +--ro destination -> /te:te/lsps-state/lsp/destination
| | +--ro tunnel-id -> /te:te/lsps-state/lsp/tunnel-id
| | +--ro lsp-id -> /te:te/lsps-state/lsp/lsp-id
| | +--ro extended-tunnel-id
-> /te:te/lsps-state/lsp/extended-tunnel-id
| | +--ro type? -> /te:te/lsps-state/lsp/type
| +--ro over-subscribed-bandwidth? uint32
+--rw rsvp-te-frr-backups {te-types:frr-te}?
+--rw config
| +--rw backup-bandwidth? uint32
| +--rw backup-bandwidth-classtype? uint32
| +--rw (type)?
| +--:(static-tunnel)
| | +--rw static-backups* [tunnel-name]
| | +--rw tunnel-name string
| +--:(auto-tunnel)
| +--rw auto-backup-protection? identityref
| +--rw auto-backup-path-computation? identityref
+--ro state
+--ro backup-bandwidth? uint32
+--ro backup-bandwidth-classtype? uint32
+--ro (type)?
+--:(static-tunnel)
| +--ro static-backups* [tunnel-name]
| +--ro tunnel-name string
+--:(auto-tunnel)
+--ro auto-backup-protection? identityref
Figure 6: MPLS RSVP-TE YANG Tree representation
3.4.2. RPC and Notification Data
TBD.
3.4.3. YANG Module
<CODE BEGINS> file "ietf-rsvp-te-mpls@2016-10-29.yang"
module ietf-rsvp-te-mpls {
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls";
prefix "rsvp-te-mpls";
import ietf-rsvp {
prefix "rsvp";
}
import ietf-routing {
prefix "rt";
}
import ietf-te-mpls-types {
prefix "te-mpls-types";
}
import ietf-te-types {
prefix "te-types";
}
import ietf-te {
prefix "te";
}
import ietf-te-device {
prefix "te-dev";
}
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>
Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com>
Editor: Himanshu Shah
<mailto:hshah@ciena.com>
Editor: Xufeng Liu
<mailto:xliu@kuatrotech.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
"Latest update to MPLS RSVP-TE YANG data model.";
revision "2016-10-29" {
description "Update to MPLS RSVP-TE YANG initial revision.";
reference "RFC3209, RFC6511, RFC6790, RFC7260, RFC4859, RFC4090";
}
/* RSVP-TE MPLS LSPs groupings */
grouping lsp-attributes-flags-mpls_config {
description
"Configuration parameters relating to RSVP-TE MPLS LSP
attribute flags";
leaf non-php-desired {
type empty;
description
"Non-PHP is desired";
reference "RFC6511";
}
leaf entropy-label-cap {
type empty;
description "Entropy label capability";
reference "RFC6790";
}
leaf oam-mep-entities-desired {
type empty;
description "OAM MEP entities desired";
reference "RFC7260";
}
leaf oam-mip-entities-desired {
type empty;
description "OAM MIP entities desired";
reference "RFC7260";
}
}
grouping lsp-session-attributes-obj-flags-mpls_config {
description
"Configuration parameters relating to RSVP-TE MPLS LSP
session attribute flags";
reference
"RFC4859: Registry for RSVP-TE Session Flags";
leaf local-protection-desired {
type empty;
description "Fastreroute local protection is desired.";
reference
"RFC4859: Registry for RSVP-TE Session Flags";
}
leaf bandwidth-protection-desired {
type empty;
description
"Request FRR bandwidth protection on LSRs if
present.";
reference "RFC4090";
}
leaf node-protection-desired {
type empty;
description
"Request FRR node protection on LSRs if
present.";
reference "RFC4090";
}
}
grouping lsp-overflow_config {
description "configuration for mpls lsp bandwidth
overflow adjustment";
leaf enabled {
type boolean;
default false;
description "enables mpls lsp bandwidth overflow
adjustment on the lsp";
}
leaf overflow-threshold {
type uint32;
description "bandwidth percentage change to trigger
an overflow event";
}
leaf trigger-event-count {
type uint16;
description "number of consecutive overflow sample
events needed to trigger an overflow adjustment";
}
}
grouping lsp-underflow_config {
description
"configuration for mpls lsp bandwidth
underflow adjustment";
leaf enabled {
type boolean;
default false;
description "enables bandwidth underflow
adjustment on the lsp";
}
leaf underflow-threshold {
type uint32;
description "bandwidth percentage change to trigger
and underflow event";
}
leaf trigger-event-count {
type uint16;
description "number of consecutive underflow sample
events needed to trigger an underflow adjustment";
}
}
grouping lsp-auto-bandwidth_config {
description
"Auto-Bandwidth grouping";
container auto-bandwidth {
description "configure auto-bandwidth operation in
which devices automatically adjust bandwidth to meet
requirements";
leaf enabled {
type boolean;
default false;
description "enables mpls auto-bandwidth on the
lsp";
}
leaf min-bw {
type uint32;
description "set the minimum bandwidth in Mbps for an
auto-bandwidth LSP";
}
leaf max-bw {
type uint32;
description "set the maximum bandwidth in Mbps for an
auto-bandwidth LSP";
}
leaf adjust-interval {
type uint32;
description "time in seconds between adjustments to
LSP bandwidth";
}
leaf adjust-threshold {
type uint32;
description "percentage difference between the LSP's
specified bandwidth and its current bandwidth
allocation -- if the difference is greater than the
specified percentage, auto-bandwidth adjustment is
triggered";
}
container overflow {
description "configuration of MPLS overflow bandwidth
adjustement for the LSP";
uses lsp-overflow_config;
}
container underflow {
description "configuration of MPLS underflow bandwidth
adjustement for the LSP";
uses lsp-underflow_config;
}
}
}
grouping lsp-bandwidth_config {
description
"LSP bandwidth grouping";
leaf static-bandwidth {
type uint32;
description
"Static bandwidth, e.g., using
offline calculation";
}
uses lsp-auto-bandwidth_config;
}
grouping tunnel-properties-mpls {
description
"Top level grouping for LSP properties.";
container config {
description
"Configuration parameters for tunnel RSVP-TE
properties";
uses lsp-bandwidth_config;
uses lsp-session-attributes-obj-flags-mpls_config;
uses lsp-attributes-flags-mpls_config;
}
container state {
description
"State parameters for tunnel RSVP-TE
properties";
uses lsp-bandwidth_config;
uses lsp-session-attributes-obj-flags-mpls_config;
uses lsp-attributes-flags-mpls_config;
}
}
grouping lsp-properties-mpls {
description
"Top level grouping for LSP properties.";
uses lsp-bandwidth_config;
uses lsp-session-attributes-obj-flags-mpls_config;
uses lsp-attributes-flags-mpls_config;
}
/* End of RSVP-TE MPLS LSPs groupings */
/* MPLS RSVP-TE interface groupings */
grouping rsvp-te-interface_state {
description
"The RSVP-TE interface state grouping";
leaf over-subscribed-bandwidth {
type uint32;
description
"The amount of over-subscribed bandwidth on
the interface";
}
}
grouping rsvp-te-interface-softpreemption_state {
description
"The RSVP-TE interface preeemptions state grouping";
container interface-softpreemption-state {
description
"The RSVP-TE interface preeemptions state grouping";
leaf soft-preempted-bandwidth {
type uint32;
description
"The amount of soft-preempted bandwidth on
this interface";
}
list lsps {
key
"source destination tunnel-id lsp-id "+
"extended-tunnel-id";
description
"List of LSPs that are soft-preempted";
leaf source {
type leafref {
path "/te:te/te:lsps-state/te:lsp/"+
"te:source";
}
description
"Tunnel sender address extracted from
SENDER_TEMPLATE object";
reference "RFC3209";
}
leaf destination {
type leafref {
path "/te:te/te:lsps-state/te:lsp/"+
"te:destination";
}
description
"Tunnel endpoint address extracted from
SESSION object";
reference "RFC3209";
}
leaf tunnel-id {
type leafref {
path "/te:te/te:lsps-state/te:lsp/"+
"te:tunnel-id";
}
description
"Tunnel identifier used in the SESSION
that remains constant over the life
of the tunnel.";
reference "RFC3209";
}
leaf lsp-id {
type leafref {
path "/te:te/te:lsps-state/te:lsp/"+
"te:lsp-id";
}
description
"Identifier used in the SENDER_TEMPLATE
and the FILTER_SPEC that can be changed
to allow a sender to share resources with
itself.";
reference "RFC3209";
}
leaf extended-tunnel-id {
type leafref {
path "/te:te/te:lsps-state/te:lsp/"+
"te:extended-tunnel-id";
}
description
"Extended Tunnel ID of the LSP.";
reference "RFC3209";
}
leaf type {
type leafref {
path "/te:te/te:lsps-state/te:lsp/"+
"te:type";
}
description "LSP type P2P or P2MP";
}
}
}
}
/* End of RSVP-TE interface groupings */
/* RSVP-TE FRR groupings */
grouping rsvp-te-frr-backups_config {
description
"Top level container for RSVP-TE FRR backup parameters";
leaf backup-bandwidth {
type uint32;
description
"Maximum bandwidth this facility backup
is allowed to protect";
}
leaf backup-bandwidth-classtype {
type uint32;
description
"Type of primary LSP bandwidth that the
backup is allowed to protect.";
}
choice type {
description
"FRR backup tunnel type";
case static-tunnel {
list static-backups {
key "tunnel-name";
description
"List of static backup tunnels that
protect the RSVP-TE interface.";
leaf tunnel-name {
type string;
description "FRR Backup tunnel";
}
}
}
case auto-tunnel {
leaf auto-backup-protection {
type identityref {
base te-mpls-types:backup-protection-type;
}
default
te-mpls-types:backup-protection-node-link;
description
"Describes whether the backup should offer
protection against link, node, or either";
}
leaf auto-backup-path-computation {
type identityref {
base
te-types:path-computation-srlg-type;
}
description
"FRR backup computation type";
}
}
}
}
grouping rsvp-te-frr-backups {
description
"Top level grouping for RSVP-TE FRR backup properties.";
container rsvp-te-frr-backups {
if-feature te-types:frr-te;
description
"Top level container for RSVP-TE FRR backup
properties.";
container config {
description
"Configuration parameters for interface RSVP-TE
FRR backup properties";
uses rsvp-te-frr-backups_config;
}
container state {
config false;
description
"State parameters for interface RSVP-TE
FRR backup properties";
uses rsvp-te-frr-backups_config;
}
}
}
grouping lps-backup-info_state {
description "Backup/bypass LSP related information";
container backup-info {
description
"backup information";
leaf backup-tunnel-name {
type string;
description
"If an LSP has an FRR backup LSP that can protect it,
this field identifies the tunnel name of the backup LSP.
Otherwise, this field is empty.";
}
leaf backup-frr-on {
type uint8;
description
"Whether currently this backup is carrying traffic";
}
leaf backup-protected-lsp-num {
type uint32;
description
"Number of LSPs protected by this backup";
}
}
}
grouping rsvp-frr-local-revert_config {
description "RSVP-TE FRR local revertive grouping";
container rsvp-frr-local-revert {
presence "Enable RSVP FRR local revertive recovery
mode.";
description
"RSVP-TE FRR local revertive container";
leaf rsvp-frr-local-revert-delay {
type uint32;
description
"Time to wait after primary link is restored
before node attempts local revertive
procedures.";
}
}
}
/*** End of RSVP-TE FRR backup information ***/
grouping globals-properties {
description
"Top level grouping for globals properties";
container config {
description
"Configuration parameters relating to
global MPLS RSVP-TE properties";
uses rsvp-frr-local-revert_config;
}
container state {
config false;
description
"State parameters relating to
global MPLS RSVP-TE properties";
uses rsvp-frr-local-revert_config;
}
}
/* RSVP-TE global propeerties */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp" {
description
"RSVP-TE augmentation to RSVP globals";
uses globals-properties;
}
grouping rsvp-te-interface-attributes-mpls {
description
"Top level grouping for MPLS RSVP-TE interface
properties.";
container config {
description
"Configuration parameters relating to RSVP-TE
bandwidth";
uses te-mpls-types:bandwidth-mpls-reservable;
}
container state {
config false;
description
"State information associated with RSVP-TE
bandwidth";
uses te-mpls-types:bandwidth-mpls-reservable;
uses rsvp-te-interface-softpreemption_state;
uses rsvp-te-interface_state;
}
}
/* Linkage to the base RSVP all interfaces */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces" {
description
"Augmentations for RSVP-TE MPLS all interfaces properties";
/* To be added */
}
/* Linkage to per RSVP interface */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:interfaces/" +
"rsvp:interface" {
description
"Augmentations for RSVP-TE MPLS per interface properties";
/* To be added */
}
/* add augmentation for sessions neighbors */
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:sessions" {
description
"Augmentations for RSVP-TE MPLS sessions";
/* To be added */
}
augment "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:neighbors" {
description
"Augmentations for RSVP-TE MPLS neighbors properties";
/* To be added */
}
/**
* Augmentation to TE generic module
*/
augment "/te:te/te:tunnels/te:tunnel" {
description
"Augmentations for RSVP-TE MPLS TE tunnel properties";
uses tunnel-properties-mpls;
}
augment "/te:te/te:lsps-state/te:lsp" {
description
"RSVP-TE MPLS LSP state properties";
uses lsp-properties-mpls;
uses lps-backup-info_state;
}
augment "/te:te/te-dev:interfaces/te-dev:interface" {
description
"RSVP reservable bandwidth configuration properties";
uses rsvp-te-interface-attributes-mpls;
uses rsvp-te-frr-backups;
}
}
<CODE ENDS>
4. IANA Considerations 4. IANA Considerations
This document registers the following URIs in the IETF XML registry This document registers the following URIs in the IETF XML registry
[RFC3688]. Following the format in [RFC3688], the following [RFC3688]. Following the format in [RFC3688], the following
registration is requested to be made. registration is requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-rsvp XML: N/A, the requested URI: urn:ietf:params:xml:ns:yang:ietf-rsvp XML: N/A, the requested
URI is an XML namespace. URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-te XML: N/A, the requested URI: urn:ietf:params:xml:ns:yang:ietf-rsvp-extended XML: N/A, the
URI is an XML namespace. requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names This document registers a YANG module in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-rsvp namespace: urn:ietf:params:xml:ns:yang:ietf-rsvp name: ietf-rsvp namespace: urn:ietf:params:xml:ns:yang:ietf-rsvp
prefix: ietf-rsvp reference: RFC3209 prefix: ietf-rsvp reference: RFC3209
name: ietf-rsvp-te namespace: urn:ietf:params:xml:ns:yang:ietf-rsvp- name: ietf-rsvp-extended namespace: urn:ietf:params:xml:ns:yang:ietf-
te prefix: ietf-rsvp-te reference: RFC3209 rsvp-extended prefix: ietf-rsvp-extendeed reference: RFC3209
5. Security Considerations 5. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The NETCONF access control model transport is SSH [RFC6242]. The NETCONF access control model
[RFC6536] provides means to restrict access for particular NETCONF [RFC6536] provides means to restrict access for particular NETCONF
users to a pre-configured subset of all available NETCONF protocol users to a pre-configured subset of all available NETCONF protocol
skipping to change at page 76, line 11 skipping to change at page 52, line 46
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., <edit-config>) in some network environments. Write operations (e.g., <edit-config>)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. effect on network operations.
6. Acknowledgement 6. Acknowledgement
The authors would like to thank Lou Berger for reviewing and The authors would like to thank Lou Berger, for reviewing and
providing valuable feedback on this document. providing valuable feedback on this document.
7. References 7. Contributors
7.1. Normative References Xia Chen
Huawei Technologies
[I-D.ietf-netmod-routing-cfg] Email: jescia.chenxia@huawei.com
Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", draft-ietf-netmod-routing-cfg-24 (work in
progress), October 2016.
[I-D.ietf-teas-yang-te] Raqib Jones
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., Brocade
Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data
Model for Traffic Engineering Tunnels and Interfaces", Email: raqib@Brocade.com
draft-ietf-teas-yang-te-05 (work in progress), October
2016. 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 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, DOI 10.17487/RFC2205, Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
September 1997, <http://www.rfc-editor.org/info/rfc2205>. September 1997, <http://www.rfc-editor.org/info/rfc2205>.
skipping to change at page 77, line 48 skipping to change at page 54, line 43
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, DOI Protocol (NETCONF) Access Control Model", RFC 6536, DOI
10.17487/RFC6536, March 2012, 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>. <http://www.rfc-editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC
6991, DOI 10.17487/RFC6991, July 2013, 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
7.2. Informative References [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, November
2016, <http://www.rfc-editor.org/info/rfc8022>.
8.2. Informative References
[I-D.openconfig-mpls-consolidated-model] [I-D.openconfig-mpls-consolidated-model]
George, J., Fang, L., eric.osborne@level3.com, e., and R. George, J., Fang, L., eric.osborne@level3.com, e., and R.
Shakir, "MPLS / TE Model for Service Provider Networks", Shakir, "MPLS / TE Model for Service Provider Networks",
draft-openconfig-mpls-consolidated-model-02 (work in draft-openconfig-mpls-consolidated-model-02 (work in
progress), October 2015. progress), October 2015.
[I-D.openconfig-netmod-opstate] [I-D.openconfig-netmod-opstate]
Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling
of Operational State Data in YANG", draft-openconfig- of Operational State Data in YANG", draft-openconfig-
netmod-opstate-01 (work in progress), July 2015. netmod-opstate-01 (work in progress), July 2015.
Authors' Addresses Authors' Addresses
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
Email: vbeeram@juniper.net Email: vbeeram@juniper.net
Tarek Saad (editor) Tarek Saad (editor)
Cisco Systems Inc Cisco Systems, Inc.
Email: tsaad@cisco.com Email: tsaad@cisco.com
Rakesh Gandhi Rakesh Gandhi
Cisco Systems Inc Cisco Systems, Inc.
Email: rgandhi@cisco.com Email: rgandhi@cisco.com
Xufeng Liu Xufeng Liu
Ericsson Jabil
Email: xliu@kuatrotech.com
Himanshu Shah
Ciena
Email: hshah@ciena.com Email: Xufeng_Liu@jabil.com
Xia Chen Igor Bryskin
Huawei Technologies Huawei Technologies
Email: jescia.chenxia@huawei.com Email: Igor.Bryskin@huawei.com
Raqib Jones
Brocade
Email: raqib@Brocade.com
Bin Wen Himanshu Shah
Comcast Ciena
Email: Bin_Wen@cable.comcast.com Email: hshah@ciena.com
 End of changes. 223 change blocks. 
2233 lines changed or deleted 1118 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/