< draft-ietf-netmod-nmda-diff-06.txt		draft-ietf-netmod-nmda-diff-07.txt >
	Network Working Group A. Clemm		Network Working Group A. Clemm
	Internet-Draft Y. Qu		Internet-Draft Y. Qu
	Intended status: Standards Track Futurewei		Intended status: Standards Track Futurewei
	Expires: March 22, 2021 J. Tantsura		Expires: March 29, 2021 J. Tantsura
	Apstra		Apstra
	A. Bierman		A. Bierman
	YumaWorks		YumaWorks
	September 18, 2020		September 25, 2020
	Comparison of NMDA datastores		Comparison of NMDA datastores
	draft-ietf-netmod-nmda-diff-06		draft-ietf-netmod-nmda-diff-07
	Abstract		Abstract
	This document defines an RPC operation to compare management		This document defines an RPC operation to compare management
	datastores that comply with the NMDA architecture.		datastores that comply with the NMDA architecture.
	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 35 ¶		skipping to change at page 1, line 35 ¶
	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 March 22, 2021.		This Internet-Draft will expire on March 29, 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 2, line 19 ¶		skipping to change at page 2, line 19 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Key Words . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Key Words . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3		3. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 3
	4. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 4		4. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 4
	5. YANG Data Model . . . . . . . . . . . . . . . . . . . . . . . 6		5. YANG Data Model . . . . . . . . . . . . . . . . . . . . . . . 6
	6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 10		6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
	7. Performance Considerations . . . . . . . . . . . . . . . . . 14		7. Performance Considerations . . . . . . . . . . . . . . . . . 14
	8. Possible Future Extensions . . . . . . . . . . . . . . . . . 15		8. Possible Future Extensions . . . . . . . . . . . . . . . . . 15
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
	9.1. Updates to the IETF XML Registry . . . . . . . . . . . . 15		9.1. Updates to the IETF XML Registry . . . . . . . . . . . . 15
	9.2. Updates to the YANG Module Names Registry . . . . . . . . 15		9.2. Updates to the YANG Module Names Registry . . . . . . . . 16
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 16		10. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
	12.1. Normative References . . . . . . . . . . . . . . . . . . 17		12.1. Normative References . . . . . . . . . . . . . . . . . . 17
	12.2. Informative References . . . . . . . . . . . . . . . . . 18		12.2. Informative References . . . . . . . . . . . . . . . . . 18
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
	1. Introduction		1. Introduction
	The revised Network Management Datastore Architecture (NMDA)		The revised Network Management Datastore Architecture (NMDA)
	[RFC8342] introduces a set of new datastores that each hold YANG-		[RFC8342] introduces a set of new datastores that each hold YANG-
	defined data [RFC7950] and represent a different "viewpoint" on the		defined data [RFC7950] and represent a different "viewpoint" on the
	data that is maintained by a server. New YANG datastores that are		data that is maintained by a server. New YANG datastores that are
	skipping to change at page 9, line 27 ¶		skipping to change at page 9, line 27 ¶
	target datastore to retrieve.";		target datastore to retrieve.";
	reference "RFC 6241, Section 6.";		reference "RFC 6241, Section 6.";
	}		}
	leaf xpath-filter {		leaf xpath-filter {
	if-feature nc:xpath;		if-feature nc:xpath;
	type yang:xpath1.0;		type yang:xpath1.0;
	description		description
	"This parameter contains an XPath expression		"This parameter contains an XPath expression
	identifying the portions of the target		identifying the portions of the target
	datastore to retrieve.";		datastore to retrieve.";
	reference "RFC 6021: Common YANG Data Types";		reference "RFC 6991: Common YANG Data Types";
	}		}
	}		}
	}		}
	output {		output {
	choice compare-response {		choice compare-response {
	description		description
	"Comparison results.";		"Comparison results.";
	leaf no-matches {		leaf no-matches {
	type empty;		type empty;
	description		description
	skipping to change at page 13, line 26 ¶		skipping to change at page 13, line 26 ¶
	<edit>		<edit>
	<edit-id>1</edit-id>		<edit-id>1</edit-id>
	<operation>replace</operation>		<operation>replace</operation>
	<target>/ietf-interfaces:interface=eth0/enabled</target>		<target>/ietf-interfaces:interface=eth0/enabled</target>
	<value>		<value>
	<if:enabled>false<if:enabled>		<if:enabled>false<if:enabled>
	</value>		</value>
	<source-value>		<source-value>
	<if:enabled or:origin="or:learned">true</if:enabled>		<if:enabled or:origin="or:learned">true</if:enabled>
	</source-value>		</source-value>
			</edit>
			<edit>
	<edit-id>2</edit-id>		<edit-id>2</edit-id>
	<operation>create</operation>		<operation>create</operation>
	<target>/ietf-interfaces:interface=eth0/description</target>		<target>/ietf-interfaces:interface=eth0/description</target>
	<value>		<value>
	<if:description>ip interface<description>		<if:description>ip interface<description>
	</value>		</value>
	</edit>		</edit>
	</yang-patch>		</yang-patch>
	</differences>		</differences>
	</rpc-reply>		</rpc-reply>
	skipping to change at page 14, line 28 ¶		skipping to change at page 14, line 29 ¶
	"target" : "/ietf-interfaces:interface=eth0/enabled",		"target" : "/ietf-interfaces:interface=eth0/enabled",
	"value" : {		"value" : {
	"ietf-interfaces:interface/enabled" : "false"		"ietf-interfaces:interface/enabled" : "false"
	},		},
	"source-value" : {		"source-value" : {
	"ietf-interfaces:interface/enabled" : "true",		"ietf-interfaces:interface/enabled" : "true",
	"@ietf-interfaces:interface/enabled" : {		"@ietf-interfaces:interface/enabled" : {
	"ietf-origin:origin" : "ietf-origin:learned"		"ietf-origin:origin" : "ietf-origin:learned"
	}		}
	}		}
			},
			{
	"edit-id" : "2",		"edit-id" : "2",
	"operation" : "create",		"operation" : "create",
	"target" : "/ietf-interfaces:interface=eth0/description",		"target" : "/ietf-interfaces:interface=eth0/description",
	"value" : {		"value" : {
	"ietf-interface:interface/description" : "ip interface"		"ietf-interface:interface/description" : "ip interface"
	}		}
	}		}
	]		]
	}		}
	}		}
End of changes. 9 change blocks.
	8 lines changed or deleted		12 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/