
From philip.eardley@bt.com  Wed Sep  4 00:31:27 2013
Return-Path: <philip.eardley@bt.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 A686E11E8188 for <multipathtcp@ietfa.amsl.com>; Wed,  4 Sep 2013 00:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.298
X-Spam-Level: 
X-Spam-Status: No, score=-103.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDKwTqPX0BWf for <multipathtcp@ietfa.amsl.com>; Wed,  4 Sep 2013 00:31:23 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp64.intersmtp.com [62.239.224.237]) by ietfa.amsl.com (Postfix) with ESMTP id BF01611E8187 for <multipathtcp@ietf.org>; Wed,  4 Sep 2013 00:31:22 -0700 (PDT)
Received: from EVMHT69-UKRD.domain1.systemhost.net (10.36.3.129) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 4 Sep 2013 08:31:20 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.113]) by EVMHT69-UKRD.domain1.systemhost.net ([10.36.3.129]) with mapi; Wed, 4 Sep 2013 08:31:20 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Date: Wed, 4 Sep 2013 08:31:19 +0100
Thread-Topic: [multipathtcp] MPTCP interim (audio) meeting on security,	late September
Thread-Index: Ac6SoyaM2riJg+/VT8mY+Ug44bT7KwLnctXgAr/iZLA=
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net>
In-Reply-To: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net>
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_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30EMV67UKRDdoma_"
MIME-Version: 1.0
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Sep 2013 07:31:27 -0000

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30EMV67UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Just to let you know. The Security Ads are kindly finding us a security adv=
isor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list bef=
ore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just a reminder, as I know a lot of people have been on holiday, please fil=
l in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> [=
mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com<ma=
ilto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late Sep=
tember

We think it would a good idea to have an interim (audio) meeting, in order =
to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach con=
sensus on what security improvements are needed - and what are not needed -=
 in order to progress MPTCP on the Standards track. We hope to cover both t=
he threat(s) that we will handle and, at a high-level, the solutions that w=
ill be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the t=
ime is no good for you.

In the meantime, please keep discussing MPTCP's security on the list!

Thanks,
Best wishes
Phil & Yoshifumi

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30EMV67UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Just to let yo=
u know. The Security Ads are kindly finding us a security advisor, but no l=
uck yet. So we may have to delay this slightly.<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-se=
rif";color:blue'>Also, it would be good if there was some discussion on the=
 mailing list before the call.<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
2.0pt;font-family:"Arial","sans-serif";color:blue'>phil<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial",=
"sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div style=3D'border:n=
one;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=
=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><=
p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-fa=
mily:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><spa=
n lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";=
mso-fareast-language:EN-GB'> Eardley,PL,Philip,TUB8 R <br><b>Sent:</b> 21 A=
ugust 2013 08:36<br><b>To:</b> Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.=
org<br><b>Subject:</b> RE: [multipathtcp] MPTCP interim (audio) meeting on =
security, late September<o:p></o:p></span></p></div></div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0=
pt;font-family:"Arial","sans-serif";color:blue'>Just a reminder, as I know =
a lot of people have been on holiday, please fill in the doodle <o:p></o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family=
:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";co=
lor:blue'>Thanks<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>phil<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-famil=
y:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div style=
=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><di=
v><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0c=
m 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</s=
pan></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";mso-fareast-language:EN-GB'> <a href=3D"mailto:multipathtcp-bou=
nces@ietf.org">multipathtcp-bounces@ietf.org</a> [<a href=3D"mailto:multipa=
thtcp-bounces@ietf.org">mailto:multipathtcp-bounces@ietf.org</a>] <b>On Beh=
alf Of </b><a href=3D"mailto:philip.eardley@bt.com">philip.eardley@bt.com</=
a><br><b>Sent:</b> 06 August 2013 13:49<br><b>To:</b> <a href=3D"mailto:mul=
tipathtcp@ietf.org">multipathtcp@ietf.org</a><br><b>Subject:</b> [multipath=
tcp] MPTCP interim (audio) meeting on security, late September<o:p></o:p></=
span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DM=
soNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>=
We think it would a good idea to have an interim (audio) meeting, in order =
to make progress on advancing RFC 6824 on the standards track.<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"=
Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>We will discus=
s the security of the MPTCP protocol. The aim is to reach consensus on what=
 security improvements are needed - and what are not needed - in order to p=
rogress MPTCP on the Standards track. We hope to cover both the threat(s) t=
hat we will handle and, at a high-level, the solutions that will be defined=
.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt=
;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>=
Please fill in the doodle at <a href=3D"http://doodle.com/xdf8eaiavvna9bcy#=
table">http://doodle.com/xdf8eaiavvna9bcy#table</a> <o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sa=
ns-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:12.0pt;font-family:"Arial","sans-serif"'>For previous MPTCP WG in=
terims, ~3pm GMT has been OK. Please shout if the time is no good for you.<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;f=
ont-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>In=
 the meantime, please keep discussing MPTCP&#8217;s security on the list!<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;fo=
nt-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>Tha=
nks, <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12=
.0pt;font-family:"Arial","sans-serif"'>Best wishes<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans=
-serif"'>Phil &amp; Yoshifumi<o:p></o:p></span></p></div></div></div></body=
></html>=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30EMV67UKRDdoma_--

From elopez@fortinet.com  Thu Sep  5 10:25:13 2013
Return-Path: <elopez@fortinet.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 2D62D21E80FD for <multipathtcp@ietfa.amsl.com>; Thu,  5 Sep 2013 10:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.465
X-Spam-Level: 
X-Spam-Status: No, score=-5.465 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id muwIURvKOSKz for <multipathtcp@ietfa.amsl.com>; Thu,  5 Sep 2013 10:25:08 -0700 (PDT)
Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by ietfa.amsl.com (Postfix) with ESMTP id E290021E8127 for <multipathtcp@ietf.org>; Thu,  5 Sep 2013 10:25:07 -0700 (PDT)
From: Edward Lopez <elopez@fortinet.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>
Thread-Topic: [multipathtcp] MPTCP interim (audio) meeting on security, late September
Thread-Index: AQHOnkEYnt/Sx47MpE2VypdHdwlkaJm1ulSAgAI4KIA=
Date: Thu, 5 Sep 2013 17:24:54 +0000
Message-ID: <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net>
In-Reply-To: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [65.115.88.15]
Content-Type: multipart/alternative; boundary="_000_0215C1A280E14BCC8A43A4530D231B27fortinetcom_"
MIME-Version: 1.0
X-FEAS-SYSTEM-WL: 192.168.221.212
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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 Sep 2013 17:25:13 -0000

--_000_0215C1A280E14BCC8A43A4530D231B27fortinetcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Phil,

I'm aware that I am relatively new to the WG and IETF as a whole (IETF 87=
 Berlin was my first meeting).  But I do have a long history of security =
and networking protocols, currently working and having worked for a numbe=
r of security appliance (middlebox) vendors.

My initial review of MPTCP is that I would have to consider it an evasion=
 technique from a content inspection standpoint.  Generally, content insp=
ection engines are designed to operate as either flow-based or transparen=
t-proxy.  A flow-based engine is generally used by IPS systems, but has n=
ow expanded to support many types of content inspection, most notably app=
lication control functionality of next-generation firewalls (NGFWs).  The=
 limitation of a flow-based engine is that it looks at data in as a strea=
m, generally without reordering and limited data reassembly.   A transpar=
ent proxy engine fully buffers and reassembles the data in the context of=
 specific protocols, then inspects this traffic in context.  Transparent =
proxies are useful when the inspection device has to interact within the =
protocol, such as in web-filtering solutions where a block message is sen=
t back to an offending user.  However, both of these content inspection e=
ngine types have a general model centered around the session paradigm.  a=
n MPTCP session is in effect an aggregate of multiple TCP sessions (sub f=
lows), so in effect has characteristics of a protocol-based application, =
similar to FTP, VoIP, etc.

The effect of MPTCP on content inspection engines is that it can be used =
as an evasion technique.  For example, I could envision the use of multi-=
homed MPTCP-based proxy engines out on the Internet, such that MPTCP base=
d hosts in net repressive countries could evade state-imposed web-filters=
, or school kids could evade their school system's web-filters, etc.  The=
 initial reaction from content inspectors would be do develop capabilitie=
s to detect MPTCP (likely based on options usage), and to either block or=
 force fallback to standard TCP.  A significant concern is that this is w=
here the incentive ends.  MPTCP is an evasion method, so mitigate the vul=
nerability.

I would prefer to consider how to support MPTCP, perhaps in the form of a=
n application-layer gateway and/or modification of content-inspection eng=
ines to deal with aggregation of sub-flows for inspection.  This line of =
thought lends itself to a philosophical discussion, as to if we intend MP=
TCP to be used to evade content inspection, or if we are looking to impro=
ve the performance of TCP-based applications.  I mention this because it =
would be desirable for the protocol to assist, or at least not hinder, th=
e ability to identify the multiple sub-flows that create an MPTCP session=
.

Eventually, I see the rise of middleboxes as MPTCP proxies, whether they =
are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodolog=
ies of SSL inspection today.  I am interested in these use-cases because =
without them, the default will be to block/fallback, which ultimately isn=
't useful relative to MPTCP.

My US $.02
Ed Lopez

On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com<mailto:philip.eardley@b=
t.com> wrote:

Just to let you know. The Security Ads are kindly finding us a security a=
dvisor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list b=
efore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp@i=
etf.org>
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te September

Just a reminder, as I know a lot of people have been on holiday, please f=
ill in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org>=
 [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.co=
m<mailto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late S=
eptember

We think it would a good idea to have an interim (audio) meeting, in orde=
r to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach c=
onsensus on what security improvements are needed - and what are not need=
ed - in order to progress MPTCP on the Standards track. We hope to cover =
both the threat(s) that we will handle and, at a high-level, the solution=
s that will be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the=
 time is no good for you.

In the meantime, please keep discussing MPTCP=92s security on the list!

Thanks,
Best wishes
Phil & Yoshifumi
_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
https://www.ietf.org/mailman/listinfo/multipathtcp



***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***

--_000_0215C1A280E14BCC8A43A4530D231B27fortinetcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <AA7E10A0E74D6243BDF1F93684760002@fortinet-us.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows=
-1252">
<base href=3D"x-msg://108/">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-l=
ine-break: after-white-space; ">
<div>Phil,</div>
<div><br>
</div>
<div>I'm aware that I am relatively new to the WG and IETF as a whole (IE=
TF 87 Berlin was my first meeting). &nbsp;But I do have a long history of=
 security and networking protocols, currently working and having worked f=
or a number of security appliance (middlebox)
 vendors.</div>
<div><br>
</div>
<div>My initial review of MPTCP is that I would have to consider it an ev=
asion technique from a content inspection standpoint. &nbsp;Generally, co=
ntent inspection engines are designed to operate as either flow-based or =
transparent-proxy. &nbsp;A flow-based engine is
 generally used by IPS systems, but has now expanded to support many type=
s of content inspection, most notably application control functionality o=
f next-generation firewalls (NGFWs). &nbsp;The limitation of a flow-based=
 engine is that it looks at data in as a stream,
 generally without reordering and limited data reassembly. &nbsp; A trans=
parent proxy engine fully buffers and reassembles the data in the context=
 of specific protocols, then inspects this traffic in context. &nbsp;Tran=
sparent proxies are useful when the inspection device
 has to interact within the protocol, such as in web-filtering solutions =
where a block message is sent back to an offending user. &nbsp;However, b=
oth of these content inspection engine types have a general model centere=
d around the session paradigm. &nbsp;an MPTCP session
 is in effect an aggregate of multiple TCP sessions (sub flows), so in ef=
fect has characteristics of a protocol-based application, similar to FTP,=
 VoIP, etc.</div>
<div><br>
</div>
<div>The effect of MPTCP on content inspection engines is that it can be =
used as an evasion technique. &nbsp;For example, I could envision the use=
 of multi-homed MPTCP-based proxy engines out on the Internet, such that =
MPTCP based hosts in net repressive countries
 could evade state-imposed web-filters, or school kids could evade their =
school system's web-filters, etc. &nbsp;The initial reaction from content=
 inspectors would be do develop capabilities to detect MPTCP (likely base=
d on options usage), and to either block or
 force fallback to standard TCP. &nbsp;A significant concern is that this=
 is where the incentive ends. &nbsp;MPTCP is an evasion method, so mitiga=
te the vulnerability.&nbsp;</div>
<div><br>
</div>
<div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: med=
ium; font-style: normal; font-variant: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
uto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-li=
ne-break: after-white-space; ">
I would prefer to consider how to support MPTCP, perhaps in the form of a=
n application-layer gateway and/or modification of content-inspection eng=
ines to deal with aggregation of sub-flows for inspection. &nbsp;This lin=
e of thought lends itself to a philosophical
 discussion, as to if we intend MPTCP to be used to evade content inspect=
ion, or if we are looking to improve the performance of TCP-based applica=
tions. &nbsp;I mention this because it would be desirable for the protoco=
l to assist, or at least not hinder, the ability
 to identify the multiple sub-flows that create an MPTCP session.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: med=
ium; font-style: normal; font-variant: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
uto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-li=
ne-break: after-white-space; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: med=
ium; font-style: normal; font-variant: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
uto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-li=
ne-break: after-white-space; ">
Eventually, I see the rise of middleboxes as MPTCP proxies, whether they =
are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodolog=
ies of SSL inspection today. &nbsp;I am interested in these use-cases bec=
ause without them, the default will be to block/fallback,
 which ultimately isn't useful relative to MPTCP.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: med=
ium; font-style: normal; font-variant: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
uto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-li=
ne-break: after-white-space; ">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: med=
ium; font-style: normal; font-variant: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
uto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-li=
ne-break: after-white-space; ">
My US $.02</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: med=
ium; font-style: normal; font-variant: normal; font-weight: normal; lette=
r-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-a=
uto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-strok=
e-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-li=
ne-break: after-white-space; ">
Ed Lopez&nbsp;</div>
</div>
<br>
<div>
<div>On Sep 4, 2013, at 3:31 AM, <a href=3D"mailto:philip.eardley@bt.com"=
>philip.eardley@bt.com</a> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" style=3D"font-family: =
Helvetica; font-size: medium; font-style: normal; font-variant: normal; f=
ont-weight: normal; letter-spacing: normal; line-height: normal; orphans:=
 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; whi=
te-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust:=
 auto; -webkit-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">Just to let you know. The Security Ads are kindly finding us a secu=
rity advisor, but no luck yet. So we may have to delay this slightly.<o:p=
></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">Also, it would be good if there was some discussion on the mailing =
list before the call.<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">phil<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">&nbsp;</span></div>
<div style=3D"border-style: none none none solid; border-left-width: 1.5p=
t; border-left-color: blue; padding: 0cm 0cm 0cm 4pt; ">
<div>
<div style=3D"border-style: solid none none; border-top-width: 1pt; borde=
r-top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sa=
ns-serif; ">From:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt=
; font-family: Tahoma, sans-serif; "><span class=3D"Apple-converted-space=
">&nbsp;</span>Eardley,PL,Philip,TUB8 R<span class=3D"Apple-converted-spa=
ce">&nbsp;</span><br>
<b>Sent:</b><span class=3D"Apple-converted-space">&nbsp;</span>21 August =
2013 08:36<br>
<b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span>Eardley,PL,P=
hilip,TUB8 R; <a href=3D"mailto:multipathtcp@ietf.org">
multipathtcp@ietf.org</a><br>
<b>Subject:</b><span class=3D"Apple-converted-space">&nbsp;</span>RE: [mu=
ltipathtcp] MPTCP interim (audio) meeting on security, late September<o:p=
></o:p></span></div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">Just a reminder, as I know a lot of people have been on holiday, pl=
ease fill in the doodle<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">Thanks<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">phil<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: bl=
ue; ">&nbsp;</span></div>
<div style=3D"border-style: none none none solid; border-left-width: 1.5p=
t; border-left-color: blue; padding: 0cm 0cm 0cm 4pt; ">
<div>
<div style=3D"border-style: solid none none; border-top-width: 1pt; borde=
r-top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; ">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sa=
ns-serif; ">From:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt=
; font-family: Tahoma, sans-serif; "><span class=3D"Apple-converted-space=
">&nbsp;</span><a href=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"=
color: purple; text-decoration: underline; ">multipathtcp-bounces@ietf.or=
g</a><span class=3D"Apple-converted-space">&nbsp;</span>[<a href=3D"mailt=
o:multipathtcp-bounces@ietf.org" style=3D"color: purple; text-decoration:=
 underline; ">mailto:multipathtcp-bounces@ietf.org</a>]<span class=3D"App=
le-converted-space">&nbsp;</span><b>On
 Behalf Of<span class=3D"Apple-converted-space">&nbsp;</span></b><a href=3D=
"mailto:philip.eardley@bt.com" style=3D"color: purple; text-decoration: u=
nderline; ">philip.eardley@bt.com</a><br>
<b>Sent:</b><span class=3D"Apple-converted-space">&nbsp;</span>06 August =
2013 13:49<br>
<b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"m=
ailto:multipathtcp@ietf.org" style=3D"color: purple; text-decoration: und=
erline; ">multipathtcp@ietf.org</a><br>
<b>Subject:</b><span class=3D"Apple-converted-space">&nbsp;</span>[multip=
athtcp] MPTCP interim (audio) meeting on security, late September<o:p></o=
:p></span></div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">We thin=
k it would a good idea to have an interim (audio) meeting, in order to ma=
ke progress on advancing RFC 6824 on the standards track.<o:p></o:p></spa=
n></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">&nbsp;<=
/span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">We will=
 discuss the security of the MPTCP protocol. The aim is to reach consensu=
s on what security improvements are needed - and what are not needed - in=
 order to progress MPTCP on the Standards
 track. We hope to cover both the threat(s) that we will handle and, at a=
 high-level, the solutions that will be defined.<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">&nbsp;<=
/span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">Please =
fill in the doodle at<span class=3D"Apple-converted-space">&nbsp;</span><=
a href=3D"http://doodle.com/xdf8eaiavvna9bcy#table" style=3D"color: purpl=
e; text-decoration: underline; ">http://doodle.com/xdf8eaiavvna9bcy#table=
</a><o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">&nbsp;<=
/span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">For pre=
vious MPTCP WG interims, ~3pm GMT has been OK. Please shout if the time i=
s no good for you.<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">&nbsp;<=
/span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">In the =
meantime, please keep discussing MPTCP=92s security on the list!<o:p></o:=
p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">&nbsp;<=
/span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">Thanks,=
<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">Best wi=
shes<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Cal=
ibri, sans-serif; ">
<span style=3D"font-size: 12pt; font-family: Arial, sans-serif; ">Phil &a=
mp; Yoshifumi<o:p></o:p></span></div>
</div>
</div>
</div>
_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/multipathtcp</div>
</blockquote>
</div>
<br>

<font bgcolor=3D"#ffffff" color=3D"#000000"><b><BR><HR>
***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***
<BR><HR></b></font>
</body>
</html>


--_000_0215C1A280E14BCC8A43A4530D231B27fortinetcom_--

From philip.eardley@bt.com  Fri Sep  6 02:58:55 2013
Return-Path: <philip.eardley@bt.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 3CF5C11E80E6 for <multipathtcp@ietfa.amsl.com>; Fri,  6 Sep 2013 02:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNNYhRL+whIb for <multipathtcp@ietfa.amsl.com>; Fri,  6 Sep 2013 02:58:48 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.com [62.239.224.236]) by ietfa.amsl.com (Postfix) with ESMTP id 2C3B921F9E6A for <multipathtcp@ietf.org>; Fri,  6 Sep 2013 02:58:46 -0700 (PDT)
Received: from EVMHT68-UKRD.domain1.systemhost.net (10.36.3.105) by RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP Server (TLS) id 8.3.298.1; Fri, 6 Sep 2013 10:58:39 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.113]) by EVMHT68-UKRD.domain1.systemhost.net ([10.36.3.105]) with mapi; Fri, 6 Sep 2013 10:58:39 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Date: Fri, 6 Sep 2013 10:58:38 +0100
Thread-Topic: MPTCP interim (audio) meeting on security - please update your doodle
Thread-Index: Ac6q56igkYLPcnOuSlKP0O5J3fem7w==
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94AFF59@EMV67-UKRD.domain1.systemhost.net>
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_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94AFF59EMV67UKRDdoma_"
MIME-Version: 1.0
Subject: [multipathtcp] MPTCP interim (audio) meeting on security - please update your doodle
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 06 Sep 2013 09:58:55 -0000

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94AFF59EMV67UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I extended the doodle to the first week of October.
Please could you update your entry or fill in

Sorry for the trouble

Thanks
phil

From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org] =
On Behalf Of philip.eardley@bt.com
Sent: 04 September 2013 08:31
To: multipathtcp@ietf.org
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just to let you know. The Security Ads are kindly finding us a security adv=
isor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list bef=
ore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp@iet=
f.org>
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just a reminder, as I know a lot of people have been on holiday, please fil=
l in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> [=
mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com<ma=
ilto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late Sep=
tember

We think it would a good idea to have an interim (audio) meeting, in order =
to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach con=
sensus on what security improvements are needed - and what are not needed -=
 in order to progress MPTCP on the Standards track. We hope to cover both t=
he threat(s) that we will handle and, at a high-level, the solutions that w=
ill be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the t=
ime is no good for you.

In the meantime, please keep discussing MPTCP's security on the list!

Thanks,
Best wishes
Phil & Yoshifumi

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94AFF59EMV67UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>I extended the=
 doodle to the first week of October.<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color=
:blue'>Please could you update your entry or fill in<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sa=
ns-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>So=
rry for the trouble<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;fon=
t-family:"Arial","sans-serif";color:blue'>Thanks<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-s=
erif";color:blue'>phil<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nb=
sp;</o:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;=
padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid =
#B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=
=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fa=
reast-language:EN-GB'>From:</span></b><span lang=3DEN-US style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> mult=
ipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org] <b>On Beha=
lf Of </b>philip.eardley@bt.com<br><b>Sent:</b> 04 September 2013 08:31<br>=
<b>To:</b> multipathtcp@ietf.org<br><b>Subject:</b> Re: [multipathtcp] MPTC=
P interim (audio) meeting on security, late September<o:p></o:p></span></p>=
</div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>=
<span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue=
'>Just to let you know. The Security Ads are kindly finding us a security a=
dvisor, but no luck yet. So we may have to delay this slightly.<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:=
"Arial","sans-serif";color:blue'>Also, it would be good if there was some d=
iscussion on the mailing list before the call.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-ser=
if";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>phil<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font=
-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div s=
tyle=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'=
><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0p=
t 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From=
:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif";mso-fareast-language:EN-GB'> Eardley,PL,Philip,TUB8 R <br><=
b>Sent:</b> 21 August 2013 08:36<br><b>To:</b> Eardley,PL,Philip,TUB8 R; <a=
 href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br><b>Subj=
ect:</b> RE: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family=
:"Arial","sans-serif";color:blue'>Just a reminder, as I know a lot of peopl=
e have been on holiday, please fill in the doodle <o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans=
-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Than=
ks<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0p=
t;font-family:"Arial","sans-serif";color:blue'>phil<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","san=
s-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;=
border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'=
border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p cl=
ass=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family=
:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><span la=
ng=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-=
fareast-language:EN-GB'> <a href=3D"mailto:multipathtcp-bounces@ietf.org">m=
ultipathtcp-bounces@ietf.org</a> [<a href=3D"mailto:multipathtcp-bounces@ie=
tf.org">mailto:multipathtcp-bounces@ietf.org</a>] <b>On Behalf Of </b><a hr=
ef=3D"mailto:philip.eardley@bt.com">philip.eardley@bt.com</a><br><b>Sent:</=
b> 06 August 2013 13:49<br><b>To:</b> <a href=3D"mailto:multipathtcp@ietf.o=
rg">multipathtcp@ietf.org</a><br><b>Subject:</b> [multipathtcp] MPTCP inter=
im (audio) meeting on security, late September<o:p></o:p></span></p></div><=
/div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>We think it woul=
d a good idea to have an interim (audio) meeting, in order to make progress=
 on advancing RFC 6824 on the standards track.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-ser=
if"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:12.0pt;font-family:"Arial","sans-serif"'>We will discuss the security o=
f the MPTCP protocol. The aim is to reach consensus on what security improv=
ements are needed - and what are not needed - in order to progress MPTCP on=
 the Standards track. We hope to cover both the threat(s) that we will hand=
le and, at a high-level, the solutions that will be defined.<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ar=
ial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>Please fill in t=
he doodle at <a href=3D"http://doodle.com/xdf8eaiavvna9bcy#table">http://do=
odle.com/xdf8eaiavvna9bcy#table</a> <o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p>=
&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt=
;font-family:"Arial","sans-serif"'>For previous MPTCP WG interims, ~3pm GMT=
 has been OK. Please shout if the time is no good for you.<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Aria=
l","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>In the meantime, p=
lease keep discussing MPTCP&#8217;s security on the list!<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial=
","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>Thanks, <o:p></o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family=
:"Arial","sans-serif"'>Best wishes<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>Phil &a=
mp; Yoshifumi<o:p></o:p></span></p></div></div></div></div></body></html>=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94AFF59EMV67UKRDdoma_--

From scott.brim@gmail.com  Sun Sep  8 04:13:30 2013
Return-Path: <scott.brim@gmail.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 3DA0621F9FD0 for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 04:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83vPuqwY-vTO for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 04:13:29 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id D0D3621F9D15 for <multipathtcp@ietf.org>; Sun,  8 Sep 2013 04:13:28 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id uz19so5069015obc.35 for <multipathtcp@ietf.org>; Sun, 08 Sep 2013 04:13:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LnnxfWsQod3VsQGmr08OyoZqd8UwH8hUaecLx5Wvqag=; b=tAAW66rJdouenNFD1/J94UP9iP9BrErNtD57p+zOk0sOmmdYtPdq5NItPPicpqhrZv /JqaniMHYgGQQmu3JwG6f1FOq0wBGxQde2aiJCtlp2ZszyFjApb2YGY7DnUGMcIXEyx+ +67gHNOT8la5NoBItUvgUiXV5ukaqxqhv70jIOCRz+eA9UiD8po33bky9UrXZ9L8Yvx6 Fji9smBGyKHU/6QHBf6qGldjJhPoND8a/7qBEkfUdkwtw+nr6CPKRy28kRe5H0mLWlis GRsNbbWlfHdSloCf+0LiGiqtY6u/YQteHtE7xez/uMy2Y+iZZxY7DV2yYluoWglna5U4 bchw==
MIME-Version: 1.0
X-Received: by 10.60.43.131 with SMTP id w3mr8031240oel.10.1378638808342; Sun, 08 Sep 2013 04:13:28 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Sun, 8 Sep 2013 04:13:28 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Sun, 8 Sep 2013 04:13:28 -0700 (PDT)
In-Reply-To: <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
Date: Sun, 8 Sep 2013 07:13:28 -0400
Message-ID: <CAPv4CP-zpUS9vmXdLzAo63UzaQnDBvZ5Gz152mxeuzVXMb3-+Q@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Edward Lopez <elopez@fortinet.com>
Content-Type: multipart/alternative; boundary=001a113346ce71e85304e5dd5c77
Cc: multipathtcp List <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 08 Sep 2013 11:13:30 -0000

--001a113346ce71e85304e5dd5c77
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It doesn't look like anyone replied to this.  Yes there's an issue with
multipathing and IPS. But rather than isolate MPTCP to a single
interconnection point, why not get IPSs to coordinate with each other? That
way you're opening the door to the future instead of trapping the Internet
in the past.
On Sep 5, 2013 1:25 PM, "Edward Lopez" <elopez@fortinet.com> wrote:

>  Phil,
>
>  I'm aware that I am relatively new to the WG and IETF as a whole (IETF
> 87 Berlin was my first meeting).  But I do have a long history of securit=
y
> and networking protocols, currently working and having worked for a numbe=
r
> of security appliance (middlebox) vendors.
>
>  My initial review of MPTCP is that I would have to consider it an
> evasion technique from a content inspection standpoint.  Generally, conte=
nt
> inspection engines are designed to operate as either flow-based or
> transparent-proxy.  A flow-based engine is generally used by IPS systems,
> but has now expanded to support many types of content inspection, most
> notably application control functionality of next-generation firewalls
> (NGFWs).  The limitation of a flow-based engine is that it looks at data =
in
> as a stream, generally without reordering and limited data reassembly.   =
A
> transparent proxy engine fully buffers and reassembles the data in the
> context of specific protocols, then inspects this traffic in context.
>  Transparent proxies are useful when the inspection device has to interac=
t
> within the protocol, such as in web-filtering solutions where a block
> message is sent back to an offending user.  However, both of these conten=
t
> inspection engine types have a general model centered around the session
> paradigm.  an MPTCP session is in effect an aggregate of multiple TCP
> sessions (sub flows), so in effect has characteristics of a protocol-base=
d
> application, similar to FTP, VoIP, etc.
>
>  The effect of MPTCP on content inspection engines is that it can be used
> as an evasion technique.  For example, I could envision the use of
> multi-homed MPTCP-based proxy engines out on the Internet, such that MPTC=
P
> based hosts in net repressive countries could evade state-imposed
> web-filters, or school kids could evade their school system's web-filters=
,
> etc.  The initial reaction from content inspectors would be do develop
> capabilities to detect MPTCP (likely based on options usage), and to eith=
er
> block or force fallback to standard TCP.  A significant concern is that
> this is where the incentive ends.  MPTCP is an evasion method, so mitigat=
e
> the vulnerability.
>
>   I would prefer to consider how to support MPTCP, perhaps in the form of
> an application-layer gateway and/or modification of content-inspection
> engines to deal with aggregation of sub-flows for inspection.  This line =
of
> thought lends itself to a philosophical discussion, as to if we intend
> MPTCP to be used to evade content inspection, or if we are looking to
> improve the performance of TCP-based applications.  I mention this becaus=
e
> it would be desirable for the protocol to assist, or at least not hinder,
> the ability to identify the multiple sub-flows that create an MPTCP sessi=
on.
>
>  Eventually, I see the rise of middleboxes as MPTCP proxies, whether they
> are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the
> methodologies of SSL inspection today.  I am interested in these use-case=
s
> because without them, the default will be to block/fallback, which
> ultimately isn't useful relative to MPTCP.
>
>  My US $.02
>  Ed Lopez
>
>  On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
>
>   Just to let you know. The Security Ads are kindly finding us a security
> advisor, but no luck yet. So we may have to delay this slightly.****
>  Also, it would be good if there was some discussion on the mailing list
> before the call.****
>
>  phil****
>
>   *From:* Eardley,PL,Philip,TUB8 R
> *Sent:* 21 August 2013 08:36
> *To:* Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
> *Subject:* RE: [multipathtcp] MPTCP interim (audio) meeting on security,
> late September****
>   ** **
>  Just a reminder, as I know a lot of people have been on holiday, please
> fill in the doodle****
>
>  Thanks****
>  phil****
>
>   *From:* multipathtcp-bounces@ietf.org [
> mailto:multipathtcp-bounces@ietf.org <multipathtcp-bounces@ietf.org>] *On
> Behalf Of *philip.eardley@bt.com
> *Sent:* 06 August 2013 13:49
> *To:* multipathtcp@ietf.org
> *Subject:* [multipathtcp] MPTCP interim (audio) meeting on security, late
> September****
>   ** **
>  We think it would a good idea to have an interim (audio) meeting, in
> order to make progress on advancing RFC 6824 on the standards track.****
>
>  We will discuss the security of the MPTCP protocol. The aim is to reach
> consensus on what security improvements are needed - and what are not
> needed - in order to progress MPTCP on the Standards track. We hope to
> cover both the threat(s) that we will handle and, at a high-level, the
> solutions that will be defined.****
>
>  Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table***=
*
>
>  For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if
> the time is no good for you.****
>
>  In the meantime, please keep discussing MPTCP=92s security on the list!*=
***
>
>  Thanks,****
>  Best wishes****
>  Phil & Yoshifumi****
>   _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
> *
> ------------------------------
> *** Please note that this message and any attachments may contain
> confidential and proprietary material and information and are intended on=
ly
> for the use of the intended recipient(s). If you are not the intended
> recipient, you are hereby notified that any review, use, disclosure,
> dissemination, distribution or copying of this message and any attachment=
s
> is strictly prohibited. If you have received this email in error, please
> immediately notify the sender and destroy this e-mail and any attachments
> and all copies, whether electronic or printed. Please also note that any
> views, opinions, conclusions or commitments expressed in this message are
> those of the individual sender and do not necessarily reflect the views o=
f
> Fortinet, Inc., its affiliates, and emails are not binding on Fortinet an=
d
> only a writing manually signed by Fortinet's General Counsel can be a
> binding commitment of Fortinet to Fortinet's customers or partners. Thank
> you. ***
> ------------------------------
> *
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>

--001a113346ce71e85304e5dd5c77
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">It doesn&#39;t look like anyone replied to this.=A0 Yes ther=
e&#39;s an issue with multipathing and IPS. But rather than isolate MPTCP t=
o a single interconnection point, why not get IPSs to coordinate with each =
other? That way you&#39;re opening the door to the future instead of trappi=
ng the Internet in the past. </p>

<div class=3D"gmail_quote">On Sep 5, 2013 1:25 PM, &quot;Edward Lopez&quot;=
 &lt;<a href=3D"mailto:elopez@fortinet.com">elopez@fortinet.com</a>&gt; wro=
te:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div style=3D"word-wrap:break-word">
<div>Phil,</div>
<div><br>
</div>
<div>I&#39;m aware that I am relatively new to the WG and IETF as a whole (=
IETF 87 Berlin was my first meeting). =A0But I do have a long history of se=
curity and networking protocols, currently working and having worked for a =
number of security appliance (middlebox)
 vendors.</div>
<div><br>
</div>
<div>My initial review of MPTCP is that I would have to consider it an evas=
ion technique from a content inspection standpoint. =A0Generally, content i=
nspection engines are designed to operate as either flow-based or transpare=
nt-proxy. =A0A flow-based engine is
 generally used by IPS systems, but has now expanded to support many types =
of content inspection, most notably application control functionality of ne=
xt-generation firewalls (NGFWs). =A0The limitation of a flow-based engine i=
s that it looks at data in as a stream,
 generally without reordering and limited data reassembly. =A0 A transparen=
t proxy engine fully buffers and reassembles the data in the context of spe=
cific protocols, then inspects this traffic in context. =A0Transparent prox=
ies are useful when the inspection device
 has to interact within the protocol, such as in web-filtering solutions wh=
ere a block message is sent back to an offending user. =A0However, both of =
these content inspection engine types have a general model centered around =
the session paradigm. =A0an MPTCP session
 is in effect an aggregate of multiple TCP sessions (sub flows), so in effe=
ct has characteristics of a protocol-based application, similar to FTP, VoI=
P, etc.</div>
<div><br>
</div>
<div>The effect of MPTCP on content inspection engines is that it can be us=
ed as an evasion technique. =A0For example, I could envision the use of mul=
ti-homed MPTCP-based proxy engines out on the Internet, such that MPTCP bas=
ed hosts in net repressive countries
 could evade state-imposed web-filters, or school kids could evade their sc=
