On 9/17/2017 7:05 PM, Tom Herbert wrote: >> I agree, there is engineering effort to bring MPTCP in the mainline Linux >> kernel, but this is outside the scope of IETF. >> > Oliver, > > I disagree, discussions about deployment and implementation are in > scope. The primary argument for necessity that this draft makes is > that MPTCP is being deployed too slowly. If we are to consider that > argument then we need to understand _why_ deployment of MPTCP is slow, > so the details about current deployment state and implementation are > pertinent. Also, while there is significant engineering needed to get > MPTCP into Linux or other systems, we cannot ignore the significant > (possibly more) engineering effort to define, standardize, develop and > deploy an interim solution on clients and converters. Additionally, this would leave in place a solution that complicates the design space for MPTCP for the future. That sort of cruft can be difficult to get rid of.
> In the end, if > the problem can be solved without creating a new complex and invasive > protocol that is the better path forward. +1. There are no "urgent" problems in the IETF for which short-term solutions are needed, IMO. We need to take the long view of our actions. Joe > > Tom >
