< draft-ietf-lime-yang-connectionless-oam-06.txt		draft-ietf-lime-yang-connectionless-oam-07.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 11, 2017 Q. Wu		Expires: December 18, 2017 Q. Wu
	Huawei		Huawei
	R. Rahman		R. Rahman
	S. Raghavan		S. Raghavan
	Cisco		Cisco
	June 9, 2017		June 16, 2017
	Generic YANG Data Model for Connectionless Operations, Administration,		Generic YANG Data Model for Connectionless Operations, Administration,
	and Maintenance(OAM) protocols		and Maintenance(OAM) protocols
	draft-ietf-lime-yang-connectionless-oam-06		draft-ietf-lime-yang-connectionless-oam-07
	Abstract		Abstract
	This document presents a base YANG Data model for connectionless		This document presents a base YANG Data model for connectionless
	Operations Administration, and Maintenance(OAM) protocols. It		Operations Administration, and Maintenance(OAM) protocols. It
	provides a technology-independent abstraction of key OAM constructs		provides a technology-independent abstraction of key OAM constructs
	for connectionless protocols. The base model presented here can be		for connectionless protocols. The base model presented here can be
	extended to include technology specific details. This is leading to		extended to include technology specific details. This is leading to
	uniformity between OAM protocols and support both nested OAM		uniformity between OAM protocols and support both nested OAM
	workflows (i.e., performing OAM functions at different or same levels		workflows (i.e., performing OAM functions at different or same levels
	skipping to change at page 1, line 43 ¶		skipping to change at page 1, line 43 ¶
	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 11, 2017.		This Internet-Draft will expire on December 18, 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
	skipping to change at page 2, line 20 ¶		skipping to change at page 2, line 20 ¶
	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 . . . . . . . . . . . . . . . . . . . . . . . 4
	2.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
	3. Overview of the Connectionless OAM Model . . . . . . . . . . 4		3. Overview of the Connectionless OAM Model . . . . . . . . . . 4
	3.1. TP Address . . . . . . . . . . . . . . . . . . . . . . . 5		3.1. TP Address . . . . . . . . . . . . . . . . . . . . . . . 5
	3.2. Tools . . . . . . . . . . . . . . . . . . . . . . . . . . 6		3.2. Tools . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3.3. OAM-layers . . . . . . . . . . . . . . . . . . . . . . . 6		3.3. OAM-layers . . . . . . . . . . . . . . . . . . . . . . . 5
	3.4. Test Point Locations Information . . . . . . . . . . . . 7		3.4. Test Point Locations Information . . . . . . . . . . . . 6
	3.5. Test Point Locations . . . . . . . . . . . . . . . . . . 7		3.5. Test Point Locations . . . . . . . . . . . . . . . . . . 7
	3.6. Path Discovery Data . . . . . . . . . . . . . . . . . . . 7		3.6. Path Discovery Data . . . . . . . . . . . . . . . . . . . 7
	3.7. Continuity Check Data . . . . . . . . . . . . . . . . . . 8		3.7. Continuity Check Data . . . . . . . . . . . . . . . . . . 7
	4. OAM YANG Module . . . . . . . . . . . . . . . . . . . . . . . 8		4. OAM YANG Module . . . . . . . . . . . . . . . . . . . . . . . 7
	5. Connectionless model applicability . . . . . . . . . . . . . 33		5. Connectionless model applicability . . . . . . . . . . . . . 33
	5.1. BFD Extension . . . . . . . . . . . . . . . . . . . . . . 34		5.1. BFD Extension . . . . . . . . . . . . . . . . . . . . . . 33
	5.1.1. Augment Method . . . . . . . . . . . . . . . . . . . 34		5.1.1. Augment Method . . . . . . . . . . . . . . . . . . . 33
	5.1.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 36		5.1.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 36
	5.2. LSP ping extension . . . . . . . . . . . . . . . . . . . 38		5.2. LSP ping extension . . . . . . . . . . . . . . . . . . . 38
	5.2.1. Augment Method . . . . . . . . . . . . . . . . . . . 38		5.2.1. Augment Method . . . . . . . . . . . . . . . . . . . 38
	5.2.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 39		5.2.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 39
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 41		6. Security Considerations . . . . . . . . . . . . . . . . . . . 41
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
	8. Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . 43		8. Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . 43
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 43		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
	9.1. Normative References . . . . . . . . . . . . . . . . . . 43		9.1. Normative References . . . . . . . . . . . . . . . . . . 43
	9.2. Informative References . . . . . . . . . . . . . . . . . 45		9.2. Informative References . . . . . . . . . . . . . . . . . 44
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
	1. Introduction		1. Introduction
	Operations, Administration, and Maintenance (OAM) are important		Operations, Administration, and Maintenance (OAM) are important
	networking functions that allow operators to:		networking functions that allow operators to:
	1. Monitor networks connections (Reachability Verification,		1. Monitor networks connections (Reachability Verification,
	Continuity Check).		Continuity Check).
	skipping to change at page 3, line 22 ¶		skipping to change at page 3, line 20 ¶
	verification and isolation tools, respectively, for IP networks.		verification and isolation tools, respectively, for IP networks.
	Over the years, different technologies have developed similar tools		Over the years, different technologies have developed similar tools
	for similar purposes.		for similar purposes.
	The different OAM tools may support connection-oriented technologies		The different OAM tools may support connection-oriented technologies
	or connectionless technologies. In connection-oriented technologies,		or connectionless technologies. In connection-oriented technologies,
	a connection is established prior to the transmission of data. In		a connection is established prior to the transmission of data. In
	connectionless technologies, data is typically sent between end		connectionless technologies, data is typically sent between end
	points without prior arrangement [RFC7276]. Note that the		points without prior arrangement [RFC7276]. Note that the
	Connection-Oriented OAM YANG DATA model is defined in		Connection-Oriented OAM YANG DATA model is defined in
	[I-D.ietf-lime-yang-oam-model].		[I-D.ietf-lime-yang-connection-oriented-oam-model].
	In this document, we presents a base YANG Data model for		In this document, we presents a base YANG Data model for
	connectionless OAM protocols. The generic YANG model for		connectionless OAM protocols. The generic YANG model for
	connectionless OAM only includes configuration data and state data.		connectionless OAM only includes configuration data and state data.
	It can be used in conjunction with data retrieval method model		It can be used in conjunction with data retrieval method model
	[I-D.ietf-lime-yang-connectionless-oam-methods], which focuses on		[I-D.ietf-lime-yang-connectionless-oam-methods], which focuses on
	data retrieval procedures like RPC. However it also can be used		data retrieval procedures like RPC. However it also can be used
	independently of data retrieval method model.		independently of data retrieval method model.
	2. Conventions used in this document		2. Conventions used in this document
	skipping to change at page 4, line 21 ¶		skipping to change at page 4, line 21 ¶
	MAC - Media Access Control		MAC - Media Access Control
	BFD - Bidirectional Forwarding Detection		BFD - Bidirectional Forwarding Detection
	RPC - A Remote Procedure Call, as used within the NETCONF protocol		RPC - A Remote Procedure Call, as used within the NETCONF protocol
	CC - Continuity Check [RFC7276] , Continuity Checks are used to		CC - Continuity Check [RFC7276] , Continuity Checks are used to
	verify that a destination is reachable and therefore also referred to		verify that a destination is reachable and therefore also referred to
	as reachability verification		as reachability verification
	2.2. Prefixes in Data Node Names
	In this document, names of data nodes, actions and other data model
	objects are often used without a prefix, as long as it is clear from
	the context in which YANG module each name is defined. Otherwise,
	names are prefixed using the standard prefix associated with the
	corresponding YANG module, as shown in Table 1.
	+--------+-----------------------+----------------------------------+
	| Prefix | YANG module | Reference |
	+--------+-----------------------+----------------------------------+
	| if | ietf-interfaces | [RFC7223] |
	| | | |
	| inet | ietf-inet-types | [RFC6991] |
	| | | |
	| yangmn | ietf-yang-schema- | [I-D.ietf-netmod-schema-mount] |
	| t | mount | |
	| | | |
	| nd | ietf-network | [I-D.ietf-i2rs-yang-network-topo |
	| | | ] |
	| | | |
	| ni | ietf-network-instance | [I-D.ietf-rtgwg-ni-model] |
	+--------+-----------------------+----------------------------------+
	Table 1: Prefixes and corresponding YANG modules
	3. Overview of the Connectionless OAM Model		3. Overview of the Connectionless OAM Model
	At the top of the model, there is an 'cc-oper-data' container for		At the top of the model, there is an 'cc-oper-data' container for
	session statistics. Grouping is also defined for common session		session statistics. Grouping is also defined for common session
	statistics and these are applicable for proactive OAM sessions.		statistics and these are applicable for proactive OAM sessions.
	Multiple 'test-point-locations' keyed using technology specific keys		Multiple 'test-point-locations' keyed using technology specific keys
	(eg., IPv4 address for IPv4 locations) are possible by augmented		(eg., IPv4 address for IPv4 locations) are possible by augmented
	network nodes which are defined in [I-D.ietf-i2rs-yang-network-topo]		network nodes which are defined in [I-D.ietf-i2rs-yang-network-topo]
	to describe the network hierarchies and the inventory of nodes		to describe the network hierarchies and the inventory of nodes
	contained in a network. Each 'test-point-location' is chosen based		contained in a network. Each 'test-point-location' is chosen based
	on 'location-type' which when chosen, leads to a container that		on 'location-type' which when chosen, leads to a container that
	includes a list of 'test-point-locations' keyed by technology		includes a list of 'test-point-locations' keyed by technology
	specific keys. Each test point location includes a 'test-point-		specific keys. Each test point location includes a 'test-point-
	location-info'. The 'test-point-location-info' includes 'tp-		location-info'. The 'test-point-location-info' includes 'tp-
	technology', 'tp-tools', and 'connectionless-oam-layers'. The		technology', 'tp-tools', and 'connectionless-oam-layers'. The
	skipping to change at page 8, line 27 ¶		skipping to change at page 7, line 51 ¶
	4. OAM YANG Module		4. OAM YANG Module
	<CODE BEGINS> file "ietf-connectionless-oam@2017-06-09.yang"		<CODE BEGINS> file "ietf-connectionless-oam@2017-06-09.yang"
	module ietf-connectionless-oam {		module ietf-connectionless-oam {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-connectionless-oam";		namespace "urn:ietf:params:xml:ns:yang:ietf-connectionless-oam";
	prefix coam;		prefix coam;
	import ietf-yang-schema-mount {		import ietf-yang-schema-mount {
	prefix yangmnt;		prefix yangmnt;
	}		}
	import ietf-network {		import ietf-network {
	prefix nd;		prefix nd;
	}		}
	import ietf-yang-types {		import ietf-yang-types {
	prefix yang;		prefix yang;
	}		}
	import ietf-interfaces {		import ietf-interfaces {
	prefix if;		prefix if;
	}		}
	skipping to change at page 43, line 23 ¶		skipping to change at page 43, line 23 ¶
	8. Acknowlegements		8. Acknowlegements
	The authors of this document would like to thank Greg Mirsky and		The authors of this document would like to thank Greg Mirsky and
	others for their sustainable review and comments, proposals to		others for their sustainable review and comments, proposals to
	improve and stabilize document.		improve and stabilize document.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[I-D.ietf-bfd-yang]
	Rahman, R., Zheng, L., Networks, J., Jethanandani, M., and
	G. Mirsky, "Yang Data Model for Bidirectional Forwarding
	Detection (BFD)", draft-ietf-bfd-yang-05 (work in
	progress), March 2017.
	[I-D.ietf-i2rs-yang-network-topo]
	Clemm, A., Medved, J., Varga, R., Bahadur, N.,
	Ananthakrishnan, H., and X. Liu, "A Data Model for Network
	Topologies", draft-ietf-i2rs-yang-network-topo-12 (work in
	progress), March 2017.
	[I-D.ietf-lime-yang-connectionless-oam-methods]
	Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,
	"Retrieval Methods YANG Data Model for Connectionless
	Operations, Administration, and Maintenance(OAM)
	protocols", draft-ietf-lime-yang-connectionless-oam-
	methods-04 (work in progress), June 2017.
	[I-D.ietf-lime-yang-oam-model]
	Kumar, D., Wu, Q., and Z. Wang, "Generic YANG Data Model
	for Connection Oriented Operations, Administration, and
	Maintenance(OAM) protocols", draft-ietf-lime-yang-oam-
	model-10 (work in progress), April 2017.
	[I-D.ietf-netmod-schema-mount]
	Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
	ietf-netmod-schema-mount-05 (work in progress), May 2017.
	[I-D.ietf-rtgwg-ni-model]
	Berger, L., Hopps, C., Lindem, A., and D. Bogdanovic,
	"YANG Network Instances", draft-ietf-rtgwg-ni-model-02
	(work in progress), March 2017.
	[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>.
	[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>.
	skipping to change at page 45, line 10 ¶		skipping to change at page 44, line 21 ¶
	<http://www.rfc-editor.org/info/rfc7223>.		<http://www.rfc-editor.org/info/rfc7223>.
	[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,		[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,
	September 1981.		September 1981.
	9.2. Informative References		9.2. Informative References
	[G.8013] "OAM functions and mechanisms for Ethernet based		[G.8013] "OAM functions and mechanisms for Ethernet based
	networks", ITU-T Recommendation G.8013/Y.1731, 2013.		networks", ITU-T Recommendation G.8013/Y.1731, 2013.
			[I-D.ietf-bfd-yang]
			Rahman, R., Zheng, L., Networks, J., Jethanandani, M., and
			G. Mirsky, "Yang Data Model for Bidirectional Forwarding
			Detection (BFD)", draft-ietf-bfd-yang-05 (work in
			progress), March 2017.
			[I-D.ietf-i2rs-yang-network-topo]
			Clemm, A., Medved, J., Varga, R., Bahadur, N.,
			Ananthakrishnan, H., and X. Liu, "A Data Model for Network
			Topologies", draft-ietf-i2rs-yang-network-topo-12 (work in
			progress), March 2017.
			[I-D.ietf-lime-yang-connection-oriented-oam-model]
			Kumar, D., Wu, Q., and Z. Wang, "Generic YANG Data Model
			for Connection Oriented Operations, Administration, and
			Maintenance(OAM) protocols", draft-ietf-lime-yang-
			connection-oriented-oam-model-00 (work in progress), June
			2017.
			[I-D.ietf-lime-yang-connectionless-oam-methods]
			Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,
			"Retrieval Methods YANG Data Model for Connectionless
			Operations, Administration, and Maintenance(OAM)
			protocols", draft-ietf-lime-yang-connectionless-oam-
			methods-04 (work in progress), June 2017.
			[I-D.ietf-netmod-schema-mount]
			Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
			ietf-netmod-schema-mount-05 (work in progress), May 2017.
	[I-D.ietf-spring-sr-yang]		[I-D.ietf-spring-sr-yang]
	Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG		Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
	Data Model for Segment Routing", draft-ietf-spring-sr-		Data Model for Segment Routing", draft-ietf-spring-sr-
	yang-06 (work in progress), March 2017.		yang-06 (work in progress), March 2017.
	[I-D.zheng-mpls-lsp-ping-yang-cfg]		[I-D.zheng-mpls-lsp-ping-yang-cfg]
	Zheng, L., Aldrin, S., Zheng, G., Mirsky, G., and R.		Zheng, L., Aldrin, S., Zheng, G., Mirsky, G., and R.
	Rahman, "Yang Data Model for LSP-PING", draft-zheng-mpls-		Rahman, "Yang Data Model for LSP-PING", draft-zheng-mpls-
	lsp-ping-yang-cfg-04 (work in progress), October 2016.		lsp-ping-yang-cfg-04 (work in progress), October 2016.
End of changes. 15 change blocks.
	76 lines changed or deleted		44 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/