
From nobody Thu Mar  5 00:21:20 2015
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 959D41B2A65 for <multipathtcp@ietfa.amsl.com>; Thu,  5 Mar 2015 00:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 kj-0fNCrZFzN for <multipathtcp@ietfa.amsl.com>; Thu,  5 Mar 2015 00:21:16 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E7121B2A30 for <multipathtcp@ietf.org>; Thu,  5 Mar 2015 00:21:16 -0800 (PST)
Received: from EVMHT61-UKRD.domain1.systemhost.net (10.36.3.127) by RDW083A005ED61.bt.com (10.187.98.10) with Microsoft SMTP Server (TLS) id 14.3.181.6; Thu, 5 Mar 2015 08:21:17 +0000
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.146]) by EVMHT61-UKRD.domain1.systemhost.net ([10.36.3.127]) with mapi; Thu, 5 Mar 2015 08:21:14 +0000
From: <philip.eardley@bt.com>
To: <nishida@sfc.wide.ad.jp>, <multipathtcp@ietf.org>
Date: Thu, 5 Mar 2015 08:21:13 +0000
Thread-Topic: [multipathtcp] Agenda for dallas meeting
Thread-Index: AdBPNBHYXHacVIBFQKemN4FPyMwfPQH6Ss+Q
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18@EMV67-UKRD.domain1.systemhost.net>
References: <CAO249ydcUPVU4nD7bzeoxsePhqRowu1RzB5JAfkdMkVDi1-cKw@mail.gmail.com>
In-Reply-To: <CAO249ydcUPVU4nD7bzeoxsePhqRowu1RzB5JAfkdMkVDi1-cKw@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18EMV67UKRDdoma_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/zT9L7Pnu910TGMDdp7ntA-40XGk>
Subject: Re: [multipathtcp] Agenda for dallas meeting
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 05 Mar 2015 08:21:18 -0000

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18EMV67UKRDdoma_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UGxlYXNlIGxldCB1cyBrbm93IGFib3V0IGFueXRoaW5nIHlvdSB3YW50IHRvIHByZXNlbnQgb3Ig
ZGlzY3VzcyBkdXJpbmcgdGhlIG1lZXRpbmcuDQpUaGFua3MNClBoaWwgJiBZb3NoaQ0KDQpGcm9t
OiBtdWx0aXBhdGh0Y3AgW21haWx0bzptdWx0aXBhdGh0Y3AtYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIFlvc2hpZnVtaSBOaXNoaWRhDQpTZW50OiAyMyBGZWJydWFyeSAyMDE1IDA2OjQ0
DQpUbzogbXVsdGlwYXRodGNwDQpTdWJqZWN0OiBbbXVsdGlwYXRodGNwXSBBZ2VuZGEgZm9yIGRh
bGxhcyBtZWV0aW5nDQoNCkhlbGxvLA0KDQpBY2NvcmRpbmcgdG8gdGhlIGN1cnJlbnQgcHJlbGlt
aW5hcnkgYWdlbmRhIChodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcvOTIvYWdl
bmRhLmh0bWwpLCB3ZSB3aWxsIGhhdmUgdGhlIGZvbGxvd2luZyB0aGUgc2xvdCBhdCB0aGUgRGFs
bGFzIG1lZXRpbmcuDQoNCiAgICAgRGF0ZTogIFR1ZXNkYXksIE1hcmNoIDI0LCAyMDE1LCAxMzow
MCAtIDE1OjAwIChBZnRlcm5vb24gU2Vzc2lvbiBJKQ0KICAgICBSb29tOiBGYXIgRWFzdA0KDQpJ
ZiB5b3UncmUgcGxhbm5pbmcgdG8gcHJlc2VudCBzb21ldGhpbmcsIHBsZWFzZSBwcm92aWRlIHVz
IHRoZSBmb2xsb3dpbmcgaW5mby4NCiAgIDE6IHByZXNlbnRlcidzIG5hbWUNCiAgIDI6IHRpdGxl
DQogICAzOiBsZW5ndGggb2YgdGhlIHByZXNlbnRhdGlvbg0KDQpUaGFua3MsDQotLQ0KWW9zaGkg
JiBQaGlsDQo=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18EMV67UKRDdoma_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw
YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7DQoJY29s
b3I6Ymx1ZTsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7DQoJdGV4
dC1kZWNvcmF0aW9uOm5vbmUgbm9uZTt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlw
ZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCW1z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYx
Mi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRp
di5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9
IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIx
IiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVhZD48Ym9keSBsYW5n
PUVOLUdCIGxpbms9Ymx1ZSB2bGluaz1wdXJwbGU+PGRpdiBjbGFzcz1Xb3JkU2VjdGlvbjE+PHAg
Y2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LWZhbWlseToiQXJpYWwiLCJzYW5zLXNl
cmlmIjtjb2xvcjpibHVlJz5QbGVhc2UgbGV0IHVzIGtub3cgYWJvdXQgYW55dGhpbmcgeW91IHdh
bnQgdG8gcHJlc2VudCBvciBkaXNjdXNzIGR1cmluZyB0aGUgbWVldGluZy4gPG86cD48L286cD48
L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1mYW1pbHk6IkFy
aWFsIiwic2Fucy1zZXJpZiI7Y29sb3I6Ymx1ZSc+VGhhbmtzPG86cD48L286cD48L3NwYW4+PC9w
PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1mYW1pbHk6IkFyaWFsIiwic2Fu
cy1zZXJpZiI7Y29sb3I6Ymx1ZSc+UGhpbCAmYW1wOyBZb3NoaTxvOnA+PC9vOnA+PC9zcGFuPjwv
cD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNh
bnMtc2VyaWYiO2NvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48ZGl2IHN0
eWxlPSdib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNt
IDBjbSAwY20gNC4wcHQnPjxkaXY+PGRpdiBzdHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20nPjxwIGNsYXNzPU1z
b05vcm1hbD48Yj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9
RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiJz4gbXVsdGlwYXRodGNwIFttYWlsdG86bXVsdGlwYXRodGNwLWJvdW5jZXNAaWV0Zi5v
cmddIDxiPk9uIEJlaGFsZiBPZiA8L2I+WW9zaGlmdW1pIE5pc2hpZGE8YnI+PGI+U2VudDo8L2I+
IDIzIEZlYnJ1YXJ5IDIwMTUgMDY6NDQ8YnI+PGI+VG86PC9iPiBtdWx0aXBhdGh0Y3A8YnI+PGI+
U3ViamVjdDo8L2I+IFttdWx0aXBhdGh0Y3BdIEFnZW5kYSBmb3IgZGFsbGFzIG1lZXRpbmc8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTAuMHB0Jz5IZWxsbyw8YnI+PGJyPkFjY29yZGluZyB0byB0aGUgY3VycmVudCBwcmVsaW1p
bmFyeSBhZ2VuZGEgKDwvc3Bhbj48YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L21lZXRpbmcvOTIvYWdlbmRhLmh0bWwiIHRhcmdldD0iX2JsYW5rIj48c3BhbiBzdHlsZT0nZm9u
dC1zaXplOjEwLjBwdCc+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzkyL2Fn
ZW5kYS5odG1sPC9zcGFuPjwvYT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdCc+KSwgd2Ug
d2lsbCBoYXZlIHRoZSZuYnNwO2ZvbGxvd2luZyB0aGUgc2xvdCBhdCB0aGUgRGFsbGFzJm5ic3A7
bWVldGluZy48YnI+PGJyPiZuYnNwOyAmbmJzcDsgJm5ic3A7RGF0ZTogJm5ic3A7VHVlc2RheSwg
TWFyY2ggMjQsIDIwMTUsIDEzOjAwIC0gMTU6MDAgKEFmdGVybm9vbiBTZXNzaW9uIEkpICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDs8YnI+Jm5ic3A7ICZuYnNwOyAmbmJzcDtSb29t
OiBGYXIgRWFzdDxicj48YnI+SWYgeW91J3JlIHBsYW5uaW5nIHRvIHByZXNlbnQgc29tZXRoaW5n
LCBwbGVhc2UgcHJvdmlkZSB1cyB0aGUgZm9sbG93aW5nIGluZm8uPGJyPiZuYnNwOyAmbmJzcDsx
OiBwcmVzZW50ZXIncyBuYW1lPGJyPiZuYnNwOyAmbmJzcDsyOiB0aXRsZTxicj4mbmJzcDsgJm5i
c3A7MzogbGVuZ3RoIG9mIHRoZSBwcmVzZW50YXRpb248YnI+PGJyPlRoYW5rcyw8YnI+LS08YnI+
WW9zaGkgJmFtcDsgUGhpbDwvc3Bhbj48bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Rpdj48L2Rpdj48
L2JvZHk+PC9odG1sPg==

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18EMV67UKRDdoma_--


