WG Review: Service Function Chaining (sfc)

The IESG <iesg-secretary@ietf.org> Thu, 12 December 2013 00:04 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 951F01AE21E; Wed, 11 Dec 2013 16:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGLsH4WqO2UY; Wed, 11 Dec 2013 16:04:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 624931AE1FE; Wed, 11 Dec 2013 16:04:31 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Service Function Chaining (sfc)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131212000431.24760.14652.idtracker@ietfa.amsl.com>
Date: Wed, 11 Dec 2013 16:04:31 -0800
Cc: sfc WG <nsc@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 00:04:33 -0000

A new IETF working group has been proposed in the Routing Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2013-12-19.

Service Function Chaining (sfc)
------------------------------------------------
Current Status: Proposed WG

Chairs:
  Jim Guichard <jguichar@cisco.com>
  Thomas Narten <narten@us.ibm.com>

Assigned Area Director:
  Adrian Farrel <adrian@olddog.co.uk>

Mailing list
  Address: nsc@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/nsc
  Archive: http://www.ietf.org/mail-archive/web/nsc/

Charter:

Network operators frequently utilize service functions such as packet
filtering at firewalls, load-balancing and transactional proxies (for
example spam filters) in the delivery of services to end users. Delivery
of these types of services is undergoing significant change with the 
introduction of virtualization, network overlays, and orchestration. 

Deploying service functions to support service delivery is currently both
a technical and an organizational challenge that involves significant
modification to the network configuration, impacting the speed at which
services can be deployed and increasing operational costs. Such
services are typically implemented by the ordered combination of a
number of service functions that are deployed at different points within
a network. 

Today, common deployment models have service functions inserted on
the data-forwarding path between communicating peers. Going forward,
however, there is a need to move to a different model, where service
functions, whether physical or virtualized, are not required to reside on
the direct data path and traffic is instead steered through required
service functions, wherever they are deployed.

For a given service, the abstracted view of the required service 
functions and the order in which they are to be applied is called a
Service Function Chain (SFC). An SFC is instantiated through selection
of specific service function instances on specific network nodes to form
a service graph: this is called a Service Function Path (SFP). The 
service functions may be applied at any layer within the network
protocol stack (network layer, transport layer, application layer, etc.).
  

The SFC working group will document a new approach to service delivery
and operation. It will produce an architecture for service function 
chaining that includes the necessary protocols or protocol extensions to
convey the Service Function Chain and Service Function Path information 
to nodes that are involved in the implementation of service functions 
and Service Function Chains, as well as mechanisms for steering traffic
through service functions. The WG will examine existing identifier
schemes,
if there is a need for such identifiers in the context of the Generic SFC
encapsulation, before defining any new identifier scheme.

The working group will examine what information needs to be gathered
from the network and service functions in support of Service Function 
Chaining and how that information may be made available to the
components of the Service Function Chaining architecture. The SFC
WG will closely consider and address the management and security 
implications when documenting these deliverables.  

Specifically, the SFC WG is chartered to deliver the following:   

1. Problem Statement: This document will provide a summary of the
   problem space to be addressed by the SFC working group including
   example high-level use cases. Additionally, the working group will
   normalize nomenclature and definitions for service function chaining.

2. Architecture: This document will provide a description of the SFC 
   architectural building blocks and their relationships including 
   interconnection, placement of SFC specific capabilities, management,
   diagnostics, design analysis, and security models, as well as
   requirements on the protocol mechanisms.  The initial scope is
   restricted to a single administrative domain, keeping in mind that
   architectural decisions made for the intra-domain case may have 
   implications for the inter-domain case. 

3. Generic SFC Encapsulation: This document will describe a single 
   service-level data plane encapsulation format that:
   - indicates the sequence of service functions that make up the
     Service Function Chain
   - specifies the Service Function Path,
   - communicates context information between nodes that implement 
     service functions and Service Function Chains.
   It is intended that the encapsulation format be agnostic to the 
   layer at which it is applied and the service that is being
   constructed. That is, the same encapsulation may be used on a
   service function chain applied at the network layer or at any other
   layer, and the same encapsulation format will apply for the
   construction of Service Function Paths regardless of the actual
   service. The working group will consider using an existing 
   encapsulation (with extensions as appropriate) if a suitable 
   candidate is found.

4. Control Plane Mechanisms: A document will be developed to describe
   requirements for conveying information between control or management
   elements and SFC implementation points. All protocol extension work 
   resulting from these requirements should be carried out in the 
   working group responsible for the protocol being modified in 
   coordination with this working group, but may be done in this working
   group under a revised charter after agreement with all the relevant
   WG chairs and responsible ADs.

5. Manageability: Work on the management and configuration of SFC 
   components related to the support of Service Function Chaining will
   certainly be needed, but first needs to be better understood and 
   scoped.

Milestones:
  Apr 2014 - Submit to IESG Information document defining the SFC problem
statement and core use cases
  Apr 2014 - Consult with OPS area on possible SFC charter modifications
for management and configuration of SFC components related to the support
of Service Function Chaining
  Jan 2015 - Submit to IESG Informational document defining the
architecture for SFC
  Jan 2015 - Informational document defining the control plane
requirements for conveying information between control or management
elements and SFC implementation points
  Aug 2015 - Submit to IESG Standards Track document specifying the
generic service function chaining header encapsulation