IETF Logo Mail Archive

Re: [multipathtcp] q about on-path proxy

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Fri, 24 March 2017 18:07 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4699F12984C for <multipathtcp@ietfa.amsl.com>; Fri, 24 Mar 2017 11:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXLrBmdeuGKl for <multipathtcp@ietfa.amsl.com>; Fri, 24 Mar 2017 11:07:07 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34B50126D05 for <multipathtcp@ietf.org>; Fri, 24 Mar 2017 11:07:06 -0700 (PDT)
Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2C2E129C144 for <multipathtcp@ietf.org>; Sat, 25 Mar 2017 03:07:04 +0900 (JST)
Received: by mail-oi0-f41.google.com with SMTP id f193so5278399oib.2 for <multipathtcp@ietf.org>; Fri, 24 Mar 2017 11:07:04 -0700 (PDT)
X-Gm-Message-State: AFeK/H0t0Xt9GsYBcQRpnxdZQvtHEfisQFjDSr/tYHgBhBtcwa5+MtpWniF1rejO6Ow7gyYBz99Z0LTxUdQCJA==
X-Received: by 10.202.81.207 with SMTP id f198mr1873161oib.136.1490378822631; Fri, 24 Mar 2017 11:07:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.41.137 with HTTP; Fri, 24 Mar 2017 11:07:02 -0700 (PDT)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E3FE7E@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <CAO249ydsuoAUn0y6yo62OM8mdp_AfyS1cA+patgQ84ata5piXw@mail.gmail.com> <a5ae92e4-c0c9-96c6-a575-f23891189087@uclouvain.be> <787AE7BB302AE849A7480A190F8B933009E37584@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <ee22e83a-464e-f3a1-3d48-15043bcd6f74@uclouvain.be> <787AE7BB302AE849A7480A190F8B933009E3C5EC@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CAO249yc6KkvxKG3g5NzLguZZfEfGrvG1qFfvXL0WNwzECWdrLg@mail.gmail.com> <f7ab3458-7004-dcce-5f4a-c036705d0530@uclouvain.be> <CAO249yfzT32mku_1jwH+H0jKwa+LuCLQ2RsORrrqcDMA3qNL7A@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E3FE7E@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Fri, 24 Mar 2017 11:07:02 -0700
X-Gmail-Original-Message-ID: <CAO249yfyYGJXy=COpF+uo-DXg67_XkJnbnd-Gs4P3U9KTjevOQ@mail.gmail.com>
Message-ID: <CAO249yfyYGJXy=COpF+uo-DXg67_XkJnbnd-Gs4P3U9KTjevOQ@mail.gmail.com>
To: mohamed.boucadair@orange.com
Cc: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, "Olivier.Bonaventure@uclouvain.be" <Olivier.Bonaventure@uclouvain.be>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="001a1146b7f04dca68054b7ddcbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/aWpx82X7AzfEsLeeAvrsUAgUHYg>
Subject: Re: [multipathtcp] q about on-path proxy
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Mar 2017 18:07:09 -0000

Hi Med,

Thanks for the response.
Just one point..

On Thu, Mar 23, 2017 at 11:41 PM, <mohamed.boucadair@orange.com> wrote:

> Hi Yoshi,
>
>
>
> Please see inline.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
> *Envoyé :* jeudi 23 mars 2017 23:38
> *À :* Olivier.Bonaventure@uclouvain.be; BOUCADAIR Mohamed IMT/OLN
> *Cc :* multipathtcp
> *Objet :* Re: [multipathtcp] q about on-path proxy
>
>
>
> Hello Olivier, Med,
>
>
>
> Thanks for providing detailed responses. I feel that things now got
> clearer than before.
>
> In my understanding, the benefits for on-path mode is MCP can stop
> intercepting and splitting connection once it learns that both endpoints
> support MPTCP.  if there're other benefits, please point out.
>
>
>
> One thing which is not very clear to me yet is MP_PREFER_PROXY.
>
> Med explained that there is a way to learn the endpoints support MPTCP. I
> think MCPs can learn it through the method described in Figure 15, however
> I'm not sure how the sender can learn it.
>
> [Med] An implementation example would look like the following :
>
> ·         A sends a SYN message with MP_CAPABLE+MP_PREFER_PROXY to B
>
> ·         This SYN is intercepted by an MCP which tracks the connection,
> that is: it removes the MP_PREFER_PROXY and add filters to intercept
> relevant incoming SYN/ACK. The SYN (MP_CAPABLE) is then forwarded to the
> next hop and so on, until it reaches B.
>
> ·         If the SYN/ACK received from B includes MP_CAPABLE, the MCP
> will forward it to A. A is now aware that B is MPTCP-capable and they can
> establish subsequent subflows directly. The MCP does not announce
> explicitly itself to A.
>

Hmm. I am not sure about this.
I understand A will receive MP_CAPABLE from B in this case. But, I think
even B doesn't support MPTCP, A will receive MP_CAPABLE from B which is
created by MCP (by spoofing). So, I think A cannot identify whether this is
from B or MCP.
--
Yoshi

>

v2.23.0 | Report a Bug | By Email