| Network Working Group | H. Li |
| Internet-Draft | Q. Wu |
| Intended status: Standards Track | O. Huang |
| Expires: September 9, 2015 | Huawei |
| M. Boucadair | |
| C. Jacquenet | |
| France Telecom | |
| W. Haeffner | |
| Vodafone | |
| S. Lee | |
| ETRI | |
| R. Parker | |
| Affirmed Networks | |
| March 8, 2015 |
Service Function Chaining (SFC) Control Plane Achitecture
draft-ww-sfc-control-plane-04
This document defines the control plane architecture which include control plane components and interface between control plane component and data plane component. This document further describes how Service Functions Chains are structured and how Service Function Chaining path is provisioned and setup.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 9, 2015.
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
The dynamic enforcement of a service-derived, adequate forwarding policy for packets entering a network that supports advanced Service Functions (SFs) has become a key challenge for operators and service providers.
Service Function Chaining (SFC) typically observe, alter or even terminate and re-establish session flows between user equipment and application platforms (Web, Video, VoIP etc.) by invoking, in a given order, a set of Service Functions [I.D-ietf-sfc-problem-statement]. Service functions involved in a given SFC may include load-balancing, firewalling, intrusion prevention, etc.
A given SFC-enabled domain may involve several instances of the same Service Function. Service function instances can be automatically added to or removed from a given SFC. SFs can be co-located or embedded in distinct physical nodes, or virtualized.
This document describes SFC control plane architecture and discusses how the Service Function Chains are structured and how Service Function Chaining path is provisioned and setup.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119 [RFC2119].
This document defines the control plane architecture while the data plane architecture is defined in [I.D-ietf-sfc-architecture].
The SFC data plane characteristics considered as basic assumptions by the SFC control architecture are summarized below:
As described in [I-D.ietf-sfc-architecture],SFC Control plane is responsible for constructing SFC, translating SFCs to forwarding paths and propagating path information to participating nodes to achieve requisite forwarding behavior and construct the service overlay. For the purpose of defining the SFC control plane architecture, the SFC control plane is broken up into five distinct components:
+-------------------------------------------------+
| SFC Control Plane |
| +---------------+ +---------------+ |
+-------| |Chain Management |Service Overlay| |
| | |Policy Control | |Topo Management| |
| | +---------------+ +---------------+ |
| | +---------------+ +---------------+ |
+---------|Chain Selection| | Chain Mapping | +----------+|
| | | Policy Control| | and Forwarding| |External SF|
| +---------------+ | Control | |Management||
| | +---------------+ +----------+|
C1 +------^-----------^-------------^----------------+
+---------------------|F----------|-------------|-------------+
| | +----+ | | |
| | | SF | |C2 |C2 |
| +----+ | | |
| +----V--- --+ | | | |
| | SFC | +----+ +-|--+ +----+ |
| |Classifier |---->|SFF |----->|SFF |------->|SFF | |
| | Node |<----| |<-----| |<-------| | |
| +-----------+ +----+ +----+ +----+ |
| | | | |
| |C2 ------- | |
| | | | +-----------+ F |
| V +----+ +----+ | SFC Proxy |--> |
| | SF | |SF | +-----------+ |
| +----+ +----+ |
| |F |F |
| SFC Data Plane Components V V |
| |
+-------------------------------------------------------------+
Figure 1: SFC Control Plane Overview
There are three interfaces connected to the SFC control plane.
The SFC control plane is in charge of Service Function chain creation and maintenance, service chain path instantiation (in case of the traffic-engineered SFCs), mapping between SFC and Service Function path, SFC Policy Table creation and configuration, including the sequence of Service Functions in a Service Function chain, Service Function information, SFC paths information.
The SFC control plane may be fed with Service Function chain information from the Management application. A SFC service template information may look like:
The SFC Control plane also creates classification rules and installs them on the classifier nodes. The SFC control plane also assigns SFC identification and installs SFC Policy Tables in the Service forwarder function.
Service Functions, e.g., deep packet inspection (DPI) or firewall may need to output some processing results of packets to the control system. This information can be used by the SFC control plane to update the SFC classification and SFC forwarding entries.
The F Interface is used to collect such kind of feedback information from the Service Functions or the SF nodes.
The F interface is also used for collecting states of attributes (e.g., availability, workload) of Service Functins to dynamically adjust Service Function paths.
This interface is used to install SFC classification rules in Service Classifier nodes. These rules are created by the SFC control Plane. They may be updated by information provided by the Service Function nodes (in case a change of the network topology has occurred, for example).
SFC Classifier Node binds incoming traffic to SFCs according to these classification rules.
Service forwarder entity make traffic forwarding decisions according to the entries maintained in their SFC Policy Table. Such Table is populated by the SFC control plane through the C2 interface.
Each Service Function has a unique Service Function identifier to identify itself in the SFC forwarding plane. The Service Function locator is typically referred to as a network address. In case the Service Function instance is directly connected to a Service forwarder entity, the forwarding entry may also include the port through which the Service Function instance can be reached.
Some proxy function may also use the C2 interface to retrieve the mapping between a Service Function Identifier and a Service Function locator from the SFC control plane.
The C2 interface is also used for collecting states of attributes (e.g., availability, workload, latency) of Service Functins or overlay links to dynamically adjust Service Function paths.
When a Service Function is instantiated into the network it is necessary to select the locator of the specific instances of Service Functions that will be used, and to construct the service overlay using Service Function's network locator. The service overlay is built on top of the underlying network. The resulting service overlay is meant to facilitate SFC-enabled domain operation, as it may provide a better, up-to-date, network-wise overview of the Service Functions status and usage.
A service specific overlay utilized by SFC then results in the creation of the service topology. Service topology information consists of network topology information collected from the underlying network and Service Function-related information (such as Service Function administration information and Service Function capability information) that may be collected from the management interface. For example, Network topology information can be collected from the network using an IGP or BGP-LS [I.D-draft-idr-ls-distribution].
Service Function-related information includes Service Function Identifier, Service Function Locator, Service Function administration information (e.g., available memory, CPU utilization, available storage capacity, etc.) or Service Function capability information (e.g., supported ACL numbers, virtual context number). This information can be retrieved by various means (e.g., registration mechanism that provides binding between Service Function Identifier and Service Function Locator(s) and allows for the dynamic discovery of locations of Service Functions).
Network topology is not required for dynamically structuring service chains, but it may be helpful during service troubleshooting and diagnostics.
The creation of the service topology is not conditioned by the creation of the network topology: what is required is the mapping between Service Function-related information and existing network topology information. Additional Service Functions or Service Function instances, for redundancy or load distribution purposes, can be added to or removed from the service topology as required. Means to dynamically discover the location of available Service Function instances may be supported.
service-chain 100 {
10 url-filter
20 web-cache
30 web-optimizer
40 firewall
}
The chain management component of the SFC control plane is responsible for the dynamic structuring of Service Function chains (i.e., define an ordered list of Service Function identifiers) that can be supported, as a function of the services that can be delivered, among other information that may include subscriber- specific information. For example, a Service Function chain can be structured as follows:
In this Service Function chain, each Service Function needs to be assigned with a unique Service Function identifier and can be located using Service Function locators. A Service Function chain should be assigned an SFC Index. A Service Function identifier does not necessarily hint the service offered by that Service Function; its purpose is to uniquely identify a Service Function among those present in a SFC-enabled domain.
The Chain Mapping and forwarding Control Component of the SFC control plane is a component that is responsible for Service Function path determination based on Service Overlay Topology information maintained in the Service Overlay Topology management component. However, not all SFC deployments may require Service Function path determination (e.g., SFC forwarding is fully distributed ). Service Function path determination is referred to determine an ordered list of locators of each Service Function that belongs to a Service Function chain.
The Service Function path determining may be static or pre-determined using specific Service Function instances, or dynamic - choosing explicit Service Function instances at the time of delivering traffic to the Service Function.
When there are multiple instances of a given Service Function that belongs to a given SFC, each of these instances is assigned a unique locator. These multiple instances may actually be invoked within the context of a single chain, or within the context of multiple chains depending on how the said chains are structured. The latter case may lead to multiple SFPs. In some other cases, a Service Function path can pre-determined by SFC mapping and forwarding component for traffic engineering purposes by interacting with Service Overlay Topology management component. However Service Function path doesn't need to be pre- determined. The chain management component responsible for structuring the service chains cannot decide in advance the actual path that will be followed by packets.
In addition, the SFC mapping and forwarding component also maintains the mapping between Service Function chains and Service Function paths. When Service Function chain structuring is complete, the SFC control plane will use the SFC forwarding and mapping component to determine the locator of each specific Service Function instance in the chain and return a set of Service Function locators associated with a Service Function chain.
A Service Function Path (SFP) is determined by composing instances of Service Functions (SFIs) and overlay links among SFFs. Thus the status of a SFP depends on the states or attributes (e.g., availability, topological location, latency, workload, etc.) of its components, i.e., SFIs and overlay links. For example, failure of a single SFI results in failure of the whole SFP which the SFI constitutes. Since these states or attributes of SFP components may vary in time, their changes are monitored and SFPs are dynamically adjusted.
Examples of use cases for SFP adjustment are as follows:
For more details about the use cases, refer to [I-D.lee-nfvrg-resource-management-service-chain].
The procedures for SFP adjustment are handled by Chain Mapping and Forwarding Control Component as follows:
Once a SFC is structured, traffic classification rules are derived and provided to the classifier nodes, along with other information maintained in Policy Tables. The policy table is built based on SFC policy and service information(e.g.,subscriber being mapped into a service class related to a SFC) captured by using policy related components, when a Service Function path is determined. The policy table will be populated at each participating node involved in the application of a Service Function chain and used by them to make their forwarding decisions on a typical hop-by-hop basis.
The SFC Control and the participating SFC functional elements must be mutually authenticated. Means to protect against an attacker who would install/remove/modify classification rules must be supported. When means to dynamically discover the location of SF instances are in use, they should be designed to avoid illegitimate SFs to belong to the SFC-enabled domain.
This documen is the result of merging with draft-lee-sfc-dynamic-instantiation.
The author would like to thank Shibi Huang for providing input and LAC Chidung for his review and comments that helped improve this document.
| [I.D-ietf-sfc-architecture] | Halpern, J. and C. Pignataro, "Service Function Chaining (SFC) Architecture", ID draft-ietf-sfc-architecture-01, September 2014. |
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", March 1997. |
| [I-D.lee-nfvrg-resource-management-service-chain] | Lee, S., Pack, S., Shin, M. and E. Paik, "Resource Management for Dynamic Service Chain Adaptation", Internet-Draft draft-lee-nfvrg-resource-management-service-chain-00, October 2014. |
| [I.D-ietf-sfc-problem-statement] | Quinn, P., "Network Service Chaining Problem Statement", ID draft-ietf-sfc-problem-statement-10, August 2014. |
| [I.D-wu-pce-traffic-steering-sfc] | Wu, Q., Dhody, D., Boucadair, M., Boucadair, C. and J. Tantsura, "PCEP Extensions for traffic steering support in Service Function Chaining", ID draft-wu-pce-traffic-steering-sfc-05, September 2014. |
+---------------------------------------------------------------+ | SFC Control Plane +----------------------+ | | | +------------+ | | | | | SFC | | | | +----------------|Orchestrator-----------+ | | | | +------------+ | | | | | | SFC Management System| | | | | +----------------------+ | | | | | | | | | | |+------|-------------+ +--------|------------+ | ||+-----|----+ | | +------|---------+ | | |||SFC Policy| | | | SFC Forwarding | | | ||| Control | | |-------| Control -----|----+ ||+-----|----+ | | | +----------------+ | | | || Enhancement in PCRF| | | SFC Controller | | | |+------|-------------+ | | | | | | | | +---------------------+ | | +-------|-------------------------|-----------------------------+ | +-------|-------------------------|------------------------------------+ |+--------------------+ +---------------+ +---------------+ | | ||Enhancement in PCEF | | Enhancement in| | Enhancement in| | | || or TDF | | ToR switch or | | ToR Switch or | | | ||+-----|-------+ | | Router | | Router | | | ||| SFC | | |+----|--+ | |+-------+ | | | ||| Classifier |-----------|| |------------- | | | | | ||| Function | | || SFF1 | | || SFF2 ---------+ | ||+-------------+ | || | | || | | | |+--------------------+ |+---|---+ | |+---|---+ | | | +----|----------+ +----|----------+ | | ------------ -----|------ | | | | | | | | +----+ +---+ +----+ +---+ | | | SF1| |SF2| | SF3| |SF4| | | +----+ +---+ +----+ +---+ | |SFC Data Plane | -----------------------------------------------------------------------+
SFC in MBB
In MBB environment, Policy Control component and Chain Management Policy Control component defined in section 4 can be supported using Enhanced PCRF. Service Overlay Topology management defined in section 4 can be supported using SFC Orchestrator. SFC Mapping and Forwarding Control component defined in section 4 can be supported using SFC Controller. Note that 3GPP is considering integrating Chain Selection Policy Control component and Chain Management Policy Control component using PCRF.
+---------------------------------------------------------------+ | SFC Control Plane +----------------------+ | | | +------------+ | | | | | SFC | | | | +----------------|Orchestrator-----------+ | | | | +------------+ | | | | | | SFC Management System| | | | | +----------------------+ | | | | | | | | | | |+------|-------------+ +--------|------------+ | ||+-----|----+ | | +------|---------+ | | |||SFC Policy| | | | SFC Forwarding | | | ||| Control | | -|-------| Control -----|----+ ||+-----|----+ | | | +----------------+ | | | || Enhancement in RADIUS | | SFC Controller | | | |+------|-------------+ | | | | | | | | +---------------------+ | | +---------------------------------------------------------------+ | +----------------------------------------------------------------------+ |+--------------------+ +---------------+ +---------------+ | | ||Enhancement in BRAS | | Enhancement in| | Enhancement in| | | || or BNG | | ToR switch or | | ToR Switch or | | | ||+-----|-------+ | | Router | | Router | | | ||| SFC | | |+----|--+ | |+-------+ | | | ||| Classifier |-----------|| |------------- | | | | | ||| Function | | || SFF1 | | || SFF2 ---------+ | ||+-------------+ | || | | || | | | |+--------------------+ |+---|---+ | |+---|---+ | | | +----|----------+ +----|----------+ | | ------------ -----|------ | | | | | | | | +----+ +---+ +----+ +---+ | | | SF1| |SF2| | SF3| |SF4| | | +----+ +---+ +----+ +---+ | |SFC Data Plane | -----------------------------------------------------------------------+
SFC in FBB
In FBB environment, Policy Control component and Chain Management Policy Control component defined in section 4 can be supported using Enhanced RADIUS. Service Overlay Topology management defined in section 4 can be supported using SFC Orchestrator. SFC Mapping and Forwarding Control component defined in section 4 can be supported using SFC Controller. Note that BBF is considering integrating Chain Selection Policy Control component and Chain Management Policy Control component using RADIUS.
+---------------------------------------------------------------+ | SFC Control Plane +----------------------+ | | | +------------+ | | | | | SFC | | | | +----------------|Orchestrator-----------+ | | | | +------------+ | | | | | | SFC Management System| | | | | +----------------------+ | | | | | | | | | | | |Download Classifier +--------|------------+ | | | Rule directly | +------|---------+ | | | | | | SFC Forwarding | | | | | -|-------| Control -----|----+ | | | | +----------------+ | | | | | | | SFC Controller | | | | | | | | | | | | | +---------------------+ | | +-------|-------------------------------------------------------+ | +-------|--------------------------------------------------------------+ |+------|-------------+ +---------------+ +---------------+ | | || Enhancement in DC | | Enhancement in| | Enhancement in| | | || | Gateway | | ToR switch or | | ToR Switch or | | | ||+-----|-------+ | | Router | | Router | | | ||| SFC | | |+----|--+ | |+-------+ | | | ||| Classifier |-----------|| |------------- | | | | | ||| Function | | || SFF1 | | || SFF2 ---------+ | ||+-------------+ | || | | || | | | |+--------------------+ |+---|---+ | |+---|---+ | | | +----|----------+ +----|----------+ | | ------------ -----|------ | | | | | | | | +----+ +---+ +----+ +---+ | | | SF1| |SF2| | SF3| |SF4| | | +----+ +---+ +----+ +---+ | |SFC Data Plane | -----------------------------------------------------------------------+
SFC in DC Environment
In DC environment, Policy Control component and Chain Management Policy Control component, Service Overlay Topology management defined in section 4 can be supported using SFC Orchestrator. SFC Mapping and Forwarding Control component defined in section 4 can be supported using SFC Controller.
+---------------------------------------------------------------+ | SFC Control Plane | | +------------------------+ | | | stateful PCE | | | +-------------| +-------+ +-------+ | | | | | |Policy | | TE-DB | |<-------| | | | | +-------+ +-------+ | | | | | +------------------------+ | | | | ---------------|-----| | | | SFC Controller | | | | | | | | | +--------------------------- | | | | | | | | | | | +------ ------ --+ | | | | | | SFC Forwarding | | | | | | +-------| Control -----|----+ | | | | | +----------------+ | | | | | | | +---------------------+ | | +-------|-----|-------------------------------------------------+ | +-------|-----|--------------------------------------------------------+ |+------|-----|-------+ +---------------+ +---------------+ | | || Enhancement in DC | | Enhancement in| | Enhancement in| | | || | Gateway | | ToR switch or | | ToR Switch or | | | ||+-----|-------+ | | Router | | Router | | | ||| SFC | | |+----|--+ | |+-------+ | | | ||| Classifier |-----------|| |------------- | | | | | ||| Function | | || SFF1 | | || SFF2 ---------+ | ||+-------------+ | || | | || | | | |+--------------------+ |+---|---+ | |+---|---+ | | | +----|----------+ +----|----------+ | | ------------ -----|------ | | | | | | | | +----+ +---+ +----+ +---+ | | | SF1| |SF2| | SF3| |SF4| | | +----+ +---+ +----+ +---+ | |SFC Data Plane | -----------------------------------------------------------------------+
SFC in DC Environment
Alternatively, In DC environment, Policy Control component and Chain Management Policy Control component, Service Overlay Topology management defined in section 4 can be supported, SFC Mapping and Forwarding Control component defined in section 4 can be supported together using SFC Controller. In addtion, SFC Controler operates a stateful PCE and its instantiation mechanism to compute and instantiate Service Function Paths (SFP).
The PCE maybe co-located with the SFC Control plane component or an external entity (e.g., [I.D-wu-pce-traffic-steering-sfc]).