Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt

From: "Soliman, Hesham" <[email-masked]>
Date: Mon, 24 Oct 2005 12:47:51 -0400

> My point is that having IPv4 CoA and Having IPv4 HoA is different
 > things and they are orthogonal.  (I think my explanation is not
 > good...)

=> Agreed. If you are trying to provide a complete transition
mechanism you might want to solve more than one issue. Some of 
the issues might be orthogonal to each other, but still crucial
for the overall problem. For example, NAT traversal is a separate
problem that may or may not be needed, depending on where the MN is 
located, but we still solved it in the current draft. 

 > Let's consider to implement IPv6 mobile node which supports IPv4
 > access network, but don't support IPv4 HoA.  Which RFC should we
 > support?  

=> I don't understand. There are no RFCs for this case today. If
you're talking about the "future" RFC, then this hypothetical
MN would be supporting parts of the current draft (future RFC).
The current draft doesn't say that the MN MUST implement the IPv4
home address option. 

   If we continue to discuss the different things in 
 > one draft,
 > we must also make it clear which section(s) is necessary to implement
 > what feature.  But I feel it is a bad idea to specify 
 > features in such
 > a manner.  Easier way to make it clear is to divide the 
 > specification...

=> This is a product management issue. I've been through this 
exercise many times before and it's pretty straight forward to
mention what features are not supported.  

 > Frankly speaking, I think I can implement the function from the text,
 > since I already have much knowledge of MIP implementation.  But maybe
 > the draft at least should mention about

=> Good to see that you can implement it. I'll take a look at the 
text you sent and give you some feedback. Thanks for your suggestion, 
it looks like this could be useful for the draft.

Hesham

===========================================================
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