MIRON MIRON MIPv6 Route Optimization for NEMO MIPv6 Route Optimization for NEMO Carlos J. Bernardos Carlos J. Bernardos <cjbc@it.uc3m.es> <cjbc@it.uc3m.es> Marcelo Bagnulo Marcelo Bagnulo <marcelo@it.uc3m.es> <marcelo@it.uc3m.es> María Calderón María Calderón <maria@it.uc3m.es> <maria@it.uc3m.es> University Carlos III of Madrid - University Carlos III of Madrid - Spain Spain 2004- 2004 -08 08- -11 11
Outline ? Network Mobility Network Mobility support ? ? NEMO Basic Protocol ? MIRON Single Mobile Network ? Nested Mobile Networks ? Performance evaluation ? ? Conclusions and future work ? References 2004-08-11 MIRON [ 2 / 15 ]
Network Mobility Internet NEtwork that MOves 2004-08-11 MIRON [ 3 / 15 ]
Network Mobility support ? Demand for Internet access in mobile platforms (e.g. trains, buses) is increasing ? There are some proposals for supporting Network Mobility ? One of them is done within the IETF NEMO WG ? NEMO Basic Support Protocol ? Mobility managed at IP level ? Based on Mobile IPv6 protocol (i.e. terminal mobility) ? Bidirectional tunnel between MR and HA 2004-08-11 MIRON [ 4 / 15 ]
NEMO Basic Support Protocol (I) Internet CN AR HA_MR Foreign Link MR MNN 2004-08-11 MIRON [ 5 / 15 ]
NEMO Basic Support Protocol (II) HA_MR1 CN AR Foreign Link MR1 HA_MR2 HA_MR3 MR3 MNN MR2 MNN MNN 2004-08-11 MIRON [ 6 / 15 ]
Route Optimization issue ? NEMO Basic Support Protocol has one of the problems of Mobile IPv6: ? Triangle Routing ? Solved in Mobile IPv6 with the Route Optimization support ? MIRON adapts MIPv6 RO to optimize CN-LFN flows ? Besides, NEMOs can be NESTED ? Pinball Routing ? Some solutions proposed so far ? No one seems to solve the problem properly ? MIRON proposes an address delegation mechanism with built-in routing that avoids the tunnel overhead 2004-08-11 MIRON [ 7 / 15 ]
MIRON. Single Mobile Network (I) ? Goals and requirements ? To provide Transparent Route Optimization between a LFN and a CN ? Avoiding triangle routing ? Preserving CN and LFN operation unchanged ? Basically consists in performing MIPv6 Route Optimization procedure between the MR (on behalf of the LFN) and the CN ? The solution profits from the installed base of CNs that support MIPv6 RO 2004-08-11 MIRON [ 8 / 15 ]
MIRON. Single Mobile Network (II) MR CN HA_MR LFN S:CN, D:LFN S:HA_MR, D: MR_CoA [S:CN, D:LFN] S:CN, D:LFN NEMO Basic DATA DATA DATA Solution operation S:LFN, D:CN S:MR_CoA, D: HA_MR [S:LFN, D:CN] S:LFN, D:CN DATA DATA DATA S:LFN, D:CN S:MR_CoA, D:HA_MR [S:LFN, D:CN] HoTI HoTI S:MR_CoA, D:CN Route CoTI Optimization S:CN, D:LFN S:HA_MR, D:MR_CoA [S:CN, D:LFN] signalling HoT HoT S:CN, D:MR_CoA CoT S:MR_CoA, D:CN BU (HoA:LFN) 2004-08-11 MIRON [ 9 / 15 ]
MIRON. Single Mobile Network (III) MR CN HA_MR LFN S:CN, D:LFN S:HA_MR, D: MR_CoA [S:CN, D:LFN] S:CN, D:LFN NEMO Basic DATA DATA DATA Solution operation S:LFN, D:CN S:MR_CoA, D: HA_MR [S:LFN, D:CN] S:LFN, D:CN DATA DATA DATA MIRON operation S:CN, D:MR_CoA RH (NH:LFN) S:CN, D:LFN DATA DATA S:MR_CoA, D:CN HoA:LFN S:LFN, D:CN DATA DATA 2004-08-11 MIRON [ 10 / 15 ]
MIRON. Nested Mobile Networks (I) ? Goals and requirements ? To provide Transparent Route Optimization for Nested Mobile Networks ? Avoiding pinball routing ? Preserving CNs and MNNs operation unchanged ? Basically consists in delegating topologically correct IPv6 addresses to every MR within a nested NEMO ? Routing of packets within the NEMO is also provided 2004-08-11 MIRON [ 11 / 15 ]
MIRON. Nested Mobile Networks (II) AR HA_MR2 HA_MR1 Foreign Link Prefix_FL::/64 5 6 1 7 Prefix_FL::MR1/64 MR2's CoA: Prefix_FL::MR2/128 MR1's CoA: Prefix_FL::MR1/64 MR1 AR CN 4 8 Foreign Link R1 MR1 4 8 R1 MAR1 9 NEMO1 MR2 LFN 3 10 2 MAR1 Prefix_FL::MR2/128 MNN MR2 NEMO2 2004-08-11 MIRON [ 12 / 15 ]
MIRON. Performance evaluation ? Parameters studied (L = nesting levels) NEMO Basic Support Protocol Reverse Routing Header MIRON 300 ? Packet Overhead 280 275 Packet Overhead (bytes) ? NEMO Basic Support Protocol: (L+1)*40 (bytes) 250 240 225 ? Reverse Routing Header: 200 40 + L*16+8 (bytes) 200 175 160 ? MIRON: 24 (bytes) 144 150 128 120 125 ? Number of HAs 112 96 100 80 80 75 ? NEMO Basic Support Protocol: L+1 64 48 50 40 24 24 24 24 24 24 24 ? Reverse Routing Header: 1 25 0 ? MIRON: {0,1} 0 1 2 3 4 5 6 L (Number of nesting levels) 2004-08-11 MIRON [ 13 / 15 ]
MIRON. Conclusions and future work ? MIRON provides Route Optimization for NEMO ? LFN-CN RO ? Route Optimization between LFN and CN (MR performs MIPv6 RO on behalf of the LFN) ? Avoid triangle routing ? Requires flow identification and tracking ? Nesting RO ? Provides valid and reachable IPv6 addresses to every MR within the nested, to be used as CoAs ? Avoid pinball routing ? Can be used also separately to avoid tunnels introduced by nesting (or together with the previous) ? Use of prefix delegation should also be studied 2004-08-11 MIRON [ 14 / 15 ]
References Nemo Basic Support Protocol . Vijay Devarapalli et al. draft-ietf-nemo- ? basic-support-01 (work-in-progress) Network Mobility Support Terminology . T. Ernst et al. draft-ietf- ? nemo-terminology-01 (work-in-progress) Network Mobility Support Goals and Requirements . T. Ernst. draft- ? ietf-nemo-requirements-02 (work-in-progress) Mobility Support in IPv6 . D. Johnson et al. draft-ietf-mobileip-ipv6-24 ? (work-in-progress) Taxonomy of Route Optimization models in the Nemo Context . P. ? Thubert et al. draft-thubert-nemo-ro-taxonomy-02 (work-in-progress) I Pv6 Reverse Routing Header and its application to Mobile Networks . ? P. Thubert et al. draft-thubert-nemo-reverse-routing-header-04 (work- in-progress) EU FP6 DAIDALOS Project. http://www.ist-daidalos.org ? 2004-08-11 MIRON [ 15 / 15 ]
MIRON MIRON MIPv6 Route Optimization for NEMO MIPv6 Route Optimization for NEMO Carlos J. Bernardos Carlos J. Bernardos <cjbc@it.uc3m.es> <cjbc@it.uc3m.es> Marcelo Bagnulo Marcelo Bagnulo <marcelo@it.uc3m.es> <marcelo@it.uc3m.es> María Calderón María Calderón <maria@it.uc3m.es> <maria@it.uc3m.es> University Carlos III of Madrid - University Carlos III of Madrid - Spain Spain 2004- 2004 -08 08- -11 11
Recommend
More recommend