1. Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt Optimized Local Routing November 20091 IETF76 - Hiroshima Optimized Local Routing for PMIPv6 (draft-oulai-netext-opt-local-routing-01.txt) Desire Oulaï Suresh Krishnan Ericsson

2. Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt Optimized Local Routing November 20092 Local Routing Initiation (draft-oulai-netext-opt-local-routing-01.txt) –LMA detects local routing (LR) is possible between MAG1 and MAG2 –LMA sends Local Routing Initiation (LRI) messages to MAG1 and MAG2. LRI may contain IP addresses, tunneling mode, Security keys, GRE keys…) –MAG1 and MAG2 directly start LR. MN1 MAG1MAG2 MN2 LMA LR tunnel LRI LRA LRI LRA

3. Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt Optimized Local Routing November 20093 Conclusion Quick LR initiation mechanism –we need messages exchanges between the MAGs only if the parameters provided by the LMA are incorrect. Optimized handover is possible Inter MAG tunnel may be preconfigured IPv4 is supported in the solution Solution can be extended to support distinct LMAs

4. Slide title In CAPITALS 50 pt Slide subtitle 32 pt Backup

5. Top right corner for field-mark, customer or partner logotypes. See Best practice for example. Slide title 40 pt Slide subtitle 24 pt Text 24 pt Bullets level 2-5 20 pt Optimized Local Routing November 20095 Fast Handover (draft-oulai-netext-opt-local-routing-01.txt) Handover in local routing scenario implies worse performance (delay, packet loss) than basic PMIP handover. The LMA is not able to switch automatically the traffic after receiving the PBU as the traffic bypasses the LMA. An optimized handover mechanism is needed.