hool system&#39;s web-filters, etc. =A0The initial reaction from content in=
spectors would be do develop capabilities to detect MPTCP (likely based on =
options usage), and to either block or
 force fallback to standard TCP. =A0A significant concern is that this is w=
here the incentive ends. =A0MPTCP is an evasion method, so mitigate the vul=
nerability.=A0</div>
<div><br>
</div>
<div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

I would prefer to consider how to support MPTCP, perhaps in the form of an =
application-layer gateway and/or modification of content-inspection engines=
 to deal with aggregation of sub-flows for inspection. =A0This line of thou=
ght lends itself to a philosophical
 discussion, as to if we intend MPTCP to be used to evade content inspectio=
n, or if we are looking to improve the performance of TCP-based application=
s. =A0I mention this because it would be desirable for the protocol to assi=
st, or at least not hinder, the ability
 to identify the multiple sub-flows that create an MPTCP session.</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

<br>
</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

Eventually, I see the rise of middleboxes as MPTCP proxies, whether they ar=
e TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodologies =
of SSL inspection today. =A0I am interested in these use-cases because with=
out them, the default will be to block/fallback,
 which ultimately isn&#39;t useful relative to MPTCP.</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

<br>
</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

My US $.02</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

Ed Lopez=A0</div>
</div>
<br>
<div>
<div>On Sep 4, 2013, at 3:31 AM, <a href=3D"mailto:philip.eardley@bt.com" t=
arget=3D"_blank">philip.eardley@bt.com</a> wrote:</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" style=3D"font-family:Hel=
vetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:n=
ormal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">

<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Just=
 to let you know. The Security Ads are kindly finding us a security advisor=
, but no luck yet. So we may have to delay this slightly.<u></u><u></u></sp=
an></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Also=
, it would be good if there was some discussion on the mailing list before =
the call.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">phil=
<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;bor=
der-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-top-=
color:rgb(181,196,223);padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt;font-famil=
y:Tahoma,sans-serif"><span>=A0</span>Eardley,PL,Philip,TUB8 R<span>=A0</spa=
n><br>
<b>Sent:</b><span>=A0</span>21 August 2013 08:36<br>
<b>To:</b><span>=A0</span>Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:multi=
pathtcp@ietf.org" target=3D"_blank">
multipathtcp@ietf.org</a><br>
<b>Subject:</b><span>=A0</span>RE: [multipathtcp] MPTCP interim (audio) mee=
ting on security, late September<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Just=
 a reminder, as I know a lot of people have been on holiday, please fill in=
 the doodle<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Than=
ks<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">phil=
<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;bor=
der-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-top-=
color:rgb(181,196,223);padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt;font-famil=
y:Tahoma,sans-serif"><span>=A0</span><a href=3D"mailto:multipathtcp-bounces=
@ietf.org" style=3D"color:purple;text-decoration:underline" target=3D"_blan=
k">multipathtcp-bounces@ietf.org</a><span>=A0</span>[<a href=3D"mailto:mult=
ipathtcp-bounces@ietf.org" style=3D"color:purple;text-decoration:underline"=
 target=3D"_blank">mailto:multipathtcp-bounces@ietf.org</a>]<span>=A0</span=
><b>On
 Behalf Of<span>=A0</span></b><a href=3D"mailto:philip.eardley@bt.com" styl=
e=3D"color:purple;text-decoration:underline" target=3D"_blank">philip.eardl=
ey@bt.com</a><br>
<b>Sent:</b><span>=A0</span>06 August 2013 13:49<br>
<b>To:</b><span>=A0</span><a href=3D"mailto:multipathtcp@ietf.org" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank">multipathtcp@iet=
f.org</a><br>
<b>Subject:</b><span>=A0</span>[multipathtcp] MPTCP interim (audio) meeting=
 on security, late September<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">We think it wou=
ld a good idea to have an interim (audio) meeting, in order to make progres=
s on advancing RFC 6824 on the standards track.<u></u><u></u></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">We will discuss=
 the security of the MPTCP protocol. The aim is to reach consensus on what =
security improvements are needed - and what are not needed - in order to pr=
ogress MPTCP on the Standards
 track. We hope to cover both the threat(s) that we will handle and, at a h=
igh-level, the solutions that will be defined.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Please fill in =
the doodle at<span>=A0</span><a href=3D"http://doodle.com/xdf8eaiavvna9bcy#=
table" style=3D"color:purple;text-decoration:underline" target=3D"_blank">h=
ttp://doodle.com/xdf8eaiavvna9bcy#table</a><u></u><u></u></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">For previous MP=
TCP WG interims, ~3pm GMT has been OK. Please shout if the time is no good =
for you.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">In the meantime=
, please keep discussing MPTCP=92s security on the list!<u></u><u></u></spa=
n></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Thanks,<u></u><=
u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Best wishes<u><=
/u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Phil &amp; Yosh=
ifumi<u></u><u></u></span></div>
</div>
</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></div>
</blockquote>
</div>
<br>

<font bgcolor=3D"#ffffff" color=3D"#000000"><b><br><hr>
***  Please note that this message and any attachments may contain confiden=
tial=20
and proprietary material and information and are intended only for the use =
of=20
the intended recipient(s). If you are not the intended recipient, you are h=
ereby=20
notified that any review, use, disclosure, dissemination, distribution or c=
opying=20
of this message and any attachments is strictly prohibited. If you have rec=
eived=20
this email in error, please immediately notify the sender and destroy this =
e-mail=20
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments expre=
ssed=20
in this message are those of the individual sender and do not necessarily r=
eflect=20
the views of Fortinet, Inc., its affiliates, and emails are not binding on=
=20
Fortinet and only a writing manually signed by Fortinet&#39;s General Couns=
el can be=20
a binding commitment of Fortinet to Fortinet&#39;s customers or partners. T=
hank you. ***
<br><hr></b></font>
</div>


<br>_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.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>
<br></blockquote></div>

--001a113346ce71e85304e5dd5c77--

From elopez@fortinet.com  Sun Sep  8 08:22:14 2013
Return-Path: <elopez@fortinet.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 3E47811E8109 for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 08:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yshYDQzuj1i for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 08:22:10 -0700 (PDT)
Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by ietfa.amsl.com (Postfix) with ESMTP id ED14E11E8105 for <multipathtcp@ietf.org>; Sun,  8 Sep 2013 08:22:09 -0700 (PDT)
From: Edward Lopez <elopez@fortinet.com>
To: Scott Brim <scott.brim@gmail.com>
Thread-Topic: [multipathtcp] MPTCP interim (audio) meeting on security, late September
Thread-Index: AQHOnkEYnt/Sx47MpE2VypdHdwlkaJm1ulSAgAI4KICABE89AP//0CK7
Date: Sun, 8 Sep 2013 15:22:08 +0000
Message-ID: <1848EE0D-3F26-488F-B9B3-A2A106767A8F@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>, <CAPv4CP-zpUS9vmXdLzAo63UzaQnDBvZ5Gz152mxeuzVXMb3-+Q@mail.gmail.com>
In-Reply-To: <CAPv4CP-zpUS9vmXdLzAo63UzaQnDBvZ5Gz152mxeuzVXMb3-+Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_1848EE0D3F26488FB9B3A2A106767A8Ffortinetcom_"
MIME-Version: 1.0
X-FEAS-SYSTEM-WL: 192.168.221.213
Cc: multipathtcp List <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 08 Sep 2013 15:22:14 -0000

--_000_1848EE0D3F26488FB9B3A2A106767A8Ffortinetcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

It's exceedingly difficult to sync memory buffer states at anything other=
 than short distances if at all, and still have an IPS perform in-line pr=
otection.  However, I will concede the possibility for IDS (just detectio=
n) to possibly do this.

This is not just a technical issue, but rather a compliance/political one=
.  Consider PCI, HIPPA, etc. which mandate the use of IPS.  It is inevita=
ble that IPS systems will learn to detect and mitigate MPTCP, just as it =
is that third-party MPTCP proxies will be built solely to evade content f=
ilters.  I for one would hate to see MPTCP relegated to intradomain use, =
because we failed to foresee the perceived security issues.

Ed Lopez

Sent from my iPhone ... Sorry for any auto-correct errors

On Sep 8, 2013, at 7:13 AM, "Scott Brim" <scott.brim@gmail.com<mailto:sco=
tt.brim@gmail.com>> wrote:


It doesn't look like anyone replied to this.  Yes there's an issue with m=
ultipathing and IPS. But rather than isolate MPTCP to a single interconne=
ction point, why not get IPSs to coordinate with each other? That way you=
're opening the door to the future instead of trapping the Internet in th=
e past.

On Sep 5, 2013 1:25 PM, "Edward Lopez" <elopez@fortinet.com<mailto:elopez=
@fortinet.com>> wrote:
Phil,

I'm aware that I am relatively new to the WG and IETF as a whole (IETF 87=
 Berlin was my first meeting).  But I do have a long history of security =
and networking protocols, currently working and having worked for a numbe=
r of security appliance (middlebox) vendors.

My initial review of MPTCP is that I would have to consider it an evasion=
 technique from a content inspection standpoint.  Generally, content insp=
ection engines are designed to operate as either flow-based or transparen=
t-proxy.  A flow-based engine is generally used by IPS systems, but has n=
ow expanded to support many types of content inspection, most notably app=
lication control functionality of next-generation firewalls (NGFWs).  The=
 limitation of a flow-based engine is that it looks at data in as a strea=
m, generally without reordering and limited data reassembly.   A transpar=
ent proxy engine fully buffers and reassembles the data in the context of=
 specific protocols, then inspects this traffic in context.  Transparent =
proxies are useful when the inspection device has to interact within the =
protocol, such as in web-filtering solutions where a block message is sen=
t back to an offending user.  However, both of these content inspection e=
ngine types have a general model centered around the session paradigm.  a=
n MPTCP session is in effect an aggregate of multiple TCP sessions (sub f=
lows), so in effect has characteristics of a protocol-based application, =
similar to FTP, VoIP, etc.

The effect of MPTCP on content inspection engines is that it can be used =
as an evasion technique.  For example, I could envision the use of multi-=
homed MPTCP-based proxy engines out on the Internet, such that MPTCP base=
d hosts in net repressive countries could evade state-imposed web-filters=
, or school kids could evade their school system's web-filters, etc.  The=
 initial reaction from content inspectors would be do develop capabilitie=
s to detect MPTCP (likely based on options usage), and to either block or=
 force fallback to standard TCP.  A significant concern is that this is w=
here the incentive ends.  MPTCP is an evasion method, so mitigate the vul=
nerability.

I would prefer to consider how to support MPTCP, perhaps in the form of a=
n application-layer gateway and/or modification of content-inspection eng=
ines to deal with aggregation of sub-flows for inspection.  This line of =
thought lends itself to a philosophical discussion, as to if we intend MP=
TCP to be used to evade content inspection, or if we are looking to impro=
ve the performance of TCP-based applications.  I mention this because it =
would be desirable for the protocol to assist, or at least not hinder, th=
e ability to identify the multiple sub-flows that create an MPTCP session=
.

Eventually, I see the rise of middleboxes as MPTCP proxies, whether they =
are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodolog=
ies of SSL inspection today.  I am interested in these use-cases because =
without them, the default will be to block/fallback, which ultimately isn=
't useful relative to MPTCP.

My US $.02
Ed Lopez

On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com<mailto:philip.eardley@b=
t.com> wrote:

Just to let you know. The Security Ads are kindly finding us a security a=
dvisor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list b=
efore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp@i=
etf.org>
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te September

Just a reminder, as I know a lot of people have been on holiday, please f=
ill in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org>=
 [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.co=
m<mailto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late S=
eptember

We think it would a good idea to have an interim (audio) meeting, in orde=
r to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach c=
onsensus on what security improvements are needed - and what are not need=
ed - in order to progress MPTCP on the Standards track. We hope to cover =
both the threat(s) that we will handle and, at a high-level, the solution=
s that will be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the=
 time is no good for you.

In the meantime, please keep discussing MPTCP=92s security on the list!

Thanks,
Best wishes
Phil & Yoshifumi
_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
https://www.ietf.org/mailman/listinfo/multipathtcp


________________________________
*** Please note that this message and any attachments may contain confide=
ntial and proprietary material and information and are intended only for =
the use of the intended recipient(s). If you are not the intended recipie=
nt, you are hereby notified that any review, use, disclosure, disseminati=
on, distribution or copying of this message and any attachments is strict=
ly prohibited. If you have received this email in error, please immediate=
ly notify the sender and destroy this e-mail and any attachments and all =
copies, whether electronic or printed. Please also note that any views, o=
pinions, conclusions or commitments expressed in this message are those o=
f the individual sender and do not necessarily reflect the views of Forti=
net, Inc., its affiliates, and emails are not binding on Fortinet and onl=
y a writing manually signed by Fortinet's General Counsel can be a bindin=
g commitment of Fortinet to Fortinet's customers or partners. Thank you. =
***
________________________________

_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
https://www.ietf.org/mailman/listinfo/multipathtcp



***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***

--_000_1848EE0D3F26488FB9B3A2A106767A8Ffortinetcom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows=
-1252">
</head>
<body dir=3D"auto">
<div>It's exceedingly difficult to sync memory buffer states at anything =
other than short distances if at all, and still have an IPS perform in-li=
ne protection. &nbsp;However, I will concede the possibility for IDS (jus=
t detection) to possibly do this.</div>
<div><br>
</div>
<div>This is not just a technical issue, but rather a compliance/politica=
l one. &nbsp;Consider PCI, HIPPA, etc. which mandate the use of IPS. &nbs=
p;It is inevitable that IPS systems will learn to detect and mitigate MPT=
CP, just as it is that third-party MPTCP proxies
 will be built solely to evade content filters. &nbsp;I for one would hat=
e to see MPTCP relegated to intradomain use, because we failed to foresee=
 the perceived security issues.<br>
<br>
<div>Ed Lopez</div>
<div><br>
</div>
Sent from my iPhone ... Sorry for any auto-correct errors</div>
<div><br>
On Sep 8, 2013, at 7:13 AM, &quot;Scott Brim&quot; &lt;<a href=3D"mailto:=
scott.brim@gmail.com">scott.brim@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<p dir=3D"ltr">It doesn't look like anyone replied to this.&nbsp; Yes the=
re's an issue with multipathing and IPS. But rather than isolate MPTCP to=
 a single interconnection point, why not get IPSs to coordinate with each=
 other? That way you're opening the door to the
 future instead of trapping the Internet in the past. </p>
<div class=3D"gmail_quote">On Sep 5, 2013 1:25 PM, &quot;Edward Lopez&quo=
t; &lt;<a href=3D"mailto:elopez@fortinet.com">elopez@fortinet.com</a>&gt;=
 wrote:<br type=3D"attribution">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">
<div>Phil,</div>
<div><br>
</div>
<div>I'm aware that I am relatively new to the WG and IETF as a whole (IE=
TF 87 Berlin was my first meeting). &nbsp;But I do have a long history of=
 security and networking protocols, currently working and having worked f=
or a number of security appliance (middlebox)
 vendors.</div>
<div><br>
</div>
<div>My initial review of MPTCP is that I would have to consider it an ev=
asion technique from a content inspection standpoint. &nbsp;Generally, co=
ntent inspection engines are designed to operate as either flow-based or =
transparent-proxy. &nbsp;A flow-based engine is
 generally used by IPS systems, but has now expanded to support many type=
s of content inspection, most notably application control functionality o=
f next-generation firewalls (NGFWs). &nbsp;The limitation of a flow-based=
 engine is that it looks at data in as a stream,
 generally without reordering and limited data reassembly. &nbsp; A trans=
parent proxy engine fully buffers and reassembles the data in the context=
 of specific protocols, then inspects this traffic in context. &nbsp;Tran=
sparent proxies are useful when the inspection device
 has to interact within the protocol, such as in web-filtering solutions =
where a block message is sent back to an offending user. &nbsp;However, b=
oth of these content inspection engine types have a general model centere=
d around the session paradigm. &nbsp;an MPTCP session
 is in effect an aggregate of multiple TCP sessions (sub flows), so in ef=
fect has characteristics of a protocol-based application, similar to FTP,=
 VoIP, etc.</div>
<div><br>
</div>
<div>The effect of MPTCP on content inspection engines is that it can be =
used as an evasion technique. &nbsp;For example, I could envision the use=
 of multi-homed MPTCP-based proxy engines out on the Internet, such that =
MPTCP based hosts in net repressive countries
 could evade state-imposed web-filters, or school kids could evade their =
school system's web-filters, etc. &nbsp;The initial reaction from content=
 inspectors would be do develop capabilities to detect MPTCP (likely base=
d on options usage), and to either block or
 force fallback to standard TCP. &nbsp;A significant concern is that this=
 is where the incentive ends. &nbsp;MPTCP is an evasion method, so mitiga=
te the vulnerability.&nbsp;</div>
<div><br>
</div>
<div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;t=
ext-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:n=
ormal;text-transform:none;font-size:medium;white-space:normal;font-family=
:Helvetica;word-wrap:break-word;word-spacing:0px">
I would prefer to consider how to support MPTCP, perhaps in the form of a=
n application-layer gateway and/or modification of content-inspection eng=
ines to deal with aggregation of sub-flows for inspection. &nbsp;This lin=
e of thought lends itself to a philosophical
 discussion, as to if we intend MPTCP to be used to evade content inspect=
ion, or if we are looking to improve the performance of TCP-based applica=
tions. &nbsp;I mention this because it would be desirable for the protoco=
l to assist, or at least not hinder, the ability
 to identify the multiple sub-flows that create an MPTCP session.</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;t=
ext-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:n=
ormal;text-transform:none;font-size:medium;white-space:normal;font-family=
:Helvetica;word-wrap:break-word;word-spacing:0px">
<br>
</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;t=
ext-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:n=
ormal;text-transform:none;font-size:medium;white-space:normal;font-family=
:Helvetica;word-wrap:break-word;word-spacing:0px">
Eventually, I see the rise of middleboxes as MPTCP proxies, whether they =
are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodolog=
ies of SSL inspection today. &nbsp;I am interested in these use-cases bec=
ause without them, the default will be to block/fallback,
 which ultimately isn't useful relative to MPTCP.</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;t=
ext-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:n=
ormal;text-transform:none;font-size:medium;white-space:normal;font-family=
:Helvetica;word-wrap:break-word;word-spacing:0px">
<br>
</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;t=
ext-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:n=
ormal;text-transform:none;font-size:medium;white-space:normal;font-family=
:Helvetica;word-wrap:break-word;word-spacing:0px">
My US $.02</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;t=
ext-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:n=
ormal;text-transform:none;font-size:medium;white-space:normal;font-family=
:Helvetica;word-wrap:break-word;word-spacing:0px">
Ed Lopez&nbsp;</div>
</div>
<br>
<div>
<div>On Sep 4, 2013, at 3:31 AM, <a href=3D"mailto:philip.eardley@bt.com"=
 target=3D"_blank">
philip.eardley@bt.com</a> wrote:</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" style=3D"font-family:H=
elvetica;font-size:medium;font-style:normal;font-variant:normal;font-weig=
ht:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-aut=
o;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px=
">
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Ju=
st to let you know. The Security Ads are kindly finding us a security adv=
isor, but no luck yet. So we may have to delay this slightly.<u></u><u></=
u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Al=
so, it would be good if there was some discussion on the mailing list bef=
ore the call.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">&n=
bsp;</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">ph=
il<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">&n=
bsp;</span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;b=
order-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-to=
p-color:rgb(181,196,223);padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Tahoma,sans-s=
erif">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt;font-f=
amily:Tahoma,sans-serif"><span>&nbsp;</span>Eardley,PL,Philip,TUB8 R<span=
>&nbsp;</span><br>
<b>Sent:</b><span>&nbsp;</span>21 August 2013 08:36<br>
<b>To:</b><span>&nbsp;</span>Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:=
multipathtcp@ietf.org" target=3D"_blank">
multipathtcp@ietf.org</a><br>
<b>Subject:</b><span>&nbsp;</span>RE: [multipathtcp] MPTCP interim (audio=
) meeting on security, late September<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<u></u>&nbsp;<u></u></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Ju=
st a reminder, as I know a lot of people have been on holiday, please fil=
l in the doodle<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">&n=
bsp;</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Th=
anks<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">ph=
il<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">&n=
bsp;</span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;b=
order-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-to=
p-color:rgb(181,196,223);padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Tahoma,sans-s=
erif">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt;font-f=
amily:Tahoma,sans-serif"><span>&nbsp;</span><a href=3D"mailto:multipathtc=
p-bounces@ietf.org" style=3D"color:purple;text-decoration:underline" targ=
et=3D"_blank">multipathtcp-bounces@ietf.org</a><span>&nbsp;</span>[<a hre=
f=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"color:purple;text-dec=
oration:underline" target=3D"_blank">mailto:multipathtcp-bounces@ietf.org=
</a>]<span>&nbsp;</span><b>On
 Behalf Of<span>&nbsp;</span></b><a href=3D"mailto:philip.eardley@bt.com"=
 style=3D"color:purple;text-decoration:underline" target=3D"_blank">phili=
p.eardley@bt.com</a><br>
<b>Sent:</b><span>&nbsp;</span>06 August 2013 13:49<br>
<b>To:</b><span>&nbsp;</span><a href=3D"mailto:multipathtcp@ietf.org" sty=
le=3D"color:purple;text-decoration:underline" target=3D"_blank">multipath=
tcp@ietf.org</a><br>
<b>Subject:</b><span>&nbsp;</span>[multipathtcp] MPTCP interim (audio) me=
eting on security, late September<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<u></u>&nbsp;<u></u></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">We think it w=
ould a good idea to have an interim (audio) meeting, in order to make pro=
gress on advancing RFC 6824 on the standards track.<u></u><u></u></span><=
/div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">&nbsp;</span>=
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">We will discu=
ss the security of the MPTCP protocol. The aim is to reach consensus on w=
hat security improvements are needed - and what are not needed - in order=
 to progress MPTCP on the Standards track.
 We hope to cover both the threat(s) that we will handle and, at a high-l=
evel, the solutions that will be defined.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">&nbsp;</span>=
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Please fill i=
n the doodle at<span>&nbsp;</span><a href=3D"http://doodle.com/xdf8eaiavv=
na9bcy#table" style=3D"color:purple;text-decoration:underline" target=3D"=
_blank">http://doodle.com/xdf8eaiavvna9bcy#table</a><u></u><u></u></span>=
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">&nbsp;</span>=
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">For previous =
MPTCP WG interims, ~3pm GMT has been OK. Please shout if the time is no g=
ood for you.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">&nbsp;</span>=
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">In the meanti=
me, please keep discussing MPTCP=92s security on the list!<u></u><u></u><=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">&nbsp;</span>=
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Thanks,<u></u=
><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Best wishes<u=
></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,=
sans-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Phil &amp; Yo=
shifumi<u></u><u></u></span></div>
</div>
</div>
</div>
_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">multipathtcp@i=
etf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a></div>
</blockquote>
</div>
<br>
<font bgcolor=3D"#ffffff" color=3D"#000000"><b><br>
<hr>
*** Please note that this message and any attachments may contain confide=
ntial and proprietary material and information and are intended only for =
the use of the intended recipient(s). If you are not the intended recipie=
nt, you are hereby notified that any review,
 use, disclosure, dissemination, distribution or copying of this message =
and any attachments is strictly prohibited. If you have received this ema=
il in error, please immediately notify the sender and destroy this e-mail=
 and any attachments and all copies, whether
 electronic or printed. Please also note that any views, opinions, conclu=
sions or commitments expressed in this message are those of the individua=
l sender and do not necessarily reflect the views of Fortinet, Inc., its =
affiliates, and emails are not binding
 on Fortinet and only a writing manually signed by Fortinet's General Cou=
nsel can be a binding commitment of Fortinet to Fortinet's customers or p=
artners. Thank you. ***
<br>
<hr>
</b></font></div>
<br>
_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
<br>
</blockquote>
</div>
</div>
</blockquote>

<font bgcolor=3D"#ffffff" color=3D"#000000"><b><BR><HR>
***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***
<BR><HR></b></font>
</body>
</html>


--_000_1848EE0D3F26488FB9B3A2A106767A8Ffortinetcom_--

From scott.brim@gmail.com  Sun Sep  8 11:17:10 2013
Return-Path: <scott.brim@gmail.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 56F2821E80B1 for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 11:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.142
X-Spam-Level: 
X-Spam-Status: No, score=-102.142 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K-6qTIQ4o8MF for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 11:17:08 -0700 (PDT)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 101C111E8128 for <multipathtcp@ietf.org>; Sun,  8 Sep 2013 11:17:07 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e52so2695493eek.30 for <multipathtcp@ietf.org>; Sun, 08 Sep 2013 11:17:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QH9zgCTq9LOatsGyUrPcUiSWLnOxiHGAk4NU+4m2zZA=; b=L2Om22NPIsy7QI+iupAGVeT1NyaK3xf4SpSUIcp716TLLgHYhqHsutc0XEHLby7606 epKx7Pn9PnzKhndnIQt5S0RprxYtRH5fUX2HxU53MGhIlHXebT4qjARqv6gr+yXf4+rr o+cTK0ftHb3cIWPYkTcbxI2/IIAQr0HW1MQbEn3FbruODhXgUyRNYdnVU1im/5AdQpqc 5OAOGv1WlFJ0B5D580x936EblHVOjmfszXvHfaCzTtL2+UrofuuXTyGtKCnIiNGstAOC 1/r6OMlb+WeENA30SMXNBEcmr2MKq5Bvz6pHI9DWV10rck+PGnPAs94ZjIt2hJHGUfoe oyBQ==
MIME-Version: 1.0
X-Received: by 10.14.176.8 with SMTP id a8mr23825634eem.12.1378664227182; Sun, 08 Sep 2013 11:17:07 -0700 (PDT)
Received: by 10.14.218.1 with HTTP; Sun, 8 Sep 2013 11:17:07 -0700 (PDT)
Received: by 10.14.218.1 with HTTP; Sun, 8 Sep 2013 11:17:07 -0700 (PDT)
In-Reply-To: <1848EE0D-3F26-488F-B9B3-A2A106767A8F@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com> <CAPv4CP-zpUS9vmXdLzAo63UzaQnDBvZ5Gz152mxeuzVXMb3-+Q@mail.gmail.com> <1848EE0D-3F26-488F-B9B3-A2A106767A8F@fortinet.com>
Date: Sun, 8 Sep 2013 14:17:07 -0400
Message-ID: <CAPv4CP_RDGyMcaNGJ8F=h7OjQWyr4AzrxdTKbW7Py3AubUzU-w@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Edward Lopez <elopez@fortinet.com>
Content-Type: multipart/alternative; boundary=047d7b62214686ba4904e5e347a0
Cc: multipathtcp List <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 08 Sep 2013 18:17:10 -0000

--047d7b62214686ba4904e5e347a0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I look forward to the interim call.
On Sep 8, 2013 11:22 AM, "Edward Lopez" <elopez@fortinet.com> wrote:

>  It's exceedingly difficult to sync memory buffer states at anything
> other than short distances if at all, and still have an IPS perform in-li=
ne
> protection.  However, I will concede the possibility for IDS (just
> detection) to possibly do this.
>
>  This is not just a technical issue, but rather a compliance/political
> one.  Consider PCI, HIPPA, etc. which mandate the use of IPS.  It is
> inevitable that IPS systems will learn to detect and mitigate MPTCP, just
> as it is that third-party MPTCP proxies will be built solely to evade
> content filters.  I for one would hate to see MPTCP relegated to
> intradomain use, because we failed to foresee the perceived security issu=
es.
>
> Ed Lopez
>
>  Sent from my iPhone ... Sorry for any auto-correct errors
>
> On Sep 8, 2013, at 7:13 AM, "Scott Brim" <scott.brim@gmail.com> wrote:
>
>   It doesn't look like anyone replied to this.  Yes there's an issue with
> multipathing and IPS. But rather than isolate MPTCP to a single
> interconnection point, why not get IPSs to coordinate with each other? Th=
at
> way you're opening the door to the future instead of trapping the Interne=
t
> in the past.
> On Sep 5, 2013 1:25 PM, "Edward Lopez" <elopez@fortinet.com> wrote:
>
>>  Phil,
>>
>>  I'm aware that I am relatively new to the WG and IETF as a whole (IETF
>> 87 Berlin was my first meeting).  But I do have a long history of securi=
ty
>> and networking protocols, currently working and having worked for a numb=
er
>> of security appliance (middlebox) vendors.
>>
>>  My initial review of MPTCP is that I would have to consider it an
>> evasion technique from a content inspection standpoint.  Generally, cont=
ent
>> inspection engines are designed to operate as either flow-based or
>> transparent-proxy.  A flow-based engine is generally used by IPS systems=
,
>> but has now expanded to support many types of content inspection, most
>> notably application control functionality of next-generation firewalls
>> (NGFWs).  The limitation of a flow-based engine is that it looks at data=
 in
>> as a stream, generally without reordering and limited data reassembly.  =
 A
>> transparent proxy engine fully buffers and reassembles the data in the
>> context of specific protocols, then inspects this traffic in context.
>>  Transparent proxies are useful when the inspection device has to intera=
ct
>> within the protocol, such as in web-filtering solutions where a block
>> message is sent back to an offending user.  However, both of these conte=
nt
>> inspection engine types have a general model centered around the session
>> paradigm.  an MPTCP session is in effect an aggregate of multiple TCP
>> sessions (sub flows), so in effect has characteristics of a protocol-bas=
ed
>> application, similar to FTP, VoIP, etc.
>>
>>  The effect of MPTCP on content inspection engines is that it can be
>> used as an evasion technique.  For example, I could envision the use of
>> multi-homed MPTCP-based proxy engines out on the Internet, such that MPT=
CP
>> based hosts in net repressive countries could evade state-imposed
>> web-filters, or school kids could evade their school system's web-filter=
s,
>> etc.  The initial reaction from content inspectors would be do develop
>> capabilities to detect MPTCP (likely based on options usage), and to eit=
her
>> block or force fallback to standard TCP.  A significant concern is that
>> this is where the incentive ends.  MPTCP is an evasion method, so mitiga=
te
>> the vulnerability.
>>
>>   I would prefer to consider how to support MPTCP, perhaps in the form
>> of an application-layer gateway and/or modification of content-inspectio=
n
>> engines to deal with aggregation of sub-flows for inspection.  This line=
 of
>> thought lends itself to a philosophical discussion, as to if we intend
>> MPTCP to be used to evade content inspection, or if we are looking to
>> improve the performance of TCP-based applications.  I mention this becau=
se
>> it would be desirable for the protocol to assist, or at least not hinder=
,
>> the ability to identify the multiple sub-flows that create an MPTCP sess=
ion.
>>
>>  Eventually, I see the rise of middleboxes as MPTCP proxies, whether
>> they are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the
>> methodologies of SSL inspection today.  I am interested in these use-cas=
es
>> because without them, the default will be to block/fallback, which
>> ultimately isn't useful relative to MPTCP.
>>
>>  My US $.02
>>  Ed Lopez
>>
>>  On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
>>
>>   Just to let you know. The Security Ads are kindly finding us a
>> security advisor, but no luck yet. So we may have to delay this slightly=
.
>> ****
>>  Also, it would be good if there was some discussion on the mailing list
>> before the call.****
>>
>>  phil****
>>
>>   *From:* Eardley,PL,Philip,TUB8 R
>> *Sent:* 21 August 2013 08:36
>> *To:* Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
>> *Subject:* RE: [multipathtcp] MPTCP interim (audio) meeting on security,
>> late September****
>>   ** **
>>  Just a reminder, as I know a lot of people have been on holiday, please
>> fill in the doodle****
>>
>>  Thanks****
>>  phil****
>>
>>   *From:* multipathtcp-bounces@ietf.org [
>> mailto:multipathtcp-bounces@ietf.org <multipathtcp-bounces@ietf.org>] *O=
n
>> Behalf Of *philip.eardley@bt.com
>> *Sent:* 06 August 2013 13:49
>> *To:* multipathtcp@ietf.org
>> *Subject:* [multipathtcp] MPTCP interim (audio) meeting on security,
>> late September****
>>   ** **
>>  We think it would a good idea to have an interim (audio) meeting, in
>> order to make progress on advancing RFC 6824 on the standards track.****
>>
>>  We will discuss the security of the MPTCP protocol. The aim is to reach
>> consensus on what security improvements are needed - and what are not
>> needed - in order to progress MPTCP on the Standards track. We hope to
>> cover both the threat(s) that we will handle and, at a high-level, the
>> solutions that will be defined.****
>>
>>  Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table**=
*
>> *
>>
>>  For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if
>> the time is no good for you.****
>>
>>  In the meantime, please keep discussing MPTCP=92s security on the list!=
***
>> *
>>
>>  Thanks,****
>>  Best wishes****
>>  Phil & Yoshifumi****
>>   _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>
>> *
>> ------------------------------
>> *** Please note that this message and any attachments may contain
>> confidential and proprietary material and information and are intended o=
nly
>> for the use of the intended recipient(s). If you are not the intended
>> recipient, you are hereby notified that any review, use, disclosure,
>> dissemination, distribution or copying of this message and any attachmen=
ts
>> is strictly prohibited. If you have received this email in error, please
>> immediately notify the sender and destroy this e-mail and any attachment=
s
>> and all copies, whether electronic or printed. Please also note that any
>> views, opinions, conclusions or commitments expressed in this message ar=
e
>> those of the individual sender and do not necessarily reflect the views =
of
>> Fortinet, Inc., its affiliates, and emails are not binding on Fortinet a=
nd
>> only a writing manually signed by Fortinet's General Counsel can be a
>> binding commitment of Fortinet to Fortinet's customers or partners. Than=
k
>> you. ***
>> ------------------------------
>> *
>>
>> _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp
>>
>>   *
> ------------------------------
> *** Please note that this message and any attachments may contain
> confidential and proprietary material and information and are intended on=
ly
> for the use of the intended recipient(s). If you are not the intended
> recipient, you are hereby notified that any review, use, disclosure,
> dissemination, distribution or copying of this message and any attachment=
s
> is strictly prohibited. If you have received this email in error, please
> immediately notify the sender and destroy this e-mail and any attachments
> and all copies, whether electronic or printed. Please also note that any
> views, opinions, conclusions or commitments expressed in this message are
> those of the individual sender and do not necessarily reflect the views o=
f
> Fortinet, Inc., its affiliates, and emails are not binding on Fortinet an=
d
> only a writing manually signed by Fortinet's General Counsel can be a
> binding commitment of Fortinet to Fortinet's customers or partners. Thank
> you. ***
> ------------------------------
> *
>

--047d7b62214686ba4904e5e347a0
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I look forward to the interim call. </p>
<div class=3D"gmail_quote">On Sep 8, 2013 11:22 AM, &quot;Edward Lopez&quot=
; &lt;<a href=3D"mailto:elopez@fortinet.com">elopez@fortinet.com</a>&gt; wr=
ote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div dir=3D"auto">
<div>It&#39;s exceedingly difficult to sync memory buffer states at anythin=
g other than short distances if at all, and still have an IPS perform in-li=
ne protection. =A0However, I will concede the possibility for IDS (just det=
ection) to possibly do this.</div>

