[PPT] - MIRON MIRON MIPv6 Route Optimization for NEMO MIPv6 Route PowerPoint Presentation

SLIDE 1

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

MIRON MIRON

SLIDE 2

2004-08-11 MIRON [ 2 / 15 ]

Outline

? Network Mobility

?

Network Mobility support

? NEMO Basic Protocol ? MIRON

?

Single Mobile Network

?

Nested Mobile Networks

?

Performance evaluation

? Conclusions and future work ? References

SLIDE 3

2004-08-11 MIRON [ 3 / 15 ]

Network Mobility

Internet NEtwork that MOves

SLIDE 4

2004-08-11 MIRON [ 4 / 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

SLIDE 5

2004-08-11 MIRON [ 5 / 15 ]

NEMO Basic Support Protocol (I)

MR AR Foreign Link MNN

Internet

HA_MR CN

SLIDE 6

2004-08-11 MIRON [ 6 / 15 ]

NEMO Basic Support Protocol (II)

MR1 AR Foreign Link MNN HA_MR3 CN MR2 MR3 MNN HA_MR2 HA_MR1 MNN

SLIDE 7

2004-08-11 MIRON [ 7 / 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

SLIDE 8

2004-08-11 MIRON [ 8 / 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

SLIDE 9

2004-08-11 MIRON [ 9 / 15 ]

MIRON. Single Mobile Network (II)

CN MR HA_MR LFN

S:CN, D:LFN DATA S:HA_MR, D: MR_CoA [S:CN, D:LFN] DATA S:CN, D:LFN DATA S:LFN, D:CN DATA S:MR_CoA, D: HA_MR [S:LFN, D:CN] DATA S:LFN, D:CN DATA S:MR_CoA, D:HA_MR [S:LFN, D:CN] HoTI S:LFN, D:CN HoTI S:MR_CoA, D:CN CoTI S:CN, D:LFN HoT S:HA_MR, D:MR_CoA [S:CN, D:LFN] HoT S:CN, D:MR_CoA CoT S:MR_CoA, D:CN BU (HoA:LFN)

NEMO Basic Solution operation Route Optimization signalling

SLIDE 10

2004-08-11 MIRON [ 10 / 15 ]

MIRON. Single Mobile Network (III)

CN MR HA_MR LFN

S:CN, D:LFN DATA S:HA_MR, D: MR_CoA [S:CN, D:LFN] DATA S:CN, D:LFN DATA S:LFN, D:CN DATA S:MR_CoA, D: HA_MR [S:LFN, D:CN] DATA S:LFN, D:CN DATA

NEMO Basic Solution operation MIRON

peration

S:CN, D:MR_CoA RH (NH:LFN) DATA S:CN, D:LFN DATA S:LFN, D:CN DATA S:MR_CoA, D:CN HoA:LFN DATA

SLIDE 11

2004-08-11 MIRON [ 11 / 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

SLIDE 12

2004-08-11 MIRON [ 12 / 15 ]

MIRON. Nested Mobile Networks

(II)

MR1 AR

1

Prefix_FL::/64 R1 MAR1

3 4 4 5 6 Prefix_FL::MR1/64 7 8 8 9 10 Prefix_FL::MR2/128

MR2

2 NEMO1 NEMO2

Foreign Link

AR Foreign Link MR2 MNN CN HA_MR1 HA_MR2 LFN MR1 MAR1 R1

MR1's CoA: Prefix_FL::MR1/64 MR2's CoA: Prefix_FL::MR2/128

SLIDE 13

2004-08-11 MIRON [ 13 / 15 ]

MIRON. Performance evaluation

? Parameters studied

(L = nesting levels)

? Packet Overhead

? NEMO Basic Support Protocol:

(L+1)*40 (bytes)

? Reverse Routing Header:

40 + L*16+8 (bytes)

? MIRON:

24 (bytes)

? Number of HAs

? NEMO Basic Support Protocol:

L+1

? Reverse Routing Header:

1

? MIRON:

{0,1}

1 2 3 4 5 6 25 50 75 100 125 150 175 200 225 250 275 300

40 80 120 160 200 240 280 48 64 80 96 112 128 144 24 24 24 24 24 24 24 NEMO Basic Support Protocol Reverse Routing Header MIRON

L (Number of nesting levels) Packet Overhead (bytes)

SLIDE 14

2004-08-11 MIRON [ 14 / 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

SLIDE 15

2004-08-11 MIRON [ 15 / 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) ? IPv6 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

SLIDE 16