Issue 56 (was: protocol draft status and moving forward)

Jari Arkko writes:
> The issue list is at [3]. The issues that I believe still
> need further discussion are
>      56 - ingress filtering

Actually I think the design draft should have enough text about this
(see section 5.1.2. Connectivity).

I do not think we need more than what is now in the protocol draft
already i.e:

----------------------------------------------------------------------
   MOBIKE follows the IKEv2 practice where a response message is sent to
   the same address and port from which the request was received.  This
   implies that MOBIKE does not work over unidirectional paths.
----------------------------------------------------------------------

but I would change that to:

----------------------------------------------------------------------
   MOBIKE follows the IKEv2 practice where a response message is sent to
   the same address and port from which the request was received.  This
   implies that MOBIKE does not work over unidirectional address
   pairs.
----------------------------------------------------------------------

i.e change "unidirectional paths" to "unidirectional address pairs",
as we do not really care about paths but address pairs.

MOBIKE will work perfectly if even if there is 2 unidirectional paths
(if we use the definition of path that includes the route of the
packet), which form one bidirectional address pair for MOBIKE to
use...
-- 
[email protected]