Service Function Chaining Use Cases in Mobile Networks
draft-ietf-sfc-use-case-mobility-07

Document Type Expired Internet-Draft (sfc WG)
Last updated 2017-04-16 (latest revision 2016-10-13)
Replaces draft-haeffner-sfc-use-case-mobility
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-sfc-use-case-mobility-07.txt

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 [RFC7498] and architecture framework [RFC7665] 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 (SFC) ensure a fair distribution of network resources according to agreed service policies, enhance the performance of service delivery or take care of security and privacy. SFCs may also include Value Added Services (VAS). Commonly, SFCs are typical middle box based services. 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. The specification of service function chaining for mobile networks must take into account an interaction between service function chains and the 3GPP Policy and Charging Control (PCC) environment.

Authors

Walter Haeffner (walter.haeffner@vodafone.com)
Jeffrey Napper (jenapper@cisco.com)
Martin Stiemerling (mls.ietf@gmail.com)
Diego Lopez (diego@tid.es)
Jim Uttaro (uttaro@att.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)