From nobody Fri Mar  6 16:08:44 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2621A8770; Fri,  6 Mar 2015 16:08:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 m2Q4QOAb6zK5; Fri,  6 Mar 2015 16:08:39 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DED7C1A876A; Fri,  6 Mar 2015 16:08:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150307000839.13658.54778.idtracker@ietfa.amsl.com>
Date: Fri, 06 Mar 2015 16:08:39 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/qKxdD2tiusmcz-wvZNLZF4TNQPU>
Cc: multipathtcp@ietf.org
Subject: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-04.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 07 Mar 2015 00:08:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multipath TCP Working Group of the IETF.

        Title           : TCP Extensions for Multipath Operation with Multiple Addresses
        Authors         : Alan Ford
                          Costin Raiciu
                          Mark Handley
                          Olivier Bonaventure
	Filename        : draft-ietf-mptcp-rfc6824bis-04.txt
	Pages           : 67
	Date            : 2015-03-06

Abstract:
   TCP/IP communication is currently restricted to a single path per
   connection, yet multiple paths often exist between peers.  The
   simultaneous use of these multiple paths for a TCP/IP session would
   improve resource usage within the network and, thus, improve user
   experience through higher throughput and improved resilience to
   network failure.

   Multipath TCP provides the ability to simultaneously use multiple
   paths between peers.  This document presents a set of extensions to
   traditional TCP to support multipath operation.  The protocol offers
   the same type of service to applications as TCP (i.e., reliable
   bytestream), and it provides the components necessary to establish
   and use multiple TCP flows across potentially disjoint paths.

   This document obsoletes RFC6824 [5] through clarifications and
   modifications, primarily driven by deployment experience.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Mar  7 01:49:55 2015
Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E2141A8A5A for <multipathtcp@ietfa.amsl.com>; Sat,  7 Mar 2015 01:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 NHabrWq92HiD for <multipathtcp@ietfa.amsl.com>; Sat,  7 Mar 2015 01:49:51 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (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 204C21A8A73 for <multipathtcp@ietf.org>; Sat,  7 Mar 2015 01:49:51 -0800 (PST)
Received: by wibbs8 with SMTP id bs8so8823929wib.0 for <multipathtcp@ietf.org>; Sat, 07 Mar 2015 01:49:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=NdU0hqDMGRlx3qOajeJmaxYWBaT0AmBggLY8XIQygvc=; b=lPaYCkr8aGdXMSaRHYcrZWyzZ7fTGJUEu0t0gy1Atgvkymq+zyrvlvW42oP+VFbHaj HD1xE+fg1SL9/HnEiB+/pxbVTL+b5uNN3KP68OiN85h+9LB3a9EF1z+4sPHPnvjVvOyt urok7cjeJTUtJlbDqRUxxQGjwIzyd/JYCIUbgFd0XdauM80Mi7PVMmg0ahoIYj4+v/Jw QYYpuZw0ja623hMysG3Ffetzz0o/kgwF80sacWthkJkZgBa/2OpxmmGwPPC9DmQvU4zG mdW1DlxqrbGi6GUZP6WYUuR6nJ2ocAZJyyoU0Xrebxl+ZdJuz835Xrun1IPWBQ5np3Za g+4w==
X-Received: by 10.180.207.6 with SMTP id ls6mr85598277wic.13.1425721789985; Sat, 07 Mar 2015 01:49:49 -0800 (PST)
Received: from [192.168.0.11] (cpc5-acto4-2-0-cust918.4-2.cable.virginm.net. [86.13.119.151]) by mx.google.com with ESMTPSA id g5sm18666820wjr.19.2015.03.07.01.49.47 for <multipathtcp@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 07 Mar 2015 01:49:48 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <20150307000839.13658.54778.idtracker@ietfa.amsl.com>
Date: Sat, 7 Mar 2015 09:49:47 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCCA9F75-48D7-4C01-98DD-D9B5E3352E7F@gmail.com>
References: <20150307000839.13658.54778.idtracker@ietfa.amsl.com>
To: multipathtcp@ietf.org
X-Mailer: Apple Mail (2.1283)
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/_UQ67g1Hh0qsrLL4USouE1qtuYg>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-04.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 07 Mar 2015 09:49:53 -0000

Hi all,

This is a small rev, the only change being the introduction of the =
version handling logic as raised by Anumita.

Cheers,
Alan

On 7 Mar 2015, at 00:08, internet-drafts@ietf.org wrote:

>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Multipath TCP Working Group of the =
IETF.
>=20
>        Title           : TCP Extensions for Multipath Operation with =
Multiple Addresses
>        Authors         : Alan Ford
>                          Costin Raiciu
>                          Mark Handley
>                          Olivier Bonaventure
> 	Filename        : draft-ietf-mptcp-rfc6824bis-04.txt
> 	Pages           : 67
> 	Date            : 2015-03-06
>=20
> Abstract:
>   TCP/IP communication is currently restricted to a single path per
>   connection, yet multiple paths often exist between peers.  The
>   simultaneous use of these multiple paths for a TCP/IP session would
>   improve resource usage within the network and, thus, improve user
>   experience through higher throughput and improved resilience to
>   network failure.
>=20
>   Multipath TCP provides the ability to simultaneously use multiple
>   paths between peers.  This document presents a set of extensions to
>   traditional TCP to support multipath operation.  The protocol offers
>   the same type of service to applications as TCP (i.e., reliable
>   bytestream), and it provides the components necessary to establish
>   and use multiple TCP flows across potentially disjoint paths.
>=20
>   This document obsoletes RFC6824 [5] through clarifications and
>   modifications, primarily driven by deployment experience.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Sun Mar  8 12:57:45 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54F551A0111; Sun,  8 Mar 2015 12:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 AW-LwGfSEzdm; Sun,  8 Mar 2015 12:57:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4689A1A00D8; Sun,  8 Mar 2015 12:57:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150308195742.6975.95888.idtracker@ietfa.amsl.com>
Date: Sun, 08 Mar 2015 12:57:42 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/hYmV5brHAmemRFQooqNnowXyOnA>
Cc: multipathtcp@ietf.org
Subject: [multipathtcp] I-D Action: draft-ietf-mptcp-experience-01.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 08 Mar 2015 19:57:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multipath TCP Working Group of the IETF.

        Title           : Experience with Multipath TCP
        Authors         : Olivier Bonaventure
                          Christoph Paasch
                          Gregory Detal
	Filename        : draft-ietf-mptcp-experience-01.txt
	Pages           : 20
	Date            : 2015-03-08

Abstract:
   This document discusses operational experiences of using Multipath
   TCP in real world networks.  It lists several prominent use cases for
   which Multipath TCP has been considered and is being used.  It also
   gives insight in some heuristics and decisions that have helped to
   realize these use cases.  Further, it presents several open issues
   that are yet unclear on how they can be solved.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mptcp-experience/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mptcp-experience-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-experience-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Mar  9 01:00:50 2015
Return-Path: <weixinpeng@huawei.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06ABC1A1F02 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Mar 2015 01:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 JmwhE9zc955a for <multipathtcp@ietfa.amsl.com>; Mon,  9 Mar 2015 01:00:47 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 304B11A1EF7 for <multipathtcp@ietf.org>; Mon,  9 Mar 2015 01:00:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQA47223; Mon, 09 Mar 2015 08:00:45 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Mar 2015 08:00:44 +0000
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.160]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Mon, 9 Mar 2015 16:00:39 +0800
From: "Weixinpeng (Jackie)" <weixinpeng@huawei.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: New Version Notification for draft-wei-mptcp-proxy-mechanism-01.txt
Thread-Index: AQHQWj1v/hKgxo0/BES8ax1xDZAQMJ0Txo2g
Date: Mon, 9 Mar 2015 08:00:38 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46E321B46@nkgeml507-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.76.176]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/LBMSwz7au2ZbSYH43_z78Ril4_o>
Subject: [multipathtcp] FW: New Version Notification for draft-wei-mptcp-proxy-mechanism-01.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 09 Mar 2015 08:00:49 -0000

