Solution Overview (LR procedure)

1. Solution Overview (LR procedure) The whole sequence for localized routing Local routing capability detection Local routing Initiation LR scope or LR type negotiation Enforce Local routing Local routing service authorization Local routing path setup Setup trust relationship Reach-ability check Establish binding and tunnel Local routing path update during handover

2. Solution Overview (MAG Initiated LR ) LMA 3.PBU’/LROREQ Home Domain 1.Attach to MAG1 MAG1 5.Service authorization (Optional) MN Home AAA server 4.PBA’/LRORSP (Enforce LR) Visited Domain 6.PBU/PBA (Setup LR) 2.Uplink Datagram trigger AAA Proxy 7.PUB/PBA (Setup LR) Intra-LMA Localized Routing Intra-MAG localized Routing MAG2 CN 1.Attach to MAG2 • Localized routing(LR) Initiation • LR is Initiated by MAG • LR is enforced on MAG through LR parameters negotiating • LR parameters negotiation is done via Enhanced PBU/PBA or new LR messages. • LR parameters contain LR Scope and LR/disable/enable • Localized routing Authorization using AAA approach (Optional) • Authorize the use of localized routing for both MAGs • Discover the address of the LMA to which the CN registers • Localized routing Setup • Setup BCE, routing table, tunnel interface table via normal PBU/PBA • Similar to setup RO path between MN and CN via BU/BA described in MIP6 RO (RFC3755), Reachability can be checked; Trust relationship can be setup.

3. Solution Overview (LMA Initiated LR ) 2.Uplink Datagram trigger LMA 3.LROREQ Home Domain 1.Attach to MAG1 MAG1 MN Home AAA server 4.LRORSP (Enforce LR) Visited Domain 6.PBU/PBA (Setup LR) AAA Proxy 5.Service authorization (Optional) 7.PUB/PBA (Setup LR) MAG2 CN Intra-LMA Localized Routing Intra-MAG localized Routing 1.Attach to MAG2 • Localized routing(LR) Initiation • LR is Initiated by LMA • Enforce LR through LMA Initiated LR message • Localized routing Authorization using AAA approach (Optional) • The operations are same as the way in the MAG initiated LR • Localized routing Setup • The operations are same as the way in the MAG initiated LR • IPSec SA between MAGs may setup before PBU/PBA exchange

4. Solution Overview (handover aspect) LMA pMAG1 MN Visited Domain 1.HI(Predictive)) 4.PBU/PBA (Setup LR) CN MAG2 nMAG1 2.HAck 5.PBU/PBA (Setup LR) 3.Attach to MAG1 a. pMAG1 initiated Predictive Handover MN pMAG1 LMA MN 2.HI(Reactive) Visited Domain 4.PBU/PBA (Setup LR) CN MAG2 5.PBU/PBA (Setup LR) 3.HAck b. nMAG1 initiated Reactive Handover 1.Attach to the nMAG1 nMAG1 MN • Local routing path update during handover • Handover case can be divided into predictive mode handover and Reactive mode handover. • Context request option defined in [I-D.ietf-mipshop-pfmip6] can be used to carry context information. • Context information contains CN’s MAG list with which MN is communicating. • HI/Hack trigger bidirectional PBU/PBA to update the binding and tunnel.

5. Solution Overview (Inter-LMA LR aspect) LMA1(MN) 3.LROREQ/LRORSP (Enforce LR[LMA2]) Home Domain 1.Attach to MAG1 MAG1 MN 4.Service authorization (LMA2) Home AAA server 4.LRORSP (Enforce LR) 5.LROREQ/LRORSP (Location Query[MAG2]) 2.Uplink Datagram trigger AAA Proxy Visited Domain 6.Service authorization (LMA2) 7.PUB/PBA (Setup LR) LMA2(CN) MAG2 CN 1.Attach to MAG1 • Localized routing Initiation • Localized Routing Authorization and entities discovery • Authorize use of localized routing between MAG1 and MAG2 and fetch LMA2 address from AAA server in terms of MN2(Policy store) • Authorize use of localize routing and Fetch MAG2 address from LMA2 • Local routing Setup • The Operations are same as the way in the intra-LMA LR.

6. Mapping to PS/Scope

7. Appendix: LR Type Classification LR Type 1: Intra-MAG localized routing LR Type 2: Intra-LMA localized routing LR Type 3:Inter-LMA localized routing