<div><br>
</div>
<div>This is not just a technical issue, but rather a compliance/political =
one. =A0Consider PCI, HIPPA, etc. which mandate the use of IPS. =A0It is in=
evitable that IPS systems will learn to detect and mitigate MPTCP, just as =
it is that third-party MPTCP proxies
 will be built solely to evade content filters. =A0I for one would hate to =
see MPTCP relegated to intradomain use, because we failed to foresee the pe=
rceived security issues.<br>
<br>
<div>Ed Lopez</div>
<div><br>
</div>
Sent from my iPhone ... Sorry for any auto-correct errors</div>
<div><br>
On Sep 8, 2013, at 7:13 AM, &quot;Scott Brim&quot; &lt;<a href=3D"mailto:sc=
ott.brim@gmail.com" target=3D"_blank">scott.brim@gmail.com</a>&gt; wrote:<b=
r>
<br>
</div>
<blockquote type=3D"cite">
<div>
<p dir=3D"ltr">It doesn&#39;t look like anyone replied to this.=A0 Yes ther=
e&#39;s an issue with multipathing and IPS. But rather than isolate MPTCP t=
o a single interconnection point, why not get IPSs to coordinate with each =
other? That way you&#39;re opening the door to the
 future instead of trapping the Internet in the past. </p>
<div class=3D"gmail_quote">On Sep 5, 2013 1:25 PM, &quot;Edward Lopez&quot;=
 &lt;<a href=3D"mailto:elopez@fortinet.com" target=3D"_blank">elopez@fortin=
et.com</a>&gt; wrote:<br type=3D"attribution">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">
<div>Phil,</div>
<div><br>
</div>
<div>I&#39;m aware that I am relatively new to the WG and IETF as a whole (=
IETF 87 Berlin was my first meeting). =A0But I do have a long history of se=
curity and networking protocols, currently working and having worked for a =
number of security appliance (middlebox)
 vendors.</div>
<div><br>
</div>
<div>My initial review of MPTCP is that I would have to consider it an evas=
ion technique from a content inspection standpoint. =A0Generally, content i=
nspection engines are designed to operate as either flow-based or transpare=
nt-proxy. =A0A flow-based engine is
 generally used by IPS systems, but has now expanded to support many types =
of content inspection, most notably application control functionality of ne=
xt-generation firewalls (NGFWs). =A0The limitation of a flow-based engine i=
s that it looks at data in as a stream,
 generally without reordering and limited data reassembly. =A0 A transparen=
t proxy engine fully buffers and reassembles the data in the context of spe=
cific protocols, then inspects this traffic in context. =A0Transparent prox=
ies are useful when the inspection device
 has to interact within the protocol, such as in web-filtering solutions wh=
ere a block message is sent back to an offending user. =A0However, both of =
these content inspection engine types have a general model centered around =
the session paradigm. =A0an MPTCP session
 is in effect an aggregate of multiple TCP sessions (sub flows), so in effe=
ct has characteristics of a protocol-based application, similar to FTP, VoI=
P, etc.</div>
<div><br>
</div>
<div>The effect of MPTCP on content inspection engines is that it can be us=
ed as an evasion technique. =A0For example, I could envision the use of mul=
ti-homed MPTCP-based proxy engines out on the Internet, such that MPTCP bas=
ed hosts in net repressive countries
 could evade state-imposed web-filters, or school kids could evade their sc=
hool system&#39;s web-filters, etc. =A0The initial reaction from content in=
spectors would be do develop capabilities to detect MPTCP (likely based on =
options usage), and to either block or
 force fallback to standard TCP. =A0A significant concern is that this is w=
here the incentive ends. =A0MPTCP is an evasion method, so mitigate the vul=
nerability.=A0</div>
<div><br>
</div>
<div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

I would prefer to consider how to support MPTCP, perhaps in the form of an =
application-layer gateway and/or modification of content-inspection engines=
 to deal with aggregation of sub-flows for inspection. =A0This line of thou=
ght lends itself to a philosophical
 discussion, as to if we intend MPTCP to be used to evade content inspectio=
n, or if we are looking to improve the performance of TCP-based application=
s. =A0I mention this because it would be desirable for the protocol to assi=
st, or at least not hinder, the ability
 to identify the multiple sub-flows that create an MPTCP session.</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

<br>
</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

Eventually, I see the rise of middleboxes as MPTCP proxies, whether they ar=
e TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodologies =
of SSL inspection today. =A0I am interested in these use-cases because with=
out them, the default will be to block/fallback,
 which ultimately isn&#39;t useful relative to MPTCP.</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

<br>
</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

My US $.02</div>
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:norma=
l;text-transform:none;font-size:medium;white-space:normal;font-family:Helve=
tica;word-wrap:break-word;word-spacing:0px">

Ed Lopez=A0</div>
</div>
<br>
<div>
<div>On Sep 4, 2013, at 3:31 AM, <a href=3D"mailto:philip.eardley@bt.com" t=
arget=3D"_blank">
philip.eardley@bt.com</a> wrote:</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" style=3D"font-family:Hel=
vetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:n=
ormal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">

<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Just=
 to let you know. The Security Ads are kindly finding us a security advisor=
, but no luck yet. So we may have to delay this slightly.<u></u><u></u></sp=
an></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Also=
, it would be good if there was some discussion on the mailing list before =
the call.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">phil=
<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;bor=
der-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-top-=
color:rgb(181,196,223);padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt;font-famil=
y:Tahoma,sans-serif"><span>=A0</span>Eardley,PL,Philip,TUB8 R<span>=A0</spa=
n><br>
<b>Sent:</b><span>=A0</span>21 August 2013 08:36<br>
<b>To:</b><span>=A0</span>Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:multi=
pathtcp@ietf.org" target=3D"_blank">
multipathtcp@ietf.org</a><br>
<b>Subject:</b><span>=A0</span>RE: [multipathtcp] MPTCP interim (audio) mee=
ting on security, late September<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Just=
 a reminder, as I know a lot of people have been on holiday, please fill in=
 the doodle<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">Than=
ks<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">phil=
<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:blue">=A0<=
/span></div>
<div style=3D"border-style:none none none solid;border-left-width:1.5pt;bor=
der-left-color:blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-top-=
color:rgb(181,196,223);padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt;font-famil=
y:Tahoma,sans-serif"><span>=A0</span><a href=3D"mailto:multipathtcp-bounces=
@ietf.org" style=3D"color:purple;text-decoration:underline" target=3D"_blan=
k">multipathtcp-bounces@ietf.org</a><span>=A0</span>[<a href=3D"mailto:mult=
ipathtcp-bounces@ietf.org" style=3D"color:purple;text-decoration:underline"=
 target=3D"_blank">mailto:multipathtcp-bounces@ietf.org</a>]<span>=A0</span=
><b>On
 Behalf Of<span>=A0</span></b><a href=3D"mailto:philip.eardley@bt.com" styl=
e=3D"color:purple;text-decoration:underline" target=3D"_blank">philip.eardl=
ey@bt.com</a><br>
<b>Sent:</b><span>=A0</span>06 August 2013 13:49<br>
<b>To:</b><span>=A0</span><a href=3D"mailto:multipathtcp@ietf.org" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank">multipathtcp@iet=
f.org</a><br>
<b>Subject:</b><span>=A0</span>[multipathtcp] MPTCP interim (audio) meeting=
 on security, late September<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">We think it wou=
ld a good idea to have an interim (audio) meeting, in order to make progres=
s on advancing RFC 6824 on the standards track.<u></u><u></u></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">We will discuss=
 the security of the MPTCP protocol. The aim is to reach consensus on what =
security improvements are needed - and what are not needed - in order to pr=
ogress MPTCP on the Standards track.
 We hope to cover both the threat(s) that we will handle and, at a high-lev=
el, the solutions that will be defined.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Please fill in =
the doodle at<span>=A0</span><a href=3D"http://doodle.com/xdf8eaiavvna9bcy#=
table" style=3D"color:purple;text-decoration:underline" target=3D"_blank">h=
ttp://doodle.com/xdf8eaiavvna9bcy#table</a><u></u><u></u></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">For previous MP=
TCP WG interims, ~3pm GMT has been OK. Please shout if the time is no good =
for you.<u></u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">In the meantime=
, please keep discussing MPTCP=92s security on the list!<u></u><u></u></spa=
n></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">=A0</span></div=
>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Thanks,<u></u><=
u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Best wishes<u><=
/u><u></u></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Phil &amp; Yosh=
ifumi<u></u><u></u></span></div>
</div>
</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></div>
</blockquote>
</div>
<br>
<font bgcolor=3D"#ffffff" color=3D"#000000"><b><br>
<hr>
*** Please note that this message and any attachments may contain confident=
ial and proprietary material and information and are intended only for the =
use of the intended recipient(s). If you are not the intended recipient, yo=
u are hereby notified that any review,
 use, disclosure, dissemination, distribution or copying of this message an=
d any attachments is strictly prohibited. If you have received this email i=
n error, please immediately notify the sender and destroy this e-mail and a=
ny attachments and all copies, whether
 electronic or printed. Please also note that any views, opinions, conclusi=
ons or commitments expressed in this message are those of the individual se=
nder and do not necessarily reflect the views of Fortinet, Inc., its affili=
ates, and emails are not binding
 on Fortinet and only a writing manually signed by Fortinet&#39;s General C=
ounsel can be a binding commitment of Fortinet to Fortinet&#39;s customers =
or partners. Thank you. ***
<br>
<hr>
</b></font></div>
<br>
_______________________________________________<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>
<br>
</blockquote>
</div>
</div>
</blockquote>

<font bgcolor=3D"#ffffff" color=3D"#000000"><b><br><hr>
***  Please note that this message and any attachments may contain confiden=
tial=20
and proprietary material and information and are intended only for the use =
of=20
the intended recipient(s). If you are not the intended recipient, you are h=
ereby=20
notified that any review, use, disclosure, dissemination, distribution or c=
opying=20
of this message and any attachments is strictly prohibited. If you have rec=
eived=20
this email in error, please immediately notify the sender and destroy this =
e-mail=20
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments expre=
ssed=20
in this message are those of the individual sender and do not necessarily r=
eflect=20
the views of Fortinet, Inc., its affiliates, and emails are not binding on=
=20
Fortinet and only a writing manually signed by Fortinet&#39;s General Couns=
el can be=20
a binding commitment of Fortinet to Fortinet&#39;s customers or partners. T=
hank you. ***
<br><hr></b></font>
</div>


</blockquote></div>

--047d7b62214686ba4904e5e347a0--

From nishida@sfc.wide.ad.jp  Sun Sep  8 14:57:20 2013
Return-Path: <nishida@sfc.wide.ad.jp>
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 BEB7611E8165 for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 14:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.378
X-Spam-Level: 
X-Spam-Status: No, score=-101.378 tagged_above=-999 required=5 tests=[AWL=-0.601, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, J_CHICKENPOX_72=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w8j-VK87e-Ng for <multipathtcp@ietfa.amsl.com>; Sun,  8 Sep 2013 14:57:19 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 18B1F21F9AED for <multipathtcp@ietf.org>; Sun,  8 Sep 2013 14:57:18 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id AB108278086 for <multipathtcp@ietf.org>; Mon,  9 Sep 2013 06:57:15 +0900 (JST)
Received: by mail-la0-f52.google.com with SMTP id ev20so4279410lab.39 for <multipathtcp@ietf.org>; Sun, 08 Sep 2013 14:57:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8Fe/uLzoYrcVgJ40kdEvWXWR9x14+NVb+P346T/Ew4Q=; b=f7VN5W1LSqM3raAlcvgGqgSbZCBcSglAVezXOkknCMCreC0z/tmAklm4Yvslmk1r+E GISSX8hrApNIEjK1fIbAEemB4iwNp/2Ol/7FyucJe7rwFv6wxLlG9dT7S9F1HkPLDJmL pWqEpxShjMk04ATIv2SZJyJcEAKrEw2OMTu45TwoJ/J6JuXoiRanQG8YDq0TChzFNFkh +h02cwPRRl2s0G3FfS+tixwYp5glYAAHKzgU7Jo4j8zQQRwriFb1pz3OxjtyvIEmueUZ tChHIr8WQy8e8wvtGHMvJwEazjbUKsrCUoNV/erBYIoEHpJUmMqN/4KGT53pCM8xB7gt fkfA==
MIME-Version: 1.0
X-Received: by 10.112.172.137 with SMTP id bc9mr13529377lbc.21.1378677432802;  Sun, 08 Sep 2013 14:57:12 -0700 (PDT)
Received: by 10.114.1.115 with HTTP; Sun, 8 Sep 2013 14:57:12 -0700 (PDT)
In-Reply-To: <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
Date: Sun, 8 Sep 2013 14:57:12 -0700
Message-ID: <CAO249ye2m+mW1x-ZC_E5qMEudsbR7piXspTZwEQjsYsxv4zhUQ@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Edward Lopez <elopez@fortinet.com>
Content-Type: multipart/alternative; boundary=001a11c26456a462ae04e5e65af6
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 08 Sep 2013 21:57:20 -0000

--001a11c26456a462ae04e5e65af6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Edward,

I'm trying to understand evasion scenarios since you have raised
interesting points.
In my understanding, it will be something like this.

case 1: There're two networks (say ISP1, ISP2) at the server side.
            ISP1 enforces IPS, but ISP2 doesn't.
            In this case, MPTCP can establish initial subflow through ISP1,
but all contents can go through other subflows through ISP2. So, the
traffic of this connection can evade IPS at ISP1

case 2: There're two networks (say ISP1, ISP2) at the server side.
           Both ISP1, ISP2 enforce IPS,
           In this case, MPTCP can split the contents into small chunks and
distributes them through multiple subflows.
           So, IPSs cannot perform inspection properly.

case 3: similar to case2, but use only one ISP.

Are those closed to what you mentioned? Or, am I thinking about totally
different things?
Please correct me if I miss something.

Thanks,
--
Yoshifumi


On Thu, Sep 5, 2013 at 10:24 AM, Edward Lopez <elopez@fortinet.com> wrote:
> Phil,
>
> I'm aware that I am relatively new to the WG and IETF as a whole (IETF 87
> Berlin was my first meeting).  But I do have a long history of security
and
> networking protocols, currently working and having worked for a number of
> security appliance (middlebox) vendors.
>
> My initial review of MPTCP is that I would have to consider it an evasion
> technique from a content inspection standpoint.  Generally, content
> inspection engines are designed to operate as either flow-based or
> transparent-proxy.  A flow-based engine is generally used by IPS systems,
> but has now expanded to support many types of content inspection, most
> notably application control functionality of next-generation firewalls
> (NGFWs).  The limitation of a flow-based engine is that it looks at data
in
> as a stream, generally without reordering and limited data reassembly.   =
A
> transparent proxy engine fully buffers and reassembles the data in the
> context of specific protocols, then inspects this traffic in context.
> Transparent proxies are useful when the inspection device has to interact
> within the protocol, such as in web-filtering solutions where a block
> message is sent back to an offending user.  However, both of these conten=
t
> inspection engine types have a general model centered around the session
> paradigm.  an MPTCP session is in effect an aggregate of multiple TCP
> sessions (sub flows), so in effect has characteristics of a protocol-base=
d
> application, similar to FTP, VoIP, etc.
>
> The effect of MPTCP on content inspection engines is that it can be used
as
> an evasion technique.  For example, I could envision the use of
multi-homed
> MPTCP-based proxy engines out on the Internet, such that MPTCP based host=
s
> in net repressive countries could evade state-imposed web-filters, or
school
> kids could evade their school system's web-filters, etc.  The initial
> reaction from content inspectors would be do develop capabilities to
detect
> MPTCP (likely based on options usage), and to either block or force
fallback
> to standard TCP.  A significant concern is that this is where the
incentive
> ends.  MPTCP is an evasion method, so mitigate the vulnerability.
>
> I would prefer to consider how to support MPTCP, perhaps in the form of a=
n
> application-layer gateway and/or modification of content-inspection
engines
> to deal with aggregation of sub-flows for inspection.  This line of
thought
> lends itself to a philosophical discussion, as to if we intend MPTCP to b=
e
> used to evade content inspection, or if we are looking to improve the
> performance of TCP-based applications.  I mention this because it would b=
e
> desirable for the protocol to assist, or at least not hinder, the ability
to
> identify the multiple sub-flows that create an MPTCP session.
>
> Eventually, I see the rise of middleboxes as MPTCP proxies, whether they
are
> TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodologies
of
> SSL inspection today.  I am interested in these use-cases because without
> them, the default will be to block/fallback, which ultimately isn't usefu=
l
> relative to MPTCP.
>
> My US $.02
> Ed Lopez
>
> On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
>
> Just to let you know. The Security Ads are kindly finding us a security
> advisor, but no luck yet. So we may have to delay this slightly.
> Also, it would be good if there was some discussion on the mailing list
> before the call.
>
> phil
>
> From: Eardley,PL,Philip,TUB8 R
> Sent: 21 August 2013 08:36
> To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
> Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security,
late
> September
>
> Just a reminder, as I know a lot of people have been on holiday, please
fill
> in the doodle
>
> Thanks
> phil
>
> From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org=
]
> On Behalf Of philip.eardley@bt.com
> Sent: 06 August 2013 13:49
> To: multipathtcp@ietf.org
> Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late
> September
>
> We think it would a good idea to have an interim (audio) meeting, in orde=
r
> to make progress on advancing RFC 6824 on the standards track.
>
> We will discuss the security of the MPTCP protocol. The aim is to reach
> consensus on what security improvements are needed - and what are not
needed
> - in order to progress MPTCP on the Standards track. We hope to cover bot=
h
> the threat(s) that we will handle and, at a high-level, the solutions tha=
t
> will be defined.
>
> Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table
>
> For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the
> time is no good for you.
>
> In the meantime, please keep discussing MPTCP=92s security on the list!
>
> Thanks,
> Best wishes
> Phil & Yoshifumi
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>
> ________________________________
> *** Please note that this message and any attachments may contain
> confidential and proprietary material and information and are intended
only
> for the use of the intended recipient(s). If you are not the intended
> recipient, you are hereby notified that any review, use, disclosure,
> dissemination, distribution or copying of this message and any attachment=
s
> is strictly prohibited. If you have received this email in error, please
> immediately notify the sender and destroy this e-mail and any attachments
> and all copies, whether electronic or printed. Please also note that any
> views, opinions, conclusions or commitments expressed in this message are
> those of the individual sender and do not necessarily reflect the views o=
f
> Fortinet, Inc., its affiliates, and emails are not binding on Fortinet an=
d
> only a writing manually signed by Fortinet's General Counsel can be a
> binding commitment of Fortinet to Fortinet's customers or partners. Thank
> you. ***
> ________________________________
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>

--001a11c26456a462ae04e5e65af6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Edward,<br><br>I&#39;m trying to understand evasion sce=
narios since you have raised interesting points.<br>In my understanding, it=
 will be something like this.=A0<div><br>case 1: There&#39;re two networks =
(say ISP1, ISP2) at the server side. <br>
=A0 =A0 =A0 =A0 =A0 =A0 ISP1 enforces IPS, but ISP2 doesn&#39;t. <br>=A0 =
=A0 =A0 =A0 =A0 =A0 In this case, MPTCP can establish initial subflow throu=
gh ISP1, but all contents can go through other subflows through ISP2. So, t=
he traffic of this connection can evade IPS at ISP1<br>
<br>case 2: There&#39;re two networks (say ISP1, ISP2) at the server side. =
<br>=A0 =A0 =A0 =A0 =A0 =A0Both ISP1, ISP2 enforce IPS,=A0<br>=A0 =A0 =A0 =
=A0 =A0 =A0In this case, MPTCP can split the contents into small chunks and=
 distributes them through multiple subflows.<div>
=A0 =A0 =A0 =A0 =A0 =A0So, IPSs cannot perform inspection properly.</div><d=
iv><br></div><div>case 3: similar to case2, but use only one ISP.<br><br>Ar=
e those closed to what you mentioned? Or, am I thinking about totally diffe=
rent things?</div>
<div>Please correct me if I miss something.</div><div><br>Thanks,<br>--</di=
v><div>Yoshifumi<br><br><br>On Thu, Sep 5, 2013 at 10:24 AM, Edward Lopez &=
lt;<a href=3D"mailto:elopez@fortinet.com">elopez@fortinet.com</a>&gt; wrote=
:<br>
&gt; Phil,<br>&gt;<br>&gt; I&#39;m aware that I am relatively new to the WG=
 and IETF as a whole (IETF 87<br>&gt; Berlin was my first meeting). =A0But =
I do have a long history of security and<br>&gt; networking protocols, curr=
ently working and having worked for a number of<br>
&gt; security appliance (middlebox) vendors.<br>&gt;<br>&gt; My initial rev=
iew of MPTCP is that I would have to consider it an evasion<br>&gt; techniq=
ue from a content inspection standpoint. =A0Generally, content<br>&gt; insp=
ection engines are designed to operate as either flow-based or<br>
&gt; transparent-proxy. =A0A flow-based engine is generally used by IPS sys=
tems,<br>&gt; but has now expanded to support many types of content inspect=
ion, most<br>&gt; notably application control functionality of next-generat=
ion firewalls<br>
&gt; (NGFWs). =A0The limitation of a flow-based engine is that it looks at =
data in<br>&gt; as a stream, generally without reordering and limited data =
reassembly. =A0 A<br>&gt; transparent proxy engine fully buffers and reasse=
mbles the data in the<br>
&gt; context of specific protocols, then inspects this traffic in context.<=
br>&gt; Transparent proxies are useful when the inspection device has to in=
teract<br>&gt; within the protocol, such as in web-filtering solutions wher=
e a block<br>
&gt; message is sent back to an offending user. =A0However, both of these c=
ontent<br>&gt; inspection engine types have a general model centered around=
 the session<br>&gt; paradigm. =A0an MPTCP session is in effect an aggregat=
e of multiple TCP<br>
&gt; sessions (sub flows), so in effect has characteristics of a protocol-b=
ased<br>&gt; application, similar to FTP, VoIP, etc.<br>&gt;<br>&gt; The ef=
fect of MPTCP on content inspection engines is that it can be used as<br>
&gt; an evasion technique. =A0For example, I could envision the use of mult=
i-homed<br>&gt; MPTCP-based proxy engines out on the Internet, such that MP=
TCP based hosts<br>&gt; in net repressive countries could evade state-impos=
ed web-filters, or school<br>
&gt; kids could evade their school system&#39;s web-filters, etc. =A0The in=
itial<br>&gt; reaction from content inspectors would be do develop capabili=
ties to detect<br>&gt; MPTCP (likely based on options usage), and to either=
 block or force fallback<br>
&gt; to standard TCP. =A0A significant concern is that this is where the in=
centive<br>&gt; ends. =A0MPTCP is an evasion method, so mitigate the vulner=
ability.<br>&gt;<br>&gt; I would prefer to consider how to support MPTCP, p=
erhaps in the form of an<br>
&gt; application-layer gateway and/or modification of content-inspection en=
gines<br>&gt; to deal with aggregation of sub-flows for inspection. =A0This=
 line of thought<br>&gt; lends itself to a philosophical discussion, as to =
if we intend MPTCP to be<br>
&gt; used to evade content inspection, or if we are looking to improve the<=
br>&gt; performance of TCP-based applications. =A0I mention this because it=
 would be<br>&gt; desirable for the protocol to assist, or at least not hin=
der, the ability to<br>
&gt; identify the multiple sub-flows that create an MPTCP session.<br>&gt;<=
br>&gt; Eventually, I see the rise of middleboxes as MPTCP proxies, whether=
 they are<br>&gt; TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with th=
e methodologies of<br>
&gt; SSL inspection today. =A0I am interested in these use-cases because wi=
thout<br>&gt; them, the default will be to block/fallback, which ultimately=
 isn&#39;t useful<br>&gt; relative to MPTCP.<br>&gt;<br>&gt; My US $.02<br>
&gt; Ed Lopez<br>&gt;<br>&gt; On Sep 4, 2013, at 3:31 AM, <a href=3D"mailto=
:philip.eardley@bt.com">philip.eardley@bt.com</a> wrote:<br>&gt;<br>&gt; Ju=
st to let you know. The Security Ads are kindly finding us a security<br>
&gt; advisor, but no luck yet. So we may have to delay this slightly.<br>&g=
t; Also, it would be good if there was some discussion on the mailing list<=
br>&gt; before the call.<br>&gt; =A0<br>&gt; phil<br>&gt; =A0<br>&gt; From:=
 Eardley,PL,Philip,TUB8 R<br>
&gt; Sent: 21 August 2013 08:36<br>&gt; To: Eardley,PL,Philip,TUB8 R; <a hr=
ef=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>&gt; Subje=
ct: RE: [multipathtcp] MPTCP interim (audio) meeting on security, late<br>
&gt; September<br>&gt; =A0<br>&gt; Just a reminder, as I know a lot of peop=
le have been on holiday, please fill<br>&gt; in the doodle<br>&gt; =A0<br>&=
gt; Thanks<br>&gt; phil<br>&gt; =A0<br>&gt; From: <a href=3D"mailto:multipa=
thtcp-bounces@ietf.org">multipathtcp-bounces@ietf.org</a> [mailto:<a href=
=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-bounces@ietf.org</a>=
]<br>
&gt; On Behalf Of <a href=3D"mailto:philip.eardley@bt.com">philip.eardley@b=
t.com</a><br>&gt; Sent: 06 August 2013 13:49<br>&gt; To: <a href=3D"mailto:=
multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>&gt; Subject: [multipat=
htcp] MPTCP interim (audio) meeting on security, late<br>
&gt; September<br>&gt; =A0<br>&gt; We think it would a good idea to have an=
 interim (audio) meeting, in order<br>&gt; to make progress on advancing RF=
C 6824 on the standards track.<br>&gt; =A0<br>&gt; We will discuss the secu=
rity of the MPTCP protocol. The aim is to reach<br>
&gt; consensus on what security improvements are needed - and what are not =
needed<br>&gt; - in order to progress MPTCP on the Standards track. We hope=
 to cover both<br>&gt; the threat(s) that we will handle and, at a high-lev=
el, the solutions that<br>
&gt; will be defined.<br>&gt; =A0<br>&gt; Please fill in the doodle at <a h=
ref=3D"http://doodle.com/xdf8eaiavvna9bcy#table">http://doodle.com/xdf8eaia=
vvna9bcy#table</a><br>&gt; =A0<br>&gt; For previous MPTCP WG interims, ~3pm=
 GMT has been OK. Please shout if the<br>
&gt; time is no good for you.<br>&gt; =A0<br>&gt; In the meantime, please k=
eep discussing MPTCP=92s security on the list!<br>&gt; =A0<br>&gt; Thanks,<=
br>&gt; Best wishes<br>&gt; Phil &amp; Yoshifumi<br>&gt; __________________=
_____________________________<br>
&gt; multipathtcp mailing list<br>&gt; <a href=3D"mailto:multipathtcp@ietf.=
org">multipathtcp@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.org/mail=
man/listinfo/multipathtcp">https://www.ietf.org/mailman/listinfo/multipatht=
cp</a><br>
&gt;<br>&gt;<br>&gt;<br>&gt; ________________________________<br>&gt; *** P=
lease note that this message and any attachments may contain<br>&gt; confid=
ential and proprietary material and information and are intended only<br>
&gt; for the use of the intended recipient(s). If you are not the intended<=
br>&gt; recipient, you are hereby notified that any review, use, disclosure=
,<br>&gt; dissemination, distribution or copying of this message and any at=
tachments<br>
&gt; is strictly prohibited. If you have received this email in error, plea=
se<br>&gt; immediately notify the sender and destroy this e-mail and any at=
tachments<br>&gt; and all copies, whether electronic or printed. Please als=
o note that any<br>
&gt; views, opinions, conclusions or commitments expressed in this message =
are<br>&gt; those of the individual sender and do not necessarily reflect t=
he views of<br>&gt; Fortinet, Inc., its affiliates, and emails are not bind=
ing on Fortinet and<br>
&gt; only a writing manually signed by Fortinet&#39;s General Counsel can b=
e a<br>&gt; binding commitment of Fortinet to Fortinet&#39;s customers or p=
artners. Thank<br>&gt; you. ***<br>&gt; ________________________________<br=
>
&gt;<br>&gt; _______________________________________________<br>&gt; multip=
athtcp mailing list<br>&gt; <a href=3D"mailto:multipathtcp@ietf.org">multip=
athtcp@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.org/mailman/listinf=
o/multipathtcp">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
&gt;<br></div></div></div>

--001a11c26456a462ae04e5e65af6--

From c.raiciu@cs.ucl.ac.uk  Mon Sep  9 00:39:24 2013
Return-Path: <c.raiciu@cs.ucl.ac.uk>
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 7A78621E80B6 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 00:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.717
X-Spam-Level: *
X-Spam-Status: No, score=1.717 tagged_above=-999 required=5 tests=[J_CHICKENPOX_72=0.6, RCVD_IN_SORBS_WEB=1.117]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWnS45AL0uB6 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 00:39:10 -0700 (PDT)
Received: from bells2.cs.ucl.ac.uk (bells2.cs.ucl.ac.uk [128.16.5.33]) by ietfa.amsl.com (Postfix) with ESMTP id E80F021E80AC for <multipathtcp@ietf.org>; Mon,  9 Sep 2013 00:38:59 -0700 (PDT)
Received: from [92.80.74.86] (helo=[192.168.1.4]) by bells2.cs.ucl.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (C.Raiciu authenticated) (Exim 4.54) id 1VIw3b-000JXC-LZ; Mon, 09 Sep 2013 08:38:48 +0100
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Costin Raiciu <c.raiciu@cs.ucl.ac.uk>
In-Reply-To: <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
Date: Mon, 9 Sep 2013 10:38:43 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <14673454-0285-4E79-87F1-83DA0CB19C7A@cs.ucl.ac.uk>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>
To: Edward Lopez <elopez@fortinet.com>
X-Mailer: Apple Mail (2.1085)
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late  September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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 Sep 2013 07:39:24 -0000

Can I ask what such boxes do with TLS connections?
Costin


On 5 Sep 2013, at 20:24, Edward Lopez wrote:

> Phil,
>=20
> I'm aware that I am relatively new to the WG and IETF as a whole (IETF =
87 Berlin was my first meeting).  But I do have a long history of =
security and networking protocols, currently working and having worked =
for a number of security appliance (middlebox) vendors.
>=20
> My initial review of MPTCP is that I would have to consider it an =
evasion technique from a content inspection standpoint.  Generally, =
content inspection engines are designed to operate as either flow-based =
or transparent-proxy.  A flow-based engine is generally used by IPS =
systems, but has now expanded to support many types of content =
inspection, most notably application control functionality of =
next-generation firewalls (NGFWs).  The limitation of a flow-based =
engine is that it looks at data in as a stream, generally without =
reordering and limited data reassembly.   A transparent proxy engine =
fully buffers and reassembles the data in the context of specific =
protocols, then inspects this traffic in context.  Transparent proxies =
are useful when the inspection device has to interact within the =
protocol, such as in web-filtering solutions where a block message is =
sent back to an offending user.  However, both of these content =
inspection engine types have a general model centered around the session =
paradigm.  an MPTCP session is in effect an aggregate of multiple TCP =
sessions (sub flows), so in effect has characteristics of a =
protocol-based application, similar to FTP, VoIP, etc.
>=20
> The effect of MPTCP on content inspection engines is that it can be =
used as an evasion technique.  For example, I could envision the use of =
multi-homed MPTCP-based proxy engines out on the Internet, such that =
MPTCP based hosts in net repressive countries could evade state-imposed =
web-filters, or school kids could evade their school system's =
web-filters, etc.  The initial reaction from content inspectors would be =
do develop capabilities to detect MPTCP (likely based on options usage), =
and to either block or force fallback to standard TCP.  A significant =
concern is that this is where the incentive ends.  MPTCP is an evasion =
method, so mitigate the vulnerability.=20
>=20
> I would prefer to consider how to support MPTCP, perhaps in the form =
of an application-layer gateway and/or modification of =
content-inspection engines to deal with aggregation of sub-flows for =
inspection.  This line of thought lends itself to a philosophical =
discussion, as to if we intend MPTCP to be used to evade content =
inspection, or if we are looking to improve the performance of TCP-based =
applications.  I mention this because it would be desirable for the =
protocol to assist, or at least not hinder, the ability to identify the =
multiple sub-flows that create an MPTCP session.
>=20
> Eventually, I see the rise of middleboxes as MPTCP proxies, whether =
they are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the =
methodologies of SSL inspection today.  I am interested in these =
use-cases because without them, the default will be to block/fallback, =
which ultimately isn't useful relative to MPTCP.
>=20
> My US $.02
> Ed Lopez=20
>=20
> On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
>=20
>> Just to let you know. The Security Ads are kindly finding us a =
security advisor, but no luck yet. So we may have to delay this =
slightly.
>> Also, it would be good if there was some discussion on the mailing =
list before the call.
>> =20
>> phil
>> =20
>> From: Eardley,PL,Philip,TUB8 R=20
>> Sent: 21 August 2013 08:36
>> To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
>> Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on =
security, late September
>> =20
>> Just a reminder, as I know a lot of people have been on holiday, =
please fill in the doodle
>> =20
>> Thanks
>> phil
>> =20
>> From: multipathtcp-bounces@ietf.org =
[mailto:multipathtcp-bounces@ietf.org] On Behalf Of =
philip.eardley@bt.com
>> Sent: 06 August 2013 13:49
>> To: multipathtcp@ietf.org
>> Subject: [multipathtcp] MPTCP interim (audio) meeting on security, =
late September
>> =20
>> We think it would a good idea to have an interim (audio) meeting, in =
order to make progress on advancing RFC 6824 on the standards track.
>> =20
>> We will discuss the security of the MPTCP protocol. The aim is to =
reach consensus on what security improvements are needed - and what are =
not needed - in order to progress MPTCP on the Standards track. We hope =
to cover both the threat(s) that we will handle and, at a high-level, =
the solutions that will be defined.
>> =20
>> Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table
>> =20
>> For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if =
the time is no good for you.
>> =20
>> In the meantime, please keep discussing MPTCP=92s security on the =
list!
>> =20
>> Thanks,
>> Best wishes
>> Phil & Yoshifumi
>> _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp
>=20
>=20
> *** Please note that this message and any attachments may contain =
confidential and proprietary material and information and are intended =
only for the use of the intended recipient(s). If you are not the =
intended recipient, you are hereby notified that any review, use, =
disclosure, dissemination, distribution or copying of this message and =
any attachments is strictly prohibited. If you have received this email =
in error, please immediately notify the sender and destroy this e-mail =
and any attachments and all copies, whether electronic or printed. =
Please also note that any views, opinions, conclusions or commitments =
expressed in this message are those of the individual sender and do not =
necessarily reflect the views of Fortinet, Inc., its affiliates, and =
emails are not binding on Fortinet and only a writing manually signed by =
Fortinet's General Counsel can be a binding commitment of Fortinet to =
Fortinet's customers or partners. Thank you. ***=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


