< draft-ietf-rtgwg-policy-model-20.txt		draft-ietf-rtgwg-policy-model-21.txt >
	RTGWG Y. Qu		RTGWG Y. Qu
	Internet-Draft Futurewei		Internet-Draft Futurewei
	Intended status: Standards Track J. Tantsura		Intended status: Standards Track J. Tantsura
	Expires: February 18, 2021 Apstra		Expires: March 7, 2021 Apstra
	A. Lindem		A. Lindem
	Cisco		Cisco
	X. Liu		X. Liu
	Volta Networks		Volta Networks
	August 17, 2020		September 3, 2020
	A YANG Data Model for Routing Policy Management		A YANG Data Model for Routing Policy Management
	draft-ietf-rtgwg-policy-model-20		draft-ietf-rtgwg-policy-model-21
	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
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 https://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 February 18, 2021.		This Internet-Draft will expire on March 7, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	(https://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
	skipping to change at page 11, line 22 ¶		skipping to change at page 11, line 22 ¶
	both import and export policies.		both import and export policies.
	7. Routing protocol-specific policies		7. Routing protocol-specific policies
	Routing models that require the ability to apply routing policy may		Routing models that require the ability to apply routing policy may
	augment the routing policy model with protocol or other specific		augment the routing policy model with protocol or other specific
	policy configuration. The routing policy model assumes that		policy configuration. The routing policy model assumes that
	additional defined sets, conditions, and actions may all be added by		additional defined sets, conditions, and actions may all be added by
	other models.		other models.
	An example of this is shown below, in which the BGP configuration		The example below provides an illustration of how another data model
	model in [I-D.ietf-idr-bgp-model] adds new defined sets to match on		can augment parts of this routing policy data model. It uses
	community values or AS paths. The model similarly augments BGP-		specific examples from draft-ietf-idr-bgp-model-09 to show in a
	specific conditions and actions in the corresponding sections of the		concrete manner how the different pieces fit together. This example
	routing policy model.		is not normative with respect to [I-D.ietf-idr-bgp-model]. The model
			similarly augments BGP-specific conditions and actions in the
			corresponding sections of the routing policy model.
	module: ietf-routing-policy		module: ietf-routing-policy
	+--rw routing-policy		+--rw routing-policy
	+--rw defined-sets		+--rw defined-sets
	| +--rw prefix-sets		| +--rw prefix-sets
	| | +--rw prefix-set* [name]		| | +--rw prefix-set* [name]
	| | +--rw name string		| | +--rw name string
	| | +--rw mode? enumeration		| | +--rw mode? enumeration
	| | +--rw prefixes		| | +--rw prefixes
	| | +--rw prefix-list* [ip-prefix mask-length-lower		| | +--rw prefix-list* [ip-prefix mask-length-lower
	skipping to change at page 38, line 37 ¶		skipping to change at page 38, line 37 ¶
	</routing-policy>		</routing-policy>
	</config>		</config>
	12. References		12. References
	12.1. Normative references		12.1. Normative references
	[INTF-EXT-YANG]		[INTF-EXT-YANG]
	Wilton, R., Ball, D., tapsingh@cisco.com, t., and S.		Wilton, R., Ball, D., tapsingh@cisco.com, t., and S.
	Sivaraj,, "Common Interface Extension YANG Data Models",		Sivaraj,, "Common Interface Extension YANG Data Models",
	2019, <https://datatracker.ietf.org/doc/		2019, <https://datatracker.ietf.org/doc/draft-ietf-netmod-
	draft-ietf-netmod-intf-ext-yang/>.		intf-ext-yang/>.
	[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,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,		[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
	DOI 10.17487/RFC2328, April 1998,		DOI 10.17487/RFC2328, April 1998,
	<https://www.rfc-editor.org/info/rfc2328>.		<https://www.rfc-editor.org/info/rfc2328>.
	skipping to change at page 40, line 35 ¶		skipping to change at page 40, line 35 ¶
	DOI 10.17487/RFC8349, March 2018,		DOI 10.17487/RFC8349, March 2018,
	<https://www.rfc-editor.org/info/rfc8349>.		<https://www.rfc-editor.org/info/rfc8349>.
	[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol		[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
	Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,		Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
	<https://www.rfc-editor.org/info/rfc8446>.		<https://www.rfc-editor.org/info/rfc8446>.
	[SUB-INTF-VLAN-YANG]		[SUB-INTF-VLAN-YANG]
	Wilton, R., Ball, D., tapsingh@cisco.com, t., and S.		Wilton, R., Ball, D., tapsingh@cisco.com, t., and S.
	Sivaraj, "Sub-interface VLAN YANG Data Model", 2019,		Sivaraj, "Sub-interface VLAN YANG Data Model", 2019,
	<https://datatracker.ietf.org/doc/		<https://datatracker.ietf.org/doc/draft-ietf-netmod-sub-
	draft-ietf-netmod-sub-intf-vlan-model/>.		intf-vlan-model/>.
	12.2. Informative references		12.2. Informative references
	[I-D.ietf-idr-bgp-model]		[I-D.ietf-idr-bgp-model]
	Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP		Jethanandani, M., Patel, K., Hares, S., and J. Haas, "BGP
	YANG Model for Service Provider Networks", draft-ietf-idr-		YANG Model for Service Provider Networks", draft-ietf-idr-
	bgp-model-09 (work in progress), June 2020.		bgp-model-09 (work in progress), June 2020.
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
End of changes. 7 change blocks.
	13 lines changed or deleted		15 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/