Re: [multipathtcp] potential MPTCP proxy charter item

Alan Ford <alan.ford@gmail.com> Tue, 08 November 2016 16:00 UTC

Return-Path: <alan.ford@gmail.com>
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 CF2D1129892 for <multipathtcp@ietfa.amsl.com>; Tue, 8 Nov 2016 08:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nQzTRXz4d_4Y for <multipathtcp@ietfa.amsl.com>; Tue, 8 Nov 2016 08:00:22 -0800 (PST)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C2471297AA for <multipathtcp@ietf.org>; Tue, 8 Nov 2016 08:00:22 -0800 (PST)
Received: by mail-lf0-x229.google.com with SMTP id t196so143388794lff.3 for <multipathtcp@ietf.org>; Tue, 08 Nov 2016 08:00:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nTq/NG27T5e6WQ2xOnu7MAFiNkKKwE5kxXyodO8o0ts=; b=pIHE/UImQgdAfOoE0HGsaX/aQsnibCh2mKvuSpYRYgqmji90RCjtFBoFpn+TaaJC2T LTvw+m2NjOPwj9Uu3rDnr6J3bpxhk6PbbVb50YuUwIJjqMn2jWCvnXuB7aZMI5ZAcoom BZpCQpJUNL6b5cUiEL6qhLfBWR5/yljWB+JinLljL9i7JTAbYmQIKDkaUNuGB0A0quev ASAAcJORAyVlmP3Mh4QkJg6mNfsWnp1HhovRzeXBTu12noF3Ot/7oWEQfghpN0T/tG6o /UUWpxWcbH7ZcRTsAN0e6s9wlDrW4WdxJcQwFwDkw11OgpUbtnrQrkADEp8kUveCnjCX ofBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nTq/NG27T5e6WQ2xOnu7MAFiNkKKwE5kxXyodO8o0ts=; b=hLhrtun/SB26dy8evHmbVZhGsrXH92TJYe+2y4hxYaAfQYw8LNQKSlThw5OuDJqa/l teEcI8mGXf4EET1/WzUA1hzEHWQoReEEkBoffW7TTZhfRjcFpUkuMaaIs4YhmdnLlT26 MMI1eSlso3QQP7kLUtydKi1PsTyXmnExobeGc8hM42Hy+/qaHwhzsR7ekq5yJGw1D9ZQ y2nqTn3h85EdahCNuJjXa3ku0Ofzhak7oBRNi5q3PAKrGPfdvXXFNhI7jCA4K2T6kPev Q+l4gg/RLz8iUEoQS38sh0p8cuM5yK8RKswW3pbsOsue/IBXJxs0vjvMJFWwBF7hafWa hwqw==
X-Gm-Message-State: ABUngveVTn8qcoL7Nj+1w3p7LSjUJpX9ZNQuuExsxlJYcmahPOe3GPn1EXqnZ3ezy7cQKg==
X-Received: by 10.25.195.195 with SMTP id t186mr6113011lff.96.1478620820450; Tue, 08 Nov 2016 08:00:20 -0800 (PST)
Received: from alans-mbp.rd.pexip.com ([46.19.20.98]) by smtp.gmail.com with ESMTPSA id g21sm6230115lfe.47.2016.11.08.08.00.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 08 Nov 2016 08:00:19 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009DAE3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Date: Tue, 8 Nov 2016 16:00:18 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A95CD4E7-6A3B-4622-A818-03B10AD75D4D@gmail.com>
References: <CCD1A987-0F3C-4775-8B0E-5232965E7E22@nokia.com> <CAO249ydpdtR53VBniDczSt4zj_kk32c2W_FoZKs2XED0Jzk7Jw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009D9577B@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <22907_1476946228_58086934_22907_5464_1_a7bca8d2-7656-4ff0-9f01-cf307f017148@OPEXCLILM42.corporate.adroot.infra.ftgroup> <57543A7A-1542-4C60-A5D3-E1658354BE5A@tik.ee.ethz.ch> <73a1c0dd64a843a5baa645d960c82886@rew09926dag03b.domain1.systemhost.net> <b8bfd5c6-21eb-4c4f-879a-851c3a71792a@OPEXCLILM31.corporate.adroot.infra.ftgroup> <56CE164A-9A62-4B57-9CFF-33DBD45BA8B2@gmail.com> <787AE7BB302AE849A7480A190F8B933009D9CA84@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <85D52AE4-FE5F-4977-8927-6BDB72614D07@gmail.com> <787AE7BB302AE849A7480A190F8B933009DAAA88@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D2630820-7586-4361-A626-3278F22C319C@gmail.com> <87270f12-59ee-3caf-eeef-685195b35dcd@uclouvain.be> <A5256E6E-E2BA-4763-AEF9-3CC50EB432A2@gmail.com> <7f9dd7ab-2e24-0319-b62f-fc4fa68b9568@tik.ee.ethz.ch> <787AE7BB302AE849A7480A190F8B933009DAE3A6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/14_fGpKpB7PqX2wZmlfFIusb_8w>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] potential MPTCP proxy charter item
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 08 Nov 2016 16:00:24 -0000

Med,

> On 8 Nov 2016, at 15:32, mohamed.boucadair@orange.com wrote:
> 
> The problem is that if the MCP blindly withdraws itself based on the server capabilities, MPTCP connections may not be established in some cases, e.g., private IPv4 addresses are assigned for some secondary access networks. 

Could you walk me through this scenario? Despite Olivier’s and your diagrams I’m not following how this does not work. If the far end supports MPTCP, the secondary interface gets to the far end by its own route and joins the MPTCP connection. If the far end does not, then the MCP will have inserted its address in the MPTCP signalling, so the secondary interface could route to it directly too.

So in what scenario does this not work?

Regards,
Alan