Marcelo, > > The other issue we mentioned we should try to figure out is how the TCPINC > extended API should look like. > TCPINC must work with unmodified applications but for those applications that > support it, it should provide additional features through an extended API. > It would be useful to nail down what are those additional features and how > this extended API should look like. > Ideas?
My viewpoint is that it is too early to discuss about an API before we have a vague idea of the type of solution that will be developed. Multipath TCP worked on an API before the full protocol was specified but it is not yet supported by implementations. We will have a very idea of what the API could provide once we know clearly what will be in the protocol. Anyway, the API will only be useful once the protocol has been implemented... Olivier _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
