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

[Vladimir Olteanu <[e-mail]>]

Hi Mohamed,

I'm replying specifically to the parts quoted below.

SOCKS is used by explicit proxies; anything related to transparent 
proxies is beyond its scope. It does not preclude the deployment of 
anything transparent. In other words, I merely propose it as an 
alternative to MP_CONVERT.

Discussing PCP, IPv6 source address preservation, UPnP etc. makes no 
sense in this context.

Cheers,
Vlad


On 7/6/2017 3:56 PM, [e-mail] wrote:
>
> *De :*Vladimir Olteanu [mailto:[e-mail]]
> *Envoyé :* mercredi 5 juillet 2017 18:39
> *À :* BOUCADAIR Mohamed IMT/OLN; David Schinazi
> *Cc :* [e-mail]; multipathtcp
> *Objet :* Re: [Int-area] SOCKS 6 Draft
>
>  <SNIP>
>
> On 7/5/2017 9:00 AM, [e-mail] 
> <mailto:[e-mail]> wrote:
>
>     <SNIP>
>
>     *De :*Vladimir Olteanu [mailto:[e-mail]]
>     *Envoyé :* mercredi 5 juillet 2017 01:35
>     *À :* BOUCADAIR Mohamed IMT/OLN; David Schinazi
>     *Cc :* [e-mail] <mailto:[e-mail]>; multipathtcp
>     *Objet :* Re: [Int-area] SOCKS 6 Draft
>
>     <SNIP>
>
> Can you please let me know if the proposal supports the following 
> features:
>
> ·Support incoming connections (Proxy<---Remote Host): That is the 
> proxy intercept a TCP connection that it transforms into an MPTCP one.
>
> Yes. See section 7.2. The client makes a request and then has to keep 
> the connection to the proxy open. When the proxy accepts a connection 
> from a remote host, it informs the client of the remote host's address 
> and starts relaying data. SOCKS 5 has the exact same feature. You are 
> limited to one incoming connection per request, though.
>
> [Med] In the plain mode, there is no such limitation because we are 
> leveraging on PCP (RFC6887).
>
> ·If such feature is supported, how a host located behind a CPE 
> (Host----CPE-----Proxy----Remote Host) can instruct dynamically the 
> CPE so that it can forward appropriately incoming connections?
>
> It does not have to. The connection on the host-proxy leg is initiated 
> by the client.
>
> [Med] I’m not sure to understand your answer here. Let’s consider that 
> your host is using UPnP IGD to talk with the CPE to accept incoming 
> connections + those connections are eligible to the MPTCP service. How 
> the solution would work?
>
> <SNIP>
>
> ·IPv6 source address/prefix preservation
>
> I'm not sure what you mean by that.
>
> [Med] Please see slide 18 of 
> https://www.ietf.org/proceedings/98/slides/slides-98-mptcp-sessa-network-assisted-mptcp-03.pdf 
>
>