Dear Tian,
First of all my apologies for the late reply to your
email. As a matter of fact I was a little occupied
because we had a visitor. By the way, this visitor was
Hesham Soliman, the individual who has written many
IETF drafts related to Mobile IPv6.
I have done several of my tests regarding to your
problem. Here is my analysis:
1) firstly for some basic fact. Handover process
completes when the MN completes the binding update and
acknowledgment process with the HA.
2) Binding Update with the CN is not part of the
handover process.
3) Return Routability Procedure is performed, the
moment the MN detects that someone (i.e. CN) is trying
to communicate with it. So the delay that yo observed
has nothing to do with the Return Routability
Procedure. The MN will not perform the Return
Routability Procedure unless the MN detects that some
one is communicating with it. In your case, the
detection is made when the VERY FIRST ICMPv6 Echo
request (i.e. Ping6) message is received. If you
notice the delay is not in starting the Return
Routability Procedure. The delay is observed when the
first ping6 message is received.
4) To reduce the delay, you could send the ping6
messages at higher frequency.
Hope it helps.
Shariq
--- tian tian <[EMAIL PROTECTED]> wrote:
---------------------------------
HI Shariq!
Thanks a lot for ur suggestion!
Yes, you are right, the the router adv interval of the
test information I gave yesterday was set as min.
0.03s to max. 0.07s.
I also did some tests with different router adv
interval of radvd, although there were less Router
adv. between BA and HoT, still got the same time delay
problem.
================= router adv interval ==============
====
min. max.
delay (average)
--------------------------------------------------------------------------------------
Test1. 1 3
0.58s Test2. 0.5
1.5 0.60s
Test3. 0.03 0.07
0.55s
===================================================
I tested with three different router adv set as shown
in the above table, each test I did ten times. The
delay between BA and HoT(the start of RRP) took place
all the same, with the average value about 0.5s-0.6s.
I show the package information below:
Test1.the router adv interval with min 1s, max 3s, the
delay is about 0.4s as blue coloured componet.
=========================================================================================
Seq. time Source Address Dist.
Address
......
178 61.313759 fe80::202:2dff:fe07:9948
ff02::1:ff5f:163e ICMPv6 Neighbor solicitation
179 61.313859 2001:106:1100:0:204:23ff:fe5f:163e
fe80::202:2dff:fe07:9948 ICMPv6 Neighbor
advertisement
180 61.315936 2001:106:1200::1
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
Acknowledgement
------------------------------------------------------------------------------------
181 61.783381 fe80::204:23ff:fe5f:163e
fe80::202:2dff:fe20:cf70 ICMPv6 Neighbor
solicitation
182 61.787571 2001:106:1200::2
2001:106:2600::2 ICMPv6 Echo request
183 61.791291 2001:106:2600::2
2001:106:1200::2 ICMPv6 Echo reply
---------------------------------------------------------------------------------------
184 61.793744 2001:106:1200::2
2001:106:2600::2 MIPv6 Home Test Init
185 61.794847 2001:106:1100:0:204:23ff:fe5f:163e
2001:106:2600::2 MIPv6 Care-of Test Init
186 61.796708 2001:106:2600::2
2001:106:1200::2 MIPv6 Home Test
187 61.797996 2001:106:2600::2
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Care-of
Test
188 61.801679 2001:106:1100:0:204:23ff:fe5f:163e
2001:106:2600::2 MIPv6 Binding Update
189 61.805637 2001:106:2600::2
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
Acknowledgement
==================================================================================
Test2.the router adv interval with min 0.5s, max 1.5s,
the worst delay is about 0.55s as blue coloured
componet.
======================================================================================
Seq. time Source Address Dist.
Address
......
36 10.950150 fe80::202:2dff:fe07:9948 ff02::1
ICMPv6 Router advertisement
37 11.273683 fe80::202:2dff:fe07:9948
ff02::1:ff5f:163e ICMPv6 Neighbor solicitation
38 11.273755 2001:106:1100:0:204:23ff:fe5f:163e
fe80::202:2dff:fe07:9948 ICMPv6 Neighbor
advertisement
39 11.276329 2001:106:1200::1
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
Acknowledgement
----------------------------------------------------------------------------------------
40 11.804624 2001:106:1200::2
2001:106:2600::2 ICMPv6 Echo request
41 11.808374 2001:106:2600::2
2001:106:1200::2 ICMPv6 Echo reply
----------------------------------------------------------------------------------------
42 11.811183 2001:106:1200::2
2001:106:2600::2 MIPv6 Home Test Init
43 11.812324 2001:106:1100:0:204:23ff:fe5f:163e
2001:106:2600::2 MIPv6 Care-of Test Init
44 11.814719 2001:106:2600::2
2001:106:1200::2 MIPv6 Home Test
45 11.816481 2001:106:2600::2
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Care-of
Test
46 11.820768 2001:106:1100:0:204:23ff:fe5f:163e
2001:106:2600::2 MIPv6 Binding Update
47 11.823915 2001:106:2600::2
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
Acknowledgement
=========================================================================================
Test2. router adv interval: 0.5s--1.5s. A better
result is as follows, this delay took 0.08s.
======================================================================================
Seq. time Source Address Dist.
Address
.....................
199 54.598008 fe80::202:2dff:fe07:9948
ff02::1:ff5f:163e ICMPv6 Neighbor solicitation
200 54.598103 2001:106:1100:0:204:23ff:fe5f:163e
fe80::202:2dff:fe07:9948 ICMPv6 Neighbor
advertisement
201 54.602306 2001:106:1200::1
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
Acknowledgement
----------------------------------------------------------------------------------------
202 54.681097 2001:106:1200::2
2001:106:2600::2 ICMPv6 Echo request
203 54.684725 2001:106:2600::2
2001:106:1200::2 ICMPv6 Echo reply
----------------------------------------------------------------------------------------
204 54.687158 2001:106:1200::2
2001:106:2600::2 MIPv6 Home Test Init
205 54.688245 2001:106:1100:0:204:23ff:fe5f:163e
2001:106:2600::2 MIPv6 Care-of Test Init
206 54.690599 2001:106:2600::2
2001:106:1200::2 MIPv6 Home Test
207 54.692981 2001:106:2600::2
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Care-of
Test
208 54.695182 2001:106:1100:0:204:23ff:fe5f:163e
2001:106:2600::2 MIPv6 Binding Update
209 54.698293 2001:106:2600::2
2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
Acknowledgement
========================================================================================
Expect more explanation about this. Thanks again£¡
Best regards
Tian
---------------------------------
From: shariq haseeb <[EMAIL PROTECTED]>
To: tian tian <[EMAIL PROTECTED]>
Subject: Re: [mipl] handover time problem: time delay
between HA'BA and the start of RRP?
Date: Thu, 22 Mar 2007 21:15:33 -0700 (PDT)
>Hi Tian,
>
>Try this. Try to reduce the router adv interval. I
>think you are currently sending RADVDs every few
>miliseconds.
>
>Could you try to reduce that and see how much is the
>delay. It could be that the RADVDS have been present
>and they were in a buffer so your Mobile Node is
>processing that.
>
>Anyways good observation, i will try to give a more
>solid explanation after few tests.
>
>rgds,
>Shariq
>--- tian tian <[EMAIL PROTECTED]> wrote:
>
>
>---------------------------------
>
>Hi!
>
>During the analysis of the handover latency of MIPv6,
>I got a confused question.
>
>A normal MIPv6 handover process is as follows:
>
>1.[movement Detection] --> 2.[Router Discovery] -->
>3.[Address Congifuration]-->4.[DAD]-
>->5.[HA Registration]-->6.[CN Registration]
>
>The first four componets are with no problems. So
hier
>I just focus the last two components.
>
>The HA registration (the MN CoA registed to HA) time
>is defined as the transmission delay incurred during
>registration of the MN CoA with its HA. It begins
from
>the MN sends BU to its HA until the MN receives the
BA
>sent by HA.
>
>And then, the MN must start the Return Routability
>Procedure (RRP) before it sends a BU to CN.That is,
>the MN must first initiate the Home Test (HoT) and
>Care-of Test before it can send a BU to CN.
>
>But I observed from the package information catched
by
>ethereal, there was always a time delay between the
BA
>sent by HA and HoT (the start of RRP), one example is
>shown below:
>
>*fe80::202:2dff:fe07:9948 is the IPv6 address of the
>new Access Router (AR),
> 2001:106:1200::2 is the Home Address of MN
> 2001:106:1200::1 is the address of the HA
> 2001:106:2600::2 is CN's address
> 2001:106:1100:0:204:23ff:fe5f:163e is MN's CoA when
>it left its homenet and moved to a visitnet.
>
>========================================================================================
>1. Seq. time Sorce Address
>Distination Address
>-----------------------------------------------------------------------------------------
> .....
> 2243 114.215153 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2244 114.275060 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2245 114.331100 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2246 114.367109 fe80::202:2dff:fe07:9948
>ff02::1:ff5f:163e ICMPv6 Neighbor solicitation
> 2247 114.367168
2001:106:1100:0:204:23ff:fe5f:163e
>fe80::202:2dff:fe07:9948 ICMPv6 Neighbor
>advertisement
> 2248 114.369291 2001:106:1200::1
>2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
>Acknowledgement (BA sent by HA to MN)
>---------------------------------------------------------------------------------------
> 2249 114.395042 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2250 114.451152 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2251 114.503107 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2252 114.556071 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2253 114.623126 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2254 114.667084 fe80::202:2dff:fe07:9948 ff02::1
> ICMPv6 Router advertisement
> 2255 114.677178 2001:106:1200::2
>2001:106:2600::2 ICMPv6 Echo request
> 2256 114.680095 2001:106:2600::2
>2001:106:1200::2 ICMPv6 Echo reply
>----------------------------------------------------------------------------------------
> 2257 114.681259 2001:106:1200::2
>2001:106:2600::2 MIPv6 Home Test Init(RRP
>start)
> 2258 114.681454
2001:106:1100:0:204:23ff:fe5f:163e
>2001:106:2600::2 MIPv6 Care-of Test Init
> 2259 114.684111 2001:106:2600::2
>2001:106:1200::2 MIPv6 Home Test
> 2260 114.686225 2001:106:2600::2
>2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Care-of
>Test
> 2261 114.686647
2001:106:1100:0:204:23ff:fe5f:163e
>2001:106:2600::2 MIPv6 Binding Update
> 2262 114.689347 2001:106:2600::2
>2001:106:1100:0:204:23ff:fe5f:163e MIPv6 Binding
>Acknowledgement (Handover completed)
>
>============================================================================================
>
>As shown in the above table, a delay of 0.32s is
>caused by the blue colored RAs sent by the AR and
also
>ICMPv6 Echo request and reply between the BA sent by
>the HA and the start of RRP. And some other tests
even
>got a worse delay time than this.
>
>What is this delay? Which fators are possible to
cause
>this delay? Anyone has idea about it?
>
>Any suggestion will be very appreciated!
>
>
>Tian
---------------------------------
ÓëÊÀ½ç¸÷µØµÄÁª»úµÄÅóÓѽøÐн»Á÷£¬Á¢¼´ÏÂÔØÃâ·ÑµÄ Live
Messenger
____________________________________________________________________________________
The fish are biting.
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
_______________________________________________
mipl mailing list
[email protected]
http://www.mobile-ipv6.org/cgi-bin/mailman/listinfo/mipl
