80 likes | 202 Views
MIF WG IETF 79, Beijing 2010-11-10 Gaétan Feige - Cisco gfeige@cisco.com Pierrick Seïté , France Telecom - Orange pierrick.seite@orange-ftgroup.com MELIA, TELEMACO - ALU telemaco.melia@alcatel-lucent.com Zuniga, Juan Carlos - InterDigital JuanCarlos.Zuniga@InterDigital.com.
E N D
MIFWGIETF79, Beijing 2010-11-10 Gaétan Feige - Cisco gfeige@cisco.comPierrick Seïté, France Telecom - Orangepierrick.seite@orange-ftgroup.com MELIA, TELEMACO - ALU telemaco.melia@alcatel-lucent.com Zuniga, Juan Carlos - InterDigital JuanCarlos.Zuniga@InterDigital.com ConnectionManager
ProblemStatement I • Availability of interface connectivity to internet • IP interface isconfigured but no internet connectivity ( eg « web logon » isrequired ( Hot Spot )) • Case 1 : a TCP session was running before the routing table prioritychanged. TCPconnection breaks as routing table and next hop changes for thatTCP(It is the case for Weak host model RFC1122) • Case 2 : Multi session application where new TCP connections are establishedusingdifferent source address(« but application shouldrequestfrom socket the initial IP and henceitwouldwork » ) • Possible solution : add state to IP interface at initialization • Interface connectivityisinterrupted • Case 1 : Active application sessions need to survive pathfailures. • Possible solutions : multipath ( MPTCP, SCTPmultihoming) , failover (MIPx, SHIM6), true session layer 5 • Case 2 : OS built in « IP Connectivity check » (multiple methodswhichmay not be compatible with network featuressuch as FW, …) • Possible solution : definemethods & add state to IP interface periodicaly • Case 3 : IP interface is active but layer 2 ispoorso no trafficcansucceed • Possible solution: use L2 triggers
ProblemStatement II • Policy Management • ReconcilevariousPolicies at the host level • Policiesfrom user / IT / Network / default-OS • when to apply updates : real time or at « session » initiation • Consistent Policy ConflictResolutionacrossfunctions: • Naming (DNS, WINS) ( local to a specificforwarder -> add a specific route to interface ) ( proposedfixed in Teemu’sdraft ) • Configuration ( DHCP , ND, …) • Routing ( Source AddressSelection, ND, IPv6advancedrouting… )
ProblemStatement III • Currently not included in the charter • Network Selection • Layer II selection • Layer II interactions • Monetarycost • Application requirements • … • Possible solution : policyframework + 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
3GPP Liaison • Multiple internet connection ( 3GPPMAPCON) • MAPCONis about multiple PDN connections simultaneously • EachPDNis an IP interface • 3GPPdoes not know how to define the exact MIF issue of resolvingpolicyconflicts and interface DNS/routingselection
Summary • Connection / Session manager is a key point for MIF host • The CM deals withMIFissues, itis a « non protocol » specification but deals with how a host shouldbehave in terms of inter component state machines and reconciliatesconflictsbased on policies • The CM handles the user experience(e.g. "smart" domainselection, source addressselection, loging, IP connectivitychecks, multipath, cost) => optimize ressource usage and QoE for end-user • The CM makesdecisionsbasedon variouscriteria (application requirement, user preferences, operatorpolicies, availableQoS,….)
Possible scope for the work item • BCP • lists • Functions and associatedoperations • APIs • The twoabovedeliverablesprovide a Connection Management conceptual architecture • Do wemodify the charter for the non yetincluded items ?