< draft-ietf-rtgwg-yang-vrrp-07.txt		draft-ietf-rtgwg-yang-vrrp-08.txt >
	Network Working Group X. Liu, Ed.		Network Working Group X. Liu, Ed.
	Internet-Draft A. Kyparlis		Internet-Draft A. Kyparlis
	Intended status: Standards Track Jabil		Intended status: Standards Track Jabil
	Expires: April 30, 2018 R. Parikh		Expires: June 18, 2018 R. Parikh
	VMware		VMware
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	M. Zhang		M. Zhang
	Huawei Technologies		Huawei Technologies
	October 27, 2017		December 15, 2017
	A YANG Data Model for Virtual Router Redundancy Protocol (VRRP)		A YANG Data Model for Virtual Router Redundancy Protocol (VRRP)
	draft-ietf-rtgwg-yang-vrrp-07		draft-ietf-rtgwg-yang-vrrp-08
	Abstract		Abstract
	This document describes a data model for Virtual Router Redundancy		This document describes a data model for Virtual Router Redundancy
	Protocol (VRRP). Both version 2 and version 3 of VRRP are covered.		Protocol (VRRP). Both version 2 and version 3 of VRRP are covered.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on April 30, 2018.		This Internet-Draft will expire on June 18, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 14 ¶		skipping to change at page 2, line 14 ¶
	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 . . . . . . . . . . . . . . . . . . 4		2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
	2.1. Scope of the Model . . . . . . . . . . . . . . . . . . . 4		2.1. Scope of the Model . . . . . . . . . . . . . . . . . . . 3
	2.2. Relations with Interface Model and IP Model . . . . . . . 4		2.2. Relations with Interface Model and IP Model . . . . . . . 4
	2.3. Protocol Configuration . . . . . . . . . . . . . . . . . 5		2.3. Protocol Configuration . . . . . . . . . . . . . . . . . 5
	2.4. Protocol States . . . . . . . . . . . . . . . . . . . . . 7		2.4. Protocol States . . . . . . . . . . . . . . . . . . . . . 6
	2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 8		2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 7
	3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 10		3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 9
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 31		5. Security Considerations . . . . . . . . . . . . . . . . . . . 31
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 32		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
	6.1. Normative References . . . . . . . . . . . . . . . . . . 32		6.1. Normative References . . . . . . . . . . . . . . . . . . 32
	6.2. Informative References . . . . . . . . . . . . . . . . . 33		6.2. Informative References . . . . . . . . . . . . . . . . . 33
	Appendix A. Complete Model Tree Structure . . . . . . . . . . . 35		Appendix A. Complete Model Tree Structure . . . . . . . . . . . 34
	Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 37		Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 36
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
	1. Introduction		1. Introduction
	This document introduces a YANG [RFC6020][RFC7950] data model for		This document introduces a YANG [RFC6020][RFC7950] data model for
	Virtual Router Redundancy Protocol (VRRP) [RFC3768][RFC5798]. VRRP		Virtual Router Redundancy Protocol (VRRP) [RFC3768][RFC5798]. VRRP
	provides higher resiliency by specifying an election protocol that		provides higher resiliency by specifying an election protocol that
	dynamically assigns responsibility for a virtual router to one of the		dynamically assigns responsibility for a virtual router to one of the
	VRRP routers on a LAN.		VRRP routers on a LAN.
	This YANG model supports both version 2 and version 3 of VRRP. VRRP		This YANG model supports both version 2 and version 3 of VRRP. VRRP
	skipping to change at page 3, line 11 ¶		skipping to change at page 3, line 11 ¶
	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 as		this document. The meaning of the symbols in these diagrams is
	follows:		defined in [I-D.ietf-netmod-yang-tree-diagrams].
	o Brackets "[" and "]" enclose list keys.
	o Curly braces "{" and "}" contain names of optional features that
	make the corresponding node conditional.
	o Abbreviations before data node names: "rw" means configuration
	(read-write), and "ro" means state data (read-only).
	o Symbols after data node names: "?" means an optional node, "!"
	means a presence container, and "*" denotes a list and leaf-list.
	o Parentheses enclose choice and case nodes, and case nodes are also
	marked with a colon (":").
	o Ellipsis ("...") stands for contents of subtrees that are not
	shown.
	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.
	+--------+-----------------+-----------------------------------+		+--------+-----------------+-----------------------------------+
	skipping to change at page 10, line 7 ¶		skipping to change at page 9, line 7 ¶
	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 xpath filters so that only interested
	contents will be sent.		contents will be sent.
	o Specify either periodic or on-demand notifications.		o Specify either periodic or on-demand notifications.
	3. YANG Module		3. YANG Module
	<CODE BEGINS> file "ietf-vrrp@2017-10-25.yang"		<CODE BEGINS> file "ietf-vrrp@2017-12-15.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 {
	skipping to change at page 11, line 12 ¶		skipping to change at page 10, line 12 ¶
	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) version 2 and version 3.";
	revision 2017-10-25 {		revision 2017-12-15 {
	description "Initial revision";		description "Initial revision";
	reference		reference
	"RFC XXXX: A YANG Data Model for Virtual Router Redundancy		"RFC XXXX: A YANG Data Model for 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.
	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).";
	skipping to change at page 19, line 11 ¶		skipping to change at page 18, line 11 ¶
	} // 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 Virtual Router Redundancy Protocol
	version 2 (VRRP) or version 3 (VRRPv3) instance to track		version 2 (VRRP) or version 3 (VRRPv3) instance to track
	an interface.";		interfaces.
			Interface tracking prevents traffic loss by detecting the
			availability of interfaces. The operational states of
			other interfaces are associated with the priority of a
			VRRP router. When a tracked interface becomes unavailable
			(or operational down), the priority of the backup router
			decrements. When an unavailable interface becomes
			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" {
	skipping to change at page 19, line 43 ¶		skipping to change at page 18, line 51 ¶
	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 backup Virtual Router Redundancy Protocol
	version 2 (VRRP) or version 3 (VRRPv3) router to track a		version 2 (VRRP) or version 3 (VRRPv3) router to track
	specified network through the IP network prefix of that		specified networks through the IP network prefixes of
	network.";		these networks.
			Network tracking prevents traffic loss by detecting
			network connectivity failure. The states of connectivity
			to some networks are associated with the priority of a
			VRRP router. When connectivity to a tracked network
			represented by its prefix is lost, the priority of the
			backup VRRP router decrements. When an unavailable network
			is again reachable, the priority of the backup 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 Virtual Router Redundancy
	Protocol version 2 (VRRP) or version 3 (VRRPv3)		Protocol version 2 (VRRP) or version 3 (VRRPv3)
	instance to track an IP network, by specifying the		instance to track an IP network, by specifying the
	prefix of the IP network.";		prefix of the IP network.";
	leaf prefix {		leaf prefix {
	type inet:ipv4-prefix;		type inet:ipv4-prefix;
	skipping to change at page 21, line 30 ¶		skipping to change at page 20, line 46 ¶
	}		}
	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 Virtual Router Redundancy Protocol
	version 2 (VRRP) or version 3 (VRRPv3) instance to track		version 2 (VRRP) or version 3 (VRRPv3) instance to track
	an interface.";		interfaces.
			Interface tracking prevents traffic loss by detecting the
			availability of interfaces. The operational states of
			other interfaces are associated with the priority of a
			VRRP router. When a tracked interface becomes unavailable
			(or operational down), the priority of the backup router
			decrements. When an unavailable interface becomes
			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.";
	skipping to change at page 22, line 13 ¶		skipping to change at page 21, line 37 ¶
	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 backup Virtual Router Redundancy Protocol
	version 2 (VRRP) or version 3 (VRRPv3) router to track a		version 2 (VRRP) or version 3 (VRRPv3) router to track
	specified network through the IP network prefix of that		specified networks through the IP network prefixes of
	network.";		these networks.
			Network tracking prevents traffic loss by detecting
			network connectivity failure. The states of connectivity
			to some networks are associated with the priority of a
			VRRP router. When connectivity to a tracked network
			represented by its prefix is lost, the priority of the
			backup VRRP router decrements. When an unavailable network
			is again reachable, the priority of the backup 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 Virtual Router Redundancy
	Protocol version 2 (VRRP) or version 3 (VRRPv3)		Protocol version 2 (VRRP) or version 3 (VRRPv3)
	instance to track an IP network, by specifying the		instance to track an IP network, by specifying the
	prefix of the IP network.";		prefix of the IP network.";
	leaf prefix {		leaf prefix {
	type inet:ipv6-prefix;		type inet:ipv6-prefix;
	skipping to change at page 32, line 23 ¶		skipping to change at page 32, line 7 ¶
	/if:interfaces/if:interface/ip:ipv4/vrrp:vrrp/vrrp:vrrp-instance		/if:interfaces/if:interface/ip:ipv4/vrrp:vrrp/vrrp:vrrp-instance
	/if:interfaces/if:interface/ip:ipv6/vrrp:vrrp/vrrp:vrrp-instance		/if:interfaces/if:interface/ip:ipv6/vrrp:vrrp/vrrp:vrrp-instance
	Unauthorized access to any node of these can adversely affect the		Unauthorized access to any node of these can adversely affect the
	routing subsystem of both the local device and the network. This may		routing subsystem of both the local device and the network. This may
	lead to network malfunctions, delivery of packets to inappropriate		lead to network malfunctions, delivery of packets to inappropriate
	destinations, and other problems.		destinations, and other problems.
			Implementers should review all the nodes for security concerns.
	6. References		6. References
	6.1. Normative References		6.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, <https://www.rfc-
	editor.org/info/rfc2119>.		editor.org/info/rfc2119>.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	skipping to change at page 33, line 26 ¶		skipping to change at page 33, line 13 ¶
	progress), August 2017.		progress), August 2017.
	[I-D.bjorklund-netmod-rfc7277bis]		[I-D.bjorklund-netmod-rfc7277bis]
	Bjorklund, M., "A YANG Data Model for IP Management",		Bjorklund, M., "A YANG Data Model for IP Management",
	draft-bjorklund-netmod-rfc7277bis-00 (work in progress),		draft-bjorklund-netmod-rfc7277bis-00 (work in progress),
	August 2017.		August 2017.
	[I-D.ietf-netmod-revised-datastores]		[I-D.ietf-netmod-revised-datastores]
	Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,		Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
	and R. Wilton, "Network Management Datastore		and R. Wilton, "Network Management Datastore
	Architecture", draft-ietf-netmod-revised-datastores-05		Architecture", draft-ietf-netmod-revised-datastores-07
	(work in progress), October 2017.		(work in progress), November 2017.
	6.2. Informative References		6.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>.
	[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration		[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
	Protocol (NETCONF) Access Control Model", RFC 6536,		Protocol (NETCONF) Access Control Model", RFC 6536,
	DOI 10.17487/RFC6536, March 2012, <https://www.rfc-		DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
	skipping to change at page 34, line 7 ¶		skipping to change at page 33, line 39 ¶
	<https://www.rfc-editor.org/info/rfc7951>.		<https://www.rfc-editor.org/info/rfc7951>.
	[I-D.ietf-netconf-rfc5277bis]		[I-D.ietf-netconf-rfc5277bis]
	Clemm, A., Prieto, A., Voit, E., Nilsen-Nygaard, E.,		Clemm, A., Prieto, A., Voit, E., Nilsen-Nygaard, E.,
	Tripathy, A., Chisholm, S., and H. Trevino, "Subscribing		Tripathy, A., Chisholm, S., and H. Trevino, "Subscribing
	to Event Notifications", draft-ietf-netconf-rfc5277bis-01		to Event Notifications", draft-ietf-netconf-rfc5277bis-01
	(work in progress), October 2016.		(work in progress), October 2016.
	[I-D.ietf-netconf-yang-push]		[I-D.ietf-netconf-yang-push]
	Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-		Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-
	Nygaard, E., Bierman, A., and B. Lengyel, "Subscribing to		Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore
	YANG datastore push updates", draft-ietf-netconf-yang-		Subscription", draft-ietf-netconf-yang-push-11 (work in
	push-10 (work in progress), October 2017.		progress), October 2017.
	[I-D.ietf-netmod-rfc6087bis]		[I-D.ietf-netmod-rfc6087bis]
	Bierman, A., "Guidelines for Authors and Reviewers of YANG		Bierman, A., "Guidelines for Authors and Reviewers of YANG
	Data Model Documents", draft-ietf-netmod-rfc6087bis-14		Data Model Documents", draft-ietf-netmod-rfc6087bis-14
	(work in progress), September 2017.		(work in progress), September 2017.
			[I-D.ietf-netmod-yang-tree-diagrams]
			Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
			ietf-netmod-yang-tree-diagrams-02 (work in progress),
			October 2017.
	Appendix A. Complete Model Tree Structure		Appendix A. Complete Model 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
	+--ro virtual-routers? uint32		+--ro virtual-routers? uint32
	+--ro interfaces? uint32		+--ro interfaces? uint32
	+--ro statistics		+--ro statistics
End of changes. 18 change blocks.
	46 lines changed or deleted		68 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/