2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 11

NEMO Route Optimization NEMO Route Optimization Next StepsNext Steps

A Personal Suggestion to Re-CharteringA Personal Suggestion to Re-Chartering

Chan Wah NgChan Wah Ng

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 22

Pieces to the PuzzlePieces 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

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 33

Flattening Nested NEMOFlattening 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

AR

MR1

LFN1 VMN1

MR2

LFN2 VMN2

MR2

LFN2

VMN2 VMN1

VMN1

MR2

LFN2 VMN2

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 44

Extending RO to LFNsExtending RO to LFNs

• Since LFNs are unmodified, most probably:– MR to provide RO

functionalityAR

MR1

LFN1

CN1

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 55

Enabling CRsEnabling 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

AR

MR1

LFN1

CN1

CR1

MN1

Normal NEMO-Normal NEMO-to-CRto-CR

MIPv6-RO: MIPv6-RO: MN-to-CRMN-to-CR

MR as a CRMR as a CR

CR2

HA-HA, HA-HA, CR-CR, etcCR-CR, etc

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 66

ConclusionConclusion

• 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?