< draft-wu-pce-traffic-steering-sfc-01.txt		draft-wu-pce-traffic-steering-sfc-02.txt >
	PCE Working Group Q. Wu		PCE Working Group Q. Wu
	Internet-Draft D. Dhody		Internet-Draft D. Dhody
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: August 17, 2014 J. Tantsura		Expires: August 17, 2014 M. Boucadair
			C. Boucadair
			France Telecom
			J. Tantsura
	Ericsson		Ericsson
	February 13, 2014		February 13, 2014
	PCEP Extensions for traffic steering support in Service Function		PCEP Extensions for traffic steering support in Service Function
	Chaining		Chaining
	draft-wu-pce-traffic-steering-sfc-01		draft-wu-pce-traffic-steering-sfc-02
	Abstract		Abstract
	This document provides an overview of the usage of Path Computation		This document provides an overview of the usage of Path Computation
	Element (PCE) with Service Function Chaining (SFC); which is		Element (PCE) with Service Function Chaining (SFC); which is
	described as the definition and instantiation of an ordered set of		described as the definition and instantiation of an ordered set of
	such service functions (such as firewalls, load balancers), and the		such service functions (such as firewalls, load balancers), and the
	subsequent "steering" of traffic flows through those service		subsequent "steering" of traffic flows through those service
	functions.		functions.
	skipping to change at page 3, line 10 ¶		skipping to change at page 3, line 10 ¶
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 8		9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
	9.2. Informative References . . . . . . . . . . . . . . . . . . 8		9.2. Informative References . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	Service chaining enables creation of composite services that consist		Service chaining enables creation of composite services that consist
	of an ordered set of Service Functions (SF) that must be applied to		of an ordered set of Service Functions (SF) that must be applied to
	packets and/or frames selected as a result of classification as		packets and/or frames selected as a result of classification as
	described in [I-D.quinn-sfc-arch] and referred to as Service Function		described in [I-D.boucadair-sfc-framework][I-D.quinn-sfc-arch] and
	Chain (SFC). Service Function Path (SFP) is the instantiation of a		referred to as Service Function Chain (SFC). Service Function Path
	SFC in the network. Packets follow a Service Function Path from a		(SFP) is the instantiation of a SFC in the network. Packets follow a
	classifier through the requisite Service Functions (SF).		Service Function Path from a classifier through the requisite Service
			Functions (SF).
	[RFC5440] describes the Path Computation Element Protocol (PCEP) as		[RFC5440] describes the Path Computation Element Protocol (PCEP) as
	the communication between a Path Computation Client (PCC) and a Path		the communication between a Path Computation Client (PCC) and a Path
	Control Element (PCE), or between PCE and PCE, enabling computation		Control Element (PCE), or between PCE and PCE, enabling computation
	of Multiprotocol Label Switching (MPLS) for Traffic Engineering Label		of Multiprotocol Label Switching (MPLS) for Traffic Engineering Label
	Switched Path (TE LSP).		Switched Path (TE LSP).
	[I-D.ietf-pce-stateful-pce] specifies extensions to PCEP to enable		[I-D.ietf-pce-stateful-pce] specifies extensions to PCEP to enable
	stateful control of MPLS TE LSPs. [I-D.ietf-pce-pce-initiated-lsp]		stateful control of MPLS TE LSPs. [I-D.ietf-pce-pce-initiated-lsp]
	provides the fundamental extensions needed for stateful PCE-initiated		provides the fundamental extensions needed for stateful PCE-initiated
	skipping to change at page 4, line 22 ¶		skipping to change at page 4, line 24 ¶
	physical network element. SFC creates an abstracted view of a		physical network element. SFC creates an abstracted view of a
	service and specifies the set of required SFs as well as the order in		service and specifies the set of required SFs as well as the order in
	which they must be executed.		which they must be executed.
	When an SFC is instantiated into the network it is necessary to		When an SFC is instantiated into the network it is necessary to
	select the specific instances of SFs that will be used, and to create		select the specific instances of SFs that will be used, and to create
	the service topology for that SFC using SF's network locator. Thus,		the service topology for that SFC using SF's network locator. Thus,
	instantiation of the SFC results in the creation of a Service		instantiation of the SFC results in the creation of a Service
	Function Path (SFP) and is used for forwarding packets through the		Function Path (SFP) and is used for forwarding packets through the
	SFC. In other words, an SFP is the instantiation of the defined SFC		SFC. In other words, an SFP is the instantiation of the defined SFC
	as described in details in [I-D.quinn-sfc-arch].		as described in details in
			[I-D.boucadair-sfc-framework][I-D.quinn-sfc-arch].
	The selection of SFP can be based on a range of policy attributes,		The selection of SFP can be based on a range of policy attributes,
	ranging from simple to more elaborate criteria and stateful PCE with		ranging from simple to more elaborate criteria and stateful PCE with
	extensions to PCEP are one such way to achieve this.		extensions to PCEP are one such way to achieve this.
	Stateful pce [I-D.ietf-pce-stateful-pce] specifies a set of		Stateful pce [I-D.ietf-pce-stateful-pce] specifies a set of
	extensions to PCEP to enable stateful control of TE LSPs.		extensions to PCEP to enable stateful control of TE LSPs.
	[I-D.ietf-pce-pce-initiated-lsp] provides the fundamental motivations		[I-D.ietf-pce-pce-initiated-lsp] provides the fundamental motivations
	and extensions needed for stateful PCE-initiated LSP instantiation.		and extensions needed for stateful PCE-initiated LSP instantiation.
	This document specifies extensions that allow a stateful PCE to		This document specifies extensions that allow a stateful PCE to
	skipping to change at page 5, line 17 ¶		skipping to change at page 5, line 17 ¶
	|| | | | |		|| | | | |
	|| | | | |		|| | | | |
	||PCE | |Policy| |		||PCE | |Policy| |
	|*------+ +------+ |		|*------+ +------+ |
	*---------------------------------+		*---------------------------------+
	/		/
	/		/
	/ SFP		/ SFP
	/ Instan-		/ Instan-
	/ tiation		/ tiation
	/		/ SF Node1 SF Node2
	/		/ +-------+ +-------+
	V		V | | | |
	+-----+ Signaling +-----+ Signaling +-----+ Signaling +-----+		+-----+ Signaling |+-----+| Signaling |+-----+| Signaling +-----+
	|SF-In|------------>|SF-1 |------------>|SF-2 |------------>|SF-E |		|SF-In|----------->||SF-1 || --------->||SF-2 ||----------->|SF-E |
	|gress| | | | | |gress|		|gress| || || || || |gress|
	+-----+ +-----+ +-----+ +-----+		+-----+ |+-----+| |+-----+| +-----+
			+-------+ +-------+
	Figure 1: SFP instantiation vis PCE		Figure 1: SFP instantiation vis PCE
	A Policy Decision Point (PDP) [RFC2753] is the central entity which		A Policy Decision Point (PDP) [RFC2753] is the central entity which
	is responsible for maintaining SFC Policy Tables and enforcing		is responsible for maintaining SFC Policy Tables and enforcing
	appropriate policies in SF Nodes described in detail in		appropriate policies in SF Nodes described in detail in
	[I-D.boucadair-sfc-framework]. A PDP may further use stateful PCE		[I-D.boucadair-sfc-framework]. A PDP may further use stateful PCE
	and its instantiation mechanism to compute and instantiate Service		and its instantiation mechanism to compute and instantiate Service
	Function Paths (SFP). The PCE maybe co-located with the PDP or an		Function Paths (SFP). The PCE maybe co-located with the PDP or an
	external entity.		external entity.
	skipping to change at page 10, line 4 ¶		skipping to change at page 10, line 4 ¶
	EMail: sunseawq@huawei.com		EMail: sunseawq@huawei.com
	Dhruv Dhody		Dhruv Dhody
	Huawei		Huawei
	Leela Palace		Leela Palace
	Bangalore, Karnataka 560008		Bangalore, Karnataka 560008
	INDIA		INDIA
	EMail: dhruv.ietf@gmail.com		EMail: dhruv.ietf@gmail.com
			Mohamed Boucadair
			France Telecom
			Rennes 35000
			France
			EMail: mohamed.boucadair@orange.com
			Christian Jacquenet
			France Telecom
			Rennes 35000
			France
			EMail: christian.jacquenet@orange.com
	Jeff Tantsura		Jeff Tantsura
	Ericsson		Ericsson
	300 Holger Way		300 Holger Way
	San Jose, CA 95134		San Jose, CA 95134
	US		US
	EMail: Jeff.Tantsura@ericsson.com		EMail: Jeff.Tantsura@ericsson.com
End of changes. 6 change blocks.
	14 lines changed or deleted		34 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/