Fast Handover for IP Flow Mobility

1
Fast Handover for IP Flow Mobility

• draft-zhao-mipshop-fho-flows-00
• Fan Zhao, Ameya Damle

2
Outline

• Overview
• Flow handover scenarios
• Issues
• Discussion

3
Overview

• RFC 5268 aims to optimize performance, such as
  packet loss and delay etc, during handover.
• RFC 5268 can be considered as optimization when
  all flows are handed over to the target access
  network.
• The MIP protocol has been extended with
• MCoA simultaneous attachment via multiple access
  networks
• Flow binding binding a particular flow to an
  interface since certain flow(s) may be better
  suited to the characteristics of a certain access
  network.

4
Flow handover scenarios

• Flow handover scenarios (both modes, though
  focusing on predictive mode) are introduced with
  such extensions.

5
Flow handover scenarios

• This scenario is related to the PFMIP and is also
  discussed in another presentation.

6
The FHO for IP flow mobility problem

• Slightly different from that of the FHO
• how to allow a mobile node to send uplink packets
  via a better access link as soon as it detects
  such a new access link and how to deliver
  downlink packets to a mobile node via a better
  access link as soon as its attachment to such a
  new access link is detected by the new access
  router.
• Handover latency for a specific flow in such
  scenarios is expected to be not different from
  that of Mobile IPv6.

7
Issues

• Most FHO messages are expected to remain the
  same.
• The most notable changes are for the FBU/FBA.
• Use the BID and FID options to register flow
  bindings at the PAR
• Similar to the case when the MN simultaneously
  attaches both a home link and a foreign link
• The FHO requires the Alt-CoA in the FBU

8
Issues

• The MCoA draft does not specify a status code in
  the BID option, in case that the NCoA formulated
  by the MN may not be valid at the NAR, therefore
  a new NCoA needs to be provided in the FBA.

9
Further optimization

• With the P2P link, the MN can send the LLA (i.e.
  that of the interface attaching to the new link)
  in the BID option in the FBU to the PAR, so that
  certain flows can be forwarded via the new access
  link as soon as possible.

10
Discussion and Next step

• In our opinion, this issue should be addressed
  and clarified.
• It can be done with some small extensions.
• Your opinions and comments on this are very
  appreciated.