IETF Logo Mail Archive

Re: [tcpm] Updated version of draft-ietf-tcpm-converters-05

<mohamed.boucadair@orange.com> Fri, 15 March 2019 07:28 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4EE1311F9 for <tcpm@ietfa.amsl.com>; Fri, 15 Mar 2019 00:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 JIqvwSjGM77E for <tcpm@ietfa.amsl.com>; Fri, 15 Mar 2019 00:28:39 -0700 (PDT)
Received: from orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADD6127987 for <tcpm@ietf.org>; Fri, 15 Mar 2019 00:28:39 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 44LHHp0H6qz8tZm; Fri, 15 Mar 2019 08:28:38 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.38]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 44LHHn6jN3z3wbD; Fri, 15 Mar 2019 08:28:37 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM5C.corporate.adroot.infra.ftgroup ([fe80::393d:418c:3f1d:991d%21]) with mapi id 14.03.0439.000; Fri, 15 Mar 2019 08:28:37 +0100
From: mohamed.boucadair@orange.com
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
CC: "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: [tcpm] Updated version of draft-ietf-tcpm-converters-05
Thread-Index: AQHU2vlApo0NOiqnkki5WmPF1laDg6YMSyrw
Date: Fri, 15 Mar 2019 07:28:37 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA3E51E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <9DD59801-36CE-407E-98F0-0BB1AAD514A7@tessares.net> <CAO249yc-eHAnOR7XfemQyJB+UVjmdtt43oZs+xJa=inZBBgp2w@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA2273F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAO249ycs3grfmcaVJem-swoAWMAU_boOc5csY-ZjWn5S8m0F5w@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA23CC3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <787AE7BB302AE849A7480A190F8B93302EA24AC5@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAO249yeALw7PJnKxkLVMr2q4-qeB_-fMwc7HW+3f-mX-s+RQag@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA25443@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAO249ydNzjkpxogU+1RNY-_aOa6XGMu7J-zmfv0NGcjFF3u9Ag@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA25F47@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAO249yd5KTOC8Y3xCpTHfqwWpg80nM_hV9ADkPNMKFxqeUvpFg@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93302EA27F2F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAO249yejJmSpzQM0UQzQq2FwOXxMQ3ynzQA_T1RUoSve7MebFA@mail.gmail.com>
In-Reply-To: <CAO249yejJmSpzQM0UQzQq2FwOXxMQ3ynzQA_T1RUoSve7MebFA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302EA3E51EOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/fJRKvWyuFHOY2JCCywDYj1P7DRM>
Subject: Re: [tcpm] Updated version of draft-ietf-tcpm-converters-05
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2019 07:28:42 -0000

Hi Yoshi,

Great!

Thank you for double checking.

Cheers,
Med

De : Yoshifumi Nishida [mailto:nishida@sfc.wide.ad.jp]
Envoyé : vendredi 15 mars 2019 07:35
À : BOUCADAIR Mohamed TGI/OLN
Cc : Yoshifumi Nishida; tcpm@ietf.org
Objet : Re: [tcpm] Updated version of draft-ietf-tcpm-converters-05

Hi Med,

On Mon, Mar 4, 2019 at 7:21 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Yoshi,

“I don't think this is always true.
If mptcp client uses multiple subflows for the mptcp connection, how does it looks to the server?
I believe it should be a single connection on the serve side.”

The server will always see the same source address/port.

“But, this means when you convert mptcp into tcp, you'll need to merge multiple TCP connections into a single TCP connection.”

The glue is done at the TCP level by the converter.

“This merging process will not be very easy when TLS are used for subflows.”

Why? I think the disconnect is that you seem to imply that data from various segments are multiplexed in the same segment upstream.


Sorry for my slow response. I did some small experiments to examine this and took some time to setup.
After I've checked, I've found the concept of the converter can work properly with TLS.
I'm sorry for the confusion. I am now fine with the current statement on this point.
--
Yoshi

v2.23.0 | Report a Bug | By Email