From philip.eardley@bt.com  Mon Sep  9 09:35:35 2013
Return-Path: <philip.eardley@bt.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 9589921E80A1 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 09:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.998
X-Spam-Level: 
X-Spam-Status: No, score=-102.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MD0UTP6jzHC0 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 09:35:31 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.com [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 7D87721F8481 for <multipathtcp@ietf.org>; Mon,  9 Sep 2013 09:35:16 -0700 (PDT)
Received: from EVMHT69-UKRD.domain1.systemhost.net (10.36.3.129) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 9 Sep 2013 17:35:07 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.113]) by EVMHT69-UKRD.domain1.systemhost.net ([10.36.3.129]) with mapi; Mon, 9 Sep 2013 17:35:07 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Date: Mon, 9 Sep 2013 17:31:57 +0100
Thread-Topic: Thursday 3rd October: MPTCP interim (audio) meeting on security
Thread-Index: Ac6tedRNJt/x3vsES6GmoIc+T+tuLQ==
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net>
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_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FBEMV67UKRDdoma_"
MIME-Version: 1.0
Subject: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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 Sep 2013 16:35:35 -0000

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FBEMV67UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Let's fix the date of the interim meeting for Thursday 3rd October at 3pm G=
MT (note, the clocks change at different times in different regions of the =
world, this time is in GMT/UTC)

Will send audio details later

Thanks!
phil

From: Eardley,PL,Philip,TUB8 R
Sent: 06 September 2013 10:59
To: multipathtcp@ietf.org
Subject: MPTCP interim (audio) meeting on security - please update your doo=
dle

I extended the doodle to the first week of October.
Please could you update your entry or fill in

Sorry for the trouble

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> [=
mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com<ma=
ilto:philip.eardley@bt.com>
Sent: 04 September 2013 08:31
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just to let you know. The Security Ads are kindly finding us a security adv=
isor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list bef=
ore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp@iet=
f.org>
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just a reminder, as I know a lot of people have been on holiday, please fil=
l in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> [=
mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com<ma=
ilto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late Sep=
tember

We think it would a good idea to have an interim (audio) meeting, in order =
to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach con=
sensus on what security improvements are needed - and what are not needed -=
 in order to progress MPTCP on the Standards track. We hope to cover both t=
he threat(s) that we will handle and, at a high-level, the solutions that w=
ill be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the t=
ime is no good for you.

In the meantime, please keep discussing MPTCP's security on the list!

Thanks,
Best wishes
Phil & Yoshifumi

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FBEMV67UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Let&#8217;s fi=
x the date of the interim meeting for Thursday 3<sup>rd</sup> October at 3p=
m GMT (note, the clocks change at different times in different regions of t=
he world, this time is in GMT/UTC)<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:bl=
ue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Arial","sans-serif";color:blue'>Will send audio deta=
ils later<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ar=
ial","sans-serif";color:blue'>Thanks!<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color=
:blue'>phil<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></=
span></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm=
 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0=
pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-langu=
age:EN-GB'>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> Eardley,PL,Phil=
ip,TUB8 R <br><b>Sent:</b> 06 September 2013 10:59<br><b>To:</b> multipatht=
cp@ietf.org<br><b>Subject:</b> MPTCP interim (audio) meeting on security - =
please update your doodle<o:p></o:p></span></p></div></div><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.=
0pt;font-family:"Arial","sans-serif";color:blue'>I extended the doodle to t=
he first week of October.<o:p></o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Pleas=
e could you update your entry or fill in<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";co=
lor:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Sorry for the =
trouble<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Aria=
l","sans-serif";color:blue'>Thanks<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:bl=
ue'>phil<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></spa=
n></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0c=
m 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;=
padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language=
:EN-GB'>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> <a href=3D"mailto:=
multipathtcp-bounces@ietf.org">multipathtcp-bounces@ietf.org</a> [<a href=
=3D"mailto:multipathtcp-bounces@ietf.org">mailto:multipathtcp-bounces@ietf.=
org</a>] <b>On Behalf Of </b><a href=3D"mailto:philip.eardley@bt.com">phili=
p.eardley@bt.com</a><br><b>Sent:</b> 04 September 2013 08:31<br><b>To:</b> =
<a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br><b>Su=
bject:</b> Re: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te September<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fami=
ly:"Arial","sans-serif";color:blue'>Just to let you know. The Security Ads =
are kindly finding us a security advisor, but no luck yet. So we may have t=
o delay this slightly.<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Also, it=
 would be good if there was some discussion on the mailing list before the =
call.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12=
.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial"=
,"sans-serif";color:blue'>phil<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid blu=
e 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-to=
p:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><s=
pan lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
";mso-fareast-language:EN-GB'>From:</span></b><span lang=3DEN-US style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-G=
B'> Eardley,PL,Philip,TUB8 R <br><b>Sent:</b> 21 August 2013 08:36<br><b>To=
:</b> Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:multipathtcp@ietf.org">mu=
ltipathtcp@ietf.org</a><br><b>Subject:</b> RE: [multipathtcp] MPTCP interim=
 (audio) meeting on security, late September<o:p></o:p></span></p></div></d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span sty=
le=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Just a =
reminder, as I know a lot of people have been on holiday, please fill in th=
e doodle <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ar=
ial","sans-serif";color:blue'>Thanks<o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:=
blue'>phil<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></s=
pan></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm =
0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0p=
t;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-langua=
ge:EN-GB'>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'> <a href=3D"mailt=
o:multipathtcp-bounces@ietf.org">multipathtcp-bounces@ietf.org</a> [<a href=
=3D"mailto:multipathtcp-bounces@ietf.org">mailto:multipathtcp-bounces@ietf.=
org</a>] <b>On Behalf Of </b><a href=3D"mailto:philip.eardley@bt.com">phili=
p.eardley@bt.com</a><br><b>Sent:</b> 06 August 2013 13:49<br><b>To:</b> <a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br><b>Subje=
ct:</b> [multipathtcp] MPTCP interim (audio) meeting on security, late Sept=
ember<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ari=
al","sans-serif"'>We think it would a good idea to have an interim (audio) =
meeting, in order to make progress on advancing RFC 6824 on the standards t=
rack.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12=
.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-seri=
f"'>We will discuss the security of the MPTCP protocol. The aim is to reach=
 consensus on what security improvements are needed - and what are not need=
ed - in order to progress MPTCP on the Standards track. We hope to cover bo=
th the threat(s) that we will handle and, at a high-level, the solutions th=
at will be defined.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"A=
rial","sans-serif"'>Please fill in the doodle at <a href=3D"http://doodle.c=
om/xdf8eaiavvna9bcy#table">http://doodle.com/xdf8eaiavvna9bcy#table</a> <o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;fon=
t-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>For =
previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the time =
is no good for you.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"A=
rial","sans-serif"'>In the meantime, please keep discussing MPTCP&#8217;s s=
ecurity on the list!<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"A=
rial","sans-serif"'>Thanks, <o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>Best wishes<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;fo=
nt-family:"Arial","sans-serif"'>Phil &amp; Yoshifumi<o:p></o:p></span></p><=
/div></div></div></div></div></body></html>=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FBEMV67UKRDdoma_--

From elopez@fortinet.com  Mon Sep  9 10:32:39 2013
Return-Path: <elopez@fortinet.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 92B3221E80A1 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 10:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.998
X-Spam-Level: 
X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qj2IVOdQqJsl for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 10:32:34 -0700 (PDT)
Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8ACE421E809C for <multipathtcp@ietf.org>; Mon,  9 Sep 2013 10:32:34 -0700 (PDT)
From: Edward Lopez <elopez@fortinet.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting	on security
Thread-Index: Ac6tedRNJt/x3vsES6GmoIc+T+tuLQACKajy
Date: Mon, 9 Sep 2013 17:32:38 +0000
Message-ID: <5B2DB2FC572BCF4692FD92FBAD6448D29A0E08@FGT-EXCH-MBX211.fortinet-us.com>
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net>
In-Reply-To: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [108.28.173.111]
Content-Type: multipart/alternative; boundary="_000_5B2DB2FC572BCF4692FD92FBAD6448D29A0E08FGTEXCHMBX211fort_"
MIME-Version: 1.0
X-FEAS-SYSTEM-WL: 192.168.221.213
Subject: Re: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting	on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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 Sep 2013 17:32:39 -0000

--_000_5B2DB2FC572BCF4692FD92FBAD6448D29A0E08FGTEXCHMBX211fort_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

FYI ... THe LISP interim meeting is on the same date in Herndon, VA, US
________________________________
From: multipathtcp-bounces@ietf.org [multipathtcp-bounces@ietf.org] on be=
half of philip.eardley@bt.com [philip.eardley@bt.com]
Sent: Monday, September 09, 2013 12:31 PM
To: multipathtcp@ietf.org
Subject: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeti=
ng on security

Let=92s fix the date of the interim meeting for Thursday 3rd October at 3=
pm GMT (note, the clocks change at different times in different regions o=
f the world, this time is in GMT/UTC)

Will send audio details later

Thanks!
phil

From: Eardley,PL,Philip,TUB8 R
Sent: 06 September 2013 10:59
To: multipathtcp@ietf.org
Subject: MPTCP interim (audio) meeting on security - please update your d=
oodle

I extended the doodle to the first week of October.
Please could you update your entry or fill in

Sorry for the trouble

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org>=
 [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.co=
m<mailto:philip.eardley@bt.com>
Sent: 04 September 2013 08:31
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te September

Just to let you know. The Security Ads are kindly finding us a security a=
dvisor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list b=
efore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp@i=
etf.org>
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te September

Just a reminder, as I know a lot of people have been on holiday, please f=
ill in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org>=
 [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.co=
m<mailto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late S=
eptember

We think it would a good idea to have an interim (audio) meeting, in orde=
r to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach c=
onsensus on what security improvements are needed - and what are not need=
ed - in order to progress MPTCP on the Standards track. We hope to cover =
both the threat(s) that we will handle and, at a high-level, the solution=
s that will be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the=
 time is no good for you.

In the meantime, please keep discussing MPTCP=92s security on the list!

Thanks,
Best wishes
Phil & Yoshifumi


***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***

--_000_5B2DB2FC572BCF4692FD92FBAD6448D29A0E08FGTEXCHMBX211fort_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows=
-1252">
<style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
span.BalloonTextChar
	{font-family:"Tahoma","sans-serif"}
span.EmailStyle19
	{font-family:"Arial","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none}
span.EmailStyle20
	{font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none}
span.EmailStyle21
	{font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none}
span.EmailStyle22
	{font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none}
span.EmailStyle23
	{font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:72.0pt 72.0pt 72.0pt 72.0pt}
-->
</style><style type=3D"text/css" id=3D"owaParaStyle"></style>
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" fpstyle=3D"1" ocsi=3D=
"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size=
: 10pt;">FYI ... THe LISP interim meeting is on the same date in Herndon,=
 VA, US<br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16=
px">
<hr tabindex=3D"-1">
<div id=3D"divRpF508331" style=3D"direction: ltr;"><font face=3D"Tahoma" =
size=3D"2" color=3D"#000000"><b>From:</b> multipathtcp-bounces@ietf.org [=
multipathtcp-bounces@ietf.org] on behalf of philip.eardley@bt.com [philip=
.eardley@bt.com]<br>
<b>Sent:</b> Monday, September 09, 2013 12:31 PM<br>
<b>To:</b> multipathtcp@ietf.org<br>
<b>Subject:</b> [multipathtcp] Thursday 3rd October: MPTCP interim (audio=
) meeting on security<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Let=92s fix the date of =
the interim meeting for Thursday 3<sup>rd</sup> October at 3pm GMT (note,=
 the clocks change at different times in different regions of the
 world, this time is in GMT/UTC)</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Will send audio details =
later</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Thanks!</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">phil</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm =
0cm 4.0pt">
<div>
<div style=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;=
 font-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&q=
uot;,&quot;sans-serif&quot;"> Eardley,PL,Philip,TUB8 R
<br>
<b>Sent:</b> 06 September 2013 10:59<br>
<b>To:</b> multipathtcp@ietf.org<br>
<b>Subject:</b> MPTCP interim (audio) meeting on security - please update=
 your doodle</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">I extended the doodle to=
 the first week of October.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Please could you update =
your entry or fill in</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Sorry for the trouble</s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Thanks</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">phil</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm =
0cm 4.0pt">
<div>
<div style=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;=
 font-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&q=
uot;,&quot;sans-serif&quot;">
<a href=3D"mailto:multipathtcp-bounces@ietf.org" target=3D"_blank">multip=
athtcp-bounces@ietf.org</a> [<a href=3D"mailto:multipathtcp-bounces@ietf.=
org" target=3D"_blank">mailto:multipathtcp-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:philip.eardley@bt.com" target=3D"_b=
lank">philip.eardley@bt.com</a><br>
<b>Sent:</b> 04 September 2013 08:31<br>
<b>To:</b> <a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">mul=
tipathtcp@ietf.org</a><br>
<b>Subject:</b> Re: [multipathtcp] MPTCP interim (audio) meeting on secur=
ity, late September</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Just to let you know. Th=
e Security Ads are kindly finding us a security advisor, but no luck yet.=
 So we may have to delay this slightly.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Also, it would be good i=
f there was some discussion on the mailing list before the call.</span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">phil</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm =
0cm 4.0pt">
<div>
<div style=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;=
 font-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&q=
uot;,&quot;sans-serif&quot;"> Eardley,PL,Philip,TUB8 R
<br>
<b>Sent:</b> 21 August 2013 08:36<br>
<b>To:</b> Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:multipathtcp@ietf.=
org" target=3D"_blank">
multipathtcp@ietf.org</a><br>
<b>Subject:</b> RE: [multipathtcp] MPTCP interim (audio) meeting on secur=
ity, late September</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Just a reminder, as I kn=
ow a lot of people have been on holiday, please fill in the doodle
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">Thanks</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">phil</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;; color:blue">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm =
0cm 4.0pt">
<div>
<div style=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;=
 font-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&q=
uot;,&quot;sans-serif&quot;">
<a href=3D"mailto:multipathtcp-bounces@ietf.org" target=3D"_blank">multip=
athtcp-bounces@ietf.org</a> [<a href=3D"mailto:multipathtcp-bounces@ietf.=
org" target=3D"_blank">mailto:multipathtcp-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:philip.eardley@bt.com" target=3D"_b=
lank">philip.eardley@bt.com</a><br>
<b>Sent:</b> 06 August 2013 13:49<br>
<b>To:</b> <a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">mul=
tipathtcp@ietf.org</a><br>
<b>Subject:</b> [multipathtcp] MPTCP interim (audio) meeting on security,=
 late September</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">We think it would a good idea to hav=
e an interim (audio) meeting, in order to make progress on advancing RFC =
6824 on the standards track.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">We will discuss the security of the =
MPTCP protocol. The aim is to reach consensus on what security improvemen=
ts are needed - and what are not needed - in order to progress
 MPTCP on the Standards track. We hope to cover both the threat(s) that w=
e will handle and, at a high-level, the solutions that will be defined.</=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">Please fill in the doodle at
<a href=3D"http://doodle.com/xdf8eaiavvna9bcy#table" target=3D"_blank">ht=
tp://doodle.com/xdf8eaiavvna9bcy#table</a>
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">For previous MPTCP WG interims, ~3pm=
 GMT has been OK. Please shout if the time is no good for you.</span></p>=

<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">In the meantime, please keep discuss=
ing MPTCP=92s security on the list!</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">Thanks,
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">Best wishes</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">Phil &amp; Yoshifumi</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>

<font bgcolor=3D"#ffffff" color=3D"#000000"><b><BR><HR>
***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***
<BR><HR></b></font>
</body>
</html>


--_000_5B2DB2FC572BCF4692FD92FBAD6448D29A0E08FGTEXCHMBX211fort_--

From tireddy@cisco.com  Mon Sep  9 23:08:54 2013
Return-Path: <tireddy@cisco.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 E22FB21E8125 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 23:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.399
X-Spam-Level: 
X-Spam-Status: No, score=-9.399 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dR7Givk5wSVt for <multipathtcp@ietfa.amsl.com>; Mon,  9 Sep 2013 23:08:50 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDAF21E809D for <multipathtcp@ietf.org>; Mon,  9 Sep 2013 23:08:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7755; q=dns/txt; s=iport; t=1378793330; x=1380002930; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Zbr3AWQVFSns3qLPorN3YibxurQAKP+biTsnMf1z3C0=; b=A1cvmbEQ8QKAtttUSE5661A56rMh4BwUmN7bsxp8MmWYs93l4MwwSKXE HpsMzLyXmmls7OWef2lX5YZoCcROnGzRgqKWZPkuVenefyxfv0DTdMYDu TaUoOhGh/sz8w9vjEb/VGy3MySvPpNsgDHqgUUKn+3MeZQQ2eypqmXgQH s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJu2LlKtJV2c/2dsb2JhbABRCg6CeThRwjCBKhZ0giUBAQEDAQEBASQTNAMIBQcEAgEIDgMEAQEBChQJBycLFAkIAgQBDQUIE4dhBgzCQo4SBgQGgQgxBwaDF4EAA5QchQmQPIJhP4FoAgcXBhw
X-IronPort-AV: E=Sophos;i="4.90,876,1371081600"; d="scan'208";a="257679940"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 10 Sep 2013 06:08:47 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r8A68l5G009244 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Sep 2013 06:08:47 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.33]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Tue, 10 Sep 2013 01:08:47 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Costin Raiciu <c.raiciu@cs.ucl.ac.uk>, Edward Lopez <elopez@fortinet.com>
Thread-Topic: [multipathtcp] MPTCP interim (audio) meeting on security,	late September
Thread-Index: AQHOrS/RyI38dVchwkmq0Qh/cVseApm+evzQ
Date: Tue, 10 Sep 2013 06:08:46 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A1905DEA0@xmb-rcd-x10.cisco.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com> <14673454-0285-4E79-87F1-83DA0CB19C7A@cs.ucl.ac.uk>
In-Reply-To: <14673454-0285-4E79-87F1-83DA0CB19C7A@cs.ucl.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.34.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late  September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 10 Sep 2013 06:08:55 -0000

> -----Original Message-----
> From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org=
] On
> Behalf Of Costin Raiciu
> Sent: Monday, September 09, 2013 1:09 PM
> To: Edward Lopez
> Cc: multipathtcp@ietf.org
> Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te
> September
>=20
> Can I ask what such boxes do with TLS connections ?

Firewalls (FW) typically perform the actions with HTTPS connection:

[1] FW only perform L4 inspection of HTTPS traffic -> Such FW should permit=
 MPTCP sub-flows destined to 443.
[2] FW in addition to L4 also inspect the TLS handshake for example validat=
e the certificate etc -> Such FW would block MPTCP sub-flows because of lac=
k of TLS handshake in the sub-flows.
[3] FW act as TLS Proxy -> Such FW may not support MPTCP and hence in the S=
YN_ACK will not signal any MPTCP capability forcing the MPTCP client to mov=
e to regular TCP connection.

-Tiru.

> Costin
>=20
>=20
> On 5 Sep 2013, at 20:24, Edward Lopez wrote:
>=20
> > Phil,
> >
> > I'm aware that I am relatively new to the WG and IETF as a whole (IETF =
87
> Berlin was my first meeting).  But I do have a long history of security a=
nd
> networking protocols, currently working and having worked for a number of
> security appliance (middlebox) vendors.
> >
> > My initial review of MPTCP is that I would have to consider it an evasi=
on
> technique from a content inspection standpoint.  Generally, content inspe=
ction
> engines are designed to operate as either flow-based or transparent-proxy=
.  A
> flow-based engine is generally used by IPS systems, but has now expanded =
to
> support many types of content inspection, most notably application contro=
l
> functionality of next-generation firewalls (NGFWs).  The limitation of a =
flow-
> based engine is that it looks at data in as a stream, generally without
> reordering and limited data reassembly.   A transparent proxy engine full=
y
> buffers and reassembles the data in the context of specific protocols, th=
en
> inspects this traffic in context.  Transparent proxies are useful when th=
e
> inspection device has to interact within the protocol, such as in web-
> filtering solutions where a block message is sent back to an offending us=
er.
> However, both of these content inspection engine types have a general mod=
el
> centered around the session paradigm.  an MPTCP session is in effect an
> aggregate of multiple TCP sessions (sub flows), so in effect has
> characteristics of a protocol-based application, similar to FTP, VoIP, et=
c.
> >
> > The effect of MPTCP on content inspection engines is that it can be use=
d as
> an evasion technique.  For example, I could envision the use of multi-hom=
ed
> MPTCP-based proxy engines out on the Internet, such that MPTCP based host=
s in
> net repressive countries could evade state-imposed web-filters, or school=
 kids
> could evade their school system's web-filters, etc.  The initial reaction=
 from
> content inspectors would be do develop capabilities to detect MPTCP (like=
ly
> based on options usage), and to either block or force fallback to standar=
d
> TCP.  A significant concern is that this is where the incentive ends.  MP=
TCP
> is an evasion method, so mitigate the vulnerability.
> >
> > I would prefer to consider how to support MPTCP, perhaps in the form of=
 an
> application-layer gateway and/or modification of content-inspection engin=
es to
> deal with aggregation of sub-flows for inspection.  This line of thought =
lends
> itself to a philosophical discussion, as to if we intend MPTCP to be used=
 to
> evade content inspection, or if we are looking to improve the performance=
 of
> TCP-based applications.  I mention this because it would be desirable for=
 the
> protocol to assist, or at least not hinder, the ability to identify the
> multiple sub-flows that create an MPTCP session.
> >
> > Eventually, I see the rise of middleboxes as MPTCP proxies, whether the=
y are
> TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodologies =
of
> SSL inspection today.  I am interested in these use-cases because without
> them, the default will be to block/fallback, which ultimately isn't usefu=
l
> relative to MPTCP.
> >
> > My US $.02
> > Ed Lopez
> >
> > On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
> >
> >> Just to let you know. The Security Ads are kindly finding us a securit=
y
> advisor, but no luck yet. So we may have to delay this slightly.
> >> Also, it would be good if there was some discussion on the mailing lis=
t
> before the call.
> >>
> >> phil
> >>
> >> From: Eardley,PL,Philip,TUB8 R
> >> Sent: 21 August 2013 08:36
> >> To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
> >> Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security,=
 late
> September
> >>
> >> Just a reminder, as I know a lot of people have been on holiday, pleas=
e
> fill in the doodle
> >>
> >> Thanks
> >> phil
> >>
> >> From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.=
org]
> On Behalf Of philip.eardley@bt.com
> >> Sent: 06 August 2013 13:49
> >> To: multipathtcp@ietf.org
> >> Subject: [multipathtcp] MPTCP interim (audio) meeting on security, lat=
e
> September
> >>
> >> We think it would a good idea to have an interim (audio) meeting, in o=
rder
> to make progress on advancing RFC 6824 on the standards track.
> >>
> >> We will discuss the security of the MPTCP protocol. The aim is to reac=
h
> consensus on what security improvements are needed - and what are not nee=
ded -
> in order to progress MPTCP on the Standards track. We hope to cover both =
the
> threat(s) that we will handle and, at a high-level, the solutions that wi=
ll be
> defined.
> >>
> >> Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table
> >>
> >> For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if =
the
> time is no good for you.
> >>
> >> In the meantime, please keep discussing MPTCP's security on the list!
> >>
> >> Thanks,
> >> Best wishes
> >> Phil & Yoshifumi
> >> _______________________________________________
> >> multipathtcp mailing list
> >> multipathtcp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/multipathtcp
> >
> >
> > *** Please note that this message and any attachments may contain
> confidential and proprietary material and information and are intended on=
ly
> for the use of the intended recipient(s). If you are not the intended
> recipient, you are hereby notified that any review, use, disclosure,
> dissemination, distribution or copying of this message and any attachment=
s is
> strictly prohibited. If you have received this email in error, please
> immediately notify the sender and destroy this e-mail and any attachments=
 and
> all copies, whether electronic or printed. Please also note that any view=
s,
> opinions, conclusions or commitments expressed in this message are those =
of
> the individual sender and do not necessarily reflect the views of Fortine=
t,
> Inc., its affiliates, and emails are not binding on Fortinet and only a
> writing manually signed by Fortinet's General Counsel can be a binding
> commitment of Fortinet to Fortinet's customers or partners. Thank you. **=
*
> > _______________________________________________
> > multipathtcp mailing list
> > multipathtcp@ietf.org
> > https://www.ietf.org/mailman/listinfo/multipathtcp
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp

From elopez@fortinet.com  Tue Sep 10 01:48:31 2013
Return-Path: <elopez@fortinet.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 CBBEE11E818F for <multipathtcp@ietfa.amsl.com>; Tue, 10 Sep 2013 01:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.398
X-Spam-Level: 
X-Spam-Status: No, score=-5.398 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0uGmSS1LbEf for <multipathtcp@ietfa.amsl.com>; Tue, 10 Sep 2013 01:48:27 -0700 (PDT)
Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by ietfa.amsl.com (Postfix) with ESMTP id B419011E818C for <multipathtcp@ietf.org>; Tue, 10 Sep 2013 01:48:27 -0700 (PDT)
From: Edward Lopez <elopez@fortinet.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Thread-Topic: [multipathtcp] MPTCP interim (audio) meeting on security, late September
Thread-Index: AQHOnkEYnt/Sx47MpE2VypdHdwlkaJm1ulSAgAI4KICABQMYAIAB0vew
Date: Tue, 10 Sep 2013 08:48:32 +0000
Message-ID: <D32ECDEE-FD19-422D-B003-08874F1F8281@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>, <CAO249ye2m+mW1x-ZC_E5qMEudsbR7piXspTZwEQjsYsxv4zhUQ@mail.gmail.com>
In-Reply-To: <CAO249ye2m+mW1x-ZC_E5qMEudsbR7piXspTZwEQjsYsxv4zhUQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_D32ECDEEFD19422DB00308874F1F8281fortinetcom_"
MIME-Version: 1.0
X-FEAS-SYSTEM-WL: 192.168.221.213
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 10 Sep 2013 08:48:31 -0000

--_000_D32ECDEEFD19422DB00308874F1F8281fortinetcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

This problem exists on either the client or server side, and is based on =
the fact that content inspection engines deal with traffic from a session=
-based paradigm.  Since an MPTCP session is really an aggregate of TCP se=
ssions (sub-flows), the inspection engine is not seeing the content in th=
e correct context, and is likely to increase its false-negative rate.

If the inspection engine is a transparent-proxy (such as used in anti-mal=
ware and web-filtering), it is buffering and reassembling traffic within =
its supported protocol types, then looking at the reassembled traffic in =
context.  But if the content is split over multiple TCP sessions, the pro=
per content reassembly does not take place.

If the inspection engine is a flow-based engine (such as used in intrusio=
n prevention and application control), since the traffic is streaming acr=
oss separate sessions, the signature (and likely pre-cursor) engines can =
fail to detect.  Flow-based engines have a better likelihood of detection=
 if the patterns are small, and thus within the bounds of a single packet=
.  But the actions taken will impact only the sub-flow the pattern was de=
tected on.

The impact on the client or server depends on the actions configured to b=
e taken by the middlebox.  For example, a strict web-filter may block all=
 sub-flows if it cannot properly detect a URL via reassembly within a tra=
nsparent proxy.

By the way, topology is irrelevant.   Consider the following:


Host A =3D=3D=3D=3D=3D Switch ----- Middlebox A ----- Internet ----- Midd=
lebox B ----- Switch =3D=3D=3D=3D=3D Host B

Even though all traffic is completely routed through both middleboxes, th=
e problem remains.  As I've noted, this is a consequence of the session-b=
ased bias of the inspection engine designs.  There will still be up to fo=
ur subflows (A.1>B.1, A.1>B.2, A.2>B.1, A.2>B.2)

Have there been other multi-session based evasion attempts ... sure.  Man=
y botnets make use of multiple sessions.  However, their pattern of sessi=
on creation can be detected and blocked.  This is the problem that we fac=
e here.  I predict that the initial reaction will be to detect and block =
MPTCP sessions as an evasion technique.  This is because the pattern of s=
ub-flow creation can be detected, and this does not require modification =
of the inspection engine designs.  Enlightened firms may try to modify th=
eir engine designs to accommodate MPTCP, if it can be done predictably an=
d reliably.

I hope this helps your understanding

Ed Lopez

Sent from my iPad

On Sep 8, 2013, at 6:07 PM, "Yoshifumi Nishida" <nishida@sfc.wide.ad.jp<m=
ailto:nishida@sfc.wide.ad.jp>> wrote:

Hi Edward,

I'm trying to understand evasion scenarios since you have raised interest=
ing points.
In my understanding, it will be something like this.

case 1: There're two networks (say ISP1, ISP2) at the server side.
            ISP1 enforces IPS, but ISP2 doesn't.
            In this case, MPTCP can establish initial subflow through ISP=
1, but all contents can go through other subflows through ISP2. So, the t=
raffic of this connection can evade IPS at ISP1

case 2: There're two networks (say ISP1, ISP2) at the server side.
           Both ISP1, ISP2 enforce IPS,
           In this case, MPTCP can split the contents into small chunks a=
nd distributes them through multiple subflows.
           So, IPSs cannot perform inspection properly.

case 3: similar to case2, but use only one ISP.

Are those closed to what you mentioned? Or, am I thinking about totally d=
ifferent things?
Please correct me if I miss something.

Thanks,
--
Yoshifumi


On Thu, Sep 5, 2013 at 10:24 AM, Edward Lopez <elopez@fortinet.com<mailto=
:elopez@fortinet.com>> wrote:
> Phil,
>
> I'm aware that I am relatively new to the WG and IETF as a whole (IETF =
87
> Berlin was my first meeting).  But I do have a long history of security=
 and
> networking protocols, currently working and having worked for a number =
of
> security appliance (middlebox) vendors.
>
> My initial review of MPTCP is that I would have to consider it an evasi=
on
> technique from a content inspection standpoint.  Generally, content
> inspection engines are designed to operate as either flow-based or
> transparent-proxy.  A flow-based engine is generally used by IPS system=
s,
> but has now expanded to support many types of content inspection, most
> notably application control functionality of next-generation firewalls
> (NGFWs).  The limitation of a flow-based engine is that it looks at dat=
a in
> as a stream, generally without reordering and limited data reassembly. =
  A
> transparent proxy engine fully buffers and reassembles the data in the
> context of specific protocols, then inspects this traffic in context.
> Transparent proxies are useful when the inspection device has to intera=
ct
> within the protocol, such as in web-filtering solutions where a block
> message is sent back to an offending user.  However, both of these cont=
ent
> inspection engine types have a general model centered around the sessio=
n
> paradigm.  an MPTCP session is in effect an aggregate of multiple TCP
> sessions (sub flows), so in effect has characteristics of a protocol-ba=
sed
> application, similar to FTP, VoIP, etc.
>
> The effect of MPTCP on content inspection engines is that it can be use=
d as
> an evasion technique.  For example, I could envision the use of multi-h=
omed
> MPTCP-based proxy engines out on the Internet, such that MPTCP based ho=
sts
> in net repressive countries could evade state-imposed web-filters, or s=
chool
> kids could evade their school system's web-filters, etc.  The initial
> reaction from content inspectors would be do develop capabilities to de=
tect
> MPTCP (likely based on options usage), and to either block or force fal=
lback
> to standard TCP.  A significant concern is that this is where the incen=
tive
> ends.  MPTCP is an evasion method, so mitigate the vulnerability.
>
> I would prefer to consider how to support MPTCP, perhaps in the form of=
 an
> application-layer gateway and/or modification of content-inspection eng=
ines
> to deal with aggregation of sub-flows for inspection.  This line of tho=
ught
> lends itself to a philosophical discussion, as to if we intend MPTCP to=
 be
> used to evade content inspection, or if we are looking to improve the
> performance of TCP-based applications.  I mention this because it would=
 be
> desirable for the protocol to assist, or at least not hinder, the abili=
ty to
> identify the multiple sub-flows that create an MPTCP session.
>
> Eventually, I see the rise of middleboxes as MPTCP proxies, whether the=
y are
> TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodologie=
s of
> SSL inspection today.  I am interested in these use-cases because witho=
ut
> them, the default will be to block/fallback, which ultimately isn't use=
ful
> relative to MPTCP.
>
> My US $.02
> Ed Lopez
>
> On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com<mailto:philip.eardley=
@bt.com> wrote:
>
> Just to let you know. The Security Ads are kindly finding us a security=

> advisor, but no luck yet. So we may have to delay this slightly.
> Also, it would be good if there was some discussion on the mailing list=

> before the call.
>
> phil
>
> From: Eardley,PL,Philip,TUB8 R
> Sent: 21 August 2013 08:36
> To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp=
@ietf.org>
> Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, =
late
> September
>
> Just a reminder, as I know a lot of people have been on holiday, please=
 fill
> in the doodle
>
> Thanks
> phil
>
> From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.or=
g> [mailto:multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf=
.org>]
> On Behalf Of philip.eardley@bt.com<mailto:philip.eardley@bt.com>
> Sent: 06 August 2013 13:49
> To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
> Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late=

> September
>
> We think it would a good idea to have an interim (audio) meeting, in or=
der
> to make progress on advancing RFC 6824 on the standards track.
>
> We will discuss the security of the MPTCP protocol. The aim is to reach=

> consensus on what security improvements are needed - and what are not n=
eeded
> - in order to progress MPTCP on the Standards track. We hope to cover b=
oth
> the threat(s) that we will handle and, at a high-level, the solutions t=
hat
> will be defined.
>
> Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table
>
> For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if t=
he
> time is no good for you.
>
> In the meantime, please keep discussing MPTCP=92s security on the list!=

>
> Thanks,
> Best wishes
> Phil & Yoshifumi
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>
> ________________________________
> *** Please note that this message and any attachments may contain
> confidential and proprietary material and information and are intended =
only
> for the use of the intended recipient(s). If you are not the intended
> recipient, you are hereby notified that any review, use, disclosure,
> dissemination, distribution or copying of this message and any attachme=
nts
> is strictly prohibited. If you have received this email in error, pleas=
e
> immediately notify the sender and destroy this e-mail and any attachmen=
ts
> and all copies, whether electronic or printed. Please also note that an=
y
> views, opinions, conclusions or commitments expressed in this message a=
re
> those of the individual sender and do not necessarily reflect the views=
 of
> Fortinet, Inc., its affiliates, and emails are not binding on Fortinet =
and
> only a writing manually signed by Fortinet's General Counsel can be a
> binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk
> you. ***
> ________________________________
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp
>


***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***

--_000_D32ECDEEFD19422DB00308874F1F8281fortinetcom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows=
-1252">
</head>
<body dir=3D"auto">
<div>This problem exists on either the client or server side, and is base=
d on the fact that content inspection engines deal with traffic from a se=
ssion-based paradigm. &nbsp;Since an MPTCP session is really an aggregate=
 of TCP sessions (sub-flows), the inspection
 engine is not seeing the content in the correct context, and is likely t=
o increase its false-negative rate.</div>
<div><br>
</div>
<div>If the inspection engine is a transparent-proxy (such as used in ant=
i-malware and web-filtering), it is buffering and reassembling traffic wi=
thin its supported protocol types, then looking at the reassembled traffi=
c in context. &nbsp;But if the content is split
 over multiple TCP sessions, the proper content reassembly does not take =
place. &nbsp;</div>
<div><br>
</div>
<div>If the inspection engine is a flow-based engine (such as used in int=
rusion prevention and application control), since the traffic is streamin=
g across separate sessions, the signature (and likely pre-cursor) engines=
 can fail to detect. &nbsp;Flow-based engines
 have a better likelihood of detection if the patterns are small, and thu=
