IETF Logo Mail Archive

Re: [multipathtcp] towards a potential work item on two-ended proxy

"Henderickx, Wim (Nokia - BE)" <wim.henderickx@nokia.com> Tue, 02 August 2016 04:19 UTC

Return-Path: <wim.henderickx@nokia.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 6B80912D119 for <multipathtcp@ietfa.amsl.com>; Mon, 1 Aug 2016 21:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level:
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 iGWZ2AuomyK8 for <multipathtcp@ietfa.amsl.com>; Mon, 1 Aug 2016 21:18:58 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D0E412D090 for <multipathtcp@ietf.org>; Mon, 1 Aug 2016 21:18:58 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id B77716ACA7B29; Tue, 2 Aug 2016 04:18:55 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u724ItJC010036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Aug 2016 04:18:56 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u724HniD010127 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Aug 2016 06:18:55 +0200
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.82]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Tue, 2 Aug 2016 06:17:50 +0200
From: "Henderickx, Wim (Nokia - BE)" <wim.henderickx@nokia.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Thread-Topic: [multipathtcp] towards a potential work item on two-ended proxy
Thread-Index: AQHR6/78+H5KVobs2E61DPJLQEiUPaA0T3oAgAAn1gCAAHgigIAAIjiA
Date: Tue, 02 Aug 2016 04:17:50 +0000
Message-ID: <2D90975F-061E-4565-8C45-53FDA5021D6A@nokia.com>
References: <b779dd12f1bb412c96c800eddaaf0247@rew09926dag03b.domain1.systemhost.net> <e2aa6ac517194af4b8c25c07f8e469fb@rew09926dag03b.domain1.systemhost.net> <9cafc779-502e-cc7f-676c-f6659e207c81@uclouvain.be> <3100ff74-0c7d-1815-03a1-aa4cec36d1e4@oracle.com> <3D8D4118-39CA-46A6-BFBD-026376C02058@nokia.com> <811b2c78-0976-6994-d759-8cac5fa58864@oracle.com> <0084773F-53E5-41A4-A244-430DAF12322A@nokia.com> <CAO249ycGiQyHy4qoKupE=NkFcSuLrPs3Bu2ie_5xtwogSSPJCw@mail.gmail.com>
In-Reply-To: <CAO249ycGiQyHy4qoKupE=NkFcSuLrPs3Bu2ie_5xtwogSSPJCw@mail.gmail.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.151008
x-originating-ip: [135.239.27.39]
Content-Type: multipart/alternative; boundary="_000_2D90975F061E45658C4553FDA5021D6Anokiacom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/H187jUIDaRnO53LJfbtwuiMMVEM>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] towards a potential work item on two-ended proxy
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: Tue, 02 Aug 2016 04:19:00 -0000


From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp<mailto:nishida@sfc.wide.ad.jp>>
Date: Tuesday 2 August 2016 at 06:15
To: Wim Henderickx <wim.henderickx@nokia.com<mailto:wim.henderickx@nokia.com>>
Cc: Rao Shoaib <rao.shoaib@oracle.com<mailto:rao.shoaib@oracle.com>>, "multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>" <multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>>
Subject: Re: [multipathtcp] towards a potential work item on two-ended proxy

Hello,

On Mon, Aug 1, 2016 at 12:05 PM, Henderickx, Wim (Nokia - BE) <wim.henderickx@nokia.com<mailto:wim.henderickx@nokia.com>> wrote:

>>> Since we seem to be only considering TCP, will the protocol field be
>>> removed from the draft ?
>> WH> this is to be discussed
>It has to be or we are allowing protocol encapsulation. In which case we
>need to define the complete mechanism.
WH> I would agree to that

Just in case, I might want to clarify this won't be encapsulation since I think what plain-mode does is protocol conversion.
My concern is protocol conversions between mptcp-tcp and mptcp-udp might be very different. Also, if we try to support other protocols, we might need other conversion rules.

WH> or we can call it protocol mapping or so.

Thanks,
--
Yoshi

v2.23.0 | Report a Bug | By Email