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

"Henderickx, Wim (Nokia - BE)" <wim.henderickx@nokia.com> Mon, 01 August 2016 19:05 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 ABEAF12D14D for <multipathtcp@ietfa.amsl.com>; Mon, 1 Aug 2016 12:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ERyrL8GRa5d2 for <multipathtcp@ietfa.amsl.com>; Mon, 1 Aug 2016 12:05:26 -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 BE62612B065 for <multipathtcp@ietf.org>; Mon, 1 Aug 2016 12:05:26 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 6138195DAA7DC; Mon, 1 Aug 2016 19:05:21 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u71J5Ov7030987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 Aug 2016 19:05:24 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u71J5Nb8027271 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Aug 2016 21:05:24 +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; Mon, 1 Aug 2016 21:05:23 +0200
From: "Henderickx, Wim (Nokia - BE)" <wim.henderickx@nokia.com>
To: Rao Shoaib <rao.shoaib@oracle.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] towards a potential work item on two-ended proxy
Thread-Index: AQHR6/78+H5KVobs2E61DPJLQEiUPaA0T3oAgAAn1gA=
Date: Mon, 1 Aug 2016 19:05:22 +0000
Message-ID: <0084773F-53E5-41A4-A244-430DAF12322A@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>
In-Reply-To: <811b2c78-0976-6994-d759-8cac5fa58864@oracle.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.40]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4F61DB95A4C84B4595406D7DCE7A8392@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/k6MPz8oq9pV8ZokMgao4VMNQm3w>
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: Mon, 01 Aug 2016 19:05:28 -0000





On 01/08/16 20:42, "Rao Shoaib" <rao.shoaib@oracle.com> wrote:

>
>
>On 08/01/2016 07:13 AM, Henderickx, Wim (Nokia - BE) wrote:
>>
>>
>>
>>
>>
>>> Why is it necessary to know that the connection has been proxied ?
>> WH> Otherwise the concentrator will perform the proxy function although the destination is the application server.
>> So assume an E2E MPTCP flow. The UE initiates it and the element with the network assisted MPTCP proxy (Concentrator) receives it. The concentrator should not proxy this flow. It should only act upon MPTCP flow that should be proxied in network assisted mode. This is the reason we need an indication about this
>This seems like a deployment issue not a protocol issue. The decision to 
>proxy or not proxy should be based on the IP addresses or out of band 
>signaling. After all the entity adding the option some how knows to add 
>the option.
>
>I liked the initial proposal as it did not require any changes to the 
>protocol. These change (as I have said before) seem very deployment 
>specific and IMHO should not be part of the protocol.
WH> I would disagree since you don’t always control the addressing and it is better to have an explicit signaling in the protocol what to expect to happen.
>>>> In the plain-mode, the HAG does not need to be on the path to/from the
>>>> client. The plain-mode option is used to signal the original
>>>> source/destination address of the connection depending on the usage.
>>> 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
>
>Rao
>>> Shoaib
>>>>
>>>>
>>>>
>>>> Olivier
>>>>
>>>> _______________________________________________
>>>> multipathtcp mailing list
>>>> multipathtcp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>> _______________________________________________
>>> multipathtcp mailing list
>>> multipathtcp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>