SGVsbG8gYWxsLA0KQSByZXZpc2VkIHZlcnNpb24gb2YgTVBUQ1AgcHJveHkgZHJhZnQgaGFzIGJl
ZW4gc3VibWl0dGVkLg0KDQpUaGFua3MuDQpYaW5wZW5nDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0
LWRyYWZ0c0BpZXRmLm9yZ10NCj5TZW50OiBNb25kYXksIE1hcmNoIDA5LCAyMDE1IDM6NDggUE0N
Cj5UbzogZWxvcGV6QGZvcnRpbmV0LmNvbTsgV2VpeGlucGVuZyAoSmFja2llKTsgRWR3YXJkIExv
cGV6OyBYaW9uZ2NodW5zaGFuDQo+KFNhbSk7IFdlaXhpbnBlbmcgKEphY2tpZSk7IFhpb25nY2h1
bnNoYW4gKFNhbSkNCj5TdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+ZHJh
ZnQtd2VpLW1wdGNwLXByb3h5LW1lY2hhbmlzbS0wMS50eHQNCj4NCj4NCj5BIG5ldyB2ZXJzaW9u
IG9mIEktRCwgZHJhZnQtd2VpLW1wdGNwLXByb3h5LW1lY2hhbmlzbS0wMS50eHQNCj5oYXMgYmVl
biBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFhpbnBlbmcgV2VpIGFuZCBwb3N0ZWQgdG8gdGhl
IElFVEYNCj5yZXBvc2l0b3J5Lg0KPg0KPk5hbWU6CQlkcmFmdC13ZWktbXB0Y3AtcHJveHktbWVj
aGFuaXNtDQo+UmV2aXNpb246CTAxDQo+VGl0bGU6CQlNUFRDUCBwcm94eSBtZWNoYW5pc21zDQo+
RG9jdW1lbnQgZGF0ZToJMjAxNS0wMy0wOQ0KPkdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9u
DQo+UGFnZXM6CQkxMQ0KPlVSTDoNCj5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC13ZWktbXB0Y3AtcHJveHktbWVjaGFuaXNtLTAxLnR4dCANCj5TdGF0dXM6DQo+aHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtd2VpLW1wdGNwLXByb3h5LW1lY2hh
bmlzbS8NCj5IdG1saXplZDoNCj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC13ZWkt
bXB0Y3AtcHJveHktbWVjaGFuaXNtLTAxDQo+RGlmZjoNCj5odHRwOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC13ZWktbXB0Y3AtcHJveHktbWVjaGFuaXNtLTAxDQo+DQo+QWJzdHJh
Y3Q6DQo+ICAgTXVsdGlwYXRoIFRDUCBwcm92aWRlcyB0aGUgYWJpbGl0eSB0byBzaW11bHRhbmVv
dXNseSB1c2UgbXVsdGlwbGUNCj4gICBwYXRocyBiZXR3ZWVuIHBlZXJzIGZvciBhIFRDUC9JUCBz
ZXNzaW9uLCBhbmQgaXQgY291bGQgaW1wcm92ZQ0KPiAgIHJlc291cmNlIHVzYWdlIHdpdGhpbiB0
aGUgbmV0d29yayBhbmQsIHRodXMsIGltcHJvdmUgdXNlciBleHBlcmllbmNlDQo+ICAgdGhyb3Vn
aCBoaWdoZXIgdGhyb3VnaHB1dCBhbmQgaW1wcm92ZWQgcmVzaWxpZW5jZSB0byBuZXR3b3JrIGZh
aWx1cmUuDQo+ICAgVGhpcyBkb2N1bWVudCBkaXNjdXNzZXMgdGhlIG1lY2hhbmlzbSBvZiBhIG5l
dyBuZXR3b3JrIGVudGl0eSwgbmFtZWQNCj4gICBNUFRDUCBwcm94eSwgd2hpY2ggaXMgYWltZWQg
dG8gYXNzaXN0IE1QVENQIGNhcGFibGUgcGVlciB0byB1c2UgTVBUQ1ANCj4gICBzZXNzaW9uIGlu
IGNhc2Ugb2Ygb25lIG9mIHRoZSBwZWVycyBub3QgYmVpbmcgTVBUQ1AgY2FwYWJsZSBvciB0byBh
Y3QNCj4gICBhcyBhbiBhZ2dyZWdhdGlvbiBwb2ludCBmb3Igc3VibGZvd3MuDQo+DQo+DQo+DQo+
DQo+DQo+UGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZy
b20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KPnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFu
ZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+DQo+VGhlIElFVEYgU2Vj
cmV0YXJpYXQNCg0K


From nobody Tue Mar 10 23:31:03 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF10A1A1AB2 for <multipathtcp@ietfa.amsl.com>; Tue, 10 Mar 2015 23:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.221
X-Spam-Level: *
X-Spam-Status: No, score=1.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 3w4JaD4HBTRF for <multipathtcp@ietfa.amsl.com>; Tue, 10 Mar 2015 23:31:00 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B35501A1AA1 for <multipathtcp@ietf.org>; Tue, 10 Mar 2015 23:31:00 -0700 (PDT)
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 3E7DF278103 for <multipathtcp@ietf.org>; Wed, 11 Mar 2015 15:30:58 +0900 (JST)
Received: by widem10 with SMTP id em10so8862088wid.2 for <multipathtcp@ietf.org>; Tue, 10 Mar 2015 23:30:55 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.222.197 with SMTP id qo5mr73515119wjc.142.1426055455955;  Tue, 10 Mar 2015 23:30:55 -0700 (PDT)
Received: by 10.194.41.167 with HTTP; Tue, 10 Mar 2015 23:30:55 -0700 (PDT)
In-Reply-To: <A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18@EMV67-UKRD.domain1.systemhost.net>
References: <CAO249ydcUPVU4nD7bzeoxsePhqRowu1RzB5JAfkdMkVDi1-cKw@mail.gmail.com> <A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18@EMV67-UKRD.domain1.systemhost.net>
Date: Tue, 10 Mar 2015 23:30:55 -0700
Message-ID: <CAO249yc3i7NiA3RdDhuqxDCkaVvxDitweqrp-oXSUt4s6cydOA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: "philip.eardley" <philip.eardley@bt.com>
Content-Type: multipart/alternative; boundary=001a11c3a99ae1e35b0510fd6895
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/bG3Ked_bzgQODFclXSBMNBJiT2c>
Cc: multipathtcp <multipathtcp@ietf.org>, Martin Stiemerling <mls.ietf@gmail.com>
Subject: Re: [multipathtcp] Agenda for dallas meeting
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Mar 2015 06:31:02 -0000

--001a11c3a99ae1e35b0510fd6895
Content-Type: text/plain; charset=UTF-8

Hi folks,

We start thinking about returning a slot for dallas meeting as we haven't
received a request so far.
Also, we have to apologize to people that both of co-chairs won't be able
to come to Dallas. But, if we have a meeting, we will find someone to take
care of it and we will try to join from remote as much as possible.
if someone has opinions or suggestions (or complaints..), please let us
hear.

