Re: [multipathtcp] [Int-area] SOCKS 6 Draft

[Vladimir Olteanu <[e-mail]>]

Hi Mohamed,

No problem. BTW, your work on MPTCP Plain Mode has, in fact, served as 
inspiration for SOCKS 6.

When coupled with TFO on the client-proxy leg, SOCKS 6 also has a 0-RTT 
overhead. It can also be stacked as many times as desired for 
arbitrarily long proxy chains. However:
  * We avoid using the SYN's payload as extra option space (which, I 
think, goes against TCP's core philosophy). The magic number at the 
start of the MP_CONVERT element implies that if any MPTCP stream happens 
to start with 0xFAA8FAA8, the client should not use TFO. I think moving 
up the protocol stack is a more desirable alternative.
  * We support authentication. Connections to the proxy can also be 
initiated from networks outside of the operator's control (e.g. home WiFis).
  * SOCKS 6 is easier to extend. If the client needs to request some 
special behavior from the proxy (e.g. what packet scheduler to use), all 
we have to do is define (and standardize) a new SOCKS option.

(I've also CCed the MPTCP WG).

Cheers,
Vlad

On 07/04/2017 12:09 PM, [e-mail] wrote:
>
> Hi Vladimir, all,
>
> (focusing only on this part of the message).
>
> I do fully agree that shortening MPTCP connections setup is key. 
> Having 0-RTT is an important requirement for this effort. Achieving it 
> without out-of-band signaling would be even ideal.
>
> Can you please elaborate on the benefits of your proposal compared to 
> https://www.ietf.org/proceedings/98/slides/slides-98-mptcp-sessa-network-assisted-mptcp-03.pdf 
> which allows to achieve 0-RTT proxying.
>
> Thank you.
>
> Cheers,
>
> Med
>
> *De :*Int-area [mailto:[e-mail]] *De la part de* 
> Vladimir Olteanu
> *Envoyé :* vendredi 30 juin 2017 23:37
> *À :* David Schinazi
> *Cc :* [e-mail]
> *Objet :* Re: [Int-area] SOCKS 6 Draft
>
> Hi David,
>
>     */[/*SNIP]
>
>     - Out of curiosity, what specific use case are you using this
>     protocol for?
>
>     We are looking into using MPTCP on mobile devices to "bind" 4G/LTE
>     and WiFi. Mobile data networks have high latency, hence the drive
>     to shave off as many RTTs as possible and to take advantage of
>     TFO, at least on the client-proxy leg.
>
> Cheers,
> Vlad
>