s within the bounds of a single packet. &nbsp;But the actions taken will =
impact only the sub-flow the pattern was detected on.</div>
<div><br>
</div>
<div>The impact on the client or server depends on the actions configured=
 to be taken by the middlebox. &nbsp;For example, a strict web-filter may=
 block all sub-flows if it cannot properly detect a URL via reassembly wi=
thin a transparent proxy.</div>
<div><br>
</div>
<div>By the way, topology is irrelevant. &nbsp; Consider the following:</=
div>
<div><br>
</div>
<div><br>
</div>
<div>Host A =3D=3D=3D=3D=3D Switch ----- Middlebox A ----- Internet -----=
 Middlebox B ----- Switch =3D=3D=3D=3D=3D Host B</div>
<div><br>
</div>
<div>Even though all traffic is completely routed through both middleboxe=
s, the problem remains. &nbsp;As I've noted, this is a consequence of the=
 session-based bias of the inspection engine designs. &nbsp;There will st=
ill be up to four subflows (A.1&gt;B.1, A.1&gt;B.2, A.2&gt;B.1,
 A.2&gt;B.2)</div>
<div><br>
</div>
<div>Have there been other multi-session based evasion attempts ... sure.=
 &nbsp;Many botnets make use of multiple sessions. &nbsp;However, their p=
attern of session creation can be detected and blocked. &nbsp;This is the=
 problem that we face here. &nbsp;I predict that the initial
 reaction will be to detect and block MPTCP sessions as an evasion techni=
que. &nbsp;This is because the pattern of sub-flow creation can be detect=
ed, and this does not require modification of the inspection engine desig=
ns. &nbsp;Enlightened firms may try to modify their
 engine designs to accommodate MPTCP, if it can be done predictably and r=
eliably.</div>
<div><br>
</div>
<div>I hope this helps your understanding</div>
<div><br>
</div>
<div>
<div>Ed Lopez</div>
<div><br>
</div>
Sent from my iPad</div>
<div><br>
On Sep 8, 2013, at 6:07 PM, &quot;Yoshifumi Nishida&quot; &lt;<a href=3D"=
mailto:nishida@sfc.wide.ad.jp">nishida@sfc.wide.ad.jp</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">Hi Edward,<br>
<br>
I'm trying to understand evasion scenarios since you have raised interest=
ing points.<br>
In my understanding, it will be something like this.&nbsp;
<div><br>
case 1: There're two networks (say ISP1, ISP2) at the server side. <br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ISP1 enforces IPS, but ISP2 doe=
sn't. <br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In this case, MPTCP can establi=
sh initial subflow through ISP1, but all contents can go through other su=
bflows through ISP2. So, the traffic of this connection can evade IPS at =
ISP1<br>
<br>
case 2: There're two networks (say ISP1, ISP2) at the server side. <br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Both ISP1, ISP2 enforce IPS,&nbs=
p;<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;In this case, MPTCP can split th=
e contents into small chunks and distributes them through multiple subflo=
ws.
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;So, IPSs cannot perform ins=
pection properly.</div>
<div><br>
</div>
<div>case 3: similar to case2, but use only one ISP.<br>
<br>
Are those closed to what you mentioned? Or, am I thinking about totally d=
ifferent things?</div>
<div>Please correct me if I miss something.</div>
<div><br>
Thanks,<br>
--</div>
<div>Yoshifumi<br>
<br>
<br>
On Thu, Sep 5, 2013 at 10:24 AM, Edward Lopez &lt;<a href=3D"mailto:elope=
z@fortinet.com">elopez@fortinet.com</a>&gt; wrote:<br>
&gt; Phil,<br>
&gt;<br>
&gt; I'm aware that I am relatively new to the WG and IETF as a whole (IE=
TF 87<br>
&gt; Berlin was my first meeting). &nbsp;But I do have a long history of =
security and<br>
&gt; networking protocols, currently working and having worked for a numb=
er of<br>
&gt; security appliance (middlebox) vendors.<br>
&gt;<br>
&gt; My initial review of MPTCP is that I would have to consider it an ev=
asion<br>
&gt; technique from a content inspection standpoint. &nbsp;Generally, con=
tent<br>
&gt; inspection engines are designed to operate as either flow-based or<b=
r>
&gt; transparent-proxy. &nbsp;A flow-based engine is generally used by IP=
S systems,<br>
&gt; but has now expanded to support many types of content inspection, mo=
st<br>
&gt; notably application control functionality of next-generation firewal=
ls<br>
&gt; (NGFWs). &nbsp;The limitation of a flow-based engine is that it look=
s at data in<br>
&gt; as a stream, generally without reordering and limited data reassembl=
y. &nbsp; A<br>
&gt; transparent proxy engine fully buffers and reassembles the data in t=
he<br>
&gt; context of specific protocols, then inspects this traffic in context=
.<br>
&gt; Transparent proxies are useful when the inspection device has to int=
eract<br>
&gt; within the protocol, such as in web-filtering solutions where a bloc=
k<br>
&gt; message is sent back to an offending user. &nbsp;However, both of th=
ese content<br>
&gt; inspection engine types have a general model centered around the ses=
sion<br>
&gt; paradigm. &nbsp;an MPTCP session is in effect an aggregate of multip=
le TCP<br>
&gt; sessions (sub flows), so in effect has characteristics of a protocol=
-based<br>
&gt; application, similar to FTP, VoIP, etc.<br>
&gt;<br>
&gt; The effect of MPTCP on content inspection engines is that it can be =
used as<br>
&gt; an evasion technique. &nbsp;For example, I could envision the use of=
 multi-homed<br>
&gt; MPTCP-based proxy engines out on the Internet, such that MPTCP based=
 hosts<br>
&gt; in net repressive countries could evade state-imposed web-filters, o=
r school<br>
&gt; kids could evade their school system's web-filters, etc. &nbsp;The i=
nitial<br>
&gt; reaction from content inspectors would be do develop capabilities to=
 detect<br>
&gt; MPTCP (likely based on options usage), and to either block or force =
fallback<br>
&gt; to standard TCP. &nbsp;A significant concern is that this is where t=
he incentive<br>
&gt; ends. &nbsp;MPTCP is an evasion method, so mitigate the vulnerabilit=
y.<br>
&gt;<br>
&gt; I would prefer to consider how to support MPTCP, perhaps in the form=
 of an<br>
&gt; application-layer gateway and/or modification of content-inspection =
engines<br>
&gt; to deal with aggregation of sub-flows for inspection. &nbsp;This lin=
e of thought<br>
&gt; lends itself to a philosophical discussion, as to if we intend MPTCP=
 to be<br>
&gt; used to evade content inspection, or if we are looking to improve th=
e<br>
&gt; performance of TCP-based applications. &nbsp;I mention this because =
it would be<br>
&gt; desirable for the protocol to assist, or at least not hinder, the ab=
ility to<br>
&gt; identify the multiple sub-flows that create an MPTCP session.<br>
&gt;<br>
&gt; Eventually, I see the rise of middleboxes as MPTCP proxies, whether =
they are<br>
&gt; TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodolo=
gies of<br>
&gt; SSL inspection today. &nbsp;I am interested in these use-cases becau=
se without<br>
&gt; them, the default will be to block/fallback, which ultimately isn't =
useful<br>
&gt; relative to MPTCP.<br>
&gt;<br>
&gt; My US $.02<br>
&gt; Ed Lopez<br>
&gt;<br>
&gt; On Sep 4, 2013, at 3:31 AM, <a href=3D"mailto:philip.eardley@bt.com"=
>philip.eardley@bt.com</a> wrote:<br>
&gt;<br>
&gt; Just to let you know. The Security Ads are kindly finding us a secur=
ity<br>
&gt; advisor, but no luck yet. So we may have to delay this slightly.<br>=

&gt; Also, it would be good if there was some discussion on the mailing l=
ist<br>
&gt; before the call.<br>
&gt; &nbsp;<br>
&gt; phil<br>
&gt; &nbsp;<br>
&gt; From: Eardley,PL,Philip,TUB8 R<br>
&gt; Sent: 21 August 2013 08:36<br>
&gt; To: Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:multipathtcp@ietf.or=
g">multipathtcp@ietf.org</a><br>
&gt; Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on securit=
y, late<br>
&gt; September<br>
&gt; &nbsp;<br>
&gt; Just a reminder, as I know a lot of people have been on holiday, ple=
ase fill<br>
&gt; in the doodle<br>
&gt; &nbsp;<br>
&gt; Thanks<br>
&gt; phil<br>
&gt; &nbsp;<br>
&gt; From: <a href=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-=
bounces@ietf.org</a> [mailto:<a href=3D"mailto:multipathtcp-bounces@ietf.=
org">multipathtcp-bounces@ietf.org</a>]<br>
&gt; On Behalf Of <a href=3D"mailto:philip.eardley@bt.com">philip.eardley=
@bt.com</a><br>
&gt; Sent: 06 August 2013 13:49<br>
&gt; To: <a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</=
a><br>
&gt; Subject: [multipathtcp] MPTCP interim (audio) meeting on security, l=
ate<br>
&gt; September<br>
&gt; &nbsp;<br>
&gt; We think it would a good idea to have an interim (audio) meeting, in=
 order<br>
&gt; to make progress on advancing RFC 6824 on the standards track.<br>
&gt; &nbsp;<br>
&gt; We will discuss the security of the MPTCP protocol. The aim is to re=
ach<br>
&gt; consensus on what security improvements are needed - and what are no=
t needed<br>
&gt; - in order to progress MPTCP on the Standards track. We hope to cove=
r both<br>
&gt; the threat(s) that we will handle and, at a high-level, the solution=
s that<br>
&gt; will be defined.<br>
&gt; &nbsp;<br>
&gt; Please fill in the doodle at <a href=3D"http://doodle.com/xdf8eaiavv=
na9bcy#table">
http://doodle.com/xdf8eaiavvna9bcy#table</a><br>
&gt; &nbsp;<br>
&gt; For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout i=
f the<br>
&gt; time is no good for you.<br>
&gt; &nbsp;<br>
&gt; In the meantime, please keep discussing MPTCP=92s security on the li=
st!<br>
&gt; &nbsp;<br>
&gt; Thanks,<br>
&gt; Best wishes<br>
&gt; Phil &amp; Yoshifumi<br>
&gt; _______________________________________________<br>
&gt; multipathtcp mailing list<br>
&gt; <a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp">https=
://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ________________________________<br>
&gt; *** Please note that this message and any attachments may contain<br=
>
&gt; confidential and proprietary material and information and are intend=
ed only<br>
&gt; for the use of the intended recipient(s). If you are not the intende=
d<br>
&gt; recipient, you are hereby notified that any review, use, disclosure,=
<br>
&gt; dissemination, distribution or copying of this message and any attac=
hments<br>
&gt; is strictly prohibited. If you have received this email in error, pl=
ease<br>
&gt; immediately notify the sender and destroy this e-mail and any attach=
ments<br>
&gt; and all copies, whether electronic or printed. Please also note that=
 any<br>
&gt; views, opinions, conclusions or commitments expressed in this messag=
e are<br>
&gt; those of the individual sender and do not necessarily reflect the vi=
ews of<br>
&gt; Fortinet, Inc., its affiliates, and emails are not binding on Fortin=
et and<br>
&gt; only a writing manually signed by Fortinet's General Counsel can be =
a<br>
&gt; binding commitment of Fortinet to Fortinet's customers or partners. =
Thank<br>
&gt; you. ***<br>
&gt; ________________________________<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; multipathtcp mailing list<br>
&gt; <a href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp">https=
://www.ietf.org/mailman/listinfo/multipathtcp</a><br>
&gt;<br>
</div>
</div>
</div>
</div>
</blockquote>

<font bgcolor=3D"#ffffff" color=3D"#000000"><b><BR><HR>
***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***
<BR><HR></b></font>
</body>
</html>


--_000_D32ECDEEFD19422DB00308874F1F8281fortinetcom_--

From elopez@fortinet.com  Tue Sep 10 01:57:34 2013
Return-Path: <elopez@fortinet.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 5933C11E819E for <multipathtcp@ietfa.amsl.com>; Tue, 10 Sep 2013 01:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level: 
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRR3tzZaEZvV for <multipathtcp@ietfa.amsl.com>; Tue, 10 Sep 2013 01:57:30 -0700 (PDT)
Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5C31F11E8192 for <multipathtcp@ietf.org>; Tue, 10 Sep 2013 01:57:30 -0700 (PDT)
From: Edward Lopez <elopez@fortinet.com>
To: Costin Raiciu <c.raiciu@cs.ucl.ac.uk>
Thread-Topic: [multipathtcp] MPTCP interim (audio) meeting on security, late September
Thread-Index: AQHOrTH2XDwo0LGbbE+diwUh/bQIzpm+rSco
Date: Tue, 10 Sep 2013 08:57:26 +0000
Message-ID: <22143220-3F13-4CAC-AA9C-3624CBFB80AA@fortinet.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com>, <14673454-0285-4E79-87F1-83DA0CB19C7A@cs.ucl.ac.uk>
In-Reply-To: <14673454-0285-4E79-87F1-83DA0CB19C7A@cs.ucl.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FEAS-SYSTEM-WL: 192.168.221.212
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late  September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 10 Sep 2013 08:57:34 -0000

Generally there are two functions relative to TLS ... offload (server) an=
d intercept (client).

For TLS offload, the middlebox is provided with the certificates of the s=
erver(s) it will protect.  TLS sessions are terminated on the middlebox, =
inspected, and forwarded to the server (optionally put into another TLS s=
ession between the middlebox and the server)

For TLS intercept, the middlebox generally performs a proxy function, and=
 has a certificate that is accepted by the hosts it is inspecting (or the=
 client otherwise receives a bad certificate warning).  The TLS sessions =
from the host are terminated on the middlebox, which in turn inspects thi=
s traffic, and repackages it into a new TLS session to its intended recip=
ient.

In either case, once the traffic is decrypted, a whole range of content i=
nspection functions can be performed on the traffic.

Ed Lopez

Sent from my iPad

On Sep 9, 2013, at 3:55 AM, "Costin Raiciu" <c.raiciu@cs.ucl.ac.uk> wrote=
:

> Can I ask what such boxes do with TLS connections?
> Costin
> 
> 
> On 5 Sep 2013, at 20:24, Edward Lopez wrote:
> 
>> Phil,
>> 
>> I'm aware that I am relatively new to the WG and IETF as a whole (IETF=
 87 Berlin was my first meeting).  But I do have a long history of securi=
ty and networking protocols, currently working and having worked for a nu=
mber of security appliance (middlebox) vendors.
>> 
>> My initial review of MPTCP is that I would have to consider it an evas=
ion technique from a content inspection standpoint.  Generally, content i=
nspection engines are designed to operate as either flow-based or transpa=
rent-proxy.  A flow-based engine is generally used by IPS systems, but ha=
s now expanded to support many types of content inspection, most notably =
application control functionality of next-generation firewalls (NGFWs).  =
The limitation of a flow-based engine is that it looks at data in as a st=
ream, generally without reordering and limited data reassembly.   A trans=
parent proxy engine fully buffers and reassembles the data in the context=
 of specific protocols, then inspects this traffic in context.  Transpare=
nt proxies are useful when the inspection device has to interact within t=
he protocol, such as in web-filtering solutions where a block message is =
sent back to an offending user.  However, both of these content inspectio=
n engine types have a general model centered around the session paradigm.=
  an MPTCP session is in effect an aggregate of multiple TCP sessions (su=
b flows), so in effect has characteristics of a protocol-based applicatio=
n, similar to FTP, VoIP, etc.
>> 
>> The effect of MPTCP on content inspection engines is that it can be us=
ed as an evasion technique.  For example, I could envision the use of mul=
ti-homed MPTCP-based proxy engines out on the Internet, such that MPTCP b=
ased hosts in net repressive countries could evade state-imposed web-filt=
ers, or school kids could evade their school system's web-filters, etc.  =
The initial reaction from content inspectors would be do develop capabili=
ties to detect MPTCP (likely based on options usage), and to either block=
 or force fallback to standard TCP.  A significant concern is that this i=
s where the incentive ends.  MPTCP is an evasion method, so mitigate the =
vulnerability. 
>> 
>> I would prefer to consider how to support MPTCP, perhaps in the form o=
f an application-layer gateway and/or modification of content-inspection =
engines to deal with aggregation of sub-flows for inspection.  This line =
of thought lends itself to a philosophical discussion, as to if we intend=
 MPTCP to be used to evade content inspection, or if we are looking to im=
prove the performance of TCP-based applications.  I mention this because =
it would be desirable for the protocol to assist, or at least not hinder,=
 the ability to identify the multiple sub-flows that create an MPTCP sess=
ion.
>> 
>> Eventually, I see the rise of middleboxes as MPTCP proxies, whether th=
ey are TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the methodo=
logies of SSL inspection today.  I am interested in these use-cases becau=
se without them, the default will be to block/fallback, which ultimately =
isn't useful relative to MPTCP.
>> 
>> My US $.02
>> Ed Lopez 
>> 
>> On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
>> 
>>> Just to let you know. The Security Ads are kindly finding us a securi=
ty advisor, but no luck yet. So we may have to delay this slightly.
>>> Also, it would be good if there was some discussion on the mailing li=
st before the call.
>>> 
>>> phil
>>> 
>>> From: Eardley,PL,Philip,TUB8 R 
>>> Sent: 21 August 2013 08:36
>>> To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
>>> Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security=
, late September
>>> 
>>> Just a reminder, as I know a lot of people have been on holiday, plea=
se fill in the doodle
>>> 
>>> Thanks
>>> phil
>>> 
>>> From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf=
.org] On Behalf Of philip.eardley@bt.com
>>> Sent: 06 August 2013 13:49
>>> To: multipathtcp@ietf.org
>>> Subject: [multipathtcp] MPTCP interim (audio) meeting on security, la=
te September
>>> 
>>> We think it would a good idea to have an interim (audio) meeting, in =
order to make progress on advancing RFC 6824 on the standards track.
>>> 
>>> We will discuss the security of the MPTCP protocol. The aim is to rea=
ch consensus on what security improvements are needed - and what are not =
needed - in order to progress MPTCP on the Standards track. We hope to co=
ver both the threat(s) that we will handle and, at a high-level, the solu=
tions that will be defined.
>>> 
>>> Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table=

>>> 
>>> For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if=
 the time is no good for you.
>>> 
>>> In the meantime, please keep discussing MPTCP=92s security on the lis=
t!
>>> 
>>> Thanks,
>>> Best wishes
>>> Phil & Yoshifumi
>>> _______________________________________________
>>> multipathtcp mailing list
>>> multipathtcp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multipathtcp
>> 
>> 
>> *** Please note that this message and any attachments may contain conf=
idential and proprietary material and information and are intended only f=
or the use of the intended recipient(s). If you are not the intended reci=
pient, you are hereby notified that any review, use, disclosure, dissemin=
ation, distribution or copying of this message and any attachments is str=
ictly prohibited. If you have received this email in error, please immedi=
ately notify the sender and destroy this e-mail and any attachments and a=
ll copies, whether electronic or printed. Please also note that any views=
, opinions, conclusions or commitments expressed in this message are thos=
e of the individual sender and do not necessarily reflect the views of Fo=
rtinet, Inc., its affiliates, and emails are not binding on Fortinet and =
only a writing manually signed by Fortinet's General Counsel can be a bin=
ding commitment of Fortinet to Fortinet's customers or partners. Thank yo=
u. *** 
>> _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp
> 

***  Please note that this message and any attachments may contain confid=
ential 
and proprietary material and information and are intended only for the us=
e of 
the intended recipient(s). If you are not the intended recipient, you are=
 hereby 
notified that any review, use, disclosure, dissemination, distribution or=
 copying 
of this message and any attachments is strictly prohibited. If you have r=
eceived 
this email in error, please immediately notify the sender and destroy thi=
s e-mail 
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments exp=
ressed 
in this message are those of the individual sender and do not necessarily=
 reflect 
the views of Fortinet, Inc., its affiliates, and emails are not binding o=
n 
Fortinet and only a writing manually signed by Fortinet's General Counsel=
 can be 
a binding commitment of Fortinet to Fortinet's customers or partners. Tha=
nk you. ***


From iesg-secretary@ietf.org  Tue Sep 10 14:19:41 2013
Return-Path: <iesg-secretary@ietf.org>
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 29EFD11E8125; Tue, 10 Sep 2013 14:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level: 
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSA6IxG8mJ8f; Tue, 10 Sep 2013 14:19:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D58C711E8106; Tue, 10 Sep 2013 14:19:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.71.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130910211939.4785.60570.idtracker@ietfa.amsl.com>
Date: Tue, 10 Sep 2013 14:19:39 -0700
Cc: multipathtcp@ietf.org
Subject: [multipathtcp] MPTCP WG Virtual Interim Meeting, 3 October 2013
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: ietf@ietf.org
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: Tue, 10 Sep 2013 21:19:41 -0000

The MPTCP WG will hold a virtual interim meeting on Thursday, 3rd =

October at 1500 GMT*. =


Agenda and WebEx information will be posted on the mailing list:
http://www.ietf.org/mail-archive/web/multipathtcp/current/maillist.html

* Time zone converter: =

  http://www.worldtimeserver.com/convert_time_in_UTC.aspx

From philip.eardley@bt.com  Wed Sep 11 00:31:01 2013
Return-Path: <philip.eardley@bt.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 E481E11E81DE for <multipathtcp@ietfa.amsl.com>; Wed, 11 Sep 2013 00:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.183
X-Spam-Level: 
X-Spam-Status: No, score=-104.183 tagged_above=-999 required=5 tests=[AWL=0.815, BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8K5SJoU37-wS for <multipathtcp@ietfa.amsl.com>; Wed, 11 Sep 2013 00:30:58 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.com [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 60D5A11E8145 for <multipathtcp@ietf.org>; Wed, 11 Sep 2013 00:30:57 -0700 (PDT)
Received: from EVMHT61-UKRD.domain1.systemhost.net (10.36.3.127) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 11 Sep 2013 08:30:56 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.113]) by EVMHT61-UKRD.domain1.systemhost.net ([10.36.3.127]) with mapi; Wed, 11 Sep 2013 08:30:56 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Date: Wed, 11 Sep 2013 08:30:55 +0100
Thread-Topic: Meeting invitation: MPTCP WG Virtual Interim Meeting
Thread-Index: Ac6uaoPy31U94aJbRtSTWCjhLeOjcQAVew+g
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B0585@EMV67-UKRD.domain1.systemhost.net>
References: <36240095.7962.1378847570822.JavaMail.nobody@jva2tc114.webex.com>
In-Reply-To: <36240095.7962.1378847570822.JavaMail.nobody@jva2tc114.webex.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_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B0585EMV67UKRDdoma_"
MIME-Version: 1.0
Subject: [multipathtcp] FW: Meeting invitation: MPTCP WG Virtual Interim Meeting
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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 Sep 2013 07:31:02 -0000

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

SGVyZSBhcmUgdGhlIGRldGFpbHMgb2YgdGhlIGF1ZGlvICh3aGljaCB3ZeKAmWxsIHJlY29yZCkN
CkkgYWxzbyBjcmVhdGVkIGEgd2lraSBodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy9tcHRj
cC90cmFjL3dpa2kvSW50ZXJpbV9PY3RfMjAxMyMNCg0KVGhhbmtzDQpwaGlsDQoNCkZyb206IENp
bmR5IE1vcmdhbiBbbWFpbHRvOm1lc3NlbmdlckB3ZWJleC5jb21dDQpTZW50OiAxMCBTZXB0ZW1i
ZXIgMjAxMyAyMjoxMw0KVG86IEVhcmRsZXksUEwsUGhpbGlwLFRVQjggUg0KU3ViamVjdDogTWVl
dGluZyBpbnZpdGF0aW9uOiBNUFRDUCBXRyBWaXJ0dWFsIEludGVyaW0gTWVldGluZw0KDQoNCkhl
bGxvICwNCg0KQ2luZHkgTW9yZ2FuIGludml0ZXMgeW91IHRvIGF0dGVuZCB0aGlzIG9ubGluZSBt
ZWV0aW5nLg0KDQpUb3BpYzogTVBUQ1AgV0cgVmlydHVhbCBJbnRlcmltIE1lZXRpbmcNCkRhdGU6
IFRodXJzZGF5LCBPY3RvYmVyIDMsIDIwMTMNClRpbWU6IDM6MDAgcG0sIEdyZWVud2ljaCBUaW1l
IChSZXlramF2aWssIEdNVCkNCk1lZXRpbmcgTnVtYmVyOiA2NDYgMDc3IDk1MA0KTWVldGluZyBQ
YXNzd29yZDogMTIzNA0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NClRvIGpvaW4gdGhlIG9ubGluZSBtZWV0aW5nIChOb3cgZnJvbSBt
b2JpbGUgZGV2aWNlcyEpDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQoxLiBHbyB0byBodHRwczovL2lldGYud2ViZXguY29tL2lldGYvai5w
aHA/RUQ9MjM1NDM0NzY3JlVJRD0xNjM0NDgxMDg3JlBXPU5aVGhpTmpsa05UVmkmUlQ9TWlNeU1B
JTNEJTNEDQoyLiBJZiByZXF1ZXN0ZWQsIGVudGVyIHlvdXIgbmFtZSBhbmQgZW1haWwgYWRkcmVz
cy4NCjMuIElmIGEgcGFzc3dvcmQgaXMgcmVxdWlyZWQsIGVudGVyIHRoZSBtZWV0aW5nIHBhc3N3
b3JkOiAxMjM0DQo0LiBDbGljayAiSm9pbiIuDQoNClRvIHZpZXcgaW4gb3RoZXIgdGltZSB6b25l
cyBvciBsYW5ndWFnZXMsIHBsZWFzZSBjbGljayB0aGUgbGluazoNCmh0dHBzOi8vaWV0Zi53ZWJl
eC5jb20vaWV0Zi9qLnBocD9FRD0yMzU0MzQ3NjcmVUlEPTE2MzQ0ODEwODcmUFc9TlpUaGlOamxr
TlRWaSZPUlQ9TWlNeU1BJTNEJTNEDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClRvIGpvaW4gdGhlIGF1ZGlvIGNvbmZlcmVuY2Ugb25s
eQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KQ2FsbC1pbiB0b2xsIG51bWJlciAoVVMvQ2FuYWRhKTogMS02NTAtNDc5LTMyMDgNCg0KQWNj
ZXNzIGNvZGU6NjQ2IDA3NyA5NTANCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KRm9yIGFzc2lzdGFuY2UNCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCjEuIEdvIHRvIGh0dHBzOi8v
aWV0Zi53ZWJleC5jb20vaWV0Zi9tYw0KMi4gT24gdGhlIGxlZnQgbmF2aWdhdGlvbiBiYXIsIGNs
aWNrICJTdXBwb3J0Ii4NCg0KWW91IGNhbiBjb250YWN0IG1lIGF0Og0KY21vcmdhbkBhbXNsLmNv
bTxtYWlsdG86Y21vcmdhbkBhbXNsLmNvbT4NCjEtNTEwLTQ5Mi00MDg1DQoNClRvIGFkZCB0aGlz
IG1lZXRpbmcgdG8geW91ciBjYWxlbmRhciBwcm9ncmFtIChmb3IgZXhhbXBsZSBNaWNyb3NvZnQg
T3V0bG9vayksIGNsaWNrIHRoaXMgbGluazoNCmh0dHBzOi8vaWV0Zi53ZWJleC5jb20vaWV0Zi9q
LnBocD9FRD0yMzU0MzQ3NjcmVUlEPTE2MzQ0ODEwODcmSUNTPU1JJkxEPTEmUkQ9MiZTVD0xJlNI
QTI9QUFBQUFuT1pUUEVBcEY4Vm5SWTB0WkEtV25wd1VXVWJ0WThHZnEzUjRzWkxCa3RxJlJUPU1p
TXlNQSUzRCUzRA0KDQpUaGUgcGxheWJhY2sgb2YgVUNGIChVbml2ZXJzYWwgQ29tbXVuaWNhdGlv
bnMgRm9ybWF0KSByaWNoIG1lZGlhIGZpbGVzIHJlcXVpcmVzIGFwcHJvcHJpYXRlIHBsYXllcnMu
IFRvIHZpZXcgdGhpcyB0eXBlIG9mIHJpY2ggbWVkaWEgZmlsZXMgaW4gdGhlIG1lZXRpbmcsIHBs
ZWFzZSBjaGVjayB3aGV0aGVyIHlvdSBoYXZlIHRoZSBwbGF5ZXJzIGluc3RhbGxlZCBvbiB5b3Vy
IGNvbXB1dGVyIGJ5IGdvaW5nIHRvIGh0dHBzOi8vaWV0Zi53ZWJleC5jb20vaWV0Zi9zeXN0ZW1k
aWFnbm9zaXMucGhwLg0KDQpTaWduIHVwIGZvciBhIGZyZWUgdHJpYWwgb2YgV2ViRXgNCmh0dHA6
Ly93d3cud2ViZXguY29tL2dvL21jZW1mcmVldHJpYWwNCg0KaHR0cDovL3d3dy53ZWJleC5jb20N
Cg0KQ0NQOisxNjUwNDc5MzIwOHg2NDYwNzc5NTAjDQoNCklNUE9SVEFOVCBOT1RJQ0U6IFRoaXMg
V2ViRXggc2VydmljZSBpbmNsdWRlcyBhIGZlYXR1cmUgdGhhdCBhbGxvd3MgYXVkaW8gYW5kIGFu
eSBkb2N1bWVudHMgYW5kIG90aGVyIG1hdGVyaWFscyBleGNoYW5nZWQgb3Igdmlld2VkIGR1cmlu
ZyB0aGUgc2Vzc2lvbiB0byBiZSByZWNvcmRlZC4gQnkgam9pbmluZyB0aGlzIHNlc3Npb24sIHlv
dSBhdXRvbWF0aWNhbGx5IGNvbnNlbnQgdG8gc3VjaCByZWNvcmRpbmdzLiBJZiB5b3UgZG8gbm90
IGNvbnNlbnQgdG8gdGhlIHJlY29yZGluZywgZGlzY3VzcyB5b3VyIGNvbmNlcm5zIHdpdGggdGhl
IG1lZXRpbmcgaG9zdCBwcmlvciB0byB0aGUgc3RhcnQgb2YgdGhlIHJlY29yZGluZyBvciBkbyBu
b3Qgam9pbiB0aGUgc2Vzc2lvbi4gUGxlYXNlIG5vdGUgdGhhdCBhbnkgc3VjaCByZWNvcmRpbmdz
IG1heSBiZSBzdWJqZWN0IHRvIGRpc2NvdmVyeSBpbiB0aGUgZXZlbnQgb2YgbGl0aWdhdGlvbi4N
Cg==

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B0585EMV67UKRDdoma_
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
cmlmIjtjb2xvcjpibHVlJz5IZXJlIGFyZSB0aGUgZGV0YWlscyBvZiB0aGUgYXVkaW8gKHdoaWNo
IHdl4oCZbGwgcmVjb3JkKTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiO2NvbG9yOmJsdWUn
PkkgYWxzbyBjcmVhdGVkIGEgd2lraSA8YSBocmVmPSJodHRwOi8vdHJhYy50b29scy5pZXRmLm9y
Zy93Zy9tcHRjcC90cmFjL3dpa2kvSW50ZXJpbV9PY3RfMjAxMyMiPmh0dHA6Ly90cmFjLnRvb2xz
LmlldGYub3JnL3dnL21wdGNwL3RyYWMvd2lraS9JbnRlcmltX09jdF8yMDEzIzwvYT4gPG86cD48
L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1mYW1p
bHk6IkFyaWFsIiwic2Fucy1zZXJpZiI7Y29sb3I6Ymx1ZSc+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1mYW1pbHk6IkFyaWFs
Iiwic2Fucy1zZXJpZiI7Y29sb3I6Ymx1ZSc+VGhhbmtzPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1mYW1pbHk6IkFyaWFsIiwic2Fucy1z
ZXJpZiI7Y29sb3I6Ymx1ZSc+cGhpbDxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtZmFtaWx5OiJBcmlhbCIsInNhbnMtc2VyaWYiO2NvbG9y
OmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+
PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFo
b21hIiwic2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVOLVVTIHN0eWxl
PSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+IENp
bmR5IE1vcmdhbiBbbWFpbHRvOm1lc3NlbmdlckB3ZWJleC5jb21dIDxicj48Yj5TZW50OjwvYj4g
MTAgU2VwdGVtYmVyIDIwMTMgMjI6MTM8YnI+PGI+VG86PC9iPiBFYXJkbGV5LFBMLFBoaWxpcCxU
VUI4IFI8YnI+PGI+U3ViamVjdDo8L2I+IE1lZXRpbmcgaW52aXRhdGlvbjogTVBUQ1AgV0cgVmly
dHVhbCBJbnRlcmltIE1lZXRpbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y
bWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPjxicj5I
ZWxsbyAsIDxicj48YnI+Q2luZHkgTW9yZ2FuIGludml0ZXMgeW91IHRvIGF0dGVuZCB0aGlzIG9u
bGluZSBtZWV0aW5nLiA8YnI+PGJyPlRvcGljOiBNUFRDUCBXRyBWaXJ0dWFsIEludGVyaW0gTWVl
dGluZyA8YnI+RGF0ZTogVGh1cnNkYXksIE9jdG9iZXIgMywgMjAxMyA8YnI+VGltZTogMzowMCBw
bSwgR3JlZW53aWNoIFRpbWUgKFJleWtqYXZpaywgR01UKSA8YnI+TWVldGluZyBOdW1iZXI6IDY0
NiAwNzcgOTUwIDxicj5NZWV0aW5nIFBhc3N3b3JkOiAxMjM0IDxicj48YnI+PGJyPi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gPGJyPlRvIGpv
aW4gdGhlIG9ubGluZSBtZWV0aW5nIChOb3cgZnJvbSBtb2JpbGUgZGV2aWNlcyEpIDxicj4tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIDxicj4x
LiBHbyB0byA8YSBocmVmPSJodHRwczovL2lldGYud2ViZXguY29tL2lldGYvai5waHA/RUQ9MjM1
NDM0NzY3JmFtcDtVSUQ9MTYzNDQ4MTA4NyZhbXA7UFc9TlpUaGlOamxrTlRWaSZhbXA7UlQ9TWlN
eU1BJTNEJTNEIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9pZXRmLndlYmV4LmNvbS9pZXRmL2ou
cGhwP0VEPTIzNTQzNDc2NyZhbXA7VUlEPTE2MzQ0ODEwODcmYW1wO1BXPU5aVGhpTmpsa05UVmkm
YW1wO1JUPU1pTXlNQSUzRCUzRDwvYT4gPGJyPjIuIElmIHJlcXVlc3RlZCwgZW50ZXIgeW91ciBu
YW1lIGFuZCBlbWFpbCBhZGRyZXNzLiA8YnI+My4gSWYgYSBwYXNzd29yZCBpcyByZXF1aXJlZCwg
ZW50ZXIgdGhlIG1lZXRpbmcgcGFzc3dvcmQ6IDEyMzQgPGJyPjQuIENsaWNrICZxdW90O0pvaW4m
cXVvdDsuIDxicj48YnI+VG8gdmlldyBpbiBvdGhlciB0aW1lIHpvbmVzIG9yIGxhbmd1YWdlcywg
cGxlYXNlIGNsaWNrIHRoZSBsaW5rOiA8YnI+PGEgaHJlZj0iaHR0cHM6Ly9pZXRmLndlYmV4LmNv
bS9pZXRmL2oucGhwP0VEPTIzNTQzNDc2NyZhbXA7VUlEPTE2MzQ0ODEwODcmYW1wO1BXPU5aVGhp
Tmpsa05UVmkmYW1wO09SVD1NaU15TUElM0QlM0QiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2ll
dGYud2ViZXguY29tL2lldGYvai5waHA/RUQ9MjM1NDM0NzY3JmFtcDtVSUQ9MTYzNDQ4MTA4NyZh
bXA7UFc9TlpUaGlOamxrTlRWaSZhbXA7T1JUPU1pTXlNQSUzRCUzRDwvYT4gPGJyPjxicj4tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIDxicj5U
byBqb2luIHRoZSBhdWRpbyBjb25mZXJlbmNlIG9ubHkgPGJyPi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gPGJyPkNhbGwtaW4gdG9sbCBudW1i
ZXIgKFVTL0NhbmFkYSk6IDEtNjUwLTQ3OS0zMjA4IDxicj48YnI+QWNjZXNzIGNvZGU6NjQ2IDA3
NyA5NTAgPGJyPjxicj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tIDxicj5Gb3IgYXNzaXN0YW5jZSA8YnI+LS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSA8YnI+MS4gR28gdG8gPGEgaHJlZj0i
aHR0cHM6Ly9pZXRmLndlYmV4LmNvbS9pZXRmL21jIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9p
ZXRmLndlYmV4LmNvbS9pZXRmL21jPC9hPiA8YnI+Mi4gT24gdGhlIGxlZnQgbmF2aWdhdGlvbiBi
YXIsIGNsaWNrICZxdW90O1N1cHBvcnQmcXVvdDsuIDxicj48YnI+WW91IGNhbiBjb250YWN0IG1l
IGF0OiA8YnI+PGEgaHJlZj0ibWFpbHRvOmNtb3JnYW5AYW1zbC5jb20iPmNtb3JnYW5AYW1zbC5j
b208L2E+IDxicj4xLTUxMC00OTItNDA4NSA8YnI+PGJyPlRvIGFkZCB0aGlzIG1lZXRpbmcgdG8g
eW91ciBjYWxlbmRhciBwcm9ncmFtIChmb3IgZXhhbXBsZSBNaWNyb3NvZnQgT3V0bG9vayksIGNs
aWNrIHRoaXMgbGluazogPGJyPjxhIGhyZWY9Imh0dHBzOi8vaWV0Zi53ZWJleC5jb20vaWV0Zi9q
LnBocD9FRD0yMzU0MzQ3NjcmYW1wO1VJRD0xNjM0NDgxMDg3JmFtcDtJQ1M9TUkmYW1wO0xEPTEm
YW1wO1JEPTImYW1wO1NUPTEmYW1wO1NIQTI9QUFBQUFuT1pUUEVBcEY4Vm5SWTB0WkEtV25wd1VX
VWJ0WThHZnEzUjRzWkxCa3RxJmFtcDtSVD1NaU15TUElM0QlM0QiIHRhcmdldD0iX2JsYW5rIj5o
dHRwczovL2lldGYud2ViZXguY29tL2lldGYvai5waHA/RUQ9MjM1NDM0NzY3JmFtcDtVSUQ9MTYz
NDQ4MTA4NyZhbXA7SUNTPU1JJmFtcDtMRD0xJmFtcDtSRD0yJmFtcDtTVD0xJmFtcDtTSEEyPUFB
QUFBbk9aVFBFQXBGOFZuUlkwdFpBLVducHdVV1VidFk4R2ZxM1I0c1pMQmt0cSZhbXA7UlQ9TWlN
eU1BJTNEJTNEPC9hPiA8YnI+PGJyPlRoZSBwbGF5YmFjayBvZiBVQ0YgKFVuaXZlcnNhbCBDb21t
dW5pY2F0aW9ucyBGb3JtYXQpIHJpY2ggbWVkaWEgZmlsZXMgcmVxdWlyZXMgYXBwcm9wcmlhdGUg
cGxheWVycy4gVG8gdmlldyB0aGlzIHR5cGUgb2YgcmljaCBtZWRpYSBmaWxlcyBpbiB0aGUgbWVl
dGluZywgcGxlYXNlIGNoZWNrIHdoZXRoZXIgeW91IGhhdmUgdGhlIHBsYXllcnMgaW5zdGFsbGVk
IG9uIHlvdXIgY29tcHV0ZXIgYnkgZ29pbmcgdG8gPGEgaHJlZj0iaHR0cHM6Ly9pZXRmLndlYmV4
LmNvbS9pZXRmL3N5c3RlbWRpYWdub3Npcy5waHAiPmh0dHBzOi8vaWV0Zi53ZWJleC5jb20vaWV0
Zi9zeXN0ZW1kaWFnbm9zaXMucGhwPC9hPi4gPGJyPjxicj5TaWduIHVwIGZvciBhIGZyZWUgdHJp
YWwgb2YgV2ViRXggPGJyPjxhIGhyZWY9Imh0dHA6Ly93d3cud2ViZXguY29tL2dvL21jZW1mcmVl
dHJpYWwiIHRhcmdldD0iX2JsYW5rIj5odHRwOi8vd3d3LndlYmV4LmNvbS9nby9tY2VtZnJlZXRy
aWFsPC9hPiA8YnI+PGJyPjxhIGhyZWY9Imh0dHA6Ly93d3cud2ViZXguY29tIiB0YXJnZXQ9Il9i
bGFuayI+aHR0cDovL3d3dy53ZWJleC5jb208L2E+IDxicj48YnI+Q0NQOisxNjUwNDc5MzIwOHg2
NDYwNzc5NTAjIDxicj48YnI+SU1QT1JUQU5UIE5PVElDRTogVGhpcyBXZWJFeCBzZXJ2aWNlIGlu
Y2x1ZGVzIGEgZmVhdHVyZSB0aGF0IGFsbG93cyBhdWRpbyBhbmQgYW55IGRvY3VtZW50cyBhbmQg
b3RoZXIgbWF0ZXJpYWxzIGV4Y2hhbmdlZCBvciB2aWV3ZWQgZHVyaW5nIHRoZSBzZXNzaW9uIHRv
IGJlIHJlY29yZGVkLiBCeSBqb2luaW5nIHRoaXMgc2Vzc2lvbiwgeW91IGF1dG9tYXRpY2FsbHkg
Y29uc2VudCB0byBzdWNoIHJlY29yZGluZ3MuIElmIHlvdSBkbyBub3QgY29uc2VudCB0byB0aGUg
cmVjb3JkaW5nLCBkaXNjdXNzIHlvdXIgY29uY2VybnMgd2l0aCB0aGUgbWVldGluZyBob3N0IHBy
aW9yIHRvIHRoZSBzdGFydCBvZiB0aGUgcmVjb3JkaW5nIG9yIGRvIG5vdCBqb2luIHRoZSBzZXNz
aW9uLiBQbGVhc2Ugbm90ZSB0aGF0IGFueSBzdWNoIHJlY29yZGluZ3MgbWF5IGJlIHN1YmplY3Qg
dG8gZGlzY292ZXJ5IGluIHRoZSBldmVudCBvZiBsaXRpZ2F0aW9uLiA8L3NwYW4+PG86cD48L286
cD48L3A+PC9kaXY+PC9ib2R5PjwvaHRtbD4=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B0585EMV67UKRDdoma_--

