MIF API Extension Discussion MIF IETF 78 Dapeng Liu Yuri Ismailov.

Slides:



Advertisements
Similar presentations
Happy Eyeballs Extension for Multiple Interfaces Gang Chen Carl
Advertisements

MPTCP Application Considerations draft-scharf-mptcp-api-01 Michael Scharf Alan Ford IETF 77, March 2010.
Draft-ietf-mptcp-api-01 Michael Scharf, Alan Ford March 31, 2011.
WELCOME! Multipath TCP Implementors Workshop Saturday 24 th July Maastricht Philip Eardley MPTCP WG Co-chair.
Applications Test Results in MIF environment draft-zheng-mif-apps-test-02.txt IETF 81 Quebec City.
Internet Area IPv6 Multi-Addressing, Locators and Paths.
Chapter 10 IPv4 and IPv6 Interoperability. contents Introduction IPv4 Client, IPv6 Server IPv6 Client, IPv4 Server IPv6 Address Testing Macros IPV6_ADDRFORM.
IPv6 Privacy Hannes Tschofenig, Tara Whalen. Agenda Privacy Threats Layering Addressing Policy Questionnaire.
Socket Programming with IPv6. Why IPv6? Addressing and routing scalability Address space exhaustion Host autoconfiguration QoS of flow using flowlabel.
TDTS21 Advanced Networking
IETF DMM WG Mobility Exposure and Selection WT Call#1 Oct 23, 2014.
A CHAT CLIENT-SERVER MODULE IN JAVA BY MAHTAB M HUSSAIN MAYANK MOHAN ISE 582 FALL 2003 PROJECT.
Draft-deng-mif-api-session-continuity-guide Hui Deng Suresh Krishnan
MIF API draft-ietf-mif-api-extension-05 Dapeng Liu.
Controlling Traffic Offloading Using Neighbor Discovery Protocol IETF#80 Mif WG, 28-March-2011 draft-korhonen-mif-ra-offload-01 Jouni Korhonen Teemu Savolainen.
Host Identity Protocol
Host Mobility for IP Networks CSCI 6704 Group Presentation presented by Ye Liang, ChongZhi Wang, XueHai Wang March 13, 2004.
IETF DMM WG Mobility Exposure and Selection WT Call#2 Nov 6, 2014.
Use Cases and API Extension for Source IP Address Selection draft-sijeon-dmm-use-cases-api-source-00.txt Presenter: Alper Yegin Authors: Seil Jeon, Sergio.
HIP API issues in base spec Tom Henderson IETF-59, March 3, 2004.
Unrestricted Connection manager MIF WG IETF 78, Maastricht Gaëtan Feige, Cisco (presenter) Pierrick Seïté, France Telecom -
Enabling Embedded Systems to access Internet Resources.
Windows 7 Firewall.
Module 4: Configuring ISA Server as a Firewall. Overview Using ISA Server as a Firewall Examining Perimeter Networks and Templates Configuring System.
Unrestricted Connection Manager MIF WG IETF 79, Beijing Gaétan Feige - Cisco Pierrick Seïté, France Telecom - Orange
Starting Work on the MIF Analysis Document Hui Deng, China Mobile Margaret Wasserman, Sandstorm IETF 76, Hiroshima, Japan.
Real-time Flow Management 2 BOF: Remote Packet Capture Extensions Jürgen Quittek NEC Europe Ltd, Heidelberg, Germany Georg Carle GMD.
Reconsidering Internet Mobility Alex C. Snoeren, Hari Balakrishnan, M. Frans Kaashoek MIT Laboratory for Computer Science.
API Extension Discussion for MIF-enabled Hosts IETF#77 Dapeng Liu, Zhen Cao.
What is SIGTRAN?. SIGTRAN Signaling Transport (SIGTRAN) is an Internet Engineering Task Force (IETF) standard for transporting Public-Switched Telephone.
4.1.4 multi-homing.
Use of the IPv6 Flow Label as a Transport-Layer Nonce draft-blake-ipv6-flow-nonce-02 Steven Blake IETF 76 November 2009.
Multiple Interfaces (MIF) WG IETF 79, Beijing, China Margaret Wasserman Hui Deng
1 NetLMM Vidya Narayanan Jonne Soininen
RTCWEB Considerations for NATs, Firewalls and HTTP proxies draft-hutton-rtcweb-nat-firewall- considerations A. Hutton, T. Stach, J. Uberti.
The Client-Server Model And the Socket API. Client-Server (1) The datagram service does not require cooperation between the peer applications but such.
Analysis and recommendation for the ULA usage draft-liu-v6ops-ula-usage-analysis-00 draft-liu-v6ops-ula-usage-analysis-00 Bing Liu(speaker), Sheng Jiang.
Discussion of MIF API draft-liu-mif-api-extension-04 IETF 80 March 28, 2011 Dapeng Liu.
Use-cases and Requirements for MPTCP Proxy in ISP Networks Lingli Deng, Dapeng Liu, Tao Sun, Mohamed Boucadair, and Gregory Cauchie draft-deng-mptcp-proxy-00.
Teacher:Quincy Wu Presented by: Ying-Neng Hseih
IP Configuration API. Network Interface Configuration NAIfconfigIsDeviceUp() NAIfconfigDeviceFromInterface() NAIfconfigBringDeviceUp() NAIfconfigSetIpAddress()
Site Multihoming for IPv6 Brian Carpenter IBM TERENA Networking Conference, Poznan, 2005.
IETF70 - Mobopts RG1 On Mobile IPv6 Optimization and Multihoming draft-ng-mobopts-multihoming-00.txt Chan-Wah Ng
Default Address Selection for IPv6 Richard Draves March 19, 2001 Minneapolis IETF Meeting draft-ietf-ipngwg-default-addr-select-03.
API Extension for MIF- enabled Hosts Dapeng Liu, Zhen Cao, Bo Zhou.
MPTCP proxy mechanisms (draft-wei-mptcp-proxy-mechanism-00)
API Extension Discussion for MIF-enabled Hosts IETF#77 Dapeng Liu, Zhen Cao.
Multiple Interfaces (MIF) WG documents status MIF WG IETF 80, Prague Problem statement and current practices documents.
IP Security (IPSec) Matt Hermanson. What is IPSec? It is an extension to the Internet Protocol (IP) suite that creates an encrypted and secure conversation.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Flow Distribution Rule Language for Multi-Access Nodes draft-larsson-mext-flow-distribution-rules-01.
Network Load Balancing Addressing
Exposing Link-Change Events to Applications
Discussion on DHCPv6 Routing Configuration
Thierry Ernst (INRIA and WIDE) Hesham Soliman (Ericsson)
4.1.5 multi-homing.
Information Security Professionals
IEEE 802 OmniRAN Study Group: SDN Use Case
Teemu Savolainen (Nokia) MIF WG IETF#75 28-July-2009
Reliable Sockets: A Foundation for Mobile Communications
SCTP v/s TCP – A Comparison of Transport Protocols for Web Traffic
Multipath TCP Yifan Peng Oct 11, 2012
* Essential Network Security Book Slides.
Considerations for MPTCP Operation in 5G
An Update on Multihoming in IPv6 Report on IETF Activity
IETF-100, MPTCP WG, November 2017
PMIP6 extensions for inter-access handovers and flow mobility
MIF DHCPv6 Route Option Update
Load balancing of a wireless network
How Applications (Will Hopefully Soon) Use the Internet
Presentation transcript:

MIF API Extension Discussion MIF IETF 78 Dapeng Liu Yuri Ismailov

Agenda Background & Motivation for MIF API Extension Potential Scope of MIF API Re-charter discussion of MIF API

Background for MIF API Extension There are already Socket API extension work in IETF IPv6 MPTCP SHIM6 HIP SCTP

CategoryDescriptionDocument IPv6 socket(AF_INET6, SOCK_STREAM, 0); socket(AF_INET6, SOCK_DGRAM, 0); IPv6 address structure IPv6 Socket address structure RFC 3493: Basic Socket Interface Extensions for IPv6 Informational MPTCPNew options for getsockopt()/setsockopt() TCP_MP_ENABLE: Enable/disable MPTCP TCP_MP_SUBFLOWS: Get the addresses currently used by the MPTCP subflows TCP_MP_PROFILE: Get/set the MPTCP profile MPTCP Application Interface Considerations Informational SHIM6New options for getsockopt()/setsockopt() SHIM_ASSOCIATED/SHIM_DONTSHIM/SHIM_HOT_STANDBY/SHIM_LOC_LO CAL_PREF Socket Application Program Interface (API) for Multihoming Shim Informational HIPNew socket/resolver structure for HIP New options forgetsockopt()/setsockopt() SHIM_LOC_LOCAL_PREF/SHIM_LOC_PEER_PREF… Basic Socket Interface Extensions for Host Identity Protocol (HIP) Experimental Examples of Socket API Extensions

Background for MIF API Extension Motivation 1: Once there is a device with multiple interfaces, which can be operational simultaneously we face up the problem of making a choice. The choice of the interface may be centralized (per device policy) or distributed (every application decides which interface(s) to use and for which flow) If the choice either centralized or distributed, then there is no collision between those two approaches If there is more than one centralized approach to interface selection then only one at a time can be used otherwise collision is possible.

Example of collision case Mobile IP with multiple CoA (centralized) The concept is to make visible a single interface for applications and the choice of where to send the traffic is up-to MIP mechanism PMIP logical interface for flow mobility (centralized) Similar to MIP. Could not be used at the same time with MIP interface because will compete for being default for applications. The same referrs to HIP, SHIM6, and probably some other approaches as well.

Potential MIF API Solution Distributed approach to interface selection Leaves choices for applications, however Assume MIP is running at the same host... Assume PMIP logical interface configured in the same host... One of possible approaches to avoid this is to assign type of interfaces for logical interfaces, but then applications will have to be aware about MIP, PMIP, etc. This goes against MIP, PMIP, … concept. MIF host Application need this flexibility According to real development and coding experience

Motivation 2 MIF host has DNS split issues Gethostbyname()/Getaddrinfo() – Lack the ability to specify which DNS server New DNS API parameters for DNS-split?

Motivation 3 Connection Manager API need to have standardized Behavior – Provide information to application: e.g. allow the application to adapt their behaviour to the selected physical interface – Receive command from application: in order to allow the Interface to user space: allow the user to provide its preferences – Interface to operator policy provisioning: get policy from operator

Agenda Motivation for MIF API Extension Potential Scope of MIF API Re-charter discussion of MIF API

Potential MIF API Scope MIF API used for interface selection MIF API used for DNS selection MIF API used for Connection Manger

Agenda Motivation for MIF API Extension Potential Scope of MIF API Re-charter discussion of MIF API

Work Item: – An API describing how applications can exploit additional features of multiple interfaces enabled stack. This API should be an optional extension to the current set of networking API, that provides ability of interface selection, dns selection, etc. Expected output: – Informational RFC