< draft-ietf-rtgwg-policy-model-11.txt		draft-ietf-rtgwg-policy-model-12.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: November 27, 2020 Apstra		Expires: November 30, 2020 Apstra
	A. Lindem		A. Lindem
	Cisco		Cisco
	X. Liu		X. Liu
	Volta Networks		Volta Networks
	May 26, 2020		May 29, 2020
	A YANG Data Model for Routing Policy Management		A YANG Data Model for Routing Policy Management
	draft-ietf-rtgwg-policy-model-11		draft-ietf-rtgwg-policy-model-12
	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 November 27, 2020.		This Internet-Draft will expire on November 30, 2020.
	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 3, line 42 ¶		skipping to change at page 3, line 42 ¶
	augment the current model.		augment the current model.
	2. Terminology and Notation		2. Terminology and Notation
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
			Routing Policy: A routing policy defines how routes are imported,
			exported, and modified across different routing protocols.
	The following terms are defined in [RFC8342]:		The following terms are defined in [RFC8342]:
	o client		o client
	o server		o server
	o configuration		o configuration
	o system state		o system state
	o operational state		o operational state
	o intended configuration		o intended configuration
	The following terms are defined in [RFC7950]:		The following terms are defined in [RFC7950]:
	o action		o action
	o augment		o augment
	o container		o container
	skipping to change at page 35, line 49 ¶		skipping to change at page 35, line 49 ¶
	</tag-sets>		</tag-sets>
	</defined-sets>		</defined-sets>
	<policy-definitions>		<policy-definitions>
	<policy-definition>		<policy-definition>
	<name>export-tagged-BGP</name>		<name>export-tagged-BGP</name>
	<statements>		<statements>
	<statement>		<statement>
	<name>term-0</name>		<name>term-0</name>
	<conditions>		<conditions>
	<source-protocol>bgp</source-protocol>
	<match-tag-set>		<match-tag-set>
	<tag-set>cust-tag1</tag-set>		<tag-set>cust-tag1</tag-set>
	</match-tag-set>		</match-tag-set>
	</conditions>		</conditions>
	<actions>		<actions>
	<policy-result>accept-route</policy-result>		<policy-result>accept-route</policy-result>
	</actions>		</actions>
	</statement>		</statement>
	</statements>		</statements>
	</policy-definition>		</policy-definition>
	</policy-definitions>		</policy-definitions>
	</routing-policy>		</routing-policy>
End of changes. 9 change blocks.
	7 lines changed or deleted		8 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/