From iesg-secretary@ietf.org  Thu Sep 12 08:52:11 2013
Return-Path: <iesg-secretary@ietf.org>
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 3B0EF21E814D; Thu, 12 Sep 2013 08:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.394
X-Spam-Level: 
X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFJ8k5SD2QUx; Thu, 12 Sep 2013 08:52:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9695021E814A; Thu, 12 Sep 2013 08:52:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.71.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130912155210.8708.20968.idtracker@ietfa.amsl.com>
Date: Thu, 12 Sep 2013 08:52:10 -0700
Cc: multipathtcp@ietf.org
Subject: [multipathtcp] Update: MPTCP WG Virtual Interim Meeting, 3 October 2013
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: ietf@ietf.org
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 Sep 2013 15:52:11 -0000

The Multipath TCP WG (mptcp) is having an interim (audio) meeting on =

Thursday 3rd October at 3pm GMT.

This will concentrate on security in order to make progress on advancing =

RFC 6824 on the standards track. The aim is to reach consensus on what =

security improvements are needed - and what are not needed - in order to =

progress MPTCP on the Standards track. We hope to cover both the =

threat(s) that we will handle and, at a high-level, the solutions that =

will be defined.

Webex / Audio details are at =

http://trac.tools.ietf.org/wg/mptcp/trac/wiki/Interim_Oct_2013#

Thanks
Philip Eardley & Yoshifumi Nishida (mptcp wg chairs)


On Sep 10, 2013, at 2:19 PM, IESG Secretary wrote:
> The MPTCP WG will hold a virtual interim meeting on Thursday, 3rd =

> October at 1500 GMT*. =

> =

> Agenda and WebEx information will be posted on the mailing list:
> http://www.ietf.org/mail-archive/web/multipathtcp/current/maillist.html
> =

> * Time zone converter: =

>  http://www.worldtimeserver.com/convert_time_in_UTC.aspx

From anumita_biswas@apple.com  Fri Sep 13 11:52:49 2013
Return-Path: <anumita_biswas@apple.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 D171321E809C for <multipathtcp@ietfa.amsl.com>; Fri, 13 Sep 2013 11:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.909
X-Spam-Level: 
X-Spam-Status: No, score=-7.909 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7bC2xqBooD89 for <multipathtcp@ietfa.amsl.com>; Fri, 13 Sep 2013 11:52:42 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9661121E80CF for <multipathtcp@ietf.org>; Fri, 13 Sep 2013 11:52:40 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vsj7eP6m/MnVoE3Orlo8/Q)"
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MT200HIJV3K6D71@mail-out.apple.com> for multipathtcp@ietf.org; Fri, 13 Sep 2013 11:52:39 -0700 (PDT)
X-AuditID: 11807158-b7fea6d000001e19-6e-52335ef66e34
Received: from panthera-tigris.apple.com (panthera-tigris.apple.com [17.193.13.99]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id C0.86.07705.6FE53325; Fri, 13 Sep 2013 11:52:38 -0700 (PDT)
From: Anumita Biswas <anumita_biswas@apple.com>
In-reply-to: <D32ECDEE-FD19-422D-B003-08874F1F8281@fortinet.com>
Date: Fri, 13 Sep 2013 11:52:38 -0700
Message-id: <E9F592FF-A24F-4671-BF6B-5CA72DA73E9B@apple.com>
References: <9510D26531EF184D9017DF24659BB87F35CD40D536@EMV65-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF8C54EF8@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9411C30@EMV67-UKRD.domain1.systemhost.net> <0215C1A2-80E1-4BCC-8A43-A4530D231B27@fortinet.com> <CAO249ye2m+mW1x-ZC_E5qMEudsbR7piXspTZwEQjsYsxv4zhUQ@mail.gmail.com> <D32ECDEE-FD19-422D-B003-08874F1F8281@fortinet.com>
To: Edward Lopez <elopez@fortinet.com>
X-Mailer: Apple Mail (2.1805)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUieJA3WfdbnHGQwZzLNhYt39MsPq++zmax cckNNgdmj/2n17B5LFnyk8nj4uvrzAHMUVw2Kak5mWWpRfp2CVwZ57e/Yy649IGx4tr0d0wN jGeOMnYxcnBICJhIrP0q38XICWSKSVy4t54NxBYSWMgkcWNrDkgJs0CCxPRpgSBhXgE9iY/X ljOC2MICoRLfV20Ds9kE9CWOPrrBDGJzCjhIrHzwih3EZhFQlTjf8pcFxGYWSJTY/nsOM8Qc G4lFm+4BxbmAVi1llrizaTJYg4iAmsS/6d3MEPfISpydPJF1AiPfLIQzZiE5YxbYWG2JZQtf M0PYBhJPO1+xYorrS7x5N4dpASPbKkaBotScxEpTvcSCgpxUveT83E2MoKBtKIzYwfh/mdUh RgEORiUe3g++xkFCrIllxZW5hxglOJiVRHhn3TUKEuJNSaysSi3Kjy8qzUktPsQozcGiJM57 xhsoJZCeWJKanZpakFoEk2Xi4JRqYDSrtZ4ivXRGzsoVUpIlzmfN7nxzktdjOK/xfvfvSq0r x7K/269MFWSZ+6T05NlSjj33njnNvPPjT4RLxAbZVqbpIa85i54e//XSYY6/gYa7/anszgPB 0R2duoc0bSd/9Vz5kaUiSMjlw80+lTtupzzsdO+ozM6SZ5eWN6wKObF6Ya9ym2ukjxJLcUai oRZzUXEiABokY9NWAgAA
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late September
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 13 Sep 2013 18:52:49 -0000

--Boundary_(ID_vsj7eP6m/MnVoE3Orlo8/Q)
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: quoted-printable

Hi,

Just want to share my 2c on this:

> Have there been other multi-session based evasion attempts ... sure.  =
Many botnets make use of multiple sessions.  However, their pattern of =
session creation can be detected and blocked.  This is the problem that =
we face here.  I predict that the initial reaction will be to detect and =
block MPTCP sessions as an evasion technique.  This is because the =
pattern of sub-flow creation can be detected, and this does not require =
modification of the inspection engine designs.  Enlightened firms may =
try to modify their engine designs to accommodate MPTCP, if it can be =
done predictably and reliably.

Completely agree. Also, this could be viewed largely as an =
administrative/configuration policy. If an inspection engine does not =
support MPTCP and must inspect all data in a particular stream that =
could potentially get split over multiple TCP connections, then the =
engine must strip MPTCP options. This allows MPTCP to seamlessly fall =
back to TCP. Yes the benefits of MPTCP are lost, but certainly noone =
wants to see MPTCP used as an evasion technique.

Going forward, deep packet inspection engine designs must accommodate =
MPTCP so as to enable the e2e benefits of MPTCP. There are potentially =
several uses of MPTCP and it would be nice to not have them undermined =
by equally critical middlebox functionality.=20

So as to allow MPTCP to work with middleboxes that do SSL termination, =
these middleboxes must also support MPTCP.

Cheers,
Anumita

On Sep 10, 2013, at 1:48 AM, Edward Lopez <elopez@fortinet.com> wrote:

> This problem exists on either the client or server side, and is based =
on the fact that content inspection engines deal with traffic from a =
session-based paradigm.  Since an MPTCP session is really an aggregate =
of TCP sessions (sub-flows), the inspection engine is not seeing the =
content in the correct context, and is likely to increase its =
false-negative rate.
>=20
> If the inspection engine is a transparent-proxy (such as used in =
anti-malware and web-filtering), it is buffering and reassembling =
traffic within its supported protocol types, then looking at the =
reassembled traffic in context.  But if the content is split over =
multiple TCP sessions, the proper content reassembly does not take =
place. =20
>=20
> If the inspection engine is a flow-based engine (such as used in =
intrusion prevention and application control), since the traffic is =
streaming across separate sessions, the signature (and likely =
pre-cursor) engines can fail to detect.  Flow-based engines have a =
better likelihood of detection if the patterns are small, and thus =
within the bounds of a single packet.  But the actions taken will impact =
only the sub-flow the pattern was detected on.
>=20
> The impact on the client or server depends on the actions configured =
to be taken by the middlebox.  For example, a strict web-filter may =
block all sub-flows if it cannot properly detect a URL via reassembly =
within a transparent proxy.
>=20
> By the way, topology is irrelevant.   Consider the following:
>=20
>=20
> Host A =3D=3D=3D=3D=3D Switch ----- Middlebox A ----- Internet ----- =
Middlebox B ----- Switch =3D=3D=3D=3D=3D Host B
>=20
> Even though all traffic is completely routed through both middleboxes, =
the problem remains.  As I've noted, this is a consequence of the =
session-based bias of the inspection engine designs.  There will still =
be up to four subflows (A.1>B.1, A.1>B.2, A.2>B.1, A.2>B.2)
>=20
> Have there been other multi-session based evasion attempts ... sure.  =
Many botnets make use of multiple sessions.  However, their pattern of =
session creation can be detected and blocked.  This is the problem that =
we face here.  I predict that the initial reaction will be to detect and =
block MPTCP sessions as an evasion technique.  This is because the =
pattern of sub-flow creation can be detected, and this does not require =
modification of the inspection engine designs.  Enlightened firms may =
try to modify their engine designs to accommodate MPTCP, if it can be =
done predictably and reliably.
>=20
> I hope this helps your understanding
>=20
> Ed Lopez
>=20
> Sent from my iPad
>=20
> On Sep 8, 2013, at 6:07 PM, "Yoshifumi Nishida" =
<nishida@sfc.wide.ad.jp> wrote:
>=20
>> Hi Edward,
>>=20
>> I'm trying to understand evasion scenarios since you have raised =
interesting points.
>> In my understanding, it will be something like this.=20
>>=20
>> case 1: There're two networks (say ISP1, ISP2) at the server side.=20
>>             ISP1 enforces IPS, but ISP2 doesn't.=20
>>             In this case, MPTCP can establish initial subflow through =
ISP1, but all contents can go through other subflows through ISP2. So, =
the traffic of this connection can evade IPS at ISP1
>>=20
>> case 2: There're two networks (say ISP1, ISP2) at the server side.=20
>>            Both ISP1, ISP2 enforce IPS,=20
>>            In this case, MPTCP can split the contents into small =
chunks and distributes them through multiple subflows.
>>            So, IPSs cannot perform inspection properly.
>>=20
>> case 3: similar to case2, but use only one ISP.
>>=20
>> Are those closed to what you mentioned? Or, am I thinking about =
totally different things?
>> Please correct me if I miss something.
>>=20
>> Thanks,
>> --
>> Yoshifumi
>>=20
>>=20
>> On Thu, Sep 5, 2013 at 10:24 AM, Edward Lopez <elopez@fortinet.com> =
wrote:
>> > Phil,
>> >
>> > I'm aware that I am relatively new to the WG and IETF as a whole =
(IETF 87
>> > Berlin was my first meeting).  But I do have a long history of =
security and
>> > networking protocols, currently working and having worked for a =
number of
>> > security appliance (middlebox) vendors.
>> >
>> > My initial review of MPTCP is that I would have to consider it an =
evasion
>> > technique from a content inspection standpoint.  Generally, content
>> > inspection engines are designed to operate as either flow-based or
>> > transparent-proxy.  A flow-based engine is generally used by IPS =
systems,
>> > but has now expanded to support many types of content inspection, =
most
>> > notably application control functionality of next-generation =
firewalls
>> > (NGFWs).  The limitation of a flow-based engine is that it looks at =
data in
>> > as a stream, generally without reordering and limited data =
reassembly.   A
>> > transparent proxy engine fully buffers and reassembles the data in =
the
>> > context of specific protocols, then inspects this traffic in =
context.
>> > Transparent proxies are useful when the inspection device has to =
interact
>> > within the protocol, such as in web-filtering solutions where a =
block
>> > message is sent back to an offending user.  However, both of these =
content
>> > inspection engine types have a general model centered around the =
session
>> > paradigm.  an MPTCP session is in effect an aggregate of multiple =
TCP
>> > sessions (sub flows), so in effect has characteristics of a =
protocol-based
>> > application, similar to FTP, VoIP, etc.
>> >
>> > The effect of MPTCP on content inspection engines is that it can be =
used as
>> > an evasion technique.  For example, I could envision the use of =
multi-homed
>> > MPTCP-based proxy engines out on the Internet, such that MPTCP =
based hosts
>> > in net repressive countries could evade state-imposed web-filters, =
or school
>> > kids could evade their school system's web-filters, etc.  The =
initial
>> > reaction from content inspectors would be do develop capabilities =
to detect
>> > MPTCP (likely based on options usage), and to either block or force =
fallback
>> > to standard TCP.  A significant concern is that this is where the =
incentive
>> > ends.  MPTCP is an evasion method, so mitigate the vulnerability.
>> >
>> > I would prefer to consider how to support MPTCP, perhaps in the =
form of an
>> > application-layer gateway and/or modification of content-inspection =
engines
>> > to deal with aggregation of sub-flows for inspection.  This line of =
thought
>> > lends itself to a philosophical discussion, as to if we intend =
MPTCP to be
>> > used to evade content inspection, or if we are looking to improve =
the
>> > performance of TCP-based applications.  I mention this because it =
would be
>> > desirable for the protocol to assist, or at least not hinder, the =
ability to
>> > identify the multiple sub-flows that create an MPTCP session.
>> >
>> > Eventually, I see the rise of middleboxes as MPTCP proxies, whether =
they are
>> > TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the =
methodologies of
>> > SSL inspection today.  I am interested in these use-cases because =
without
>> > them, the default will be to block/fallback, which ultimately isn't =
useful
>> > relative to MPTCP.
>> >
>> > My US $.02
>> > Ed Lopez
>> >
>> > On Sep 4, 2013, at 3:31 AM, philip.eardley@bt.com wrote:
>> >
>> > Just to let you know. The Security Ads are kindly finding us a =
security
>> > advisor, but no luck yet. So we may have to delay this slightly.
>> > Also, it would be good if there was some discussion on the mailing =
list
>> > before the call.
>> > =20
>> > phil
>> > =20
>> > From: Eardley,PL,Philip,TUB8 R
>> > Sent: 21 August 2013 08:36
>> > To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
>> > Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on =
security, late
>> > September
>> > =20
>> > Just a reminder, as I know a lot of people have been on holiday, =
please fill
>> > in the doodle
>> > =20
>> > Thanks
>> > phil
>> > =20
>> > From: multipathtcp-bounces@ietf.org =
[mailto:multipathtcp-bounces@ietf.org]
>> > On Behalf Of philip.eardley@bt.com
>> > Sent: 06 August 2013 13:49
>> > To: multipathtcp@ietf.org
>> > Subject: [multipathtcp] MPTCP interim (audio) meeting on security, =
late
>> > September
>> > =20
>> > We think it would a good idea to have an interim (audio) meeting, =
in order
>> > to make progress on advancing RFC 6824 on the standards track.
>> > =20
>> > We will discuss the security of the MPTCP protocol. The aim is to =
reach
>> > consensus on what security improvements are needed - and what are =
not needed
>> > - in order to progress MPTCP on the Standards track. We hope to =
cover both
>> > the threat(s) that we will handle and, at a high-level, the =
solutions that
>> > will be defined.
>> > =20
>> > Please fill in the doodle at =
http://doodle.com/xdf8eaiavvna9bcy#table
>> > =20
>> > For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout =
if the
>> > time is no good for you.
>> > =20
>> > In the meantime, please keep discussing MPTCP=92s security on the =
list!
>> > =20
>> > Thanks,
>> > Best wishes
>> > Phil & Yoshifumi
>> > _______________________________________________
>> > multipathtcp mailing list
>> > multipathtcp@ietf.org
>> > https://www.ietf.org/mailman/listinfo/multipathtcp
>> >
>> >
>> >
>> > ________________________________
>> > *** Please note that this message and any attachments may contain
>> > confidential and proprietary material and information and are =
intended only
>> > for the use of the intended recipient(s). If you are not the =
intended
>> > recipient, you are hereby notified that any review, use, =
disclosure,
>> > dissemination, distribution or copying of this message and any =
attachments
>> > is strictly prohibited. If you have received this email in error, =
please
>> > immediately notify the sender and destroy this e-mail and any =
attachments
>> > and all copies, whether electronic or printed. Please also note =
that any
>> > views, opinions, conclusions or commitments expressed in this =
message are
>> > those of the individual sender and do not necessarily reflect the =
views of
>> > Fortinet, Inc., its affiliates, and emails are not binding on =
Fortinet and
>> > only a writing manually signed by Fortinet's General Counsel can be =
a
>> > binding commitment of Fortinet to Fortinet's customers or partners. =
Thank
>> > you. ***
>> > ________________________________
>> >
>> > _______________________________________________
>> > multipathtcp mailing list
>> > multipathtcp@ietf.org
>> > https://www.ietf.org/mailman/listinfo/multipathtcp
>> >
>=20
> *** Please note that this message and any attachments may contain =
confidential and proprietary material and information and are intended =
only for the use of the intended recipient(s). If you are not the =
intended recipient, you are hereby notified that any review, use, =
disclosure, dissemination, distribution or copying of this message and =
any attachments is strictly prohibited. If you have received this email =
in error, please immediately notify the sender and destroy this e-mail =
and any attachments and all copies, whether electronic or printed. =
Please also note that any views, opinions, conclusions or commitments =
expressed in this message are those of the individual sender and do not =
necessarily reflect the views of Fortinet, Inc., its affiliates, and =
emails are not binding on Fortinet and only a writing manually signed by =
Fortinet's General Counsel can be a binding commitment of Fortinet to =
Fortinet's customers or partners. Thank you. ***=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


--Boundary_(ID_vsj7eP6m/MnVoE3Orlo8/Q)
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Hi,<div><br></div><div>Just want to share my 2c on =
this:</div><div><br></div><div><blockquote type=3D"cite"><div =
dir=3D"auto">Have there been other multi-session based evasion attempts =
... sure. &nbsp;Many botnets make use of multiple sessions. =
&nbsp;However, their pattern of session creation can be detected and =
blocked. &nbsp;This is the problem that we face here. &nbsp;I predict =
that the initial reaction will be to detect and block MPTCP sessions as =
an evasion technique. &nbsp;This is because the pattern of sub-flow =
creation can be detected, and this does not require modification of the =
inspection engine designs. &nbsp;Enlightened firms may try to modify =
their engine designs to accommodate MPTCP, if it can be done predictably =
and reliably.</div></blockquote><div><div =
dir=3D"auto"><br></div></div><div dir=3D"auto">Completely agree. Also, =
this could be viewed largely as an administrative/configuration policy. =
If an inspection engine does not support MPTCP and must inspect all data =
in a particular stream that could potentially get split over multiple =
TCP connections, then the engine must strip MPTCP options. This allows =
MPTCP to seamlessly fall back to TCP. Yes the benefits of MPTCP are =
lost, but certainly noone wants to see MPTCP used as an evasion =
technique.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Going =
forward, deep packet inspection engine designs must accommodate MPTCP so =
as to enable the e2e benefits of MPTCP. There are potentially several =
uses of MPTCP and it would be nice to not have them undermined by =
equally critical middlebox functionality.&nbsp;</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">So as to allow MPTCP to work =
with middleboxes that do SSL termination, these middleboxes must also =
support MPTCP.</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">Cheers,</div><div dir=3D"auto">Anumita</div><div =
dir=3D"auto"><br></div><div><div>On Sep 10, 2013, at 1:48 AM, Edward =
Lopez &lt;<a =
href=3D"mailto:elopez@fortinet.com">elopez@fortinet.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252">

<div dir=3D"auto">
<div>This problem exists on either the client or server side, and is =
based on the fact that content inspection engines deal with traffic from =
a session-based paradigm. &nbsp;Since an MPTCP session is really an =
aggregate of TCP sessions (sub-flows), the inspection
 engine is not seeing the content in the correct context, and is likely =
to increase its false-negative rate.</div>
<div><br>
</div>
<div>If the inspection engine is a transparent-proxy (such as used in =
anti-malware and web-filtering), it is buffering and reassembling =
traffic within its supported protocol types, then looking at the =
reassembled traffic in context. &nbsp;But if the content is split
 over multiple TCP sessions, the proper content reassembly does not take =
place. &nbsp;</div>
<div><br>
</div>
<div>If the inspection engine is a flow-based engine (such as used in =
intrusion prevention and application control), since the traffic is =
streaming across separate sessions, the signature (and likely =
pre-cursor) engines can fail to detect. &nbsp;Flow-based engines
 have a better likelihood of detection if the patterns are small, and =
thus within the bounds of a single packet. &nbsp;But the actions taken =
will impact only the sub-flow the pattern was detected on.</div>
<div><br>
</div>
<div>The impact on the client or server depends on the actions =
configured to be taken by the middlebox. &nbsp;For example, a strict =
web-filter may block all sub-flows if it cannot properly detect a URL =
via reassembly within a transparent proxy.</div>
<div><br>
</div>
<div>By the way, topology is irrelevant. &nbsp; Consider the =
following:</div>
<div><br>
</div>
<div><br>
</div>
<div>Host A =3D=3D=3D=3D=3D Switch ----- Middlebox A ----- Internet =
----- Middlebox B ----- Switch =3D=3D=3D=3D=3D Host B</div>
<div><br>
</div>
<div>Even though all traffic is completely routed through both =
middleboxes, the problem remains. &nbsp;As I've noted, this is a =
consequence of the session-based bias of the inspection engine designs. =
&nbsp;There will still be up to four subflows (A.1&gt;B.1, A.1&gt;B.2, =
A.2&gt;B.1,
 A.2&gt;B.2)</div>
<div><br>
</div>
<div>Have there been other multi-session based evasion attempts ... =
sure. &nbsp;Many botnets make use of multiple sessions. &nbsp;However, =
their pattern of session creation can be detected and blocked. =
&nbsp;This is the problem that we face here. &nbsp;I predict that the =
initial
 reaction will be to detect and block MPTCP sessions as an evasion =
technique. &nbsp;This is because the pattern of sub-flow creation can be =
detected, and this does not require modification of the inspection =
engine designs. &nbsp;Enlightened firms may try to modify their
 engine designs to accommodate MPTCP, if it can be done predictably and =
reliably.</div>
<div><br>
</div>
<div>I hope this helps your understanding</div>
<div><br>
</div>
<div>
<div>Ed Lopez</div>
<div><br>
</div>
Sent from my iPad</div>
<div><br>
On Sep 8, 2013, at 6:07 PM, "Yoshifumi Nishida" &lt;<a =
href=3D"mailto:nishida@sfc.wide.ad.jp">nishida@sfc.wide.ad.jp</a>&gt; =
wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">Hi Edward,<br>
<br>
I'm trying to understand evasion scenarios since you have raised =
interesting points.<br>
In my understanding, it will be something like this.&nbsp;
<div><br>
case 1: There're two networks (say ISP1, ISP2) at the server side. <br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ISP1 enforces IPS, but ISP2 =
doesn't. <br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; In this case, MPTCP can =
establish initial subflow through ISP1, but all contents can go through =
other subflows through ISP2. So, the traffic of this connection can =
evade IPS at ISP1<br>
<br>
case 2: There're two networks (say ISP1, ISP2) at the server side. <br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Both ISP1, ISP2 enforce =
IPS,&nbsp;<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;In this case, MPTCP can split =
the contents into small chunks and distributes them through multiple =
subflows.
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;So, IPSs cannot perform =
inspection properly.</div>
<div><br>
</div>
<div>case 3: similar to case2, but use only one ISP.<br>
<br>
Are those closed to what you mentioned? Or, am I thinking about totally =
different things?</div>
<div>Please correct me if I miss something.</div>
<div><br>
Thanks,<br>
--</div>
<div>Yoshifumi<br>
<br>
<br>
On Thu, Sep 5, 2013 at 10:24 AM, Edward Lopez &lt;<a =
href=3D"mailto:elopez@fortinet.com">elopez@fortinet.com</a>&gt; =
wrote:<br>
&gt; Phil,<br>
&gt;<br>
&gt; I'm aware that I am relatively new to the WG and IETF as a whole =
(IETF 87<br>
&gt; Berlin was my first meeting). &nbsp;But I do have a long history of =
security and<br>
&gt; networking protocols, currently working and having worked for a =
number of<br>
&gt; security appliance (middlebox) vendors.<br>
&gt;<br>
&gt; My initial review of MPTCP is that I would have to consider it an =
evasion<br>
&gt; technique from a content inspection standpoint. &nbsp;Generally, =
content<br>
&gt; inspection engines are designed to operate as either flow-based =
or<br>
&gt; transparent-proxy. &nbsp;A flow-based engine is generally used by =
IPS systems,<br>
&gt; but has now expanded to support many types of content inspection, =
most<br>
&gt; notably application control functionality of next-generation =
firewalls<br>
&gt; (NGFWs). &nbsp;The limitation of a flow-based engine is that it =
looks at data in<br>
&gt; as a stream, generally without reordering and limited data =
reassembly. &nbsp; A<br>
&gt; transparent proxy engine fully buffers and reassembles the data in =
the<br>
&gt; context of specific protocols, then inspects this traffic in =
context.<br>
&gt; Transparent proxies are useful when the inspection device has to =
interact<br>
&gt; within the protocol, such as in web-filtering solutions where a =
block<br>
&gt; message is sent back to an offending user. &nbsp;However, both of =
these content<br>
&gt; inspection engine types have a general model centered around the =
session<br>
&gt; paradigm. &nbsp;an MPTCP session is in effect an aggregate of =
multiple TCP<br>
&gt; sessions (sub flows), so in effect has characteristics of a =
protocol-based<br>
&gt; application, similar to FTP, VoIP, etc.<br>
&gt;<br>
&gt; The effect of MPTCP on content inspection engines is that it can be =
used as<br>
&gt; an evasion technique. &nbsp;For example, I could envision the use =
of multi-homed<br>
&gt; MPTCP-based proxy engines out on the Internet, such that MPTCP =
based hosts<br>
&gt; in net repressive countries could evade state-imposed web-filters, =
or school<br>
&gt; kids could evade their school system's web-filters, etc. &nbsp;The =
initial<br>
&gt; reaction from content inspectors would be do develop capabilities =
to detect<br>
&gt; MPTCP (likely based on options usage), and to either block or force =
fallback<br>
&gt; to standard TCP. &nbsp;A significant concern is that this is where =
the incentive<br>
&gt; ends. &nbsp;MPTCP is an evasion method, so mitigate the =
vulnerability.<br>
&gt;<br>
&gt; I would prefer to consider how to support MPTCP, perhaps in the =
form of an<br>
&gt; application-layer gateway and/or modification of content-inspection =
engines<br>
&gt; to deal with aggregation of sub-flows for inspection. &nbsp;This =
line of thought<br>
&gt; lends itself to a philosophical discussion, as to if we intend =
MPTCP to be<br>
&gt; used to evade content inspection, or if we are looking to improve =
the<br>
&gt; performance of TCP-based applications. &nbsp;I mention this because =
it would be<br>
&gt; desirable for the protocol to assist, or at least not hinder, the =
ability to<br>
&gt; identify the multiple sub-flows that create an MPTCP session.<br>
&gt;<br>
&gt; Eventually, I see the rise of middleboxes as MPTCP proxies, whether =
they are<br>
&gt; TCP-to-MPTCP or MPTCP-to-MPTCP, perhaps analogous with the =
methodologies of<br>
&gt; SSL inspection today. &nbsp;I am interested in these use-cases =
because without<br>
&gt; them, the default will be to block/fallback, which ultimately isn't =
useful<br>
&gt; relative to MPTCP.<br>
&gt;<br>
&gt; My US $.02<br>
&gt; Ed Lopez<br>
&gt;<br>
&gt; On Sep 4, 2013, at 3:31 AM, <a =
href=3D"mailto:philip.eardley@bt.com">philip.eardley@bt.com</a> =
wrote:<br>
&gt;<br>
&gt; Just to let you know. The Security Ads are kindly finding us a =
security<br>
&gt; advisor, but no luck yet. So we may have to delay this =
slightly.<br>
&gt; Also, it would be good if there was some discussion on the mailing =
list<br>
&gt; before the call.<br>
&gt; &nbsp;<br>
&gt; phil<br>
&gt; &nbsp;<br>
&gt; From: Eardley,PL,Philip,TUB8 R<br>
&gt; Sent: 21 August 2013 08:36<br>
&gt; To: Eardley,PL,Philip,TUB8 R; <a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>
&gt; Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on =
security, late<br>
&gt; September<br>
&gt; &nbsp;<br>
&gt; Just a reminder, as I know a lot of people have been on holiday, =
please fill<br>
&gt; in the doodle<br>
&gt; &nbsp;<br>
&gt; Thanks<br>
&gt; phil<br>
&gt; &nbsp;<br>
&gt; From: <a =
href=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-bounces@ietf.or=
g</a> [mailto:<a =
href=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-bounces@ietf.or=
g</a>]<br>
&gt; On Behalf Of <a =
href=3D"mailto:philip.eardley@bt.com">philip.eardley@bt.com</a><br>
&gt; Sent: 06 August 2013 13:49<br>
&gt; To: <a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>
&gt; Subject: [multipathtcp] MPTCP interim (audio) meeting on security, =
late<br>
&gt; September<br>
&gt; &nbsp;<br>
&gt; We think it would a good idea to have an interim (audio) meeting, =
in order<br>
&gt; to make progress on advancing RFC 6824 on the standards track.<br>
&gt; &nbsp;<br>
&gt; We will discuss the security of the MPTCP protocol. The aim is to =
reach<br>
&gt; consensus on what security improvements are needed - and what are =
not needed<br>
&gt; - in order to progress MPTCP on the Standards track. We hope to =
cover both<br>
&gt; the threat(s) that we will handle and, at a high-level, the =
solutions that<br>
&gt; will be defined.<br>
&gt; &nbsp;<br>
&gt; Please fill in the doodle at <a =
href=3D"http://doodle.com/xdf8eaiavvna9bcy#table">
http://doodle.com/xdf8eaiavvna9bcy#table</a><br>
&gt; &nbsp;<br>
&gt; For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout =
if the<br>
&gt; time is no good for you.<br>
&gt; &nbsp;<br>
&gt; In the meantime, please keep discussing MPTCP=92s security on the =
list!<br>
&gt; &nbsp;<br>
&gt; Thanks,<br>
&gt; Best wishes<br>
&gt; Phil &amp; Yoshifumi<br>
&gt; _______________________________________________<br>
&gt; multipathtcp mailing list<br>
&gt; <a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>
&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp">https://www.ie=
tf.org/mailman/listinfo/multipathtcp</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ________________________________<br>
&gt; *** Please note that this message and any attachments may =
contain<br>
&gt; confidential and proprietary material and information and are =
intended only<br>
&gt; for the use of the intended recipient(s). If you are not the =
intended<br>
&gt; recipient, you are hereby notified that any review, use, =
disclosure,<br>
&gt; dissemination, distribution or copying of this message and any =
attachments<br>
&gt; is strictly prohibited. If you have received this email in error, =
please<br>
&gt; immediately notify the sender and destroy this e-mail and any =
attachments<br>
&gt; and all copies, whether electronic or printed. Please also note =
that any<br>
&gt; views, opinions, conclusions or commitments expressed in this =
message are<br>
&gt; those of the individual sender and do not necessarily reflect the =
views of<br>
&gt; Fortinet, Inc., its affiliates, and emails are not binding on =
Fortinet and<br>
&gt; only a writing manually signed by Fortinet's General Counsel can be =
a<br>
&gt; binding commitment of Fortinet to Fortinet's customers or partners. =
Thank<br>
&gt; you. ***<br>
&gt; ________________________________<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; multipathtcp mailing list<br>
&gt; <a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>
&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp">https://www.ie=
tf.org/mailman/listinfo/multipathtcp</a><br>
&gt;<br>
</div>
</div>
</div>
</div>
</blockquote>

<font bgcolor=3D"#ffffff"><b><br><hr>
***  Please note that this message and any attachments may contain =
confidential
and proprietary material and information and are intended only for the =
use of
the intended recipient(s). If you are not the intended recipient, you =
are hereby
notified that any review, use, disclosure, dissemination, distribution =
or copying
of this message and any attachments is strictly prohibited. If you have =
received
this email in error, please immediately notify the sender and destroy =
this e-mail
and any attachments and all copies, whether electronic or printed.
Please also note that any views, opinions, conclusions or commitments =
expressed
in this message are those of the individual sender and do not =
necessarily reflect
the views of Fortinet, Inc., its affiliates, and emails are not binding =
on
Fortinet and only a writing manually signed by Fortinet's General =
Counsel can be
a binding commitment of Fortinet to Fortinet's customers or partners. =
Thank you. ***
<br><hr></b></font>
</div>


_______________________________________________<br>multipathtcp mailing =
list<br><a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>https:/=
/www.ietf.org/mailman/listinfo/multipathtcp<br></blockquote></div><br></di=
v></body></html>=

--Boundary_(ID_vsj7eP6m/MnVoE3Orlo8/Q)--

From philip.eardley@bt.com  Fri Sep 20 02:10:35 2013
Return-Path: <philip.eardley@bt.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 444F221F8EC3 for <multipathtcp@ietfa.amsl.com>; Fri, 20 Sep 2013 02:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.344
X-Spam-Level: 
X-Spam-Status: No, score=-102.344 tagged_above=-999 required=5 tests=[AWL=-1.346, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LY2c5fUJkhym for <multipathtcp@ietfa.amsl.com>; Fri, 20 Sep 2013 02:10:29 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.com [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 1B97721F8EB5 for <multipathtcp@ietf.org>; Fri, 20 Sep 2013 02:10:28 -0700 (PDT)
Received: from EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.298.1; Fri, 20 Sep 2013 10:10:26 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.2.113]) by EVMHT67-UKRD.domain1.systemhost.net ([10.36.3.104]) with mapi; Fri, 20 Sep 2013 10:10:26 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Date: Fri, 20 Sep 2013 10:10:25 +0100
Thread-Topic: MPTCP in iOS7
Thread-Index: Ac614T3XgrvVHzPNRwmfEahmZ38z2Q==
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9519008@EMV67-UKRD.domain1.systemhost.net>
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_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9519008EMV67UKRDdoma_"
MIME-Version: 1.0
Subject: [multipathtcp] MPTCP in iOS7
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 20 Sep 2013 09:10:35 -0000

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9519008EMV67UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,



It looks like Multipath TCP has been implemented in IOS7!

Great news!



http://www.networkworld.com/news/2013/091913-ios7-multipath-273995.html

phil

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9519008EMV67UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Arial","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span style=
=3D'font-family:"Times New Roman","serif"'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Times New Roman","serif"'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-fam=
ily:"Times New Roman","serif"'>It looks like Multipath TCP has been impleme=
nted in IOS7!<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'f=
ont-family:"Times New Roman","serif"'>Great news!<o:p></o:p></span></p><p c=
lass=3DMsoPlainText><span style=3D'font-family:"Times New Roman","serif"'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-fami=
ly:"Times New Roman","serif"'><a href=3D"http://www.networkworld.com/news/2=
013/091913-ios7-multipath-273995.html">http://www.networkworld.com/news/201=
3/091913-ios7-multipath-273995.html</a><o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif=
"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Times New Roman","serif"'>phil<o:p></o:p></span></p><=
/div></body></html>=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9519008EMV67UKRDdoma_--

From nishida@sfc.wide.ad.jp  Sun Sep 22 23:00:58 2013
Return-Path: <nishida@sfc.wide.ad.jp>
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 0142B21F9B8F for <multipathtcp@ietfa.amsl.com>; Sun, 22 Sep 2013 23:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.677
X-Spam-Level: 
X-Spam-Status: No, score=-100.677 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deK5O9vUgsHG for <multipathtcp@ietfa.amsl.com>; Sun, 22 Sep 2013 23:00:57 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id 36CD821F9B8A for <multipathtcp@ietf.org>; Sun, 22 Sep 2013 23:00:56 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 1455327809C for <multipathtcp@ietf.org>; Mon, 23 Sep 2013 15:00:51 +0900 (JST)
Received: by mail-lb0-f182.google.com with SMTP id c11so2433417lbj.27 for <multipathtcp@ietf.org>; Sun, 22 Sep 2013 23:00:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=B+rURpYnp9tUA68q7xp3UeBDnQyMevyJRY6XhRrYhoc=; b=LZ2s+C6fQjB/aFzocvO0VqSIS7IVdim/T3vGfOBKAXgSXRnon6nNUJjNd62Ezydq0D zxlOixpb1o9d1aBWjF+GMpKBg/GYSQprRUnSFI7sLkHy0vlFmU4/u610QP5V8kGw+Ufn Dx8ZyltO0rCFzPwENnnRPEQhdRt1S9iCwjpsbVTiOCz0X5i37fQxH/8Wan1hOxTzTZLh c1tn09kXTeWN5e0rRU3w1XezHipuOqdxRrxIiPa8XDowHLDqu2lpaaUIjn3K/XgErz5i KXmP92UraZLmecl2lp+M/WSeqwGtTsSzmrSaSK5SrZwKxiQVZ6gHqpd4Bz82MrWfRJBj sNiQ==
MIME-Version: 1.0
X-Received: by 10.112.29.147 with SMTP id k19mr18566171lbh.9.1379916049573; Sun, 22 Sep 2013 23:00:49 -0700 (PDT)
Received: by 10.114.230.231 with HTTP; Sun, 22 Sep 2013 23:00:49 -0700 (PDT)
Date: Sun, 22 Sep 2013 23:00:49 -0700
Message-ID: <CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary=001a1133aa86f46ba004e706bdf8
Subject: [multipathtcp] some comments on draft-khalili-mptcp-congestion-control-01
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Sep 2013 06:00:58 -0000

--001a1133aa86f46ba004e706bdf8
Content-Type: text/plain; charset=ISO-8859-1

Hello,
I've read draft-khalili-mptcp-congestion-control-01 with great interests
and have the following comments. Please let me know if I miss something.

1: It seems to me that how to determine collective_paths and max_w_paths
are a bit ambiguous. Since they are "paths", it seems that they are
expected to be more than 1.
However, I'm not very sure about the logic to choose them. For example, if
3 paths have
10MSS, 20MSS, 30MSS cwnd respectively, do we choose the 20MSS path as one
of max_w_paths? Or, how about 10MSS, 29MSS, 30MSS case?

2: Do we really need to set the ssthresh to 1 MSS when multiple paths are
used? RFC6356 doesn't have this kind of logic. I'm wondering why this is
required. Also, in case of single path, the draft requires to set the
ssthresh to 2 MSS, but I'm not very sure about the rationale behind this.

3: It looks that w_p and rtt_p in equation (1) are not defined.

Editorial comment:
Reference 7 is not cited in the draft.

Thanks,
--
Yoshifumi

--001a1133aa86f46ba004e706bdf8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div>I&#39;ve read draft-khalili-mptcp-congestion-co=
ntrol-01 with great interests and have the following comments. Please let m=
e know if I miss something.</div><div><div><br></div><div>1: It seems to me=
 that how to determine collective_paths and max_w_paths are a bit ambiguous=
. Since they are &quot;paths&quot;, it seems that they are expected to be m=
ore than 1.</div>
<div>However, I&#39;m not very sure about the logic to choose them. For exa=
mple, if 3 paths have</div><div>10MSS, 20MSS, 30MSS cwnd respectively, do w=
e choose the 20MSS path as one of max_w_paths? Or, how about 10MSS, 29MSS, =
30MSS case?</div>
<div><br></div><div>2: Do we really need to=A0<span style=3D"color:rgb(0,0,=
0);font-size:1em">set the ssthresh to 1 MSS when multiple paths are used? R=
FC6356 doesn&#39;t have this kind of logic. I&#39;m wondering why this is r=
equired. Also, in case of single path, the draft requires to set the ssthre=
sh to 2 MSS, but I&#39;m not very sure about the rationale behind this.</sp=
an></div>
<div><span style=3D"color:rgb(0,0,0);font-size:1em"><br></span></div><div><=
span style=3D"color:rgb(0,0,0);font-size:1em">3: It looks that w_p and rtt_=
p in equation (1) are not defined.</span></div><div><span style=3D"color:rg=
b(0,0,0);font-size:1em"><br>
</span></div><div><font color=3D"#000000">Editorial comment:</font></div><d=
iv><font color=3D"#000000">Reference 7 is not cited in the draft.</font></d=
iv><div><font color=3D"#000000"><br></font></div><div><font color=3D"#00000=
0">Thanks,</font></div>
<div><font color=3D"#000000">--</font></div><div><font color=3D"#000000">Yo=
shifumi</font></div></div></div>

