1 / 9

Addressing Challenges in Multi-Interface Hosts: Analysis & Solutions

This document outlines problems faced by multi-interface hosts, current practices, and proposes solutions. It examines application layer, connection management, TCP/IP stack, IETF standards, and future considerations.

erwin
Télécharger la présentation

Addressing Challenges in Multi-Interface Hosts: Analysis & Solutions

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. Starting Work on theMIF Analysis Document Hui Deng, China Mobile Margaret Wasserman, Sandstorm IETF 76, Hiroshima, Japan

  2. WG Deliverables • Problem Statement (WG Draft) • What problems do multiple interface hosts have to handle? • Current Practices (WG Draft) • How do current implementations deal with those problems? • Analysis Document (Starting Now)

  3. Purpose of Analysis • Do current practices solve the MIF problems? Or are there gaps? • If current practices work, should we standardize them? • If not, can we design solutions that fill the gaps?

  4. Selection at Different Layers 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

  5. Application Layer • Application layer: • How do apps indicate what they want? Treated as advice or override? • Application knowledge (compiled in) • Along with API extensions to allow apps full control • Should applications need to know what interfaces are available? • Connection Manager • User policies/configuration to override connection manager default • MISSING: Configuration policy doesn't come from the other side/network

  6. TCP/IP Stack • What does the TCP/IP stack do with multiple sets of information? • How does the stack get/store configuration information • Per stack? Per interface? • MISSING: • Per interface configuration in some cases (DHCP, DNS, etc.) • Per prefix configuration for default gateway and routing?

  7. Current IETF Standards • The standard data model (MIBs, Netconf schema, etc.) • Single routing table • MISSING: No information scoped per-interface or per-prefix • DHCP on multiple interfaces • MISSING: Mechanisms to select/merge info from multiple servers

  8. Current IETF Standards (cont) • Address selection algorithm • MISSING: Policy support, per prefix selection • Sockets API • Override source address selection • MISSING: Overrides for outbound interface selection, DNS server selection

  9. Going Forward • Do we have agreement on the scope of this document? • Need to get document written/adopted • Target Schedule • Document out by EOY 2009 • Adopted by March/April 2010 • WG Last Call July/Aug 2010 • Submit to IESG Sept 2010

More Related