Subject: RE: [nemo] RE: [Mip6] Consensus call on making IDdraft-wakikawa-nemo-v4tunnel aMIP6/NEMO WGs document

From: "Soliman, Hesham" <[email-masked]>
Date: Fri, 1 Apr 2005 16:00:17 -0500

> okay. draft-soliman-v4v6 deals with lots of scenarios including
 > scenario 1) and 2) above. draft-wakikawa talks only about 
 > scenario 1).
 > the idea of binding an IPv4 CoA to an IPv6 HoA is very old.
 > draft-soliman is not the first one that spoke about it. 

=> As a side note, for my own research, Vijay, I'd appreciate a pointer
to some prior art in this area. I don't believe Doors does that binding.
Doors does something different.

thx,
Hesham

 > draft-wakikawa
 > just explains in *very* detail how to do scenario 1), including a new
 > mobility option, MN and HA operation to process this new mobility
 > option, IPsec SPD and SAD entries for securing the IPv6-over-IPv4
 > tunnel, NAT traversal, how to negotiate a particular tunneling
 > mechanism and new binding ack status values.
 > 
 > > The main difference is the BU message
 > > format: based on draft-wakikawa the source address of the 
 > IPv6 packet is
 > > the HoA, since the message is treated as a particular 
 > de-registration;
 > > in draft-soliman the source address is the CoAv4 mapped in 
 > IPv6 address
 > > format. I'd like to understand better the rationale behind 
 > the choice in
 > > draft-wakikawa. Personally, I think that the approach of 
 > draft-soliman
 > > is a little bit cleaner since the BU is not considered a 
 > de-registration
 > > message. 
 > 
 > hmm.. but you want to remove any existing binding cache entries that
 > bind the IPv6 HoA to an IPv6 CoA, right? we are just combining
 > removing an existing BCE with IPv6 CoA and adding a new BCE with IPv4
 > CoA.
 > 
 > Vijay
 > 
 > 
 > 

===========================================================
This email may contain confidential and privileged material for the sole use
 of the intended recipient.  Any review or distribution by others is strictly
 prohibited.  If you are not the intended recipient please contact the sender
 and delete all copies.
===========================================================

_______________________________________________
Mip6 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mip6