Re: issue 3: nat traversal

 In your previous mail you wrote:

   luckily this issue is orthogonal to the problems addressed in mobike. mobike
   should allow you to communicate (via some message that has to be defined)
   the addresses that are available at a peer. you might obtain these addresses
   by querying your interface cards, based on pre-configuration

=> I agree only until here.

   or even based
   on the usage of a signaling protocol (such as nsis, midcom or stun). 
   
=> but there is a big difference between this and the previous:
with a NAT the peer has no control at all on its addresses, and
you implicitely ask the other peer to trust the NATs!
   
   > 1) How does the end node discover the public address securely ? 
   > 2) If the public address is known, how does the node communicate this
   >     to the other end securely ?

   i agree with your observation.
   
=> note this is explicitly outside the charter of MOBIKE.

   > I am wondering whether these two things can be seen separately.
   i think they are. if they are we can treat them as a separate problem and
   try to move forward within mobike working group. i think that this is good
   news.  
   
=> please don't forget to change the charter before.

Regards

[email protected]