Regards,
--
Yoshi & Phil

On Thu, Mar 5, 2015 at 12:21 AM, <philip.eardley@bt.com> wrote:

> Please let us know about anything you want to present or discuss during
> the meeting.
>
> Thanks
>
> Phil & Yoshi
>
>
>
> *From:* multipathtcp [mailto:multipathtcp-bounces@ietf.org] *On Behalf Of
> *Yoshifumi Nishida
> *Sent:* 23 February 2015 06:44
> *To:* multipathtcp
> *Subject:* [multipathtcp] Agenda for dallas meeting
>
>
>
> Hello,
>
> According to the current preliminary agenda (
> https://datatracker.ietf.org/meeting/92/agenda.html), we will have
> the following the slot at the Dallas meeting.
>
>      Date:  Tuesday, March 24, 2015, 13:00 - 15:00 (Afternoon Session I)
>
>      Room: Far East
>
> If you're planning to present something, please provide us the following
> info.
>    1: presenter's name
>    2: title
>    3: length of the presentation
>
> Thanks,
> --
> Yoshi & Phil
>

--001a11c3a99ae1e35b0510fd6895
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi folks,<div><br></div><div>We start thinking about retur=
ning a slot for dallas meeting as we haven&#39;t received a request so far.=
</div><div>Also, we have to apologize to people that both of co-chairs won&=
#39;t be able to come to Dallas. But, if we have a meeting, we will find so=
meone to take care of it and we will try to join from remote as much as pos=
sible.</div><div>if someone has opinions or suggestions (or complaints..), =
please let us hear.</div><div><br></div><div>Regards,</div><div>--</div><di=
v>Yoshi &amp; Phil<br><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Thu, Mar 5, 2015 at 12:21 AM,  <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:philip.eardley@bt.com" target=3D"_blank">philip.eardley@bt.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D=
"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D"font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">Please let us know=
 about anything you want to present or discuss during the meeting. <u></u><=
u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:blue">Thanks<u></u><u></u></span></p=
><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:blue">Phil &amp; Yoshi<u></u><u></u></span></p><p cl=
ass=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-s=
erif&quot;;color:blue"><u></u>=C2=A0<u></u></span></p><div style=3D"border:=
none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div styl=
e=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">=
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> multipathtcp [mailto:<a href=3D"mailto:multipathtcp-b=
ounces@ietf.org" target=3D"_blank">multipathtcp-bounces@ietf.org</a>] <b>On=
 Behalf Of </b>Yoshifumi Nishida<br><b>Sent:</b> 23 February 2015 06:44<br>=
<b>To:</b> multipathtcp<br><b>Subject:</b> [multipathtcp] Agenda for dallas=
 meeting<u></u><u></u></span></p></div></div><div><div><p class=3D"MsoNorma=
l"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNormal"><span style=3D"font-=
size:10.0pt">Hello,<br><br>According to the current preliminary agenda (</s=
pan><a href=3D"https://datatracker.ietf.org/meeting/92/agenda.html" target=
=3D"_blank"><span style=3D"font-size:10.0pt">https://datatracker.ietf.org/m=
eeting/92/agenda.html</span></a><span style=3D"font-size:10.0pt">), we will=
 have the=C2=A0following the slot at the Dallas=C2=A0meeting.<br><br>=C2=A0=
 =C2=A0 =C2=A0Date: =C2=A0Tuesday, March 24, 2015, 13:00 - 15:00 (Afternoon=
 Session I) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<br>=C2=A0 =C2=A0 =C2=A0Room:=
 Far East<br><br>If you&#39;re planning to present something, please provid=
e us the following info.<br>=C2=A0 =C2=A01: presenter&#39;s name<br>=C2=A0 =
=C2=A02: title<br>=C2=A0 =C2=A03: length of the presentation<br><br>Thanks,=
<br>--<br>Yoshi &amp; Phil</span><u></u><u></u></p></div></div></div></div>=
</div></div></blockquote></div><br></div></div></div>

--001a11c3a99ae1e35b0510fd6895--


From nobody Wed Mar 11 23:17:39 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EEE61A8A94 for <multipathtcp@ietfa.amsl.com>; Wed, 11 Mar 2015 23:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.215
X-Spam-Level: **
X-Spam-Status: No, score=2.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 4lX64mfyK10e for <multipathtcp@ietfa.amsl.com>; Wed, 11 Mar 2015 23:17:36 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E682D1A8A93 for <multipathtcp@ietf.org>; Wed, 11 Mar 2015 23:17:35 -0700 (PDT)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 4D9BD2780B0 for <multipathtcp@ietf.org>; Thu, 12 Mar 2015 15:17:34 +0900 (JST)
Received: by wesw62 with SMTP id w62so14013812wes.8 for <multipathtcp@ietf.org>; Wed, 11 Mar 2015 23:17:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.21.206 with SMTP id x14mr30225498wie.65.1426141051933; Wed, 11 Mar 2015 23:17:31 -0700 (PDT)
Received: by 10.194.41.167 with HTTP; Wed, 11 Mar 2015 23:17:31 -0700 (PDT)
In-Reply-To: <21760.13284.484490.737078@fireball.kivinen.iki.fi>
References: <21760.13284.484490.737078@fireball.kivinen.iki.fi>
Date: Wed, 11 Mar 2015 23:17:31 -0700
Message-ID: <CAO249ye8Ki6MmGVtjuWezwJYKtXet9jrXTBSsTf0QeYZuMvm1g@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b874e08ccfbec05111156af
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/82RoElJZPzW_A46NePGIGXjrhyA>
Subject: [multipathtcp] Fwd: [tcpinc] Going forward without protecting TCP headers
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Mar 2015 06:17:38 -0000

--047d7b874e08ccfbec05111156af
Content-Type: text/plain; charset=UTF-8

Hi,
I'm guessing this may have some impacts on mptcp.
If tcpinc go to this direction, are we going to use solutions like
draft-bonaventure-mptcp-tls-00 for prong 2 approach?

Thanks,
--
Yoshi

---------- Forwarded message ----------
From: Tero Kivinen <kivinen@iki.fi>
Date: Wed, Mar 11, 2015 at 5:24 AM
Subject: [tcpinc] Going forward without protecting TCP headers
To: tcpinc@ietf.org


In the Honolulu meeting we had long discussion about whether to
protect the TCP headers or not. There were several people who
considered the main idea of tcpinc, to be to protect against
passive attacks, and did not care that much about active attacks,
i.e. didn't care for protection of the TCP headers. There were
also few people in favor of protection of header bits, i.e.
protect against active attacks.

Everybody wanted to protect data for integrity, i.e. MAC of data
stream and protection against replay. As most people in he
meeting did not seem to want to have protection against active
attacks, it was decided that those people who do want protect TCP
header, would send email to the list and explain why they want it
and what features needs to be protected.

I sent out the request for such comments at 2014-11-15:

http://www.ietf.org/mail-archive/web/tcpinc/current/msg00393.html

In my analysis of the email thread, there were two people who
said they would like to have some TCP features to be protected:

http://www.ietf.org/mail-archive/web/tcpinc/current/msg00396.html
http://www.ietf.org/mail-archive/web/tcpinc/current/msg00403.html

There were more than dozen people discussing this in the meeting, and
while people expressed opinions supporting the two options, we believe
that there is more support for going for not protecting the header.
Moreover, we believe that at this stage it is more important to make a
decision and move forward.

Based on this the tcpinc chairs have decided that we will go with
the option of NOT protecting the TCP headers.

This means that in Dallas IETF we should work forward based on
this decision.
--
kivinen@iki.fi

_______________________________________________
Tcpinc mailing list
Tcpinc@ietf.org
https://www.ietf.org/mailman/listinfo/tcpinc

--047d7b874e08ccfbec05111156af
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div>I&#39;m guessing this may have some imp=
acts on mptcp.</div><div>If tcpinc go to this direction, are we going to us=
e solutions like draft-bonaventure-mptcp-tls-00 for prong 2 approach?</div>=
<div><br></div><div>Thanks,</div><div>--</div><div>Yoshi</div><br><div clas=
s=3D"gmail_quote">---------- Forwarded message ----------<br>From: <b class=
=3D"gmail_sendername">Tero Kivinen</b> <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:kivinen@iki.fi">kivinen@iki.fi</a>&gt;</span><br>Date: Wed, Mar 11, 201=
5 at 5:24 AM<br>Subject: [tcpinc] Going forward without protecting TCP head=
ers<br>To: <a href=3D"mailto:tcpinc@ietf.org">tcpinc@ietf.org</a><br><br><b=
r>In the Honolulu meeting we had long discussion about whether to<br>
protect the TCP headers or not. There were several people who<br>
considered the main idea of tcpinc, to be to protect against<br>
passive attacks, and did not care that much about active attacks,<br>
i.e. didn&#39;t care for protection of the TCP headers. There were<br>
also few people in favor of protection of header bits, i.e.<br>
protect against active attacks.<br>
<br>
Everybody wanted to protect data for integrity, i.e. MAC of data<br>
stream and protection against replay. As most people in he<br>
meeting did not seem to want to have protection against active<br>
attacks, it was decided that those people who do want protect TCP<br>
header, would send email to the list and explain why they want it<br>
and what features needs to be protected.<br>
<br>
I sent out the request for such comments at 2014-11-15:<br>
<br>
<a href=3D"http://www.ietf.org/mail-archive/web/tcpinc/current/msg00393.htm=
l" target=3D"_blank">http://www.ietf.org/mail-archive/web/tcpinc/current/ms=
g00393.html</a><br>
<br>
In my analysis of the email thread, there were two people who<br>
said they would like to have some TCP features to be protected:<br>
<br>
<a href=3D"http://www.ietf.org/mail-archive/web/tcpinc/current/msg00396.htm=
l" target=3D"_blank">http://www.ietf.org/mail-archive/web/tcpinc/current/ms=
g00396.html</a><br>
<a href=3D"http://www.ietf.org/mail-archive/web/tcpinc/current/msg00403.htm=
l" target=3D"_blank">http://www.ietf.org/mail-archive/web/tcpinc/current/ms=
g00403.html</a><br>
<br>
There were more than dozen people discussing this in the meeting, and<br>
while people expressed opinions supporting the two options, we believe<br>
that there is more support for going for not protecting the header.<br>
Moreover, we believe that at this stage it is more important to make a<br>
decision and move forward.<br>
<br>
Based on this the tcpinc chairs have decided that we will go with<br>
the option of NOT protecting the TCP headers.<br>
<br>
This means that in Dallas IETF we should work forward based on<br>
this decision.<br>
<span class=3D""><font color=3D"#888888">--<br>
<a href=3D"mailto:kivinen@iki.fi">kivinen@iki.fi</a><br>
<br>
_______________________________________________<br>
Tcpinc mailing list<br>
<a href=3D"mailto:Tcpinc@ietf.org">Tcpinc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcpinc" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/tcpinc</a><br>
</font></span></div><br></div>

--047d7b874e08ccfbec05111156af--


From nobody Thu Mar 12 00:40:46 2015
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BE301A1B6C for <multipathtcp@ietfa.amsl.com>; Thu, 12 Mar 2015 00:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 BjN6f6LlEP4J for <multipathtcp@ietfa.amsl.com>; Thu, 12 Mar 2015 00:40:43 -0700 (PDT)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC131A1B40 for <multipathtcp@ietf.org>; Thu, 12 Mar 2015 00:40:43 -0700 (PDT)
Received: from mbpobo.local (host-78-129-6-94.dynamic.voo.be [78.129.6.94]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id C1335B40B6; Thu, 12 Mar 2015 08:40:34 +0100 (CET)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be C1335B40B6
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1426146034; bh=FnICJmOd8TXff26ortEdghyKicdEcyhNOhPpNlnNX1M=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=GoJEkMP77YzHgBciBazFyVas658IYXuqOPCJm1HYk7olQxqNiP5PPdzX8ecQoABBB cjZkClXLEZMuX+KWIfwk5QVDmJHB4ouwELMNyoLpQW+VgNo8Lud6ApOvyuFzXDc7wQ OSnMIuJ4+29JMPzGrI1dO0Fe/WudmMcUGl8X7EK0=
Message-ID: <550142F5.2010703@uclouvain.be>
Date: Thu, 12 Mar 2015 08:40:37 +0100
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>,  multipathtcp <multipathtcp@ietf.org>
References: <21760.13284.484490.737078@fireball.kivinen.iki.fi> <CAO249ye8Ki6MmGVtjuWezwJYKtXet9jrXTBSsTf0QeYZuMvm1g@mail.gmail.com>
In-Reply-To: <CAO249ye8Ki6MmGVtjuWezwJYKtXet9jrXTBSsTf0QeYZuMvm1g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.97.7-exp at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: C1335B40B6.A3D28
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/OflKCoy3a4DPjHjAwLbEthWnPOQ>
Subject: Re: [multipathtcp] Fwd: [tcpinc] Going forward without protecting TCP headers
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Mar 2015 07:40:44 -0000

Yoshifumi,

> I'm guessing this may have some impacts on mptcp.
> If tcpinc go to this direction, are we going to use solutions like
> draft-bonaventure-mptcp-tls-00 for prong 2 approach?

I think that Multipath TCP would be a better starting point than TCP for 
the TCPINC work because Multipath TCP brings two important benefits :
  - Multipath TCP already includes a way to deal with RST attacks
  - Multipath TCP enables the utilisation of multiple paths, which 
brings a new dimension to the problem space.

With Multipath TCP, a host that detects a problem on a path (e.g. MAC 
failure) can opt to stop using this path and move the connection to 
another path to hopefully counter the attacker. With regular TCP, this 
is not possible. The MPTCP working has shown that with RFC6824 and the 
deployed MPTCP stack it is already possible to deal with various types 
of middleboxes. If there is middlebox interference on a path and several 
paths exist, MPTCP implementations already stop using the path with 
interference.

I think that draft-bonaventure-mptcp-tls-00 could be a very good 
starting point to design a TCPINC like solution for MPTCP, but of course 
my viewpoint might be biased...



Olivier



From nobody Thu Mar 12 08:52:12 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD3981A0022 for <multipathtcp@ietfa.amsl.com>; Thu, 12 Mar 2015 08:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 LsE0s20xcIfV for <multipathtcp@ietfa.amsl.com>; Thu, 12 Mar 2015 08:52:09 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 441BA1A8A84 for <multipathtcp@ietf.org>; Thu, 12 Mar 2015 08:50:26 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 898E118C5C7; Thu, 12 Mar 2015 16:50:24 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.72]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 6BC1123808F; Thu, 12 Mar 2015 16:50:24 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541%19]) with mapi id 14.03.0224.002; Thu, 12 Mar 2015 16:50:24 +0100
From: <mohamed.boucadair@orange.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: I-D Action: draft-boucadair-mptcp-symmetric-02.txt
Thread-Index: AQHQWmW1jGdZlr/o6UetmdBnoRBXIZ0ZAw/g
Date: Thu, 12 Mar 2015 15:50:24 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300492BE30@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20150309123626.17741.17314.idtracker@ietfa.amsl.com>
In-Reply-To: <20150309123626.17741.17314.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/6mYZtU9hR_aC4WtlT4Png-qE868>
Cc: "draft-boucadair-mptcp-symmetric@tools.ietf.org" <draft-boucadair-mptcp-symmetric@tools.ietf.org>
Subject: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-symmetric-02.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 12 Mar 2015 15:52:10 -0000

