Transcript PPT Version
2003/3/18 56th IETF NEMO WG Basic Network Mobility Support draft-wakikawa-nemo-basic-00.txt Ryuji Wakikawa ([email protected]) Keisuke Uehara ([email protected]) Koshiro Mitsuya ([email protected]) Thierry Ernst ([email protected]) KEIO University and WIDE project 1 2003/3/18 56th IETF NEMO WG CN 2 Network Configuration CN No Advertisement the3ffe:a::/32->Router1 route of the mobile network prefix the aggregated BGP Network all the time (even Propagating at home link) route of the domain, but not the mobile 3ffe:a::/32 network 3ffe:a:b:c::/64 -> HA MR CoA 3ffe:a:b:/48 MR MR-Address 3ffe:a:b:c::/64 is managed by any routing protocol 3ffe:a:c:/48 Propagating the route of the mobile network Route on HA HA 3ffe:a:b:c::/64 -> tunnel IF Home Link (3ffe:a:b:d::/64) 2003/3/18 56th IETF NEMO WG CN 3 System Configuration Router Advertising Route info. by routing protocol Route NEMO prefix: HA Internet BA BU+Prefix Sub-opt HA Binding Cache MR-A/len: MR-CoA RoutePrefix BU Length NEMO prefix: tunnel interface IP(dst:HA, src:MR-CoA) AR MR CoA MR MR Address(MR-A) MR’s prefix is delegated by HA MR-A 2003/3/18 56th IETF NEMO WG 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 IP(dst:HA, src:MR-CoA) MR-A BU Prefix Length – 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 2003/3/18 56th IETF NEMO WG 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 MR’s movement – Using proxy NDP advertised by HA • How to intercepts all of packets by using proxy NDP of MR’s HoA? • MR’s 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 MR’s HoA and another is for prefix binding of MR’s network. 2003/3/18 56th IETF NEMO WG 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 6 2003/3/18 56th IETF NEMO WG To-Do • Prefix Delegation – Co-operation with proposed prefix delegation protocol (DHCPv6, what else?) • Multiple HAs – Consistency of MR’s 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 7 2003/3/18 • end of slides 56th IETF NEMO WG 8