< draft-wu-pce-traffic-steering-sfc-00.txt   draft-wu-pce-traffic-steering-sfc-01.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 14, 2014 February 10, 2014 Expires: August 17, 2014 J. Tantsura
Ericsson
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-00 draft-wu-pce-traffic-steering-sfc-01
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 1, line 40 skipping to change at page 1, line 42
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 August 14, 2014. This Internet-Draft will expire on August 17, 2014.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions used in this document . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . . 3
3. Service Function Paths and PCE . . . . . . . . . . . . . . . 3 3. Service Function Paths and PCE . . . . . . . . . . . . . . . . 4
4. Overview of PCEP Operation in SFC enabled Networks . . . . . 4 4. Overview of PCEP Operation in SFC enabled Networks . . . . . . 5
4.1. SFP Instantiation . . . . . . . . . . . . . . . . . . . . 5 4.1. SFP Instantiation . . . . . . . . . . . . . . . . . . . . . 5
4.2. SFP Deletion . . . . . . . . . . . . . . . . . . . . . . 5 4.2. SFP Deletion . . . . . . . . . . . . . . . . . . . . . . . 6
4.3. SFP Delegation and Cleanup . . . . . . . . . . . . . . . 5 4.3. SFP Delegation and Cleanup . . . . . . . . . . . . . . . . 6
4.4. SFP State Synchronization . . . . . . . . . . . . . . . . 5 4.4. SFP State Synchronization . . . . . . . . . . . . . . . . . 6
4.5. SFP Update and Report . . . . . . . . . . . . . . . . . . 5 4.5. SFP Update and Report . . . . . . . . . . . . . . . . . . . 6
5. Object Formats . . . . . . . . . . . . . . . . . . . . . . . 5 5. Object Formats . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. The OPEN Object . . . . . . . . . . . . . . . . . . . . . 5 5.1. The OPEN Object . . . . . . . . . . . . . . . . . . . . . . 6
5.2. The LSP Object . . . . . . . . . . . . . . . . . . . . . 6 5.2. The LSP Object . . . . . . . . . . . . . . . . . . . . . . 7
5.2.1. SFP Identifiers TLV . . . . . . . . . . . . . . . . . 6 5.2.1. SFP Identifiers TLV . . . . . . . . . . . . . . . . . . 7
6. Backward Compatibility . . . . . . . . . . . . . . . . . . . 7 6. Backward Compatibility . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 7 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.quinn-sfc-arch] and referred to as Service Function
Chain (SFC). Service Function Path (SFP) is the instantiation of a Chain (SFC). Service Function Path (SFP) is the instantiation of a
SFC in the network. Packets follow a Service Function Path from a SFC in the network. Packets follow a Service Function Path from a
classifier through the requisite Service Functions (SF). classifier through the requisite Service Functions (SF).
skipping to change at page 4, line 46 skipping to change at page 5, line 35
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.
4. Overview of PCEP Operation in SFC enabled Networks 4. Overview of PCEP Operation in SFC enabled Networks
A PCEP speaker indicates its ability to support PCE initiated dynamic A PCEP speaker indicates its ability to support PCE initiated dynamic
SFP during the PCEP Initialization Phase via mechanism described in SFP during the PCEP Initialization Phase via mechanism described in
Section 5.1. Section 5.1.
As per section 5.1 of [I-D.ietf-pce-pce-initiated-lsp], the PCE sends As per section 5.1 of [I-D.ietf-pce-pce-initiated-lsp], the PCE sends
a Path Computation LSP Initiate Request (PCInitiate) message to the a Path Computation LSP Initiate Request (PCInitiate) message to the
PCC to instantiate or delete a LSP. This document makes no change to PCC to instantiate or delete a LSP. This document makes no change to
the PCInitiate message format but extends LSP objects described in the PCInitiate message format but extends LSP objects described in
Section 5.2. Section 5.2.
skipping to change at page 7, line 33 skipping to change at page 8, line 31
specification. No additional security measure is required. specification. No additional security measure is required.
8. IANA Considerations 8. IANA Considerations
TBD TBD
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in
Requirement Levels", BCP 14, RFC 2119, March 1997. RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119,
March 1997.
[I-D.ietf-pce-stateful-pce] [I-D.ietf-pce-stateful-pce] Crabbe, E., Medved, J., Minei, I.,
Crabbe, E., Medved, J., Minei, I., and R. Varga, "PCEP and R. Varga, "PCEP Extensions for
Extensions for Stateful PCE", draft-ietf-pce-stateful- Stateful PCE",
pce-07 (work in progress), October 2013. draft-ietf-pce-stateful-pce-07
(work in progress), October 2013.
[I-D.ietf-pce-pce-initiated-lsp] [I-D.ietf-pce-pce-initiated-lsp] Crabbe, E., Minei, I., Sivabalan,
Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP S., and R. Varga, "PCEP Extensions
Extensions for PCE-initiated LSP Setup in a Stateful PCE for PCE-initiated LSP Setup in a
Model", draft-ietf-pce-pce-initiated-lsp-00 (work in Stateful PCE Model",
progress), December 2013. draft-ietf-pce-pce-initiated-lsp-00
(work in progress), December 2013.
9.2. Informative References 9.2. Informative References
[RFC2753] Yavatkar, R., Pendarakis, D., and R. Guerin, "A Framework [RFC2753] Yavatkar, R., Pendarakis, D., and
for Policy-based Admission Control", RFC 2753, January R. Guerin, "A Framework for Policy-
2000. based Admission Control", RFC 2753,
January 2000.
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element [RFC5440] Vasseur, JP. and JL. Le Roux, "Path
(PCE) Communication Protocol (PCEP)", RFC 5440, March Computation Element (PCE)
2009. Communication Protocol (PCEP)",
RFC 5440, March 2009.
[I-D.quinn-sfc-arch] [I-D.quinn-sfc-arch] Quinn, P. and A. Beliveau, "Service
Quinn, P. and A. Beliveau, "Service Function Chaining Function Chaining (SFC)
(SFC) Architecture", draft-quinn-sfc-arch-04 (work in Architecture",
progress), January 2014. draft-quinn-sfc-arch-04 (work in
progress), January 2014.
[I-D.boucadair-sfc-framework] [I-D.boucadair-sfc-framework] Boucadair, M., Jacquenet, C.,
Boucadair, M., Jacquenet, C., Parker, R., Lopez, D., Parker, R., Lopez, D., Guichard,
Guichard, J., and C. Pignataro, "Service Function J., and C. Pignataro, "Service
Chaining: Framework & Architecture", draft-boucadair-sfc- Function Chaining: Framework &
framework-00 (work in progress), October 2013. Architecture",
draft-boucadair-sfc-framework-02
(work in progress), February 2014.
Authors' Addresses Authors' Addresses
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
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
Jeff Tantsura
Ericsson
300 Holger Way
San Jose, CA 95134
US
EMail: Jeff.Tantsura@ericsson.com
 End of changes. 13 change blocks. 
49 lines changed or deleted 60 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/