[multipathtcp] draft-boucadair-mptcp-plain-mode-07

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 01 June 2016 18:37 UTC

Return-Path: <sarikaya2012@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 58BBA12D18C for <multipathtcp@ietfa.amsl.com>; Wed, 1 Jun 2016 11:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 WWWn4OhjYw6v for <multipathtcp@ietfa.amsl.com>; Wed, 1 Jun 2016 11:37:47 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 4942412D16C for <multipathtcp@ietf.org>; Wed, 1 Jun 2016 11:37:47 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id a6so39464275vkg.3 for <multipathtcp@ietf.org>; Wed, 01 Jun 2016 11:37:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to; bh=QUM5H4MjoRq9FYLmnZUWUW+hEgE2jNvLaO37JkDb/y4=; b=RRoBpetK9/SWhVA79ZtQa3qJ8DCLWX899R+hSBIhDpUBJASKmrpkQormLhkRfmBKyI ivyTJXaOZYVMR0BeE2kDe7SeJ5AJ/Wsf3Hj0SV2y0B9EWNJ6RMN/OYf8K2XgUi+xGzLv 0d3TJ3KdF/r8X4jJ5YnY5GulYLh11QGggNy0FeADas6iZ+b/9MP1x+5lOzAhpyMPau2Q 8vI/e/JJtzmZqxEwv5hwtuF6qY4Qxmmit0yc98UHBiKZG5XkkAhj1X3bzL2DAU8OUCXG BoWLlS/yozUK+psDe5+2iJ1psuwZ5gOeEEJOfuRvZIrJt4pomXtIav4iYh3DW+Mm/zyi Yi+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:date:message-id:subject :from:to; bh=QUM5H4MjoRq9FYLmnZUWUW+hEgE2jNvLaO37JkDb/y4=; b=SgYTZD/qwydYAZC/DoxgtsDgE2QKyr1Z8R1ETpTBiAVUaOr07PTkT8Kjnm8ngvBkab xabMHKFU/LoSeAPb9OQ26d6St0laVPhIdPfwbLzqOjAauQamL/O1xUnM7NXWA9sbqtiI YpK4oBFtvJV9L9Jpm/48z9c2BuCbbcXX+gmWQv4UdiJeRln45ZxMbdLhgviFQH/YDNBw rz+lp20hRdW3aT2pNfRF1ZYTQjmPT+hJ2qa1r0Tuwl7icmaW1/RzC+CLUbdP/FGz+YcG nMae73jGqYomqSMbOmsNkekNc9XAAFFPENTz43KEmQMjHAAm0F1rHn0qD5TbOwF6cOGE OeYQ==
X-Gm-Message-State: ALyK8tIlOc3US+B3CcV1tIPL22HQdAmu26+4QoyQVINXlzN16pU2KQj4UhCAqyXWYDP3FNICAjC544+4JpfnKg==
MIME-Version: 1.0
X-Received: by 10.159.38.54 with SMTP id 51mr2777916uag.27.1464806266176; Wed, 01 Jun 2016 11:37:46 -0700 (PDT)
Received: by 10.176.2.232 with HTTP; Wed, 1 Jun 2016 11:37:46 -0700 (PDT)
Date: Wed, 01 Jun 2016 13:37:46 -0500
Message-ID: <CAC8QAccht1nMP95HVdP6YcqJfxNryvDbhaK=LY0LcW5-JKM82A@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: multipathtcp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/8iB7J3NLcjsMIUKIYJ9TfobAVIM>
Subject: [multipathtcp] draft-boucadair-mptcp-plain-mode-07
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: sarikaya@ieee.org
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: Wed, 01 Jun 2016 18:37:49 -0000

 Hi all,

Recent mails in this thread came to my attention because I work on the
hybrid access network issues and wish to convey my views on some of
the issues discussed.

First of all, the claims that there is strong operator interest on
this is over blown. Hybrid access is based on offloading some CPE
traffic to 3G/LTE network, I don't think mobile operators are fond of
such a thing.

Also I strongly concur with Yoshi's point of CPE to convert UDP or TCP
into MPTCP and requires
Concentrators to convert back MPTCP into UDP or TCP is a complex
process. The crux of this is the problems arising from the use of
MPTCP for tunneling, which is what this draft is advocating.

Here I recommend Joe Touch's Intarea draft
https://tools.ietf.org/id/draft-ietf-intarea-tunnels-02.txt
on IP Tunnels in the Internet Architecture. IETF developed many
tunneling protocols which are surveyed in this draft but none of them
are TCP/MPTCP based.
I also question suitability of this work to the charter. There is this
charter text:
Finally, the working group will explore whether an MPTCP-aware
  middlebox would be useful, where at least one end host is MPTCP-enabled.
  For example, potentially helping MPTCP's incremental deployment by
  allowing only one end host to be MPTCP-enabled and the middlebox acts as
  an MPTCP proxy for the other end host, which runs TCP; and potentially
  helping some mobility scenarios, where the middlebox acts as an anchor
  between two MPTCP-enabled hosts. The working group will detail what real
  problems an MPTCP-enabled middlebox might solve, how it would impact the
  Multipath TCP architecture (RFC6182), what proxy approach might be
  justified as compared against alternative solutions to the problems, and
  the likely feasibility of solving the technical and security issues.

This draft has a middlebox called Concentrator but it is not trying to
enable MPTCP hosts to communicate with TCP hosts, it is just tunneling
the traffic. So there is no charter item that fits to this draft.
I strongly suggest staying away from making MPTCP a tunneling protocol.

Regards,

Behcet