Service Function Chaining Use Cases in Mobile Networks
draft-haeffner-sfc-use-case-mobility-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-02-14
Replaced by draft-ietf-sfc-use-case-mobility
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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
Intended status: Informational                                 J. Napper
Expires: August 18, 2014                                   Cisco Systems
                                                          M. Stiemerling
                                                                     NEC
                                                                D. Lopez
                                                          Telefonica I+D
                                                       February 14, 2014

         Service Function Chaining Use Cases in Mobile Networks
                draft-haeffner-sfc-use-case-mobility-01

Abstract

   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.

Requirements Language

   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].

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

Haeffner, et al.         Expires August 18, 2014                [Page 1]
Internet-Draft          SFC Use Cases in Mobility          February 2014

   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 August 18, 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
   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology and abbreviations . . . . . . . . . . . . . .   3
     1.2.  General structure of end-to-end carrier networks  . . . .   3
     1.3.  General scope of mobile service chains  . . . . . . . . .   5
     1.4.  General scope of mobile service chains  . . . . . . . . .   5
   2.  Mobile Network overview . . . . . . . . . . . . . . . . . . .   5
     2.1.  Building blocks of 3GPP mobile networks . . . . . . . . .   6
     2.2.  General scope of mobile service chains  . . . . . . . . .   7
     2.3.  The most common classification scheme . . . . . . . . . .   8
     2.4.  More sophisticated classification schemes . . . . . . . .   9
   3.  Example use cases specific to mobile networks . . . . . . . .  10
     3.1.  Service chain model for Internet HTTP services  . . . . .  11
       3.1.1.  Weaknesses of current approaches  . . . . . . . . . .  13
       3.1.2.  Requirements from use case  . . . . . . . . . . . . .  14
     3.2.  Service chain for TCP optimization  . . . . . . . . . . .  14
       3.2.1.  Weaknesses of current approaches  . . . . . . . . . .  15
       3.2.2.  Additional requirements from use case . . . . . . . .  15
   4.  Remarks on QoS in mobile networks . . . . . . . . . . . . . .  16
Show full document text