PMIP 6 extensions for interaccess handovers and flow

PMIP 6 extensions for inter-access handovers and flow mobility Basavaraj Patil and Rajeev Koodli IETF 76

Base PMIP 6 LMA PMIP 6 domain IP network MAG-1 Access-1 MAG-2 Access-1

Beyond Base PMIP 6 LMA PMIP 6 domain IP network MAG-1 Access-1 MAG-2 Access-2

Beyond RFC 5213 1. How does MAG-2 perform PMIP 6 Binding Update (enabling the MN to maintain the same HNP)? - Inter-access handover 2. Internally, how does the MN move HNP from Access-1 to Access-2? 3. If the MN is attached to both accesses simultaneously, how can the network (i. e. , LMA) move a subset of flows from Access-1 to Access-2? – Multihoming, flow mobility

Status and Steps • There is MAG – LMA interaction and MAG – MN interaction • MAG – LMA interaction is network only (clearly) • No agreement on MN extensions for MAG – MN interaction – Extensions to RS/RA to indicate interface change, provide new prefix? – Link-layer specific mechanisms? – Presentation to follow • Need to decide on WG adoption of topics

Additional slides Jul 28, 09 IETF 75 6

Base PMIP 6, Beyond Base PMIP 6 • LMA manages MN mobility, but the MN is unaware of LMA managing it – There is no signaling between the MN and the LMA • MAG is the MN’s default router – There is (IP) signaling between the MN and the MAG • The mobility paradigm is network-based – There is only LMA, MAG managing mobility, session (Qo. S, policy, accounting etc. ) – No additional entities are present Jul 28, 09 IETF 75 7

Inter-access handover • MAG-2 needs parameters to perform the PBU operation (to ensure that the same HNP is assigned) • LMA can assign the same HNP based on MN Identifier (typically the MN-NAI) • Choices: – AAA server can provide LMA address, MN Identifier (MN-NAI) when access authentication is in place – MAG-1 can provide via context transfer – MN provides an indication of interface change in RS – Others? Jul 28, 09 IETF 75 8

Use of same HNP • The MN needs to have the capability to hide interface change in order to preserve the same HNP and addresses in use • Choices: – Virtual interface? – Others? Jul 28, 09 IETF 75 9

Multihoming (Flow Mobility) • When the MN is simultaneously attached, how to share the same HNP across interfaces? – LMA needs to identify the flows that need to be mapped to the corresponding interfaces – The control logic resides at and internal to the LMA – MAG signaling extensions • Indication to the MN - Choices: – L 2: MAG can inform change in traffic template via access-specific signaling; e. g. , NAS messaging in LTE – RA with new option – Others? Jul 28, 09 IETF 75 10