PMIPv6 Route Optimization Protocol draft-qin-mipshop-pmipro-00.txt Alice Qin Andy Huang Wenson Wu Behcet Sarikaya

Problem Statement PMIPv6 uses indirect routing via HA –Type 1 CNs MIPv6 corresponding node functionality enabled, not behind PMIPv6 ‘MAG’ –Type 2 CNs MNs behind PMIPv6 ‘MAG’ –Our solution for Type 1 CNs is adopted from enhanced RO draft (draft-ietf-mipshop-cga-cba) AR(MAG2) HA1(LMA1) AR(MAG1) MN CN PMIP Network Scenario 2 CN behind MAG HA2(LMA2) HA1(LMA) AR(MAG1) MN CN PMIP Network Scenario 1 MIP6 enabled CN

E-RO Initial home address test Early BU/BA exchange (care-of test) Complete BU/BA CGA for MN’s HoA based on RFC 3972 CBA adopted with no change

PMIPv6 RO (1/2) Initial home address test -> Proxy Home Test Early BU/BA exchange (care-of test) -> Early Proxy BU/BA Added handover keygen token MAG Home Agent (HA) CN Proxy Home address Test Init (Proxy HoTI) Proxy HoTI Proxy Home address Test (Proxy HoT) Proxy HoT Early Proxy Binding Update (care-of test) Proxy Binding Acknowledge

PMIPv6 RO (2/2) CN MAG1 Early Proxy Binding Update Proxy Binding Acknowledge MAG2 Handoff Complete Proxy Binding Update Proxy Binding Acknowledge Handover context MN (Handover keygen token)

RO with CNs behind MAG(1/2) MAG1 of MN needs to know CoA of CN which is provided by HA of CN Proxy BU exchange between MAGs MAG1 (MN) Home Agent (CN) MAG2 (CN) Proxy Binding Update Proxy Binding Acknowledgement Binding cache Request/Ack (CoA list of CNs)

RO with CN behind MAG(2/2) RO in Handover MAG2 (MN)MAG3 (CN) Proxy Binding Update Proxy Binding Acknowledgement Context Transfer Request MAG1 Context Transfer Data MN (CoA list of CNs)

Next Steps Get more comments and revise accordingly Issue a revised draft by next IETF Listen to WG on the next steps