[Mobike] issue 3: nat traversal

[Francis Dupont]

 In your previous mail you wrote:

    >    > 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 not sure which part you are referring to. MOBIKE is about
   exchanging addresses. And i don't know why doing (2) would put it
   outside the charter.
   
=> perhaps I have not the same reading of the charter? Quoting it:

"An explicit non-goal is the construction of a fully fledged mobility
 protocol. In particular, the WG shall NOT develop mechanisms for the
 following functions:

 ...

 o IP address changes done by third parties (NATs, firewalls etc). In
   particular, MOBIKE shall not replace or modify IKEv2 NAT traversal
   function. MOBIKE handles IP address changes initiated by one of the
   endpoints of the security associations. NAT traversal handles other
   address changes. MOBIKE should not be tightly coupled with the NAT
   traversal function, but it is necessary to specify in which cases
   (if any) they can be used together, and how they interact."
   
Regards

Francis.Dupont at enst-bretagne.fr