--------------------

Maureen Stillman (2005-10-04):

The fact that we are only discussing tunnel mode is not explicitly
mentioned until section 3.4 in this document.  There is one place in the
introduction that mentions it, but only in passing.  Everywhere else, it
is inferred and/or assumed.  Although it is said explicitly in section
3.4, but that is after we have read a lot of text without knowing this.
Also, it is called limitations, rather than scope.  I suggest that you
move this 3.4 to section 2. and call it scope.  

Here is suggested text:

2. Scope

The scope of this document is limited to tunnel mode as the base version
of the MOBIKE protocol.

---------------------------------------------------------------
Some nits:

   MOBIKE allows both parties to have several addresses, and there are
   up to N*M pairs of IP addresses that could potentially be used.
   The decision of which of these pairs to use has to take into
   account several factors.  First, the parties have may preferences
   about which interface should be used, due to performance and cost
   reasons, for instance.  Second, the decision is constrained by the
   fact that some of the pairs may not work at all due to incompatible
   IP versions, outages somewhere in the network, problems at the
   local link at either end, and so on.

How about changed text indicated by *:

   MOBIKE allows both parties to have *multiple points of attachment
   each represented by an IP address*, and there are up to N*M pairs
   of IP addresses that could potentially be used *for the tunnel
   endpoints*.  The decision of which of these pairs to use has to
   take into account several factors.  First, the parties have *many*
   preferences about which interface should be used, due to
   performance and cost reasons, for instance.  Second, the decision
   is constrained by the fact that some of the pairs may not work at
   all due to incompatible IP versions, outages *delete somewhere* in
   the network, problems at the local link at either end, and so on.

--------------------

James Kempf (2005-10-04):
https://www.machshav.com/pipermail/mobike/2005-October/001100.html

Yes, I noticed this as well.

I'd suggest including it even earlier, in the abstract:

    ...MOBIKE allows hostst to update the (outer) IP addresses associated 
with IKEv2 and **tunnel mode** IPsec Security Associations...

--------------------

Pasi Eronen (2005-10-24):
https://www.machshav.com/pipermail/mobike/2005-October/001198.html

Ok with me (although the fact we're dealing with tunnel
mode is already mentioned in Section 1: transport mode SAs
don't have "outer (tunnel header)" addresses).

--------------------