Re: [multipathtcp] Consensus call on potential MPTCP proxy work

[Juliusz Chroboczek <[e-mail]>]

>>> What I meant by "native MPTCP connections" is that the CPE won't proxy
>>> a SYN that contains MP_CPABALE received from an MPTCP-capable
>>> client. That is, the CPE won't modify the destination IP address to the
>>> one of the network-located proxy. That SYN+MP_CPABALE will be received
>>> and handled directly by the remote server.

>> It will still act as a middlebox, though, with no way for the client to
>> avoid it.

> No. This is not true. 

> Connections that are not eligible to network-assisted MPTCP service
> WON'T involve a proxy.

I've probably missed something, then.  I don't see anything in -10 that
says that non-eligible packets are forwarded statelessly without any
modification, including forwarding unknown IP and TCP options.  All I see
on the subject is Section 4.3 paragraph 2, which I find hardly reassuring.

My gut feeling is that either the proxy is implemented at the upper
layers, in which case it terminates all connections and hence discards any
unknown options, or it is implemented at a lower layer, allowing it to
bypass selected packets, in which case it is no longer a mere upper layer
proxy.  I just don't see how you can have it both ways.

Could you please explain what I'm missing?

-- Juliusz