RE: an example of optimistic DAD in action, with MIPv6

"Ed Remmell" <[email protected]> Tue, 22 Jul 2003 10:32:27 -0700
Newsgroups gmane.ietf.mobileip
Message-ID <000801c35077$3ad73ae0$0400a8c0@eremmell>
I've had a request for the full packet logs for this MN handover
testing. Rather than spamming the list with them, I'll send them to
whomever requests them.

Thanks.
- Ed

> -----Original Message-----
> From: Greg Daley [mailto:[email protected]] 
> Sent: Tuesday, July 22, 2003 12:06 AM
> To: Ed Remmell
> Cc: [email protected]
> Subject: Re: [mobile-ip] an example of optimistic DAD in 
> action, with MIPv6
> 
> 
> Hi Ed,
> 
> It's really cool that you've done this.
> I liked the packet capture too.
> 
> As you may know, there seemed to be interest
> in the DNA BoF session on friday to pursue
> DAD optimization in that forum.
> (So it may be that Opti-DAD has a home).
> 
> Greg
> 
> 
> Ed Remmell wrote:
> > Hello,
> > 
> > Attached is a packet capture of the Elmic Systems' MIPv6 MN 
> performing 
> > a handover per Eager Cell Switching, IPsec/IKE is being 
> used between 
> > the HA and the MN with the (K) bit set to 1 in the BU/BA, the CN is 
> > 3ffe:3333::3333 and is setup to continuously ping the MN's home 
> > address 3ffe:aaaa::bbbb. The MN implements optimistic DAD. Handover 
> > performance (once movement detection has occurred, i.e. 
> once a Router 
> > Advertisement from a new router is received) is very fast, 
> less than 
> > 50 msec between frame #1 (RA) and frame #14 (BA from the 
> CN). The CN 
> > continues ping'ing the MN at its new primary care-of address using 
> > route optimization (frames #16, 17). We have our CN ping 
> client setup 
> > to use a 1-second delay between pings, which is why there 
> is a delay 
> > between frame #14 and frame #16. Frame #15 is the MN 
> completing DAD on 
> > its auto-configured link-local scope address. Frames #8 and 9 are 
> > interesting, because they show optimistic DAD in action (i.e. the 
> > router solicits the MN's auto-configured primary CoA, the 
> MN responds 
> > with a NA for that CoA but the override bit is cleared). 
> Frame #5 is 
> > the MN sending the BU to the HA, and frame #10 is the HA's BA 
> > response. The SAs used to protect this BU/BA exchange were 
> negotiated 
> > earlier using IKE, and as you see from this trace the phase 
> 1 SAs do 
> > not need to be renegotiated due to the (K)=1 Key Management 
> Mobility 
> > Capability. The HoTI/HoT exchange is protected using manually-keyed 
> > IPsec SAs.
> > 
> > Thanks.
> > - Ed Remmell
> > Elmic Systems USA, Inc.
> > 
> > Best of Show Winner, ESC 2003
> > Click on the link and take a look! 
> > http://cmp.iconvention.com/escshowdaily/v33/index.cvn?ID=10183
> >  
> > 
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.497 / Virus Database: 296 - Release Date: 7/4/2003
> >  
> >   
> 
> 
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.497 / Virus Database: 296 - Release Date: 7/4/2003
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.497 / Virus Database: 296 - Release Date: 7/4/2003