Fast handovers for PMIPv6 draftyokotamipshoppfmipv601

1
Fast handovers for PMIPv6ltdraft-yokota-mipshop-pf
mipv6-01gt

• Hidetoshi Yokota KDDI Lab
• Kuntal Chowdhury Starent Networks
• Rajeev Koodli Nokia Siemens Networks
• Basavaraj Patil Nokia Siemens Networks

IETF 70 Vancouver
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
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
Changes from -00

• PMIPv6-07 newly introduced four handoff types and
  Handoff Indicator (HI) flag
• Attachment over a new interface (HI1)
• Handoff between interfaces (HI2)
• Handoff between on the same interface (HI3)
• Handoff state unknown (HI4)
• MAG sends PBU with the Handoff Indicator flag in
  Access Technology Type Option

5
Use case of handoff types in PMIPv6
MAG1?2 IP1 IF1-gtIF2 MN-NAI
MAG1?2 IP1 IF1 MN-NAI
LMA
LMA
MAG1
MAG2
MAG1
MAG2
IP1
IP1
IF1
IF2
IF1
MN
MN
MN NAI
MN NAI
(c) Inter MAG HO with single I/F (HI3)
(b) Inter MAG HO with multi-I/F (HI2)
6
Handoff Types in PMIPv6 (contd)

• 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
  nodes 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
  nodes current attachment is due to
• Need to provide a solution to implement them

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
Example logic for handoff type determination
LMA
LMA
PBU(ATTHI1)
PBU(ATTHI1)
MAG1
MAG2
MAG2
ATT Access Technology Type Option HI Handoff
Indicator flag
IF2
IF2
IF1
IF2
IF2
IP1
IP2
IP2
MN
MN
MN NAI
MN NAI
(a) multi-homing with single LMA (HI1)
(a) initial attachment (HI1)
LMA
LMA
PBU(ATTHI3)
PBU(ATTHI2)
MAG1
MAG2
MAG1
MAG2
IF1 ! IF2
IF1 IF1
IF1
IF1
IF2
IF1
IP1
IP1
IF1
IF2
IF1
MN
MN
MN NAI
MN NAI
(c) Inter MAG HO with single I/F (HI3)
(b) Inter MAG HO with multi-I/F (HI2)
9
Mobile Node Interface Identifier Option
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
Next steps

• Keep capturing new features/functionalities of
  PMIPv6
• Propose to adopt this I-D as a MIPSHOP WG
  document