Hi Alper, I agree with you that there should be some kind of coordination between different mobility mechanisms. Thanks for providing this document, and here are some of my questions: (1) It's possible for orchestrator to discovery mobility capabilities such as MIPv6, PMIPv6, GTP, MPTCP, but I think it's not convenient to find out whether L7 application is mobility capable. (2) If there is no communication between MN and CN, then which mobility management scheme will be used when MN moving in network? (3) what's the criteria for Mobility Protocol Selection in section 4.4? I think that may depends on the characteristic of application traffic. (4) In Fig. 2, step 5b, you mean the DNS system is used to discovery CN's mobility capability? Could be explain how it works?
Thanks! Best Regards, Xinpeng From: dmm [mailto:[email protected]] On Behalf Of Alper Yegin Sent: Friday, July 04, 2014 3:11 PM To: [email protected] Subject: [DMM] draft-yegin-ip-mobility-orchestrator-00.txt Hello DMMers, We have a new I-D for your reading and discussion. Title : IP Mobility Orchestrator Authors : Alper Yegin Jungshin Park Kisuk Kweon Jinsung Lee Filename : draft-yegin-ip-mobility-orchestrator-00.txt Pages : 13 Date : 2014-07-03 Abstract: Host stacks can support mobility at multiple layers. Mobility protocols operating at different layers constitute alternate solutions with various pros and cons, and they can also have adverse affects on each other when used simultaneously. Optimal results in terms of seamless handover and data-path optimization can be achieved when execution of these protocols are coordinated. We'll also be submitting an IPR statement to IETF. https://datatracker.ietf.org/doc/draft-yegin-ip-mobility-orchestrator/ Please review this I-D and share your comments. Thanks, Alper
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
