| < draft-wu-pce-traffic-steering-sfc-09.txt | draft-wu-pce-traffic-steering-sfc-10.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: March 12, 2017 M. Boucadair | Expires: September 7, 2017 M. Boucadair | |||
| C. Jacquenet | C. Jacquenet | |||
| Orange | Orange | |||
| J. Tantsura | J. Tantsura | |||
| September 8, 2016 | March 6, 2017 | |||
| PCEP Extensions for Service Function Chaining (SFC) | PCEP Extensions for Service Function Chaining (SFC) | |||
| draft-wu-pce-traffic-steering-sfc-09 | draft-wu-pce-traffic-steering-sfc-10 | |||
| 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) to dynamically structure service function chains. | Element (PCE) to dynamically structure service function chains. | |||
| Service Function Chaining (SFC) is a technique that is meant to | Service Function Chaining (SFC) is a technique that is meant to | |||
| facilitate the dynamic enforcement of differentiated traffic | facilitate the dynamic enforcement of differentiated traffic | |||
| forwarding policies within a domain. Service function chains are | forwarding policies within a domain. Service function chains are | |||
| composed of an ordered set of elementary Service Functions (such as | composed of an ordered set of elementary Service Functions (such as | |||
| firewalls, load balancers) that need to be invoked according to the | firewalls, load balancers) that need to be invoked according to the | |||
| skipping to change at page 1, line 47 ¶ | skipping to change at page 1, line 47 ¶ | |||
| 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 March 12, 2017. | This Internet-Draft will expire on September 7, 2017. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2016 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 | |||
| (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 | |||
| skipping to change at page 10, line 23 ¶ | skipping to change at page 10, line 23 ¶ | |||
| 11.1. Normative References | 11.1. Normative References | |||
| [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>. | |||
| [I-D.ietf-pce-stateful-pce] | [I-D.ietf-pce-stateful-pce] | |||
| Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP | Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP | |||
| Extensions for Stateful PCE", draft-ietf-pce-stateful- | Extensions for Stateful PCE", draft-ietf-pce-stateful- | |||
| pce-16 (work in progress), September 2016. | pce-18 (work in progress), December 2016. | |||
| [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation | [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation | |||
| Element (PCE) Communication Protocol (PCEP)", RFC 5440, | Element (PCE) Communication Protocol (PCEP)", RFC 5440, | |||
| DOI 10.17487/RFC5440, March 2009, | DOI 10.17487/RFC5440, March 2009, | |||
| <http://www.rfc-editor.org/info/rfc5440>. | <http://www.rfc-editor.org/info/rfc5440>. | |||
| [I-D.ietf-pce-pce-initiated-lsp] | [I-D.ietf-pce-pce-initiated-lsp] | |||
| Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP | Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP | |||
| Extensions for PCE-initiated LSP Setup in a Stateful PCE | Extensions for PCE-initiated LSP Setup in a Stateful PCE | |||
| Model", draft-ietf-pce-pce-initiated-lsp-07 (work in | Model", draft-ietf-pce-pce-initiated-lsp-08 (work in | |||
| progress), July 2016. | progress), March 2017. | |||
| [I-D.ietf-teas-pce-central-control] | [I-D.ietf-teas-pce-central-control] | |||
| Farrel, A., Zhao, Q., Li, Z., and C. Zhou, "An | Farrel, A., Zhao, Q., Li, Z., and C. Zhou, "An | |||
| Architecture for Use of PCE and PCEP in a Network with | Architecture for Use of PCE and PCEP in a Network with | |||
| Central Control", draft-ietf-teas-pce-central-control-00 | Central Control", draft-ietf-teas-pce-central-control-01 | |||
| (work in progress), September 2016. | (work in progress), December 2016. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [RFC2753] Yavatkar, R., Pendarakis, D., and R. Guerin, "A Framework | [RFC2753] Yavatkar, R., Pendarakis, D., and R. Guerin, "A Framework | |||
| for Policy-based Admission Control", RFC 2753, | for Policy-based Admission Control", RFC 2753, | |||
| DOI 10.17487/RFC2753, January 2000, | DOI 10.17487/RFC2753, January 2000, | |||
| <http://www.rfc-editor.org/info/rfc2753>. | <http://www.rfc-editor.org/info/rfc2753>. | |||
| [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, | |||
| skipping to change at page 11, line 13 ¶ | skipping to change at page 11, line 13 ¶ | |||
| <http://www.rfc-editor.org/info/rfc7665>. | <http://www.rfc-editor.org/info/rfc7665>. | |||
| [RFC5394] Bryskin, I., Papadimitriou, D., Berger, L., and J. Ash, | [RFC5394] Bryskin, I., Papadimitriou, D., Berger, L., and J. Ash, | |||
| "Policy-Enabled Path Computation Framework", RFC 5394, | "Policy-Enabled Path Computation Framework", RFC 5394, | |||
| DOI 10.17487/RFC5394, December 2008, | DOI 10.17487/RFC5394, December 2008, | |||
| <http://www.rfc-editor.org/info/rfc5394>. | <http://www.rfc-editor.org/info/rfc5394>. | |||
| [I-D.ietf-sfc-control-plane] | [I-D.ietf-sfc-control-plane] | |||
| Boucadair, M., "Service Function Chaining (SFC) Control | Boucadair, M., "Service Function Chaining (SFC) Control | |||
| Plane Components & Requirements", draft-ietf-sfc-control- | Plane Components & Requirements", draft-ietf-sfc-control- | |||
| plane-07 (work in progress), August 2016. | plane-08 (work in progress), October 2016. | |||
| [I-D.ietf-pce-segment-routing] | [I-D.ietf-pce-segment-routing] | |||
| Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E., | Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E., | |||
| Lopez, V., Tantsura, J., Henderickx, W., and J. Hardwick, | Raszuk, R., Lopez, V., Tantsura, J., Henderickx, W., and | |||
| "PCEP Extensions for Segment Routing", draft-ietf-pce- | J. Hardwick, "PCEP Extensions for Segment Routing", draft- | |||
| segment-routing-07 (work in progress), March 2016. | ietf-pce-segment-routing-08 (work in progress), October | |||
| 2016. | ||||
| [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-07 (work in progress), August 2016. | ietf-sfc-nsh-12 (work in progress), February 2017. | |||
| 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: bill.wu@huawei.com | EMail: bill.wu@huawei.com | |||
| End of changes. 11 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/ | ||||