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

[Comment from secretary: TEMP-draft-kivinen-mobike-protocol-00.txt has
both direct indications (peer explicitly requests change) and indirect
based on address lists (when current address seems to have stopped
working, try others). draft-dupont-ikev2-addrmgmt-04.txt also has
both.]

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

Jari Arkko (2005-05-13):

It seems to me that our understanding of this problem
has develop a lot since we originally wrote issue 1. We
now have a better understanding of what other components
there are in a system and how Mobike interacts with them;
we are debating which entity makes decisions (20), we
have decided what to do when the sign of trouble is
a lack of packets (16), we have decided what kind of
connectivity assumptions we make (17), and we are
working through how the appearance of NATs on a
new path affects MOBIKE (3).

In conclusion it seems that we are already covering the
details in several other issues. Therefore issue 1 will
be closed as a duplicate.

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