Dear all,

We submitted this short I-D.

Comments are welcome.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> internet-drafts@ietf.org
> Envoy=E9=A0: lundi 9 mars 2015 13:36
> =C0=A0: i-d-announce@ietf.org
> Objet=A0: I-D Action: draft-boucadair-mptcp-symmetric-02.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>=20
>=20
>         Title           : An Extension to MPTCP for Symmetrical Sub-Flow
> Management
>         Authors         : Mohamed Boucadair
>                           Christian Jacquenet
> 	Filename        : draft-boucadair-mptcp-symmetric-02.txt
> 	Pages           : 7
> 	Date            : 2015-03-09
>=20
> Abstract:
>    This document specifies a MPTCP extension that allows to achieve
>    symmetrical subflow management.  In particular, this extension allows
>    both endpoints to add new subflows whenever needed without waiting
>    for the endpoint which initiated the first subflow to add new ones.
>=20
>    This document updates RFC 6824.
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-boucadair-mptcp-symmetric/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-boucadair-mptcp-symmetric-02
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-mptcp-symmetric-02
>=20
>=20
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Sat Mar 14 14:22:46 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F12B81A0218 for <multipathtcp@ietfa.amsl.com>; Sat, 14 Mar 2015 14:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.221
X-Spam-Level: *
X-Spam-Status: No, score=1.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 nAG5gesC1tK0 for <multipathtcp@ietfa.amsl.com>; Sat, 14 Mar 2015 14:22:43 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 687481A0235 for <multipathtcp@ietf.org>; Sat, 14 Mar 2015 14:22:42 -0700 (PDT)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 5174A278102 for <multipathtcp@ietf.org>; Sun, 15 Mar 2015 06:22:40 +0900 (JST)
Received: by wixw10 with SMTP id w10so13349245wix.0 for <multipathtcp@ietf.org>; Sat, 14 Mar 2015 14:22:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.222.197 with SMTP id qo5mr106960514wjc.142.1426368157871;  Sat, 14 Mar 2015 14:22:37 -0700 (PDT)
Received: by 10.194.41.167 with HTTP; Sat, 14 Mar 2015 14:22:37 -0700 (PDT)
In-Reply-To: <550142F5.2010703@uclouvain.be>
References: <21760.13284.484490.737078@fireball.kivinen.iki.fi> <CAO249ye8Ki6MmGVtjuWezwJYKtXet9jrXTBSsTf0QeYZuMvm1g@mail.gmail.com> <550142F5.2010703@uclouvain.be>
Date: Sat, 14 Mar 2015 14:22:37 -0700
Message-ID: <CAO249yf=PNOhEYogRNw4cg4FA0Dx2FfEpcyi5qaPOHmvO08NHA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Content-Type: multipart/alternative; boundary=001a11c3a99a5e781005114637d3
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/pAoeTI8Uhqd1YJYVhAm6Fhkr_7E>
Cc: multipathtcp <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] Fwd: [tcpinc] Going forward without protecting TCP headers
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 14 Mar 2015 21:22:45 -0000

