< draft-kumar-spring-sr-oam-requirement-01.txt		draft-kumar-spring-sr-oam-requirement-02.txt >
	spring N. Kumar		spring N. Kumar
	Internet-Draft C. Pignataro		Internet-Draft C. Pignataro
	Intended status: Informational N. Akiya		Intended status: Informational N. Akiya
	Expires: January 2, 2015 Cisco Systems, Inc.		Expires: July 4, 2015 Cisco Systems, Inc.
	R. Geib		R. Geib
	Deutsche Telekom		Deutsche Telekom
	G. Mirsky		G. Mirsky
	Ericsson		Ericsson
	July 1, 2014		December 31, 2014
	OAM Requirements for Segment Routing Network		OAM Requirements for Segment Routing Network
	draft-kumar-spring-sr-oam-requirement-01		draft-kumar-spring-sr-oam-requirement-02
	Abstract		Abstract
	This document describes a list of functional requirement for OAM in		This document describes a list of functional requirement for OAM in
	Segment Routing (SR) based network.		Segment Routing (SR) based network.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 36 ¶
	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 January 2, 2015.		This Internet-Draft will expire on July 4, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 24 ¶		skipping to change at page 2, line 24 ¶
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 4		6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 4		7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 4
	8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 4		8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 4
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	9.1. Normative References . . . . . . . . . . . . . . . . . . 5		9.1. Normative References . . . . . . . . . . . . . . . . . . 5
	9.2. Informative References . . . . . . . . . . . . . . . . . 5		9.2. Informative References . . . . . . . . . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	[I-D.filsfils-spring-segment-routing] introduces and explains Segment		[I-D.ietf-spring-segment-routing] introduces and explains Segment
	Routing architecture that leverages source routing and tunneling		Routing architecture that leverages source routing and tunneling
	standards which can be applied directly to MPLS dataplane with no		standards which can be applied directly to MPLS dataplane with no
	changes on forwarding plane and on IPv6 dataplane with new Routing		changes on forwarding plane and on IPv6 dataplane with new Routing
	Extension Header.		Extension Header.
	This document list the OAM requirements for Segment Routing based		This document list the OAM requirements for Segment Routing based
	network which can further be used to produce OAM tools, either		network which can further be used to produce OAM tools, either
	through enhancing existing OAM tools or constructing new OAM tools,		through enhancing existing OAM tools or constructing new OAM tools,
	for path liveliness and service validation.		for path liveliness and service validation.
	skipping to change at page 5, line 9 ¶		skipping to change at page 5, line 9 ¶
	8. Contributing Authors		8. Contributing Authors
	Sriganesh Kini		Sriganesh Kini
	Ericsson		Ericsson
	Email: sriganesh.kini@ericsson.com		Email: sriganesh.kini@ericsson.com
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[I-D.filsfils-spring-segment-routing]
	Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,
	Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R.,
	Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe,
	"Segment Routing Architecture", draft-filsfils-spring-
	segment-routing-04 (work in progress), July 2014.
	[I-D.geib-spring-oam-usecase]		[I-D.geib-spring-oam-usecase]
	Geib, R., Filsfils, C., Pignataro, C., and N. Kumar, "Use		Geib, R., Filsfils, C., Pignataro, C., and N. Kumar, "Use
	case for a scalable and topology aware MPLS data plane		case for a scalable and topology aware MPLS data plane
	monitoring system", draft-geib-spring-oam-usecase-02 (work		monitoring system", draft-geib-spring-oam-usecase-03 (work
	in progress), July 2014.		in progress), October 2014.
			[I-D.ietf-spring-segment-routing]
			Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,
			Litkowski, S., Horneffer, M., Shakir, R., Tantsura, J.,
			and E. Crabbe, "Segment Routing Architecture", draft-ietf-
			spring-segment-routing-00 (work in progress), December
			2014.
	[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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	9.2. Informative References		9.2. Informative References
	[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol		[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
	Label Switched (MPLS) Data Plane Failures", RFC 4379,		Label Switched (MPLS) Data Plane Failures", RFC 4379,
	February 2006.		February 2006.
End of changes. 7 change blocks.
	14 lines changed or deleted		14 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/