MANEMO Applicability of existing mechanism Ryuji Wakikawa (Keio U)

MANEMO Problems AR AR MR1 MR1 MR2 MR2 MR3 MR4 MR3 MR4 HA3 HA3 HA2 HA2 INTERNET INTERNET CN AR AR MR1 MR1 MR2 MR2 MR3 MR4 MR3 MR4 2

Issue 1: Sub-optimal path Communication in Nested NEMO

Optimal Path for internal communication HA3 HA3 HA2 HA2 HA1 HA4 HA1 HA4 INTERNET INTERNET CN AR AR MR1 MR1 MR2 MR2 MR3 MR4 MR3 MR4 4

MANET/AUTOCONF Applicability HA3 HA2 Required functions Prefix Route Exchange for neighboring MRs (MNP) Address assignment for local communication in nested NEMO NEMO MR exchanges prefix route of own MNP routes the packets to the destination according to the prefix route if available bypass the HA (no tunnel) HA1 HA4 INTERNET CN AR/IGW ANP::/64 LL:LMR1 ANP::MR1 LL:MR2 ANP::MR2 MR1 MR2 LL::MR4 ANP::MR4 LL:MR3 ANP::MR3 MR3 MR4 5

Considerations Routing Scope? Who should participate in the MANET? 1-hop? (NDP) 2-hop? (NHDP) n-hop? (MANET) Who should participate in the MANET? mobile router (MR) fixed router (FR) mobile network node (MNN) mobile host (MH) Which address is used? link local? unique site-local? global address owned by each MR, HoA? (unique, topology incorrect) obtained from upper MR? (topology incorrect) obtained from AR? (topology correct) Is Tunnel required? NO HA independent

MANET/AUTOCONF applicability Solutions What NEMO MR can get AUTOCONF local address for internal communication in nested NEMO global topologically correct address to reach the Internet over nested NEMO NHDP neighbor's information of 2-hop mobile routers MR's HoA and MNP MR's address (local address and global address) Link information OLSR -n-hop mobile routers -route to the Internet (IGW) DYMO - discovering n-hop mobile routers - discovering IGW

NHDP vs NDP NDP NHDP offers similar functionalities of NDP Mobile IPv6 based protocols rely on NDP for movement detection (DNA) network reachable detection (Router reachability) address configuration (including DAD) Neighbor Unreachability Detection returning home operation 1-hop neighboring information NHDP offers similar functionalities of NDP 2-hop neighbors information link information How can mobile router interact with NDP and NHDP simultaneously?! conflicting reachability information conflicting routing table information

Issue 2: Sub-optimal Path from Nested NEMO to the Internet

Optimal Path from nested NEMO to the Internet HA3 HA3 HA2 HA2 HA1 HA4 HA1 HA4 INTERNET INTERNET CN CN AR AR MR1 MR1 MR2 MR2 MR3 MR4 MR3 MR4 10

MANET/AUTOCONF Applicability Required functions Global topology correct address assignment from AR Route setup to AR (Internet) Sending BU and Creating tunnel NEMO MR sends BU for the global address to its HA Tunnel setup routes the packets of other MRs AR/IGW MUST NOT leak the prefix routes to the Internet HA3 HA2 HA1 HA4 INTERNET CN AR/IGW ANP::/64 ANP::MR1 ANP::MR2 MR1 MR2 ANP::MR4 ANP::MR3 MR3 MR4 11

Considerations Routing Scope? Who should participate in the manet? 1-hop? (NDP) 2-hop? (NHDP) n-hop? (MANET) Who should participate in the manet? mobile router (MR) fixed router (FR) mobile network node (MNN) mobile host (MH) Which address is used? link local? unique site-local? global address owned by each MR, HoA? (topology incorrect) obtained from upper MR? (topology incorrect) obtained from AR? (topology correct) Is Tunnel required? YES HA dependent

MANET/AUTOCONF applicability Solutions What NEMO MR can get AUTOCONF local address for internal communication in nested NEMO -global topologically correct address to reach the Internet over nested NEMO NHDP neighbor's information of 2-hop mobile routers MR's HoA and MNP MR's address (local address and global address) Link information OLSR -n-hop mobile routers -route to the Internet (IGW) DYMO - discovering n-hop mobile routers - discovering IGW

