Basic Network Mobility Support draft-wakikawa-nemo-basic-00.txt

1
Basic Network Mobility Supportdraft-wakikawa-nemo
-basic-00.txt

• Ryuji Wakikawa (ryuji_at_sfc.wide.ad.jp)
• Keisuke Uehara (kei_at_wide.ad.jp)
• Koshiro Mitsuya (mitsuya_at_sfc.wide.ad.jp)
• Thierry Ernst (ernst_at_sfc.wide.ad.jp)
• KEIO University and WIDE project

2

CN
CN
Network Configuration
BGP Network
No Advertisement the route of the mobile network
prefix all the time (even at home link)
Propagating the aggregated route of the domain,
but not the mobile network
MR CoA
3ffea/32
3ffeab/48
3ffeac/48
Propagating the route of the mobile network
MR
HA
Route on HA 3ffeabc/64 -gt tunnel IF
MR-Address
3ffeabc/64 is managed by any routing
protocol
Home Link (3ffeabd/64)
3
System Configuration
CN
Router
HA
Route NEMO prefix HA
Internet
Route NEMO prefix tunnel interface
AR
MR CoA
MR
MR Address(MR-A)
MRs prefix is delegated by HA
4
Changes of Mobile IPv6

• MR address (MR-A) instead of HoA
• MR-A is generated by mobile network prefix and MR
  identifier(ex. EUI64)
• Binding Update is like
• New prefix suboption(4byte) to store the prefix
  length
• Search Binding Cache
• step1. search BC w/ 128 bit length (Normal
  MIPv6)
• step2. search BC w/ the registered prefix length
• No returning home network, but returning home
  link
• Deregistration of Binding is still used to delete
  the binding when MR shut down the operation
• Security is provided the same way of ha-ipsec
  draft
• Meet most of the requirements of NEMO basic scheme

5
Advantages

• Security
• Mobile network prefix is authorized and
  authenticated by IPsec w/ MR-A
• HoA of MR is authenticated and authorized by
  IPsec, but not mobile network prefix stored in BU
• Advertisement of mobile network prefix
• MR never advertise the prefix from the egress
  interface by routing protocol, but HA do it
• MR advertises the prefix from the egress
  interface when it returns home-network.
• How to recover or prevent the situation when MR
  mistakes advertising the prefix?! (i.e. Error
  operation)
• Interception of packets on HA
• Using proxy routing information advertised by HA
• This proxy route is never changed during MRs
  movement
• Using proxy NDP advertised by HA
• How to intercepts all of packets by using proxy
  NDP of MRs HoA?
• MRs Host mobility
• MR is identified by MR-A which is configured w/
  the network prefix
• Single prefix binding cache provides host
  mobility when BC is searched w/ 128 bit len, and
  network mobility when BC is searched w/
  registered prefix len
• Each MR has HoA of MIP6, and HoA is different
  from the network prefix.
• MR registers two binding. One is for binding of
  MRs HoA and another is for prefix binding of
  MRs network.

6
Implementation

• Support FreeBSD-RELEASE
• Implemented on original Mobile IPv6 code (which
  is based on draft20)
• Nested Mobility is also supported
• VMN moves to mobile network
• The situation when MR visits another MR is not
  tested yet, but should work

7
To-Do

• Prefix Delegation
• Co-operation with proposed prefix delegation
  protocol (DHCPv6, what else?)
• Multiple HAs
• Consistency of MRs Binding among multiple HAs
• Multi-Homed MR (Mobile Network)
• Multihomed MR w/ multiple HA can be supported
  (not appear in the draft)
• Multihomed MR w/ single HA is not discussed yet
• Multiple MRs is not discussed yet

8

• end of slides