sadah
Uploaded by
8 SLIDES
160 VUES
80LIKES

Effective Connection Management for Mobile Internet Hosts

DESCRIPTION

Addressing interface connectivity, policy management, and network selection for seamless mobile internet experience. Focus on resolving connectivity issues and harmonizing policies across different domains. Proposal for a comprehensive Connection Manager solution.

1 / 8

Télécharger la présentation

Effective Connection Management for Mobile Internet Hosts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. ProblemStatementI • 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. TCPconnectionbreaks as routing table and next hop changes for thatTCP(It is the case for Weakhost 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 Connectivitycheck » (multiple methodswhichmay not be compatible with network featuressuch as FW, …) • Possible solution : definemethods & addstate to IP interface periodicaly • Case 3 : IP interface is active but layer 2 ispoorso no trafficcansucceed • Possible solution: use L2 triggers

  3. ProblemStatement II • Policy Management • ReconcilevariousPoliciesat 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… )

  4. 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 virtualinterfaces

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

  6. 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,….)

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

  8. End

More Related