Stephane Beaulieu's comments on draft-mobike-protocol-04.txt

Section 3.
"MOBIKE allows both parties to have several addresses, and there are
   up to N*M pairs of IP addresses that could potentially be used."

- Do we not also allow a party to temporarily have 0 addresses?  While I
walk from the office to Starbucks across the street, I may loose all
wireless for a few minutes.

++++++++++++++++++++++++++

Section 3.2 (2nd example)
"(The initiator gives up on the current address pair, and tests the
   other available address pair.)"

- Can the initiator test multiple address pairs simultaneously?
(assuming he has the window space to do so).
- If not, how many retries and how many seconds between each retry on a
single address pair before we move on to the next?  Are there
recommendations for this, or is this purely implementation detail?

+++++++++++++++++++++++++++++

Section 3.2
- Is there a way to remove an address? (ex. Pull out my wireless
adapter).  

Tero mentioned in another thread that he assumed that sending a new
ADDITIONAL_X_ADDRESS notify overwrote all past addresses, but this isn't
clear to me from the text.

++++++++++++++++++++++++++++++

Section 3.3

IMO, there should be text in this section that explains that Mobike
tries to detect sporadic NAT mapping changes by adding NATD payloads in
the DPD msgs.  I know this is explained later, but I would expect to
hear something about this in this section, since this is the "NAT"
section.

++++++++++++++++++++++++++++++

Section 4.2

I don't understand why we need to switch to port 4500 even if there is
no NAT in the path.  Can someone explain this to me?  Or better yet,
explain it in the draft?


Thanks,
Stephane.