unrestricted Connection Manager MIF WG IETF 79, Beijing Gaétan Feige - Cisco Pierrick Seïté, France Telecom - Orange MELIA, TELEMACO - ALU Zuniga, Juan Carlos - InterDigital

unrestricted Problem Statement I  Availability of interface connectivity to internet –IP interface is configured but no internet connectivity ( eg « web logon » is required ( Hot Spot )) – Case 1 : a TCP session was running before the routing table priority changed. TCP connection breaks as routing table and next hop changes for that TCP (It is the case for Weak host model RFC1122) – Case 2 : Multi session application where new TCP connections are established using different source address (« but application should request from socket the initial IP and hence it would work » ) –Possible solution : add state to IP interface at initialization –Interface connectivity is interrupted – Case 1 : Active application sessions need to survive path failures. –Possible solutions : multipath ( MPTCP, SCTP multihoming), failover (MIPx, SHIM6), true session layer 5 – Case 2 : OS built in « IP Connectivity check » (multiple methods which may not be compatible with network features such as FW, …) –Possible solution : define methods & add state to IP interface periodicaly – Case 3 : IP interface is active but layer 2 is poor so no traffic can succeed –Possible solution: use L2 triggers

unrestricted Problem Statement II  Policy Management –Reconcile various Policies at the host level – Policies from user / IT / Network / default-OS – when to apply updates : real time or at « session » initiation –Consistent Policy Conflict Resolution across functions: – Naming (DNS, WINS) ( local to a specific forwarder -> add a specific route to interface ) ( proposed fixed in Teemu’s draft ) – Configuration ( DHCP, ND, …) – Routing ( Source Address Selection, ND, IPv6 advanced routing… )

unrestricted Problem Statement III  Currently not included in the charter –Network Selection – Layer II selection –Layer II interactions –Monetary cost –Application requirements –… –Possible solution : policy framework + APIs –Mobility – Support of multiple interfaces belonging to the same administrative domain – Support of IP Flow Mobility –Possible solution : Policy control and configuration of the system virtual interfaces

unrestricted 3GPP Liaison  Multiple internet connection ( 3GPP MAPCON ) –MAPCON is about multiple PDN connections simultaneously –Each PDN is an IP interface – 3GPP does not know how to define the exact MIF issue of resolving policy conflicts and interface DNS/routing selection

unrestricted Summary  Connection / Session manager is a key point for MIF host –The CM deals with MIF issues, it is a « non protocol » specification but deals with how a host should behave in terms of inter component state machines and reconciliates conflicts based on policies –The CM handles the user experience (e.g. "smart" domain selection, source address selection, loging, IP connectivity checks, multipath, cost) => optimize ressource usage and QoE for end-user –The CM makes decisions based on various criteria (application requirement, user preferences, operator policies, available QoS,….)

unrestricted Possible scope for the work item  BCP  lists  Functions and associated operations  APIs The two above deliverables provide a Connection Management conceptual architecture –Do we modify the charter for the non yet included items ?

unrestricted End