[mif] draft-deng-mif-api-session-continuity-guide-02

[Brian E Carpenter <[e-mail]>]

Hi,

If the interface changes I can understand how this works from the
application's point of view: it discovers experimentally whether it has
a working path via the new interface. Nothing new there, really.

If the host's address changes too, I don't find the discussion in
section 3 very helpful. Saying that the application ought to be able
to handle this really says nothing. And of course there are other
approaches possible, by having either the transport layer or the
network layer handle it. We have at least three existence proofs for
such solutions (SCTP, MPTCP and shim6). They all need tweaking for the
case of a brand-new address being added, and 6renum needs that tweak
too.

A related point is that load balancers at the server end are part
of the problem too, if you want to preserve sessions across a
re-addressing event.

I think section 3 is just the tip of a very complicated iceberg.

Regards
   Brian