< draft-ietf-lime-yang-connectionless-oam-methods-03.txt		draft-ietf-lime-yang-connectionless-oam-methods-04.txt >
	Network Working Group D. Kumar		Network Working Group D. Kumar
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track M. Wang		Intended status: Standards Track M. Wang
	Expires: December 1, 2017 Q. Wu		Expires: December 10, 2017 Q. Wu
	Huawei		Huawei
	R. Rahman		R. Rahman
	S. Raghavan		S. Raghavan
	Cisco		Cisco
	May 30, 2017		June 8, 2017
	Retrieval Methods YANG Data Model for Connectionless Operations,		Retrieval Methods YANG Data Model for Connectionless Operations,
	Administration, and Maintenance(OAM) protocols		Administration, and Maintenance(OAM) protocols
	draft-ietf-lime-yang-connectionless-oam-methods-03		draft-ietf-lime-yang-connectionless-oam-methods-04
	Abstract		Abstract
	This document presents a retrieval method YANG Data model for		This document presents a retrieval method YANG Data model for
	connectionless OAM protocols. It provides a technology-independent		connectionless OAM protocols. It provides a technology-independent
	RPC commands for connectionless OAM protocols. The retrieval methods		RPC commands for connectionless OAM protocols. The retrieval methods
	model presented here can be extended to include technology specific		model presented here can be extended to include technology specific
	details. This is leading to uniformity between OAM protocols and		details. This is leading to uniformity between OAM protocols and
	support both nested OAM workflows (i.e., performing OAM functions at		support both nested OAM workflows (i.e., performing OAM functions at
	different levels through a unified interface) and interactive OAM		different levels through a unified interface) and interactive OAM
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	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 December 1, 2017.		This Internet-Draft will expire on December 10, 2017.
	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
	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
	2. Conventions used in this document . . . . . . . . . . . . . . 3		2. Conventions used in this document . . . . . . . . . . . . . . 3
	2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4		2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4		2.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
	3. Overview of the Connectionless OAM retrieval methods Model . 5		3. Overview of the Connectionless OAM retrieval methods Model . 4
	3.1. RPC definitions . . . . . . . . . . . . . . . . . . . . . 5		3.1. RPC definitions . . . . . . . . . . . . . . . . . . . . . 5
	3.2. OAM Retrieval Methods Hierarchy . . . . . . . . . . . . . 8		3.2. OAM Retrieval Methods Hierarchy . . . . . . . . . . . . . 8
	4. OAM Retrieval Methods YANG Module . . . . . . . . . . . . . . 17		4. OAM Retrieval Methods YANG Module . . . . . . . . . . . . . . 17
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 20		5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 21		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
	7.1. Normative References . . . . . . . . . . . . . . . . . . 21		7.1. Normative References . . . . . . . . . . . . . . . . . . 21
	7.2. Informative References . . . . . . . . . . . . . . . . . 22		7.2. Informative References . . . . . . . . . . . . . . . . . 22
	Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 23		Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 23
	A.1. OAM Retrieval Persistent Methods YANG Module . . . . . . 23		A.1. OAM Retrieval Persistent Methods YANG Module . . . . . . 23
	skipping to change at page 3, line 23 ¶		skipping to change at page 3, line 23 ¶
	separated from the generic YANG model for connectionless OAM		separated from the generic YANG model for connectionless OAM
	[I-D.ietf-lime-yang-connectionless-oam] and can avoid mixing the		[I-D.ietf-lime-yang-connectionless-oam] and can avoid mixing the
	models for the retrieved-data from the retrieval procedures. It is		models for the retrieved-data from the retrieval procedures. It is
	expected that retrieval procedures would evolve faster than the data		expected that retrieval procedures would evolve faster than the data
	model [I-D.ietf-lime-yang-connectionless-oam] and will allow new		model [I-D.ietf-lime-yang-connectionless-oam] and will allow new
	procedures to be defined for retrieval of the same data defined by		procedures to be defined for retrieval of the same data defined by
	the base data model.		the base data model.
	2. Conventions used in this document		2. Conventions used in this document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].
	The following terms are defined in [RFC6241] and are not redefined		The following terms are defined in [RFC6241] and are not redefined
	here:		here:
	o client		o client
	o configuration data		o configuration data
	o server		o server
	o state data		o state data
	skipping to change at page 5, line 31 ¶		skipping to change at page 5, line 22 ¶
	OAM functions and define the generic RPC commands: 'continuity-check'		OAM functions and define the generic RPC commands: 'continuity-check'
	and 'path-discovery'. In practice, these commands are supported by		and 'path-discovery'. In practice, these commands are supported by
	corresponding technology-specific OAM tools [RFC7276]. For example,		corresponding technology-specific OAM tools [RFC7276]. For example,
	for the IP OAM model, the continuity-check RPC corresponds to the IP		for the IP OAM model, the continuity-check RPC corresponds to the IP
	Ping [RFC792] [RFC4443], while the path-discovery RPC command		Ping [RFC792] [RFC4443], while the path-discovery RPC command
	corresponds to IP Traceroute [RFC792] [RFC4443].		corresponds to IP Traceroute [RFC792] [RFC4443].
	Note that the RPC command presented in this document is the base		Note that the RPC command presented in this document is the base
	building block, which is used to derive a model for a technology-		building block, which is used to derive a model for a technology-
	specific OAM (i.e., ICMP ping [RFC792] [RFC4443], LSP ping		specific OAM (i.e., ICMP ping [RFC792] [RFC4443], LSP ping
	[RFC4379]), the base building block should be extended with		[RFC8029]), the base building block should be extended with
	corresponding technology specific parameters. To facilitate this and		corresponding technology specific parameters. To facilitate this and
	for future enhancements to data retrieval methods, the RPCs are		for future enhancements to data retrieval methods, the RPCs are
	captured under a separate module.		captured under a separate module.
	The generic 'path-discovery-data' and 'continuity-check-data' are		The generic 'path-discovery-data' and 'continuity-check-data' are
	used as data outputs from the different RPCs described in the		used as data outputs from the different RPCs described in the
	document. Similar methods including other RPCs can retrieve the data		document. Similar methods including other RPCs can retrieve the data
	using the same data model.		using the same data model.
	rpc continuity-check {		rpc continuity-check {
	skipping to change at page 16, line 41 ¶		skipping to change at page 16, line 31 ¶
	| | +--:(pw)		| | +--:(pw)
	| | | +--ro remote-pe-address? inet:ip-address		| | | +--ro remote-pe-address? inet:ip-address
	| | | +--ro pw-id? uint32		| | | +--ro pw-id? uint32
	| | +--:(vpls)		| | +--:(vpls)
	| | | +--ro route-distinguisher? uint32		| | | +--ro route-distinguisher? uint32
	| | | +--ro sender-ve-id? uint32		| | | +--ro sender-ve-id? uint32
	| | | +--ro receiver-ve-id? uint32		| | | +--ro receiver-ve-id? uint32
	| | +--:(mpls-mldp)		| | +--:(mpls-mldp)
	| | +--ro (root-address)?		| | +--ro (root-address)?
	| | +--:(ip-address)		| | +--:(ip-address)
	| | | +--ro source-address inet:ip-address		| | | +--ro source-address inet:ip-address
	| | | +--ro group-ip-address? IP-Multicast-		| | | +--ro group-ip-address? IP-Multicast-
	Group-Address		Group-Address
	| | +--:(vpn)		| | +--:(vpn)
	| | | +--ro as-number? inet:as-number		| | | +--ro as-number? inet:as-number
	| | +--:(global-id)		| | +--:(global-id)
	| | +--ro lsp-id? string		| | +--ro lsp-id? string
	| +--:(tlv-address)		| +--:(tlv-address)
	| | +--ro tlv-type? int16		| | +--ro tlv-type? int16
	| | +--ro tlv-len? int16		| | +--ro tlv-len? int16
	| | +--ro tlv-value? binary		| | +--ro tlv-value? binary
	skipping to change at page 17, line 32 ¶		skipping to change at page 17, line 24 ¶
	prefix if;		prefix if;
	}		}
	import ietf-connectionless-oam {		import ietf-connectionless-oam {
	prefix coam;		prefix coam;
	}		}
	organization		organization
	"IETF LIME Working Group";		"IETF LIME Working Group";
	contact		contact
	"Deepak Kumar dekumar@cisco.com		"Deepak Kumar dekumar@cisco.com
	Qin Wu bill.wu@huawei.com		Qin Wu bill.wu@huawei.com
	S Raghavan srihari@cisco.com		S Raghavan srihari@cisco.com
	Zitao Wang wangzitao@huawei.com		Zitao Wang wangzitao@huawei.com
	R Rahman rrahman@cisco.com";		R Rahman rrahman@cisco.com";
	description		description
	"This YANG module defines the RPCs for ,		"This YANG module defines the RPCs for ,
	connectionless OAM to be used within IETF		connectionless OAM to be used within IETF
	in a protocol Independent manner.		in a protocol Independent manner.
	Functional level abstraction is indendent with		Functional level abstraction is indendent with
	YANG modeling. It is assumed that each protocol maps		YANG modeling. It is assumed that each protocol maps
	corresponding abstracts to its native format.		corresponding abstracts to its native format.
	Each protocol may extend the YANG model defined		Each protocol may extend the YANG model defined
	here to include protocol specific extensions";		here to include protocol specific extensions";
	skipping to change at page 22, line 11 ¶		skipping to change at page 21, line 50 ¶
	Administration, and Maintenance(OAM) protocols", draft-		Administration, and Maintenance(OAM) protocols", draft-
	ietf-lime-yang-connectionless-oam-05 (work in progress),		ietf-lime-yang-connectionless-oam-05 (work in progress),
	May 2017.		May 2017.
	[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, "Subscribing to
	YANG datastore push updates", draft-ietf-netconf-yang-		YANG datastore push updates", draft-ietf-netconf-yang-
	push-06 (work in progress), April 2017.		push-06 (work in progress), April 2017.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,
	<http://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,		DOI 10.17487/RFC3688, January 2004,
	<http://www.rfc-editor.org/info/rfc3688>.		<http://www.rfc-editor.org/info/rfc3688>.
	[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,		DOI 10.17487/RFC6020, October 2010,
	<http://www.rfc-editor.org/info/rfc6020>.		<http://www.rfc-editor.org/info/rfc6020>.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	skipping to change at page 23, line 5 ¶		skipping to change at page 22, line 35 ¶
	"Specification of the IP Flow Information Export (IPFIX)		"Specification of the IP Flow Information Export (IPFIX)
	Protocol for the Exchange of Flow Information", STD 77,		Protocol for the Exchange of Flow Information", STD 77,
	RFC 7011, DOI 10.17487/RFC7011, September 2013,		RFC 7011, DOI 10.17487/RFC7011, September 2013,
	<http://www.rfc-editor.org/info/rfc7011>.		<http://www.rfc-editor.org/info/rfc7011>.
	[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,		[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,
	September 1981.		September 1981.
	7.2. Informative References		7.2. Informative References
	[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
	Label Switched (MPLS) Data Plane Failures", RFC 4379,
	DOI 10.17487/RFC4379, February 2006,
	<http://www.rfc-editor.org/info/rfc4379>.
	[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet		[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
	Control Message Protocol (ICMPv6) for the Internet		Control Message Protocol (ICMPv6) for the Internet
	Protocol Version 6 (IPv6) Specification", RFC 4443,		Protocol Version 6 (IPv6) Specification", RFC 4443,
	DOI 10.17487/RFC4443, March 2006,		DOI 10.17487/RFC4443, March 2006,
	<http://www.rfc-editor.org/info/rfc4443>.		<http://www.rfc-editor.org/info/rfc4443>.
	[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection		[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
	(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,		(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
	<http://www.rfc-editor.org/info/rfc5880>.		<http://www.rfc-editor.org/info/rfc5880>.
	[RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.		[RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
	Weingarten, "An Overview of Operations, Administration,		Weingarten, "An Overview of Operations, Administration,
	and Maintenance (OAM) Tools", RFC 7276,		and Maintenance (OAM) Tools", RFC 7276,
	DOI 10.17487/RFC7276, June 2014,		DOI 10.17487/RFC7276, June 2014,
	<http://www.rfc-editor.org/info/rfc7276>.		<http://www.rfc-editor.org/info/rfc7276>.
			[RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N.,
			Aldrin, S., and M. Chen, "Detecting Multiprotocol Label
			Switched (MPLS) Data-Plane Failures", RFC 8029,
			DOI 10.17487/RFC8029, March 2017,
			<http://www.rfc-editor.org/info/rfc8029>.
	Appendix A. Appendix		Appendix A. Appendix
	The following are some examples of extensions possible to the yang		The following are some examples of extensions possible to the yang
	model. The example discusses persistent methods.		model. The example discusses persistent methods.
	The persistent method RPCs are commands to trigger persistent		The persistent method RPCs are commands to trigger persistent
	continuity check or path discovery OAM while specifying the options		continuity check or path discovery OAM while specifying the options
	for data-export from the device. Internet Protocol Flow Information		for data-export from the device. Internet Protocol Flow Information
	Export (IPFIX) [RFC7011] or yang-push [I-D.ietf-netconf-yang-push].		Export (IPFIX) [RFC7011] or yang-push [I-D.ietf-netconf-yang-push].
	are currently outlined here as data export options and more can be		are currently outlined here as data export options and more can be
	added in future. It should be noted that the persistent methods are		added in future. It should be noted that the persistent methods are
	used to trigger create, modify and delete the persistent state		used to trigger create, modify and delete the persistent state
	associated with the data export options. The data export specific		associated with the data export options. The data export specific
	configurations are beyond the scope of this document.		configurations are beyond the scope of this document.
	A.1. OAM Retrieval Persistent Methods YANG Module		A.1. OAM Retrieval Persistent Methods YANG Module
	<CODE BEGINS> file "ietf-connectionless-oam-persistent-methods.yang"		module example-cl-oam-persistent-methods {
			namespace "http://example.com/cl-oam-persistent-methods";
			prefix pcoam-methods;
			import ietf-interfaces {
			prefix if;
			}
			import ietf-connectionless-oam {
			prefix coam;
			}
			import ietf-yang-types {
			prefix yang;
			}
	identity export-method {		identity export-method {
	description		description
	"Base identity to represent a conceptual export-method.";		"Base identity to represent a conceptual export-method.";
	}		}
	identity ipfix-export {		identity ipfix-export {
	base export-method;		base export-method;
	description		description
	"IPFIX based export. Configuration provided separately.";		"IPFIX based export. Configuration provided separately.";
	skipping to change at page 33, line 29 ¶		skipping to change at page 33, line 25 ¶
	"error code is ";		"error code is ";
	}		}
	leaf status-sub-code {		leaf status-sub-code {
	type uint8;		type uint8;
	description		description
	"sub code is ";		"sub code is ";
	}		}
	}		}
	}		}
	}		}
			}
	<CODE ENDS>
	Authors' Addresses		Authors' Addresses
	Deepak Kumar		Deepak Kumar
	CISCO Systems		CISCO Systems
	510 McCarthy Blvd		510 McCarthy Blvd
	Milpitas, CA 95035		Milpitas, CA 95035
	USA		USA
	Email: dekumar@cisco.com		Email: dekumar@cisco.com
End of changes. 15 change blocks.
	29 lines changed or deleted		32 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/