Re: [multipathtcp] potential MPTCP proxy charter item

<mohamed.boucadair@orange.com> Fri, 04 November 2016 15:08 UTC

Return-Path: <mohamed.boucadair@orange.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 C1410129561 for <multipathtcp@ietfa.amsl.com>; Fri, 4 Nov 2016 08:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham 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 jseXYo0Eh0nP for <multipathtcp@ietfa.amsl.com>; Fri, 4 Nov 2016 08:07:59 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17AE81288B8 for <multipathtcp@ietf.org>; Fri, 4 Nov 2016 08:07:59 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 5E5502DC4EA; Fri, 4 Nov 2016 16:07:55 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.33]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 3994123809A; Fri, 4 Nov 2016 16:07:55 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM42.corporate.adroot.infra.ftgroup ([fe80::d5fd:9c7d:2ee3:39d9%19]) with mapi id 14.03.0319.002; Fri, 4 Nov 2016 16:07:55 +0100
From: <mohamed.boucadair@orange.com>
To: Joe Touch <touch@isi.edu>, =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
Thread-Topic: [multipathtcp] potential MPTCP proxy charter item
Thread-Index: AQHSNqumRUtLqWz5O0GSJn2xeu0zS6DI7COQ
Date: Fri, 4 Nov 2016 15:07:54 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009DAC92E@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <CCD1A987-0F3C-4775-8B0E-5232965E7E22@nokia.com> <428609FE-DE79-45CD-B668-EF95F409B593@tik.ee.ethz.ch> <8bed05c5-9f6f-04aa-8aa8-690aa3ce30f4@uclouvain.be> <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> <e81c001b-ba6b-2990-9a62-09622e1339e1@uclouvain.be> <ACE6C987-A8AD-477B-986C-CFB4A438323F@gmail.com> <DA4EE00C-A54A-45C0-95B1-72F59BE5134D@tik.ee.ethz.ch> <AE721A71-0B9C-4A05-94AE-C104318DCF7F@isi.edu> <787AE7BB302AE849A7480A190F8B933009DAC89D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <eb401a5b-4260-fbe4-935c-08343c2ed2fd@isi.edu>
In-Reply-To: <eb401a5b-4260-fbe4-935c-08343c2ed2fd@isi.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.17.114517
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/jWoWw9cfHwR-hmLHOagtV_GWNJc>
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: Fri, 04 Nov 2016 15:08:01 -0000

Re-,

I'm familiar with those documents, Joe. 

In addition to the proposal shared by Olivier, we are also considering this one: https://tools.ietf.org/html/draft-boucadair-tcpm-capability-option-00 for managed environments. 

Cheers,
Med

> -----Message d'origine-----
> De : Joe Touch [mailto:touch@isi.edu]
> Envoyé : vendredi 4 novembre 2016 15:57
> À : BOUCADAIR Mohamed IMT/OLN; Mirja Kühlewind
> Cc : multipathtcp@ietf.org
> Objet : Re: [multipathtcp] potential MPTCP proxy charter item
> 
> 
> 
> On 11/4/2016 7:54 AM, mohamed.boucadair@orange.com wrote:
> > Re-,
> >
> > There are already some generic proposals (e.g., SYN EOS), but IMHO those
> require an out of band SYN (second SYN) to extend the TCP option space,
> while the payload space of the original SYN can be used!
> 
> Please read the generic proposals. The explain why the SYN payload
> cannot be used.
> 
> Joe