Seil Jeon, Sergio Figueiredo, Younghan Kim, John Kaippallimalil 97th IETF, Nov. 2016, (Seoul, Korea) Use Cases and API Extension for Source IP Address Selection draft-sijeon-dmm-use-cases-api-source-05.txt Seil Jeon, Sergio Figueiredo, Younghan Kim, John Kaippallimalil

Overview This draft is about “use cases” analysis of the DMM on-demand mobility WG draft In addition, an API proposed to address a gap from the analysis

Status Presented two times in 93rd Prague meeting and 94th Yokohama meeting Revised for clarity in -05 (current) draft

Motivation What source IP addresses for apps? Sus-C:: Sus-A:: Sus-B:: AR3 AR1 AR2 Sus-A:: ? Sus-A:: or Sus-B:: (?) App1 App2 Sus-A:: Sus-A:: ? ? App1 App1 App2 App3 App4 App5 MN MN MN

Issue #1 “Acquiring a new session-lasting IP address may take some time (due to the exchange with the network) while using an existing one is instantaneous On the other hand, using the existing one might yield less optimal routing” Might not be preferred by newly initiated applications

Issue #2 FRC 3484, “Default Address Selection for IPv6” For example, Rule 8: Use longest matching prefix. If CommonPrefixLen (SA, D) > CommonPrefixLen(SB, D), then prefer SA. This may also lead a undesired behavior in the source IP address selection

ON_NET property IPV6_XX_SRC_ON_NET /* Require (or Prefer) an IP address based on a requested IP address type as source, assigned from the current serving network, whatever it has been assigned or should be assigned */

Way Forward Adoption for a WG document?