110 likes | 528 Views
Service Function Chaining in Mobile Networks Status draft- haeffner - sfc -use-case-mobility. IETF 89 London , 3 March 2014 Service Function Chaining WG Walter Haeffner - walter.haeffner@vodafone.com , Jeff Napper - jenapper@cisco.com
E N D
Service Function Chaining in Mobile NetworksStatus draft-haeffner-sfc-use-case-mobility IETF 89 London, 3 March 2014 Service Function Chaining WG Walter Haeffner - walter.haeffner@vodafone.com, Jeff Napper - jenapper@cisco.com Martin Stiemerling - mls.ietf@gmail.com, Diego R. Lopez - diego@tid.es IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobilityacknowledgement • We thank Linda Dunbar • Ron Parker • Wim Hendericks • Alla Goldner • Dave Dolson • Peter Bosch • Praveen Muley • Carlos Correia, ...... for valuable comments IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility1 – context Mobile network operators need to implement a complex array of single- (or few-) function devices ( a.k.a. SFC) to control data traffic such that they can achieve their business goals. per userpolicy and chargingenforcement PCRF caches • IPTV • eMail • VoIP P-GW • YouTube • bing • iTunes 3GPP Mobile Network > SFC < DCAppl. protect network & privacy – FW, IDS, ACL, ... optimize transport & payload – TCP Opt., Video Opt., ... functions required for technical reasons – GC-NAT, DPI, LB, ... merge signaling information into data flow - HTTP header enrichment, ... network-based value added services – parental control, malware protection, ... @Appl. IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility2 - objectives • Understand importance of Service Function Chaining formobile network operators - Influence to their business • Discuss Service Function Chains (SFC) in the context of mobilenetwork architectures – exemplary state of the art use cases • Work out potential weaknesses in current environments andderive operator requirements to support SFC WG objectives • Compare with activities of other standard bodies, especially clarify interaction between 3GPP and IETF SFC approach • A possible dream SFC environment from an operator’s point of view based on NFV, SDN, reflecting abstraction levels .... IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility3 – status draft • Draft-00 issued 29 Jan. 2014 • Service chains supplement 3GPP policy and charging control architecture • PCC and SFCs play a significant role in mobile service specifications • SFCs often a sequence of “little” proprietary SFC implementations • Therefore typically a hierarchy of inspections & classifications in place • Discussed simple classification and flow steering schemes • Sketched use case “video optimization” (L7) and “TCP optimization” (L4) • Discussed weakness of current solutions and requirements to SFC WGs • Draft-01 issued 14 Feb. 2014 • Added 3GPP R11 Traffic Detection Function (TDF) [3GPP TS.23.203] • Allows for fine grained classification schemes and feedback to PCC IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility3 – status draft - basics of a video optimization SFC Functional view of a model video optimizer SFC Cache classified“video” e.g. VoIP DPI DPI CrtlDPI VideoOpt. VideoOpt. VideoOpt. P-GW LB LB FW NAT @ classified“port 80” • “port 80 no video” • “non-port 80” classified“web service” Draft-00 & draft-01 shows flow steering based on HTTP redirections IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility4 – outlook draft-02 to be published end of March Discuss impact of re-classification and chains of value added services. Load Action/Forwardingbased on NW Load PCRF 4G (LTE) VideoSFC GW move RAT = 4G : opt .off RAT = 3G : opt. on 3G (UMTS) RAT VAS @ Malware Prevention DPI @ Port 80 IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility5 – outlook draft-02 to be published end of March Grown multi-vendor structures may become very complex, inefficient, hard to understand and hard to manage re-classify RAT VideoOpt. classified video VideoCache PCRF MalwarePrev. CRTL DPI classified port 80 classified port 80, non-video P-GW FWNAT @ WebAPN WebAPN WebAPN LB LB DPI LBDPI classified non-port 80 does not reflect wiringandactual packet flow! TCP Opt. Analytics ParentalControl vendor a vendor b vendor c IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility5 – Weaknesses and Requirements • Weaknesses in current deployments • Per APN service chaining, in almost any case classification too coarse grained • Means traffic often unnecessarily traverses a service function, no offloading • Often ad hoc sequence of individual mini-chains, each with its own classification • Results in multiple, individual DPI inspection systems, multiple LB batteries • Is expensive, complex, inflexible, hard to modify/extend with reduced performance • Possible solutions • Mobile network MUST exchange context with the IETF SFC classifier function • SFC classifier MUST tag packets such that these enter only the SFs required • Means bi- and unidirectional flows MUST be allowed • Individual SFs MUST participate in multiple, different SFCs • Creation/modification of SFCs including their branching rules SHOULD bedone in a simple to use SFC editor. Mapping onto the underlay MUST then be automatic. IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility6 – IETF SFC interactions with 3GPP PCC architecture How to exchange 3GPP user & control plane metadata with IETF SFC? OnlineCharging System Subscription Profile Repository Application Functions Metadata Exchange ? Sp Rx Sy PCRF IF ? Sd Gxx Gx Gy [DPI] “3GPP Classifier” IETF SFC-1 P-GW Access Network Gateway IETF SFC Classifier TDF BBERF PCEF IETF SFC-n OfflineCharging System IETF SFC 3GPP PCC BBERF: Bearer Binding and Event Reporting Function IETF 89 - London, UK - 3 March 2014
draft-haeffner-sfc-use-case-mobility7 – outlook draft-IETF 90 • Listed all use case classes required to verify universalityof SFC WG architecture and design paradigms for mobile. • Isolate input to requirements and functional specifications. • SFCs for fixed networks (xDSL, Cable) are typically a subsetof what is seen in mobile. List synergies w.r.t. FMC scenarios. • Analyse requirements for the interaction between the 3GPPand the IETF SFC classification schemes. • Initiate a discussion to clarify how to proceed in case of encrypted traffic (IETF 88 resolution). IETF 89 - London, UK - 3 March 2014