Service Function Chaining Use Cases in Mobile Networks

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-01-28
Replaced by draft-ietf-sfc-use-case-mobility
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Service Function Chaining                                    W. Haeffner
Internet-Draft                                                  Vodafone
Expires: August 2, 2014                                        J. Napper
                                                           Cisco Systems
                                                        January 29, 2014

         Service Function Chaining Use Cases in Mobile Networks


   This document provides some exemplary use cases for service function
   chaining in mobile service provider networks.  The objective of this
   draft is not to cover all conceivable service chains in detail.
   Rather, the intention is to localize and explain the application
   domain of service chaining within mobile networks as far as it is
   required to complement the problem statement and framework statements
   of the working group.

   Service function chains typically reside in a LAN segment which links
   the mobile access network to the actual application platforms located
   in the carrier's datacenters or somewhere else in the Internet.
   Service function chains ensure a fair distribution of network
   resources according to agreed service policies, enhance the
   performance of service delivery, take care of security and privacy or
   support application and business support platforms.  General
   considerations and specific use cases are presented in this document
   to demonstrate the different technical requirements of these goals
   for service function chaining in mobile service provider networks.

Status of This Memo

   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

   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 August 2, 2014.

Haeffner & Napper        Expires August 2, 2014                 [Page 1]
Internet-Draft          SFC Use Cases in Mobility           January 2014

Copyright Notice

   Copyright (c) 2014 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
   ( 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.

1.  Introduction

1.1.  Terminology and abbreviations

   Much of the terminology used in this document has been defined by the
   3rd Generation Partnership Project (3GPP), which defines standards
   for mobile service provider networks.  Although a few terms are
   defined here for convenience, further terms can be found in

   Device  A physical or virtualized function.

   < payload | IP header >  IP packet.

   UE User equipment like tablets or smartphones.

   S-IP  Source IP address.

   D-IP  Destination IP address.

   IMSI  The International Mobile Subscriber Identity that identifies a
      mobile subscriber.

   SGi, Gi  Egress termination point of the mobile network (SGi in case
      of LTE, Gi in case of UMTS/HSPA).  The internal data structure of
      this interface is not standardized by 3GPP.

   PCRF  3GPP standardized Policy and Charging Rules Function.

Haeffner & Napper        Expires August 2, 2014                 [Page 2]
Internet-Draft          SFC Use Cases in Mobility           January 2014

1.2.  General scope of mobile service chains

   Mobile access networks terminate at a mobile service creation point
   (Packet Gateway) typically located at the edge of an operator IP
   backbone.  From the user equipment (UE) up to the Packet Gateway
   (P-GW) everything is fully standardized by the 3rd Generation
   Partnership Project (3GPP) e.g., in [TS.23.401].  Within the mobile
   network, the user payload is encapsulated in 3GPP specific tunnels
   terminating eventually at the P-GW.  In many cases application-
   specific IP traffic is not directly exchanged between the original
   mobile network, more specific the P-GW, and an application platform,
   but will be forced to pass a set of service functions.  Those
   application platforms are, for instance, a web server environment, a
Show full document text