--001a1133aa86f46ba004e706bdf8--

From Nicolas.Kuhn@isae.fr  Mon Sep 23 00:01:31 2013
Return-Path: <Nicolas.Kuhn@isae.fr>
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 5D7E821F9E94 for <multipathtcp@ietfa.amsl.com>; Mon, 23 Sep 2013 00:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.389
X-Spam-Level: 
X-Spam-Status: No, score=-0.389 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzaG6FaSO15R for <multipathtcp@ietfa.amsl.com>; Mon, 23 Sep 2013 00:01:23 -0700 (PDT)
Received: from smtpext.isae.fr (smtpext.isae.fr [193.54.120.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1340521F9A8D for <multipathtcp@ietf.org>; Mon, 23 Sep 2013 00:01:23 -0700 (PDT)
Received: from catalpa (unknown [10.4.1.11]) by smtpext.isae.fr (Postfix) with ESMTP id A44C722E4AA for <multipathtcp@ietf.org>; Mon, 23 Sep 2013 09:01:18 +0200 (CEST)
Received: from [10.33.1.141] (port-nguyentheson.isae.fr [10.33.1.141]) by catalpa (Postfix) with ESMTP id 78CA2B7D87 for <multipathtcp@ietf.org>; Mon, 23 Sep 2013 09:01:21 +0200 (CEST)
Message-ID: <523FE749.8070900@isae.fr>
Date: Mon, 23 Sep 2013 09:01:29 +0200
From: Nicolas Kuhn <nicolas.kuhn@isae.fr>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: multipathtcp@ietf.org
References: <CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com>
In-Reply-To: <CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030203070200020601000607"
Subject: Re: [multipathtcp] some comments on draft-khalili-mptcp-congestion-control-01
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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, 23 Sep 2013 07:01:31 -0000

This is a multi-part message in MIME format.
--------------030203070200020601000607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Hello,

Le 23/09/2013 08:00, Yoshifumi Nishida a écrit :
> Hello,
> I've read draft-khalili-mptcp-congestion-control-01 with great
> interests and have the following comments. Please let me know if I
> miss something.
>
> 1: It seems to me that how to determine collective_paths and
> max_w_paths are a bit ambiguous. Since they are "paths", it seems that
> they are expected to be more than 1.
> However, I'm not very sure about the logic to choose them. For
> example, if 3 paths have
> 10MSS, 20MSS, 30MSS cwnd respectively, do we choose the 20MSS path as
> one of max_w_paths? Or, how about 10MSS, 29MSS, 30MSS case?
>
More details can be found in [5], Section 4.1: Equations (3) and (4)
should be included in the draft.

> 2: Do we really need to set the ssthresh to 1 MSS when multiple paths
> are used? RFC6356 doesn't have this kind of logic. I'm wondering why
> this is required. Also, in case of single path, the draft requires to
> set the ssthresh to 2 MSS, but I'm not very sure about the rationale
> behind this.
>
This may be required to avoid the overuse of a congested path whereas
other paths are available. If there are many paths, there is no use in
spoiling media resources with ssthresh set to 2 MSS. I guess this
parameter is set to 1 MSS to properly only analyze the traffic around.

The authors may have more explanations than I do.

> 3: It looks that w_p and rtt_p in equation (1) are not defined.
>
It should be: SUM_{p \in paths}(w_p;rtt_p) - according to [5].

Regards,

Nicolas KUHN

> Editorial comment:
> Reference 7 is not cited in the draft.
>
> Thanks,
> --
> Yoshifumi
>
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


--------------030203070200020601000607
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hello, <br>
      <br>
      Le 23/09/2013 08:00, Yoshifumi Nishida a &eacute;crit&nbsp;:<br>
    </div>
    <blockquote
cite="mid:CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hello,
        <div>I've read draft-khalili-mptcp-congestion-control-01 with
          great interests and have the following comments. Please let me
          know if I miss something.</div>
        <div>
          <div><br>
          </div>
          <div>1: It seems to me that how to determine collective_paths
            and max_w_paths are a bit ambiguous. Since they are "paths",
            it seems that they are expected to be more than 1.</div>
          <div>However, I'm not very sure about the logic to choose
            them. For example, if 3 paths have</div>
          <div>10MSS, 20MSS, 30MSS cwnd respectively, do we choose the
            20MSS path as one of max_w_paths? Or, how about 10MSS,
            29MSS, 30MSS case?</div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote>
    More details can be found in [5], Section 4.1: Equations (3) and (4)
    should be included in the draft. <br>
    <br>
    <blockquote
cite="mid:CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>2: Do we really need to&nbsp;<span
              style="color:rgb(0,0,0);font-size:1em">set the ssthresh to
              1 MSS when multiple paths are used? RFC6356 doesn't have
              this kind of logic. I'm wondering why this is required.
              Also, in case of single path, the draft requires to set
              the ssthresh to 2 MSS, but I'm not very sure about the
              rationale behind this.</span></div>
          <div><span style="color:rgb(0,0,0);font-size:1em"><br>
            </span></div>
        </div>
      </div>
    </blockquote>
    This may be required to avoid the overuse of a congested path
    whereas other paths are available. If there are many paths, there is
    no use in spoiling media resources with ssthresh set to 2 MSS. I
    guess this parameter is set to 1 MSS to properly only analyze the
    traffic around. <br>
    <br>
    The authors may have more explanations than I do. <br>
    <br>
    <blockquote
cite="mid:CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><span style="color:rgb(0,0,0);font-size:1em">3: It looks
              that w_p and rtt_p in equation (1) are not defined.</span></div>
          <div><span style="color:rgb(0,0,0);font-size:1em"><br>
            </span></div>
        </div>
      </div>
    </blockquote>
    It should be: SUM_{p \in paths}(w_p;rtt_p) - according to [5]. <br>
    <br>
    Regards, <br>
    <br>
    Nicolas KUHN<br>
    <br>
    <blockquote
cite="mid:CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><span style="color:rgb(0,0,0);font-size:1em">
            </span></div>
          <div><font color="#000000">Editorial comment:</font></div>
          <div><font color="#000000">Reference 7 is not cited in the
              draft.</font></div>
          <div><font color="#000000"><br>
            </font></div>
          <div><font color="#000000">Thanks,</font></div>
          <div><font color="#000000">--</font></div>
          <div><font color="#000000">Yoshifumi</font></div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
multipathtcp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/multipathtcp">https://www.ietf.org/mailman/listinfo/multipathtcp</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030203070200020601000607--

From nishida@sfc.wide.ad.jp  Thu Sep 26 00:32:52 2013
Return-Path: <nishida@sfc.wide.ad.jp>
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 E7CF521F9926 for <multipathtcp@ietfa.amsl.com>; Thu, 26 Sep 2013 00:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.544
X-Spam-Level: 
X-Spam-Status: No, score=-101.544 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1GleB26MZuA for <multipathtcp@ietfa.amsl.com>; Thu, 26 Sep 2013 00:32:52 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (ns.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:143]) by ietfa.amsl.com (Postfix) with ESMTP id B2F1A21F99B0 for <multipathtcp@ietf.org>; Thu, 26 Sep 2013 00:32:50 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 9AC692780BF for <multipathtcp@ietf.org>; Thu, 26 Sep 2013 16:32:45 +0900 (JST)
Received: by mail-la0-f53.google.com with SMTP id el20so613653lab.12 for <multipathtcp@ietf.org>; Thu, 26 Sep 2013 00:32:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lBca8tizz6k9B8YDPNKJZucchn+HDVFVKbhccnCvXac=; b=aK/QVM2GJRW2iZvQ9mqi+gxf9bG23dx1GWdARrWT0u3H2k7WO74gRjcB19deluCCl/ K5O0lpXNL3L3NblRC+A9/APQB5JkWDy1UPJ1k8TAm0xeSncT6Z7HEdxtp8iqkKFcxvJL Wpzv5nQCW7gS+RFEi+cKIWRG3IFY5T3LQyoaJUfakXzdwrsQHIi1Xeh/byOvD/YyKvYe /+P6xkZrqtgDGh+bTNlzd2BEoXpUtZUMiCcoy5h27dF5blj/vo2QYXgAl1dTHUOUf0O9 9rgOgoxeSEsCDqjK6N+1yJ+iezDGOm+D1xz7ELri7Hbk9Li6jF+I3P34L/19AH++fJrO Hqyg==
MIME-Version: 1.0
X-Received: by 10.112.50.109 with SMTP id b13mr79067lbo.47.1380180762793; Thu, 26 Sep 2013 00:32:42 -0700 (PDT)
Received: by 10.114.230.231 with HTTP; Thu, 26 Sep 2013 00:32:42 -0700 (PDT)
In-Reply-To: <523FE749.8070900@isae.fr>
References: <CAO249yfJ5FGNCzhsPV3V19BqOo2PGsedDRMu_imTKVh7o0a6ow@mail.gmail.com> <523FE749.8070900@isae.fr>
Date: Thu, 26 Sep 2013 00:32:42 -0700
Message-ID: <CAO249yeAtMUgJbBrs6a__MbJkawXBMznCFTLtRwjOWawNnJfwg@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Nicolas Kuhn <nicolas.kuhn@isae.fr>
Content-Type: multipart/alternative; boundary=001a11336ce2179cf904e74460a8
Cc: multipathtcp <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] some comments on draft-khalili-mptcp-congestion-control-01
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Sep 2013 07:32:53 -0000

--001a11336ce2179cf904e74460a8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Nicolas,

Thanks for the response.

On Mon, Sep 23, 2013 at 12:01 AM, Nicolas Kuhn <nicolas.kuhn@isae.fr> wrote=
:

>  Hello,
>
> Le 23/09/2013 08:00, Yoshifumi Nishida a =E9crit :
>
> Hello,
> I've read draft-khalili-mptcp-congestion-control-01 with great interests
> and have the following comments. Please let me know if I miss something.
>
>  1: It seems to me that how to determine collective_paths and max_w_paths
> are a bit ambiguous. Since they are "paths", it seems that they are
> expected to be more than 1.
> However, I'm not very sure about the logic to choose them. For example, i=
f
> 3 paths have
> 10MSS, 20MSS, 30MSS cwnd respectively, do we choose the 20MSS path as one
> of max_w_paths? Or, how about 10MSS, 29MSS, 30MSS case?
>
>   More details can be found in [5], Section 4.1: Equations (3) and (4)
> should be included in the draft.
>

OK. Thanks for the info.


>   2: Do we really need to set the ssthresh to 1 MSS when multiple paths
> are used? RFC6356 doesn't have this kind of logic. I'm wondering why this
> is required. Also, in case of single path, the draft requires to set the
> ssthresh to 2 MSS, but I'm not very sure about the rationale behind this.
>
>   This may be required to avoid the overuse of a congested path whereas
> other paths are available. If there are many paths, there is no use in
> spoiling media resources with ssthresh set to 2 MSS. I guess this paramet=
er
> is set to 1 MSS to properly only analyze the traffic around.
>
> The authors may have more explanations than I do.
>

I personally think setting small ssthresh is not very necessarily,
especially for single path case.
If this is an important point for the logic, I would like to see some
rationale in the draft.
I hope authors will address this in new version.

Thanks,
--
Yoshifumi

--001a11336ce2179cf904e74460a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Nicolas,=A0<div><br></div><div>Thanks for the response.=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Sep 23, 2=
013 at 12:01 AM, Nicolas Kuhn <span dir=3D"ltr">&lt;<a href=3D"mailto:nicol=
as.kuhn@isae.fr" target=3D"_blank">nicolas.kuhn@isae.fr</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>Hello, <br>
      <br>
      Le 23/09/2013 08:00, Yoshifumi Nishida a =E9crit=A0:<br>
    </div><div class=3D"im">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hello,
        <div>I&#39;ve read draft-khalili-mptcp-congestion-control-01 with
          great interests and have the following comments. Please let me
          know if I miss something.</div>
        <div>
          <div><br>
          </div>
          <div>1: It seems to me that how to determine collective_paths
            and max_w_paths are a bit ambiguous. Since they are &quot;paths=
&quot;,
            it seems that they are expected to be more than 1.</div>
          <div>However, I&#39;m not very sure about the logic to choose
            them. For example, if 3 paths have</div>
          <div>10MSS, 20MSS, 30MSS cwnd respectively, do we choose the
            20MSS path as one of max_w_paths? Or, how about 10MSS,
            29MSS, 30MSS case?</div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote></div>
    More details can be found in [5], Section 4.1: Equations (3) and (4)
    should be included in the draft.=A0</div></blockquote><div><br></div><d=
iv>OK. Thanks for the info. =A0</div><div>=A0<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <div>2: Do we really need to=A0<span style=3D"font-size:1em">set =
the ssthresh to
              1 MSS when multiple paths are used? RFC6356 doesn&#39;t have
              this kind of logic. I&#39;m wondering why this is required.
              Also, in case of single path, the draft requires to set
              the ssthresh to 2 MSS, but I&#39;m not very sure about the
              rationale behind this.</span></div>
          <div><span style=3D"font-size:1em"><br>
            </span></div>
        </div>
      </div>
    </blockquote></div>
    This may be required to avoid the overuse of a congested path
    whereas other paths are available. If there are many paths, there is
    no use in spoiling media resources with ssthresh set to 2 MSS. I
    guess this parameter is set to 1 MSS to properly only analyze the
    traffic around. <br>
    <br>
    The authors may have more explanations than I do.=A0</div></blockquote>=
<div><br></div><div>I personally think setting small ssthresh is not very n=
ecessarily, especially for single path case.=A0</div><div>If this is an imp=
ortant point for the logic, I would like to see some rationale in the draft=
.</div>
<div>I hope authors will address this in new version.</div><div><br></div><=
div>Thanks,</div><div>--</div><div>Yoshifumi =A0</div></div></div></div></d=
iv>

--001a11336ce2179cf904e74460a8--

From philip.eardley@bt.com  Fri Sep 27 03:56:56 2013
Return-Path: <philip.eardley@bt.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 6CC2011E814B for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 03:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.242
X-Spam-Level: 
X-Spam-Status: No, score=-103.242 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKWiK3arXmom for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 03:56:51 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.com [62.239.224.236]) by ietfa.amsl.com (Postfix) with ESMTP id 42C0A11E8147 for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 03:56:48 -0700 (PDT)
Received: from EVMHT68-UKRD.domain1.systemhost.net (10.36.3.105) by RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP Server (TLS) id 8.3.298.1; Fri, 27 Sep 2013 11:56:47 +0100
Received: from EMV67-UKRD.domain1.systemhost.net ([169.254.1.51]) by EVMHT68-UKRD.domain1.systemhost.net ([10.36.3.105]) with mapi; Fri, 27 Sep 2013 11:56:46 +0100
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>
Date: Fri, 27 Sep 2013 11:56:45 +0100
Thread-Topic: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting	on security
Thread-Index: Ac6tedRNJt/x3vsES6GmoIc+T+tuLQN83BSA
Message-ID: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171@EMV67-UKRD.domain1.systemhost.net>
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net>
In-Reply-To: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net>
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_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171EMV67UKRDdoma_"
MIME-Version: 1.0
Subject: Re: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting	on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 10:56:56 -0000

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171EMV67UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Chatting with a couple of people and thinking about the way forward.

Marcelo has suggested a 2-pronged approach:-

Prong 1: how to improve RFC6824 to solve the ADD_ADDR attack. The aim is to=
 get security equivalent to RFC5061 (SCTP with dynamic addresses). We can a=
lso improve RFC6824 to make some of the fallback cases clearer (I remember =
that came out of the implementation survey). We could hope to do this quite=
 quickly as a relatively small improvement to 6824, since there was some di=
scussion on the list a while back how to solve this.

Prong 2: RFC6824 sends the key in the clear on the MP_CAPABLE exchange - Wh=
at could we do better?  We've had some possibilities mentioned in the past,=
 but I don't think there's any consensus yet.

Personally I think this seems a good way forward. We could do Prong 1 quick=
ly if it looks like Prong 2 will take some time

Comments on this approach welcome.
Also if anyone would like a timeslot in the interim meeting, please let us =
know

Reading
http://tools.ietf.org/html/draft-bagnulo-mptcp-attacks-00

thanks


From: multipathtcp-bounces@ietf.org [mailto:multipathtcp-bounces@ietf.org] =
On Behalf Of philip.eardley@bt.com
Sent: 09 September 2013 17:32
To: multipathtcp@ietf.org
Subject: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting=
 on security

Let's fix the date of the interim meeting for Thursday 3rd October at 3pm G=
MT (note, the clocks change at different times in different regions of the =
world, this time is in GMT/UTC)

Will send audio details later

Thanks!
phil

From: Eardley,PL,Philip,TUB8 R
Sent: 06 September 2013 10:59
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: MPTCP interim (audio) meeting on security - please update your doo=
dle

I extended the doodle to the first week of October.
Please could you update your entry or fill in

Sorry for the trouble

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> [=
mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com<ma=
ilto:philip.eardley@bt.com>
Sent: 04 September 2013 08:31
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just to let you know. The Security Ads are kindly finding us a security adv=
isor, but no luck yet. So we may have to delay this slightly.
Also, it would be good if there was some discussion on the mailing list bef=
ore the call.

phil

From: Eardley,PL,Philip,TUB8 R
Sent: 21 August 2013 08:36
To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org<mailto:multipathtcp@iet=
f.org>
Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, late=
 September

Just a reminder, as I know a lot of people have been on holiday, please fil=
l in the doodle

Thanks
phil

From: multipathtcp-bounces@ietf.org<mailto:multipathtcp-bounces@ietf.org> [=
mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com<ma=
ilto:philip.eardley@bt.com>
Sent: 06 August 2013 13:49
To: multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
Subject: [multipathtcp] MPTCP interim (audio) meeting on security, late Sep=
tember

We think it would a good idea to have an interim (audio) meeting, in order =
to make progress on advancing RFC 6824 on the standards track.

We will discuss the security of the MPTCP protocol. The aim is to reach con=
sensus on what security improvements are needed - and what are not needed -=
 in order to progress MPTCP on the Standards track. We hope to cover both t=
he threat(s) that we will handle and, at a high-level, the solutions that w=
ill be defined.

Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table

For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if the t=
ime is no good for you.

In the meantime, please keep discussing MPTCP's security on the list!

Thanks,
Best wishes
Phil & Yoshifumi

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171EMV67UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Arial","sans-serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1305039746;
	mso-list-type:hybrid;
	mso-list-template-ids:2002161612 990930284 134807555 134807557 134807553 1=
34807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:1590;
	mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Chatting with =
a couple of people and thinking about the way forward.<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","=
sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>=
Marcelo has suggested a 2-pronged approach:-<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-seri=
f";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Prong 1: =
how to improve RFC6824 to solve the ADD_ADDR attack. The aim is to get secu=
rity equivalent to RFC5061 (SCTP with dynamic addresses). We can also impro=
ve RFC6824 to make some of the fallback cases clearer (I remember that came=
 out of the implementation survey). We could hope to do this quite quickly =
as a relatively small improvement to 6824, since there was some discussion =
on the list a while back how to solve this. <o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-seri=
f";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Prong 2: =
RFC6824 sends the key in the clear on the MP_CAPABLE exchange - What could =
we do better?&nbsp; We&#8217;ve had some possibilities mentioned in the pas=
t, but I don&#8217;t think there&#8217;s any consensus yet. <o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ar=
ial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:=
blue'>Personally I think this seems a good way forward. We could do Prong 1=
 quickly if it looks like Prong 2 will take some time <o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","=
sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>=
Comments on this approach welcome.<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:bl=
ue'>Also if anyone would like a timeslot in the interim meeting, please let=
 us know<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:12.0pt;font-family:"Arial","sans-serif";color:blue'>&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","=
sans-serif";color:blue'>Reading<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'=
><a href=3D"http://tools.ietf.org/html/draft-bagnulo-mptcp-attacks-00">http=
://tools.ietf.org/html/draft-bagnulo-mptcp-attacks-00</a><o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial=
","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blu=
e'>thanks<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ar=
ial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div style=3D'bor=
der:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0=
cm'><p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;fo=
nt-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b=
><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif";mso-fareast-language:EN-GB'> multipathtcp-bounces@ietf.org [mailto:mul=
tipathtcp-bounces@ietf.org] <b>On Behalf Of </b>philip.eardley@bt.com<br><b=
>Sent:</b> 09 September 2013 17:32<br><b>To:</b> multipathtcp@ietf.org<br><=
b>Subject:</b> [multipathtcp] Thursday 3rd October: MPTCP interim (audio) m=
eeting on security<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;fon=
t-family:"Arial","sans-serif";color:blue'>Let&#8217;s fix the date of the i=
nterim meeting for Thursday 3<sup>rd</sup> October at 3pm GMT (note, the cl=
ocks change at different times in different regions of the world, this time=
 is in GMT/UTC)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:12.0pt;font-family:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fami=
ly:"Arial","sans-serif";color:blue'>Will send audio details later<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-famil=
y:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";c=
olor:blue'>Thanks!<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>phil<o:p></o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fam=
ily:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div style=
=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><di=
v><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0c=
m 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</s=
pan></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";mso-fareast-language:EN-GB'> Eardley,PL,Philip,TUB8 R <br><b>Se=
nt:</b> 06 September 2013 10:59<br><b>To:</b> <a href=3D"mailto:multipathtc=
p@ietf.org">multipathtcp@ietf.org</a><br><b>Subject:</b> MPTCP interim (aud=
io) meeting on security - please update your doodle<o:p></o:p></span></p></=
div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>=
I extended the doodle to the first week of October.<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","san=
s-serif";color:blue'>Please could you update your entry or fill in<o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fami=
ly:"Arial","sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";=
color:blue'>Sorry for the trouble<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blu=
e'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Arial","sans-serif";color:blue'>Thanks<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Ar=
ial","sans-serif";color:blue'>phil<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:bl=
ue'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid=
 blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;borde=
r-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><=
b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-s=
erif";mso-fareast-language:EN-GB'>From:</span></b><span lang=3DEN-US style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language=
:EN-GB'> <a href=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-boun=
ces@ietf.org</a> [<a href=3D"mailto:multipathtcp-bounces@ietf.org">mailto:m=
ultipathtcp-bounces@ietf.org</a>] <b>On Behalf Of </b><a href=3D"mailto:phi=
lip.eardley@bt.com">philip.eardley@bt.com</a><br><b>Sent:</b> 04 September =
2013 08:31<br><b>To:</b> <a href=3D"mailto:multipathtcp@ietf.org">multipath=
tcp@ietf.org</a><br><b>Subject:</b> Re: [multipathtcp] MPTCP interim (audio=
) meeting on security, late September<o:p></o:p></span></p></div></div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'f=
ont-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>Just to let yo=
u know. The Security Ads are kindly finding us a security advisor, but no l=
uck yet. So we may have to delay this slightly.<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-se=
rif";color:blue'>Also, it would be good if there was some discussion on the=
 mailing list before the call.<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