AR/IGW involvement MANEMO Scope?? The problem of Nested NEMO HA3 HA2 AR/IGW nested NEMO aware HA1 HA4 AR/IGW NOT Nested NEMO aware INTERNET Prefix Delegation to MR1 CN MR1 takes roles of IGW/AR a bit optimization AR/IGW ANP::/64 ANP::MR1 MR1::MR2 MR1 MANEMO Scope?? MR2 MR1::MR4 MR1::MR3 MR3 MR4

Possible Issue: divide a Nested NEMO An IPv6 router in a mobile network, named Fixed Router, may divide a nested NEMO, unless it is MANET aware. FR is MANET aware, full optimization FR is NOT MANET aware, it is still better than the basic nested NEMO AR ANP::/48 AR Nested NEMO-1 Nested NEMO-2 ANP::/64 ANP::MR1 ANP:1::/64 ANP:1::MR1 MR1 MR1 MNP1::/64 MNP1::/64 FR FR MNP1:1::/64 MNP1:1::/64 MNP1:1::MR2 ANP:2::/64?? ANP:2::MR2?? MR2 MR2 MNP2::/64 MNP2::/64 15

Impact of MR movement ANP1::/48 ANP2::/48 ANP1:1::MR1 MNP1::/64 AR1 ANP1::/48 AR2 ANP2::/48 ANP1:1::MR1 MR1 MNP1::/64 ANP1:2::MR2 MR2 MNP2::/64 ANP1:3::MR3 ANP1:4::MR4 MR3 MR4 MNP3::/64 MNP4::/64

Impact of MR movement ANP2::/48 ANP1::/48 ANP2:1::MR1 AR1 AR2 ANP2::/48 ANP1::/48 ANP2:1::MR1 MR1 A MR movement causes address changes on all the other MRs. -> MR MUST update CoA -> MR MUST send BU -> MR MAY re-calculate routes This is orthogonal to the NEMO basic functionality, movement transparency. MNP1::/64 ANP2:2::MR2 MR2 MNP2::/64 ANP2:3::MR3 ANP2:4::MR4 MR3 MR4 MNP3::/64 MNP4::/64

The NEMO Addressing: Movement Transparency ANP1::/48 ANP2::/48 ANP1::MR1 ANP2::MR1 MR1 MR1 MNP1::/64 MNP1::/64 MNP1::MR2 MNP1::MR2 MR2 MR2 MNP2::/64 MNP2::/64 MR3 MR4 MR3 MR4 MNP3::/64 MNP4::/64 MNP3::/64 MNP4::/64

Multihoming Capability A MR may obtain multiple addresses in Nested NEMO, 1) NEMO topologically incorrect address & 2) AUTOCONF topologically correct address. INTERNET INTERNET AUTOCONF NEMO AR ANP::/48 AR ANP::/64 ANP::MR1 ANP:1::/64 ANP:1::MR1 MR1 MR1 Prefix Delegation MNP1::/64 MNP1::/64 MNP1::MR2 ANP:2::/64 Which is CoA? ANP:2::MR2 (from AR) MNP1::MR2 (from MR1) MR's HoA (from HA) MR2 MR2 MNP2::/64 MNP2::/64

Monami6 Applicability?? NEMO&AUTOCONF MR2's binding AR It can register both addresses as CoA with MCoA (Monami6), although it may not help anything for the nested NEMO. HA2 HA1 MR2's binding ANP:2::MR2 (BID1) MNP1::MR2 (BID2) INTERNET ANP::/48 AR Tunnel Selection? HoA/CoA Selection? Path Selection? (I.e.tunnel or MANET direct) ANP:1::/64 ANP:1::MR1 MR1 MNP1::/64 Prefix Delegation ANP:2::/64 ANP:2::MR2 MNP1::MR2 MR2 NEMO&AUTOCONF MNP2::/64 20

Some Overall Observations Integration of NEMO, AUTOCONF, OLSR/DYMO, NHDP, NDP…. MR obtains IPv6 address through NDP or AUTOCONF MR updates routes by OLSR/DYMO, NHDP, NEMO(tunnel), NDP MR checks reachability by NDP and NHDP Interoperability & backward compatibility MR is not always participating in MANET, but attaches to the legacy v6 link