[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: API for SHIM
El 08/03/2006, a las 16:39, Wesley Eddy escribió:
On Wed, Mar 08, 2006 at 04:16:10PM +0200, marcelo bagnulo braun wrote:
In addition to the interface between the shim and application, it is
imperative that the interface between shim and transport protocol be
considered. At the time when the shim decides to failover, the
transport protocol should be kicked so that it can reinitialize the
state associated with estimation of various path properties (congestion
window, RTT, path MTU, etc). Research has indicated that not doing
this can be problematic both for the end host and the network .
indeed, good point
I guess the communication between the shim and transport should be
bi-directional, since i guess that the shim would benefit from knowing
that the connections that are using certain locator pair are working.
I am not sure if with the current failure detection mechanisms we can
benefit from ULP positive feedback). I mean, what would be ULP positive
feedback be useful for?
This has been discussed in TSVWG and TCPM, and is described in at least
a couple of internet drafts (in the process of merging):
Wesley M. Eddy
Verizon Federal Network Systems