IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Thu, 20 July 2017 05:39 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 D20DE12783A; Wed, 19 Jul 2017 22:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 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, 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 k5m1KJ2MEoQH; Wed, 19 Jul 2017 22:39:05 -0700 (PDT)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A732126B6E; Wed, 19 Jul 2017 22:39:05 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id CBF5640522; Thu, 20 Jul 2017 07:39:03 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 7ECBA1C00B1; Thu, 20 Jul 2017 07:39:03 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%18]) with mapi id 14.03.0352.000; Thu, 20 Jul 2017 07:39:03 +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: AQHTAMej/WwR69lLRUy6PvQRGBZ9W6JcMrmw
Date: Thu, 20 Jul 2017 05:39:03 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A00F6A7@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> <aa347f86-6be0-57b4-cd84-628eeaab6261@isi.edu> <787AE7BB302AE849A7480A190F8B93300A00F3B9@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <45768767-79b5-42bf-6d2b-fe3a9799ef57@isi.edu>
In-Reply-To: <45768767-79b5-42bf-6d2b-fe3a9799ef57@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/cF64WvlojDeYAyIkhVNXBICpbsY>
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:39:07 -0000

Hi Joe, 

The text can always be worked out. This is not an IETF LC :)

The main point is that we are following your suggestion to define the solution as an application proxy using a dedicated port number. 

Cheers,
Med

> -----Message d'origine-----
> De : Joe Touch [mailto:touch@isi.edu]
> Envoyé : mercredi 19 juillet 2017 21:46
> À : BOUCADAIR Mohamed IMT/OLN; Olivier Bonaventure; Internet Area; tsv-
> area@ietf.org
> Objet : Re: [Int-area] Middleboxes to aid the deployment of MPTCP
> 
> 
> 
> On 7/19/2017 11:43 AM, mohamed.boucadair@orange.com wrote:
> > I don't understand your argument here, especially because you are the
> one who proposed me the following (check mptcp archives, April 20, 2017)
> which we endorsed in the latest version of the specification:
> >
> > "If that were the case, you'd simply be defining a new application
> service and asking for a TCP port number."
> >
> > Are you saying that you suggested us a bad design choice?
> The text I saw talks about SYN packets.
> 
> If this is at the application layer - and doesn't hijack TCP connections
> to other IP addresses - then it's fine, but then the ID is very badly in
> need of revision. I'm working off the text I saw.
> 
> Joe

v2.23.0 | Report a Bug | By Email