draft-ietf-rtgwg-yang-vrrp-11.txt   rfc8347.txt 
Network Working Group X. Liu, Ed. Internet Engineering Task Force (IETF) X. Liu, Ed.
Internet-Draft A. Kyparlis Request for Comments: 8347 A. Kyparlis
Intended status: Standards Track Jabil Category: Standards Track Jabil
Expires: August 26, 2018 R. Parikh ISSN: 2070-1721 R. Parikh
VMware VMware
A. Lindem A. Lindem
Cisco Systems Cisco Systems
M. Zhang M. Zhang
Huawei Technologies Huawei Technologies
February 22, 2018 March 2018
A YANG Data Model for Virtual Router Redundancy Protocol (VRRP) A YANG Data Model for the Virtual Router Redundancy Protocol (VRRP)
draft-ietf-rtgwg-yang-vrrp-11
Abstract Abstract
This document describes a data model for Virtual Router Redundancy This document describes a data model for the Virtual Router
Protocol (VRRP). Both version 2 and version 3 of VRRP are covered. Redundancy Protocol (VRRP). Both versions 2 and 3 of VRRP are
covered.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on August 26, 2018. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8347.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 (https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction ....................................................2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology ................................................2
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams ..............................................3
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 1.3. Prefixes in Data Node Names ................................3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3 2. Design of the Data Model ........................................3
2.1. Scope of the Model . . . . . . . . . . . . . . . . . . . 3 2.1. Scope of the Model .........................................3
2.2. Relations with Interface Model and IP Model . . . . . . . 4 2.2. Relationships with the Interface Model and IP Model ........4
2.3. Protocol Configuration . . . . . . . . . . . . . . . . . 5 2.3. Protocol Configuration .....................................5
2.4. Protocol States . . . . . . . . . . . . . . . . . . . . . 6 2.4. Protocol States ............................................6
2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 8 2.5. Notifications ..............................................9
3. Tree Structure . . . . . . . . . . . . . . . . . . . . . . . 10 3. Tree Structure .................................................10
4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 12 4. YANG Module ....................................................13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 5. IANA Considerations ............................................35
6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 6. Security Considerations ........................................36
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 7. References .....................................................37
7.1. Normative References . . . . . . . . . . . . . . . . . . 36 7.1. Normative References ......................................37
7.2. Informative References . . . . . . . . . . . . . . . . . 38 7.2. Informative References ....................................38
Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 39 Appendix A. Data Tree Example .....................................40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 Authors' Addresses ................................................45
1. Introduction 1. Introduction
This document introduces a YANG [RFC6020][RFC7950] data model for This document introduces a YANG data model [RFC6020] [RFC7950] for
Virtual Router Redundancy Protocol (VRRP) [RFC3768] [RFC5798]. VRRP the Virtual Router Redundancy Protocol (VRRP) [RFC3768] [RFC5798].
provides higher resiliency by specifying an election protocol that VRRP provides higher resiliency by specifying an election protocol
dynamically assigns responsibility for a virtual router to one of the that dynamically assigns responsibility for a virtual router to one
VRRP routers on a LAN. of the VRRP routers on a LAN.
This YANG model supports both version 2 and version 3 of VRRP. VRRP The YANG module specified in this document supports both versions 2
version 2 defined in [RFC3768] supports IPv4. VRRP version 3 defined and 3 of VRRP. VRRP version 2 (defined in [RFC3768]) supports IPv4.
in [RFC5798] supports both IPv4 and IPv6. VRRP version 3 (defined in [RFC5798]) supports both IPv4 and IPv6.
1.1. Terminology 1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The following terms are defined in [RFC7950] and are not redefined The following terms are defined in [RFC7950] and are not redefined
here: here:
o augment o augment
o data model o data model
o data node o data node
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is this document. The meaning of the symbols in these diagrams is
defined in [I-D.ietf-netmod-yang-tree-diagrams]. defined in [RFC8340].
1.3. Prefixes in Data Node Names 1.3. Prefixes in Data Node Names
In this document, names of data nodes, actions, and other data model In this document, names of data nodes, actions, and other data model
objects are often used without a prefix, as long as it is clear from objects are often used without a prefix, as long as it is clear from
the context in which YANG module each name is defined. Otherwise, the context in which YANG module each name is defined. Otherwise,
names are prefixed using the standard prefix associated with the names are prefixed using the standard prefix associated with the
corresponding YANG module, as shown in Table 1. corresponding YANG module, 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] |
| if | ietf-interfaces | [I-D.ietf-netmod-rfc7223bis] | | if | ietf-interfaces | [RFC8343] |
| ip | ietf-ip | [I-D.ietf-netmod-rfc7277bis] | | ip | ietf-ip | [RFC8344] |
+--------+-----------------+------------------------------+ +--------+-----------------+-----------+
Table 1: Prefixes and Corresponding YANG Modules Table 1: Prefixes and Corresponding YANG Modules
2. Design of the Data Model 2. Design of the Data Model
2.1. Scope of the Model 2.1. Scope of the Model
The model covers VRRP version 2 [RFC3768] and VRRP version 3 The model covers VRRP version 2 [RFC3768] and VRRP version 3
[RFC5798] protocols. The model is designed to be implemented on a [RFC5798]. The model is designed to be implemented on a device where
device where VRRP version 2 or version 3 is implemented. With the VRRP version 2 or 3 is implemented. With the help of a proper
help of a proper management protocol, the defined model can be used management protocol, the defined model can be used to:
to:
o Configure the VRRP version 2 or version 3 protocol. o Configure VRRP version 2 or 3.
o Manage the protocol operational behavior. o Manage the protocol operational behavior.
o Retrieve the protocol operational status. o Retrieve the protocol operational status.
o Receive the protocol notifications. o Receive the protocol notifications.
2.2. Relations with Interface Model and IP Model 2.2. Relationships with the Interface Model and IP Model
This model augments the interface data model "ietf-interfaces" This model augments the interface data model "ietf-interfaces"
[I-D.ietf-netmod-rfc7223bis] and the IP management model "ietf-ip" [RFC8343] and the IP management model "ietf-ip" [RFC8344]. The
[I-D.ietf-netmod-rfc7277bis]. The augmentation relations are shown augmentation relationships are shown as follows:
as follows:
module: ietf-interfaces module: ietf-interfaces
+--rw interfaces +--rw interfaces
+--rw interface* [name] +--rw interface* [name]
... ...
+--rw ip:ipv4! +--rw ip:ipv4!
| +--rw ip:address* [ip] | +--rw ip:address* [ip]
... ...
| +--rw vrrp:vrrp | +--rw vrrp:vrrp
| +--rw vrrp:vrrp-instance* [vrid] | +--rw vrrp:vrrp-instance* [vrid]
skipping to change at page 4, line 42 skipping to change at page 4, line 45
In the above figure, a tree node without a prefix is from the model In the above figure, a tree node without a prefix is from the model
"ietf-interfaces". A tree node with prefix "ip:" is from the model "ietf-interfaces". A tree node with prefix "ip:" is from the model
"ietf-ip". A tree node with prefix "vrrp:" is from the VRRP model "ietf-ip". A tree node with prefix "vrrp:" is from the VRRP model
specified in this document. specified in this document.
The "vrrp" container contains a list of vrrp-instance nodes, which The "vrrp" container contains a list of vrrp-instance nodes, which
are instantiated under an interface for a specified address family are instantiated under an interface for a specified address family
(IPv4 or IPv6). (IPv4 or IPv6).
Each vrrp-instance node represents a VRRP router state machine Each vrrp-instance node represents a VRRP router state machine, as
described in Section 6.4 of [RFC5798], providing the configuration described in Section 6.4 of [RFC5798], providing the configuration
and state information for the election process of a virtual router. and state information for the election process of a virtual router.
The IP addresses on the augmented interface are the real addresses The IP addresses on the augmented interface are the real addresses
through which the VRRP router operates. The IPv4 or IPv6 address(es) through which the VRRP router operates. The IPv4 or IPv6 address or
associated with a virtual router (described in Section 1 of addresses associated with a virtual router (described in Section 1 of
[RFC5798]) are modeled as a list of IPv4 or IPv6 addresses under the [RFC5798]) are modeled as a list of IPv4 or IPv6 addresses under the
vrrp-instance. vrrp-instance.
2.3. Protocol Configuration 2.3. Protocol Configuration
The model structure for the protocol configuration is as shown below: The model structure for the protocol configuration is as shown below:
augment /if:interfaces/if:interface/ip:ipv4: augment /if:interfaces/if:interface/ip:ipv4:
+--rw vrrp +--rw vrrp
+--rw vrrp-instance* [vrid] +--rw vrrp-instance* [vrid]
skipping to change at page 5, line 45 skipping to change at page 6, line 5
| | +--rw interface if:interface-ref | | +--rw interface if:interface-ref
| | ... | | ...
| +--rw networks | +--rw networks
| +--rw network* [prefix] | +--rw network* [prefix]
| +--rw prefix inet:ipv6-prefix | +--rw prefix inet:ipv6-prefix
| ... | ...
+--rw virtual-ipv6-addresses +--rw virtual-ipv6-addresses
+--rw virtual-ipv6-address* [ipv6-address] +--rw virtual-ipv6-address* [ipv6-address]
+--rw ipv6-address inet:ipv6-address +--rw ipv6-address inet:ipv6-address
The model allows to configure the following protocol entities: The model allows the following protocol entities to be configured:
o VRRP instance (version 2 or version 3), representing a VRRP o VRRP instance (version 2 or 3), representing a VRRP router.
router.
o Virtual IPv4 or IPv6 address associated with a virtual router. o Virtual IPv4 or IPv6 address associated with a virtual router.
o Tracking interface, to detect interface connectivity failures. o Tracking interface, to detect interface connectivity failures.
o Tracking network, to detect interface connectivity failures. o Tracking network, to detect network connectivity failures.
2.4. Protocol States 2.4. Protocol States
The model structure for the protocol states is as shown below: The model structure for the protocol states is as shown below:
module: ietf-vrrp module: ietf-vrrp
+--ro vrrp +--ro vrrp
| // global operational states | // global operational states
+--ro virtual-routers? uint32 +--ro virtual-routers? uint32
+--ro interfaces? uint32 +--ro interfaces? uint32
skipping to change at page 6, line 39 skipping to change at page 7, line 4
| ... | ...
+--rw track +--rw track
| +--rw interfaces | +--rw interfaces
| | +--rw interface* [interface] | | +--rw interface* [interface]
| | +--rw interface if:interface-ref | | +--rw interface if:interface-ref
| | ... | | ...
| +--rw networks | +--rw networks
| +--rw network* [prefix] | +--rw network* [prefix]
| +--rw prefix inet:ipv4-prefix | +--rw prefix inet:ipv4-prefix
| ... | ...
+--rw virtual-ipv4-addresses +--rw virtual-ipv4-addresses
| +--rw virtual-ipv4-address* [ipv4-address] | +--rw virtual-ipv4-address* [ipv4-address]
| +--rw ipv4-address inet:ipv4-address | +--rw ipv4-address inet:ipv4-address
| |
| // per instance operational states | // per-instance operational states
+--ro state? identityref +--ro state? identityref
+--ro is-owner? boolean +--ro is-owner? boolean
+--ro last-adv-source? inet:ip-address +--ro last-adv-source? inet:ip-address
+--ro up-datetime? yang:date-and-time +--ro up-datetime? yang:date-and-time
+--ro master-down-interval? uint32 +--ro master-down-interval? uint32
+--ro skew-time? uint32 +--ro skew-time? uint32
+--ro last-event? identityref +--ro last-event? identityref
+--ro new-master-reason? new-master-reason-type +--ro new-master-reason? new-master-reason-type
+--ro statistics // per instance statistics +--ro statistics // per-instance statistics
+--ro discontinuity-datetime? yang:date-and-time +--ro discontinuity-datetime? yang:date-and-time
+--ro master-transitions? yang:counter32 +--ro master-transitions? yang:counter32
+--ro advertisement-recv? yang:counter64 +--ro advertisement-rcvd? yang:counter64
+--ro advertisement-sent? yang:counter64 +--ro advertisement-sent? yang:counter64
+--ro interval-errors? yang:counter64 +--ro interval-errors? yang:counter64
| {validate-interval-errors}? | {validate-interval-errors}?
+--ro priority-zero-pkts-rcvd? yang:counter64 +--ro priority-zero-pkts-rcvd? yang:counter64
+--ro priority-zero-pkts-sent? yang:counter64 +--ro priority-zero-pkts-sent? yang:counter64
+--ro invalid-type-pkts-rcvd? yang:counter64 +--ro invalid-type-pkts-rcvd? yang:counter64
+--ro address-list-errors? yang:counter64 +--ro address-list-errors? yang:counter64
| {validate-address-list-errors}? | {validate-address-list-errors}?
+--ro packet-length-errors? yang:counter64 +--ro packet-length-errors? yang:counter64
skipping to change at page 7, line 36 skipping to change at page 8, line 4
| | +--rw interface if:interface-ref | | +--rw interface if:interface-ref
| | ... | | ...
| +--rw networks | +--rw networks
| +--rw network* [prefix] | +--rw network* [prefix]
| +--rw prefix inet:ipv6-prefix | +--rw prefix inet:ipv6-prefix
| ... | ...
+--rw virtual-ipv6-addresses +--rw virtual-ipv6-addresses
| +--rw virtual-ipv6-address* [ipv6-address] | +--rw virtual-ipv6-address* [ipv6-address]
| +--rw ipv6-address inet:ipv6-address | +--rw ipv6-address inet:ipv6-address
| |
| // per instance operational states | // per-instance operational states
+--ro state? identityref +--ro state? identityref
+--ro is-owner? boolean +--ro is-owner? boolean
+--ro last-adv-source? inet:ip-address +--ro last-adv-source? inet:ip-address
+--ro up-datetime? yang:date-and-time +--ro up-datetime? yang:date-and-time
+--ro master-down-interval? uint32 +--ro master-down-interval? uint32
+--ro skew-time? uint32 +--ro skew-time? uint32
+--ro last-event? identityref +--ro last-event? identityref
+--ro new-master-reason? new-master-reason-type +--ro new-master-reason? new-master-reason-type
+--ro statistics // per instance statistics +--ro statistics // per-instance statistics
+--ro discontinuity-datetime? yang:date-and-time +--ro discontinuity-datetime? yang:date-and-time
+--ro master-transitions? yang:counter32 +--ro master-transitions? yang:counter32
+--ro advertisement-recv? yang:counter64 +--ro advertisement-rcvd? yang:counter64
+--ro advertisement-sent? yang:counter64 +--ro advertisement-sent? yang:counter64
+--ro interval-errors? yang:counter64 +--ro interval-errors? yang:counter64
| {validate-interval-errors}? | {validate-interval-errors}?
+--ro priority-zero-pkts-rcvd? yang:counter64 +--ro priority-zero-pkts-rcvd? yang:counter64
+--ro priority-zero-pkts-sent? yang:counter64 +--ro priority-zero-pkts-sent? yang:counter64
+--ro invalid-type-pkts-rcvd? yang:counter64 +--ro invalid-type-pkts-rcvd? yang:counter64
+--ro address-list-errors? yang:counter64 +--ro address-list-errors? yang:counter64
| {validate-address-list-errors}? | {validate-address-list-errors}?
+--ro packet-length-errors? yang:counter64 +--ro packet-length-errors? yang:counter64
This model conforms to the Network Management Datastore Architecture This model conforms to the Network Management Datastore Architecture
(NMDA) [I-D.ietf-netmod-revised-datastores]. The operational state (NMDA) [RFC8342]. The operational state data is combined with the
data is combined with the associated configuration data in the same associated configuration data in the same hierarchy
hierarchy [I-D.ietf-netmod-rfc6087bis]. When protocol states are [YANG-Guidelines]. When protocol states are retrieved from the NMDA
retrieved from the NMDA operational state datastore, the returned operational state datastore, the returned states cover all
states cover all "config true" (rw) and "config false" (ro) nodes "config true" (rw) and "config false" (ro) nodes defined in the
defined in the schema. schema.
The model allows to retrieve protocol states at the following levels: The model allows the retrieval of protocol states at the following
levels:
o VRRP instance (version 2 or version 3), representing a VRRP o VRRP instance (version 2 or 3), representing a VRRP router.
router.
o Virtual IPv4 or IPv6 address associated with a virtual router. o Virtual IPv4 or IPv6 address associated with a virtual router.
o Tracking interface, to detect interface connectivity failures. o Tracking interface, to detect interface connectivity failures.
o Tracking network, to detect interface connectivity failures. o Tracking network, to detect network connectivity failures.
o Global states and statistics summarizing all instances. o Global states and statistics summarizing all instances.
2.5. Notifications 2.5. Notifications
This model defines the following VRRP specific notifications: This model defines the following VRRP-specific notifications:
notifications: notifications:
+---n vrrp-new-master-event +---n vrrp-new-master-event
| +--ro master-ip-address inet:ip-address | +--ro master-ip-address inet:ip-address
| +--ro new-master-reason new-master-reason-type | +--ro new-master-reason new-master-reason-type
+---n vrrp-protocol-error-event +---n vrrp-protocol-error-event
| +--ro protocol-error-reason identityref | +--ro protocol-error-reason identityref
+---n vrrp-virtual-router-error-event +---n vrrp-virtual-router-error-event
+--ro interface if:interface-ref +--ro interface if:interface-ref
+--ro (ip-version) +--ro (ip-version)
| +--:(ipv4) | +--:(ipv4)
| | +--ro ipv4 | | +--ro ipv4
| | +--ro vrid leafref | | +--ro vrid leafref
| +--:(ipv6) | +--:(ipv6)
| +--ro ipv6 | +--ro ipv6
| +--ro vrid leafref | +--ro vrid leafref
+--ro virtual-router-error-reason identityref +--ro virtual-router-error-reason identityref
Each notification type is used to indicate a type of VRRP state Each notification type is used to indicate a type of VRRP state
changes or error occurances: change or error occurrence:
vrrp-new-master-event vrrp-new-master-event
VRRP new master event, indicating that a new master has been VRRP new master event, indicating that a new master has been
elected. elected.
vrrp-protocol-error-event vrrp-protocol-error-event
VRRP protocol error event for a message that fails to reach a VRRP VRRP protocol error event for a message that fails to reach a VRRP
instance to be processed. instance to be processed.
vrrp-virtual-router-error-event vrrp-virtual-router-error-event
VRRP virtual router error event for a message processed on a VRRP VRRP virtual router error event for a message processed on a VRRP
instance. instance.
In addition to the notifications specified above, the mechanism In addition to the notifications specified above, the mechanisms
defined in [I-D.ietf-netconf-subscribed-notifications] and defined in [Subscribed-Notifications] and [YANG-Push] can be used for
[I-D.ietf-netconf-yang-push] can be used for other general other general notifications. These mechanisms currently allow the
notifications. This mechanism currently allows the user to: user to:
o Subscribe notifications on a per client basis. o Subscribe notifications on a per-client basis.
o Specify subtree filters or xpath filters so that only interested o Specify subtree filters or XML Path Language (XPath) filters so
contents will be sent. that only contents of interest will be sent.
o Specify either periodic or on-demand notifications. o Specify either periodic or on-demand notifications.
3. Tree Structure 3. Tree Structure
The VRRP YANG data model defined in this document has the following The VRRP YANG data model defined in this document has the following
tree structure: tree structure:
module: ietf-vrrp module: ietf-vrrp
+--ro vrrp +--ro vrrp
skipping to change at page 11, line 11 skipping to change at page 11, line 11
+--ro last-adv-source? inet:ip-address +--ro last-adv-source? inet:ip-address
+--ro up-datetime? yang:date-and-time +--ro up-datetime? yang:date-and-time
+--ro master-down-interval? uint32 +--ro master-down-interval? uint32
+--ro skew-time? uint32 +--ro skew-time? uint32
+--ro last-event? identityref +--ro last-event? identityref
+--ro new-master-reason? +--ro new-master-reason?
new-master-reason-type new-master-reason-type
+--ro statistics +--ro statistics
+--ro discontinuity-datetime? yang:date-and-time +--ro discontinuity-datetime? yang:date-and-time
+--ro master-transitions? yang:counter32 +--ro master-transitions? yang:counter32
+--ro advertisement-recv? yang:counter64 +--ro advertisement-rcvd? yang:counter64
+--ro advertisement-sent? yang:counter64 +--ro advertisement-sent? yang:counter64
+--ro interval-errors? yang:counter64 +--ro interval-errors? yang:counter64
| {validate-interval-errors}? | {validate-interval-errors}?
+--ro priority-zero-pkts-rcvd? yang:counter64 +--ro priority-zero-pkts-rcvd? yang:counter64
+--ro priority-zero-pkts-sent? yang:counter64 +--ro priority-zero-pkts-sent? yang:counter64
+--ro invalid-type-pkts-rcvd? yang:counter64 +--ro invalid-type-pkts-rcvd? yang:counter64
+--ro address-list-errors? yang:counter64 +--ro address-list-errors? yang:counter64
| {validate-address-list-errors}? | {validate-address-list-errors}?
+--ro packet-length-errors? yang:counter64 +--ro packet-length-errors? yang:counter64
augment /if:interfaces/if:interface/ip:ipv6: augment /if:interfaces/if:interface/ip:ipv6:
skipping to change at page 12, line 9 skipping to change at page 12, line 11
+--ro last-adv-source? inet:ip-address +--ro last-adv-source? inet:ip-address
+--ro up-datetime? yang:date-and-time +--ro up-datetime? yang:date-and-time
+--ro master-down-interval? uint32 +--ro master-down-interval? uint32
+--ro skew-time? uint32 +--ro skew-time? uint32
+--ro last-event? identityref +--ro last-event? identityref
+--ro new-master-reason? +--ro new-master-reason?
new-master-reason-type new-master-reason-type
+--ro statistics +--ro statistics
+--ro discontinuity-datetime? yang:date-and-time +--ro discontinuity-datetime? yang:date-and-time
+--ro master-transitions? yang:counter32 +--ro master-transitions? yang:counter32
+--ro advertisement-recv? yang:counter64 +--ro advertisement-rcvd? yang:counter64
+--ro advertisement-sent? yang:counter64 +--ro advertisement-sent? yang:counter64
+--ro interval-errors? yang:counter64 +--ro interval-errors? yang:counter64
| {validate-interval-errors}? | {validate-interval-errors}?
+--ro priority-zero-pkts-rcvd? yang:counter64 +--ro priority-zero-pkts-rcvd? yang:counter64
+--ro priority-zero-pkts-sent? yang:counter64 +--ro priority-zero-pkts-sent? yang:counter64
+--ro invalid-type-pkts-rcvd? yang:counter64 +--ro invalid-type-pkts-rcvd? yang:counter64
+--ro address-list-errors? yang:counter64 +--ro address-list-errors? yang:counter64
| {validate-address-list-errors}? | {validate-address-list-errors}?
+--ro packet-length-errors? yang:counter64 +--ro packet-length-errors? yang:counter64
skipping to change at page 12, line 39 skipping to change at page 13, line 7
| +--:(ipv4) | +--:(ipv4)
| | +--ro ipv4 | | +--ro ipv4
| | +--ro vrid leafref | | +--ro vrid leafref
| +--:(ipv6) | +--:(ipv6)
| +--ro ipv6 | +--ro ipv6
| +--ro vrid leafref | +--ro vrid leafref
+--ro virtual-router-error-reason identityref +--ro virtual-router-error-reason identityref
4. YANG Module 4. YANG Module
This module references [RFC2787], [RFC3768], [RFC5798] and [RFC6527]. This module references [RFC2787], [RFC3768], [RFC5798], and
[RFC6527].
<CODE BEGINS> file "ietf-vrrp@2018-03-13.yang"
<CODE BEGINS> file "ietf-vrrp@2018-01-09.yang"
module ietf-vrrp { module ietf-vrrp {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-vrrp"; namespace "urn:ietf:params:xml:ns:yang:ietf-vrrp";
prefix "vrrp"; prefix "vrrp";
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
} }
import ietf-ip { import ietf-ip {
prefix "ip"; prefix "ip";
skipping to change at page 13, line 23 skipping to change at page 13, line 40
prefix "ip"; prefix "ip";
} }
organization organization
"IETF Routing Area Working Group (RTGWG)"; "IETF Routing Area Working Group (RTGWG)";
contact contact
"WG Web: <https://datatracker.ietf.org/wg/rtgwg/> "WG Web: <https://datatracker.ietf.org/wg/rtgwg/>
WG List: <mailto:rtgwg@ietf.org> WG List: <mailto:rtgwg@ietf.org>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:Xufeng_Liu@jabil.com> <mailto:xufeng.liu.ietf@gmail.com>
Editor: Athanasios Kyparlis Editor: Athanasios Kyparlis
<mailto:Athanasios_Kyparlis@jabil.com> <mailto:Athanasios_Kyparlis@jabil.com>
Editor: Ravi Parikh Editor: Ravi Parikh
<mailto:parikhr@vmware.com> <mailto:parikhr@vmware.com>
Editor: Acee Lindem Editor: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Editor: Mingui Zhang Editor: Mingui Zhang
<mailto:zhangmingui@huawei.com>"; <mailto:zhangmingui@huawei.com>";
description description
skipping to change at page 13, line 39 skipping to change at page 14, line 7
<mailto:parikhr@vmware.com> <mailto:parikhr@vmware.com>
Editor: Acee Lindem Editor: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Editor: Mingui Zhang Editor: Mingui Zhang
<mailto:zhangmingui@huawei.com>"; <mailto:zhangmingui@huawei.com>";
description description
"This YANG module defines a model for managing Virtual Router "This YANG module defines a model for managing Virtual Router
Redundancy Protocol (VRRP) version 2 and version 3. Redundancy Protocol (VRRP) versions 2 and 3.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC 8347; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2018-01-09 { revision 2018-03-13 {
description "Initial revision"; description
"Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Virtual Router Redundancy "RFC 8347: A YANG Data Model for the Virtual Router Redundancy
Protocol (VRRP). Protocol (VRRP)
RFC 2787: Definitions of Managed Objects for the Virtual RFC 2787: Definitions of Managed Objects for the Virtual
Router Redundancy Protocol. Router Redundancy Protocol
RFC 3768: Virtual Router Redundancy Protocol (VRRP). RFC 3768: Virtual Router Redundancy Protocol (VRRP)
RFC 5798: Virtual Router Redundancy Protocol (VRRP) Version 3. RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6
RFC 6527: Definitions of Managed Objects for the Virtual RFC 6527: Definitions of Managed Objects for the Virtual
Router Redundancy Protocol Version 3 (VRRPv3)."; Router Redundancy Protocol Version 3 (VRRPv3)";
} }
/* /*
* Features * Features
*/ */
feature validate-interval-errors { feature validate-interval-errors {
description description
"This feature indicates that the system validates that "This feature indicates that the system validates that the
the advertisement interval from advertisement packets advertisement interval from advertisement packets received
received is the same as the one configured for the local is the same as the interval configured for the local
VRRP router."; VRRP router.";
} }
feature validate-address-list-errors { feature validate-address-list-errors {
description description
"This feature indicates that the system validates that "This feature indicates that the system validates that
the address list from received packets matches the the address list from received packets matches the
locally configured list for the VRRP router."; locally configured list for the VRRP router.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef new-master-reason-type { typedef new-master-reason-type {
type enumeration { type enumeration {
enum not-master { enum not-master {
description description
"The virtual router has never transitioned to master "The virtual router has never transitioned to master
state,"; state.";
} }
enum priority { enum priority {
description "Priority was higher."; description
"Priority was higher.";
} }
enum preempted { enum preempted {
description "The master was preempted."; description
"The master was preempted.";
} }
enum no-response { enum no-response {
description "Previous master did not respond."; description
"Previous master did not respond.";
} }
} }
description description
"The reason for the virtual router to transition to master "Indicates why the virtual router has transitioned to
state."; master state.";
} // new-master-reason-type } // new-master-reason-type
/* /*
* Identities * Identities
*/ */
/* vrrp-event-type identity and its derivatives. */ /* vrrp-event-type identity and its derivatives. */
identity vrrp-event-type { identity vrrp-event-type {
description description
"The type to indicate the type of a VRRP protocol event."; "Indicates the type of a VRRP protocol event.";
} }
identity vrrp-event-none { identity vrrp-event-none {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates a non-meaningful event."; "Indicates a non-meaningful event.";
} }
identity vrrp-event-startup { identity vrrp-event-startup {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that a VRRP router has initiated the protocol."; "Indicates that a VRRP router has initiated the protocol.";
skipping to change at page 16, line 7 skipping to change at page 16, line 27
} }
identity vrrp-event-master-timeout { identity vrrp-event-master-timeout {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the current master has not sent an "Indicates that the current master has not sent an
advertisement within the limit of master-down-interval."; advertisement within the limit of master-down-interval.";
} }
identity vrrp-event-interface-up { identity vrrp-event-interface-up {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the VRRP enabled interface has become "Indicates that the VRRP-enabled interface has become
operational up."; 'operational up'.";
} }
identity vrrp-event-interface-down { identity vrrp-event-interface-down {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the VRRP enabled interface has become "Indicates that the VRRP-enabled interface has become
operational down."; 'operational down'.";
} }
identity vrrp-event-no-primary-ip-address { identity vrrp-event-no-primary-ip-address {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the primary IP address on the VRRP enabled "Indicates that the primary IP address on the VRRP-enabled
interface has become unavailable."; interface has become unavailable.";
} }
identity vrrp-event-primary-ip-address { identity vrrp-event-primary-ip-address {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the primary IP address on the VRRP enabled "Indicates that the primary IP address on the VRRP-enabled
interface has become available."; interface has become available.";
} }
identity vrrp-event-no-virtual-ip-addresses { identity vrrp-event-no-virtual-ip-addresses {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that there are no virtual IP addresses on the "Indicates that there are no virtual IP addresses on the
virtual router."; virtual router.";
} }
identity vrrp-event-virtual-ip-addresses { identity vrrp-event-virtual-ip-addresses {
base vrrp-event-type; base vrrp-event-type;
skipping to change at page 16, line 49 skipping to change at page 17, line 21
} }
identity vrrp-event-preempt-hold-timeout { identity vrrp-event-preempt-hold-timeout {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the configured preemption hold time has "Indicates that the configured preemption hold time has
passed."; passed.";
} }
identity vrrp-event-lower-priority-master { identity vrrp-event-lower-priority-master {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that there is a lower priority VRRP master."; "Indicates that there is a lower-priority VRRP master.";
} }
identity vrrp-event-owner-preempt { identity vrrp-event-owner-preempt {
base vrrp-event-type; base vrrp-event-type;
description description
"Indicates that the owner has preempted another router to "Indicates that the owner has preempted another router to
become the master."; become the master.";
} }
/* vrrp-error-global identity and its derivatives. */ /* vrrp-error-global identity and its derivatives. */
identity vrrp-error-global { identity vrrp-error-global {
description description
"The type to indicate the type of a VRRP error that occurs "Indicates the type of a VRRP error that occurred
for a packet before it reaches a VRRP router."; for a packet before it reaches a VRRP router.";
} }
identity checksum-error { identity checksum-error {
base vrrp-error-global; base vrrp-error-global;
description description
"A packet has been received with an invalid VRRP checksum "A packet has been received with an invalid VRRP checksum
value."; value.";
} }
identity ip-ttl-error { identity ip-ttl-error {
base vrrp-error-global; base vrrp-error-global;
skipping to change at page 17, line 37 skipping to change at page 18, line 9
} }
identity version-error { identity version-error {
base vrrp-error-global; base vrrp-error-global;
description description
"A packet has been received with an unknown or unsupported "A packet has been received with an unknown or unsupported
version number."; version number.";
} }
identity vrid-error { identity vrid-error {
base vrrp-error-global; base vrrp-error-global;
description description
"A packet has been received with a VRID that is not valid "A packet has been received with a Virtual Router Identifier
for any virtual router on this router."; (VRID) that is not valid for any virtual router on this
router.";
} }
/* vrrp-error-virtual-router identity and its derivatives. */ /* vrrp-error-virtual-router identity and its derivatives. */
identity vrrp-error-virtual-router { identity vrrp-error-virtual-router {
description description
"The type to indicate the type of a VRRP error that occurs "Indicates the type of a VRRP error that occurred
after a packet reaches a VRRP router."; after a packet reaches a VRRP router.";
} }
identity address-list-error { identity address-list-error {
base vrrp-error-virtual-router; base vrrp-error-virtual-router;
description description
"A packet has been received with an address list that "A packet has been received with an address list that
does not match the locally configured address list for does not match the locally configured address list for
the virtual router."; the virtual router.";
} }
identity interval-error { identity interval-error {
base vrrp-error-virtual-router; base vrrp-error-virtual-router;
description description
"A packet has been received with an advertisement "A packet has been received with an advertisement interval
interval different than the one configured for the local different than the interval configured for the local
virtual router"; virtual router.";
} }
identity packet-length-error { identity packet-length-error {
base vrrp-error-virtual-router; base vrrp-error-virtual-router;
description description
"A packet has been received with a packet length less "A packet has been received with a packet length less
than the length of the VRRP header."; than the length of the VRRP header.";
} }
/* vrrp-state-type identity and its derivatives. */ /* vrrp-state-type identity and its derivatives. */
identity vrrp-state-type { identity vrrp-state-type {
description description
"The type to indicate the state of a virtual router."; "Indicates the state of a virtual router.";
} }
identity initialize { identity initialize {
base vrrp-state-type; base vrrp-state-type;
description description
"Indicates that the virtual router is waiting "Indicates that the virtual router is waiting
for a startup event."; for a startup event.";
} }
identity backup { identity backup {
base vrrp-state-type; base vrrp-state-type;
description description
skipping to change at page 18, line 48 skipping to change at page 19, line 21
base vrrp-state-type; base vrrp-state-type;
description description
"Indicates that the virtual router is forwarding "Indicates that the virtual router is forwarding
packets for IP addresses that are associated with packets for IP addresses that are associated with
this virtual router."; this virtual router.";
} }
/* vrrp-version identity and its derivatives. */ /* vrrp-version identity and its derivatives. */
identity vrrp-version { identity vrrp-version {
description description
"The version of the VRRP protocol."; "The version of VRRP.";
} }
identity vrrp-v2 { identity vrrp-v2 {
base vrrp-version; base vrrp-version;
description description
"Indicates version 2 of the VRRP protocol."; "Indicates version 2 of VRRP.";
} }
identity vrrp-v3 { identity vrrp-v3 {
base vrrp-version; base vrrp-version;
description description
"Indicates version 3 of the VRRP protocol."; "Indicates version 3 of VRRP.";
} }
/* /*
* Groupings * Groupings
*/ */
grouping vrrp-common-attributes { grouping vrrp-common-attributes {
description description
"Group of VRRP attributes common to version 2 and version 3"; "Group of VRRP attributes common to versions 2 and 3.";
leaf vrid { leaf vrid {
type uint8 { type uint8 {
range 1..255; range "1..255";
} }
description "Virtual router ID."; description
"Virtual Router ID (i.e., VRID).";
} }
leaf version { leaf version {
type identityref { type identityref {
base vrrp:vrrp-version; base vrrp:vrrp-version;
} }
mandatory true; mandatory true;
description "Version 2 or version 3 of VRRP."; description
"Version 2 or 3 of VRRP.";
} }
leaf log-state-change { leaf log-state-change {
type boolean; type boolean;
default "false"; default "false";
description description
"Generates VRRP state change messages each time the VRRP "Generates VRRP state change messages each time the
instance changes state (from up to down or down to up)."; VRRP instance changes state (from 'up' to 'down'
or 'down' to 'up').";
} }
container preempt { container preempt {
description description
"Enables a higher priority Virtual Router Redundancy "Enables a higher-priority VRRP backup router to preempt a
Protocol (VRRP) backup router to preempt a lower priority lower-priority VRRP master.";
VRRP master.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default "true"; default "true";
description description
"'true' if preemption is enabled."; "'true' if preemption is enabled.";
} }
leaf hold-time { leaf hold-time {
type uint16; type uint16;
units seconds; units seconds;
default 0; default 0;
description description
"Hold time, in seconds, for which a higher priority VRRP "Hold time, in seconds, for which a higher-priority VRRP
backup router must wait before preempting a lower priority backup router must wait before preempting a lower-priority
VRRP master."; VRRP master.";
} }
} }
leaf priority { leaf priority {
type uint8 { type uint8 {
range 1..254; range "1..254";
} }
default 100; default 100;
description description
"Configures the Virtual Router Redundancy Protocol (VRRP) "Configures the VRRP election priority for the backup
election priority for the backup virtual router."; virtual router.";
} }
leaf accept-mode { leaf accept-mode {
when "derived-from-or-self(current()/../version, 'vrrp-v3')" { when "derived-from-or-self(current()/../version, 'vrrp-v3')" {
description "Applicable only to version 3."; description
"Applicable only to version 3.";
} }
type boolean; type boolean;
default "false"; default "false";
description description
"Controls whether a virtual router in Master state will "Controls whether a virtual router in master state will
accept packets addressed to the address owner's IPvX address accept packets addressed to the address owner's IPvX address
as its own if it is not the IPvX address owner. The default as its own if it is not the IPvX address owner. The default
is false. Deployments that rely on, for example, pinging the is 'false'. Deployments that rely on, for example, pinging
address owner's IPvX address may wish to configure the address owner's IPvX address may wish to configure
accept-mode to true. accept-mode to 'true'.
Note: IPv6 Neighbor Solicitations and Neighbor Note: IPv6 Neighbor Solicitations and Neighbor
Advertisements MUST NOT be dropped when accept-mode is Advertisements MUST NOT be dropped when accept-mode
false."; is 'false'.";
} }
} // vrrp-common-attributes } // vrrp-common-attributes
grouping vrrp-ipv4-attributes { grouping vrrp-ipv4-attributes {
description description
"Group of VRRP attributes for IPv4."; "Group of VRRP attributes for IPv4.";
uses vrrp-common-attributes; uses vrrp-common-attributes;
choice advertise-interval-choice { choice advertise-interval-choice {
description description
"The options for the advertisement interval at which VRRPv2 "The options for the advertisement interval at which VRRPv2
or VRRPv3 advertisements are sent from the specified or VRRPv3 advertisements are sent from the specified
interface."; interface.";
case v2 { case v2 {
when "derived-from-or-self(version, 'vrrp-v2')" { when "derived-from-or-self(version, 'vrrp-v2')" {
description "Applicable only to version 2."; description
"Applicable only to version 2.";
} }
leaf advertise-interval-sec { leaf advertise-interval-sec {
type uint8 { type uint8 {
range 1..254; range "1..254";
} }
units seconds; units seconds;
default 1; default 1;
description description
"Configures the interval that Virtual Router "Configures the interval that VRRPv2 advertisements
Redundancy Protocol Version 2 (VRRPv2) advertisements
are sent from the specified interface."; are sent from the specified interface.";
} }
} }
case v3 { case v3 {
when "derived-from-or-self(version, 'vrrp-v3')" { when "derived-from-or-self(version, 'vrrp-v3')" {
description "Applicable only to version 3."; description
"Applicable only to version 3.";
} }
leaf advertise-interval-centi-sec { leaf advertise-interval-centi-sec {
type uint16 { type uint16 {
range 1..4095; range "1..4095";
} }
units centiseconds; units centiseconds;
default 100; default 100;
description description
"Configures the interval that Virtual Router "Configures the interval that VRRPv3 advertisements
Redundancy Protocol version 3 (VRRPv3) advertisements
are sent from the specified interface."; are sent from the specified interface.";
} }
} }
} // advertise-interval-choice } // advertise-interval-choice
container track { container track {
description description
"Enables the specified VRRP instance to track interfaces "Enables the specified VRRP instance to track interfaces
or networks."; or networks.";
container interfaces { container interfaces {
description description
"Enables the specified Virtual Router Redundancy Protocol "Enables the specified VRRPv2 or VRRPv3 instance to track
version 2 (VRRP) or version 3 (VRRPv3) instance to track interfaces. Interface tracking prevents traffic loss by
interfaces. detecting the availability of interfaces. The operational
Interface tracking prevents traffic loss by detecting the states of other interfaces are associated with the
availability of interfaces. The operational states of priority of a VRRP router. When a tracked interface
other interfaces are associated with the priority of a becomes unavailable (or 'operational down'), the priority
VRRP router. When a tracked interface becomes unavailable of the VRRP router decrements. When an unavailable
(or operational down), the priority of the backup router interface becomes available again, the priority of the
decrements. When an unavailable interface becomes VRRP router is incremented by the same amount.";
available again, the priority of the backup VRRP router is
incremented by the same amount.";
list interface { list interface {
key "interface"; key "interface";
description description
"Interface to track."; "Interface to track.";
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name=current()]/" must "/if:interfaces/if:interface[if:name=current()]/"
+ "ip:ipv4" { + "ip:ipv4" {
description "Interface is IPv4."; description
"Interface is IPv4.";
} }
description description
"Interface to track."; "Interface to track.";
} }
leaf priority-decrement { leaf priority-decrement {
type uint8 { type uint8 {
range 1..254; range "1..254";
} }
default 10; default 10;
description description
"Specifies how much to decrement the priority of the "Specifies how much to decrement the priority of the
VRRP instance if the interface goes down."; VRRP instance if the interface goes down.";
} }
} // interface } // interface
} // interfaces } // interfaces
container networks { container networks {
description description
"Enables the backup Virtual Router Redundancy Protocol "Enables the VRRPv2 or VRRPv3 router instance to track the
version 2 (VRRP) or version 3 (VRRPv3) router to track specified networks through their IPv4 network prefixes.
specified networks through the IP network prefixes of
these networks.
Network tracking prevents traffic loss by detecting Network tracking prevents traffic loss by detecting
network connectivity failure. The states of connectivity network connectivity failure. The states of
to some networks are associated with the priority of a connectivity to some networks are associated with the
VRRP router. When connectivity to a tracked network priority of a VRRP router. When connectivity to a
represented by its prefix is lost, the priority of the tracked network represented by its prefix is lost, the
backup VRRP router decrements. When an unavailable network priority of the VRRP router decrements. When an
is again reachable, the priority of the backup VRRP router unavailable network is again reachable, the priority of
is incremented by the same amount."; the VRRP router is incremented by the same amount.";
list network { list network {
key "prefix"; key "prefix";
description description
"Enables the specified Virtual Router Redundancy "Enables the specified VRRPv2 or VRRPv3 instance to
Protocol version 2 (VRRP) or version 3 (VRRPv3) track an IPv4 network by specifying the prefix of the
instance to track an IP network, by specifying the IPv4 network.";
prefix of the IP network.";
leaf prefix { leaf prefix {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"The prefix of the network to track."; "The IPv4 prefix of the network to track.";
} }
leaf priority-decrement { leaf priority-decrement {
type uint8 { type uint8 {
range 1..254; range "1..254";
} }
default 10; default 10;
description description
"Specifies how much to decrement the priority of the "Specifies how much to decrement the priority of the
backup VRRP router if there is a failure in the IP VRRP router if there is a failure in the IPv4
network."; network.";
} }
} // track-network } // network
} // track-networks
} // networks
} // track } // track
container virtual-ipv4-addresses { container virtual-ipv4-addresses {
description description
"Configures the virtual IP address for the Virtual Router "Configures the virtual IPv4 address for the
Redundancy Protocol (VRRP) interface."; VRRP interface.";
list virtual-ipv4-address { list virtual-ipv4-address {
key "ipv4-address"; key "ipv4-address";
max-elements 16; max-elements 16;
description description
"Virtual IP addresses for a single VRRP instance. For a "Virtual IPv4 addresses for a single VRRP instance. For a
VRRP owner router, the virtual address must match one VRRP owner router, the virtual address must match one
of the IP addresses configured on the interface of the IPv4 addresses configured on the interface
corresponding to the virtual router."; corresponding to the virtual router.";
leaf ipv4-address { leaf ipv4-address {
type inet:ipv4-address; type inet:ipv4-address;
description description
"An IPv4 address associated with a virtual router."; "An IPv4 address associated with a virtual router.";
reference reference
"RFC 5798: Virtual Router Redundancy Protocol (VRRP) "RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3. Section 1.2."; Version 3 for IPv4 and IPv6. Section 1.2";
} }
} // virtual-ipv4-address } // virtual-ipv4-address
} // virtual-ipv4-addresses } // virtual-ipv4-addresses
} // grouping vrrp-ipv4-attributes } // vrrp-ipv4-attributes
grouping vrrp-ipv6-attributes { grouping vrrp-ipv6-attributes {
description description
"Group of VRRP attributes for IPv6."; "Group of VRRP attributes for IPv6.";
uses vrrp-common-attributes; uses vrrp-common-attributes;
leaf advertise-interval-centi-sec { leaf advertise-interval-centi-sec {
type uint16 { type uint16 {
range 1..4095; range "1..4095";
} }
units centiseconds; units centiseconds;
default 100; default 100;
description description
"Configures the interval that Virtual Router "Configures the interval that VRRPv3 advertisements
Redundancy Protocol version 3 (VRRPv3) advertisements
are sent from the specified interface."; are sent from the specified interface.";
} }
container track { container track {
description description
"Enables the specified VRRP instance to track interfaces "Enables the specified VRRP instance to track interfaces
or networks."; or networks.";
container interfaces { container interfaces {
description description
"Enables the specified Virtual Router Redundancy Protocol "Enables the specified VRRPv2 or VRRPv3 instance to track
version 2 (VRRP) or version 3 (VRRPv3) instance to track interfaces. Interface tracking prevents traffic loss by
interfaces. detecting the availability of interfaces. The operational
Interface tracking prevents traffic loss by detecting the states of other interfaces are associated with the
availability of interfaces. The operational states of priority of a VRRP router. When a tracked interface
other interfaces are associated with the priority of a becomes unavailable (or 'operational down'), the priority
VRRP router. When a tracked interface becomes unavailable of the VRRP router decrements. When an unavailable
(or operational down), the priority of the backup router interface becomes available again, the priority of the
decrements. When an unavailable interface becomes VRRP router is incremented by the same amount.";
available again, the priority of the backup VRRP router is
incremented by the same amount.";
list interface { list interface {
key "interface"; key "interface";
description description
"Interface to track."; "Interface to track.";
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name=current()]/" must "/if:interfaces/if:interface[if:name=current()]/"
+ "ip:ipv6" { + "ip:ipv6" {
description "Interface is IPv6."; description
"Interface is IPv6.";
} }
description description
"Interface to track."; "Interface to track.";
} }
leaf priority-decrement { leaf priority-decrement {
type uint8 { type uint8 {
range 1..254; range "1..254";
} }
default 10; default 10;
description description
"Specifies how much to decrement the priority of the "Specifies how much to decrement the priority of the
VRRP instance if the interface goes down."; VRRP instance if the interface goes down.";
} }
} // interface } // interface
} // interfaces } // interfaces
container networks { container networks {
description description
"Enables the backup Virtual Router Redundancy Protocol "Enables the VRRPv2 or VRRPv3 router instance to track the
version 2 (VRRP) or version 3 (VRRPv3) router to track specified networks through their IPv6 network prefixes.
specified networks through the IP network prefixes of
these networks.
Network tracking prevents traffic loss by detecting Network tracking prevents traffic loss by detecting
network connectivity failure. The states of connectivity network connectivity failure. The states of
to some networks are associated with the priority of a connectivity to some networks are associated with the
VRRP router. When connectivity to a tracked network priority of a VRRP router. When connectivity to a
represented by its prefix is lost, the priority of the tracked network represented by its prefix is lost, the
backup VRRP router decrements. When an unavailable network priority of the VRRP router decrements. When an
is again reachable, the priority of the backup VRRP router unavailable network is again reachable, the priority of
is incremented by the same amount."; the VRRP router is incremented by the same amount.";
list network { list network {
key "prefix"; key "prefix";
description description
"Enables the specified Virtual Router Redundancy "Enables the specified VRRPv2 or VRRPv3 instance to
Protocol version 2 (VRRP) or version 3 (VRRPv3) track an IPv6 network by specifying the prefix of the
instance to track an IP network, by specifying the IPv6 network.";
prefix of the IP network.";
leaf prefix { leaf prefix {
type inet:ipv6-prefix; type inet:ipv6-prefix;
description description
"The prefix of the network to track."; "The IPv6 prefix of the network to track.";
} }
leaf priority-decrement { leaf priority-decrement {
type uint8 { type uint8 {
range 1..254; range "1..254";
} }
default 10; default 10;
description description
"Specifies how much to decrement the priority of the "Specifies how much to decrement the priority of the
backup VRRP router if there is a failure in the IP VRRP router if there is a failure in the IPv6
network."; network.";
} }
} // track-network } // network
} // track-networks } // networks
} // track } // track
container virtual-ipv6-addresses { container virtual-ipv6-addresses {
description description
"Configures the virtual IP address for the Virtual Router "Configures the virtual IPv6 address for the
Redundancy Protocol (VRRP) interface."; VRRP interface.";
list virtual-ipv6-address { list virtual-ipv6-address {
key "ipv6-address"; key "ipv6-address";
max-elements 2; max-elements 2;
description description
"Two IPv6 addresses are allowed. The first one must be "Two IPv6 addresses are allowed. The first address must
a link-local address and the second one can be a be a link-local address. The second address can be a
link-local or global address."; link-local or global address.";
leaf ipv6-address { leaf ipv6-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"An IPv6 address associated with a virtual router."; "An IPv6 address associated with a virtual router.";
reference reference
"RFC 5798: Virtual Router Redundancy Protocol (VRRP) "RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3. Section 1.3."; Version 3 for IPv4 and IPv6. Section 1.3";
} }
} // virtual-ipv6-address } // virtual-ipv6-address
} // virtual-ipv6-addresses } // virtual-ipv6-addresses
} // grouping vrrp-ipv6-attributes } // vrrp-ipv6-attributes
grouping vrrp-state-attributes { grouping vrrp-state-attributes {
description description
"Group of VRRP state attributes."; "Group of VRRP state attributes.";
leaf state { leaf state {
type identityref { type identityref {
base vrrp:vrrp-state-type; base vrrp:vrrp-state-type;
} }
config false; config false;
description description
"Operational state."; "Operational state.";
} }
leaf is-owner { leaf is-owner {
type boolean; type boolean;
config false; config false;
description description
"Set to true if this virtual router is owner."; "Set to 'true' if this virtual router is the owner.";
} }
leaf last-adv-source { leaf last-adv-source {
type inet:ip-address; type inet:ip-address;
config false; config false;
description description
"Last advertised IPv4/IPv6 source address"; "Last advertised IPv4/IPv6 source address.";
} }
leaf up-datetime { leaf up-datetime {
type yang:date-and-time; type yang:date-and-time;
config false; config false;
description description
"The date and time when this virtual router "The date and time when this virtual router
transitioned out of init state."; transitioned out of 'init' state.";
} }
leaf master-down-interval { leaf master-down-interval {
type uint32; type uint32;
units centiseconds; units centiseconds;
config false; config false;
description description
"Time interval for backup virtual router to declare "Time interval for the backup virtual router to declare
Master down."; 'master down'.";
} }
leaf skew-time { leaf skew-time {
type uint32; type uint32;
units microseconds; units microseconds;
config false; config false;
description description
"Calculated based on the priority and advertisement "Calculated based on the priority and advertisement
interval configuration command parameters. See RFC 3768."; interval configuration command parameters. See RFC 3768.";
} }
leaf last-event { leaf last-event {
type identityref { type identityref {
base vrrp:vrrp-event-type; base vrrp:vrrp-event-type;
} }
config false; config false;
description description
"Last reported event."; "Last reported event.";
} }
leaf new-master-reason { leaf new-master-reason {
skipping to change at page 28, line 17 skipping to change at page 28, line 30
} }
config false; config false;
description description
"Last reported event."; "Last reported event.";
} }
leaf new-master-reason { leaf new-master-reason {
type new-master-reason-type; type new-master-reason-type;
config false; config false;
description description
"Indicates the reason for the virtual router to transition "Indicates why the virtual router has transitioned to
to master state."; master state.";
} }
container statistics { container statistics {
config false; config false;
description description
"VRRP statistics."; "VRRP statistics.";
leaf discontinuity-datetime { leaf discontinuity-datetime {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which any one or "The time on the most recent occasion at which any one or
more of the VRRP statistic counters suffered a more of the VRRP statistics 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 management since the last re-initialization of the local management
subsystem, then this node contains the time that the subsystem, then this node contains the time that the
local management subsystem re-initialized itself."; local management subsystem re-initialized itself.";
} }
leaf master-transitions { leaf master-transitions {
type yang:counter32; type yang:counter32;
description description
"The total number of times that this virtual router's "The total number of times that this virtual router's
state has transitioned to master"; state has transitioned to 'master'.";
} }
leaf advertisement-recv { leaf advertisement-rcvd {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP advertisements received by "The total number of VRRP advertisements received by
this virtual router."; this virtual router.";
} }
leaf advertisement-sent { leaf advertisement-sent {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP advertisements sent by "The total number of VRRP advertisements sent by
this virtual router."; this virtual router.";
} }
leaf interval-errors { leaf interval-errors {
if-feature validate-interval-errors; if-feature validate-interval-errors;
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP advertisement packets "The total number of VRRP advertisement packets received
received with an advertisement interval with an advertisement interval different than the
different than the one configured for the local interval configured for the local virtual router.";
virtual router";
} }
leaf priority-zero-pkts-rcvd { leaf priority-zero-pkts-rcvd {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP packets received by the "The total number of VRRP packets received by the
virtual router with a priority of 0."; virtual router with a priority of 0.";
} }
leaf priority-zero-pkts-sent { leaf priority-zero-pkts-sent {
skipping to change at page 30, line 8 skipping to change at page 30, line 19
address list that does not match the locally address list that does not match the locally
configured address list for the virtual router."; configured address list for the virtual router.";
} }
leaf packet-length-errors { leaf packet-length-errors {
type yang:counter64; type yang:counter64;
description description
"The total number of packets received with a packet "The total number of packets received with a packet
length less than the length of the VRRP header."; length less than the length of the VRRP header.";
} }
} // container statistics } // statistics
} // grouping vrrp-state-attributes } // vrrp-state-attributes
grouping vrrp-global-state-attributes { grouping vrrp-global-state-attributes {
description description
"Group of VRRP global state attributes."; "Group of VRRP global state attributes.";
leaf virtual-routers { leaf virtual-routers {
type uint32; type uint32;
description "Number of configured virtual routers."; description
"Number of configured virtual routers.";
} }
leaf interfaces { leaf interfaces {
type uint32; type uint32;
description "Number of interface with VRRP configured."; description
"Number of interfaces with VRRP configured.";
} }
container statistics { container statistics {
description description
"VRRP global statistics."; "VRRP global statistics.";
leaf discontinuity-datetime { leaf discontinuity-datetime {
type yang:date-and-time; type yang:date-and-time;
description description
"The time on the most recent occasion at which one of "The time on the most recent occasion at which any
checksum-errors, version-errors, vrid-errors, and one or more of checksum-errors, version-errors,
ip-ttl-errors suffered a discontinuity. vrid-errors, or ip-ttl-errors suffered a
discontinuity.
If no such discontinuities have occurred since the last If no such discontinuities have occurred since the last
re-initialization of the local management subsystem, re-initialization of the local management subsystem,
then this node contains the time that the local management then this node contains the time that the local management
subsystem re-initialized itself."; subsystem re-initialized itself.";
} }
leaf checksum-errors { leaf checksum-errors {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP packets received with an invalid "The total number of VRRP packets received with an invalid
VRRP checksum value."; VRRP checksum value.";
reference "RFC 5798, Section 5.2.8"; reference
"RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6. Section 5.2.8";
} }
leaf version-errors { leaf version-errors {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP packets received with an unknown "The total number of VRRP packets received with an unknown
or unsupported version number."; or unsupported version number.";
reference "RFC 5798, Section 5.2.1"; reference
"RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6. Section 5.2.1";
} }
leaf vrid-errors { leaf vrid-errors {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP packets received with a VRID that "The total number of VRRP packets received with a VRID that
is not valid for any virtual router on this router."; is not valid for any virtual router on this router.";
reference "RFC 5798, Section 5.2.3"; reference
"RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6. Section 5.2.3";
} }
leaf ip-ttl-errors { leaf ip-ttl-errors {
type yang:counter64; type yang:counter64;
description description
"The total number of VRRP packets received by the "The total number of VRRP packets received by the
virtual router with IP TTL (Time-To-Live) not equal virtual router with IP TTL (IPv4) or Hop Limit (IPv6)
to 255."; not equal to 255.";
reference "RFC 5798, Sections 5.1.1.3 and 5.1.2.3."; reference
"RFC 5798: Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6.
Sections 5.1.1.3 and 5.1.2.3";
} }
} // statistics } // statistics
} // vrrp-global-state-attributes } // vrrp-global-state-attributes
/* /*
* Configuration data and operational state data nodes * Configuration data and operational state data nodes
*/ */
augment "/if:interfaces/if:interface/ip:ipv4" { augment "/if:interfaces/if:interface/ip:ipv4" {
description "Augment IPv4 interface."; description
"Augments IPv4 interface.";
container vrrp { container vrrp {
description description
"Configures the Virtual Router Redundancy Protocol (VRRP) "Configures VRRP version 2 or 3 for IPv4.";
version 2 or version 3 for IPv4.";
list vrrp-instance { list vrrp-instance {
key "vrid"; key "vrid";
description description
"Defines a virtual router, identified by a virtual router "Defines a virtual router, identified by a VRID, within the
identifier (VRID), within IPv4 address space."; IPv4 address space.";
uses vrrp-ipv4-attributes; uses vrrp-ipv4-attributes;
uses vrrp-state-attributes; uses vrrp-state-attributes;
} }
} }
} // augment ipv4 } // augments ipv4
augment "/if:interfaces/if:interface/ip:ipv6" { augment "/if:interfaces/if:interface/ip:ipv6" {
description "Augment IPv6 interface."; description
"Augments IPv6 interface.";
container vrrp { container vrrp {
description description
"Configures the Virtual Router Redundancy Protocol (VRRP) "Configures VRRP version 3 for IPv6.";
version 3 for IPv6.";
list vrrp-instance { list vrrp-instance {
must "derived-from-or-self(version, 'vrrp-v3')" { must "derived-from-or-self(version, 'vrrp-v3')" {
description description
"IPv6 is only supported by version 3."; "IPv6 is only supported by version 3.";
} }
key "vrid"; key "vrid";
description description
"Defines a virtual router, identified by a virtual router "Defines a virtual router, identified by a VRID, within the
identifier (VRID), within IPv6 address space."; IPv6 address space.";
uses vrrp-ipv6-attributes; uses vrrp-ipv6-attributes;
uses vrrp-state-attributes; uses vrrp-state-attributes;
} // list vrrp-instance }
} // container vrrp }
} // augment ipv6 } // augments ipv6
container vrrp { container vrrp {
config false; config false;
description "VRRP data at the global level."; description
"VRRP data at the global level.";
uses vrrp-global-state-attributes; uses vrrp-global-state-attributes;
} }
/* /*
* Notifications * Notifications
*/ */
notification vrrp-new-master-event { notification vrrp-new-master-event {
description description
"Notification event for a change of VRRP new master."; "Notification event for the election of a new VRRP master.";
leaf master-ip-address { leaf master-ip-address {
type inet:ip-address; type inet:ip-address;
mandatory true; mandatory true;
description description
"IPv4 or IPv6 address of the new master."; "IPv4 or IPv6 address of the new master.";
} }
leaf new-master-reason { leaf new-master-reason {
type new-master-reason-type; type new-master-reason-type;
mandatory true; mandatory true;
description description
"Indicates the reason for the virtual router to transition "Indicates why the virtual router has transitioned to
to master state."; master state.";
} }
} }
notification vrrp-protocol-error-event { notification vrrp-protocol-error-event {
description description
"Notification event for a VRRP protocol error."; "Notification event for a VRRP protocol error.";
leaf protocol-error-reason { leaf protocol-error-reason {
type identityref { type identityref {
base vrrp:vrrp-error-global; base vrrp:vrrp-error-global;
} }
mandatory true; mandatory true;
description description
"Indicates the reason for the protocol error."; "Indicates the reason for the protocol error.";
} }
} }
notification vrrp-virtual-router-error-event { notification vrrp-virtual-router-error-event {
description description
"Notification event for an error happened on a virtual "Notification event for an error that happened on a
router."; virtual router.";
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
mandatory true; mandatory true;
description description
"Indicates the interface for which statistics area "Indicates the interface on which the event has occurred.";
to be cleared.";
} }
choice ip-version { choice ip-version {
mandatory true; mandatory true;
description description
"The error may have happened on either an IPv4 virtual "The error may have happened on either an IPv4 virtual
router or an IPv6 virtual router. The information router or an IPv6 virtual router. The information
related to a specific IP version is provided by one of related to a specific IP version is provided by one of
the following cases."; the following cases.";
case ipv4 { case ipv4 {
description "IPv4"; description
"IPv4.";
container ipv4 { container ipv4 {
description description
"Error information for IPv4."; "Error information for IPv4.";
leaf vrid { leaf vrid {
type leafref { type leafref {
path "/if:interfaces/if:interface" path "/if:interfaces/if:interface"
+ "[if:name = current()/../../vrrp:interface]/" + "[if:name = current()/../../vrrp:interface]/"
+ "ip:ipv4/vrrp:vrrp/vrrp:vrrp-instance/vrrp:vrid"; + "ip:ipv4/vrrp:vrrp/vrrp:vrrp-instance/vrrp:vrid";
} }
mandatory true; mandatory true;
description description
"Indicates the virtual router on which the event has "Indicates the virtual router on which the event has
occurred."; occurred.";
} }
} }
} }
case ipv6 { case ipv6 {
description "IPv6"; description
"IPv6.";
container ipv6 { container ipv6 {
description description
"Error information for IPv6."; "Error information for IPv6.";
leaf vrid { leaf vrid {
type leafref { type leafref {
path "/if:interfaces/if:interface" path "/if:interfaces/if:interface"
+ "[if:name = current()/../../vrrp:interface]/" + "[if:name = current()/../../vrrp:interface]/"
+ "ip:ipv6/vrrp:vrrp/vrrp:vrrp-instance/vrrp:vrid"; + "ip:ipv6/vrrp:vrrp/vrrp:vrrp-instance/vrrp:vrid";
} }
mandatory true; mandatory true;
skipping to change at page 34, line 41 skipping to change at page 35, line 20
leaf virtual-router-error-reason { leaf virtual-router-error-reason {
type identityref { type identityref {
base vrrp:vrrp-error-virtual-router; base vrrp:vrrp-error-virtual-router;
} }
mandatory true; mandatory true;
description description
"Indicates the reason for the virtual router error."; "Indicates the reason for the virtual router error.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
RFC Ed.: In this section, replace all occurrences of 'XXXX' with the This document registers the following namespace URI in the "IETF XML
actual RFC number (and remove this note). Registry" [RFC3688]:
This document registers the following namespace URIs in the IETF XML
registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-vrrp URI: urn:ietf:params:xml:ns:yang:ietf-vrrp
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
-------------------------------------------------------------------- --------------------------------------------------------------------
This document registers the following YANG modules in the YANG Module This document registers the following YANG module in the "YANG Module
Names registry [RFC7950]: Names" registry [RFC7950]:
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-vrrp name: ietf-vrrp
namespace: urn:ietf:params:xml:ns:yang:ietf-vrrp namespace: urn:ietf:params:xml:ns:yang:ietf-vrrp
prefix: vrrp prefix: vrrp
reference: RFC XXXX reference: RFC 8347
-------------------------------------------------------------------- --------------------------------------------------------------------
6. Security Considerations 6. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246]. [RFC5246].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC8341] provides the means to
restrict access for particular NETCONF or RESTCONF users to a restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that 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. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
skipping to change at page 36, line 26 skipping to change at page 37, line 11
Unauthorized access to any data node of these subtrees can disclose Unauthorized access to any data node of these subtrees can disclose
the operational state information of VRRP on this device. the operational state information of VRRP on this device.
7. References 7. References
7.1. Normative References 7.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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2787] Jewell, B. and D. Chuang, "Definitions of Managed Objects [RFC2787] Jewell, B. and D. Chuang, "Definitions of Managed Objects
for the Virtual Router Redundancy Protocol", RFC 2787, for the Virtual Router Redundancy Protocol", RFC 2787,
DOI 10.17487/RFC2787, March 2000, <https://www.rfc- DOI 10.17487/RFC2787, March 2000,
editor.org/info/rfc2787>. <https://www.rfc-editor.org/info/rfc2787>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004,
editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, <https://www.rfc- DOI 10.17487/RFC5246, August 2008,
editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP) [RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6", RFC 5798, Version 3 for IPv4 and IPv6", RFC 5798,
DOI 10.17487/RFC5798, March 2010, <https://www.rfc- DOI 10.17487/RFC5798, March 2010,
editor.org/info/rfc5798>. <https://www.rfc-editor.org/info/rfc5798>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <https://www.rfc- DOI 10.17487/RFC6020, October 2010,
editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6527] Tata, K., "Definitions of Managed Objects for Virtual [RFC6527] Tata, K., "Definitions of Managed Objects for Virtual
Router Redundancy Protocol Version 3 (VRRPv3)", RFC 6527, Router Redundancy Protocol Version 3 (VRRPv3)", RFC 6527,
DOI 10.17487/RFC6527, March 2012, <https://www.rfc- DOI 10.17487/RFC6527, March 2012,
editor.org/info/rfc6527>. <https://www.rfc-editor.org/info/rfc6527>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[I-D.ietf-netmod-rfc7223bis] [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in
Bjorklund, M., "A YANG Data Model for Interface RFC 2119 Key Words", BCP 14, RFC 8174,
Management", draft-ietf-netmod-rfc7223bis-03 (work in DOI 10.17487/RFC8174, May 2017,
progress), January 2018. <https://www.rfc-editor.org/info/rfc8174>.
[I-D.ietf-netmod-rfc7277bis] [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Bjorklund, M., "A YANG Data Model for IP Management", Access Control Model", STD 91, RFC 8341,
draft-ietf-netmod-rfc7277bis-03 (work in progress), DOI 10.17487/RFC8341, March 2018,
January 2018. <https://www.rfc-editor.org/info/rfc8341>.
[I-D.ietf-netmod-revised-datastores] [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture
and R. Wilton, "Network Management Datastore (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
Architecture", draft-ietf-netmod-revised-datastores-10 <https://www.rfc-editor.org/info/rfc8342>.
(work in progress), January 2018.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",
RFC 8344, DOI 10.17487/RFC8344, March 2018,
<https://www.rfc-editor.org/info/rfc8344>.
7.2. Informative References 7.2. Informative References
[RFC3768] Hinden, R., Ed., "Virtual Router Redundancy Protocol [RFC3768] Hinden, R., Ed., "Virtual Router Redundancy Protocol
(VRRP)", RFC 3768, DOI 10.17487/RFC3768, April 2004, (VRRP)", RFC 3768, DOI 10.17487/RFC3768, April 2004,
<https://www.rfc-editor.org/info/rfc3768>. <https://www.rfc-editor.org/info/rfc3768>.
[RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",
RFC 7224, DOI 10.17487/RFC7224, May 2014,
<https://www.rfc-editor.org/info/rfc7224>.
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016, RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>. <https://www.rfc-editor.org/info/rfc7951>.
[I-D.ietf-netconf-subscribed-notifications] [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
A. Tripathy, "Custom Subscription to Event Streams", <https://www.rfc-editor.org/info/rfc8340>.
draft-ietf-netconf-subscribed-notifications-09 (work in
progress), January 2018.
[I-D.ietf-netconf-yang-push] [Subscribed-Notifications]
Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen- Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,
Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore E., and A. Tripathy, "Custom Subscription to Event
Subscription", draft-ietf-netconf-yang-push-14 (work in Streams", Work in Progress, draft-ietf-netconf-subscribed-
progress), February 2018. notifications-10, February 2018.
[I-D.ietf-netmod-rfc6087bis] [YANG-Push]
Bierman, A., "Guidelines for Authors and Reviewers of YANG Clemm, A., Voit, E., Gonzalez Prieto, A., Tripathy, A.,
Data Model Documents", draft-ietf-netmod-rfc6087bis-17 Nilsen-Nygaard, E., Bierman, A., and B. Lengyel, "YANG
(work in progress), February 2018. Datastore Subscription", Work in Progress,
draft-ietf-netconf-yang-push-15, February 2018.
[I-D.ietf-netmod-yang-tree-diagrams] [YANG-Guidelines]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bierman, A., "Guidelines for Authors and Reviewers of YANG
ietf-netmod-yang-tree-diagrams-06 (work in progress), Data Model Documents", Work in Progress,
February 2018. draft-ietf-netmod-rfc6087bis-20, March 2018.
Appendix A. Data Tree Example Appendix A. Data Tree Example
This section contains an example of an instance data tree in the JSON This section contains an example of an instance data tree in JSON
encoding [RFC7951], containing both configuration and state data. encoding [RFC7951], containing both configuration and state data.
(This example includes "iana-if-type", which is defined in
[RFC7224].)
Virtual router IP address: fe80::1 Virtual router IP address: fe80::1
+-----------------+ +-----------------+ +-----------------+ +-----------------+
| | | | | | | |
| Router 1 | | Router 2 | | Router 1 | | Router 2 |
| | | | | | | |
+--------+--------+ +--------+--------+ +--------+--------+ +--------+--------+
|eth1 |eth1 |eth1 |eth1
|fe80::11 |fe80::12 |fe80::11 |fe80::12
-------+--------------------------+------- -------+--------------------------+-------
skipping to change at page 40, line 44 skipping to change at page 42, line 4
] ]
} }
} }
] ]
} }
} }
} }
] ]
} }
} }
The corresponding operational state data for Router 1 could be as
The cooresponding operational state data for Router 1 could be as
follows: follows:
{ {
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interface": [ "interface": [
{ {
"name": "eth1", "name": "eth1",
"description": "An interface with VRRP enabled.", "description": "An interface with VRRP enabled.",
"type": "iana-if-type:ethernetCsmacd", "type": "iana-if-type:ethernetCsmacd",
"phys-address": "00:00:5e:00:53:01", "phys-address": "00:00:5e:00:53:01",
skipping to change at page 42, line 10 skipping to change at page 43, line 34
"last-adv-source": "fe80::11", "last-adv-source": "fe80::11",
"up-datetime": "2016-10-24T17:11:27+02:00", "up-datetime": "2016-10-24T17:11:27+02:00",
"master-down-interval": 161, "master-down-interval": 161,
"skew-time": 11, "skew-time": 11,
"last-event": "vrrp-event-interface-up", "last-event": "vrrp-event-interface-up",
"new-master-reason": "priority", "new-master-reason": "priority",
"statistics": { "statistics": {
"discontinuity-datetime": "discontinuity-datetime":
"2016-10-24T17:11:27+02:00", "2016-10-24T17:11:27+02:00",
"master-transitions": 2, "master-transitions": 2,
"advertisement-recv": 20, "advertisement-rcvd": 20,
"advertisement-sent": 12, "advertisement-sent": 12,
"interval-errors": 0, "interval-errors": 0,
"priority-zero-pkts-rcvd": 0, "priority-zero-pkts-rcvd": 0,
"priority-zero-pkts-sent": 0, "priority-zero-pkts-sent": 0,
"invalid-type-pkts-rcvd": 0, "invalid-type-pkts-rcvd": 0,
"address-list-errors": 0, "address-list-errors": 0,
"packet-length-errors": 1 "packet-length-errors": 1
} }
} }
] ]
skipping to change at page 42, line 47 skipping to change at page 45, line 10
"ip-ttl-errors": 1 "ip-ttl-errors": 1
} }
} }
} }
Authors' Addresses Authors' Addresses
Xufeng Liu (editor) Xufeng Liu (editor)
Jabil Jabil
8281 Greensboro Drive, Suite 200 8281 Greensboro Drive, Suite 200
McLean VA 22102 McLean, VA 22102
USA United States of America
Email: xufeng.liu.ietf@gmail.com
EMail: Xufeng_Liu@jabil.com
Athanasios Kyparlis Athanasios Kyparlis
Jabil Jabil
8281 Greensboro Drive, Suite 200 8281 Greensboro Drive, Suite 200
McLean VA 22102 McLean, VA 22102
USA United States of America
EMail: Athanasios_Kyparlis@jabil.com Email: Athanasios_Kyparlis@jabil.com
Ravi Parikh Ravi Parikh
VMware VMware
3425 Hillview Avenue 3425 Hillview Avenue
Palo Alto CA 94304 Palo Alto, CA 94304
USA United States of America
EMail: parikhr@vmware.com Email: parikhr@vmware.com
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
301 Midenhall Way 301 Midenhall Way
Cary NC 27513 Cary, NC 27513
USA United States of America
EMail: acee@cisco.com Email: acee@cisco.com
Mingui Zhang Mingui Zhang
Huawei Technologies Huawei Technologies
No. 156 Beiqing Rd. Haidian District No. 156 Beiqing Rd. Haidian District
Beijing 100095 Beijing 100095
P.R. China China
EMail: zhangmingui@huawei.com Email: zhangmingui@huawei.com
 End of changes. 199 change blocks. 
392 lines changed or deleted 409 lines changed or added

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