< draft-ietf-lime-yang-connectionless-oam-15.txt		draft-ietf-lime-yang-connectionless-oam-16.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: May 1, 2018 Q. Wu, Ed.		Expires: May 3, 2018 Q. Wu
	Huawei		Huawei
	R. Rahman		R. Rahman
	S. Raghavan		S. Raghavan
	Cisco		Cisco
	October 28, 2017		October 30, 2017
	Generic YANG Data Model for the Management of Operations,		Generic YANG Data Model for the Management of Operations,
	Administration, and Maintenance (OAM) Protocols that use Connectionless		Administration, and Maintenance (OAM) Protocols that use Connectionless
	Communications		Communications
	draft-ietf-lime-yang-connectionless-oam-15		draft-ietf-lime-yang-connectionless-oam-16
	Abstract		Abstract
	This document presents a base YANG Data model for Operations		This document presents a base YANG Data model for Operations
	Administration, and Maintenance(OAM) protocols that use		Administration, and Maintenance(OAM) protocols that use
	Connectionless Communications. The data model is defined using the		Connectionless Communications. The data model is defined using the
	YANG in RFC7950 data modeling language. It provides a technology-		YANG in RFC7950 data modeling language. It provides a technology-
	independent abstraction of key OAM constructs for OAM protocols that		independent abstraction of key OAM constructs for OAM protocols that
	use connectionless communication. The base model presented here can		use connectionless communication. The base model presented here can
	be extended to include technology specific details. This is leading		be extended to include technology specific details. This is leading
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 May 1, 2018.		This Internet-Draft will expire on May 3, 2018.
	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
	(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 35 ¶		skipping to change at page 2, line 35 ¶
	2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5		2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Overview of the Connectionless OAM Model . . . . . . . . . . 5		3. Overview of the Connectionless OAM Model . . . . . . . . . . 5
	3.1. TP Address . . . . . . . . . . . . . . . . . . . . . . . 6		3.1. TP Address . . . . . . . . . . . . . . . . . . . . . . . 6
	3.2. Tools . . . . . . . . . . . . . . . . . . . . . . . . . . 6		3.2. Tools . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3.3. OAM neighboring test points . . . . . . . . . . . . . . . 7		3.3. OAM neighboring test points . . . . . . . . . . . . . . . 7
	3.4. Test Point Locations Information . . . . . . . . . . . . 8		3.4. Test Point Locations Information . . . . . . . . . . . . 8
	3.5. Test Point Locations . . . . . . . . . . . . . . . . . . 8		3.5. Test Point Locations . . . . . . . . . . . . . . . . . . 8
	3.6. Path Discovery Data . . . . . . . . . . . . . . . . . . . 9		3.6. Path Discovery Data . . . . . . . . . . . . . . . . . . . 9
	3.7. Continuity Check Data . . . . . . . . . . . . . . . . . . 9		3.7. Continuity Check Data . . . . . . . . . . . . . . . . . . 9
	3.8. OAM data hierarchy . . . . . . . . . . . . . . . . . . . 9		3.8. OAM data hierarchy . . . . . . . . . . . . . . . . . . . 9
	4. LIME Common Types YANG Module . . . . . . . . . . . . . . . . 12		4. LIME Time Types YANG Module . . . . . . . . . . . . . . . . . 12
	5. Connectionless OAM YANG Module . . . . . . . . . . . . . . . 14		5. Connectionless OAM YANG Module . . . . . . . . . . . . . . . 14
	6. Connectionless model applicability . . . . . . . . . . . . . 42		6. Connectionless model applicability . . . . . . . . . . . . . 42
	6.1. BFD Extension . . . . . . . . . . . . . . . . . . . . . . 43		6.1. BFD Extension . . . . . . . . . . . . . . . . . . . . . . 43
	6.1.1. Augment Method . . . . . . . . . . . . . . . . . . . 43		6.1.1. Augment Method . . . . . . . . . . . . . . . . . . . 43
	6.1.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 46		6.1.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 46
	6.2. LSP ping extension . . . . . . . . . . . . . . . . . . . 48		6.2. LSP ping extension . . . . . . . . . . . . . . . . . . . 48
	6.2.1. Augment Method . . . . . . . . . . . . . . . . . . . 48		6.2.1. Augment Method . . . . . . . . . . . . . . . . . . . 48
	6.2.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 49		6.2.2. Schema Mount . . . . . . . . . . . . . . . . . . . . 49
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 51		7. Security Considerations . . . . . . . . . . . . . . . . . . . 51
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53
	skipping to change at page 6, line 36 ¶		skipping to change at page 6, line 36 ¶
	With connectionless OAM protocols, the TP address can be one of the		With connectionless OAM protocols, the TP address can be one of the
	following types:		following types:
	o MAC address [RFC6136] at link layer for TPs		o MAC address [RFC6136] at link layer for TPs
	o IPv4 or IPv6 address at IP layer for TPs		o IPv4 or IPv6 address at IP layer for TPs
	o TP-attribute identifying a TP associated with an application layer		o TP-attribute identifying a TP associated with an application layer
	function		function
	o Router-id to represent the device or node.		o Router-id to represent the device or node, which is commonly used
	[I-D.ietf-spring-sr-yang]		to identify nodes in routing and other control plane
			protocols.[I-D.ietf-rtgwg-routing-types]
	To define a forwarding treatment of a test packet, the 'tp-address'		To define a forwarding treatment of a test packet, the 'tp-address'
	grouping needs to be associated with additional parameters, e.g.,		grouping needs to be associated with additional parameters, e.g.,
	DSCP for IP or EXP (renamed to Traffic Classic in [RFC5462]) for		DSCP for IP or EXP (renamed to Traffic Classic in [RFC5462]) for
	MPLS. In generic connectionless OAM YANG model, these parameters are		MPLS. In generic connectionless OAM YANG model, these parameters are
	not explicitly configured. The model user can add corresponding		not explicitly configured. The model user can add corresponding
	parameters according to their requirements.		parameters according to their requirements.
	3.2. Tools		3.2. Tools
	skipping to change at page 12, line 41 ¶		skipping to change at page 12, line 41 ¶
	| +--rw mac-address-location? yang:mac-address		| +--rw mac-address-location? yang:mac-address
	+--:(ipv4-address)		+--:(ipv4-address)
	| +--rw ipv4-address-location? inet:ipv4-address		| +--rw ipv4-address-location? inet:ipv4-address
	+--:(ipv6-address)		+--:(ipv6-address)
	| +--rw ipv6-address-location? inet:ipv6-address		| +--rw ipv6-address-location? inet:ipv6-address
	+--:(as-number)		+--:(as-number)
	| +--rw as-number-location? inet:as-number		| +--rw as-number-location? inet:as-number
	+--:(router-id)		+--:(router-id)
	+--rw router-id-location? rt:router-id		+--rw router-id-location? rt:router-id
	4. LIME Common Types YANG Module		4. LIME Time Types YANG Module
	<CODE BEGINS> file "ietf-lime-common-types@2017-09-06.yang"		<CODE BEGINS> file "ietf-lime-time-types@2017-09-06.yang"
	module ietf-lime-common-types {		module ietf-lime-time-types {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-lime-common-types";		namespace "urn:ietf:params:xml:ns:yang:ietf-lime-time-types";
	prefix "lime";		prefix "lime";
	organization		organization
	"IETF Layer Independent OAM Management(LIME)		"IETF Layer Independent OAM Management(LIME)
	Working Group";		Working Group";
	contact		contact
	"WG Web: <https://datatracker.ietf.org/wg/lime>		"WG Web: <https://datatracker.ietf.org/wg/lime>
	WG List: <mailto:lmap@ietf.org>		WG List: <mailto:lmap@ietf.org>
	Editor: Qin Wu		Editor: Qin Wu
	<bill.wu@huawei.com>";		<bill.wu@huawei.com>";
	description		description
	"This module provides common definitions used by the data		"This module provides time related definitions used by the data
	models written for Layer Independent OAM Management(LIME).		models written for Layer Independent OAM Management(LIME).
	This module defines identities but no schema tree elements.";		This module defines identities but no schema tree elements.";
	revision "2017-09-06" {		revision "2017-09-06" {
	description		description
	"Initial version";		"Initial version";
	reference		reference
	"RFC xxxx: A YANG Data Model for OAM Protocols that use Connectionless		"RFC xxxx: A YANG Data Model for OAM Protocols that use Connectionless
	Communications";		Communications";
	}		}
	skipping to change at page 15, line 24 ¶		skipping to change at page 15, line 24 ¶
	}		}
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	}		}
	import ietf-network-instance {		import ietf-network-instance {
	prefix ni;		prefix ni;
	}		}
	import ietf-routing-types {		import ietf-routing-types {
	prefix rt;		prefix rt;
	}		}
	import ietf-lime-common-types {		import ietf-lime-time-types {
	prefix lime;		prefix lime;
	}		}
	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";
	skipping to change at page 53, line 14 ¶		skipping to change at page 53, line 14 ¶
	/coam:cc-session-statistics-data/cl-oam:cc-ipv6-sessions-		/coam:cc-session-statistics-data/cl-oam:cc-ipv6-sessions-
	statistics/cl-oam:cc-session-statistics/cl-oam:session-admin-down-		statistics/cl-oam:cc-session-statistics/cl-oam:session-admin-down-
	count/		count/
	8. IANA Considerations		8. IANA Considerations
	This document registers a URI in the IETF XML registry [RFC3688].		This document registers a URI in the IETF XML registry [RFC3688].
	Following the format in [RFC3688] the following registration is		Following the format in [RFC3688] the following registration is
	requested to be made:		requested to be made:
	URI: urn:ietf:params:xml:ns:yang:ietf-lime-common-types		URI: urn:ietf:params:xml:ns:yang:ietf-lime-time-types
	Registrant Contact: The IESG.		Registrant Contact: The IESG.
	XML: N/A; the requested URI is an XML namespace.		XML: N/A; the requested URI is an XML namespace.
	URI: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam		URI: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam
	Registrant Contact: The IESG.		Registrant Contact: The IESG.
	XML: N/A, the requested URI is an XML namespace.		XML: N/A, the requested URI is an XML namespace.
	This document registers a YANG module in the YANG Module Names		This document registers a YANG module in the YANG Module Names
	registry [RFC7950].		registry [RFC7950].
	Name: ietf-lime-common-types		Name: ietf-lime-common-types
	Namespace: urn:ietf:params:xml:ns:yang:ietf-lime-common-types		Namespace: urn:ietf:params:xml:ns:yang:ietf-lime-time-types
	Prefix: lime		Prefix: lime
	Reference: RFC XXXX		Reference: RFC XXXX
	Name: ietf-connectionless-oam		Name: ietf-connectionless-oam
	Namespace: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam		Namespace: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam
	Prefix: cl-oam		Prefix: cl-oam
	Reference: RFC XXXX		Reference: RFC XXXX
	9. Acknowlegements		9. Acknowlegements
	The authors of this document would like to thank Elwyn Davies, Alia		The authors of this document would like to thank Elwyn Davies, Alia
	Atlas,Brian E Carpenter,Greg Mirsky,Adam Roach,Alissa Cooper,Eric		Atlas,Brian E Carpenter,Greg Mirsky,Adam Roach,Alissa Cooper,Eric
	skipping to change at page 54, line 5 ¶		skipping to change at page 54, line 5 ¶
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[I-D.ietf-i2rs-yang-network-topo]		[I-D.ietf-i2rs-yang-network-topo]
	Clemm, A., Medved, J., Varga, R., Bahadur, N.,		Clemm, A., Medved, J., Varga, R., Bahadur, N.,
	Ananthakrishnan, H., and X. Liu, "A Data Model for Network		Ananthakrishnan, H., and X. Liu, "A Data Model for Network
	Topologies", draft-ietf-i2rs-yang-network-topo-17 (work in		Topologies", draft-ietf-i2rs-yang-network-topo-17 (work in
	progress), October 2017.		progress), October 2017.
			[I-D.ietf-rtgwg-ni-model]
			Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X.
			Liu, "YANG Network Instances", draft-ietf-rtgwg-ni-
			model-04 (work in progress), September 2017.
	[I-D.ietf-rtgwg-routing-types]		[I-D.ietf-rtgwg-routing-types]
	Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,		Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
	"Routing Area Common YANG Data Types", draft-ietf-rtgwg-		"Routing Area Common YANG Data Types", draft-ietf-rtgwg-
	routing-types-17 (work in progress), October 2017.		routing-types-17 (work in progress), October 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,
	<https://www.rfc-editor.org/info/rfc3688>.		<https://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
	skipping to change at page 55, line 52 ¶		skipping to change at page 56, line 10 ¶
	for Connection Oriented Operations, Administration, and		for Connection Oriented Operations, Administration, and
	Maintenance(OAM) protocols", draft-ietf-lime-yang-		Maintenance(OAM) protocols", draft-ietf-lime-yang-
	connection-oriented-oam-model-00 (work in progress), June		connection-oriented-oam-model-00 (work in progress), June
	2017.		2017.
	[I-D.ietf-lime-yang-connectionless-oam-methods]		[I-D.ietf-lime-yang-connectionless-oam-methods]
	Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,		Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,
	"Retrieval Methods YANG Data Model for Connectionless		"Retrieval Methods YANG Data Model for Connectionless
	Operations, Administration, and Maintenance(OAM)		Operations, Administration, and Maintenance(OAM)
	protocols", draft-ietf-lime-yang-connectionless-oam-		protocols", draft-ietf-lime-yang-connectionless-oam-
	methods-11 (work in progress), October 2017.		methods-12 (work in progress), October 2017.
	[I-D.ietf-netmod-schema-mount]		[I-D.ietf-netmod-schema-mount]
	Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-		Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
	ietf-netmod-schema-mount-08 (work in progress), October		ietf-netmod-schema-mount-08 (work in progress), October
	2017.		2017.
	[I-D.ietf-rtgwg-ni-model]
	Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X.
	Liu, "YANG Network Instances", draft-ietf-rtgwg-ni-
	model-04 (work in progress), September 2017.
	[I-D.ietf-spring-sr-yang]
	Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
	Data Model for Segment Routing", draft-ietf-spring-sr-
	yang-07 (work in progress), July 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-05 (work in progress), June 2017.		lsp-ping-yang-cfg-06 (work in progress), October 2017.
	[IEEE.1588]		[IEEE.1588]
	"IEEE Standard for a Precision Clock Synchronization		"IEEE Standard for a Precision Clock Synchronization
	Protocol for Networked Measurement and Control Systems",		Protocol for Networked Measurement and Control Systems",
	IEEE IEEE Std 1588-2008, 2008.		IEEE IEEE Std 1588-2008, 2008.
	[RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching		[RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching
	(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic		(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
	Class" Field", RFC 5462, DOI 10.17487/RFC5462, February		Class" Field", RFC 5462, DOI 10.17487/RFC5462, February
	2009, <https://www.rfc-editor.org/info/rfc5462>.		2009, <https://www.rfc-editor.org/info/rfc5462>.
	skipping to change at page 57, line 4 ¶		skipping to change at page 56, line 45 ¶
	DOI 10.17487/RFC6136, March 2011,		DOI 10.17487/RFC6136, March 2011,
	<https://www.rfc-editor.org/info/rfc6136>.		<https://www.rfc-editor.org/info/rfc6136>.
	[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,
	<https://www.rfc-editor.org/info/rfc7276>.		<https://www.rfc-editor.org/info/rfc7276>.
	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
	Michael Wang		Michael Wang
	Huawei Technologies,Co.,Ltd		Huawei Technologies,Co.,Ltd
	101 Software Avenue, Yuhua District		101 Software Avenue, Yuhua District
	Nanjing 210012		Nanjing 210012
	China		China
	Email: wangzitao@huawei.com		Email: wangzitao@huawei.com
	Qin Wu (editor)		Qin Wu
	Huawei		Huawei
	101 Software Avenue, Yuhua District		101 Software Avenue, Yuhua District
	Nanjing, Jiangsu 210012		Nanjing, Jiangsu 210012
	China		China
	Email: bill.wu@huawei.com		Email: bill.wu@huawei.com
	Reshad Rahman		Reshad Rahman
	Cisco Systems		Cisco Systems
	2000 Innovation Drive		2000 Innovation Drive
End of changes. 21 change blocks.
	33 lines changed or deleted		29 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/