1 / 6

NEMO Route Optimization Next Steps A Personal Suggestion to Re-Chartering

NEMO Route Optimization Next Steps A Personal Suggestion to Re-Chartering. Chan Wah Ng. Pieces to the Puzzle. Flattening Nested NEMO Allows modified MNNs to appear as though they are not in a NEMO but directly attached to AR Extending Route Optimization to LFNs

chiko
Download Presentation

NEMO Route Optimization Next Steps A Personal Suggestion to Re-Chartering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NEMO Route Optimization Next StepsA Personal Suggestion to Re-Chartering Chan Wah Ng 64th IETF - NEMO WG

  2. Pieces to the Puzzle • Flattening Nested NEMO • Allows modified MNNs to appear as though they are not in a NEMO but directly attached to AR • Extending Route Optimization to LFNs • Allows unmodified LFNs to enjoy RO • Enabling Correspondent Routers • Allows unmodified CNs to enjoy RO 64th IETF - NEMO WG

  3. AR MR1 MR2 VMN1 VMN2 MR2 VMN1 LFN1 LFN2 MR2 LFN2 VMN2 VMN1 LFN2 VMN2 Flattening Nested NEMO • Let MNNs appear to be attached to AR • Solves the problem of • Security Policy Prohibiting VMN’s Traffic • Nested Home Agents • Allows MIPv6 RO to be unhindered by NEMO-Basic Tunnel 64th IETF - NEMO WG

  4. Extending RO to LFNs • Since LFNs are unmodified, most probably: • MR to provide RO functionality CN1 AR MR1 LFN1 64th IETF - NEMO WG

  5. MIPv6-RO: MN-to-CR CR2 MR as a CR Normal NEMO-to-CR HA-HA, CR-CR, etc Enabling CRs • CR allows CN to have no mobility support • CR can itself be an MR • Scope may be bigger then NEMO • CR for MIPv6 RO • May include other variations: • HA-HA, anchor routers, etc CN1 MN1 CR1 AR MR1 LFN1 64th IETF - NEMO WG

  6. Conclusion • There are different pieces to the NEMO RO picture • it will be best to break them up • divide and conquer • Some may be ready for an engineering solution • Recharter NEMO to work on them • Some may not • IRTF? 64th IETF - NEMO WG

More Related