Nemo RO taxonomy

1
Nemo RO taxonomy
59th IETF, NEMO WG

• P. Thubert, M. Molteni (Cisco)
• C. Ng (Panasonic)
• H. Ohnishi (NTT)
• E. Paik (Seoul Nat. Univ.)

2
Outline

• Types of route optimization
• Nested Nemo RO and Local Mobility Managt
• RO Multihoming
• Shades of transparency
• AR selection

3
Types of route optimizations
HA

• MR-to-CN
• MIPv6 Route Optimization over NEMO
• Nested Mobile Network

MR
LFN
CN
MRs HA
MNs HA
MR
MN
CN
MR2s HA
MR1s HA
MR2
CN
MR1
LFN
4
RO and LMM

• Model Nested Nemo attached to an AR
• AR (or root-MR) owns all the CareOfs of the MNs
  (from the infrastructure standpoint)
• AR (or root-MR) handles the local mobility to the
  MNs (using ad-hoc or MIP)
• HMIP and DHCP-PD based approaches
• Need more on MANET / Micromobility LMM

MR2s HA
MR1s HA
MR2
CN
MR1
LFN
5
RO and Multihoming

• Model Multiple HAs (1, N, ) or Jet Set
• maybe multiple HoAs as well?
• Problem select best HA to shorten MR/HA/CR
• Other problem?

HA
MR
LFN
CN
HA
6
AR selection

• Model Nested Nemo attached to an AR, where
• MRs act as MAR for others MRs to attach to
• If loops are avoided, MRs form a tree
• Problem How to select MAR?
• Avoiding loops
• Optimizing metrics such as hops and bandwidth
• Need a Tree Discovery mechanism
• Quick
• Minimal overhead on top of ND

How to select?
MR
AR
MR
7
Shades of Transparency

• cwng's interpretation of Mobility Transparency
  in RO
• achieving mobility transparency may not be
  practical.
• For instance, to achieve nested tunnel
  optimizations, the mobility of the top-level MR
  is often exposed to other entities, such as the
  HA of a nested MR. In the case of MR performing
  BU for MNNs, it might be necessary to pass
  mobility information of the MR to CN (and even
  MNN) in order not to break the end-to-end
  principle. For the scenario of optimization using
  infrastructure, the mobility information might be
  necessarily exposed to correspondent routers or
  MAP.
• Thus, one should bear in mind when designing RO
  solution that a sacrifice might be necessary when
  weighing conflicting factors such as mobility
  transparency, optimization level, and end-to-end
  integrity.
• Hosik's interpretation of Mobility Transparency
  in RO
• In the case of extended support of NEMO such as
  nested NEMO, mobility transparency is desirable
  but that is not mandatory for the efficiency of
  the route optimization. For example, the notebook
  and PDA inside a vehicle can access to the
  Internet through the mobile router of the
  vehicle. In that case, if the movement of the
  vehicle affects to the notebook or the PDA, they
  can perform individual binding update operation
  to the correspondent node or its home agent but
  that can cause location privacy problem.
• Onishi's interpretation of Mobility Transparency
  in RO
• In RO solutions, MR can optimize the route
  between its own HA and MR. It is desirable that
  communication can not be interrupted by this
  route optimization. ????

8
Mailing List issues

• Chapter 6
• needs more elaboration
• must be simpler to grasp
• Should this become a WG item?