2.0pt;font-family:"Arial","sans-serif";color:blue'>phil<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial",=
"sans-serif";color:blue'><o:p>&nbsp;</o:p></span></p><div style=3D'border:n=
one;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=
=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><=
p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-fa=
mily:"Tahoma","sans-serif";mso-fareast-language:EN-GB'>From:</span></b><spa=
n lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";=
mso-fareast-language:EN-GB'> Eardley,PL,Philip,TUB8 R <br><b>Sent:</b> 21 A=
ugust 2013 08:36<br><b>To:</b> Eardley,PL,Philip,TUB8 R; <a href=3D"mailto:=
multipathtcp@ietf.org">multipathtcp@ietf.org</a><br><b>Subject:</b> RE: [mu=
ltipathtcp] MPTCP interim (audio) meeting on security, late September<o:p><=
/o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-s=
erif";color:blue'>Just a reminder, as I know a lot of people have been on h=
oliday, please fill in the doodle <o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:bl=
ue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Arial","sans-serif";color:blue'>Thanks<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"A=
rial","sans-serif";color:blue'>phil<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:b=
lue'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:soli=
d blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;bord=
er-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal>=
<b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif";mso-fareast-language:EN-GB'>From:</span></b><span lang=3DEN-US style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language=
:EN-GB'> <a href=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-boun=
ces@ietf.org</a> [<a href=3D"mailto:multipathtcp-bounces@ietf.org">mailto:m=
ultipathtcp-bounces@ietf.org</a>] <b>On Behalf Of </b><a href=3D"mailto:phi=
lip.eardley@bt.com">philip.eardley@bt.com</a><br><b>Sent:</b> 06 August 201=
3 13:49<br><b>To:</b> <a href=3D"mailto:multipathtcp@ietf.org">multipathtcp=
@ietf.org</a><br><b>Subject:</b> [multipathtcp] MPTCP interim (audio) meeti=
ng on security, late September<o:p></o:p></span></p></div></div><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Arial","sans-serif"'>We think it would a good idea to=
 have an interim (audio) meeting, in order to make progress on advancing RF=
C 6824 on the standards track.<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-=
family:"Arial","sans-serif"'>We will discuss the security of the MPTCP prot=
ocol. The aim is to reach consensus on what security improvements are neede=
d - and what are not needed - in order to progress MPTCP on the Standards t=
rack. We hope to cover both the threat(s) that we will handle and, at a hig=
h-level, the solutions that will be defined.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-seri=
f"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Arial","sans-serif"'>Please fill in the doodle at <a=
 href=3D"http://doodle.com/xdf8eaiavvna9bcy#table">http://doodle.com/xdf8ea=
iavvna9bcy#table</a> <o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"A=
rial","sans-serif"'>For previous MPTCP WG interims, ~3pm GMT has been OK. P=
lease shout if the time is no good for you.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-seri=
f"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Arial","sans-serif"'>In the meantime, please keep di=
scussing MPTCP&#8217;s security on the list!<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sans-seri=
f"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Arial","sans-serif"'>Thanks, <o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Arial","sa=
ns-serif"'>Best wishes<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:12.0pt;font-family:"Arial","sans-serif"'>Phil &amp; Yoshifum=
i<o:p></o:p></span></p></div></div></div></div></div></div></body></html>=

--_000_A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171EMV67UKRDdoma_--

From anumita_biswas@apple.com  Fri Sep 27 10:20:59 2013
Return-Path: <anumita_biswas@apple.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 0C59F21F9D69 for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 10:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.954
X-Spam-Level: 
X-Spam-Status: No, score=-8.954 tagged_above=-999 required=5 tests=[AWL=1.044,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Seps5WO3ajNI for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 10:20:51 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id C6F1F21F9D0E for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 10:20:46 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_FyR9fsaVcEmxpaSIfbRAbA)"
Received: from relay7.apple.com ([17.128.113.101]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MTS00MN8O6M5XH1@mail-out.apple.com> for multipathtcp@ietf.org; Fri, 27 Sep 2013 10:20:46 -0700 (PDT)
X-AuditID: 11807165-b7f426d000003169-07-5245be6dcc87
Received: from panthera-tigris.apple.com (panthera-tigris.apple.com [17.193.13.99]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay7.apple.com (Apple SCV relay) with SMTP id E0.F4.12649.D6EB5425; Fri, 27 Sep 2013 10:20:46 -0700 (PDT)
From: Anumita Biswas <anumita_biswas@apple.com>
In-reply-to: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171@EMV67-UKRD.domain1.systemhost.net>
Date: Fri, 27 Sep 2013 10:22:41 -0700
Message-id: <6CE57EDE-92FE-457E-8237-DDBC3910A6BB@apple.com>
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171@EMV67-UKRD.domain1.systemhost.net>
To: philip.eardley@bt.com
X-Mailer: Apple Mail (2.1805)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDLMWRmVeSWpSXmKPExsUieJA3WTdvn2uQwVt3i8+rr7NZLFu7gtGB yaPty2QmjyVLfjIFMEVx2aSk5mSWpRbp2yVwZfzYe5ilYPpHxoqX564yNzDOu8TYxcjJISFg IvFlewszhC0mceHeerYuRi4OIYGFTBKP9mxmAUkwCyRIPP42kQnE5hXQk/h4bTlQMweHsEC0 xO1VBSBhNgF9iaOPboDN4QQK72r5AGazCKhKrF5ymBFijKTEir+fWCHG2Eg0PN7ADLFrJaPE 8iVzweaLgBRtX8UGcZCsxNnJE1knMPLNQnLGLCRnQMS1JZYtfM0MYRtIPO18xYopri/x5t0c pgWMbKsYBYpScxIrzfUSCwpyUvWS83M3MYLCtKEwdQdj43KrQ4wCHIxKPLwHZrgGCbEmlhVX 5h5ilOBgVhLhFV4AFOJNSaysSi3Kjy8qzUktPsQozcGiJM4bssclSEggPbEkNTs1tSC1CCbL xMEp1cC47ust6zSnXEnWic+qO3vXcKy/KZjcz/qy1PXh2hiv44+SOAWilrTGVl/6/OrNBIvD i77xbZDZG935kv97SMaM32u2b1/ZvVOe89l3OQOtYr1qr5JN865ppOw6NmNWxoKMz+eWxfV+ 2RMdo1WnL94Xla7CenDBAtVl9YVf69bYFrztbFv5zWSiEktxRqKhFnNRcSIAiBa/LE8CAAA=
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 17:20:59 -0000

--Boundary_(ID_FyR9fsaVcEmxpaSIfbRAbA)
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: quoted-printable

Hi Phil,

Prong 2 or the discussion of how to alter MP_JOINs so as to not be =
dependent on keys exchanged in the clear is a higher priority (compared =
to Prong 1) although it can take more time. Perhaps if we could start =
with the list of ideas on the table, that would be great ?=20

ADD_ADDR vulnerability is real, but since it is an optional part of the =
protocol it is not as important a threat as Prong 2 below. ADD_ADDR is =
also not as easily implementable in Internet environments as most peer =
to peer or client side end-points have to use out of band mechanisms to =
discover their public facing addresses to send out over ADD_ADDR. This =
limits the utility of ADD_ADDR to public facing servers or middleboxes =
on the Internet. For this limited set of public facing servers, ability =
to use ADD_ADDR allows connectivity to them be more robust, yet it is =
not as important an use case and if these middleboxes do not support =
ADD_ADDR until the vulnerability is solved, it is acceptable imo.

In data center type environments/ private environments, ADD_ADDR =
probably does not pose as real a threat and could be suitable in its =
current shape.=20

Thanks,
Anumita

On Sep 27, 2013, at 3:56 AM, philip.eardley@bt.com wrote:

> Chatting with a couple of people and thinking about the way forward.
> =20
> Marcelo has suggested a 2-pronged approach:-
> =20
> Prong 1: how to improve RFC6824 to solve the ADD_ADDR attack. The aim =
is to get security equivalent to RFC5061 (SCTP with dynamic addresses). =
We can also improve RFC6824 to make some of the fallback cases clearer =
(I remember that came out of the implementation survey). We could hope =
to do this quite quickly as a relatively small improvement to 6824, =
since there was some discussion on the list a while back how to solve =
this.
> =20
> Prong 2: RFC6824 sends the key in the clear on the MP_CAPABLE exchange =
- What could we do better?  We=92ve had some possibilities mentioned in =
the past, but I don=92t think there=92s any consensus yet.
> =20
> Personally I think this seems a good way forward. We could do Prong 1 =
quickly if it looks like Prong 2 will take some time
> =20
> Comments on this approach welcome.
> Also if anyone would like a timeslot in the interim meeting, please =
let us know
>                                                                        =
   =20
> Reading
> http://tools.ietf.org/html/draft-bagnulo-mptcp-attacks-00
> =20
> thanks
> =20
> =20
> From: multipathtcp-bounces@ietf.org =
[mailto:multipathtcp-bounces@ietf.org] On Behalf Of =
philip.eardley@bt.com
> Sent: 09 September 2013 17:32
> To: multipathtcp@ietf.org
> Subject: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) =
meeting on security
> =20
> Let=92s fix the date of the interim meeting for Thursday 3rd October =
at 3pm GMT (note, the clocks change at different times in different =
regions of the world, this time is in GMT/UTC)
> =20
> Will send audio details later
> =20
> Thanks!
> phil
> =20
> From: Eardley,PL,Philip,TUB8 R=20
> Sent: 06 September 2013 10:59
> To: multipathtcp@ietf.org
> Subject: MPTCP interim (audio) meeting on security - please update =
your doodle
> =20
> I extended the doodle to the first week of October.
> Please could you update your entry or fill in
> =20
> Sorry for the trouble
> =20
> Thanks
> phil
> =20
> From: multipathtcp-bounces@ietf.org =
[mailto:multipathtcp-bounces@ietf.org] On Behalf Of =
philip.eardley@bt.com
> Sent: 04 September 2013 08:31
> To: multipathtcp@ietf.org
> Subject: Re: [multipathtcp] MPTCP interim (audio) meeting on security, =
late September
> =20
> Just to let you know. The Security Ads are kindly finding us a =
security advisor, but no luck yet. So we may have to delay this =
slightly.
> Also, it would be good if there was some discussion on the mailing =
list before the call.
> =20
> phil
> =20
> From: Eardley,PL,Philip,TUB8 R=20
> Sent: 21 August 2013 08:36
> To: Eardley,PL,Philip,TUB8 R; multipathtcp@ietf.org
> Subject: RE: [multipathtcp] MPTCP interim (audio) meeting on security, =
late September
> =20
> Just a reminder, as I know a lot of people have been on holiday, =
please fill in the doodle
> =20
> Thanks
> phil
> =20
> From: multipathtcp-bounces@ietf.org =
[mailto:multipathtcp-bounces@ietf.org] On Behalf Of =
philip.eardley@bt.com
> Sent: 06 August 2013 13:49
> To: multipathtcp@ietf.org
> Subject: [multipathtcp] MPTCP interim (audio) meeting on security, =
late September
> =20
> We think it would a good idea to have an interim (audio) meeting, in =
order to make progress on advancing RFC 6824 on the standards track.
> =20
> We will discuss the security of the MPTCP protocol. The aim is to =
reach consensus on what security improvements are needed - and what are =
not needed - in order to progress MPTCP on the Standards track. We hope =
to cover both the threat(s) that we will handle and, at a high-level, =
the solutions that will be defined.
> =20
> Please fill in the doodle at http://doodle.com/xdf8eaiavvna9bcy#table
> =20
> For previous MPTCP WG interims, ~3pm GMT has been OK. Please shout if =
the time is no good for you.
> =20
> In the meantime, please keep discussing MPTCP=92s security on the =
list!
> =20
> Thanks,
> Best wishes
> Phil & Yoshifumi
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


--Boundary_(ID_FyR9fsaVcEmxpaSIfbRAbA)
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi =
Phil,<div><br></div><div>Prong 2 or the discussion of how to alter =
MP_JOINs so as to not be dependent on keys exchanged in the clear is a =
higher priority (compared to Prong 1) although it can take more time. =
Perhaps if we could start with the list of ideas on the table, that =
would be great ?&nbsp;</div><div><br></div><div>ADD_ADDR vulnerability =
is real, but since it is an optional part of the protocol it is not as =
important a threat as Prong 2 below. ADD_ADDR is also not as easily =
implementable in Internet environments as most peer to peer or client =
side end-points have to use out of band mechanisms to discover their =
public facing addresses to send out over ADD_ADDR. This limits the =
utility of ADD_ADDR to public facing servers or middleboxes on the =
Internet. For this limited set of public facing servers, ability to use =
ADD_ADDR allows connectivity to them be more robust, yet it is not as =
important an use case and if these middleboxes do not support ADD_ADDR =
until the vulnerability is solved, it is acceptable =
imo.</div><div><br></div><div>In data center type environments/ private =
environments, ADD_ADDR probably does not pose as real a threat and could =
be suitable in its current =
shape.&nbsp;</div><div><br></div><div>Thanks,</div><div>Anumita</div><div>=
<br><div><div>On Sep 27, 2013, at 3:56 AM, <a =
href=3D"mailto:philip.eardley@bt.com">philip.eardley@bt.com</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;"><div class=3D"WordSection1" =
style=3D"page: WordSection1;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Chatting with a couple of people and thinking about the way =
forward.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Marcelo has suggested a 2-pronged =
approach:-<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Prong 1: how to improve RFC6824 to solve the ADD_ADDR attack. The =
aim is to get security equivalent to RFC5061 (SCTP with dynamic =
addresses). We can also improve RFC6824 to make some of the fallback =
cases clearer (I remember that came out of the implementation survey). =
We could hope to do this quite quickly as a relatively small improvement =
to 6824, since there was some discussion on the list a while back how to =
solve this.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Prong 2: RFC6824 sends the key in the clear on the MP_CAPABLE =
exchange - What could we do better?&nbsp; We=92ve had some possibilities =
mentioned in the past, but I don=92t think there=92s any consensus =
yet.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Personally I think this seems a good way forward. We could do =
Prong 1 quickly if it looks like Prong 2 will take some =
time<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Comments on this approach welcome.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif; color: blue;">Also if anyone would like a timeslot in =
the interim meeting, please let us know<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif; color: =
blue;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Reading<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;"><a =
href=3D"http://tools.ietf.org/html/draft-bagnulo-mptcp-attacks-00" =
style=3D"color: purple; text-decoration: =
underline;">http://tools.ietf.org/html/draft-bagnulo-mptcp-attacks-00</a><=
o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">thanks<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"border-style: none none none =
solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0cm =
0cm 0cm 4pt;"><div><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;">From:</span></b><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp-bounces@ietf.org">multipathtcp-bounces@ietf.or=
g</a> [<a =
href=3D"mailto:multipathtcp-bounces@ietf.org">mailto:multipathtcp-bounces@=
ietf.org</a>]<span class=3D"Apple-converted-space">&nbsp;</span><b>On =
Behalf Of<span class=3D"Apple-converted-space">&nbsp;</span></b><a =
href=3D"mailto:philip.eardley@bt.com">philip.eardley@bt.com</a><br><b>Sent=
:</b><span class=3D"Apple-converted-space">&nbsp;</span>09 September =
2013 17:32<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>multipathtcp@ietf.org<br><b>S=
ubject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[multipathtcp] Thursday 3rd =
October: MPTCP interim (audio) meeting on =
security<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Let=92s fix the date of the interim meeting for Thursday =
3<sup>rd</sup><span class=3D"Apple-converted-space">&nbsp;</span>October =
at 3pm GMT (note, the clocks change at different times in different =
regions of the world, this time is in =
GMT/UTC)<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Will send audio details later<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif; color: blue;">&nbsp;</span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif; color: blue;">Thanks!<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif; color: blue;">phil<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif; color: blue;">&nbsp;</span></div><div =
style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt;"><div><div =
style=3D"border-style: solid none none; border-top-color: rgb(181, 196, =
223); border-top-width: 1pt; padding: 3pt 0cm 0cm;"><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;">From:</span></b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span>Eardley,PL,Philip,TUB8 =
R<span class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>06 September 2013 =
10:59<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">multipathtcp@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>MPTCP interim (audio) =
meeting on security - please update your =
doodle<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">I extended the doodle to the first week of =
October.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Please could you update your entry or fill =
in<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Sorry for the trouble<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif; color: blue;">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Thanks<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">phil<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"border-style: none none none =
solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0cm =
0cm 0cm 4pt;"><div><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;">From:</span></b><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;">multipathtcp-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[<a =
href=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">mailto:multipathtcp-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a =
href=3D"mailto:philip.eardley@bt.com" style=3D"color: purple; =
text-decoration: =
underline;">philip.eardley@bt.com</a><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>04 September 2013 =
08:31<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">multipathtcp@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [multipathtcp] MPTCP =
interim (audio) meeting on security, late =
September<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Just to let you know. The Security Ads are kindly finding us a =
security advisor, but no luck yet. So we may have to delay this =
slightly.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Also, it would be good if there was some discussion on the =
mailing list before the call.<o:p></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif; color: blue;">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">phil<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"border-style: none none none =
solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0cm =
0cm 0cm 4pt;"><div><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;">From:</span></b><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span>Eardley,PL,Philip,TUB8 =
R<span class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>21 August 2013 =
08:36<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Eardley,PL,Philip,TUB8 =
R;<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">multipathtcp@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>RE: [multipathtcp] MPTCP =
interim (audio) meeting on security, late =
September<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Just a reminder, as I know a lot of people have been on holiday, =
please fill in the doodle<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif; color: blue;">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">Thanks<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">phil<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif; color: =
blue;">&nbsp;</span></div><div style=3D"border-style: none none none =
solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0cm =
0cm 0cm 4pt;"><div><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0cm 0cm;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif;">From:</span></b><span lang=3D"EN-US" style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;">multipathtcp-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[<a =
href=3D"mailto:multipathtcp-bounces@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">mailto:multipathtcp-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b><a =
href=3D"mailto:philip.eardley@bt.com" style=3D"color: purple; =
text-decoration: =
underline;">philip.eardley@bt.com</a><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>06 August 2013 =
13:49<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:multipathtcp@ietf.org" style=3D"color: purple; =
text-decoration: =
underline;">multipathtcp@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[multipathtcp] MPTCP =
interim (audio) meeting on security, late =
September<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;">We think it =
would a good idea to have an interim (audio) meeting, in order to make =
progress on advancing RFC 6824 on the standards =
track.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;">We will =
discuss the security of the MPTCP protocol. The aim is to reach =
consensus on what security improvements are needed - and what are not =
needed - in order to progress MPTCP on the Standards track. We hope to =
cover both the threat(s) that we will handle and, at a high-level, the =
solutions that will be defined.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;">Please fill =
in the doodle at<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://doodle.com/xdf8eaiavvna9bcy#table" style=3D"color: =
purple; text-decoration: =
underline;">http://doodle.com/xdf8eaiavvna9bcy#table</a><o:p></o:p></span>=
</div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span style=3D"font-size: 12pt; =
font-family: Arial, sans-serif;">&nbsp;</span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;">For previous MPTCP WG interims, ~3pm GMT has been OK. =
Please shout if the time is no good for you.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 12pt; font-family: =
Arial, sans-serif;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;">In the =
meantime, please keep discussing MPTCP=92s security on the =
list!<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, =
sans-serif;">Thanks,<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;">Best =
wishes<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 12pt; font-family: Arial, sans-serif;">Phil &amp; =
Yoshifumi<o:p></o:p></span></div></div></div></div></div></div></div>_____=
__________________________________________<br>multipathtcp mailing =
list<br><a =
href=3D"mailto:multipathtcp@ietf.org">multipathtcp@ietf.org</a><br>https:/=
/www.ietf.org/mailman/listinfo/multipathtcp</div></blockquote></div><br></=
div></body></html>=

--Boundary_(ID_FyR9fsaVcEmxpaSIfbRAbA)--

From olivier.bonaventure@uclouvain.be  Fri Sep 27 12:35:13 2013
Return-Path: <olivier.bonaventure@uclouvain.be>
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 BCDC821F9F1B for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 12:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6O1Bg5ggUB4R for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 12:35:08 -0700 (PDT)
Received: from smtp6.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 061F521F9ED4 for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 12:35:06 -0700 (PDT)
Received: from mbpobo.local (unknown [172.17.0.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp6.sgsi.ucl.ac.be) by smtp6.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 7243618344E; Fri, 27 Sep 2013 21:34:56 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp6.sgsi.ucl.ac.be 7243618344E
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1380310496; bh=gey0G3HlLbaQaMr46nVqZ9klF5Uj6rfI1tcFAd0PORY=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Rwk/RPcvsIehk6sOru3UMOHtIv0TYK9BA/ZISGF5ptFRHdHql/n3xtNgrPsbc/tMv H+OTZwhkFNPSMdbX+U9EZucyBkXBJdKT1BoWvucxHF6HxcjzZl0Xa/CEC6nYpgVnyh T3Qettzkp3ZmgA+mCzhFxoNhKoQ3Pti293tqQ5TQ=
Message-ID: <5245DF07.7050600@uclouvain.be>
Date: Fri, 27 Sep 2013 21:39:51 +0200
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Anumita Biswas <anumita_biswas@apple.com>
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171@EMV67-UKRD.domain1.systemhost.net> <6CE57EDE-92FE-457E-8237-DDBC3910A6BB@apple.com>
In-Reply-To: <6CE57EDE-92FE-457E-8237-DDBC3910A6BB@apple.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-6.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: 7243618344E.AEA80
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 19:35:13 -0000

Anumita,
>
> Prong 2 or the discussion of how to alter MP_JOINs so as to not be
> dependent on keys exchanged in the clear is a higher priority (compared
> to Prong 1) although it can take more time. Perhaps if we could start
> with the list of ideas on the table, that would be great ?

The first issue that we need to take into account are the constraints on 
the three way handshake and the utilisation of crypto inside TCP.

The current design heavily depends on the assumption that we cannot 
perform strong crypto inside TCP and the constraint on the maximum 
length of the TCP option field (mainly during the three way handshake). 
Given these two constraints, it seems pretty difficult to provide a 
strong and secure mechanism in the TCP layer. We will always be blocked 
by the limited size of the TCP options. Exchanging public keys or 
certificates is impossible in TCP options.

A first possible approach is to allow MPTCP to reuse keys that are 
derived in a secure manner by the application. This solution could work 
with SSL/TLS and SSH for example. These application-layer protocols can 
derive secure keys after a Diffie-Hellman exchange. MPTCP could provide 
an API to receive such a key and use it to autheticate MP_JOINs.

This solution has been described in
http://tools.ietf.org/html/draft-paasch-mptcp-ssl-00
and there is a prototype implementation.

This draft sketches the solution and shows that it is feasible. However, 
there are two points that would need to be improved :
  - the algorithm to derive the MPTCP session should be proposed by 
security experts
  - MPTCP should use a key identifier and allow the application to 
change the MPTCP key (e.g. as a result of a change of the master keys by 
SSL/TLS)

With this solution, MPTCP cannot create additional subflows at the 
beginning of the MPTCP connection since it must wait until the security 
keys have been computed.

A second direction that has been discussed is the utilisation of hash 
chains. The client and the server could generate a hash chain for each 
MPTCP connection and use it to authenticate subsequent MP_JOINs. The 
hash chains could be included in the SYN and SYN+ACK segments if there 
is enough option space. The main advantage of hash chains is that they 
do not require strong crypto. However, a hash chain will be valid for N 
additional subflows. To create the N+1th subflow, the peers would need 
to exchange securely a new hash chain.

A third direction could be to build upon the tcpcrypt proposal and 
include it inside MPTCP. This requires strong crypto in the transport layer.

My impression is that trying to secure MPTCP without securing the data 
exchanged is a bit overkill and I would try to pursue the first 
direction in more details.



Olivier


From anumita_biswas@apple.com  Fri Sep 27 13:18:35 2013
Return-Path: <anumita_biswas@apple.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 BE11511E811D for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 13:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.476
X-Spam-Level: 
X-Spam-Status: No, score=-9.476 tagged_above=-999 required=5 tests=[AWL=0.523,  BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OjtdNuzfEwXS for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 13:18:30 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA7421F9FBF for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 13:18:29 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay2.apple.com ([17.128.113.67]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MTS00JNMWDOUM50@mail-out.apple.com> for multipathtcp@ietf.org; Fri, 27 Sep 2013 13:18:29 -0700 (PDT)
X-AuditID: 11807143-b7fce6d000001c8e-47-5245e8155a31
Received: from panthera-tigris.apple.com (panthera-tigris.apple.com [17.193.13.99]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay2.apple.com (Apple SCV relay) with SMTP id CB.8D.07310.518E5425; Fri, 27 Sep 2013 13:18:29 -0700 (PDT)
From: Anumita Biswas <anumita_biswas@apple.com>
In-reply-to: <5245DF07.7050600@uclouvain.be>
Date: Fri, 27 Sep 2013 13:20:30 -0700
Message-id: <A2950BFA-B914-4AD9-A333-C4C5BB2D2398@apple.com>
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171@EMV67-UKRD.domain1.systemhost.net> <6CE57EDE-92FE-457E-8237-DDBC3910A6BB@apple.com> <5245DF07.7050600@uclouvain.be>
To: Olivier.Bonaventure@uclouvain.be
X-Mailer: Apple Mail (2.1805)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUieJA3WVf0hWuQwYzn6hafV19ns7jR8IPF YtnaFYwOzB5tXyYzeSxZ8pPJ49Wx7ywBzFFcNimpOZllqUX6dglcGVN2zGIvaJSr+DXhNVMD Y7NEFyMnh4SAicSl9/PZIWwxiQv31rN1MXJxCAksZJJYvesbE0iCWUBHYufWO2wgNq+AnsTH a8sZuxg5OIQFoiVuryoACbMJ6EscfXSDGcTmBCo/ePkoWCuLgKrEtUeLWSDGGEl07ZoKNVJb YtnC18wgY3gFbCR+beeDWPuLUeLBw19gNSICKhKT+54zQ9wmK3F28kTWCYz8s5BcNAvJRbOQ jF3AyLyKUaAoNSex0kgvsaAgJ1UvOT93EyMoDBsKnXcwHltmdYhRgINRiYf3wAzXICHWxLLi ytxDjBIczEoivMILgEK8KYmVValF+fFFpTmpxYcYpTlYlMR5A/e4BAkJpCeWpGanphakFsFk mTg4pRoYA5LLBAtS3r+UkmLsPCPH5Fa8xVmDPeKp15vbbC9+zpvt6HpysYRU+I+EVGft/5dY c/iurOAwWRA89fflpEn5iowR814LRbfc+XBa+9LSK1mzvgpm8GscKpNI3zDFh7U09Hj3JUZ+ j6O8R45Z6xQcnuTOUtH53/qtwaOHgVM5Xs45e7t7/88NSizFGYmGWsxFxYkA2kXgdT8CAAA=
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 20:18:35 -0000

On Sep 27, 2013, at 12:39 PM, Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> wrote:

> Anumita,
>> 
>> Prong 2 or the discussion of how to alter MP_JOINs so as to not be
>> dependent on keys exchanged in the clear is a higher priority (compared
>> to Prong 1) although it can take more time. Perhaps if we could start
>> with the list of ideas on the table, that would be great ?
> 
> The first issue that we need to take into account are the constraints on the three way handshake and the utilisation of crypto inside TCP.
> 
> The current design heavily depends on the assumption that we cannot perform strong crypto inside TCP and the constraint on the maximum length of the TCP option field (mainly during the three way handshake). Given these two constraints, it seems pretty difficult to provide a strong and secure mechanism in the TCP layer. We will always be blocked by the limited size of the TCP options. Exchanging public keys or certificates is impossible in TCP options.
> 
> A first possible approach is to allow MPTCP to reuse keys that are derived in a secure manner by the application. This solution could work with SSL/TLS and SSH for example. These application-layer protocols can derive secure keys after a Diffie-Hellman exchange. MPTCP could provide an API to receive such a key and use it to autheticate MP_JOINs.
> 
> This solution has been described in
> http://tools.ietf.org/html/draft-paasch-mptcp-ssl-00
> and there is a prototype implementation.
> 
> This draft sketches the solution and shows that it is feasible. However, there are two points that would need to be improved :
> - the algorithm to derive the MPTCP session should be proposed by security experts
> - MPTCP should use a key identifier and allow the application to change the MPTCP key (e.g. as a result of a change of the master keys by SSL/TLS)
> 
> With this solution, MPTCP cannot create additional subflows at the beginning of the MPTCP connection since it must wait until the security keys have been computed.
> 
> A second direction that has been discussed is the utilisation of hash chains. The client and the server could generate a hash chain for each MPTCP connection and use it to authenticate subsequent MP_JOINs. The hash chains could be included in the SYN and SYN+ACK segments if there is enough option space. The main advantage of hash chains is that they do not require strong crypto. However, a hash chain will be valid for N additional subflows. To create the N+1th subflow, the peers would need to exchange securely a new hash chain.
> 
> A third direction could be to build upon the tcpcrypt proposal and include it inside MPTCP. This requires strong crypto in the transport layer.
> 
> My impression is that trying to secure MPTCP without securing the data exchanged is a bit overkill and I would try to pursue the first direction in more details.
I agree. Using SSL keys to improve the strength of the negotiation in Join is the preferred approach. Yes, security experts should look into the algorithm. I think trading off the delay added to initiating subflow joins until the SSL handshake is complete on the primary subflow is worth it for cases where secure join is more important than faster subflow addition. If the spec continues to support the existing join mechanism, then the faster subflow addition albeit slightly less secure (with TLS) is still there for those cases where this is necessary.  

One other thing is that the 4th ACK from the server on Joins should probably not contain the Data ACK so as to not give away the Data Sequence space to a connection hijacker.

Thanks,
Anumita

> 
> 
> 
> Olivier
> 


From marcelo@it.uc3m.es  Fri Sep 27 13:52:58 2013
Return-Path: <marcelo@it.uc3m.es>
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 8C67E21E8087 for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 13:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.31
X-Spam-Level: 
X-Spam-Status: No, score=-106.31 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UE0tildFnEfL for <multipathtcp@ietfa.amsl.com>; Fri, 27 Sep 2013 13:52:53 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1BA21E8095 for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 13:52:49 -0700 (PDT)
Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id F0F11CD555F for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 22:52:47 +0200 (CEST)
X-uc3m-safe: yes
Received: from [163.117.203.208] (unknown [163.117.203.208]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: marcelo@smtp01.uc3m.es) by smtp01.uc3m.es (Postfix) with ESMTPSA id C4AE3CD555E for <multipathtcp@ietf.org>; Fri, 27 Sep 2013 22:52:47 +0200 (CEST)
Message-ID: <5245F017.4020800@it.uc3m.es>
Date: Fri, 27 Sep 2013 22:52:39 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: multipathtcp@ietf.org
References: <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF94B02FB@EMV67-UKRD.domain1.systemhost.net> <A2E337CDB7BC4145B018B9BEE8EB3E0D3FF9CFE171@EMV67-UKRD.domain1.systemhost.net> <6CE57EDE-92FE-457E-8237-DDBC3910A6BB@apple.com> <5245DF07.7050600@uclouvain.be>
In-Reply-To: <5245DF07.7050600@uclouvain.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelistedACL 138 matched, not delayed by milter-greylist-4.2.7 (smtp01.uc3m.es); Fri, 27 Sep 2013 22:52:47 +0200 (CEST)
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-20178.002
Subject: Re: [multipathtcp] Thursday 3rd October: MPTCP interim (audio) meeting on security
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 20:52:58 -0000

Hi,

some comments below...

El 27/09/13 21:39, Olivier Bonaventure escribió:
> Anumita,
>>
>> Prong 2 or the discussion of how to alter MP_JOINs so as to not be
>> dependent on keys exchanged in the clear is a higher priority (compared
>> to Prong 1) although it can take more time. Perhaps if we could start
>> with the list of ideas on the table, that would be great ?
>
> The first issue that we need to take into account are the constraints 
> on the three way handshake and the utilisation of crypto inside TCP.
>
> The current design heavily depends on the assumption that we cannot 
> perform strong crypto inside TCP and the constraint on the maximum 
> length of the TCP option field (mainly during the three way 
> handshake). Given these two constraints, it seems pretty difficult to 
> provide a strong and secure mechanism in the TCP layer. We will always 
> be blocked by the limited size of the TCP options. Exchanging public 
> keys or certificates is impossible in TCP options.
>
> A first possible approach is to allow MPTCP to reuse keys that are 
> derived in a secure manner by the application. This solution could 
> work with SSL/TLS and SSH for example. These application-layer 
> protocols can derive secure keys after a Diffie-Hellman exchange. 
> MPTCP could provide an API to receive such a key and use it to 
> autheticate MP_JOINs.
>

I understand that the data that would be carried in the MPTCP session in 
this case would be SSL data, correct?
If this is the case, then the data itself is already encrypted, so i 
guess we should do a residual threat analysis to understand what is what 
an attacker can do to already encrypted ssl traffic.

The other limitiation here of course is that this only applies to SSL 
traffic, which afaict is only a small fract of the internet traffic, so, 
this begs the question what happens with the remaining traffic, right?


> This solution has been described in
> http://tools.ietf.org/html/draft-paasch-mptcp-ssl-00
> and there is a prototype implementation.
>
> This draft sketches the solution and shows that it is feasible. 
> However, there are two points that would need to be improved :
>  - the algorithm to derive the MPTCP session should be proposed by 
> security experts
>  - MPTCP should use a key identifier and allow the application to 
> change the MPTCP key (e.g. as a result of a change of the master keys 
> by SSL/TLS)
>
> With this solution, MPTCP cannot create additional subflows at the 
> beginning of the MPTCP connection since it must wait until the 
> security keys have been computed.
>
> A second direction that has been discussed is the utilisation of hash 
> chains. The client and the server could generate a hash chain for each 
> MPTCP connection and use it to authenticate subsequent MP_JOINs. The 
> hash chains could be included in the SYN and SYN+ACK segments if there 
> is enough option space. The main advantage of hash chains is that they 
> do not require strong crypto. However, a hash chain will be valid for 
> N additional subflows. To create the N+1th subflow, the peers would 
> need to exchange securely a new hash chain.
>
> A third direction could be to build upon the tcpcrypt proposal and 
> include it inside MPTCP. This requires strong crypto in the transport 
> layer.
>
> My impression is that trying to secure MPTCP without securing the data 
> exchanged is a bit overkill and I would try to pursue the first 
> direction in more details.
>

I actually think the argument is in the other side, if the traffic is 
already encrypted, how much harm can an attacker do?

I mean, i dont oppose to this, i only belibe that solves a small piece 
of the problem.

Regards, marcelo

>
>
> Olivier
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>