--001a11c3a99a5e781005114637d3
Content-Type: text/plain; charset=UTF-8

Hi Olivier,

On Thu, Mar 12, 2015 at 12:40 AM, Olivier Bonaventure <
Olivier.Bonaventure@uclouvain.be> wrote:

> Yoshifumi,
>
>  I'm guessing this may have some impacts on mptcp.
>> If tcpinc go to this direction, are we going to use solutions like
>> draft-bonaventure-mptcp-tls-00 for prong 2 approach?
>>
>
> I think that Multipath TCP would be a better starting point than TCP for
> the TCPINC work because Multipath TCP brings two important benefits :
>  - Multipath TCP already includes a way to deal with RST attacks
>  - Multipath TCP enables the utilisation of multiple paths, which brings a
> new dimension to the problem space.

With Multipath TCP, a host that detects a problem on a path (e.g. MAC
> failure) can opt to stop using this path and move the connection to another
> path to hopefully counter the attacker. With regular TCP, this is not
> possible. The MPTCP working has shown that with RFC6824 and the deployed
> MPTCP stack it is already possible to deal with various types of
> middleboxes. If there is middlebox interference on a path and several paths
> exist, MPTCP implementations already stop using the path with interference.
>

It might be a good starting point, but one concen is tcpinc is focusing on
TCP in general.
The solution for mptcp may not be applied to other situations, which won't
be applicable for tcpinc.
We might need to explore solutions without relying on tcpinc.

I think that draft-bonaventure-mptcp-tls-00 could be a very good starting
> point to design a TCPINC like solution for MPTCP, but of course my
> viewpoint might be biased...


I also think so.
Another possibility is to cherry-pick the ideas proposed for tcpinc or
check some authors to update them for mptcp.

Thanks,
--
Yoshi

--001a11c3a99a5e781005114637d3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Olivier,<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Mar 12, 2015 at 12:40 AM, Olivier Bonaventure <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:Olivier.Bonaventure@uclouvain.be" targe=
t=3D"_blank">Olivier.Bonaventure@uclouvain.be</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Yoshifumi,<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I&#39;m guessing this may have some impacts on mptcp.<br>
If tcpinc go to this direction, are we going to use solutions like<br>
draft-bonaventure-mptcp-tls-00 for prong 2 approach?<br>
</blockquote>
<br></span>
I think that Multipath TCP would be a better starting point than TCP for th=
e TCPINC work because Multipath TCP brings two important benefits :<br>
=C2=A0- Multipath TCP already includes a way to deal with RST attacks<br>
=C2=A0- Multipath TCP enables the utilisation of multiple paths, which brin=
gs a new dimension to the problem space.</blockquote><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
With Multipath TCP, a host that detects a problem on a path (e.g. MAC failu=
re) can opt to stop using this path and move the connection to another path=
 to hopefully counter the attacker. With regular TCP, this is not possible.=
 The MPTCP working has shown that with RFC6824 and the deployed MPTCP stack=
 it is already possible to deal with various types of middleboxes. If there=
 is middlebox interference on a path and several paths exist, MPTCP impleme=
ntations already stop using the path with interference.<br></blockquote><di=
v><br></div><div>It might be a good starting point, but one concen is tcpin=
c is focusing on TCP in general.=C2=A0</div><div>The solution for mptcp may=
 not be applied to other situations, which won&#39;t be applicable for tcpi=
nc.=C2=A0</div><div>We might need to explore solutions without relying on t=
cpinc.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think that draft-bonaventure-mptcp-tls-00 could be a very good starting p=
oint to design a TCPINC like solution for MPTCP, but of course my viewpoint=
 might be biased...</blockquote><div><br></div><div>I also think so.=C2=A0<=
/div><div>Another possibility is to cherry-pick the ideas proposed for tcpi=
nc or check some authors to update them for mptcp.</div><div><br></div><div=
>Thanks,</div><div>--</div><div>Yoshi=C2=A0</div></div></div></div>

--001a11c3a99a5e781005114637d3--


From nobody Wed Mar 18 23:56:36 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08BB1A8948 for <multipathtcp@ietfa.amsl.com>; Wed, 18 Mar 2015 23:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.215
X-Spam-Level: **
X-Spam-Status: No, score=2.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 YqNwtFhgEhNz for <multipathtcp@ietfa.amsl.com>; Wed, 18 Mar 2015 23:56:33 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D55101A8723 for <multipathtcp@ietf.org>; Wed, 18 Mar 2015 23:56:32 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 165072780E0 for <multipathtcp@ietf.org>; Thu, 19 Mar 2015 15:56:30 +0900 (JST)
Received: by wixw10 with SMTP id w10so60281114wix.0 for <multipathtcp@ietf.org>; Wed, 18 Mar 2015 23:56:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.110.233 with SMTP id id9mr149888454wjb.136.1426748187616;  Wed, 18 Mar 2015 23:56:27 -0700 (PDT)
Received: by 10.194.41.167 with HTTP; Wed, 18 Mar 2015 23:56:27 -0700 (PDT)
In-Reply-To: <CAO249yc3i7NiA3RdDhuqxDCkaVvxDitweqrp-oXSUt4s6cydOA@mail.gmail.com>
References: <CAO249ydcUPVU4nD7bzeoxsePhqRowu1RzB5JAfkdMkVDi1-cKw@mail.gmail.com> <A2E337CDB7BC4145B018B9BEE8EB3E0D4148DFAE18@EMV67-UKRD.domain1.systemhost.net> <CAO249yc3i7NiA3RdDhuqxDCkaVvxDitweqrp-oXSUt4s6cydOA@mail.gmail.com>
Date: Wed, 18 Mar 2015 23:56:27 -0700
Message-ID: <CAO249yeYKRTM1p4Wk39rGavBroACd21T2H_bqAM1Ht3rVK_fOA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Content-Type: multipart/alternative; boundary=047d7bf10b3ae82e7105119eb29e
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/8g3tIqA08aSSTeIz-0FuqXEKBVs>
Cc: multipathtcp <multipathtcp@ietf.org>, Martin Stiemerling <mls.ietf@gmail.com>
Subject: Re: [multipathtcp] Agenda for dallas meeting
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 19 Mar 2015 06:56:35 -0000

