Re: [multipathtcp] Consensus call on potential MPTCP proxy work

SungHoon Seo <sh.seo@kt.com> Tue, 25 April 2017 11:31 UTC

Return-Path: <sh.seo@kt.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 E253612EC01 for <multipathtcp@ietfa.amsl.com>; Tue, 25 Apr 2017 04:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 oxMOBvGFeyLI for <multipathtcp@ietfa.amsl.com>; Tue, 25 Apr 2017 04:31:07 -0700 (PDT)
Received: from smfilter2.kt.com (smfilter2.kt.com [14.63.245.209]) by ietfa.amsl.com (Postfix) with ESMTP id 7A24612EC13 for <multipathtcp@ietf.org>; Tue, 25 Apr 2017 04:31:05 -0700 (PDT)
Received: from external ([147.6.42.87]) by smfilter2.kt.com (1.0) id v3PBUEN0069A; Tue, 25 Apr 2017 20:30:14 +0900
Received: by KTEX2.localdomain (Postfix, from userid 600) id 3wC1GZ0Gjlz4KwV5; Tue, 25 Apr 2017 20:30:07 +0900 (KST)
Received: from MAIL-FRT-03.corp.ktad.kt.com (unknown [147.6.42.85]) by KTEX2.localdomain (Postfix) with ESMTP id 3wC1GR3Gxlz4KwV7; Tue, 25 Apr 2017 20:30:07 +0900 (KST)
Received: from MAIL-MBX-02.corp.ktad.kt.com ([10.215.33.72]) by MAIL-FRT-03.corp.ktad.kt.com ([10.215.33.53]) with mapi id 14.03.0210.002; Tue, 25 Apr 2017 20:30:07 +0900
From: SungHoon Seo <sh.seo@kt.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "lars@netapp.com" <lars@netapp.com>
CC: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] Consensus call on potential MPTCP proxy work
Thread-Index: AdK4HBNY1jXzvDFKRxmRsHBM53IcbgCSLSEA//9s2QCAAAMxgIAACAeAgAZN1wD//yIysA==
Date: Tue, 25 Apr 2017 11:30:05 +0000
Message-ID: <AAA2913CE97A474D937BF3C760E855A7608BCB05@MAIL-MBX-02>
References: <8c5ffa879686472594bfd3db2fa06076@rew09926dag03b.domain1.systemhost.net> <3F6DAF4F-87AD-411E-96A6-4FB52FF83F6D@netapp.com> <787AE7BB302AE849A7480A190F8B933009E51D3E@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <225E7ED6-F614-4216-BF01-1E6E30605A3B@netapp.com> <787AE7BB302AE849A7480A190F8B933009E51D65@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <fde4be28d9b6474bbde2d92c817dfecb@rew09926dag03b.domain1.systemhost.net>
In-Reply-To: <fde4be28d9b6474bbde2d92c817dfecb@rew09926dag03b.domain1.systemhost.net>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-dispnameaddress: sh.seo@kt.com
x-originating-ip: [10.214.73.222]
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/1geHI7vR99ms5jErEGa1quSgBBQ>
Subject: Re: [multipathtcp] Consensus call on potential MPTCP proxy work
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 25 Apr 2017 11:31:11 -0000

Hello~ Phil and WG,

I fully support this proxy work in the WG.

Use case with this proxy work may increase the usage of the MPTCP, since most of the existing servers do not have MPTCP capability.

Regards,
SungHoon

> -----Original Message-----
> From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of
> philip.eardley@bt.com
> Sent: Tuesday, April 25, 2017 4:12 PM
> To: mohamed.boucadair@orange.com; lars@netapp.com
> Cc: multipathtcp@ietf.org
> Subject: Re: [multipathtcp] Consensus call on potential MPTCP proxy work
>
> Just to clarify our interpretation of the various hums during the meeting.
>
> We interpreted them as indicating there was one topic that it was
> worthwhile doing a consensus call on. We did not interpret the hums as
> indicating clear consensus that we merely needed to confirm on the list.
>
> So far we see:
> In favour:
> christian.jacquenet@orange.com
> mohamed.boucadair@orange.com
> William Ivancic <ivancic@syzygyengineering.com>;
> Stefano Secci <stefano.secci@lip6.fr>;
> Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com>; David
> Allan I <david.i.allan@ericsson.com>; Markus.Brunner3@swisscom.com Robert
> Skog <robert.skog@ericsson.com>; Olivier Bonaventure
> <Olivier.Bonaventure@uclouvain.be>;
> Costin Raiciu <costin.raiciu@cs.pub.ro>;
>
> Against:
> Joe Touch <touch@isi.edu>;
> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>; Eggert, Lars
> <lars@netapp.com>;
>
>
> It is therefore important to hear views from other people. Of course it is
> also welcome for the technical discussion to continue (indeed, some people
> may want more of the technical discussion before giving their view on the
> consensus call).
>
> Thanks
> Phil & Yoshi
>
> -----Original Message-----
> From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
> Sent: 21 April 2017 07:55
>
> [cut]
>
> Lacking that information, I don't see a new element here that could lead
> to change the consensus reached at the Chicago meeting (of course I'm not
> entitled to do that call anyway).
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을 포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는 사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기 바랍니다.
This E-mail may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. If you receive this email by mistake, please either delete it without reproducing, distributing or retaining copies thereof or notify the sender immediately.