1. Fast handovers for PMIPv6 Hidetoshi Yokota KDDI Lab Kuntal Chowdhury Starent Networks Rajeev Koodli Nokia Siemens Networks Basavaraj Patil Nokia Siemens Networks IETF #70 Vancouver

2. 2 Motivation of Proxy-FMIPv6 Background  PMIPv6 will be a common IP mobility protocol for new and existing access technologies Handover optimization for PMIPv6  Service continuity for intra-/inter- access technology handover is critical for real-time applications  FMIPv6 (RFC4068/4068bis) can be a common approach for IP-level fast handover  some modifications are needed to adapt to PMIPv6 Status  Initial draft was proposed in Chicago meeting

3. 3 Design principles Reuse FMIPv6 as much as possible  Minimum amendments for PMIPv6 MN is not involved with fast handover procedure  Some of FMIP signaling (e.g. FBU, FBAck, FNA/UNA) are replaced by lower layer signaling Enhancements of FMIPv6 for context transfer  Context information is transferred by HI/Hack message exchange

4. 4 Changes from -00 PMIPv6-07 newly introduced four handoff types and Handoff Indicator (HI) flag:  Attachment over a new interface (HI=1)  Handoff between interfaces (HI=2)  Handoff between on the same interface (HI=3)  Handoff state unknown (HI=4) MAG sends PBU with the Handoff Indicator flag in Access Technology Type Option

5. 5 Use case of handoff types in PMIPv6 MAG1MAG2 LMA MN IP1 IF1 MAG1  2 IP1 IF1 MN-NAI MAG1  2 IP1 IF1 MN-NAI MN NAI (c) Inter MAG HO with single I/F (HI=3) MAG1MAG2 LMA MN IF1IF2 MN NAI (a) multi-homing with single LMA (HI=1) MAG2 IP2 IF2 MN-NAI MAG2 IP2 IF2 MN-NAI MAG1 IP1 IF1 MN-NAI MAG1 IP1 IF1 MN-NAI IP1IP2 (b) Inter MAG HO with multi-I/F (HI=2) MAG1  2 IP1 IF1->IF2 MN-NAI MAG1  2 IP1 IF1->IF2 MN-NAI MAG1MAG2 LMA MN IF1IF2 MN NAI IP1

6. 6 Handoff Types in PMIPv6 (cont’d) According to Section 6.9.1 of PMIPv6-07: “The Handoff Indicator flag in the Access Technology Type option MUST be set to value 1 (Attachment over a new interface), if the mobile access gateway predictably knows that the mobile node’s attachment to the network using the current interface is due to...” “The Handoff Indicator flag in the Access Technology Type option MUST be set to value 2 (Handoff between interfaces), if the mobile access gateway definitively knows the mobile node’s current attachment is due to…” Need to provide a solution to implement them…

7. 7 New option for context transfer Major and common context information (defined in -00)  NAI  Tunnel-ID  MN-HoA  LMA Technology-dependent context information (defined in - 00)  Vendor-specific option Context Request Option (defined in -00)  Option to request context information Mobile Node Interface Identifier Option  new option

8. 8 Example logic for handoff type determination MAG1MAG2 LMA MN IP1 IF1 MN NAI (c) Inter MAG HO with single I/F (HI=3) MAG1MAG2 LMA MN IF1IF2 MN NAI (a) multi-homing with single LMA (HI=1) IP1IP2 (b) Inter MAG HO with multi-I/F (HI=2) MAG1MAG2 LMA MN IF1IF2 MN NAI IP1 PBU(ATT[HI=1]) IF1 IF1 != IF2 IF1 IF1= = IF1 PBU(ATT[HI=3])PBU(ATT[HI=2]) IF2 IF1 ATT: Access Technology Type Option HI: Handoff Indicator flag ATT: Access Technology Type Option HI: Handoff Indicator flag MAG2 LMA MN IF2 MN NAI (a’) initial attachment (HI=1) IP2 PBU(ATT[HI=1]) IF2

9. 9 Mobile Node Interface Identifier Option

10. 10 Summary Proxy-FMIPv6 is customized for PMIPv6 to provide the fast handover functionality Also provides essential information for the New MAG to proactively determine:  MN-HoA  LMA address  Handoff type  etc…

11. 11 Next steps Keep capturing new features/functionalities of PMIPv6 Propose to adopt this I-D as a MIPSHOP WG document…