IETF Logo Mail Archive

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

"Meyer, Ullrich, Vodafone DE" <ullrich.meyer@vodafone.com> Fri, 28 April 2017 12:35 UTC

Return-Path: <ullrich.meyer@vodafone.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 44CA912EA7A for <multipathtcp@ietfa.amsl.com>; Fri, 28 Apr 2017 05:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level:
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_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 Cw8_fSQOLq7g for <multipathtcp@ietfa.amsl.com>; Fri, 28 Apr 2017 05:34:48 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.151]) (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 AF7B7129B22 for <multipathtcp@ietf.org>; Fri, 28 Apr 2017 05:31:23 -0700 (PDT)
Received: from [85.158.139.163] by server-15.bemta-5.messagelabs.com id 58/2E-01730-A1633095; Fri, 28 Apr 2017 12:31:22 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMKsWRWlGSWpSXmKPExsWi75nTpStmxhx pcPmPqMWL1z0sFp9XX2ezWLZ2BaMDs0fbl8lMHkuW/GTymPHpC1sAcxRrZl5SfkUCa8bh7x4F K3IrJm4+z9jAeD6zi5GLQ0hgO6NE17lXzF2MnEDOYUaJ9QsVIRJA9vE1/5khnE2MEm8/LmYFq WITcJA4+ughWIeIQKTElLk32UBsZoFUifX7msBqhAU8JL6+fM4KUeMp8enVXcYuRg4gO0zi4S FnkDCLgKrEjQ27WUBsXoFQiY8vrrJD7WKW6Dg1BWwmJ1Ci+XQjWBGjgKzEhg3nmSF2iUtsevY dbL6EgIjEw4un2SBsUYmXj/+xggxiFpjPKLFoKkQRr4CgxMmZT1hAjhASUJc4P9VhAqPoLCSj ZiFrmYWkBaJIX+LyvrOsELa2xLKFr5khbGuJGb8OskHYihJTuh+yQ9imEq+PfmRcwMixilG9O LWoLLVI10QvqSgzPaMkNzEzR9fQwFQvN7W4ODE9NScxqVgvOT93EyMwchmAYAfjrT7nQ4ySHE xKorylrMyRQnxJ+SmVGYnFGfFFpTmpxYcYZTg4lCR4RUyBcoJFqempFWmZOcAUApOW4OBREuH NA0nzFhck5hZnpkOkTjEqSonzRoMkBEASGaV5cG2wtHWJUVZKmJcR6BAhnoLUotzMElT5V4zi HIxKwrxMIFN4MvNK4Ka/AlrMBLSYxYUBZHFJIkJKqoFRjLHu5I1ZVSfyPtxWsZIvm9+rcv+Iv qKTfP6WMEWlK+E7jFIVr09ZpR292JCNQ780rfGq9/nfK75U2sczdDi6PF72iH/7CwbDs5y/XV bMUlrZGC7YY8GtVCb359r0N7unGvyOU+jIixE/7s909HBk1t9ZCe/P2/gkfe541h1puU5G8o2 SiYASS3FGoqEWc1FxIgC1KGKLVgMAAA==
X-Env-Sender: ullrich.meyer@vodafone.com
X-Msg-Ref: server-15.tower-188.messagelabs.com!1493382664!104963964!10
X-Originating-IP: [47.73.108.138]
X-StarScan-Received:
X-StarScan-Version: 9.4.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7908 invoked from network); 28 Apr 2017 12:31:18 -0000
Received: from vgdpm12vr.vodafone.com (HELO voxe02hw.internal.vodafone.com) (47.73.108.138) by server-15.tower-188.messagelabs.com with AES256-SHA256 encrypted SMTP; 28 Apr 2017 12:31:18 -0000
Received: from VOEXH10W.internal.vodafone.com (47.73.211.214) by edge1.vodafone.com (195.232.244.47) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 28 Apr 2017 14:31:03 +0200
Received: from VOEXC06W.internal.vodafone.com (145.230.101.26) by VOEXH10W.internal.vodafone.com (47.73.211.208) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 28 Apr 2017 14:31:03 +0200
Received: from VOEXC12W.internal.vodafone.com (145.230.101.14) by VOEXC06W.internal.vodafone.com (145.230.101.26) with Microsoft SMTP Server (TLS) id 14.3.294.0; Fri, 28 Apr 2017 14:31:03 +0200
Received: from VOEXM20W.internal.vodafone.com ([169.254.4.88]) by voexc12w.internal.vodafone.com ([145.230.101.14]) with mapi id 14.03.0294.000; Fri, 28 Apr 2017 14:31:01 +0200
From: "Meyer, Ullrich, Vodafone DE" <ullrich.meyer@vodafone.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "lars@netapp.com" <lars@netapp.com>
CC: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "philip.eardley@bt.com" <philip.eardley@bt.com>
Thread-Topic: [multipathtcp] Consensus call on potential MPTCP proxy work
Thread-Index: AdK4HBNYFYN3Pf6Ey0Kw29UUSw2QvQCSLSEA///y9gCAAAMwgIAACAeA//mir4D/7jX7gA==
Date: Fri, 28 Apr 2017 12:31:01 +0000
Message-ID: <378851B30BE1AA4E85FFD1FAFE10ABE6A7272049@VOEXM20W.internal.vodafone.com>
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: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="2.16.840.1.101.3.4.2.1"; boundary="----=_NextPart_000_0084_01D2C02C.0E7CF550"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/akNWTZNEN0IWz6HPdRpaXduaPEY>
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 12:35:01 -0000

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).

v2.23.0 | Report a Bug | By Email