1. 2007.12.03IETF70 - Mobopts RG1 On Mobile IPv6 Optimization and Multihoming draft-ng-mobopts-multihoming-00.txt Chan-Wah Ng chanwah.ng@sg.panasonic.com Keigo Aso asou.keigo@jp.panasonic.com

2. 2007.12.03IETF70 - Mobopts RG2 Agenda Background Scenario: Multihomed Correspondent Node Problem with Route Optimization Possible Enhancement Approaches

3. 2007.12.03IETF70 - Mobopts RG3 Background Mobility and multihoming is getting more and more common An excellent discussion on their interactions –draft-vidya-ip-mobility-multihoming-interactions-01.txt Focus here is more on the performance of Mobile IPv6 when: –Mobile node is multihomed –Anchor point is multihomed –Correspondent node is multihomed Possibly to extend RFC4651

4. 2007.12.03IETF70 - Mobopts RG4 Scenario: Multihomed CN CN is multihomed: –CN is on an multihomed site –CN has multiple interfaces INTERNET INTERNET CN’s Network CN’s Network ER ER P1P1 P2P2 CN MN INTERNET INTERNET P1P1 P2P2 CN MN

5. 2007.12.03IETF70 - Mobopts RG5 Scenario: Multihomed CN CN uses multiple addresses when communicating with MN –Single Session Using SCTP or SHIM6 –Multiple Sessions Application-level flow distribution Different applications CN MN App SCTP/SHIM6 INTERNET INTERNET App SCTP/SHIM6 P2::CN P1::CN CN MN App1 TCP/UDP INTERNET INTERNET P2::CN P1::CN App2 App1 TCP/UDP App2

6. 2007.12.03IETF70 - Mobopts RG6 Problem with Route Optimization The MIPv6 layer at MN has no way of knowing that P1::CN and P2::CN belongs to the same node When route optimization is triggered, MN would –Trigger RR and send BU to P1::CN –Trigger RR and send BU to P2::CN CN MN P2::CN P1::CN HoTI HoT CoTI CoT BU BA HoTI HoT CoTI CoT BU BA Redundant!!!

7. 2007.12.03IETF70 - Mobopts RG7 Resolution Principle –Make Mobile IPv6 Layer aware of CN’s multihoming Two main approaches –Inter-layer APIs –MIPv6 RO Signaling

8. 2007.12.03IETF70 - Mobopts RG8 Inter-Layer APIs Allow applications or transport/SHIM layers to notify Mobile IPv6 layer –A list of addresses that are linked –CoA bindings at any address implies all CoA bindings at all linked address Pros –Simple, no protocol extension Cons –Applications, transport layers need to be changed –Does not work with multiple applications

9. 2007.12.03IETF70 - Mobopts RG9 Protocol Extension CN informs MN of its multiple addresses –After receiving HoTI/CoTI/BU –Response with list of addresses in HoT/CoT/BA Pros –Works for all applications Cons –Protocol extension needed –Requires more in depth considerations

10. 2007.12.03IETF70 - Mobopts RG10 Protocol Extension (cont’d) Design points to consider: –Which message to include the list of addresses? HoT, CoT, BA? –Notify all MNs or selectively? How to select? –Security consideration Threats on MN? –Fake list of linked address Threats on CN? –Reveal all of CN’s addresses

11. 2007.12.03IETF70 - Mobopts RG11 Discussion Is this work worth looking into in IRTF/IETF community? –Only multihomed CN is analyzed –Two more cases multihomed MN multihomed anchor points (eg. HA, MAP) Any similar work being done?