--047d7bf10b3ae82e7105119eb29e
Content-Type: text/plain; charset=UTF-8

Hi folks,

We have decided to return the slot for the WG meeting at Dallas due to the
lack of agenda.
While not having a meeting this time, we'll try to facilitate the
discussions on the ML for the next meeting and proceed things as well.
Also, if you think having a (virtual) interim meeting is a good option,
please let us know.

Regards,
--
Yoshi & Phil


On Tue, Mar 10, 2015 at 11:30 PM, Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
wrote:

> Hi folks,
>
> We start thinking about returning a slot for dallas meeting as we haven't
> received a request so far.
> Also, we have to apologize to people that both of co-chairs won't be able
> to come to Dallas. But, if we have a meeting, we will find someone to take
> care of it and we will try to join from remote as much as possible.
> if someone has opinions or suggestions (or complaints..), please let us
> hear.
>
> Regards,
> --
> Yoshi & Phil
>
>
> On Thu, Mar 5, 2015 at 12:21 AM, <philip.eardley@bt.com> wrote:
>
>> Please let us know about anything you want to present or discuss during
>> the meeting.
>>
>> Thanks
>>
>> Phil & Yoshi
>>
>>
>>
>> *From:* multipathtcp [mailto:multipathtcp-bounces@ietf.org] *On Behalf
>> Of *Yoshifumi Nishida
>> *Sent:* 23 February 2015 06:44
>> *To:* multipathtcp
>> *Subject:* [multipathtcp] Agenda for dallas meeting
>>
>>
>>
>> Hello,
>>
>> According to the current preliminary agenda (
>> https://datatracker.ietf.org/meeting/92/agenda.html), we will have
>> the following the slot at the Dallas meeting.
>>
>>      Date:  Tuesday, March 24, 2015, 13:00 - 15:00 (Afternoon Session I)
>>
>>      Room: Far East
>>
>> If you're planning to present something, please provide us the following
>> info.
>>    1: presenter's name
>>    2: title
>>    3: length of the presentation
>>
>> Thanks,
>> --
>> Yoshi & Phil
>>
>
>

--047d7bf10b3ae82e7105119eb29e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi folks,<div><br></div><div>We have decided to return the=
 slot for the WG meeting at Dallas due to the lack of agenda.</div><div>Whi=
le not having a meeting this time, we&#39;ll try to facilitate the discussi=
ons on the ML for the next meeting and proceed things as well.</div><div>Al=
so, if you think having a (virtual) interim meeting is a good option, pleas=
e let us know.</div><div><br></div><div>Regards,</div><div>--</div><div>Yos=
hi &amp; Phil</div><div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar 10, 2015 at 11:30 P=
M, Yoshifumi Nishida <span dir=3D"ltr">&lt;<a href=3D"mailto:nishida@sfc.wi=
de.ad.jp" target=3D"_blank">nishida@sfc.wide.ad.jp</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi folks,<div><br></div><d=
iv>We start thinking about returning a slot for dallas meeting as we haven&=
#39;t received a request so far.</div><div>Also, we have to apologize to pe=
ople that both of co-chairs won&#39;t be able to come to Dallas. But, if we=
 have a meeting, we will find someone to take care of it and we will try to=
 join from remote as much as possible.</div><div>if someone has opinions or=
 suggestions (or complaints..), please let us hear.</div><div><br></div><di=
v>Regards,</div><div>--</div><div>Yoshi &amp; Phil<div><div class=3D"h5"><b=
r><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Mar 5, =
2015 at 12:21 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:philip.eardley@b=
t.com" target=3D"_blank">philip.eardley@bt.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purp=
le"><div><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot=
;,&quot;sans-serif&quot;;color:blue">Please let us know about anything you =
want to present or discuss during the meeting. <u></u><u></u></span></p><p =
class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans=
-serif&quot;;color:blue">Thanks<u></u><u></u></span></p><p class=3D"MsoNorm=
al"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;col=
or:blue">Phil &amp; Yoshi<u></u><u></u></span></p><p class=3D"MsoNormal"><s=
pan style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blu=
e"><u></u>=C2=A0<u></u></span></p><div style=3D"border:none;border-left:sol=
id blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style=3D"border:none;bor=
der-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNorma=
l"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Taho=
ma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
> multipathtcp [mailto:<a href=3D"mailto:multipathtcp-bounces@ietf.org" tar=
get=3D"_blank">multipathtcp-bounces@ietf.org</a>] <b>On Behalf Of </b>Yoshi=
fumi Nishida<br><b>Sent:</b> 23 February 2015 06:44<br><b>To:</b> multipath=
tcp<br><b>Subject:</b> [multipathtcp] Agenda for dallas meeting<u></u><u></=
u></span></p></div></div><div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u><=
/u></p><div><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Hello,<=
br><br>According to the current preliminary agenda (</span><a href=3D"https=
://datatracker.ietf.org/meeting/92/agenda.html" target=3D"_blank"><span sty=
le=3D"font-size:10.0pt">https://datatracker.ietf.org/meeting/92/agenda.html=
</span></a><span style=3D"font-size:10.0pt">), we will have the=C2=A0follow=
ing the slot at the Dallas=C2=A0meeting.<br><br>=C2=A0 =C2=A0 =C2=A0Date: =
=C2=A0Tuesday, March 24, 2015, 13:00 - 15:00 (Afternoon Session I) =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0<br>=C2=A0 =C2=A0 =C2=A0Room: Far East<br><br>If=
 you&#39;re planning to present something, please provide us the following =
info.<br>=C2=A0 =C2=A01: presenter&#39;s name<br>=C2=A0 =C2=A02: title<br>=
=C2=A0 =C2=A03: length of the presentation<br><br>Thanks,<br>--<br>Yoshi &a=
mp; Phil</span><u></u><u></u></p></div></div></div></div></div></div></bloc=
kquote></div><br></div></div></div></div></div>
</blockquote></div><br></div></div></div>

--047d7bf10b3ae82e7105119eb29e--


From nobody Tue Mar 24 23:58:14 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC2C1A8878 for <multipathtcp@ietfa.amsl.com>; Tue, 24 Mar 2015 23:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.215
X-Spam-Level: **
X-Spam-Status: No, score=2.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 lqjoKvMsJUVn for <multipathtcp@ietfa.amsl.com>; Tue, 24 Mar 2015 23:58:10 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DC801A037C for <multipathtcp@ietf.org>; Tue, 24 Mar 2015 23:58:10 -0700 (PDT)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 9BD762780A8 for <multipathtcp@ietf.org>; Wed, 25 Mar 2015 15:58:07 +0900 (JST)
Received: by wibg7 with SMTP id g7so97704202wib.1 for <multipathtcp@ietf.org>; Tue, 24 Mar 2015 23:58:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.84.3 with SMTP id u3mr35360601wiy.38.1427266684336; Tue, 24 Mar 2015 23:58:04 -0700 (PDT)
Received: by 10.194.41.167 with HTTP; Tue, 24 Mar 2015 23:58:04 -0700 (PDT)
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300492BE30@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20150309123626.17741.17314.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93300492BE30@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Date: Tue, 24 Mar 2015 23:58:04 -0700
Message-ID: <CAO249ycaZRYKYP9ZLLM8xy=F5V+sq866xM9rBKHi2jLy3VPPFA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: mohamed.boucadair@orange.com
Content-Type: multipart/alternative; boundary=14dae9cc9c94b842200512176b19
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/EO9rBddyp8cgMWPWnHVn-ZuLq1Q>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "draft-boucadair-mptcp-symmetric@tools.ietf.org" <draft-boucadair-mptcp-symmetric@tools.ietf.org>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-symmetric-02.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Mar 2015 06:58:13 -0000

--14dae9cc9c94b842200512176b19
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Med,

I have read the draft. I agree with the motivation of the draft, but I'm
not very sure if we need to extend or develop an option yet.
My comments are below...

1: I think you will need to use ADD_ADDR2 instead of ADD_ADDR in future
versions as ADD_ADDR will be deprecated.

2: mptcp cannot guarantee if it can receive incoming flows as it depends on
external mechanisms.
    So, I'm not very sure how much the check flag can be useful.

3: From the same reason above, I'm also not very sure about the lifetime
info, either.
    Also, even if an endpoint tries to use a staled address for a new
subflow, I think it will fail since the peer won't be able to send back a
proper token.

Thanks,
--
Yoshi

On Thu, Mar 12, 2015 at 8:50 AM, <mohamed.boucadair@orange.com> wrote:

> Dear all,
>
> We submitted this short I-D.
>
> Comments are welcome.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> > internet-drafts@ietf.org
> > Envoy=C3=A9 : lundi 9 mars 2015 13:36
> > =C3=80 : i-d-announce@ietf.org
> > Objet : I-D Action: draft-boucadair-mptcp-symmetric-02.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> >
> >         Title           : An Extension to MPTCP for Symmetrical Sub-Flo=
w
> > Management
> >         Authors         : Mohamed Boucadair
> >                           Christian Jacquenet
> >       Filename        : draft-boucadair-mptcp-symmetric-02.txt
> >       Pages           : 7
> >       Date            : 2015-03-09
> >
> > Abstract:
> >    This document specifies a MPTCP extension that allows to achieve
> >    symmetrical subflow management.  In particular, this extension allow=
s
> >    both endpoints to add new subflows whenever needed without waiting
> >    for the endpoint which initiated the first subflow to add new ones.
> >
> >    This document updates RFC 6824.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-symmetric/
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-boucadair-mptcp-symmetric-02
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-mptcp-symmetric-02
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>

--14dae9cc9c94b842200512176b19
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Med,<div><br><div>I have read the draft. I agree with t=
he motivation of the draft, but I&#39;m not very sure if we need to extend =
or develop an option yet.</div><div>My comments are below...</div><div><br>=
</div><div>1: I think you will need to use ADD_ADDR2 instead of ADD_ADDR in=
 future versions as ADD_ADDR will be deprecated.</div><div><br></div><div>2=
: mptcp cannot guarantee if it can receive incoming flows as it depends on =
external mechanisms.=C2=A0</div><div>=C2=A0 =C2=A0 So, I&#39;m not very sur=
e how much the check flag can be useful.=C2=A0</div><div><br></div><div>3: =
>From the same reason above, I&#39;m also not very sure about the lifetime i=
nfo, either.</div><div>=C2=A0 =C2=A0 Also, even if an endpoint tries to use=
 a staled address for a new subflow, I think it will fail since the peer wo=
n&#39;t be able to send back a proper token.<br></div><div>=C2=A0 =C2=A0 =
=C2=A0=C2=A0<br></div><div>Thanks,</div><div>--</div><div>Yoshi</div><div><=
br><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Thu, Mar 12, 20=
15 at 8:50 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:mohamed.boucadair@o=
range.com" target=3D"_blank">mohamed.boucadair@orange.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex">Dear all,<br>
<br>
We submitted this short I-D.<br>
<br>
Comments are welcome.<br>
<br>
Cheers,<br>
Med<br>
<br>
&gt; -----Message d&#39;origine-----<br>
&gt; De=C2=A0: I-D-Announce [mailto:<a href=3D"mailto:i-d-announce-bounces@=
ietf.org" target=3D"_blank">i-d-announce-bounces@ietf.org</a>] De la part d=
e<br>
&gt; <a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet=
-drafts@ietf.org</a><br>
&gt; Envoy=C3=A9=C2=A0: lundi 9 mars 2015 13:36<br>
&gt; =C3=80=C2=A0: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blan=
k">i-d-announce@ietf.org</a><br>
&gt; Objet=C2=A0: I-D Action: draft-boucadair-mptcp-symmetric-02.txt<br>
<div><div>&gt;<br>
&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts<br>
&gt; directories.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: An Extension to MPTCP for Symmetrical Sub-Flow<br>
&gt; Management<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Mohamed Boucadair<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0Christian Jacquenet<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-=
boucadair-mptcp-symmetric-02.txt<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 7<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : 2015-03-09<br>
&gt;<br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0 This document specifies a MPTCP extension that allows to =
achieve<br>
&gt;=C2=A0 =C2=A0 symmetrical subflow management.=C2=A0 In particular, this=
 extension allows<br>
&gt;=C2=A0 =C2=A0 both endpoints to add new subflows whenever needed withou=
t waiting<br>
&gt;=C2=A0 =C2=A0 for the endpoint which initiated the first subflow to add=
 new ones.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 This document updates RFC 6824.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-boucadair-mptcp-symm=
etric/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-boucadair-=
mptcp-symmetric/</a><br>
&gt;<br>
&gt; There&#39;s also a htmlized version available at:<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-boucadair-mptcp-symmetric-=
02" target=3D"_blank">http://tools.ietf.org/html/draft-boucadair-mptcp-symm=
etric-02</a><br>
&gt;<br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-mptcp-sy=
mmetric-02" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-bouc=
adair-mptcp-symmetric-02</a><br>
&gt;<br>
&gt;<br>
&gt; Please note that it may take a couple of minutes from the time of<br>
&gt; submission<br>
&gt; until the htmlized version and diff are available at <a href=3D"http:/=
/tools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp:=
//ftp.ietf.org/internet-drafts/</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; I-D-Announce mailing list<br>
&gt; <a href=3D"mailto:I-D-Announce@ietf.org" target=3D"_blank">I-D-Announc=
e@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
&gt; Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.html=
" target=3D"_blank">http://www.ietf.org/shadow.html</a><br>
&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_bl=
ank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
<br>
</div></div>_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">multipathtcp@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
</blockquote></div><br></div></div></div></div>

--14dae9cc9c94b842200512176b19--


From nobody Fri Mar 27 10:26:04 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4191C1B2AC3; Fri, 27 Mar 2015 10:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 x0nfWr1UMsPS; Fri, 27 Mar 2015 10:26:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AE21B2AA7; Fri, 27 Mar 2015 10:25:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150327172554.12793.72407.idtracker@ietfa.amsl.com>
Date: Fri, 27 Mar 2015 10:25:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/aAhELDEwFOb4JGbtfQjh_L9oVUE>
Cc: multipathtcp@ietf.org
Subject: [multipathtcp] I-D Action: draft-ietf-mptcp-attacks-04.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 Mar 2015 17:26:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multipath TCP Working Group of the IETF.

        Title           : Analysis of MPTCP residual threats and possible fixes
        Authors         : Marcelo Bagnulo
                          Christoph Paasch
                          Fernando Gont
                          Olivier Bonaventure
                          Costin Raiciu
	Filename        : draft-ietf-mptcp-attacks-04.txt
	Pages           : 18
	Date            : 2015-03-27

Abstract:
   This documents performs an analysis of the residual threats for MPTCP
   and explores possible solutions to them.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mptcp-attacks/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mptcp-attacks-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-attacks-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

