< draft-ietf-lime-yang-connectionless-oam-methods-10.txt		draft-ietf-lime-yang-connectionless-oam-methods-11.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: April 26, 2018 Q. Wu		Expires: April 27, 2018 Q. Wu
	Huawei		Huawei
	R. Rahman		R. Rahman
	S. Raghavan		S. Raghavan
	Cisco		Cisco
	October 23, 2017		October 24, 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-10		draft-ietf-lime-yang-connectionless-oam-methods-11
	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 technology-independent RPC		connectionless OAM protocols. It provides technology-independent RPC
	operations for connectionless OAM protocols. The retrieval methods		operations 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 interacting OAM		different levels through a unified interface) and interacting 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 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 April 26, 2018.		This Internet-Draft will expire on April 27, 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 16, line 28 ¶		skipping to change at page 16, line 28 ¶
	description		description
	"A generic protocol identifier.";		"A generic protocol identifier.";
	}		}
	identity protocol-id-internet {		identity protocol-id-internet {
	base protocol-id;		base protocol-id;
	description		description
	"Internet Protocols.";		"Internet Protocols.";
	}		}
	identity protocol-id-propreitary {		identity protocol-id-proprietary {
	base protocol-id;		base protocol-id;
	description		description
	"Propreitary protocol (e.g.,IP SLA).";		"Proprietary protocol (e.g.,IP SLA).";
	}		}
	identity protocol-id-sfc {		identity protocol-id-sfc {
	base protocol-id;		base protocol-id;
	description		description
	"Service Function Chaining.";		"Service Function Chaining.";
	}		}
	identity protocol-id-mpls {		identity protocol-id-mpls {
	base protocol-id;		base protocol-id;
	skipping to change at page 22, line 21 ¶		skipping to change at page 22, line 21 ¶
	Some of the RPC operations in this YANG module may be considered		Some of the RPC operations in this YANG module may be considered
	sensitive or vulnerable in some network environments. It is thus		sensitive or vulnerable in some network environments. It is thus
	important to control access to these operations. These are the		important to control access to these operations. These are the
	operations and their sensitivity/vulnerability:		operations and their sensitivity/vulnerability:
	o continuity-check: Generates continuity check.		o continuity-check: Generates continuity check.
	o path-discovery: Generates path discovery.		o path-discovery: Generates path discovery.
	which may lead to Denial-of-Service attack on both the local device		These operations are used to retrieve the data from the device that
	and the network or unauthorized source access to some sensitive		need to execute the OAM command. Unauthorized source access to some
	information.		sensitive information in the above data may lead to Denial-of-Service
			attack on both the local device and the network.
	6. IANA Considerations		6. 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-connectionless-oam-methods		URI: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam-methods
	Registrant Contact: The IESG.		Registrant Contact: The IESG.
	skipping to change at page 23, line 11 ¶		skipping to change at page 23, line 11 ¶
	prefix: cloam-methods		prefix: cloam-methods
	reference: RFC XXXX		reference: RFC XXXX
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[I-D.ietf-lime-yang-connectionless-oam]		[I-D.ietf-lime-yang-connectionless-oam]
	Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,		Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,
	"Generic YANG Data Model for Connectionless Operations,		"Generic YANG Data Model for Operations, Administration,
	Administration, and Maintenance(OAM) protocols", draft-		and Maintenance(OAM) protocols for Connectionless
	ietf-lime-yang-connectionless-oam-11 (work in progress),		networks", draft-ietf-lime-yang-connectionless-oam-13
	September 2017.		(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>.
	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security		[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
	(TLS) Protocol Version 1.2", RFC 5246,		(TLS) Protocol Version 1.2", RFC 5246,
	DOI 10.17487/RFC5246, August 2008,		DOI 10.17487/RFC5246, August 2008,
	<https://www.rfc-editor.org/info/rfc5246>.		<https://www.rfc-editor.org/info/rfc5246>.
	skipping to change at page 26, line 30 ¶		skipping to change at page 26, line 30 ¶
	}		}
	identity yang-push-export {		identity yang-push-export {
	base export-method;		base export-method;
	description		description
	"Yang-push from draft-ietf-netconf-yang-push";		"Yang-push from draft-ietf-netconf-yang-push";
	}		}
	identity protocol-id {		identity protocol-id {
	description		description
	"A generic protocol identifier.";		"A generic protocol identifier.";
	}		}
	identity status-code{		identity status-code {
	description		description
	"Base status code";		"Base status code";
	}		}
	identity invalid-cc{		identity invalid-cc {
	base status-code;		base status-code;
	description		description
	"Indicates that the Continuity check message is invalid";		"Indicates that the Continuity check message is invalid";
	}		}
	identity invalid-pd {		identity invalid-pd {
	base status-code;		base status-code;
	description		description
	"Indicates that the path discovery message is invalid";		"Indicates that the path discovery message is invalid";
	}		}
End of changes. 10 change blocks.
	15 lines changed or deleted		16 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/