Coordination of mobility solutions

As promised, let me enumerate the "protocol" worked involved for solutions aimed at "discovery, selection, and coordinated execution of mobility protocols at multiple layers". 

- Discovering network's mobility capabilities:

Whether it supports PMIP, LISP,  etc.
Possible approach is to define new DHCP options to deliver this "network info" to the terminal.

- Discovering corresponding node's mobility capabilities:

Whether it supports MPTCP, MIP route optimization, etc.
Possible approach is to use DNS-based discovery.


Discovering the MN's own mobility capabilities does not involve any protocol work. It may be based on platform-specific methods, API, application profiling, etc.

How the terminal selects the mobility protocol(s) to apply to a given flow, and how it coordinates execution of them are materials for an "informational" document that'd also refer to the aforementioned discovery elements.

Like Danny was suggesting, we can tackle this in the working team that deals with the source address selection, as there's an interaction  between the two. Whether a flow needs a fixed or sustained or nomadic IP address is influenced by whether the application traffic would need IP-layer mobility or not.

Alper