Hi DMM folks, Yesterday, I created a ticket on the on-demand mobility issue. I believe this is critical to be essentially implemented in the on-demand WG draft. We can start a discussion based on the raised description.
Best Regards, Seil Jeon -----Original Message----- From: dmm issue tracker [mailto:trac+...@tools.ietf.org] Sent: Tuesday, May 19, 2015 6:43 PM To: draft-ietf-dmm-ondemand-mobil...@tools.ietf.org; seilj...@av.it.pt Cc: dmm@ietf.org Subject: [dmm] #49 (ondemand-mobility): full on-demand mobility support #49: full on-demand mobility support The three proposed flags express a “type” of source IP address an application wants to get to the IP stack. Particularly, the sustained IP address is proposed to provide on-demand IP session continuity, which activates IP mobility once the terminal moves across other access network. While the terminal stays at the same network where the session is initiated, regular IP routing is applied. The on-demand draft does not assure provide the full on-demand mobility for all scenarios by merely indicating the Socket API, IPV6_REQ_SUSTAINED_IP. An example scenario raising the aforementioned issue is as follows; 0. The MN is configured with one or more Nomadic IP addresses. 1. Once an app. requests “sustained IP address” to the IP stack, and it will obtain a sustained IP address through a protocol procedure between the terminal and network. 2. Other app. initiated over the same access network will use the same sustained IP address while the terminal remains connected at the same access network. 3. The terminal moves to another access network and a new app. requests a sustained IP address with the Socket API to the IP stack. Since a sustained IP address is already available in the IP stack, the sustained IP address is assigned to the new app. Besides, in case sustained IP address allocation is used default, there may be multiple sustained IP addresses including newly obtained sustained IP address over the new access network in the IP stack. However, when an app. is initiated, the IP stack may not select the new one in the context of the default source IP address selection mechanism [RFC6724][RFC5014]. For providing the full on-demand mobility, a new flag is needed, letting the IP stack request a new sustained IP address or choose a sustained IP address not requiring IP mobility anchoring when an application is initiated, among the existing ones in the IP stack. -- -------------------------+---------------------------------------------- -------------------------+--- Reporter: | Owner: draft-ietf-dmm-ondemand- seilj...@av.it.pt | mobil...@tools.ietf.org Type: defect | Status: new Priority: critical | Milestone: Component: ondemand- | Version: mobility | Keywords: on-demand mobility Severity: Submitted | WG Document | -------------------------+---------------------------------------------- -------------------------+--- Ticket URL: <http://trac.tools.ietf.org/wg/dmm/trac/ticket/49> dmm <http://tools.ietf.org/dmm/> _______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
