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

Joe Touch <touch@isi.edu> Fri, 28 April 2017 15:50 UTC

Return-Path: <touch@isi.edu>
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 608BE1293F2 for <multipathtcp@ietfa.amsl.com>; Fri, 28 Apr 2017 08:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 nEjl59yH8mCG for <multipathtcp@ietfa.amsl.com>; Fri, 28 Apr 2017 08:50:03 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6FBC128CDC for <multipathtcp@ietf.org>; Fri, 28 Apr 2017 08:46:54 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3SFkT4N024944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 28 Apr 2017 08:46:30 -0700 (PDT)
To: "Meyer, Ullrich, Vodafone DE" <ullrich.meyer@vodafone.com>, "philip.eardley@bt.com" <philip.eardley@bt.com>, "lars@netapp.com" <lars@netapp.com>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
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> <378851B30BE1AA4E85FFD1FAFE10ABE6A7272049@VOEXM20W.internal.vodafone.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <4cebc0e9-fc76-46e1-f00e-15c8cce1d798@isi.edu>
Date: Fri, 28 Apr 2017 08:46:28 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <378851B30BE1AA4E85FFD1FAFE10ABE6A7272049@VOEXM20W.internal.vodafone.com>
Content-Type: multipart/alternative; boundary="------------5BBFDA42D34686B40DDB7287"
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/zI2R6utoTzJcedNntK-I6CjgwGM>
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: Fri, 28 Apr 2017 15:50:06 -0000

Ullrich,

FYI - the IETF is a place for individual expression, not corporate
endorsement.

So you, individually, support this work. Nothing else.

Joe


On 4/28/2017 5:31 AM, Meyer, Ullrich, Vodafone DE wrote:
> Dear all,
>
> herewith I want to declare very clearly our (Vodafone) interest on that
> MPTCP proxy work within the IETF. The work has our plenary support.
>
> Kind regards,
>
> Ullrich Meyer 
> Senior Engineer Service Design
> VPN Solution Engineering within
> Group Network Engineering and Delivery
> FixLine: +49 69 2169 3290
> Mobile: +49 172 190 3120
> Email: ullrich.meyer@vodafone.com
>
> Vodafone GmbH, Düsseldorfer Straße 15, 65760 Eschborn
> vodafone-deutschland.de 
>
> Die gesetzlichen Pflichtangaben finden Sie unter
> www.vodafone.de/pflichtangaben 
>
>
> -----Ursprüngliche Nachricht-----
> Von: philip.eardley@bt.com [mailto:philip.eardley@bt.com] 
> Gesendet: Dienstag, 25. April 2017 09:12
> An: BOUCADAIR Mohamed IMT/OLN <mohamed.boucadair@orange.com>;;
> lars@netapp.com
> Cc: multipathtcp@ietf.org
> Betreff: 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