< draft-ooamdt-rtgwg-ooam-requirement-00.txt		draft-ooamdt-rtgwg-ooam-requirement-01.txt >
	rtgwg N. Kumar		rtgwg N. Kumar
	Internet-Draft C. Pignataro		Internet-Draft C. Pignataro
	Intended status: Informational D. Kumar		Intended status: Informational D. Kumar
	Expires: September 22, 2016 Cisco Systems, Inc.		Expires: November 26, 2016 Cisco Systems, Inc.
	G. Mirsky		G. Mirsky
	Ericsson		Ericsson
	M. Chen		M. Chen
	Huawei Technologies		Huawei Technologies
	E. Nordmark		E. Nordmark
	Arista Networks		Arista Networks
	S. Pallagatti		S. Pallagatti
	Juniper Networks		Juniper Networks
	D. Mozes		D. Mozes
	Mellanox Technologies Ltd		Mellanox Technologies Ltd
	March 21, 2016		May 25, 2016
	Overlay OAM Requirements		Overlay OAM Requirements
	draft-ooamdt-rtgwg-ooam-requirement-00		draft-ooamdt-rtgwg-ooam-requirement-01
	Abstract		Abstract
	This document describes a list of functional requirements for		This document describes a list of functional requirements for
	Operations Administration and Maintenance (OAM) in various Overlay		Operations Administration and Maintenance (OAM) in various Overlay
	and Service networks like Service Function Chaining (SFC), Bit Index		and Service networks like Service Function Chaining (SFC), Bit Index
	Explicit Replication (BIER), Network Virtualization over Layer 3		Explicit Replication (BIER), Network Virtualization over Layer 3
	(NVO3).		(NVO3).
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	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 September 22, 2016.		This Internet-Draft will expire on November 26, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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 33 ¶		skipping to change at page 2, line 33 ¶
	2. Requirements notation . . . . . . . . . . . . . . . . . . . . 3		2. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
	3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. Detailed Requirement List . . . . . . . . . . . . . . . . . . 4		4. Detailed Requirement List . . . . . . . . . . . . . . . . . . 4
	4.1. Fault Management . . . . . . . . . . . . . . . . . . . . 5		4.1. Fault Management . . . . . . . . . . . . . . . . . . . . 5
	4.1.1. Pro-active Fault Management . . . . . . . . . . . . . 5		4.1.1. Pro-active Fault Management . . . . . . . . . . . . . 5
	4.1.2. On-demand Fault Management . . . . . . . . . . . . . 5		4.1.2. On-demand Fault Management . . . . . . . . . . . . . 5
	4.2. Performance Management . . . . . . . . . . . . . . . . . 5		4.2. Performance Management . . . . . . . . . . . . . . . . . 5
	4.3. Alarm Indication Suppression . . . . . . . . . . . . . . 6		4.3. Alarm Indication Suppression . . . . . . . . . . . . . . 6
	4.4. Overlay Network Resiliency . . . . . . . . . . . . . . . 6		4.4. Overlay Network Resiliency . . . . . . . . . . . . . . . 6
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 6		6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7		7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	8.1. Normative References . . . . . . . . . . . . . . . . . . 7		8.1. Normative References . . . . . . . . . . . . . . . . . . 7
	8.2. Informative References . . . . . . . . . . . . . . . . . 8		8.2. Informative References . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	We have witnessed and participated in design of new paradigms in the		We have witnessed and participated in design of new paradigms in the
	networking that are aimed to address network virtualization, service		networking that are aimed to address network virtualization, service
	function chaining, and multicast services. New paradigms require new		function chaining, and multicast services. New paradigms require new
	architectural concepts, principles and components. [RFC7365] defines		architectural concepts, principles and components. [RFC7365] defines
	a framework for Data Center Network Virtualization over Layer 3		a framework for Data Center Network Virtualization over Layer 3
	(NVO3). [RFC7665] describes the architecture for creating and		(NVO3). [RFC7665] describes the architecture for creating and
	maintaining Service Function Chains (SFCs) in a network.		maintaining Service Function Chains (SFCs) in a network.
	skipping to change at page 4, line 26 ¶		skipping to change at page 4, line 26 ¶
	4. Detailed Requirement List		4. Detailed Requirement List
	This section list the OAM requirement for different Overlay networks.		This section list the OAM requirement for different Overlay networks.
	The below listed requirement MUST be supported with any underlay		The below listed requirement MUST be supported with any underlay
	transport network:		transport network:
	REQ#1: The listed requirements MUST be supported with any type of		REQ#1: The listed requirements MUST be supported with any type of
	transport layer over which the overlay network can be		transport layer over which the overlay network can be
	realized		realized
	REQ#2: It MUST be possible to initialize Overlay OAM session from		REQ#2: It MUST be possible to initialize Overlay OAM session between
	any node in the overlay network.		any node in the overlay network.
	REQ#3: It SHOULD be possible to initialize an Overlay OAM session		REQ#3: It SHOULD be possible to initialize an Overlay OAM session
	from a centralized controller.		from a centralized controller.
	REQ#4: Overlay OAM MUST support proactive and on-demand OAM		REQ#4: Overlay OAM MUST support proactive and on-demand OAM
	monitoring and measurement methods.		monitoring and measurement methods.
	REQ#5: Overlay OAM MUST support unidirectional OAM methods, both		REQ#5: Overlay OAM MUST support unidirectional OAM methods, both
	continuity check and performance measurement.		continuity check and performance measurement.
	skipping to change at page 5, line 44 ¶		skipping to change at page 5, line 44 ¶
	REQ#14: Overlay OAM MUST have the ability to discover and exercise		REQ#14: Overlay OAM MUST have the ability to discover and exercise
	equal cost multipath (ECMP) paths in its transport network.		equal cost multipath (ECMP) paths in its transport network.
	REQ#15: Overlay OAM MUST be able to trigger on-demand FM with		REQ#15: Overlay OAM MUST be able to trigger on-demand FM with
	responses being directed towards initiator of such proxy		responses being directed towards initiator of such proxy
	request.		request.
	4.2. Performance Management		4.2. Performance Management
			This section lists both active and passive mode of performance
			measurement. Section 3.4 and Section 3.5 of [RFC7799] defines the
			definition for Active and Passive mode of Performance Measurement.
	REQ#16: Overlay OAM MUST support active one-way packet delay		REQ#16: Overlay OAM MUST support active one-way packet delay
	measurement.		measurement.
	REQ#17: Overlay OAM MUST support passive one-way packet delay		REQ#17: Overlay OAM MUST support passive one-way packet delay
	measurement.		measurement.
	REQ#18: Overlay OAM MUST support active two-way packet delay		REQ#18: Overlay OAM MUST support active two-way packet delay
	measurement.		measurement.
	REQ#19: Overlay OAM MUST support packet delay variation measurement.		REQ#19: Overlay OAM MUST support packet delay variation measurement.
	skipping to change at page 7, line 7 ¶		skipping to change at page 7, line 12 ¶
	This document does not propose any IANA consideration.		This document does not propose any IANA consideration.
	6. Security Considerations		6. Security Considerations
	This document list the OAM requirement for various Overlay network		This document list the OAM requirement for various Overlay network
	and does not raise any security considerations.		and does not raise any security considerations.
	7. Acknowledgement		7. Acknowledgement
	TBD		The Authors would like to thank Ron Bonico for his review and
			comments.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-bier-architecture]		[I-D.ietf-bier-architecture]
	Wijnands, I., Rosen, E., Dolganow, A., P, T., and S.		Wijnands, I., Rosen, E., Dolganow, A., Przygienda, A., and
	Aldrin, "Multicast using Bit Index Explicit Replication",		S. Aldrin, "Multicast using Bit Index Explicit
	draft-ietf-bier-architecture-03 (work in progress),		Replication", draft-ietf-bier-architecture-03 (work in
	January 2016.		progress), January 2016.
	[I-D.ietf-bier-mpls-encapsulation]		[I-D.ietf-bier-mpls-encapsulation]
	Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., and		Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., and
	S. Aldrin, "Encapsulation for Bit Index Explicit		S. Aldrin, "Encapsulation for Bit Index Explicit
	Replication in MPLS Networks", draft-ietf-bier-mpls-		Replication in MPLS Networks", draft-ietf-bier-mpls-
	encapsulation-03 (work in progress), February 2016.		encapsulation-04 (work in progress), April 2016.
	[I-D.ietf-nvo3-vxlan-gpe]		[I-D.ietf-nvo3-vxlan-gpe]
	Quinn, P., Manur, R., Kreeger, L., Lewis, D., Maino, F.,		Kreeger, L. and U. Elzur, "Generic Protocol Extension for
	Smith, M., Agarwal, P., Yong, L., Xu, X., Elzur, U., Garg,		VXLAN", draft-ietf-nvo3-vxlan-gpe-02 (work in progress),
	P., and D. Melman, "Generic Protocol Extension for VXLAN",		April 2016.
	draft-ietf-nvo3-vxlan-gpe-01 (work in progress), November
	2015.
	[I-D.ietf-sfc-nsh]		[I-D.ietf-sfc-nsh]
	Quinn, P. and U. Elzur, "Network Service Header", draft-		Quinn, P. and U. Elzur, "Network Service Header", draft-
	ietf-sfc-nsh-02 (work in progress), January 2016.		ietf-sfc-nsh-04 (work in progress), March 2016.
	[I-D.ietf-sfc-oam-framework]		[I-D.ietf-sfc-oam-framework]
	Aldrin, S., Krishnan, R., Akiya, N., Pignataro, C., and A.		Aldrin, S., Krishnan, R., Akiya, N., Pignataro, C., and A.
	Ghanwani, "Service Function Chaining Operation,		Ghanwani, "Service Function Chaining Operation,
	Administration and Maintenance Framework", draft-ietf-sfc-		Administration and Maintenance Framework", draft-ietf-sfc-
	oam-framework-01 (work in progress), February 2016.		oam-framework-01 (work in progress), February 2016.
	[I-D.kumarzheng-bier-ping]		[I-D.kumarzheng-bier-ping]
	Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M.,		Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M.,
	and G. Mirsky, "BIER Ping and Trace", draft-kumarzheng-		and G. Mirsky, "BIER Ping and Trace", draft-kumarzheng-
	bier-ping-02 (work in progress), December 2015.		bier-ping-02 (work in progress), December 2015.
	[I-D.nordmark-nvo3-transcending-traceroute]		[I-D.nordmark-nvo3-transcending-traceroute]
	Nordmark, E., Appanna, C., and A. Lo, "Layer-Transcending		Nordmark, E., Appanna, C., and A. Lo, "Layer-Transcending
	Traceroute for Overlay Networks like VXLAN", draft-		Traceroute for Overlay Networks like VXLAN", draft-
	nordmark-nvo3-transcending-traceroute-01 (work in		nordmark-nvo3-transcending-traceroute-02 (work in
	progress), October 2015.		progress), March 2016.
	[I-D.xu-bier-encapsulation]		[I-D.xu-bier-encapsulation]
	Xu, X., Somasundaram, S., Jacquenet, C., and R. Raszuk,		Xu, X., Somasundaram, S., Jacquenet, C., and R. Raszuk,
	"BIER Encapsulation", draft-xu-bier-encapsulation-03 (work		"BIER Encapsulation", draft-xu-bier-encapsulation-03 (work
	in progress), October 2015.		in progress), October 2015.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	skipping to change at page 8, line 37 ¶		skipping to change at page 8, line 43 ¶
	[RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network		[RFC7637] Garg, P., Ed. and Y. Wang, Ed., "NVGRE: Network
	Virtualization Using Generic Routing Encapsulation",		Virtualization Using Generic Routing Encapsulation",
	RFC 7637, DOI 10.17487/RFC7637, September 2015,		RFC 7637, DOI 10.17487/RFC7637, September 2015,
	<http://www.rfc-editor.org/info/rfc7637>.		<http://www.rfc-editor.org/info/rfc7637>.
	[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function		[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function
	Chaining (SFC) Architecture", RFC 7665,		Chaining (SFC) Architecture", RFC 7665,
	DOI 10.17487/RFC7665, October 2015,		DOI 10.17487/RFC7665, October 2015,
	<http://www.rfc-editor.org/info/rfc7665>.		<http://www.rfc-editor.org/info/rfc7665>.
			[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
			Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
			May 2016, <http://www.rfc-editor.org/info/rfc7799>.
	8.2. Informative References		8.2. Informative References
	[I-D.ietf-bier-oam-requirements]		[I-D.ietf-bier-oam-requirements]
	Mirsky, G., Nordmark, E., Pignataro, C., Kumar, N.,		Mirsky, G., Nordmark, E., Pignataro, C., Kumar, N.,
	Aldrin, S., Zheng, L., Chen, M., Akiya, N., and J.		Aldrin, S., Zheng, L., Chen, M., Akiya, N., and S.
	Networks, "Operations, Administration and Maintenance		Pallagatti, "Operations, Administration and Maintenance
	(OAM) Requirements for Bit Index Explicit Replication		(OAM) Requirements for Bit Index Explicit Replication
	(BIER) Layer", draft-ietf-bier-oam-requirements-00 (work		(BIER) Layer", draft-ietf-bier-oam-requirements-01 (work
	in progress), September 2015.		in progress), March 2016.
	Authors' Addresses		Authors' Addresses
	Nagendra Kumar		Nagendra Kumar
	Cisco Systems, Inc.		Cisco Systems, Inc.
	7200 Kit Creek Road		7200 Kit Creek Road
	Research Triangle Park, NC 27709		Research Triangle Park, NC 27709
	US		US
	Email: naikumar@cisco.com		Email: naikumar@cisco.com
	Carlos Pignataro		Carlos Pignataro
	Cisco Systems, Inc.		Cisco Systems, Inc.
End of changes. 18 change blocks.
	25 lines changed or deleted		33 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/