1 / 10

Current Practices in Mobile and Desktop Connection Management

This document outlines the current practices for connection management across various platforms, including mobile systems (such as Nokia S60, Windows Mobile, Blackberry, and Google Android) and desktop environments (like Windows and Linux). It highlights the role of connection managers in facilitating transparent multiple interface usage for applications, addressing user-configured policies, and resolving conflicting configuration information. The document emphasizes collaboration and calls for further contributions to ensure comprehensive coverage of implementations, with an eye on upcoming updates and timelines for further review by the IETF.

rue
Télécharger la présentation

Current Practices in Mobile and Desktop Connection Management

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. MIF Current Practicesdraft-ietf-mif-current-practices-00.txt Margaret Wasserman mrw@sandstorm.net IETF 76, Hiroshima, Japan

  2. Mobile Nokia S60 (Symbian) Windows Mobile 2003 Blackberry Google Android Arena Connection Manager Desktop Windows 2000, XP, Vista, Server 2003 Linux BSD-based systems Apple Mac OS Implementations Included

  3. Others Coming • Qualcomm AMSS/Brew • Sent to list by George Tsirtis • Windows 7 • TBD (from Gabriel Montenegro) • Still looking for details about Apple iPhone

  4. Different Perspectives • Mobile vendors approach from the top • Applications know what “connection” they want • To make multiple interfaces transparent to applications, connection manager is added • Policy/configuration comes from user • Stack interface extensions, as needed • Even here, stack needs to know what to do if information is not provided by app

  5. Different Perspectives (cont) • Desktop vendors approach from bottom • Stack includes mechanisms to select appropriate address(es) and interface • Conflicting configuration information (DHCP, DNS, NTP) is resolved within the operating system • Some allowance for per-application overrides

  6. MIF Approaches Application Connection Mgr • Application Layer • Apps know what “connection” they use • Or unified connection manager • Interface between Apps & Stack • What information can be passed in • Advice or override? • IP Stack • Including DNS, DHCP Interface (e.g.Sockets API) TCP/IP Stack (w/DHCP/DNS) Before selection Outbound interface selection After selection

  7. Changes in WG -00 • Updated to match problem statement • Moved summary to beginning, system specifics to end • Added more implementation details for some systems

  8. Work in Progress • Indicate what included implementations do at all three levels: • Application/Connection Manager support • Interface between apps and stack • Within the stack • Indicate what support (if any) there is for remote configuration/policy setting

  9. Missing Information • Lots of information still needed • Will send e-mail to contributors for each implementation with specific requests • If you know about an implementation that is not included, please send e-mail

  10. Next Steps • Expect new draft for WG review by EOY • Target Schedule: • Complete content by IETF 77 (March 2010) • WG Last Call in April/May 2010 • To IESG in June/July 2010

More Related