IETF Logo Mail Archive

Re: [Int-area] Middleboxes to aid the deployment of MPTCP

<mohamed.boucadair@orange.com> Thu, 20 July 2017 05:43 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF01124D85; Wed, 19 Jul 2017 22:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level:
X-Spam-Status: No, score=-5.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 oZvvwO5G3uKn; Wed, 19 Jul 2017 22:43:52 -0700 (PDT)
Received: from relais-inet.orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FE82124217; Wed, 19 Jul 2017 22:43:52 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id AF329C0503; Thu, 20 Jul 2017 07:43:50 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.60]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 76D6F1A00C4; Thu, 20 Jul 2017 07:43:50 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0352.000; Thu, 20 Jul 2017 07:43:50 +0200
From: mohamed.boucadair@orange.com
To: Joe Touch <touch@isi.edu>, Olivier Bonaventure <olivier.bonaventure@tessares.net>, Internet Area <int-area@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Thread-Topic: [Int-area] Middleboxes to aid the deployment of MPTCP
Thread-Index: AQHTAMZ+/WwR69lLRUy6PvQRGBZ9W6JbbJyAgAABRICAAAGgAIAAw/oQ
Date: Thu, 20 Jul 2017 05:43:49 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A00F6BD@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <fe384d2b-a0ba-9444-2ee9-cd0de6d24b7c@tessares.net> <61608b70-6861-e7f8-96de-5679718a9680@isi.edu> <0174561d-9baf-13e7-06a4-a8f843c3621f@tessares.net> <608a81e9-f61c-b0b2-646f-777e5f5937c9@isi.edu> <6a116785-51d2-6270-fb1f-10f9a2e64c31@tessares.net> <6977c9a1-19b8-0bf5-4396-3cc3d8385b57@isi.edu> <bab6cb75-946f-cb4b-e4e6-32f49a7ea8ae@tessares.net> <7b76a8de-d07e-a51d-28fc-f6d3e70b9f1c@isi.edu> <b6543473-fc83-d78a-31a4-7faee67b0c7d@tessares.net> <2ee957ad-757b-c457-f6ff-894a3d995149@isi.edu>
In-Reply-To: <2ee957ad-757b-c457-f6ff-894a3d995149@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.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Y2N44Po1lncxZAyH5kI9xOXlTeI>
Subject: Re: [Int-area] Middleboxes to aid the deployment of MPTCP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 05:43:54 -0000

Re-,

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Int-area [mailto:int-area-bounces@ietf.org] De la part de Joe Touch
> Envoyé : mercredi 19 juillet 2017 21:58
> À : Olivier Bonaventure; Internet Area; tsv-area@ietf.org
> Objet : Re: [Int-area] Middleboxes to aid the deployment of MPTCP
> 
> 
> 
> On 7/19/2017 12:51 PM, Olivier Bonaventure wrote:
> > Joe,
> >>>>
> >>>> On 7/19/2017 12:41 AM, Olivier Bonaventure wrote:
> >>>>>> - IMO, TCP always needs to be able to fall back (which should be
> >>>>>> true now)
> >>>>>
> >>>>> This is not a concern with the proposed design
> >>>> Prove that is true if/when TCP-AO is enabled.
> >>>
> >>> I don't think that TCP-AO is a use case for the proposed converters.
> >>
> >> You don't get to decide that. If you use TCP, then TCP-AO could be
> >> enabled on the client.
> >
> > The converter is not intended to be used for all TCP connections. In
> > the draft we explain how an MPTCP endpoint can bypass the converter if
> > the destination server supports MPTCP. For TCP-AO, my recommendation
> > would be that the default policy of the client would be to never use
> > the converter if TCP-AO is requested by the application.
> 
> How do you know you're using the converter?

[Med] The converter is explicilty configured (e.g., locally configured or y means of https://tools.ietf.org/html/draft-boucadair-mptcp-dhc-07). 

 Is the initial connection to
> that converter?

[Med] When a connection is eligible to network-assisted MPTCP, the first subflow will be established via the converter. Subsequent flows will be established with that proxy involved. Packets are sent with destination IP address set to the one of the converter. 

 Or does the converter hijack (the latter is the
> implication of the text, AFAICT).
> 
> Joe
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

v2.23.0 | Report a Bug | By Email