< draft-ietf-rtgwg-policy-model-05.txt		draft-ietf-rtgwg-policy-model-06.txt >
	RTGWG Y. Qu		RTGWG Y. Qu
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Informational J. Tantsura		Intended status: Standards Track J. Tantsura
	Expires: July 11, 2019 Apstra		Expires: September 11, 2019 Apstra
	A. Lindem		A. Lindem
	Cisco		Cisco
	X. Liu		X. Liu
	Volta Networks		Volta Networks
	January 7, 2019		March 10, 2019
	A YANG Data Model for Routing Policy Management		A YANG Data Model for Routing Policy Management
	draft-ietf-rtgwg-policy-model-05		draft-ietf-rtgwg-policy-model-06
	Abstract		Abstract
	This document defines a YANG data model for configuring and managing		This document defines a YANG data model for configuring and managing
	routing policies in a vendor-neutral way and based on actual		routing policies in a vendor-neutral way and based on actual
	operational practice. The model provides a generic policy framework		operational practice. The model provides a generic policy framework
	which can be augmented with protocol-specific policy configuration.		which can be augmented with protocol-specific policy configuration.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 July 11, 2019.		This Internet-Draft will expire on September 11, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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
	skipping to change at page 9, line 12 ¶		skipping to change at page 9, line 12 ¶
	generic actions in addition to the basic route disposition actions.		generic actions in addition to the basic route disposition actions.
	These are shown below.		These are shown below.
	+--rw routing-policy		+--rw routing-policy
	+--rw policy-definitions		+--rw policy-definitions
	+--rw policy-definition* [name]		+--rw policy-definition* [name]
	+--rw statements		+--rw statements
	+--rw statement* [name]		+--rw statement* [name]
	+--rw actions		+--rw actions
	+--rw policy-result? policy-result-type		+--rw policy-result? policy-result-type
	+--rw set-metric? union		+--rw set-metric? uint32
	+--rw set-preference? union		+--rw set-preference? uint16
	4.4. Policy subroutines		4.4. Policy subroutines
	Policy 'subroutines' (or nested policies) are supported by allowing		Policy 'subroutines' (or nested policies) are supported by allowing
	policy statement conditions to reference other policy definitions		policy statement conditions to reference other policy definitions
	using the call-policy configuration. Called policies apply their		using the call-policy configuration. Called policies apply their
	conditions and actions before returning to the calling policy		conditions and actions before returning to the calling policy
	statement and resuming evaluation. The outcome of the called policy		statement and resuming evaluation. The outcome of the called policy
	affects the evaluation of the calling policy. If the called policy		affects the evaluation of the calling policy. If the called policy
	results in an accept-route, then the subroutine returns an effective		results in an accept-route, then the subroutine returns an effective
	skipping to change at page 12, line 48 ¶		skipping to change at page 12, line 48 ¶
	| +--rw bgp-pol:match-ext-community-set		| +--rw bgp-pol:match-ext-community-set
	| | +--rw bgp-pol:ext-community-set?		| | +--rw bgp-pol:ext-community-set?
	| | +--rw bgp-pol:match-set-options?		| | +--rw bgp-pol:match-set-options?
	| | match-set-options-type		| | match-set-options-type
	| +--rw bgp-pol:match-as-path-set		| +--rw bgp-pol:match-as-path-set
	| +--rw bgp-pol:as-path-set?		| +--rw bgp-pol:as-path-set?
	| +--rw bgp-pol:match-set-options?		| +--rw bgp-pol:match-set-options?
	| match-set-options-type		| match-set-options-type
	+--rw actions		+--rw actions
	+--rw policy-result? policy-result-type		+--rw policy-result? policy-result-type
	+--rw set-metric? union		+--rw set-metric? uint32
	+--rw set-preference? union		+--rw set-preference? uint16
	+--rw bgp-pol:bgp-actions		+--rw bgp-pol:bgp-actions
	+--rw bgp-pol:set-route-origin?		+--rw bgp-pol:set-route-origin?
	bgp-types:bgp-origin-attr-type		bgp-types:bgp-origin-attr-type
	+--rw bgp-pol:set-local-pref? uint32		+--rw bgp-pol:set-local-pref? uint32
	+--rw bgp-pol:set-next-hop? bgp-next-hop-type		+--rw bgp-pol:set-next-hop? bgp-next-hop-type
	+--rw bgp-pol:set-med? bgp-set-med-type		+--rw bgp-pol:set-med? bgp-set-med-type
	+--rw bgp-pol:set-as-path-prepend		+--rw bgp-pol:set-as-path-prepend
	| +--rw bgp-pol:repeat-n? uint8		| +--rw bgp-pol:repeat-n? uint8
	+--rw bgp-pol:set-community		+--rw bgp-pol:set-community
	| +--rw bgp-pol:method? enumeration		| +--rw bgp-pol:method? enumeration
	skipping to change at page 14, line 12 ¶		skipping to change at page 14, line 12 ¶
	YANG modules will be registered in the "YANG Module Names" registry		YANG modules will be registered in the "YANG Module Names" registry
	[RFC6020].		[RFC6020].
	10. YANG modules		10. YANG modules
	The routing policy model is described by the YANG modules in the		The routing policy model is described by the YANG modules in the
	sections below.		sections below.
	10.1. Routing policy model		10.1. Routing policy model
	<CODE BEGINS> file "ietf-routing-policy@2019-01-07.yang"		<CODE BEGINS> file "ietf-routing-policy@2019-03-06.yang"
	module ietf-routing-policy {		module ietf-routing-policy {
	yang-version "1.1";		yang-version "1.1";
	namespace "urn:ietf:params:xml:ns:yang:ietf-routing-policy";		namespace "urn:ietf:params:xml:ns:yang:ietf-routing-policy";
	prefix rt-pol;		prefix rt-pol;
	import ietf-inet-types {		import ietf-inet-types {
	prefix "inet";		prefix "inet";
	}		}
	skipping to change at page 16, line 24 ¶		skipping to change at page 16, line 24 ¶
	the referenced policy before returning to the calling policy		the referenced policy before returning to the calling policy
	statement and resuming evaluation. If the called policy		statement and resuming evaluation. If the called policy
	results in an accept-route (either explicit or by default),		results in an accept-route (either explicit or by default),
	then the subroutine returns an effective true value to the		then the subroutine returns an effective true value to the
	calling policy. Similarly, a reject-route action returns		calling policy. Similarly, a reject-route action returns
	false. If the subroutine returns true, the calling policy		false. If the subroutine returns true, the calling policy
	continues to evaluate the remaining conditions (using a		continues to evaluate the remaining conditions (using a
	modified route if the subroutine performed any changes to the		modified route if the subroutine performed any changes to the
	route).";		route).";
	revision "2019-01-07" {		revision "2019-03-06" {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: Routing Policy Configuration Model for Service		"RFC XXXX: Routing Policy Configuration Model for Service
	Provider Networks";		Provider Networks";
	}		}
	// typedef statements		// typedef statements
	typedef default-policy-type {		typedef default-policy-type {
	skipping to change at page 31, line 6 ¶		skipping to change at page 31, line 6 ¶
	Below we show an example of XML-encoded configuration data using the		Below we show an example of XML-encoded configuration data using the
	routing policy and BGP models to illustrate both how policies are		routing policy and BGP models to illustrate both how policies are
	defined, and also how they can be applied. Note that the XML has		defined, and also how they can be applied. Note that the XML has
	been simplified for readability.		been simplified for readability.
	<?yfile include="file:///tmp/routing-policy-example-draft.xml"?>		<?yfile include="file:///tmp/routing-policy-example-draft.xml"?>
	12. References		12. References
	12.1. Normative references		12.1. Normative references
			[I-D.ietf-netmod-intf-ext-yang]
			Wilton, R., Ball, D., tsingh@juniper.net, t., and S.
			Sivaraj, "Common Interface Extension YANG Data Models",
			draft-ietf-netmod-intf-ext-yang-07 (work in progress),
			March 2019.
			[I-D.ietf-netmod-sub-intf-vlan-model]
			Wilton, R., Ball, D., tapsingh@cisco.com, t., and S.
			Sivaraj, "Sub-interface VLAN YANG Data Models", draft-
			ietf-netmod-sub-intf-vlan-model-05 (work in progress),
			March 2019.
	[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>.
	[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>.
	[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A		[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
	Border Gateway Protocol 4 (BGP-4)", RFC 4271,		Border Gateway Protocol 4 (BGP-4)", RFC 4271,
	DOI 10.17487/RFC4271, January 2006, <https://www.rfc-		DOI 10.17487/RFC4271, January 2006,
	editor.org/info/rfc4271>.		<https://www.rfc-editor.org/info/rfc4271>.
	[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>.
	[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>.
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	skipping to change at page 32, line 7 ¶		skipping to change at page 32, line 16 ¶
	and R. Wilton, "Network Management Datastore Architecture		and R. Wilton, "Network Management Datastore Architecture
	(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,		(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
	<https://www.rfc-editor.org/info/rfc8342>.		<https://www.rfc-editor.org/info/rfc8342>.
	[RFC8343] Bjorklund, M., "A YANG Data Model for Interface		[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
	Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,		Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
	<https://www.rfc-editor.org/info/rfc8343>.		<https://www.rfc-editor.org/info/rfc8343>.
	[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for		[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
	Routing Management (NMDA Version)", RFC 8349,		Routing Management (NMDA Version)", RFC 8349,
	DOI 10.17487/RFC8349, March 2018, <https://www.rfc-		DOI 10.17487/RFC8349, March 2018,
	editor.org/info/rfc8349>.		<https://www.rfc-editor.org/info/rfc8349>.
	[I-D.ietf-netmod-intf-ext-yang]
	Wilton, R., Ball, D., tsingh@juniper.net, t., and S.
	Sivaraj, "Common Interface Extension YANG Data Models",
	draft-ietf-netmod-intf-ext-yang-06 (work in progress),
	July 2018.
	12.2. Informative references		12.2. Informative references
	[I-D.ietf-idr-bgp-model]		[I-D.ietf-idr-bgp-model]
	Patel, K., Jethanandani, M., and S. Hares, "BGP Model for		Patel, K., Jethanandani, M., and S. Hares, "BGP YANG Model
	Service Provider Networks", draft-ietf-idr-bgp-model-03		for Service Provider Networks", draft-ietf-idr-bgp-
	(work in progress), May 2018.		model-04 (work in progress), February 2019.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	The routing policy module defined in this draft is based on the		The routing policy module defined in this draft is based on the
	OpenConfig route policy model. The authors would like to thank to		OpenConfig route policy model. The authors would like to thank to
	OpenConfig for their contributions, especially Anees Shaikh, Rob		OpenConfig for their contributions, especially Anees Shaikh, Rob
	Shakir, Kevin D'Souza, and Chris Chase.		Shakir, Kevin D'Souza, and Chris Chase.
	The authors are grateful for valuable contributions to this document		The authors are grateful for valuable contributions to this document
	and the associated models from: Ebben Aires, Luyuan Fang, Josh		and the associated models from: Ebben Aires, Luyuan Fang, Josh
End of changes. 17 change blocks.
	32 lines changed or deleted		38 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/