
From nobody Sun Nov  1 00:35:07 2015
Return-Path: <cse1200137@iiti.ac.in>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78AA1A8A99 for <multipathtcp@ietfa.amsl.com>; Sat, 31 Oct 2015 13:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.695
X-Spam-Level: 
X-Spam-Status: No, score=0.695 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwbF66yTuMGj for <multipathtcp@ietfa.amsl.com>; Sat, 31 Oct 2015 13:10:48 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 056C71A8A95 for <multipathtcp@ietf.org>; Sat, 31 Oct 2015 13:10:46 -0700 (PDT)
Received: by igdg1 with SMTP id g1so33483218igd.1 for <multipathtcp@ietf.org>; Sat, 31 Oct 2015 13:10:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iiti_ac_in.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cbi0snQaWzCv83KJx0ZRUfFy+RE3R8PJlTn7lRyAt+Q=; b=r0o8zvpM7bTGP1qqNuf7i/PVjHQIU8hG9ikjMIfrp4xBFVHv+8ywK64j2x3yWY17uw mjO5SvPv2/zdRGTkDqZJnzaDVRq/cI4Vb+p64VZmo8t/lkAFApbeEAG9SETC+BBobJ8t HEIvZ8l7aS95ssgQqYlz3rzFMcm4SwaaHoQrns7n9RoPbZIoc/nwMUut7eeikFzvPI4u 1LzuCxO7qZEqbq+pCZF/gpuXavxEYaXP8h+36RIsPwPnBEpZPiA4UXKsmsJtLVkvmdti dKSnYHds0d6eTxeU6++p5Gq25f32cBm1PNivNLoK0tYyBSwbqNO3aMh/+oS8tQhbDCXR T7iA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=cbi0snQaWzCv83KJx0ZRUfFy+RE3R8PJlTn7lRyAt+Q=; b=Ax8CpPwYjPf2DOdBJ1j9kae83vTF3X1kcBGVd9FBGu265MtcsGRZf4UMXBcSMuhgn9 fU04fyPTiY9Ib7G3C4aGDKtbcjOIgvmlfw/8TGDNO5PqWEEiPv4piFWhSXjXEj2KDv2F r9e7CIac38knPfi8MYxImzC/MHFcONnFLGNryJ1U0rcNLtnM4Hy5VCXfQ/VT+lDS6Kno cuhwkaYhDFu2sjo7W/xxiOxNPWu8wnl/YmUUYVUkaEJkmtJlvNoTirTJ8aCHNPRXVzj3 sjKojKbvTe09a4naDVZvwqy9ttKe8fTR9ooXZn2WfcCISU10vHRmafiMmpO6i5sQejtq lYHg==
X-Gm-Message-State: ALoCoQne3KaeBFzgqB/i+pVjZy66pkAGOIWlQh5WlsEm6RSAnGvGwHrr4cLdOFYK7mo3+6vTVx+I
MIME-Version: 1.0
X-Received: by 10.50.111.79 with SMTP id ig15mr4176522igb.41.1446322246196; Sat, 31 Oct 2015 13:10:46 -0700 (PDT)
Received: by 10.79.0.88 with HTTP; Sat, 31 Oct 2015 13:10:46 -0700 (PDT)
In-Reply-To: <9505AE4C-7707-4518-96C6-4F52905662BA@gmail.com>
References: <CAMNnBcgUi-3WjRjJo6FjdLdNe4UBE2euk6pY54MGnzOfEEvimA@mail.gmail.com> <9505AE4C-7707-4518-96C6-4F52905662BA@gmail.com>
Date: Sun, 1 Nov 2015 01:40:46 +0530
Message-ID: <CAMNnBcgX_q9NAt5FK8xU4-q2V_wg2W8OM4bjd_OCFyUmx44Tog@mail.gmail.com>
From: Vikas Raunak <cse1200137@iiti.ac.in>
To: Martin Becke <scimbe@gmail.com>
Content-Type: multipart/alternative; boundary=089e01294c8cb7408105236c23d1
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/qJDu8QN9slZtng4yO1UZvcLDwlY>
X-Mailman-Approved-At: Sun, 01 Nov 2015 00:35:06 -0700
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] MPTCP Simulation
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2015 20:10:50 -0000

--089e01294c8cb7408105236c23d1
Content-Type: text/plain; charset=UTF-8

Dear sir

Thanks a lot for your reply.

The observations were for : 50 Mbps, 1ms (subflow 0) and 5 Mbps, 100 ms
(subflow 1) p2p links (ns-3) under Round Robin scheduling and LIA
congestion control algorithm.

Sir, my doubt pertains to the way retransmission (driven by dup acks) is
done in MPTCP. If Retransmissions are driven only by subflow sequence
numbers: this should not cause reductions in cwnd of faster link under any
scheduling (even under RR, which is not the default scheduling algorithm
for the Linux MPTCP kernel).

In my understanding, an ACK in MPTCP has a DSS option that contains a Data
Ack (for flow control only), and the normal subflow-level ack (as in TCP)
drives retransmissions. So, if a subflow gets 3 acks with same data ack
field but different subflow-level field, then it should not retransmit,
since it is not a dup-ack at the subflow level.

The explanation of the behaviour in the figure: the behaviour could only
happen (repeated retransmissions on the faster subflow) when data-acks also
participate in retransmissions i.e. two acks with same data field are
considered as duplicates. As packets on faster link arrive earlier (more
"dup data acks"), repeated halving of the faster link's cwnd suppresses it.

Sir, I would be very grateful if you could spare some time considering this
problem/doubt. Sir, please correct me if I am making a misinterpretation (I
suspect this is a very big issue, which if true makes the ns-3 model wrong).

Thanks a lot.
Regards
Vikas


On Sat, Oct 31, 2015 at 10:59 PM, Martin Becke <scimbe@gmail.com> wrote:

> Hi,
>
> i created a simulation in omen++/inet  for several months.
> I had the same observation in some scenarios with short FIFO Queues.
> Here the behavior was caused by a short FIFO queue and a huge difference
> in the BDP (for example on connecting routers).
> Have you more information about your queue status and the BDP of both
> paths?
> I was not able to reproduce this effect in a real testbed.
>
> Best,
>
> Martin
>
>
> Am 29.10.2015 um 12:53 schrieb Vikas Raunak <cse1200137@iiti.ac.in>:
>
> Hi
>
> I am working on MPTCP using the ns-3 simulator
> <https://hal.archives-ouvertes.fr/hal-00641539/document>. I have a very
> important observation.
>
> Please consider the attached figure. In this, the congestion window of
> faster delay subflow (subflow 0) is reduced under Round Robin scheduling.
>
> The simulator repeatedly halves the congestion window of the faster
> subflow. Why is it happening ? As per MPTCP specifications this should not
> happen.
>
> Could you explain this observation. I have tried to seek the explanation
> from a lot of people and yet, I have no answer.
>
> Thanks a lot for your help.
> Regards
> Vikas
> <congestion_windows.png>_______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
>

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

<div dir=3D"ltr"><div>Dear sir</div><div><br></div><div>Thanks a lot for yo=
ur reply.</div><div><br></div><div>The observations were for : 50 Mbps, 1ms=
 (subflow 0) and 5 Mbps, 100 ms (subflow 1) p2p links (ns-3) under Round Ro=
bin scheduling and LIA congestion control algorithm.</div><div><br></div><d=
iv>Sir, my doubt pertains to the way retransmission (driven by dup acks) is=
 done in MPTCP. If Retransmissions are driven only by subflow sequence numb=
ers: this should not cause reductions in cwnd of faster link under any sche=
duling (even under RR, which is not the default scheduling algorithm for th=
e Linux MPTCP kernel).</div><div><br></div><div>In my understanding, an ACK=
 in MPTCP has a DSS option that contains a Data Ack (for flow control only)=
, and the normal subflow-level ack (as in TCP) drives retransmissions. So, =
if a subflow gets 3 acks with same data ack field but different subflow-lev=
el field, then it should not retransmit, since it is not a dup-ack at the s=
ubflow level.</div><div><br></div><div>The explanation of the behaviour in =
the figure: the behaviour could only happen (repeated retransmissions on th=
e faster subflow) when data-acks also participate in retransmissions i.e. t=
wo acks with same data field are considered as duplicates. As packets on fa=
ster link arrive earlier (more &quot;dup data acks&quot;), repeated halving=
 of the faster link&#39;s cwnd suppresses it.</div><div><br></div><div>Sir,=
 I would be very grateful if you could spare some time considering this pro=
blem/doubt. Sir, please correct me if I am making a misinterpretation (I su=
spect this is a very big issue, which if true makes the ns-3 model wrong).<=
/div><div><br></div><div>Thanks a lot.</div><div>Regards</div><div>Vikas</d=
iv><div><br></div><div></div></div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Sat, Oct 31, 2015 at 10:59 PM, Martin Becke <span dir=
=3D"ltr">&lt;<a href=3D"mailto:scimbe@gmail.com" target=3D"_blank">scimbe@g=
mail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div sty=
le=3D"word-wrap:break-word">Hi,=C2=A0<div><br></div><div>i created a simula=
tion in omen++/inet =C2=A0for several months.=C2=A0</div><div>I had the sam=
e observation in some scenarios with short FIFO Queues.=C2=A0</div><div>Her=
e the behavior was caused by a short FIFO queue and a huge difference in th=
e BDP (for example on connecting routers).=C2=A0</div><div>Have you more in=
formation about your queue status and the BDP of both paths?</div><div>I wa=
s not able to reproduce this effect in a real testbed.=C2=A0</div><div><br>=
</div><div>Best,</div><div><br></div><div>Martin</div><div>=C2=A0<br><div><=
blockquote type=3D"cite"><div><div class=3D"h5"><div>Am 29.10.2015 um 12:53=
 schrieb Vikas Raunak &lt;<a href=3D"mailto:cse1200137@iiti.ac.in" target=
=3D"_blank">cse1200137@iiti.ac.in</a>&gt;:</div><br></div></div><div><div><=
div class=3D"h5"><div dir=3D"ltr">Hi<div><br></div><div>I am working on MPT=
CP using the <a href=3D"https://hal.archives-ouvertes.fr/hal-00641539/docum=
ent" target=3D"_blank">ns-3 simulator</a>. I have a very important observat=
ion.</div><div><br></div><div>Please consider the attached figure. In this,=
 the congestion window of faster delay subflow (subflow 0) is reduced under=
 Round Robin scheduling.</div><div><br></div><div>The simulator repeatedly =
halves the congestion window of the faster subflow. Why is it happening ? A=
s per MPTCP specifications this should not happen.</div><div><br></div><div=
>Could you explain this observation. I have tried to seek the explanation f=
rom a lot of people and yet, I have no answer.</div><div><br></div><div>Tha=
nks a lot for your help.</div><div>Regards</div><div>Vikas</div></div>
</div></div><span>&lt;congestion_windows.png&gt;</span>____________________=
___________________________<br>multipathtcp mailing list<br><a href=3D"mail=
to:multipathtcp@ietf.org" target=3D"_blank">multipathtcp@ietf.org</a><br><a=
 href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br></div></block=
quote></div><br></div></div></blockquote></div><br></div>

--089e01294c8cb7408105236c23d1--


From nobody Sun Nov  1 00:47:08 2015
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2F11B6F7E for <multipathtcp@ietfa.amsl.com>; Sun,  1 Nov 2015 00:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.101
X-Spam-Level: 
X-Spam-Status: No, score=-4.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jTOZhoYGgFcM for <multipathtcp@ietfa.amsl.com>; Sun,  1 Nov 2015 00:47:06 -0700 (PDT)
Received: from mail-in1.asia.apple.com (mail-out.asia.apple.com [17.82.254.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D71701B6F7C for <multipathtcp@ietf.org>; Sun,  1 Nov 2015 00:47:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple;  q=dns/txt; i=@apple.com; t=1446364023; x=2310277623; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=h37S2+4Vd9Ov9VmTwA75erJ2R9VjINZx6ZXb/MAKELs=; b=XeY9o/pSpskvj8kA1jUED8JeLgQMT3gLisvxFxKT+LV4DkJktlNQMISFiQRJ75/B jE98mIlg+fC3MoOI/zVjnx9HHXDVomX0g7I6MUoob0bjhgUgtPGJIAFvY5frYC9m vjI5HbSv1gf6i29W73E1oCXg7vcWPT1FEMRiw+3yiiK9HKr4+MZg16nhfTnK5v31 gAUgOyq+72aFeAjGiB1YsgYaykLYOGJxRultT1l/5fI7FRKF3bzvjrh63SLPrkw3 wQFChVBjQRnykWIKzJReL9shWFxnr6BIbeuTU//yfK4FsVHTWNat2YSaAuy35YwL TAe5FDDquzJEgywlABUi5Q==;
Received: from relay1.asia.apple.com ( [17.82.200.18]) by mail-in1.asia.apple.com (Apple Singapore Mail Gateway) with SMTP id FA.01.31082.773C5365; Sun,  1 Nov 2015 15:47:03 +0800 (MYT)
X-AuditID: 1152fe11-f79686d00000796a-2b-5635c3772888
Received: from sng-mmpp-sz01.asia.apple.com ( [17.82.200.58]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay1.asia.apple.com (Apple Singapore relay) with SMTP id 75.5A.18564.773C5365; Sun,  1 Nov 2015 15:47:03 +0800 (MYT)
Received: from localhost ([17.83.29.205]) by sng-mmpp-sz01.asia.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NX400BFTLMEJM00@sng-mmpp-sz01.asia.apple.com> for multipathtcp@ietf.org; Sun, 01 Nov 2015 15:47:03 +0800 (SGT)
Sender: cpaasch@apple.com
Date: Sun, 01 Nov 2015 16:47:02 +0900
From: Christoph Paasch <cpaasch@apple.com>
To: "Demaria, Fabrizio" <fabrizio.demaria@intel.com>
Message-id: <20151101074702.GS1778@Chimay.local>
References: <F80DA2172C0B3C4E8DE69F8628BD3AC8FBE68E@IRSMSX103.ger.corp.intel.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
In-reply-to: <F80DA2172C0B3C4E8DE69F8628BD3AC8FBE68E@IRSMSX103.ger.corp.intel.com>
User-Agent: Mutt/1.5.24 (08e81162482f) (2015-08-30)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUiGHRCSLf8sGmYwcUFXBafV19nc2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuXF9xgLTnFWPNt6lK2B8Sx7FyMnh4SAiUTngR1MELaYxIV7 69m6GLk4hAR2M0p8P7SKBabo78p2dojEZCaJR+cXs0A485gkXu+5xAxSJSwgKdF95w6QzcHB IqAqseRyKkiYTUBL4u3tdlYQWwRo0KK29WA2s4CxxOENt9kgWm0llnzdAHYFr4CBxJGZfYwg tpBAsMT6FTOYIeKCEj8m32OB6NWSWL/zOBOELS3x6O8MsG84BUIkJi3YDNYrCjS/6cgcZpA7 JQT+skpc+LeLfQKjyCwks2YhmTULyawFjMyrGMVzEzNzdDPzDPUSizMT9RILCnJS9ZLzczcx gkP9n+AOxqkLDQ8xCnAwKvHwxm8zDRNiTSwrrsw9xCjBwawkwntlPVCINyWxsiq1KD++qDQn tfgQozQHi5I4r3GtUZiQQHpiSWp2ampBahFMlomDU6qBsTcn1+dfweKlmyewxU/5XdBzmk1U acGX5ysd0teIzz56JHfN6vcZ5161Tr3081ThHyuNK/bqkWuFf6hV6Bgdunbu5JJNc33i/O4L aMrHdTs8zPsk9Hr586dWPgsWa8z6tfmRXEXcieX/jcMvzvPq11qVoM+uJdFm0aAuFLTr7rut az77bsoy+qDEUpyRaKjFXFScCAC+aDULcQIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUiGHTCSrf8sGmYwfzP7BafV19nc2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuXF9xgLTnFWPNt6lK2B8Sx7FyMnh4SAicTfle1QtpjEhXvr 2boYuTiEBCYzSTw6v5gFwpnHJPF6zyVmkCphAUmJ7jt3gGwODhYBVYkll1NBwmwCWhJvb7ez gtgiQEMXta0Hs5kFjCUOb7jNBtFqK7Hk6wYmEJtXwEDiyMw+RhBbSCBYYv2KGcwQcUGJH5Pv sUD0akms33mcCcKWlnj0dwbYoZwCIRKTFmwG6xUFmt90ZA7zBEbBWUjaZyFpn4WkfQEj8ypG 0aLUnMRKQ73E4sxEvcSCgpxUveT83E2MkNAU2sH4cb/BIUYBDkYlHt7abaZhQqyJZcWVuYcY JTiYlUR4r6wHCvGmJFZWpRblxxeV5qQWH2KU5mBREuednmcQJiSQnliSmp2aWpBaBJNl4uCU amDsy8pn/mMzt3S30H1Rm57PvPtzvv/Yk9Q5Rf5tul/XVb+JNlP9Va8eE5feHc9gFHLmRsbc h/vaIwPnPuJwLo172qq5eMrGvYcUnZ2nmehfTJDlSv1rrGZl27xl13PzNed2eK7/LSIctiLb +8dW4TmqS25l//37c5qMh+LBxXXHliltWx3amdGnxFKckWioxVxUnAgA6m8mXUkCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/1mUWuR03_IXWPEX7NG4t8GFeEV8>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] RFC6824bis-04 ADD_ADDR2 comments
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 07:47:07 -0000

Hello Fabrizio,

On 20/10/15 - 09:00:55, Demaria, Fabrizio wrote:
> On the document RFC6824bis-04, where ADD_ADDR2 implementation is specified, there are two points I would like to discuss regarding the following statement:
> 
> "The key used in the HMAC calculation is that of the sender,
> as originally declared in the MP_CAPABLE handshake. The message for
> the HMAC is the Address ID, IP Address, and Port which precede the
> HMAC in the ADD_ADDR2 option."
> 
> This is the indicated procedure to calculate the HMAC to be added in ADD_ADDR2.
> I think it should be specified how to handle the case in which the Port is not present (being optional).

this is a good point. It is currently missing in the spec.
I think it is ok if we set the Port to 0 in the case where it is not set by
the host.

> Moreover, since we have the SHA-1 hash algorithm already implemented for MP_CAPABLE that takes two keys as input, it would be good considering to use both the key of the sender and the one of the receiver for ADD_ADDR2, too. This might ease reuse of code and add some security improvement overall.

I agree. We should use both keys. It has not downsides and will improve the
security.


Christoph


From nobody Mon Nov  2 00:06:15 2015
Return-Path: <njwilliams@swin.edu.au>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C6C1B349E for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 00:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.506
X-Spam-Level: 
X-Spam-Status: No, score=-3.506 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20QouoRCDkpY for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 00:06:11 -0800 (PST)
Received: from gpo3.cc.swin.edu.au (gpo3.cc.swin.edu.au [136.186.1.32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D5A21B3480 for <multipathtcp@ietf.org>; Mon,  2 Nov 2015 00:06:11 -0800 (PST)
Received: from Nigels-MacBook-Air.local (vpn242-147.cc.swin.edu.au [136.186.242.147]) by gpo3.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id tA2864SP012063; Mon, 2 Nov 2015 19:06:07 +1100
Message-ID: <5637196C.9050207@swin.edu.au>
Date: Mon, 02 Nov 2015 19:06:04 +1100
From: Nigel Williams <njwilliams@swin.edu.au>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: multipathtcp <multipathtcp@ietf.org>, Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/1QHIOobTqDOV9bZYQqAoK82wkmI>
Subject: [multipathtcp] Further comments on the WG FreeBSD status update
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 08:06:13 -0000

Hi Yoshi,

You asked a couple of questions during this WG this morning and although 
I was watching the meeting unfortunately I was not able to get an answer 
to you.

The questions were about how much of the MPTCP protocol was currently 
supported by the FreeBSD implementation and whether any interop testing 
had been done.

In terms of how much of the protocol is implemented - for the moment 
MP_CAPABLE, ADD_ADDR, MP_JOIN, DSS (DSN, DACK, DFIN) are supported. It 
only supports sending of 4-byte DSNs. Currently missing are things like 
MP_FASTCLOSE, fallback, checksums...

As Grenville mentioned I had tried some interop testing a little over a 
year ago, though have not done so recently while I have been re-working 
the implementation.

There are still some stability issues with FreeBSD-to-FreeBSD 
connections that I need to address, but after this the intention is to 
fill in the gaps in protocol support and again look at interop. I'll 
update the list when there is progress on this.

cheers,
nigel


From nobody Mon Nov  2 00:30:43 2015
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 211FC1B331F for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 00:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dmqdG8Wv3Qv for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 00:30:39 -0800 (PST)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 01A4B1ACEC6 for <multipathtcp@ietf.org>; Mon,  2 Nov 2015 00:30:39 -0800 (PST)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.16]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 737961980E3; Mon,  2 Nov 2015 09:30:21 +0100 (CET)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be 737961980E3
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1446453021; bh=tpAgP6BTZbGzDu1fXHw0zyY/wBWVCHEHl4M0W6gkU/A=; h=Reply-To:Subject:References:To:Cc:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=WFnYhu0zdtdVonE+Rd/3dFCFh0hrC6n4nBRdjrPBueRXfyhDPAUMnNjD9+MnUGdqf fTEMGzBGGpv825u2FWPFzBBhqDTuHsyX4GR9RKTE4tqYsYCQ+6W2Qfb+xfhl9AapcS RVDyJqT70/d1I5PWPgTpVlGLYfeZOM87D2ZCWlHs=
References: <F80DA2172C0B3C4E8DE69F8628BD3AC8FBE68E@IRSMSX103.ger.corp.intel.com> <20151101074702.GS1778@Chimay.local>
To: Christoph Paasch <cpaasch@apple.com>, "Demaria, Fabrizio" <fabrizio.demaria@intel.com>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <5635F202.5030703@uclouvain.be>
Date: Sun, 1 Nov 2015 12:05:38 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151101074702.GS1778@Chimay.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99-beta1 at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: 737961980E3.A01DA
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/XiaiQdYsJch9J39ZzmFmQV1fOKw>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] RFC6824bis-04 ADD_ADDR2 comments
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 08:30:41 -0000

Hello,
>
> On 20/10/15 - 09:00:55, Demaria, Fabrizio wrote:
>> On the document RFC6824bis-04, where ADD_ADDR2 implementation is specified, there are two points I would like to discuss regarding the following statement:
>>
>> "The key used in the HMAC calculation is that of the sender,
>> as originally declared in the MP_CAPABLE handshake. The message for
>> the HMAC is the Address ID, IP Address, and Port which precede the
>> HMAC in the ADD_ADDR2 option."
>>
>> This is the indicated procedure to calculate the HMAC to be added in ADD_ADDR2.
>> I think it should be specified how to handle the case in which the Port is not present (being optional).
>
> this is a good point. It is currently missing in the spec.
> I think it is ok if we set the Port to 0 in the case where it is not set by
> the host.

Agreed

>> Moreover, since we have the SHA-1 hash algorithm already implemented for MP_CAPABLE that takes two keys as input, it would be good considering to use both the key of the sender and the one of the receiver for ADD_ADDR2, too. This might ease reuse of code and add some security improvement overall.
>
> I agree. We should use both keys. It has not downsides and will improve the
> security.

Agreed. We should probably define in rfc6824bis a generic procedure to 
compute all the HMACs (MP_JOIN, ADD_ADDR2) and then apply it each time 
it is necessary


Olivier


From igor.lopez@ehu.eus  Mon Nov  2 03:37:57 2015
Return-Path: <igor.lopez@ehu.eus>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B521B2CB7 for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 03:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Px8hv21rBuRY for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 03:37:53 -0800 (PST)
Received: from smtp.ehu.eus (smtp.lg.ehu.es [158.227.0.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 239011B2C93 for <multipathtcp@ietf.org>; Mon,  2 Nov 2015 03:37:51 -0800 (PST)
Received: from smtp.ehu.eus (localhost.localdomain [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 3327137A35 for <multipathtcp@ietf.org>; Mon,  2 Nov 2015 12:37:49 +0100 (CET)
Received: from [158.227.98.62] (unknown [158.227.98.62]) by smtp1 (Postfix) with ESMTPSA id EDD5E37461 for <multipathtcp@ietf.org>; Mon,  2 Nov 2015 12:37:48 +0100 (CET)
Message-ID: <56374B39.8020102@ehu.eus>
Date: Mon, 02 Nov 2015 12:38:33 +0100
From: Igor Lopez Orbe <igor.lopez@ehu.eus>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: multipathtcp@ietf.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4 (smtp1 [0.0.0.0]); Mon, 02 Nov 2015 12:37:49 +0100 (CET)
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-8.0.0.1202-21916.006
X-TM-AS-Result: No-0.410-7.0-31-1
X-imss-scan-details: No-0.410-7.0-31-1
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4 (postfix.imss71 [0.0.0.0]); Mon, 02 Nov 2015 12:37:50 +0100 (CET)
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/mAmNsiiGhy5h5XMhF6lIwdVrn1Q>
X-Mailman-Approved-At: Mon, 02 Nov 2015 07:05:56 -0800
Subject: [multipathtcp] Extension of MPTCP socket interface for selecting the scheduler to be used
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 11:56:45 -0000

Hello,

I am wondering if it could be possible to extend the Socket Interface
Extensions described in RFC 6897 in order to select the scheduled used
by MPTCP for a connection. During last months multiple scheduler
proposals have been released. Each scheduler is optimal for a concrete
application and different applications, with different associated
schedulers, could coexist in the same node. Thus, the extension of the
Socket Interface would allow to define the most proper scheduler by each
application.
As an example of this, we have recently submitted a redundant delivery
scheme [1] for services that demand low latency and high reliability
communications. These services could coexist in the same node with other
services with more regular requirements and therefore using other
schedules that care more about the network use. For that, the best idea
seems to be able to define in the socket the scheduler that is aim to be
used in that MPTCP connection.

Best regards,

Igor

[1] https://github.com/i2t/rmptcp

-- 
Igor Lopez Orbe <igor.lopez@ehu.eus>
I2T Research Group, Department of Communications Engineering
University of the Basque Country (UPV/EHU)


From nobody Mon Nov  2 08:25:53 2015
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6DF71B4950 for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 08:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F759w6zMWZEw for <multipathtcp@ietfa.amsl.com>; Mon,  2 Nov 2015 08:25:50 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 384341B494E for <multipathtcp@ietf.org>; Mon,  2 Nov 2015 08:25:50 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 7E184C144C47C; Mon,  2 Nov 2015 16:25:45 +0000 (GMT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id tA2GPlgF021628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Nov 2015 17:25:48 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.114]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Mon, 2 Nov 2015 17:25:47 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Igor Lopez Orbe <igor.lopez@ehu.eus>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] Extension of MPTCP socket interface for selecting the scheduler to be used
Thread-Index: AQHRFX/9MxcBbmHV00GYJ2vEHPewSJ6I6oNg
Date: Mon, 2 Nov 2015 16:25:47 +0000
Message-ID: <655C07320163294895BBADA28372AF5D48538D34@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <56374B39.8020102@ehu.eus>
In-Reply-To: <56374B39.8020102@ehu.eus>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/2kBjmSS2U912hb9y5XQXeaFkJ-4>
Subject: Re: [multipathtcp] Extension of MPTCP socket interface for selecting the scheduler to be used
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 16:25:52 -0000

We had many discussions on that when writing RFC 6897, but at that time it =
was consensus in the WG to wait for more implementation experience.

A future extension of RFC 6897 has always been on the table, see e.g. Appen=
dix A. But I'd suggest to closely align any follow-up document with actual =
implementations.

Michael=20

> -----Original Message-----
> From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of
> Igor Lopez Orbe
> Sent: Monday, November 02, 2015 12:39 PM
> To: multipathtcp@ietf.org
> Subject: [multipathtcp] Extension of MPTCP socket interface for
> selecting the scheduler to be used
>=20
> Hello,
>=20
> I am wondering if it could be possible to extend the Socket Interface
> Extensions described in RFC 6897 in order to select the scheduled used
> by MPTCP for a connection. During last months multiple scheduler
> proposals have been released. Each scheduler is optimal for a concrete
> application and different applications, with different associated
> schedulers, could coexist in the same node. Thus, the extension of the
> Socket Interface would allow to define the most proper scheduler by
> each
> application.
> As an example of this, we have recently submitted a redundant delivery
> scheme [1] for services that demand low latency and high reliability
> communications. These services could coexist in the same node with
> other
> services with more regular requirements and therefore using other
> schedules that care more about the network use. For that, the best idea
> seems to be able to define in the socket the scheduler that is aim to
> be
> used in that MPTCP connection.
>=20
> Best regards,
>=20
> Igor
>=20
> [1] https://github.com/i2t/rmptcp
>=20
> --
> Igor Lopez Orbe <igor.lopez@ehu.eus>
> I2T Research Group, Department of Communications Engineering
> University of the Basque Country (UPV/EHU)
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Thu Nov  5 05:45:59 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A86F61B2C62 for <multipathtcp@ietfa.amsl.com>; Thu,  5 Nov 2015 05:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGF3lOiHWd9b for <multipathtcp@ietfa.amsl.com>; Thu,  5 Nov 2015 05:45:51 -0800 (PST)
Received: from relais-inet.orange.com (relais-nor34.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A49341B2C64 for <multipathtcp@ietf.org>; Thu,  5 Nov 2015 05:45:50 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 7F68C402D9; Thu,  5 Nov 2015 14:45:49 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.57]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 54B111A0069; Thu,  5 Nov 2015 14:45:49 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM23.corporate.adroot.infra.ftgroup ([fe80::787e:db0c:23c4:71b3%19]) with mapi id 14.03.0248.002; Thu, 5 Nov 2015 14:45:42 +0100
From: <mohamed.boucadair@orange.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
Thread-Index: AQHRF86Wij74CTaPZ0ezZp8tXFg1ZZ6Nb4fw
Date: Thu, 5 Nov 2015 13:45:41 +0000
Message-ID: <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com>
In-Reply-To: <20151105133319.27130.76692.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/FaAbzVMcn4RU41lqhlpPGGjktMU>
Cc: "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 13:45:57 -0000

Dear all,

This is an update to a proposal that intends to avoid requiring an extra en=
capsulating scheme between a CPE and an MPTCP Concentrator located in the p=
rovider's network.=20

The document suggests also relaying UDP packets into TCP-formatted packets =
in the CPE-Concentrator leg. Some features may be disabled/enabled at the C=
PE/Concentrator when processing UDP packets.

The main motivation is to ease integrating an MPTCP Concentrator into an op=
erational network without requiring updating intermediate service functions=
 to support another yet encapsulation scheme.

Comments are more than welcome.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> internet-drafts@ietf.org
> Envoy=E9=A0: jeudi 5 novembre 2015 14:33
> =C0=A0: i-d-announce@ietf.org
> Objet=A0: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>=20
>=20
>         Title           : An MPTCP Option for Network-Assisted MPTCP
> Deployments: Plain Transport Mode
>         Authors         : Mohamed Boucadair
>                           Christian Jacquenet
>                           Denis Behaghel
>                           Stefano Secci
> 	Filename        : draft-boucadair-mptcp-plain-mode-03.txt
> 	Pages           : 14
> 	Date            : 2015-11-05
>=20
> Abstract:
>    One of the promising deployment scenarios for Multipath TCP (MPTCP)
>    is to enable a Customer Premises Equipment (CPE) that is connected to
>    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of its
>    network attachments.  Because of the lack of MPTCP support at the
>    server side, some service providers now consider a network-assisted
>    model that relies upon the activation of a dedicated function called
>    MPTCP Concentrator.  This document focuses on a deployment scheme
>    where the identity of the MPTCP Concentrator(s) is explicitly
>    configured on connected hosts.
>=20
>    This document specifies an MPTCP option that is used to avoid an
>    encapsulation scheme between the CPE and the MPTCP Concentrator.
>    Also, this document specifies how UDP traffic can be distributed
>    among available paths without requiring any encapsulation scheme.
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-boucadair-mptcp-plain-mode/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-boucadair-mptcp-plain-mode-03
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-mptcp-plain-mode-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Thu Nov  5 17:12:53 2015
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92DAA1AC422 for <multipathtcp@ietfa.amsl.com>; Thu,  5 Nov 2015 17:12:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTTbdOSfcaQ4 for <multipathtcp@ietfa.amsl.com>; Thu,  5 Nov 2015 17:12:42 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD931AC447 for <multipathtcp@ietf.org>; Thu,  5 Nov 2015 17:12:41 -0800 (PST)
Received: from EVMHT05-UKBR.domain1.systemhost.net (193.113.108.58) by EVMED04-UKBR.bt.com (10.216.161.34) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 6 Nov 2015 01:12:37 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by EVMHT05-UKBR.domain1.systemhost.net (193.113.108.58) with Microsoft SMTP Server (TLS) id 8.3.342.0; Fri, 6 Nov 2015 01:12:39 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03b.domain1.systemhost.net (10.55.202.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 6 Nov 2015 01:12:38 +0000
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1104.000; Fri, 6 Nov 2015 01:12:38 +0000
From: <philip.eardley@bt.com>
To: <multipathtcp@ietf.org>, <nishida@sfc.wide.ad.jp>
Thread-Topic: Draft minutes from MPTCP WG meeting
Thread-Index: AdEYMBKFsOzM5UsuQD2fNvoLVRtOeA==
Date: Fri, 6 Nov 2015 01:12:38 +0000
Message-ID: <ec7b8d4172ad4835b556fa582c806917@rew09926dag03b.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.202.232]
Content-Type: multipart/alternative; boundary="_000_ec7b8d4172ad4835b556fa582c806917rew09926dag03bdomain1sy_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/Z6P0Pj3U8alNzFCaxZXH7v2PTn4>
Subject: [multipathtcp] Draft minutes from MPTCP WG meeting
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 01:12:52 -0000

--_000_ec7b8d4172ad4835b556fa582c806917rew09926dag03bdomain1sy_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Here are the draft minutes for the WG meeting on Monday. Please let us know=
 of any corrections.

Many thanks to Pasi and Alan for taking the notes


Multipath TCP (MPTCP)
Draft agenda Date: Monday, November 2, 2015, 9:00 - 11:30 (Morning Session =
I)
Room: 413

Taking notes: Pasi Sarolahti

- Intro - Chairs [15mins]
-------------------------

* Status Updates

* Discussion on interim meeting output and other progression between meetin=
gs: E.g. increasing version number, which opens possibility to redesign sig=
naling

* Chairs: Realistic to last call before next IETF?

* Christoph Paasch: depending on how much we change the spec, it may be dif=
ficult to get done by next IETF, but will try to do that

* Shaoib Rao: why decided to drop implementation advice?

* Phil Eardly: Implementation People thought that the protocol documentatio=
n was sufficient

** Shaoib Rao: why do we support both 8-byte and 4-byte fields? why do we w=
ant to support 4 bytes?

** Yoshi Nishida: already discussed and consensus-called before

** Christoph: good point, people would not switch to 8 bytes, but will be l=
onger discussion to change this. Linux implementation support receiving bot=
h variants, but never sends 8 bytes

** Shaoib Rao: If timestamp option is mandatory, we would not need 8 bytes

** Alan Ford: we would not need to use timestamp option with 8-byte option,=
 but some people might have other uses. Linux does not need to send both if=
 it can accept. If we only support 8 bytes, what problem would it solve? ma=
kes simpler implementation, but it is only optional to implement

** Christoph: decission can be triggered by application based on envrionmen=
t

** Shaoib Rao: receiver should need to support both variants always.

** Shaoib: what is the motivation for 4 bytes?

** Alan: saving option space

** Shaoib: Header option placement is also problematic, alignment is import=
ant

** Alan: space constraints are problem

** Chistoph: implementation choice, can place options otherwise

** Yoshi: making 8 bytes mandatory, 4 bytes optional, would that make peopl=
e happy?

** Alan: that's basically what we already have. If we spell out more explic=
tly that sending is optional and receiving mandatory, would you be happier?=
 Conclusion: nothing fundamentally changes, but we spell out more clearly i=
n the draft that sending is optional

Implementation updates:

** Shaoib: implementing MPTCP in Solaris kernel, seems to be working well


- Making Multipath TCP robust for stateless webservers - Christoph Paasch (=
10 mins)    (draft-paasch-mptcp-syncookies)
------------------------------------------------------

(going through slides)

Yoshi: implementation status?

Christoph: no implementation yet

Phil: any implementation plans in Louvain?

Fabien Duch=EAne: no plans for implementation at Louvain yet

Shaoib: can try to implement but can't estimate when? Seems very complicate=
d but does seem necessary. Yes, seems relevant.

Phil: this would not be backward compatible

Alan: yes this is v1, not v0. Earlier you did not need to put key in data A=
CK, now you do need keys in data-ack

Alan: would love to get consensus on this, so that we can work forward

Phil: plan to give it a week or two, then do an explicit consensus call


- Reflecting on the MPTCP handshake" - Christoph Paasch (20 mins)
(draft-paasch-mptcp-loadbalancer + security)
--------------------------------------------

* Shaoib (on deployment behind L4 loadbalancers): question about currently =
deployed solution (missed)

* Christoph (answering): Netscaler is L7 load balancer, terminates connecti=
ons

* (missed Alan's question/comment)

* Yoshi: is token used only for server?

* Christoph: use is to identify the MPTCP connection, for single server thi=
s works well

* Yoshi: you want to change meaning only for one use case?

* Christoph: increasing information that the token carries

* Alan: to summarize: you want to decouple token from key. makes lot of sen=
se, seems fine. from signaling point of view: have flag to get key form ext=
ernal source, to say that key comes from TLS or somewhere else. Logical ext=
ension to what we got. Earlier we completely ran out of option space when t=
rying to do this. Maybe we should wait for TCPINC, to see if they give some=
 additional tools

* Christoph: worried about TCPINC, not sure how quick they are going to pro=
ceed.

* Phil: we should be able to finish our work earlier

* Alan: this does not need to be part of base v1 spec, but additional mecha=
nism.

* Christoph: can live very well with the TLS, but getting locally meaningfu=
l token would be a big issue.

* Phil: are the two issues (loadbalancers, security) totally separable issu=
es?

* Christoph: need to make token meaningful

* Alan: TLS is a potential solution to the problem

* Christoph: might we just decrease the size of the keys, they are already =
sent in the clear. Are there any MPTCP deployments that are not using TLS, =
and think seeing keys in clear is fine.

* Alan: our goal has never been to provide secure solution, but something e=
quivalent to TCP.

* Alan: this should be specified in a separate draft, at least initially...=
 concerned that this is a distraction, makes a jump away from where we are.

* Christoph: can we try to see whether we want to solve one of those issues=
?

* Phil: comments? personally think the datacenter case is important to solv=
e. Should be designing for the present, not the future.

* Christoph: do you think it is worthwhile to have draft to support discuss=
ion?

* Yoshi: yes

* Phil: wider issue: should there be more flexibility about the security so=
lution?

* Alan: we already have that kind of flexibility, haven't yet specified wha=
t the negotiation means. Would need to work through the details.

* Daniel Giffin: Both main TCPINC have been adopted to specify the negotiat=
ion of encryption protocol, also uses session ID (TCP-ENO), you might find =
that is useful.

* Christoph: We are deferring key exchange until after the SYN, could do it=
 already in SYN, maybe this would make it simpler in terms of signaling.

* Phil's conclusion: make a draft about the possible solution space


- Mptcp enduser use cases and enhancement opportunities - Chetan Harsha   (=
20 mins)   (draft-palanivelanchetansenthil-mptcp-enhancements)
-----------------------------------------------

* Christoph: is it separate TCP connections when MPTCP is disabled (about s=
lide on upload latency graph, with number of subflows)

* Chetan: yes

* Yoshi: why the red line behaves so differently with ups and downs?

(some discussion clarifying the graphs)

* Phil: interested in hearing about protocol tweaks you might suggest?

* Chetan: not sure yet what the changes could be, currently just some param=
eters

* Christoph: there is generally need for more signaling in MPTCP, to indica=
te subflow characteristics, to help scheduling traffic, but it is a bigger =
change is protocol.

* David Allan: if you are going to depend a lot on end-user signaling, make=
s life difficult for proxies.

* Shaoib: performance depends also on scheduler, that's why MPTCP results d=
iffer.


- LISA: A Linked Slow-Start Algorithm for MPTCP  - Runa Barik          (20 =
mins)    (draft-barik-mptcp-lisa)
----------------------------------------

* Yoshi: if bottleneck is not shared, we don't have to use slow-start?

* Runa: we are reducing latency in non-shared scenario also. Some differenc=
es are explained that paths are both 3G or WiFi.

(some additional discussion clarifying the results)

* Ilpo J=E4rvinen: not sure why number of retransmissions affects the way y=
ou say

* Runa: because of slow-start loss it is explained, not understanding Ilpo'=
s point

* Christoph: could be nice to see the patch and paper traces.

* Runa: will do, but currently a paper in submission.

* Phil: hard to understand

* Michio Honda: your point that slowing down slow start will reduce retrans=
missions, does not work in large delay-bw environments. Should see graphs r=
elating to BDP. Current parameters are unrealistic.


Management information base for MPTCP - Fabien Duch=EAne(15 mins)
(draft-duchene-mptcp-mib-00)
------------------------------------------

* Shaoib: thank you, this is very useful. One thing missing: what are the c=
ombinations of the flows supporting MPTCP vs. TCP. Port numbers, addresses =
as well.

* Fabien: will look at them, because wanted to keep it simple, might be get=
ting complicated, but is interesting

* Phil: good to have more feedback

* Yoshi: question to AD: when we define MIB, do we need cross-area review?

* Martin Stiemerling: should get MIB doctor review, might be useful to ask =
them when you have stable version, but before WGLC.

* Phil: should it be WG document before doing it? A: yes.

* Phil: plan to make this WG document before the next IETF


Phil: Update of Louvain Linux implementation? in terms of getting to mainli=
ne kernel

* Fabien: Nothing much to report

* Christoph: there are lot of users, but no contributions that come back


MPTCP for FreeBSD update  - Grenville Armitage (5 mins)
-------------------------------------------

* Phil: anybody here interested in FreeBSD stuff (no hands)

* Phil: how much does the current version implement?

* Grenville: the URL on slides will describe the features

-- Meeting concluded at 11:15 --




Philip Eardley
Research and Innovation
This email contains BT information, which may be privileged or confidential=
. It's meant only for the individual(s) or entity named above. If you're no=
t the intended recipient, note that disclosing, copying, distributing or us=
ing this information is prohibited. If you've received this email in error,=
 please let me know immediately on the email address above. Thank you.
We monitor our email system, and may record your emails.
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no: 1800000


--_000_ec7b8d4172ad4835b556fa582c806917rew09926dag03bdomain1sy_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.author-a-z81zz84z299z69znkykz87zz71zsz122zz122z9
	{mso-style-name:author-a-z81zz84z299z69znkykz87zz71zsz122zz122z9;}
span.author-a-c73z73zz80zz81zz83z2z85zz82zl54cz82zz65z
	{mso-style-name:author-a-c73z73zz80zz81zz83z2z85zz82zl54cz82zz65z;}
.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=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Her=
e are the draft minutes for the WG meeting on Monday. Please let us know of=
 any corrections.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Man=
y thanks to Pasi and Alan for taking the notes
<o:p></o:p></span></p>
<div style=3D"mso-element:para-border-div;border:none;border-bottom:solid w=
indowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class=3D"MsoNormal" style=3D"line-height:12.0pt;border:none;padding:0cm"=
><span style=3D"font-size:9.0pt;font-family:&quot;Courier New&quot;;mso-far=
east-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Mul=
tipath TCP (MPTCP)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Dra=
ft agenda Date: Monday, November 2, 2015, 9:00 - 11:30 (Morning Session I)<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Roo=
m: 413<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Tak=
ing notes: Pasi Sarolahti<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">- I=
ntro - Chairs [15mins]<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
----------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* S=
tatus Updates<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* D=
iscussion on interim meeting output and other progression between meetings:=
 E.g. increasing version number, which opens possibility
 to redesign signaling<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hairs: Realistic to last call before next IETF?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph Paasch: depending on how much we change the spec, it may be diffic=
ult to get done by next IETF, but will try to do
 that<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* S=
haoib Rao: why decided to drop implementation advice?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil Eardly: Implementation People thought that the protocol documentation w=
as sufficient<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Shaoib Rao: why do we support both 8-byte and 4-byte fields? why do we want=
 to support 4 bytes?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Yoshi Nishida: already discussed and consensus-called before<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Christoph: good point, people would not switch to 8 bytes, but will be long=
er discussion to change this. Linux implementation
 support receiving both variants, but never sends 8 bytes<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Shaoib Rao: If timestamp option is mandatory, we would not need 8 bytes<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Alan Ford: we would not need to use timestamp option with 8-byte option, bu=
t some people might have other uses. Linux does
 not need to send both if it can accept. If we only support 8 bytes, what p=
roblem would it solve? makes simpler implementation, but it is only optiona=
l to implement<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Christoph: decission can be triggered by application based on envrionment<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Shaoib Rao: receiver should need to support both variants always.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Shaoib: what is the motivation for 4 bytes?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Alan: saving option space<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Shaoib: Header option placement is also problematic, alignment is important=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Alan: space constraints are problem<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Chistoph: implementation choice, can place options otherwise<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Yoshi: making 8 bytes mandatory, 4 bytes optional, would that make people h=
appy?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Alan: that's basically what we already have. If we spell out more explictly=
 that sending is optional and receiving mandatory,
 would you be happier? Conclusion: nothing fundamentally changes, but we sp=
ell out more clearly in the draft that sending is optional<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Imp=
lementation updates:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">** =
Shaoib: implementing MPTCP in Solaris kernel, seems to be working well<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">- M=
aking Multipath TCP robust for stateless webservers - Christoph Paasch (10 =
mins)&nbsp;&nbsp;&nbsp; (draft-paasch-mptcp-syncookies)<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
---------------------------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">(go=
ing through slides)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Yos=
hi: implementation status?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Chr=
istoph: no implementation yet<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Phi=
l: any implementation plans in Louvain?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Fab=
ien Duch=EAne: no plans for implementation at Louvain yet<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Sha=
oib: can try to implement but can't estimate when? Seems very complicated b=
ut does seem necessary. Yes, seems relevant.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Phi=
l: this would not be backward compatible<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Ala=
n: yes this is v1, not v0. Earlier you did not need to put key in data ACK,=
 now you do need keys in data-ack<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Ala=
n: would love to get consensus on this, so that we can work forward<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Phi=
l: plan to give it a week or two, then do an explicit consensus call<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">- R=
eflecting on the MPTCP handshake&quot; - Christoph Paasch (20 mins)<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">(dr=
aft-paasch-mptcp-loadbalancer &#43; security)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
-----------------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* S=
haoib (on deployment behind L4 loadbalancers): question about currently dep=
loyed solution (missed)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph (answering): Netscaler is L7 load balancer, terminates connections=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* (=
missed Alan's question/comment)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* Y=
oshi: is token used only for server?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: use is to identify the MPTCP connection, for single server this w=
orks well<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* Y=
oshi: you want to change meaning only for one use case?<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: increasing information that the token carries<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* A=
lan: to summarize: you want to decouple token from key. makes lot of sense,=
 seems fine. from signaling point of view: have
 flag to get key form external source, to say that key comes from TLS or so=
mewhere else. Logical extension to what we got. Earlier we completely ran o=
ut of option space when trying to do this. Maybe we should wait for TCPINC,=
 to see if they give some additional
 tools<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: worried about TCPINC, not sure how quick they are going to procee=
d.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: we should be able to finish our work earlier<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* A=
lan: this does not need to be part of base v1 spec, but additional mechanis=
m.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: can live very well with the TLS, but getting locally meaningful t=
oken would be a big issue.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: are the two issues (loadbalancers, security) totally separable issues?=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: need to make token meaningful<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* A=
lan: TLS is a potential solution to the problem<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: might we just decrease the size of the keys, they are already sen=
t in the clear. Are there any MPTCP deployments
 that are not using TLS, and think seeing keys in clear is fine.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* A=
lan: our goal has never been to provide secure solution, but something equi=
valent to TCP.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* A=
lan: this should be specified in a separate draft, at least initially... co=
ncerned that this is a distraction, makes a jump
 away from where we are.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: can we try to see whether we want to solve one of those issues?<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: comments? personally think the datacenter case is important to solve. =
Should be designing for the present, not the future.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: do you think it is worthwhile to have draft to support discussion=
?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* Y=
oshi: yes<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: wider issue: should there be more flexibility about the security solut=
ion?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* A=
lan: we already have that kind of flexibility, haven't yet specified what t=
he negotiation means. Would need to work through
 the details.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* D=
aniel Giffin: Both main TCPINC have been adopted to specify the negotiation=
 of encryption protocol, also uses session ID (TCP-ENO),
 you might find that is useful.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: We are deferring key exchange until after the SYN, could do it al=
ready in SYN, maybe this would make it simpler in
 terms of signaling.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil's conclusion: make a draft about the possible solution space<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">- M=
ptcp enduser use cases and enhancement opportunities - Chetan Harsha&nbsp;&=
nbsp; (20 mins)&nbsp;&nbsp; (draft-palanivelanchetansenthil-mptcp-enhanceme=
nts)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
--------------------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: is it separate TCP connections when MPTCP is disabled (about slid=
e on upload latency graph, with number of subflows)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hetan: yes<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* Y=
oshi: why the red line behaves so differently with ups and downs?<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">(so=
me discussion clarifying the graphs)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: interested in hearing about protocol tweaks you might suggest?<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hetan: not sure yet what the changes could be, currently just some paramete=
rs<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: there is generally need for more signaling in MPTCP, to indicate =
subflow characteristics, to help scheduling traffic,
 but it is a bigger change is protocol.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* D=
avid Allan: if you are going to depend a lot on end-user signaling, makes l=
ife difficult for proxies.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* S=
haoib: performance depends also on scheduler, that's why MPTCP results diff=
er.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">- L=
ISA: A Linked Slow-Start Algorithm for MPTCP&nbsp; - Runa Barik&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (20 mins)&nbsp;&nbsp;&nbsp; (dra=
ft-barik-mptcp-lisa)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
-------------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* Y=
oshi: if bottleneck is not shared, we don't have to use slow-start?<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* R=
una: we are reducing latency in non-shared scenario also. Some differences =
are explained that paths are both 3G or WiFi.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">(so=
me additional discussion clarifying the results)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* I=
lpo J=E4rvinen: not sure why number of retransmissions affects the way you =
say<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* R=
una: because of slow-start loss it is explained, not understanding Ilpo's p=
oint<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: could be nice to see the patch and paper traces.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* R=
una: will do, but currently a paper in submission.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: hard to understand<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* M=
ichio Honda: your point that slowing down slow start will reduce retransmis=
sions, does not work in large delay-bw environments.
 Should see graphs relating to BDP. Current parameters are unrealistic.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Man=
agement information base for MPTCP - Fabien Duch=EAne(15 mins)<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">(dr=
aft-duchene-mptcp-mib-00)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
---------------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* S=
haoib: thank you, this is very useful. One thing missing: what are the comb=
inations of the flows supporting MPTCP vs. TCP.
 Port numbers, addresses as well.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* F=
abien: will look at them, because wanted to keep it simple, might be gettin=
g complicated, but is interesting<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: good to have more feedback<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* Y=
oshi: question to AD: when we define MIB, do we need cross-area review?<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* M=
artin Stiemerling: should get MIB doctor review, might be useful to ask the=
m when you have stable version, but before WGLC.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: should it be WG document before doing it? A: yes.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: plan to make this WG document before the next IETF<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">Phi=
l: Update of Louvain Linux implementation? in terms of getting to mainline =
kernel<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* F=
abien: Nothing much to report<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* C=
hristoph: there are lot of users, but no contributions that come back<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">MPT=
CP for FreeBSD update&nbsp; - Grenville Armitage (5 mins)<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">---=
----------------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: anybody here interested in FreeBSD stuff (no hands)<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* P=
hil: how much does the current version implement?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">* G=
renville: the URL on slides will describe the features<o:p></o:p></span></p=
>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB">-- =
Meeting concluded at 11:15 --<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt"><span style=3D"font-siz=
e:9.0pt;font-family:&quot;Courier New&quot;;mso-fareast-language:EN-GB"><o:=
p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN" style=3D"mso-fareast-language:EN-GB">Philip Eard=
ley<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN" style=3D"mso-fareast-language:EN-GB">Research an=
d Innovation<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN" style=3D"mso-fareast-language:EN-GB">This email =
contains BT information, which may be privileged or confidential. It's mean=
t only for the individual(s) or entity named
 above. If you're not the intended recipient, note that disclosing, copying=
, distributing or using this information is prohibited. If you've received =
this email in error, please let me know immediately on the email address ab=
ove. Thank you.<br>
We monitor our email system, and may record your emails.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN" style=3D"mso-fareast-language:EN-GB">British Tel=
ecommunications plc<br>
Registered office: 81 Newgate Street London EC1A 7AJ<br>
Registered in England no: 1800000<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_ec7b8d4172ad4835b556fa582c806917rew09926dag03bdomain1sy_--


From nobody Mon Nov  9 23:04:09 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF7E1B3402 for <multipathtcp@ietfa.amsl.com>; Mon,  9 Nov 2015 23:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfUKRHs_Ig-r for <multipathtcp@ietfa.amsl.com>; Mon,  9 Nov 2015 23:04:06 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34CF81B3401 for <multipathtcp@ietf.org>; Mon,  9 Nov 2015 23:04:06 -0800 (PST)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 851332AC5B1 for <multipathtcp@ietf.org>; Tue, 10 Nov 2015 08:04:04 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.32]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 5C5C5158072 for <multipathtcp@ietf.org>; Tue, 10 Nov 2015 08:04:04 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0248.002; Tue, 10 Nov 2015 08:04:04 +0100
From: <mohamed.boucadair@orange.com>
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4QAf1LWA
Date: Tue, 10 Nov 2015 07:04:03 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9ACA1@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com>
In-Reply-To: <D2660C4C.7A833%dan.seibel@telus.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.10.16.122716
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/a9_IoLMur7R-D9LZQz_VNRW2K14>
Subject: [multipathtcp] TR: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 07:04:08 -0000

Dear all,

I'm forwarding this review from the DHC working group. The full thread is a=
vailable at: https://mailarchive.ietf.org/arch/search/?email_list=3Ddhcwg=20

Your feedback is more than welcome.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dan Seibel [mailto:Dan.Seibel@TELUS.COM]
> Envoy=E9=A0: lundi 9 novembre 2015 16:51
> =C0=A0: BOUCADAIR Mohamed IMT/OLN; dhcwg@ietf.org
> Objet=A0: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>=20
> I think your document gives a good overall impression of how this will
> work (having no experience with MPTCP implementations I found this fairly
> easy to follow).
>=20
> A few questions:
>=20
> - in sections 4.2 you mention a client requests this option, but does it
> have to?  I.e could a server send this option without the client
> requesting it, and the client would still accept it? (should there be a
> MUST or SHOULD statement in there?)
>=20
> - similarly, in section 5 I don=B9t see any mention of if the server need=
s
> to see a request for this option to hand it out.
>=20
>=20
>=20
>=20
>=20
> On 2015-11-05, 8:19 AM, "dhcwg on behalf of mohamed.boucadair@orange.com"
> <dhcwg-bounces@ietf.org on behalf of mohamed.boucadair@orange.com> wrote:
>=20
> >Dear all,
> >
> >Comments are more than welcome.
> >
> >Cheers,
> >Med
> >
> >> -----Message d'origine-----
> >> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >> Envoy=E9 : jeudi 5 novembre 2015 16:19
> >> =C0 : BOUCADAIR Mohamed IMT/OLN; Tirumaleswar Reddy; JACQUENET Christi=
an
> >> IMT/OLN
> >> Objet : New Version Notification for draft-boucadair-mptcp-dhc-02.txt
> >>
> >>
> >> A new version of I-D, draft-boucadair-mptcp-dhc-02.txt
> >> has been successfully submitted by Mohamed Boucadair and posted to the
> >> IETF repository.
> >>
> >> Name:		draft-boucadair-mptcp-dhc
> >> Revision:	02
> >> Title:		DHCP Options for Network-Assisted Multipath TCP (MPTCP)
> >> Document date:	2015-11-05
> >> Group:		Individual Submission
> >> Pages:		11
> >> URL:            https://www.ietf.org/internet-drafts/draft-boucadair-
> >> mptcp-dhc-02.txt
> >> Status:         https://datatracker.ietf.org/doc/draft-boucadair-mptcp=
-
> >> dhc/
> >> Htmlized:       https://tools.ietf.org/html/draft-boucadair-mptcp-dhc-
> 02
> >> Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-
> mptcp-
> >> dhc-02
> >>
> >> Abstract:
> >>    One of the promising deployment scenarios for Multipath TCP (MPTCP)
> >>    is to enable a Customer Premises Equipment (CPE) that is connected
> to
> >>    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of
> its
> >>    network attachments.  Because of the lack of MPTCP support at the
> >>    server side, some service providers consider a network-assisted
> model
> >>    that relies upon the activation of a dedicated function called:
> MPTCP
> >>    Concentrator.
> >>
> >>    This document focuses on the explicit deployment scheme where the
> >>    identity of the MPTCP Concentrator(s) is explicitly configured on
> >>    connected hosts.  This document specifies DHCP (IPv4 and IPv6)
> >>    options to configure hosts with Multipath TCP (MPTCP) parameters.
> >>
> >>
> >>
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of
> >> submission
> >> until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> The IETF Secretariat
> >
> >_______________________________________________
> >dhcwg mailing list
> >dhcwg@ietf.org
> >https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Nov 12 05:00:27 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91C411A8894; Thu, 12 Nov 2015 05:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WiT-04ik5Pc; Thu, 12 Nov 2015 05:00:22 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F029A1A8890; Thu, 12 Nov 2015 05:00:18 -0800 (PST)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 32ECC3741C8; Thu, 12 Nov 2015 14:00:17 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.61]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id 12C5A180059; Thu, 12 Nov 2015 14:00:17 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7E.corporate.adroot.infra.ftgroup ([fe80::b91c:ea2c:ac8a:7462%19]) with mapi id 14.03.0248.002; Thu, 12 Nov 2015 14:00:16 +0100
From: <mohamed.boucadair@orange.com>
To: Simon Hobson <linux@thehobsons.co.uk>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AQHRG9LloIa0MQcdN0KDD9p3IjCBh56YUoWg
Date: Thu, 12 Nov 2015 13:00:16 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9BA1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>
In-Reply-To: <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.12.122417
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/2XLGXiKuBRRpKSrmFwU8RVdYZvo>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "draft-boucadair-mptcp-dhc@ietf.org" <draft-boucadair-mptcp-dhc@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 13:00:24 -0000

Hi Simon,

(adding mptcp to the discussion)

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De=A0: dhcwg [mailto:dhcwg-bounces@ietf.org] De la part de Simon Hobson
> Envoy=E9=A0: mardi 10 novembre 2015 17:14
> =C0=A0: dhcwg@ietf.org
> Objet=A0: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>=20
> mohamed.boucadair@orange.com wrote:
>=20
> > But, in addition to updating the client's behavior so that it must be
> prepared to receive the option even if it didn't requested for it
>=20
> I think the specific use case was that the client is expecting it, but
> just doesn't ask for it.

[Med] Agree on the use case. BTW, this is governed by the following:=20

https://tools.ietf.org/html/rfc7227#section-19:=20

"  For some options, such as the options required for the functioning of
   DHCPv6 itself, it doesn't make sense to require that they be
   explicitly requested using the Option Request Option.  In all other
   cases, it is prudent to assume that any new option must be present on
   the relevant option request list if the client desires to receive it."

and https://tools.ietf.org/html/rfc7227#section-21: =20

"As a convenience to the reader, we
   mention here that the server will send option foo only if configured
   with specific values for foo and if the client requested it."

My initial comment was: if we allow the server to return an option a client=
 didn't asked for, we need to add a sentence like this one in the client's =
behavior section:

"The DHCP client MUST be prepared to receive the DHCP MPTCP Concentrator
   Option even if it didn't include it in the request."

(I do personally think this adds extra complexity without any guarantee tha=
t a broken implementation will make use of an option it didn't asked for).

 I'm no expert user, but I have come across stuff
> where a vendor has built server and client, and makes the two work
> together - but not in a standards compliant way. Since in some cases the
> vendor has zero interest in working with anything but an "all mine and
> nothing else" network environment, they may have no interest in fixing a
> client that is broken according to the standards, but which is working
> with their server which is also non-standards compliant in a way that
> makes the pair work together.
>=20

[Med] That's the point. Does it really matter to have a "SHOULD NOT" instea=
d of "MUST NOT" if the standard behavior will be broken anyway?

> > ... the server must support a logic to decide which clients should be
> supplied with the mptcp option.
>=20
> Typically that would be done by the admin, classifying the clients by som=
e
> means, and then overriding the requested parameter list. This is certainl=
y
> possible with the ISC server.

[Med] Yes; that's implementation-specific. My point is not about "how" but =
that the sever should be able to do that using "some means".=20

>=20
> I can't remember what it was for (it was a good few years ago with a
> different hat on), but I know I've had to provide an option list override
> for a problematic client in the past - it was most likely a done by addin=
g
> it to a "host" declaration with the ISC server.
>=20
> > Although I understand the arguments you raised, I'm not convinced the
> text should be relaxed.
>=20
> As Niall points out, it prohibits an admin faced with a broken client fro=
m
> working around the issue.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Nov 12 05:24:13 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F378A1A8954; Thu, 12 Nov 2015 05:24:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srRQQZL-J4oi; Thu, 12 Nov 2015 05:24:07 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 495791A8953; Thu, 12 Nov 2015 05:24:07 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 0BE1F3B4170; Thu, 12 Nov 2015 14:24:06 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.24]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id E15CCC8020; Thu, 12 Nov 2015 14:24:05 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7D.corporate.adroot.infra.ftgroup ([fe80::9044:c5ee:4dd2:4f16%19]) with mapi id 14.03.0248.002; Thu, 12 Nov 2015 14:24:05 +0100
From: <mohamed.boucadair@orange.com>
To: Niall O'Reilly <niall.oreilly@ucd.ie>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AQHRG9BsoIa0MQcdN0KDD9p3IjCBh56YXylg
Date: Thu, 12 Nov 2015 13:24:04 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9BA7C@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2lha5g858.wl-Niall.oReilly@ucd.ie>
In-Reply-To: <m2lha5g858.wl-Niall.oReilly@ucd.ie>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.12.111517
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/MzXRoULA_ciEKm-GboYzIj-nl7E>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, Simon Hobson <linux@thehobsons.co.uk>, "draft-boucadair-mptcp-dhc@ietf.org" <draft-boucadair-mptcp-dhc@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 13:24:09 -0000

SGkgTmlhbGwsDQoNCldlIGFyZSBub3QgdHJ5aW5nIHRvIG1ha2UgdGhlIHNwZWNpZmljYXRpb24g
InBlcmZlY3QiLi4ud2UgYXJlIGRvaW5nIG91ciBiZXN0IHRvIGZvbGxvdyBkaGMgZ3VpZGVsaW5l
cyAocmZjNzIyNywgaW4gcGFydGljdWxhcikuIA0KDQpDaGVlcnMsDQpNZWQNCg0KPiAtLS0tLU1l
c3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGXCoDogTmlhbGwgTydSZWlsbHkgW21haWx0bzpuaWFs
bC5vcmVpbGx5QHVjZC5pZV0NCj4gRW52b3nDqcKgOiBtYXJkaSAxMCBub3ZlbWJyZSAyMDE1IDE2
OjU3DQo+IMOAwqA6IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE4NCj4gQ2PCoDogU2ltb24gSG9i
c29uOyBkaGN3Z0BpZXRmLm9yZw0KPiBPYmpldMKgOiBSZTogW2RoY3dnXSBESENQIE9wdGlvbnMg
Zm9yIE5ldHdvcmstQXNzaXN0ZWQgTXVsdGlwYXRoIFRDUA0KPiAoTVBUQ1ApDQo+IA0KPiBPbiBU
dWUsIDEwIE5vdiAyMDE1IDE0OjM0OjAyICswMDAwLA0KPiA8bW9oYW1lZC5ib3VjYWRhaXJAb3Jh
bmdlLmNvbT4gd3JvdGU6DQo+ID4NCj4gPiBBbHRob3VnaCBJIHVuZGVyc3RhbmQgdGhlIGFyZ3Vt
ZW50cyB5b3UgcmFpc2VkLCBJJ20gbm90IGNvbnZpbmNlZA0KPiA+IHRoZSB0ZXh0IHNob3VsZCBi
ZSByZWxheGVkLg0KPiANCj4gICBJIGJlbGlldmUgdGhhdCwgYXMgaXQgc3RhbmRzLCB0aGUgdGV4
dCBjb25zdHJhaW5zIHVuZHVseSB0aGUNCj4gICBkaXNjcmV0aW9uIG9mIHRoZSBvcGVyYXRvciB0
byBjb25maWd1cmUgdGhlIHNlcnZlciB0byBhY2NvbW1vZGF0ZQ0KPiAgIGEgYnJva2VuIGNsaWVu
dCB3aG9zZSByZXBhaXIgY2Fubm90IHByYWN0aWNhbGx5IGJlIGVmZmVjdGVkLg0KPiANCj4gICBP
cGVyYXRpb25hbGx5LCB0aGlzIGlzIGxpa2VseSB0byBjYXVzZSBhIHBhaW4gaW4gdGhlIHByb3Zl
cmJpYWxzLg0KPiAgIFBsZWFzZSBzZWUgaHR0cHM6Ly9mci53aWtpc291cmNlLm9yZy93aWtpL0xh
X0IlQzMlQTlndWV1bGUNCj4gDQo+ICAgQmVzdCByZWdhcmRzLA0KPiAgIE5pYWxsIE8nUmVpbGx5
DQo+IA0K


From nobody Thu Nov 12 05:28:19 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 494B21A8955; Thu, 12 Nov 2015 05:28:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blNdzLwXPBVW; Thu, 12 Nov 2015 05:28:11 -0800 (PST)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B3241A896D; Thu, 12 Nov 2015 05:28:11 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 7FE4BC0130; Thu, 12 Nov 2015 14:28:09 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.69]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 4DBE21A0054; Thu, 12 Nov 2015 14:28:09 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%19]) with mapi id 14.03.0248.002; Thu, 12 Nov 2015 14:28:09 +0100
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AQHRG9LloIa0MQcdN0KDD9p3IjCBh56YUoWggAANzoiAAAJK8A==
Date: Thu, 12 Nov 2015 13:28:08 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9BA96@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>, <787AE7BB302AE849A7480A190F8B933008C9BA1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0705B986-C01F-49E8-AD15-14C7D14C74BD@cisco.com>
In-Reply-To: <0705B986-C01F-49E8-AD15-14C7D14C74BD@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933008C9BA96OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/3ck0l9rli6uIHOMnN8W2-NuidHU>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, Simon Hobson <linux@thehobsons.co.uk>, "draft-boucadair-mptcp-dhc@ietf.org" <draft-boucadair-mptcp-dhc@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 13:28:16 -0000

--_000_787AE7BB302AE849A7480A190F8B933008C9BA96OPEXCLILMA3corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Bernie,

I'm on the same page as you.

The proposed text was to explicitly show to Simon the complexity induced by=
 the request to handle broken implementations.

FWIW, the latest version of the draft is available at: https://tools.ietf.o=
rg/html/draft-boucadair-mptcp-dhc-03

Cheers,
Med

De : Bernie Volz (volz) [mailto:volz@cisco.com]
Envoy=E9 : jeudi 12 novembre 2015 14:14
=C0 : BOUCADAIR Mohamed IMT/OLN
Cc : Simon Hobson; dhcwg@ietf.org; multipathtcp@ietf.org; draft-boucadair-m=
ptcp-dhc@ietf.org
Objet : Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)

Please don't over specify this.

If client wants option it MUST request it in the ORO / PRL. End of story.

Note that clients may receive options they didn't ask for (perhaps ones the=
y don't even know) and proper action is to ignore those.

It also makes little sense for a client not to ask for something it support=
s (except in cases where it is being asked (by an application?) to get some=
thing (via Information-Request/Inform) that it didn't request in the past).

What does a statement like the following mean?

"The DHCP client MUST be prepared to receive the DHCP MPTCP Concentrator
  Option even if it didn't include it in the request."

What is "prepared"? Again, client should always be "prepared" to receive an=
y option - that may just mean ignoring it.

We are working to update RFC3315bis text to clarify that clients and server=
s must be capable of receiving any option - but will ignore those that they=
 do not care about or know about.

We really want "other configuration" options documents to say very little a=
bout option processing. State that client MUST include in ORO/PRL to have a=
ny chance to receive it.

- Bernie (from iPad)

On Nov 12, 2015, at 8:00 AM, "mohamed.boucadair@orange.com<mailto:mohamed.b=
oucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucadai=
r@orange.com>> wrote:
Hi Simon,

(adding mptcp to the discussion)

Please see inline.

Cheers,
Med


-----Message d'origine-----
De : dhcwg [mailto:dhcwg-bounces@ietf.org] De la part de Simon Hobson
Envoy=E9 : mardi 10 novembre 2015 17:14
=C0 : dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
(MPTCP)

mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:

But, in addition to updating the client's behavior so that it must be
prepared to receive the option even if it didn't requested for it

I think the specific use case was that the client is expecting it, but
just doesn't ask for it.

[Med] Agree on the use case. BTW, this is governed by the following:

https://tools.ietf.org/html/rfc7227#section-19:

"  For some options, such as the options required for the functioning of
  DHCPv6 itself, it doesn't make sense to require that they be
  explicitly requested using the Option Request Option.  In all other
  cases, it is prudent to assume that any new option must be present on
  the relevant option request list if the client desires to receive it."

and https://tools.ietf.org/html/rfc7227#section-21:

"As a convenience to the reader, we
  mention here that the server will send option foo only if configured
  with specific values for foo and if the client requested it."

My initial comment was: if we allow the server to return an option a client=
 didn't asked for, we need to add a sentence like this one in the client's =
behavior section:

"The DHCP client MUST be prepared to receive the DHCP MPTCP Concentrator
  Option even if it didn't include it in the request."

(I do personally think this adds extra complexity without any guarantee tha=
t a broken implementation will make use of an option it didn't asked for).

I'm no expert user, but I have come across stuff

where a vendor has built server and client, and makes the two work
together - but not in a standards compliant way. Since in some cases the
vendor has zero interest in working with anything but an "all mine and
nothing else" network environment, they may have no interest in fixing a
client that is broken according to the standards, but which is working
with their server which is also non-standards compliant in a way that
makes the pair work together.


[Med] That's the point. Does it really matter to have a "SHOULD NOT" instea=
d of "MUST NOT" if the standard behavior will be broken anyway?


... the server must support a logic to decide which clients should be
supplied with the mptcp option.

Typically that would be done by the admin, classifying the clients by some
means, and then overriding the requested parameter list. This is certainly
possible with the ISC server.

[Med] Yes; that's implementation-specific. My point is not about "how" but =
that the sever should be able to do that using "some means".



I can't remember what it was for (it was a good few years ago with a
different hat on), but I know I've had to provide an option list override
for a problematic client in the past - it was most likely a done by adding
it to a "host" declaration with the ISC server.

Although I understand the arguments you raised, I'm not convinced the
text should be relaxed.

As Niall points out, it prohibits an admin faced with a broken client from
working around the issue.

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

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

--_000_787AE7BB302AE849A7480A190F8B933008C9BA96OPEXCLILMA3corp_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft 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:12.0pt;
	font-family:"Times New Roman","serif";}
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:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Bernie,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I&#8217;m on the same page as y=
ou.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">The proposed text was to explic=
itly show to Simon the complexity induced by the request to handle broken i=
mplementations.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">FWIW, the latest version of the=
 draft is available at:
<a href=3D"https://tools.ietf.org/html/draft-boucadair-mptcp-dhc-03">https:=
//tools.ietf.org/html/draft-boucadair-mptcp-dhc-03</a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><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 class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bern=
ie Volz (volz) [mailto:volz@cisco.com]
<br>
<b>Envoy=E9&nbsp;:</b> jeudi 12 novembre 2015 14:14<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc&nbsp;:</b> Simon Hobson; dhcwg@ietf.org; multipathtcp@ietf.org; draft=
-boucadair-mptcp-dhc@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [dhcwg] DHCP Options for Network-Assisted Multipath=
 TCP (MPTCP)<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Please don't over specify this.<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">If client wants option it MUST request it in the ORO=
 / PRL. End of story.<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">Note that clients may receive options they didn't as=
k for (perhaps ones they don't even know) and proper action is to ignore th=
ose.<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">It also makes little sense for a client not to ask f=
or something it supports (except in cases where it is being asked (by an ap=
plication?) to get something (via Information-Request/Inform) that it didn'=
t request in the past).<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">What does a statement like the following mean?<o:p><=
/o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><span style=3D"color:black">&quot;The DHCP client MU=
ST be prepared to receive the DHCP MPTCP Concentrator<br>
&nbsp;&nbsp;Option even if it didn't include it in the request.&quot;</span=
><o:p></o:p></p>
</blockquote>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">What is &quot;prepared&quot;? Again, client should a=
lways be &quot;prepared&quot; to receive any option - that may just mean ig=
noring it.<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">We are working to update RFC3315bis text to clarify =
that clients and servers must be capable of receiving any option - but will=
 ignore those that they do not care about or know about.<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal">We really want &quot;other configuration&quot; optio=
ns documents to say very little about option processing. State that client =
MUST include in ORO/PRL to have any chance to receive it.<o:p></o:p></p>
</div>
<div id=3D"AppleMailSignature">
<p class=3D"MsoNormal"><br>
- Bernie (from iPad)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Nov 12, 2015, at 8:00 AM, &quot;<a href=3D"mailto:mohamed.boucadair@oran=
ge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:mohame=
d.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<o:p></o=
:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Hi Simon,<br>
<br>
(adding mptcp to the discussion)<br>
<br>
Please see inline.<br>
<br>
Cheers,<br>
Med<br>
<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">-----Message d'origine-----<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">De&nbsp;: dhcwg [<a href=3D"mailto:dhcwg-bounces@iet=
f.org">mailto:dhcwg-bounces@ietf.org</a>] De la part de Simon Hobson<o:p></=
o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Envoy=E9&nbsp;: mardi 10 novembre 2015 17:14<o:p></o=
:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">=C0&nbsp;: <a href=3D"mailto:dhcwg@ietf.org">dhcwg@i=
etf.org</a><o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Objet&nbsp;: Re: [dhcwg] DHCP Options for Network-As=
sisted Multipath TCP<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">(MPTCP)<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><a href=3D"mailto:mohamed.boucadair@orange.com">moha=
med.boucadair@orange.com</a> wrote:<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">But, in addition to updating the client's behavior s=
o that it must be<o:p></o:p></p>
</blockquote>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">prepared to receive the option even if it didn't req=
uested for it<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">I think the specific use case was that the client is=
 expecting it, but<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">just doesn't ask for it.<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
[Med] Agree on the use case. BTW, this is governed by the following: <br>
<br>
<a href=3D"https://tools.ietf.org/html/rfc7227#section-19:">https://tools.i=
etf.org/html/rfc7227#section-19:</a>
<br>
<br>
&quot; &nbsp;For some options, such as the options required for the functio=
ning of<br>
&nbsp;&nbsp;DHCPv6 itself, it doesn't make sense to require that they be<br=
>
&nbsp;&nbsp;explicitly requested using the Option Request Option. &nbsp;In =
all other<br>
&nbsp;&nbsp;cases, it is prudent to assume that any new option must be pres=
ent on<br>
&nbsp;&nbsp;the relevant option request list if the client desires to recei=
ve it.&quot;<br>
<br>
and <a href=3D"https://tools.ietf.org/html/rfc7227#section-21:">https://too=
ls.ietf.org/html/rfc7227#section-21:</a> &nbsp;<br>
<br>
&quot;As a convenience to the reader, we<br>
&nbsp;&nbsp;mention here that the server will send option foo only if confi=
gured<br>
&nbsp;&nbsp;with specific values for foo and if the client requested it.&qu=
ot;<br>
<br>
My initial comment was: if we allow the server to return an option a client=
 didn't asked for, we need to add a sentence like this one in the client's =
behavior section:<br>
<br>
&quot;The DHCP client MUST be prepared to receive the DHCP MPTCP Concentrat=
or<br>
&nbsp;&nbsp;Option even if it didn't include it in the request.&quot;<br>
<br>
(I do personally think this adds extra complexity without any guarantee tha=
t a broken implementation will make use of an option it didn't asked for).<=
br>
<br>
I'm no expert user, but I have come across stuff<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">where a vendor has built server and client, and make=
s the two work<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">together - but not in a standards compliant way. Sin=
ce in some cases the<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">vendor has zero interest in working with anything bu=
t an &quot;all mine and<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">nothing else&quot; network environment, they may hav=
e no interest in fixing a<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">client that is broken according to the standards, bu=
t which is working<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">with their server which is also non-standards compli=
ant in a way that<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">makes the pair work together.<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
[Med] That's the point. Does it really matter to have a &quot;SHOULD NOT&qu=
ot; instead of &quot;MUST NOT&quot; if the standard behavior will be broken=
 anyway?<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">... the server must support a logic to decide which =
clients should be<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">supplied with the mptcp option.<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Typically that would be done by the admin, classifyi=
ng the clients by some<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">means, and then overriding the requested parameter l=
ist. This is certainly<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">possible with the ISC server.<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
[Med] Yes; that's implementation-specific. My point is not about &quot;how&=
quot; but that the sever should be able to do that using &quot;some means&q=
uot;.
<br>
<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">I can't remember what it was for (it was a good few =
years ago with a<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">different hat on), but I know I've had to provide an=
 option list override<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">for a problematic client in the past - it was most l=
ikely a done by adding<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">it to a &quot;host&quot; declaration with the ISC se=
rver.<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Although I understand the arguments you raised, I'm =
not convinced the<o:p></o:p></p>
</blockquote>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">text should be relaxed.<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">As Niall points out, it prohibits an admin faced wit=
h a broken client from<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">working around the issue.<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">_______________________________________________<o:p>=
</o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">dhcwg mailing list<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>=
<o:p></o:p></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><a href=3D"https://www.ietf.org/mailman/listinfo/dhc=
wg">https://www.ietf.org/mailman/listinfo/dhcwg</a><o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg">https://www.ietf.or=
g/mailman/listinfo/dhcwg</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B933008C9BA96OPEXCLILMA3corp_--


From nobody Thu Nov 12 05:37:19 2015
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0181F1A89B9 for <multipathtcp@ietfa.amsl.com>; Thu, 12 Nov 2015 05:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLlVNn3A8sXx for <multipathtcp@ietfa.amsl.com>; Thu, 12 Nov 2015 05:37:15 -0800 (PST)
Received: from smtp6.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id ABD8B1A89B5 for <multipathtcp@ietf.org>; Thu, 12 Nov 2015 05:37:15 -0800 (PST)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.16]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp6.sgsi.ucl.ac.be) by smtp6.sgsi.ucl.ac.be (Postfix) with ESMTPSA id CC555183434; Thu, 12 Nov 2015 14:37:09 +0100 (CET)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp6.sgsi.ucl.ac.be CC555183434
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1447335429; bh=VD0AjfvTwR53NiIofkL8IHHReaLbMC57aZ1d3+sNzDo=; h=Reply-To:Subject:References:To:Cc:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=F1i8EO1oFRr29aTPi9BpcXgdAd9xsmEduvnfa0iN4vLnmLn2+dH/pKoQLNgjzI4NQ uHgWbpZvbHrlSxo9LBrgetkwDWifM8/OdHnJyHPjJuygDjZIrDSGfNilCxzzKY/WD/ Rfm9D4y6rhqJX/jX4grRN4XyoXx5FoyjwwQ4TMAg=
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <56449606.9030106@uclouvain.be>
Date: Thu, 12 Nov 2015 14:37:10 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99-beta1 at smtp-6.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: CC555183434.A2CD2
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/xw4hNzNJAcrchDOVNlI4zpBf5C4>
Cc: "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 13:37:18 -0000

Med,
>
> This is an update to a proposal that intends to avoid requiring an extra encapsulating scheme between a CPE and an MPTCP Concentrator located in the provider's network.

This is an extension of the solution proposed earlier in
http://inl.info.ucl.ac.be/publications/multipath-middlebox

Do you have any implementation results that demonstrate the feasibility 
of the proposed approach ?

> The document suggests also relaying UDP packets into TCP-formatted packets in the CPE-Concentrator leg. Some features may be disabled/enabled at the CPE/Concentrator when processing UDP packets.

I'm not sure I understand why you want to map UDP packets into 
TCP-formatted packets. What is the benefit of having a 20 bytes header 
in front of UDP packets (maybe less if you apply a solution like
https://tools.ietf.org/html/draft-denis-udp-transport-00) ?

Do you plan to send SYN/SYN+ACK before the first packet of a flow and 
FIN/RST after ?


Olivier



From nobody Thu Nov 12 06:00:39 2015
Return-Path: <volz@cisco.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E57D1A88A7; Thu, 12 Nov 2015 05:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gIPaPBQDPjR; Thu, 12 Nov 2015 05:13:58 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 806131A889C; Thu, 12 Nov 2015 05:13:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15857; q=dns/txt; s=iport; t=1447334038; x=1448543638; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=WL/3yCUtzTA5fFtm61SpxtDAOUTaq65tCWuARHqOpEg=; b=TGEA/UgMPW2egfLsX2E8lyEWVDUKyvn1a+Pg7eUnmXlDOqOkngFGlLYz s1eXgXhdj6Hdqp53FuM/ggRmKDbwcjbjs5w3rd5lVHAAbtCVHEjnsL+H/ BAR2jpeDFPu/u06jlrLsb8/sbmvWw262OawFD5z58aNqCs0zgqnnPAbC7 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D8AQCMj0RW/5JdJa1egztTb74/AQ2BZRcBCYVvAoEwOBQBAQEBAQEBfwuENQEBBAEBAWgDCxACAQg/BycLFBECBA4FiC4Nw20BAQEBAQEBAQEBAQEBAQEBAQEBAQEUBIhkgm6EQkaDHIEVBY1UhRODYQGFHGmHIYFbhECNVohTAR8BAUKEBHKFPQEBAQ
X-IronPort-AV: E=Sophos;i="5.20,281,1444694400";  d="scan'208,217";a="206844332"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-4.cisco.com with ESMTP; 12 Nov 2015 13:13:57 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id tACDDv0J005606 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 12 Nov 2015 13:13:57 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 12 Nov 2015 07:13:56 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1104.000; Thu, 12 Nov 2015 07:13:56 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AQHRG9Llbwftk3lYQ+2W8C9ebSXh4Z6YUoWggAANzog=
Date: Thu, 12 Nov 2015 13:13:56 +0000
Message-ID: <0705B986-C01F-49E8-AD15-14C7D14C74BD@cisco.com>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>, <787AE7BB302AE849A7480A190F8B933008C9BA1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008C9BA1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_0705B986C01F49E8AD1514C7D14C74BDciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/2ESP-E53obkrI-AUDwlehxi-fkE>
X-Mailman-Approved-At: Thu, 12 Nov 2015 06:00:35 -0800
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, Simon Hobson <linux@thehobsons.co.uk>, "draft-boucadair-mptcp-dhc@ietf.org" <draft-boucadair-mptcp-dhc@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 13:14:01 -0000

--_000_0705B986C01F49E8AD1514C7D14C74BDciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Please don't over specify this.

If client wants option it MUST request it in the ORO / PRL. End of story.

Note that clients may receive options they didn't ask for (perhaps ones the=
y don't even know) and proper action is to ignore those.

It also makes little sense for a client not to ask for something it support=
s (except in cases where it is being asked (by an application?) to get some=
thing (via Information-Request/Inform) that it didn't request in the past).

What does a statement like the following mean?

"The DHCP client MUST be prepared to receive the DHCP MPTCP Concentrator
  Option even if it didn't include it in the request."

What is "prepared"? Again, client should always be "prepared" to receive an=
y option - that may just mean ignoring it.

We are working to update RFC3315bis text to clarify that clients and server=
s must be capable of receiving any option - but will ignore those that they=
 do not care about or know about.

We really want "other configuration" options documents to say very little a=
bout option processing. State that client MUST include in ORO/PRL to have a=
ny chance to receive it.

- Bernie (from iPad)

On Nov 12, 2015, at 8:00 AM, "mohamed.boucadair@orange.com<mailto:mohamed.b=
oucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.boucadai=
r@orange.com>> wrote:

Hi Simon,

(adding mptcp to the discussion)

Please see inline.

Cheers,
Med

-----Message d'origine-----
De : dhcwg [mailto:dhcwg-bounces@ietf.org] De la part de Simon Hobson
Envoy=E9 : mardi 10 novembre 2015 17:14
=C0 : dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Objet : Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
(MPTCP)

mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:

But, in addition to updating the client's behavior so that it must be
prepared to receive the option even if it didn't requested for it

I think the specific use case was that the client is expecting it, but
just doesn't ask for it.

[Med] Agree on the use case. BTW, this is governed by the following:

https://tools.ietf.org/html/rfc7227#section-19:

"  For some options, such as the options required for the functioning of
  DHCPv6 itself, it doesn't make sense to require that they be
  explicitly requested using the Option Request Option.  In all other
  cases, it is prudent to assume that any new option must be present on
  the relevant option request list if the client desires to receive it."

and https://tools.ietf.org/html/rfc7227#section-21:

"As a convenience to the reader, we
  mention here that the server will send option foo only if configured
  with specific values for foo and if the client requested it."

My initial comment was: if we allow the server to return an option a client=
 didn't asked for, we need to add a sentence like this one in the client's =
behavior section:

"The DHCP client MUST be prepared to receive the DHCP MPTCP Concentrator
  Option even if it didn't include it in the request."

(I do personally think this adds extra complexity without any guarantee tha=
t a broken implementation will make use of an option it didn't asked for).

I'm no expert user, but I have come across stuff
where a vendor has built server and client, and makes the two work
together - but not in a standards compliant way. Since in some cases the
vendor has zero interest in working with anything but an "all mine and
nothing else" network environment, they may have no interest in fixing a
client that is broken according to the standards, but which is working
with their server which is also non-standards compliant in a way that
makes the pair work together.


[Med] That's the point. Does it really matter to have a "SHOULD NOT" instea=
d of "MUST NOT" if the standard behavior will be broken anyway?

... the server must support a logic to decide which clients should be
supplied with the mptcp option.

Typically that would be done by the admin, classifying the clients by some
means, and then overriding the requested parameter list. This is certainly
possible with the ISC server.

[Med] Yes; that's implementation-specific. My point is not about "how" but =
that the sever should be able to do that using "some means".


I can't remember what it was for (it was a good few years ago with a
different hat on), but I know I've had to provide an option list override
for a problematic client in the past - it was most likely a done by adding
it to a "host" declaration with the ISC server.

Although I understand the arguments you raised, I'm not convinced the
text should be relaxed.

As Niall points out, it prohibits an admin faced with a broken client from
working around the issue.

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

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

--_000_0705B986C01F49E8AD1514C7D14C74BDciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body dir=3D"auto">
<div>Please don't over specify this.</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">If client wants option it MUST request it in=
 the ORO / PRL. End of story.</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">Note that clients may receive options they d=
idn't ask for (perhaps ones they don't even know) and proper action is to i=
gnore those.</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">It also makes little sense for a client not =
to ask for something it supports (except in cases where it is being asked (=
by an application?) to get something (via Information-Request/Inform) that =
it didn't request in the past).</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">What does a statement like the following mea=
n?</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">
<blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"background=
-color: rgba(255, 255, 255, 0);">&quot;The DHCP client MUST be prepared to =
receive the DHCP MPTCP Concentrator<br>
&nbsp;&nbsp;Option even if it didn't include it in the request.&quot;</span=
></font></blockquote>
</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">What is &quot;prepared&quot;? Again, client =
should always be &quot;prepared&quot; to receive any option - that may just=
 mean ignoring it.</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">We are working to update RFC3315bis text to =
clarify that clients and servers must be capable of receiving any option - =
but will ignore those that they do not care about or know about.</div>
<div id=3D"AppleMailSignature"><br>
</div>
<div id=3D"AppleMailSignature">We really want &quot;other configuration&quo=
t; options documents to say very little about option processing. State that=
 client MUST include in ORO/PRL to have any chance to receive it.</div>
<div id=3D"AppleMailSignature"><br>
- Bernie (from iPad)</div>
<div><br>
On Nov 12, 2015, at 8:00 AM, &quot;<a href=3D"mailto:mohamed.boucadair@oran=
ge.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:mohame=
d.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><span>Hi Simon,</span><br>
<span></span><br>
<span>(adding mptcp to the discussion)</span><br>
<span></span><br>
<span>Please see inline.</span><br>
<span></span><br>
<span>Cheers,</span><br>
<span>Med</span><br>
<span></span><br>
<blockquote type=3D"cite"><span>-----Message d'origine-----</span><br>
</blockquote>
<blockquote type=3D"cite"><span>De&nbsp;: dhcwg [<a href=3D"mailto:dhcwg-bo=
unces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>] De la part de Simon Hobs=
on</span><br>
</blockquote>
<blockquote type=3D"cite"><span>Envoy=E9&nbsp;: mardi 10 novembre 2015 17:1=
4</span><br>
</blockquote>
<blockquote type=3D"cite"><span>=C0&nbsp;: <a href=3D"mailto:dhcwg@ietf.org=
">dhcwg@ietf.org</a></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Objet&nbsp;: Re: [dhcwg] DHCP Options for N=
etwork-Assisted Multipath TCP</span><br>
</blockquote>
<blockquote type=3D"cite"><span>(MPTCP)</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"mailto:mohamed.boucadair@orange.=
com">mohamed.boucadair@orange.com</a> wrote:</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>But, in addition to updating the client's b=
ehavior so that it must be</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite"><span>prepared to receive the option even if it d=
idn't requested for it</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>I think the specific use case was that the =
client is expecting it, but</span><br>
</blockquote>
<blockquote type=3D"cite"><span>just doesn't ask for it.</span><br>
</blockquote>
<span></span><br>
<span>[Med] Agree on the use case. BTW, this is governed by the following: =
</span>
<br>
<span></span><br>
<span><a href=3D"https://tools.ietf.org/html/rfc7227#section-19:">https://t=
ools.ietf.org/html/rfc7227#section-19:</a>
</span><br>
<span></span><br>
<span>&quot; &nbsp;For some options, such as the options required for the f=
unctioning of</span><br>
<span>&nbsp;&nbsp;DHCPv6 itself, it doesn't make sense to require that they=
 be</span><br>
<span>&nbsp;&nbsp;explicitly requested using the Option Request Option. &nb=
sp;In all other</span><br>
<span>&nbsp;&nbsp;cases, it is prudent to assume that any new option must b=
e present on</span><br>
<span>&nbsp;&nbsp;the relevant option request list if the client desires to=
 receive it.&quot;</span><br>
<span></span><br>
<span>and <a href=3D"https://tools.ietf.org/html/rfc7227#section-21:">https=
://tools.ietf.org/html/rfc7227#section-21:</a> &nbsp;</span><br>
<span></span><br>
<span>&quot;As a convenience to the reader, we</span><br>
<span>&nbsp;&nbsp;mention here that the server will send option foo only if=
 configured</span><br>
<span>&nbsp;&nbsp;with specific values for foo and if the client requested =
it.&quot;</span><br>
<span></span><br>
<span>My initial comment was: if we allow the server to return an option a =
client didn't asked for, we need to add a sentence like this one in the cli=
ent's behavior section:</span><br>
<span></span><br>
<span>&quot;The DHCP client MUST be prepared to receive the DHCP MPTCP Conc=
entrator</span><br>
<span>&nbsp;&nbsp;Option even if it didn't include it in the request.&quot;=
</span><br>
<span></span><br>
<span>(I do personally think this adds extra complexity without any guarant=
ee that a broken implementation will make use of an option it didn't asked =
for).</span><br>
<span></span><br>
<span>I'm no expert user, but I have come across stuff</span><br>
<blockquote type=3D"cite"><span>where a vendor has built server and client,=
 and makes the two work</span><br>
</blockquote>
<blockquote type=3D"cite"><span>together - but not in a standards compliant=
 way. Since in some cases the</span><br>
</blockquote>
<blockquote type=3D"cite"><span>vendor has zero interest in working with an=
ything but an &quot;all mine and</span><br>
</blockquote>
<blockquote type=3D"cite"><span>nothing else&quot; network environment, the=
y may have no interest in fixing a</span><br>
</blockquote>
<blockquote type=3D"cite"><span>client that is broken according to the stan=
dards, but which is working</span><br>
</blockquote>
<blockquote type=3D"cite"><span>with their server which is also non-standar=
ds compliant in a way that</span><br>
</blockquote>
<blockquote type=3D"cite"><span>makes the pair work together.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<span></span><br>
<span>[Med] That's the point. Does it really matter to have a &quot;SHOULD =
NOT&quot; instead of &quot;MUST NOT&quot; if the standard behavior will be =
broken anyway?</span><br>
<span></span><br>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>... the server must support a logic to deci=
de which clients should be</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite"><span>supplied with the mptcp option.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Typically that would be done by the admin, =
classifying the clients by some</span><br>
</blockquote>
<blockquote type=3D"cite"><span>means, and then overriding the requested pa=
rameter list. This is certainly</span><br>
</blockquote>
<blockquote type=3D"cite"><span>possible with the ISC server.</span><br>
</blockquote>
<span></span><br>
<span>[Med] Yes; that's implementation-specific. My point is not about &quo=
t;how&quot; but that the sever should be able to do that using &quot;some m=
eans&quot;.
</span><br>
<span></span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>I can't remember what it was for (it was a =
good few years ago with a</span><br>
</blockquote>
<blockquote type=3D"cite"><span>different hat on), but I know I've had to p=
rovide an option list override</span><br>
</blockquote>
<blockquote type=3D"cite"><span>for a problematic client in the past - it w=
as most likely a done by adding</span><br>
</blockquote>
<blockquote type=3D"cite"><span>it to a &quot;host&quot; declaration with t=
he ISC server.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Although I understand the arguments you rai=
sed, I'm not convinced the</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite"><span>text should be relaxed.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>As Niall points out, it prohibits an admin =
faced with a broken client from</span><br>
</blockquote>
<blockquote type=3D"cite"><span>working around the issue.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>___________________________________________=
____</span><br>
</blockquote>
<blockquote type=3D"cite"><span>dhcwg mailing list</span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"mailto:dhcwg@ietf.org">dhcwg@iet=
f.org</a></span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"https://www.ietf.org/mailman/lis=
tinfo/dhcwg">https://www.ietf.org/mailman/listinfo/dhcwg</a></span><br>
</blockquote>
<span></span><br>
<span>_______________________________________________</span><br>
<span>dhcwg mailing list</span><br>
<span><a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg">https://www.i=
etf.org/mailman/listinfo/dhcwg</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_0705B986C01F49E8AD1514C7D14C74BDciscocom_--


From nobody Thu Nov 12 06:03:31 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B201A9177 for <multipathtcp@ietfa.amsl.com>; Thu, 12 Nov 2015 06:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4bTVlGSnRzH for <multipathtcp@ietfa.amsl.com>; Thu, 12 Nov 2015 06:03:28 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DEBE1A914E for <multipathtcp@ietf.org>; Thu, 12 Nov 2015 06:03:24 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id B173022C41C; Thu, 12 Nov 2015 15:03:22 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.75]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 8F59827C053; Thu, 12 Nov 2015 15:03:22 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%19]) with mapi id 14.03.0248.002; Thu, 12 Nov 2015 15:03:22 +0100
From: <mohamed.boucadair@orange.com>
To: "Olivier.Bonaventure@uclouvain.be" <Olivier.Bonaventure@uclouvain.be>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
Thread-Index: AQHRHU8/CdM7cujz+kS67VTMKL4kHp6YZx3Q
Date: Thu, 12 Nov 2015 14:03:21 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9BB1A@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <56449606.9030106@uclouvain.be>
In-Reply-To: <56449606.9030106@uclouvain.be>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.12.132415
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/DVYS1o0rKnnRBPds4KElwC8lxLE>
Cc: Stefano SECCI <stefano.secci@lip6.fr>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 14:03:30 -0000

Hi Olivier,=20

Thank you for the feedback.=20

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De=A0: Olivier Bonaventure [mailto:Olivier.Bonaventure@uclouvain.be]
> Envoy=E9=A0: jeudi 12 novembre 2015 14:37
> =C0=A0: BOUCADAIR Mohamed IMT/OLN; multipathtcp@ietf.org
> Cc=A0: Denis Behaghel (Denis.Behaghel@oneaccess-net.com)
> (Denis.Behaghel@oneaccess-net.com)
> Objet=A0: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-
> mode-03.txt
>=20
> Med,
> >
> > This is an update to a proposal that intends to avoid requiring an extr=
a
> encapsulating scheme between a CPE and an MPTCP Concentrator located in
> the provider's network.
>=20
> This is an extension of the solution proposed earlier in
> http://inl.info.ucl.ac.be/publications/multipath-middlebox

[Med] Thank you for sharing the pointer. I will look at that document.=20

>=20
> Do you have any implementation results that demonstrate the feasibility
> of the proposed approach ?

[Med] We are planning to have one or two implementations that follow this s=
pecification. We will share the results once available.=20

>=20
> > The document suggests also relaying UDP packets into TCP-formatted
> packets in the CPE-Concentrator leg. Some features may be disabled/enable=
d
> at the CPE/Concentrator when processing UDP packets.
>=20
> I'm not sure I understand why you want to map UDP packets into
> TCP-formatted packets.

[Med] The benefit is to reuse at maximum the same functional blocks for han=
dling both TCP and UDP traffic. Some specific TCP features may be enabled/d=
isabled when handling the UDP traffic; this is deployment-specific. If tunn=
eling is enabled for UDP, then there is no point to avoid it for TCP.

 What is the benefit of having a 20 bytes header
> in front of UDP packets (maybe less if you apply a solution like
> https://tools.ietf.org/html/draft-denis-udp-transport-00) ?

[Med] I'm not aware of that draft. Will look at it.

>=20
> Do you plan to send SYN/SYN+ACK before the first packet of a flow and
> FIN/RST after ?

[Med] No. The plan is to maintain the sessions used to transport udp packet=
s open so that there is 0-RTT for relaying UDP packets.=20

>=20
>=20
> Olivier
>=20


From nobody Thu Nov 12 06:32:32 2015
Return-Path: <linux@thehobsons.co.uk>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C01171B2EB4; Thu, 12 Nov 2015 06:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrNmua9mKi6t; Thu, 12 Nov 2015 06:24:00 -0800 (PST)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [81.174.135.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7292C1B2EAC; Thu, 12 Nov 2015 06:24:00 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 302FB1BC65; Thu, 12 Nov 2015 14:23:55 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008C9BA96@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Date: Thu, 12 Nov 2015 14:23:53 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E745D70-F0BA-42E2-B8BF-E281DEED19A6@thehobsons.co.uk>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>, <787AE7BB302AE849A7480A190F8B933008C9BA1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0705B986-C01F-49E8-AD15-14C7D14C74BD@cisco.com> <787AE7BB302AE849A7480A190F8B933008C9BA96@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
To: multipathtcp@ietf.org, "dhcwg@ietf.org" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/WEPJ9sLpF17wZfW2sY-UDeC76P0>
X-Mailman-Approved-At: Thu, 12 Nov 2015 06:32:32 -0800
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 14:24:02 -0000

mohamed.boucadair@orange.com wrote:

> The proposed text was to explicitly show to Simon the complexity =
induced by the request to handle broken implementations.

Which IMO you failed to do.

If a client receives an option that it doesn't know what to do with - it =
is already required to ignore it. As Bernie points out, you do not need =
to specify that as that's already "standard requirement" for all =
options.
You also don't need to specify that the client must request it - that =
too is standard requirement.

The suggestion was simply that you change one instance of "must not" to =
"should not".
In the ideal world, no client would ever want an option but not request =
it - "should not" is sufficient instruction for a normal server, serving =
a normal client, with nothing broken, to not send the option if not =
requested.

But in the non-ideal world, sometimes the admin needs to override the =
strictly correct operation so as to deal with something that isn't =
completely ideal. Stating "must not" precludes the admin from working =
around a problem, and technically means an implementation must prevent =
him from trying*. In the real world there are broken things we can't fix =
- only work around the broken bits.

You don't need to specify any mechanism for that, you don't even need to =
reference the possibility - just don't prohibit it. So the sole change =
required is to change "must" to "should" in one place.

* If the server "must not" send an option the client didn't ask for, =
then strictly speaking, an implementation "must not" have a means for =
the admin to override that parameter list.


From nobody Thu Nov 12 07:09:46 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A03E1ACD90; Thu, 12 Nov 2015 07:09:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tx6Pa323qk91; Thu, 12 Nov 2015 07:09:43 -0800 (PST)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCC891ACD8E; Thu, 12 Nov 2015 07:09:40 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 338C8402F3; Thu, 12 Nov 2015 16:09:39 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.75]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 0853C1A0056; Thu, 12 Nov 2015 16:09:39 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe%19]) with mapi id 14.03.0248.002; Thu, 12 Nov 2015 16:09:38 +0100
From: <mohamed.boucadair@orange.com>
To: Simon Hobson <linux@thehobsons.co.uk>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AQHRHVXLu5Q2PNkW5Uy2kMuw8b3YvZ6Yc/NA
Date: Thu, 12 Nov 2015 15:09:38 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9BBB0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>, <787AE7BB302AE849A7480A190F8B933008C9BA1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0705B986-C01F-49E8-AD15-14C7D14C74BD@cisco.com> <787AE7BB302AE849A7480A190F8B933008C9BA96@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <5E745D70-F0BA-42E2-B8BF-E281DEED19A6@thehobsons.co.uk>
In-Reply-To: <5E745D70-F0BA-42E2-B8BF-E281DEED19A6@thehobsons.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/7pZ9Rt8ZUOc-DmaFBBHTjCCYiBI>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 15:09:45 -0000

Re-,

The change you asked for is as follows:=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
OLD:
   The DHCP server MUST NOT reply with the DHCP MPTCP Concentrator
   option unless the client has explicitly requested for it.

NEW:
   The DHCP server SHOULD NOT reply with the DHCP MPTCP Concentrator
   option unless the client has explicitly requested for it.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Comments from the wg about this change is welcome.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: dhcwg [mailto:dhcwg-bounces@ietf.org] De la part de Simon Hobson
> Envoy=E9=A0: jeudi 12 novembre 2015 15:24
> =C0=A0: multipathtcp@ietf.org; dhcwg@ietf.org
> Objet=A0: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>=20
> mohamed.boucadair@orange.com wrote:
>=20
> > The proposed text was to explicitly show to Simon the complexity induce=
d
> by the request to handle broken implementations.
>=20
> Which IMO you failed to do.
>=20
> If a client receives an option that it doesn't know what to do with - it
> is already required to ignore it. As Bernie points out, you do not need t=
o
> specify that as that's already "standard requirement" for all options.
> You also don't need to specify that the client must request it - that too
> is standard requirement.
>=20
> The suggestion was simply that you change one instance of "must not" to
> "should not".
> In the ideal world, no client would ever want an option but not request i=
t
> - "should not" is sufficient instruction for a normal server, serving a
> normal client, with nothing broken, to not send the option if not
> requested.
>=20
> But in the non-ideal world, sometimes the admin needs to override the
> strictly correct operation so as to deal with something that isn't
> completely ideal. Stating "must not" precludes the admin from working
> around a problem, and technically means an implementation must prevent hi=
m
> from trying*. In the real world there are broken things we can't fix -
> only work around the broken bits.
>=20
> You don't need to specify any mechanism for that, you don't even need to
> reference the possibility - just don't prohibit it. So the sole change
> required is to change "must" to "should" in one place.
>=20
> * If the server "must not" send an option the client didn't ask for, then
> strictly speaking, an implementation "must not" have a means for the admi=
n
> to override that parameter list.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Fri Nov 13 10:09:41 2015
Return-Path: <niall.oreilly@ucd.ie>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9E221B2A84 for <multipathtcp@ietfa.amsl.com>; Fri, 13 Nov 2015 08:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PA0pocGQHp7b for <multipathtcp@ietfa.amsl.com>; Fri, 13 Nov 2015 08:48:48 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AF5D1B2A8A for <multipathtcp@ietf.org>; Fri, 13 Nov 2015 08:48:45 -0800 (PST)
Received: by wmww144 with SMTP id w144so38711471wmw.0 for <multipathtcp@ietf.org>; Fri, 13 Nov 2015 08:48:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucd_ie.20150623.gappssmtp.com; s=20150623; h=from:date:message-id:to:cc:subject:in-reply-to:references :user-agent:mime-version:content-type:content-transfer-encoding; bh=RNBjiTrGJ+m1bFdxFVMnGcwAQudhyVR7kc/lC3rwgc4=; b=Muahr1i0ARAm4caLKkr2HYGj318XX7uqFlQd+WV2RUtiVXrbsilwJvoORW5NovFWFF DYbN3klgcH0lVGDCOn/Hoka7OmIVSJfxPA6j9z5wb3kmR5JkzLKX0JmzXM1zrk/hB+WW WbTVmppB0ZLZG4GT7HBSyLDtVXvJ8hGA610ouHAp7tJNcIXUrnoF0TPDmJAobecbkz7s 7wo+PDmf1LLzFogYxltmd+SYOXw1PYHTY/+bzetSyFrwN5kH5XJEG4+/4+bC4ZwUBtbi ZZ3KSHVkGo35I7O4vPuAXfXDo3b0oVr14xvHSV97dcuvpPiPmEp2oEyOqevkE1JnXGRU Z4cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:message-id:to:cc:subject:in-reply-to :references:user-agent:mime-version:content-type :content-transfer-encoding; bh=RNBjiTrGJ+m1bFdxFVMnGcwAQudhyVR7kc/lC3rwgc4=; b=cDQBrVccvwQJCSUWfEYGf1ZX9oPZnz4/gxuuwHy5qRshvMQ3gWMV2Mo19tfWx5lE/1 jSbi6LI6rGdM0s6VuN2NUJOSaDL2j+5awHz8lrL3tTLpTaF5MpSR18EfgRinBMtDQf8L xDXqaCsA+NfoR1uf9QSY9FkopFRu4hyWZtjPKbD2Y0IJyhv587C6e4K9ouMYDW86ZDs0 miMqOuFgDY6QexN/oDtyrZAxvfl6Br+qvvQfyMw0w5GPsVlWmLE2V0e5cDXxmhv7BohD i5CBCfA2Zq/FrUqPXYo+fFYZgcpORCAhh6o7xHWyNcuhtuWx/ubnD9t54K7+Z34Oayo8 epXQ==
X-Gm-Message-State: ALoCoQkIvRe73I1AjQPOBbvB6jQUEumO5aN34uP+zWKa5ZxrDHWqYXCj6h5YLBOJ8X+nX5ag7prc
X-Received: by 10.28.4.212 with SMTP id 203mr5136800wme.89.1447433324156; Fri, 13 Nov 2015 08:48:44 -0800 (PST)
Received: from 162.1.0.10.in-addr.no8.be.ucd.ie ([2001:770:13f:1:5ac:2c7b:3101:2934]) by smtp.gmail.com with ESMTPSA id pc2sm20661070wjb.11.2015.11.13.08.48.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Nov 2015 08:48:43 -0800 (PST)
From: "Niall O'Reilly" <niall.oreilly@ucd.ie>
X-Google-Original-From: Niall O'Reilly <Niall.oReilly@ucd.ie>
Date: Fri, 13 Nov 2015 16:48:42 +0000
Message-ID: <m237w9g80l.wl-Niall.oReilly@ucd.ie>
To: <mohamed.boucadair@orange.com>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008C9BBB0@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/Mv-t0Vnq0eN01pXhxa3oWclQTw8>
X-Mailman-Approved-At: Fri, 13 Nov 2015 10:09:39 -0800
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, Simon Hobson <linux@thehobsons.co.uk>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2015 16:48:50 -0000

On Thu, 12 Nov 2015 15:09:38 +0000,
<mohamed.boucadair@orange.com> wrote:
>=20
> Re-,
>=20
> The change you asked for is as follows:=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> OLD:
>    The DHCP server MUST NOT reply with the DHCP MPTCP Concentrator
>    option unless the client has explicitly requested for it.
>=20
> NEW:
>    The DHCP server SHOULD NOT reply with the DHCP MPTCP Concentrator
>    option unless the client has explicitly requested for it.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Comments from the wg about this change is welcome.=20

  Yes, please!  I think Simon has explained the need already.

  Best regards,
  Niall O'Reilly
 =20


From nobody Sun Nov 15 18:23:17 2015
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD31D1B2A03 for <multipathtcp@ietfa.amsl.com>; Sun, 15 Nov 2015 18:23:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhtohRsoRwkh for <multipathtcp@ietfa.amsl.com>; Sun, 15 Nov 2015 18:23:14 -0800 (PST)
Received: from mail-in7.apple.com (mail-out7.apple.com [17.151.62.29]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD0531B2A0C for <multipathtcp@ietf.org>; Sun, 15 Nov 2015 18:23:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple;  q=dns/txt; i=@apple.com; t=1447640591; x=2311554191; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Tt4KJ5oA7O505Si494kuA1HfgldDpdVVH6u/Use1IqA=; b=VcPiJzfvw0TuyGoiA40f8XKBDrB+2NGwgbo0wOH/NFx86MpVJUcTl5O9Yrt1JYNd ICE326WqWBV/yRFCwBuUdzub9vRwIzTJ4YyrKNCiiK/P/NJdXYVPixlJdrpubqqt /nBa+LwP4JNrxdM3eSA1lBl0letffKZ7gwTNy4m13cf8Ijake3Vpnxj3saphb3vI 3RjKqo/6VLK7O8qIlbZ3BswVkyQuIST0DZsxaxZ73F+BDYEpYHPlC0zEPQe3yFqN qzVHwWbHi5ELSQ54LTDlbnfqgH2SBHeYHwSrRneGEPkelGZh4zVNcv6kjI0MLvB5 rB1LBi4xaZ19vBedDsouIg==;
Received: from relay6.apple.com (relay6.apple.com [17.128.113.90]) by mail-in7.apple.com (Apple Secure Mail Relay) with SMTP id C6.5E.27014.F0E39465; Sun, 15 Nov 2015 18:23:11 -0800 (PST)
X-AuditID: 11973e16-f793c6d000006986-81-56493e0f6fbd
Received: from chicory.apple.com (chicory.apple.com [17.128.115.99]) (using TLS with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay6.apple.com (Apple SCV relay) with SMTP id 4B.BE.29392.F0E39465; Sun, 15 Nov 2015 18:23:11 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=iso-8859-1
Received: from localhost ([17.153.85.111]) by chicory.apple.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NXV00MTAYMNUA10@chicory.apple.com> for multipathtcp@ietf.org; Sun, 15 Nov 2015 18:23:11 -0800 (PST)
Sender: cpaasch@apple.com
Date: Sun, 15 Nov 2015 18:23:10 -0800
From: Christoph Paasch <cpaasch@apple.com>
To: mohamed.boucadair@orange.com
Message-id: <20151116022310.GI49988@da0602a-dhcp129.apple.com>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-reply-to: <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
User-Agent: Mutt/1.5.24 (08e81162482f) (2015-08-30)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUi2FAYpctv5xlm8HKmtcXn1dfZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMXPFG/aCd0oVL/ceZGtg3CbdxcjJISFgItG9/xkjhC0mceHe erYuRi4OIYG9jBJb9rxnhClqbP0AlZjFJDHh0g4WkASvgKDEj8n3gGwODmYBeYkjl7JBwswC 0hKP/s5gh7B1JHq/f2OG6O1kkmiYNokNJCEsICnRfecOM4jNIqAq8eV6MxOIzSagJfH2djsr iC0ioCCxr62fBaSZWWATo8T0PbNYIJpDJX7eP8cKcYSdxNr9k1kgNkxllHj3YgfYak6BBInd 08+CNYgKGEs0HZkDdoaEwA42idcnpzFNYBSdheSLWQhfzELyxSwkXyxgZFnFKJSbmJmjm5ln rpdYUJCTqpecn7uJERQT0+3EdjA+XGV1iFGAg1GJh/fEE/cwIdbEsuLK3EOM0hwsSuK8Fvvd woQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwbu5PfPF909ak+CjeH1J+rtpsc0xyXLInfPux 1ePKyqVrjH1OOq+zNGroFK67cK7ge80D7wkloncMfzCuKckPWK0ToeP1ao6fi2dj58XT7rG/ 3MxV+wVkjQxUrJq2HHiTe/BaC7f/ihzPAuH9PEl3VxpGRv/M8E5kmBDUKm5rnH5tHquycKkS S3FGoqEWc1FxIgDBSZAzagIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUi2FCcrMtv5xlmsGqthcXn1dfZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMXPFG/aCd0oVL/ceZGtg3CbdxcjJISFgItHY+oENwhaTuHBv PZDNxSEkMItJYsKlHSwgCV4BQYkfk+8B2RwczALyEkcuZYOEmQWkJR79ncEOYetI9H7/xgzR 28kk0TBtEthQYQFJie47d5hBbBYBVYkv15uZQGw2AS2Jt7fbWUFsEQEFiX1t/SwgzcwCmxgl pu+ZxQLRHCrx8/45Vogj7CTW7p/MArFhKqPEuxc7wFZzCiRI7J5+FqxBVMBYounIHOYJjEKz kBw+C+HwWUgOn4Xk8AWMLKsYBYpScxIrzfQSCwpyUvWS83M3MYJDuDBqB2PDcqtDjAIcjEo8 vArP3cOEWBPLiitzDzFKcDArifD+YPEME+JNSaysSi3Kjy8qzUktPsSYDPTxRGYp0eR8YHzl lcQbmpgYmBgbmxkbm5uYkyasJM67wNctTEggPbEkNTs1tSC1CGYLEwenVANjZ3/8jPIdLs/r DX+aHlGeYyR28mbEybjtp1Qna/Aln7hoox+1oOPaxYS1q43Pb46+qO0y5/Skz/31Oi+ylPwL VQ5MnKC506lgP9ORRqfn1xLmzZddv7JxUqHwFfkjTN8uZwi9sjQu/W1jec/6wOPNDyq9rgp8 XVmpK6lxcOsvze6/kno63aE9SizFGYmGWsxFxYkAFLMoSaUCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/pzYfCb0U9q8xjOZvgCHTGVmjd-Y>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 02:23:16 -0000

Hello Mohamed,


I tried to understand the draft, but it's not yet clear to me how the
proxying would work.

Am I right that the draft is proposing a scheme where the Proxies (CPE and
concentrator) are not terminating the TCP-connections?
If that's the case, I am wondering how the TCP sequence numbers are being
handled end-to-end (from the client's device to the server).

Further, it seems to me that the assumption is that MPTCP guarantees the
message-boundaries, because the Plain Mode MPTCP option is put on a
per-segment basis. However, MPTCP cannot guarantee that those message
boundaries are respected.
In my opinion, Plain Mode MPTCP's option belongs into the payload. So,
basically, this would be multistreaming (e.g., HTTP/2-style) on top of a
reliable transport like MPTCP.


Cheers,
Christoph


On 05/11/15 - 13:45:41, mohamed.boucadair@orange.com wrote:
> This is an update to a proposal that intends to avoid requiring an extra encapsulating scheme between a CPE and an MPTCP Concentrator located in the provider's network. 
> 
> The document suggests also relaying UDP packets into TCP-formatted packets in the CPE-Concentrator leg. Some features may be disabled/enabled at the CPE/Concentrator when processing UDP packets.
> 
> The main motivation is to ease integrating an MPTCP Concentrator into an operational network without requiring updating intermediate service functions to support another yet encapsulation scheme.
> 
> Comments are more than welcome. 
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> > internet-drafts@ietf.org
> > Envoyé : jeudi 5 novembre 2015 14:33
> > À : i-d-announce@ietf.org
> > Objet : I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
> > 
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > 
> > 
> >         Title           : An MPTCP Option for Network-Assisted MPTCP
> > Deployments: Plain Transport Mode
> >         Authors         : Mohamed Boucadair
> >                           Christian Jacquenet
> >                           Denis Behaghel
> >                           Stefano Secci
> > 	Filename        : draft-boucadair-mptcp-plain-mode-03.txt
> > 	Pages           : 14
> > 	Date            : 2015-11-05
> > 
> > Abstract:
> >    One of the promising deployment scenarios for Multipath TCP (MPTCP)
> >    is to enable a Customer Premises Equipment (CPE) that is connected to
> >    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of its
> >    network attachments.  Because of the lack of MPTCP support at the
> >    server side, some service providers now consider a network-assisted
> >    model that relies upon the activation of a dedicated function called
> >    MPTCP Concentrator.  This document focuses on a deployment scheme
> >    where the identity of the MPTCP Concentrator(s) is explicitly
> >    configured on connected hosts.
> > 
> >    This document specifies an MPTCP option that is used to avoid an
> >    encapsulation scheme between the CPE and the MPTCP Concentrator.
> >    Also, this document specifies how UDP traffic can be distributed
> >    among available paths without requiring any encapsulation scheme.
> > 
> > 
> > 
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-plain-mode/
> > 
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-boucadair-mptcp-plain-mode-03
> > 
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-boucadair-mptcp-plain-mode-03
> > 
> > 
> > Please note that it may take a couple of minutes from the time of
> > submission
> > until the htmlized version and diff are available at tools.ietf.org.
> > 
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > 
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Mon Nov 16 03:15:31 2015
Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8331A1B1C for <multipathtcp@ietfa.amsl.com>; Mon, 16 Nov 2015 03:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.486
X-Spam-Level: 
X-Spam-Status: No, score=-7.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dseCcr633Yvb for <multipathtcp@ietfa.amsl.com>; Mon, 16 Nov 2015 03:15:27 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1986C1A1B1B for <multipathtcp@ietf.org>; Mon, 16 Nov 2015 03:15:26 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 5465ED5287A13; Mon, 16 Nov 2015 11:15:22 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id tAGBFMQ9018106 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Nov 2015 12:15:23 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.17]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Mon, 16 Nov 2015 12:15:22 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: Christoph Paasch <cpaasch@apple.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
Thread-Index: AQHRIBXHBkXGX/O0xU2YYw+O5JGB+Z6d6R0A
Date: Mon, 16 Nov 2015 11:15:21 +0000
Message-ID: <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com>
In-Reply-To: <20151116022310.GI49988@da0602a-dhcp129.apple.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.151008
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="utf-8"
Content-ID: <2B233A1F52ADBF45AF535E3E2B75B02F@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/LdZH3wIl5nwanLOOvqYyA_IKWEw>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 11:15:29 -0000

Q2hyaXN0b3BoLCBteSAyIGNlbnRzOg0KLSBUaGUgcHJvcG9zYWwgdGVybWluYXRlcyB0aGUgc2Vx
dWVuY2UgbnVtYmVycyBhbmQgcHJvdmlkZXMgYSB0cnVlIHByb3h5IGFuZCBoZW5jZSByZXdyaXRl
cyB0aGUgc2VxdWVuY2UgbnVtYmVycyBhdCB0aGUgcHJveHkgcG9pbnRzLg0KLSBJIGFtIG5vdCBz
dXJlIHdoYXQgeW91IG1lYW4gd2l0aCB0aGUgbWVzc2FnZSBib3VuZGFyaWVzLiBDYW4geW91IGNs
YXJpZnk/DQoNCg0KDQoNCk9uIDE1LzExLzE1IDE4OjIzLCAibXVsdGlwYXRodGNwIG9uIGJlaGFs
ZiBvZiBDaHJpc3RvcGggUGFhc2NoIiA8bXVsdGlwYXRodGNwLWJvdW5jZXNAaWV0Zi5vcmcgb24g
YmVoYWxmIG9mIGNwYWFzY2hAYXBwbGUuY29tPiB3cm90ZToNCg0KPkhlbGxvIE1vaGFtZWQsDQo+
DQo+DQo+SSB0cmllZCB0byB1bmRlcnN0YW5kIHRoZSBkcmFmdCwgYnV0IGl0J3Mgbm90IHlldCBj
bGVhciB0byBtZSBob3cgdGhlDQo+cHJveHlpbmcgd291bGQgd29yay4NCj4NCj5BbSBJIHJpZ2h0
IHRoYXQgdGhlIGRyYWZ0IGlzIHByb3Bvc2luZyBhIHNjaGVtZSB3aGVyZSB0aGUgUHJveGllcyAo
Q1BFIGFuZA0KPmNvbmNlbnRyYXRvcikgYXJlIG5vdCB0ZXJtaW5hdGluZyB0aGUgVENQLWNvbm5l
Y3Rpb25zPw0KPklmIHRoYXQncyB0aGUgY2FzZSwgSSBhbSB3b25kZXJpbmcgaG93IHRoZSBUQ1Ag
c2VxdWVuY2UgbnVtYmVycyBhcmUgYmVpbmcNCj5oYW5kbGVkIGVuZC10by1lbmQgKGZyb20gdGhl
IGNsaWVudCdzIGRldmljZSB0byB0aGUgc2VydmVyKS4NCj4NCj5GdXJ0aGVyLCBpdCBzZWVtcyB0
byBtZSB0aGF0IHRoZSBhc3N1bXB0aW9uIGlzIHRoYXQgTVBUQ1AgZ3VhcmFudGVlcyB0aGUNCj5t
ZXNzYWdlLWJvdW5kYXJpZXMsIGJlY2F1c2UgdGhlIFBsYWluIE1vZGUgTVBUQ1Agb3B0aW9uIGlz
IHB1dCBvbiBhDQo+cGVyLXNlZ21lbnQgYmFzaXMuIEhvd2V2ZXIsIE1QVENQIGNhbm5vdCBndWFy
YW50ZWUgdGhhdCB0aG9zZSBtZXNzYWdlDQo+Ym91bmRhcmllcyBhcmUgcmVzcGVjdGVkLg0KPklu
IG15IG9waW5pb24sIFBsYWluIE1vZGUgTVBUQ1AncyBvcHRpb24gYmVsb25ncyBpbnRvIHRoZSBw
YXlsb2FkLiBTbywNCj5iYXNpY2FsbHksIHRoaXMgd291bGQgYmUgbXVsdGlzdHJlYW1pbmcgKGUu
Zy4sIEhUVFAvMi1zdHlsZSkgb24gdG9wIG9mIGENCj5yZWxpYWJsZSB0cmFuc3BvcnQgbGlrZSBN
UFRDUC4NCj4NCj4NCj5DaGVlcnMsDQo+Q2hyaXN0b3BoDQo+DQo+DQo+T24gMDUvMTEvMTUgLSAx
Mzo0NTo0MSwgbW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSB3cm90ZToNCj4+IFRoaXMgaXMg
YW4gdXBkYXRlIHRvIGEgcHJvcG9zYWwgdGhhdCBpbnRlbmRzIHRvIGF2b2lkIHJlcXVpcmluZyBh
biBleHRyYSBlbmNhcHN1bGF0aW5nIHNjaGVtZSBiZXR3ZWVuIGEgQ1BFIGFuZCBhbiBNUFRDUCBD
b25jZW50cmF0b3IgbG9jYXRlZCBpbiB0aGUgcHJvdmlkZXIncyBuZXR3b3JrLiANCj4+IA0KPj4g
VGhlIGRvY3VtZW50IHN1Z2dlc3RzIGFsc28gcmVsYXlpbmcgVURQIHBhY2tldHMgaW50byBUQ1At
Zm9ybWF0dGVkIHBhY2tldHMgaW4gdGhlIENQRS1Db25jZW50cmF0b3IgbGVnLiBTb21lIGZlYXR1
cmVzIG1heSBiZSBkaXNhYmxlZC9lbmFibGVkIGF0IHRoZSBDUEUvQ29uY2VudHJhdG9yIHdoZW4g
cHJvY2Vzc2luZyBVRFAgcGFja2V0cy4NCj4+IA0KPj4gVGhlIG1haW4gbW90aXZhdGlvbiBpcyB0
byBlYXNlIGludGVncmF0aW5nIGFuIE1QVENQIENvbmNlbnRyYXRvciBpbnRvIGFuIG9wZXJhdGlv
bmFsIG5ldHdvcmsgd2l0aG91dCByZXF1aXJpbmcgdXBkYXRpbmcgaW50ZXJtZWRpYXRlIHNlcnZp
Y2UgZnVuY3Rpb25zIHRvIHN1cHBvcnQgYW5vdGhlciB5ZXQgZW5jYXBzdWxhdGlvbiBzY2hlbWUu
DQo+PiANCj4+IENvbW1lbnRzIGFyZSBtb3JlIHRoYW4gd2VsY29tZS4gDQo+PiANCj4+IENoZWVy
cywNCj4+IE1lZA0KPj4gDQo+PiA+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPj4gPiBE
ZSA6IEktRC1Bbm5vdW5jZSBbbWFpbHRvOmktZC1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnXSBE
ZSBsYSBwYXJ0IGRlDQo+PiA+IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPj4gPiBFbnZvecOp
IDogamV1ZGkgNSBub3ZlbWJyZSAyMDE1IDE0OjMzDQo+PiA+IMOAIDogaS1kLWFubm91bmNlQGll
dGYub3JnDQo+PiA+IE9iamV0IDogSS1EIEFjdGlvbjogZHJhZnQtYm91Y2FkYWlyLW1wdGNwLXBs
YWluLW1vZGUtMDMudHh0DQo+PiA+IA0KPj4gPiANCj4+ID4gQSBOZXcgSW50ZXJuZXQtRHJhZnQg
aXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzDQo+PiA+IGRpcmVj
dG9yaWVzLg0KPj4gPiANCj4+ID4gDQo+PiA+ICAgICAgICAgVGl0bGUgICAgICAgICAgIDogQW4g
TVBUQ1AgT3B0aW9uIGZvciBOZXR3b3JrLUFzc2lzdGVkIE1QVENQDQo+PiA+IERlcGxveW1lbnRz
OiBQbGFpbiBUcmFuc3BvcnQgTW9kZQ0KPj4gPiAgICAgICAgIEF1dGhvcnMgICAgICAgICA6IE1v
aGFtZWQgQm91Y2FkYWlyDQo+PiA+ICAgICAgICAgICAgICAgICAgICAgICAgICAgQ2hyaXN0aWFu
IEphY3F1ZW5ldA0KPj4gPiAgICAgICAgICAgICAgICAgICAgICAgICAgIERlbmlzIEJlaGFnaGVs
DQo+PiA+ICAgICAgICAgICAgICAgICAgICAgICAgICAgU3RlZmFubyBTZWNjaQ0KPj4gPiAJRmls
ZW5hbWUgICAgICAgIDogZHJhZnQtYm91Y2FkYWlyLW1wdGNwLXBsYWluLW1vZGUtMDMudHh0DQo+
PiA+IAlQYWdlcyAgICAgICAgICAgOiAxNA0KPj4gPiAJRGF0ZSAgICAgICAgICAgIDogMjAxNS0x
MS0wNQ0KPj4gPiANCj4+ID4gQWJzdHJhY3Q6DQo+PiA+ICAgIE9uZSBvZiB0aGUgcHJvbWlzaW5n
IGRlcGxveW1lbnQgc2NlbmFyaW9zIGZvciBNdWx0aXBhdGggVENQIChNUFRDUCkNCj4+ID4gICAg
aXMgdG8gZW5hYmxlIGEgQ3VzdG9tZXIgUHJlbWlzZXMgRXF1aXBtZW50IChDUEUpIHRoYXQgaXMg
Y29ubmVjdGVkIHRvDQo+PiA+ICAgIG11bHRpcGxlIG5ldHdvcmtzIChlLmcuLCBEU0wsIExURSwg
V0xBTikgdG8gb3B0aW1pemUgdGhlIHVzYWdlIG9mIGl0cw0KPj4gPiAgICBuZXR3b3JrIGF0dGFj
aG1lbnRzLiAgQmVjYXVzZSBvZiB0aGUgbGFjayBvZiBNUFRDUCBzdXBwb3J0IGF0IHRoZQ0KPj4g
PiAgICBzZXJ2ZXIgc2lkZSwgc29tZSBzZXJ2aWNlIHByb3ZpZGVycyBub3cgY29uc2lkZXIgYSBu
ZXR3b3JrLWFzc2lzdGVkDQo+PiA+ICAgIG1vZGVsIHRoYXQgcmVsaWVzIHVwb24gdGhlIGFjdGl2
YXRpb24gb2YgYSBkZWRpY2F0ZWQgZnVuY3Rpb24gY2FsbGVkDQo+PiA+ICAgIE1QVENQIENvbmNl
bnRyYXRvci4gIFRoaXMgZG9jdW1lbnQgZm9jdXNlcyBvbiBhIGRlcGxveW1lbnQgc2NoZW1lDQo+
PiA+ICAgIHdoZXJlIHRoZSBpZGVudGl0eSBvZiB0aGUgTVBUQ1AgQ29uY2VudHJhdG9yKHMpIGlz
IGV4cGxpY2l0bHkNCj4+ID4gICAgY29uZmlndXJlZCBvbiBjb25uZWN0ZWQgaG9zdHMuDQo+PiA+
IA0KPj4gPiAgICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhbiBNUFRDUCBvcHRpb24gdGhhdCBp
cyB1c2VkIHRvIGF2b2lkIGFuDQo+PiA+ICAgIGVuY2Fwc3VsYXRpb24gc2NoZW1lIGJldHdlZW4g
dGhlIENQRSBhbmQgdGhlIE1QVENQIENvbmNlbnRyYXRvci4NCj4+ID4gICAgQWxzbywgdGhpcyBk
b2N1bWVudCBzcGVjaWZpZXMgaG93IFVEUCB0cmFmZmljIGNhbiBiZSBkaXN0cmlidXRlZA0KPj4g
PiAgICBhbW9uZyBhdmFpbGFibGUgcGF0aHMgd2l0aG91dCByZXF1aXJpbmcgYW55IGVuY2Fwc3Vs
YXRpb24gc2NoZW1lLg0KPj4gPiANCj4+ID4gDQo+PiA+IA0KPj4gPiBUaGUgSUVURiBkYXRhdHJh
Y2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCj4+ID4gaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYm91Y2FkYWlyLW1wdGNwLXBsYWluLW1vZGUvDQo+PiA+
IA0KPj4gPiBUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj4+
ID4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWJvdWNhZGFpci1tcHRjcC1wbGFp
bi1tb2RlLTAzDQo+PiA+IA0KPj4gPiBBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBp
cyBhdmFpbGFibGUgYXQ6DQo+PiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1k
cmFmdC1ib3VjYWRhaXItbXB0Y3AtcGxhaW4tbW9kZS0wMw0KPj4gPiANCj4+ID4gDQo+PiA+IFBs
ZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0
aW1lIG9mDQo+PiA+IHN1Ym1pc3Npb24NCj4+ID4gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24g
YW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4+ID4gDQo+PiA+IElu
dGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj4+
ID4gZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCj4+ID4gDQo+PiA+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+IEktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCj4+ID4gSS1ELUFubm91bmNlQGlldGYub3JnDQo+PiA+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo+PiA+IEludGVy
bmV0LURyYWZ0IGRpcmVjdG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sDQo+
PiA+IG9yIGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+PiANCj4+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBtdWx0
aXBhdGh0Y3AgbWFpbGluZyBsaXN0DQo+PiBtdWx0aXBhdGh0Y3BAaWV0Zi5vcmcNCj4+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwDQo+DQo+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5tdWx0aXBhdGh0Y3Ag
bWFpbGluZyBsaXN0DQo+bXVsdGlwYXRodGNwQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0Y3ANCg==


From nobody Mon Nov 16 05:09:28 2015
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 294A61A8AE7 for <multipathtcp@ietfa.amsl.com>; Mon, 16 Nov 2015 05:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06Dm-OMZqvb9 for <multipathtcp@ietfa.amsl.com>; Mon, 16 Nov 2015 05:09:25 -0800 (PST)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 40CB21A893C for <multipathtcp@ietf.org>; Mon, 16 Nov 2015 05:09:25 -0800 (PST)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.16]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id BA200198405; Mon, 16 Nov 2015 14:08:57 +0100 (CET)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be BA200198405
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1447679337; bh=EMIcNNfqfp84zx8ZwDkz1j2y8Frh2ggxbttZKeoc29I=; h=Reply-To:Subject:References:To:Cc:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=yF4HHiiD9AiP7G017OYfKJiz/BTGCrryw8QAZNrh+EPxXQainLLqqtlZMxkwLYOuG sGiAZpPlmHK/L6fU82n7kWJ1AhVbyle8A9oH1zwScaSTyeV9B8M9BfET3PV0BN5Kcq B/UXZ0469OfLC/xdBcMFnEkHoseHzwS0ntGgqZJ8=
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <5649D574.30801@uclouvain.be>
Date: Mon, 16 Nov 2015 14:09:08 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99-beta1 at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: BA200198405.A2372
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/vPmh6tK4tzxi7fjFWg0H8rOTVWw>
Cc: "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 13:09:27 -0000

Med,
>
> This is an update to a proposal that intends to avoid requiring an extra encapsulating scheme between a CPE and an MPTCP Concentrator located in the provider's network.

I'm not sure I fully understand your proposal. Can I summarize it in 
saying that you place the plain mode MPTCP option in all segments that 
are exchanged and that this option is used to allow the CPE and the 
concentrator to rewrite the IP addresses of the MPTCP segments that they 
receive ?

This looks strange to me because it creates some overhead in each 
segment and also requires the utilisation of EDO which is not yet widely 
implemented. Note you might have problems to use EDO and support any 
middlebox that would already exist in the network as mentioned in 
section 4.1
"The use of a plain transport mode does not require the upgrade of any
    intermediate function (security, TCP optimizer, etc.) that may be
    located on-path."

I would start to analyse first what can be done when there are no 
middleboxes, because if you want to support them, they will mess with 
almost everything.


Olivier


From nobody Tue Nov 17 00:16:40 2015
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2D041B2C57 for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 00:16:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.886
X-Spam-Level: 
X-Spam-Status: No, score=-4.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCGK_y61PIwM for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 00:16:36 -0800 (PST)
Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A28701B2C4E for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 00:16:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple;  q=dns/txt; i=@apple.com; t=1447748196; x=2311661796; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=BLihoHkNZLQjA3Tv+nyi4xFdIesuofVXKMdlUaKyoTM=; b=MUOLuBlTC1n0QqbUUIBIClpSmhC3F51OumbuBN4/Wv2KEuxNEvwGBEzuiQFFemNQ PXm1y8s4WBHIOP/TWAGo/YuMdy7VZ9sVFgfPqRoTcj+TOD6utLsGvMFKyya+2Fg4 KTr4xS5hVQSuUxLYeqVicZ7W1PuoOH7P/zpIJH9TAYkjD3Y7vSq4F9dqsylJwOQb ApYB8h70jeBNZ+IyE8y5ped5xUlAI2RiZ/qv3p6hBk+Q9bIK88IkPGmtUL6azmMw p5D9FDQ86ze+y/IYFmV8IybjW/d4bXG/XQpxF0xQWT3Y55znhfWDguvL01nUbF9Q tQ6r6Ud34X7RTVDPgiDzsQ==;
Received: from relay3.apple.com (relay3.apple.com [17.128.113.83]) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id 3A.1D.09556.462EA465; Tue, 17 Nov 2015 00:16:36 -0800 (PST)
X-AuditID: 11973e15-f79be6d000002554-5b-564ae264e002
Received: from cilantro.apple.com (cilantro.apple.com [17.128.115.18]) (using TLS with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id 64.67.05180.462EA465; Tue, 17 Nov 2015 00:16:36 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=iso-8859-1
Received: from localhost ([17.149.239.115]) by cilantro.apple.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NXY00ATA9NNRK30@cilantro.apple.com> for multipathtcp@ietf.org; Tue, 17 Nov 2015 00:16:36 -0800 (PST)
Sender: cpaasch@apple.com
Date: Tue, 17 Nov 2015 00:16:35 -0800
From: Christoph Paasch <cpaasch@apple.com>
To: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
Message-id: <20151117081635.GY49988@da0602a-dhcp129.apple.com>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com> <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com>
In-reply-to: <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com>
User-Agent: Mutt/1.5.24 (08e81162482f) (2015-08-30)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUi2FAYrJvyyCvMoO2SoMXn1dfZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8WzGYtaC2aYV/7acZW1g7NPqYuTkkBAwkXi26h0ThC0mceHe erYuRi4OIYG9jBItX5exwRTNu/yAEcQWEpjDJPHliAiIzSsgKPFj8j2WLkYODmYBeYkjl7JB wswC0hKP/s5gh7B1JHq/f2OGmNnDJPG48RvYMmEBSYnuO3eYQWwWAVWJN5unsoLYbAJaEm9v t4PZIgL2Eu/uzGQHaWYW+Mwo8XnWaUaI5lCJn/fPsUIcYScx6/xFqA1tTBLLr2xiAUlwCrhJ fDvZD9YgKmAs0XRkDliRhMAONombd6+wTmAUnYXki1kIX8xC8sUsJF8sYGRZxSiUm5iZo5uZ Z6aXWFCQk6qXnJ+7iREUEdPtRHcwnllldYhRgINRiYdX4LhXmBBrYllxZe4hRmkOFiVxXsly oJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGgwk8eWw1TnW7J6wuNA3dwWLy/q322ns8l1ed 2h5orVGad8nl0589LG/ELgteN3lUunzq4xnKn28z5N2KVdYLkbthsPNNcPtlD/9pyVxGzmKz 0yoYf8+7r1ZznSGk3pbTQWHHHsWJqebs0cs/r9BsXzqldkXi6ck1t0K5X/+pWNBZ4C90qtZc iaU4I9FQi7moOBEAWSJazGkCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUi2FAspJvyyCvMoPMUn8Xn1dfZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8WzGYtaC2aYV/7acZW1g7NPqYuTkkBAwkZh3+QEjhC0mceHe ejYQW0hgDpPElyMiIDavgKDEj8n3WLoYOTiYBeQljlzKBgkzC0hLPPo7gx3C1pHo/f6NuYuR C6i1h0niceM3JpCEsICkRPedO8wgNouAqsSbzVNZQWw2AS2Jt7fbwWwRAXuJd3dmsoM0Mwt8 ZpT4POs0I0RzqMTP++dYIY6wk5h1/iLUhjYmieVXNrGAJDgF3CS+newHaxAVMJZoOjKHeQKj 0Cwkh89COHwWksNnITl8ASPLKkaBotScxEpjvcSCgpxUveT83E2M4AAuDN7B+GeZ1SFGAQ5G JR5egeNeYUKsiWXFlbmHGCU4mJVEeJWvA4V4UxIrq1KL8uOLSnNSiw8xJgN9PJFZSjQ5Hxhd eSXxhiYmBibGxmbGxuYm5qQJK4nz1hUBrRBITyxJzU5NLUgtgtnCxMEp1cAYI9R7/Ll93NsD Vzzak1Ne+czatuxGVvzknJINC7LiL9kFTvo2yfHnY0FeTi8urd8toZ7bFF6GKJh8O64cEXmG /cE92ZZjE3NDfm5/IvG/eLu2kd6TK3wB0xJdp5y7Vna30Fm4v2OTSerp9ecS5ss/816wb4LZ SQ2JnVuObaubUPjFwPjahbezlViKMxINtZiLihMBKZGx1KQCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/9xtfAs8_VDc4xOT9bVGnWId2Qp4>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 08:16:38 -0000

On 16/11/15 - 11:15:21, Henderickx, Wim (Wim) wrote:
> Christoph, my 2 cents:
> - The proposal terminates the sequence numbers and provides a true proxy and hence rewrites the sequence numbers at the proxy points.

Ok, I see. Thanks for clarifying.

> - I am not sure what you mean with the message boundaries. Can you clarify?

>From Mohamed's document I understand that he wants to tunnel multiple TCP
streams on top of a single MPTCP connection.
This means, that different TCP connections with different destinations will
be sent on the same MPTCP-connection. Thus, each of those segments will have
a different MPTCP Plain Mode option, which implies that these segments
cannot get split/coalesced as otherwise data will be delivered to the wrong
destination behind the concentrator. And it also implies that MPTCP will
take into account to which TCP-connection data in the send-buffer belongs
to, thus it effectively has to guarantee the message boundaries by the
application that is writing into its send-buffer.

I do not think that this is the right approach. If we want to tunnel
multiple TCP streams on top of a single MPTCP-connection, the demultiplexing
should either be backed into the payload (aka, HTTP/2-style), or be part of
MPTCP's DSS-mapping (as the DSS mapping guarantees the boundaries of its
mapping). The former is easy to achieve, while the latter could be done by
adding a "stream-identifier" into the DSS-option.

The advantage of this is that the transport (MPTCP in this case) is free to
choose to schedule traffic in the most efficient way, without having to take
into account message-boundaries and be limited by the constraint that this
imposes.



Christoph



> On 15/11/15 18:23, "multipathtcp on behalf of Christoph Paasch" <multipathtcp-bounces@ietf.org on behalf of cpaasch@apple.com> wrote:
> 
> >Hello Mohamed,
> >
> >
> >I tried to understand the draft, but it's not yet clear to me how the
> >proxying would work.
> >
> >Am I right that the draft is proposing a scheme where the Proxies (CPE and
> >concentrator) are not terminating the TCP-connections?
> >If that's the case, I am wondering how the TCP sequence numbers are being
> >handled end-to-end (from the client's device to the server).
> >
> >Further, it seems to me that the assumption is that MPTCP guarantees the
> >message-boundaries, because the Plain Mode MPTCP option is put on a
> >per-segment basis. However, MPTCP cannot guarantee that those message
> >boundaries are respected.
> >In my opinion, Plain Mode MPTCP's option belongs into the payload. So,
> >basically, this would be multistreaming (e.g., HTTP/2-style) on top of a
> >reliable transport like MPTCP.
> >
> >
> >Cheers,
> >Christoph
> >
> >
> >On 05/11/15 - 13:45:41, mohamed.boucadair@orange.com wrote:
> >> This is an update to a proposal that intends to avoid requiring an extra encapsulating scheme between a CPE and an MPTCP Concentrator located in the provider's network. 
> >> 
> >> The document suggests also relaying UDP packets into TCP-formatted packets in the CPE-Concentrator leg. Some features may be disabled/enabled at the CPE/Concentrator when processing UDP packets.
> >> 
> >> The main motivation is to ease integrating an MPTCP Concentrator into an operational network without requiring updating intermediate service functions to support another yet encapsulation scheme.
> >> 
> >> Comments are more than welcome. 
> >> 
> >> Cheers,
> >> Med
> >> 
> >> > -----Message d'origine-----
> >> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> >> > internet-drafts@ietf.org
> >> > Envoyé : jeudi 5 novembre 2015 14:33
> >> > À : i-d-announce@ietf.org
> >> > Objet : I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
> >> > 
> >> > 
> >> > A New Internet-Draft is available from the on-line Internet-Drafts
> >> > directories.
> >> > 
> >> > 
> >> >         Title           : An MPTCP Option for Network-Assisted MPTCP
> >> > Deployments: Plain Transport Mode
> >> >         Authors         : Mohamed Boucadair
> >> >                           Christian Jacquenet
> >> >                           Denis Behaghel
> >> >                           Stefano Secci
> >> > 	Filename        : draft-boucadair-mptcp-plain-mode-03.txt
> >> > 	Pages           : 14
> >> > 	Date            : 2015-11-05
> >> > 
> >> > Abstract:
> >> >    One of the promising deployment scenarios for Multipath TCP (MPTCP)
> >> >    is to enable a Customer Premises Equipment (CPE) that is connected to
> >> >    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of its
> >> >    network attachments.  Because of the lack of MPTCP support at the
> >> >    server side, some service providers now consider a network-assisted
> >> >    model that relies upon the activation of a dedicated function called
> >> >    MPTCP Concentrator.  This document focuses on a deployment scheme
> >> >    where the identity of the MPTCP Concentrator(s) is explicitly
> >> >    configured on connected hosts.
> >> > 
> >> >    This document specifies an MPTCP option that is used to avoid an
> >> >    encapsulation scheme between the CPE and the MPTCP Concentrator.
> >> >    Also, this document specifies how UDP traffic can be distributed
> >> >    among available paths without requiring any encapsulation scheme.
> >> > 
> >> > 
> >> > 
> >> > The IETF datatracker status page for this draft is:
> >> > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-plain-mode/
> >> > 
> >> > There's also a htmlized version available at:
> >> > https://tools.ietf.org/html/draft-boucadair-mptcp-plain-mode-03
> >> > 
> >> > A diff from the previous version is available at:
> >> > https://www.ietf.org/rfcdiff?url2=draft-boucadair-mptcp-plain-mode-03
> >> > 
> >> > 
> >> > Please note that it may take a couple of minutes from the time of
> >> > submission
> >> > until the htmlized version and diff are available at tools.ietf.org.
> >> > 
> >> > Internet-Drafts are also available by anonymous FTP at:
> >> > ftp://ftp.ietf.org/internet-drafts/
> >> > 
> >> > _______________________________________________
> >> > I-D-Announce mailing list
> >> > I-D-Announce@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/i-d-announce
> >> > Internet-Draft directories: http://www.ietf.org/shadow.html
> >> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >> 
> >> _______________________________________________
> >> multipathtcp mailing list
> >> multipathtcp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/multipathtcp
> >
> >_______________________________________________
> >multipathtcp mailing list
> >multipathtcp@ietf.org
> >https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Tue Nov 17 00:55:17 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E9FD1B2CD9 for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 00:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lm_gF6-BYB0X for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 00:55:13 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 794D31B2CD8 for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 00:55:13 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id D486A22C092; Tue, 17 Nov 2015 09:55:11 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.58]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id B1DBB4C05D; Tue, 17 Nov 2015 09:55:11 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0248.002; Tue, 17 Nov 2015 09:55:11 +0100
From: <mohamed.boucadair@orange.com>
To: "cpaasch@apple.com" <cpaasch@apple.com>, "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
Thread-Topic: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
Thread-Index: AQHRIRBJkw8gV6aWpEqYOU4Vk6puAZ6f5qHA
Date: Tue, 17 Nov 2015 08:55:10 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9F02F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com> <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com> <20151117081635.GY49988@da0602a-dhcp129.apple.com>
In-Reply-To: <20151117081635.GY49988@da0602a-dhcp129.apple.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.17.81517
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/9hu4Nfx0h9Slq2dxrdRY23aEXic>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 08:55:16 -0000

Hi Christoph,

Please see inline.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: cpaasch@apple.com [mailto:cpaasch@apple.com]
> Envoy=E9=A0: mardi 17 novembre 2015 09:17
> =C0=A0: Henderickx, Wim (Wim)
> Cc=A0: BOUCADAIR Mohamed IMT/OLN; multipathtcp@ietf.org; Denis Behaghel
> (Denis.Behaghel@oneaccess-net.com) (Denis.Behaghel@oneaccess-net.com)
> Objet=A0: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-
> mode-03.txt
>=20
> On 16/11/15 - 11:15:21, Henderickx, Wim (Wim) wrote:
> > Christoph, my 2 cents:
> > - The proposal terminates the sequence numbers and provides a true prox=
y
> and hence rewrites the sequence numbers at the proxy points.
>=20
> Ok, I see. Thanks for clarifying.
>=20
> > - I am not sure what you mean with the message boundaries. Can you
> clarify?
>=20
> From Mohamed's document I understand that he wants to tunnel multiple TCP
> streams on top of a single MPTCP connection.

[Med] No, sorry if this was not clear in the draft but we are not proposing=
 that way for transforming TCP connections into MPTCP connections. Typicall=
y, there will be as many MPTCP connections as TCP connections that are "ele=
cted" to be distributed among multiple paths.=20

> This means, that different TCP connections with different destinations
> will
> be sent on the same MPTCP-connection. Thus, each of those segments will
> have
> a different MPTCP Plain Mode option, which implies that these segments
> cannot get split/coalesced as otherwise data will be delivered to the
> wrong
> destination behind the concentrator. And it also implies that MPTCP will
> take into account to which TCP-connection data in the send-buffer belongs
> to, thus it effectively has to guarantee the message boundaries by the
> application that is writing into its send-buffer.
>=20
> I do not think that this is the right approach. If we want to tunnel
> multiple TCP streams on top of a single MPTCP-connection, the
> demultiplexing
> should either be backed into the payload (aka, HTTP/2-style), or be part
> of
> MPTCP's DSS-mapping (as the DSS mapping guarantees the boundaries of its
> mapping). The former is easy to achieve, while the latter could be done b=
y
> adding a "stream-identifier" into the DSS-option.
>=20
> The advantage of this is that the transport (MPTCP in this case) is free
> to
> choose to schedule traffic in the most efficient way, without having to
> take
> into account message-boundaries and be limited by the constraint that thi=
s
> imposes.
>=20
>=20
>=20
> Christoph
>=20
>=20
>=20
> > On 15/11/15 18:23, "multipathtcp on behalf of Christoph Paasch"
> <multipathtcp-bounces@ietf.org on behalf of cpaasch@apple.com> wrote:
> >
> > >Hello Mohamed,
> > >
> > >
> > >I tried to understand the draft, but it's not yet clear to me how the
> > >proxying would work.
> > >
> > >Am I right that the draft is proposing a scheme where the Proxies (CPE
> and
> > >concentrator) are not terminating the TCP-connections?
> > >If that's the case, I am wondering how the TCP sequence numbers are
> being
> > >handled end-to-end (from the client's device to the server).
> > >
> > >Further, it seems to me that the assumption is that MPTCP guarantees
> the
> > >message-boundaries, because the Plain Mode MPTCP option is put on a
> > >per-segment basis. However, MPTCP cannot guarantee that those message
> > >boundaries are respected.
> > >In my opinion, Plain Mode MPTCP's option belongs into the payload. So,
> > >basically, this would be multistreaming (e.g., HTTP/2-style) on top of
> a
> > >reliable transport like MPTCP.
> > >
> > >
> > >Cheers,
> > >Christoph
> > >
> > >
> > >On 05/11/15 - 13:45:41, mohamed.boucadair@orange.com wrote:
> > >> This is an update to a proposal that intends to avoid requiring an
> extra encapsulating scheme between a CPE and an MPTCP Concentrator locate=
d
> in the provider's network.
> > >>
> > >> The document suggests also relaying UDP packets into TCP-formatted
> packets in the CPE-Concentrator leg. Some features may be disabled/enable=
d
> at the CPE/Concentrator when processing UDP packets.
> > >>
> > >> The main motivation is to ease integrating an MPTCP Concentrator int=
o
> an operational network without requiring updating intermediate service
> functions to support another yet encapsulation scheme.
> > >>
> > >> Comments are more than welcome.
> > >>
> > >> Cheers,
> > >> Med
> > >>
> > >> > -----Message d'origine-----
> > >> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la par=
t
> de
> > >> > internet-drafts@ietf.org
> > >> > Envoy=E9 : jeudi 5 novembre 2015 14:33
> > >> > =C0 : i-d-announce@ietf.org
> > >> > Objet : I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
> > >> >
> > >> >
> > >> > A New Internet-Draft is available from the on-line Internet-Drafts
> > >> > directories.
> > >> >
> > >> >
> > >> >         Title           : An MPTCP Option for Network-Assisted
> MPTCP
> > >> > Deployments: Plain Transport Mode
> > >> >         Authors         : Mohamed Boucadair
> > >> >                           Christian Jacquenet
> > >> >                           Denis Behaghel
> > >> >                           Stefano Secci
> > >> > 	Filename        : draft-boucadair-mptcp-plain-mode-03.txt
> > >> > 	Pages           : 14
> > >> > 	Date            : 2015-11-05
> > >> >
> > >> > Abstract:
> > >> >    One of the promising deployment scenarios for Multipath TCP
> (MPTCP)
> > >> >    is to enable a Customer Premises Equipment (CPE) that is
> connected to
> > >> >    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage
> of its
> > >> >    network attachments.  Because of the lack of MPTCP support at
> the
> > >> >    server side, some service providers now consider a network-
> assisted
> > >> >    model that relies upon the activation of a dedicated function
> called
> > >> >    MPTCP Concentrator.  This document focuses on a deployment
> scheme
> > >> >    where the identity of the MPTCP Concentrator(s) is explicitly
> > >> >    configured on connected hosts.
> > >> >
> > >> >    This document specifies an MPTCP option that is used to avoid a=
n
> > >> >    encapsulation scheme between the CPE and the MPTCP Concentrator=
.
> > >> >    Also, this document specifies how UDP traffic can be distribute=
d
> > >> >    among available paths without requiring any encapsulation
> scheme.
> > >> >
> > >> >
> > >> >
> > >> > The IETF datatracker status page for this draft is:
> > >> > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-plain-mode/
> > >> >
> > >> > There's also a htmlized version available at:
> > >> > https://tools.ietf.org/html/draft-boucadair-mptcp-plain-mode-03
> > >> >
> > >> > A diff from the previous version is available at:
> > >> > https://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-mptcp-plain-mo=
de-
> 03
> > >> >
> > >> >
> > >> > Please note that it may take a couple of minutes from the time of
> > >> > submission
> > >> > until the htmlized version and diff are available at
> tools.ietf.org.
> > >> >
> > >> > Internet-Drafts are also available by anonymous FTP at:
> > >> > ftp://ftp.ietf.org/internet-drafts/
> > >> >
> > >> > _______________________________________________
> > >> > I-D-Announce mailing list
> > >> > I-D-Announce@ietf.org
> > >> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > >> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > >> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > >>
> > >> _______________________________________________
> > >> multipathtcp mailing list
> > >> multipathtcp@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/multipathtcp
> > >
> > >_______________________________________________
> > >multipathtcp mailing list
> > >multipathtcp@ietf.org
> > >https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Tue Nov 17 00:56:13 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F161B2CE3; Tue, 17 Nov 2015 00:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M2CqqWpeXAHZ; Tue, 17 Nov 2015 00:56:07 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFB51B2CD9; Tue, 17 Nov 2015 00:56:06 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id A655918C59C; Tue, 17 Nov 2015 09:56:05 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.60]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 7D82F35C06A; Tue, 17 Nov 2015 09:56:05 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7F.corporate.adroot.infra.ftgroup ([fe80::c1d7:e278:e357:11ad%19]) with mapi id 14.03.0248.002; Tue, 17 Nov 2015 09:56:05 +0100
From: <mohamed.boucadair@orange.com>
To: Niall O'Reilly <niall.oreilly@ucd.ie>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AQHRHjMpfXA3LRq140OUNdcdAefgC56f7v5A
Date: Tue, 17 Nov 2015 08:56:04 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk> <m237w9g80l.wl-Niall.oReilly@ucd.ie>
In-Reply-To: <m237w9g80l.wl-Niall.oReilly@ucd.ie>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.10.16.122716
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/9WvltVmba9dBZ6ACB2W-aAhsD8Y>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, Simon Hobson <linux@thehobsons.co.uk>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 08:56:12 -0000

SGkgTmlhbGwsDQoNCk9rLCBub3RlZC4gDQoNCkhvcGUgdG8gaGVhciBtb3JlIHZvaWNlcy4NCg0K
Q2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+IERlwqA6IE5p
YWxsIE8nUmVpbGx5IFttYWlsdG86bmlhbGwub3JlaWxseUB1Y2QuaWVdDQo+IEVudm95w6nCoDog
dmVuZHJlZGkgMTMgbm92ZW1icmUgMjAxNSAxNzo0OQ0KPiDDgMKgOiBCT1VDQURBSVIgTW9oYW1l
ZCBJTVQvT0xODQo+IENjwqA6IFNpbW9uIEhvYnNvbjsgbXVsdGlwYXRodGNwQGlldGYub3JnOyBk
aGN3Z0BpZXRmLm9yZw0KPiBPYmpldMKgOiBSZTogW2RoY3dnXSBESENQIE9wdGlvbnMgZm9yIE5l
dHdvcmstQXNzaXN0ZWQgTXVsdGlwYXRoIFRDUA0KPiAoTVBUQ1ApDQo+IA0KPiBPbiBUaHUsIDEy
IE5vdiAyMDE1IDE1OjA5OjM4ICswMDAwLA0KPiA8bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNv
bT4gd3JvdGU6DQo+ID4NCj4gPiBSZS0sDQo+ID4NCj4gPiBUaGUgY2hhbmdlIHlvdSBhc2tlZCBm
b3IgaXMgYXMgZm9sbG93czoNCj4gPg0KPiA+ID09PT09PT09PT09PT09DQo+ID4gT0xEOg0KPiA+
ICAgIFRoZSBESENQIHNlcnZlciBNVVNUIE5PVCByZXBseSB3aXRoIHRoZSBESENQIE1QVENQIENv
bmNlbnRyYXRvcg0KPiA+ICAgIG9wdGlvbiB1bmxlc3MgdGhlIGNsaWVudCBoYXMgZXhwbGljaXRs
eSByZXF1ZXN0ZWQgZm9yIGl0Lg0KPiA+DQo+ID4gTkVXOg0KPiA+ICAgIFRoZSBESENQIHNlcnZl
ciBTSE9VTEQgTk9UIHJlcGx5IHdpdGggdGhlIERIQ1AgTVBUQ1AgQ29uY2VudHJhdG9yDQo+ID4g
ICAgb3B0aW9uIHVubGVzcyB0aGUgY2xpZW50IGhhcyBleHBsaWNpdGx5IHJlcXVlc3RlZCBmb3Ig
aXQuDQo+ID4gPT09PT09PT09PT09PT0NCj4gPg0KPiA+IENvbW1lbnRzIGZyb20gdGhlIHdnIGFi
b3V0IHRoaXMgY2hhbmdlIGlzIHdlbGNvbWUuDQo+IA0KPiAgIFllcywgcGxlYXNlISAgSSB0aGlu
ayBTaW1vbiBoYXMgZXhwbGFpbmVkIHRoZSBuZWVkIGFscmVhZHkuDQo+IA0KPiAgIEJlc3QgcmVn
YXJkcywNCj4gICBOaWFsbCBPJ1JlaWxseQ0KPiANCg==


From nobody Tue Nov 17 05:37:24 2015
Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8034E1B2F56 for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 05:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.486
X-Spam-Level: 
X-Spam-Status: No, score=-7.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xw04w2kDOaiS for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 05:37:21 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B02351B2F55 for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 05:37:20 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 824239FC5E5AC; Tue, 17 Nov 2015 13:37:15 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id tAHDav8C024518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 17 Nov 2015 14:37:10 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.17]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Tue, 17 Nov 2015 14:37:07 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: Christoph Paasch <cpaasch@apple.com>
Thread-Topic: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
Thread-Index: AQHRIBXHBkXGX/O0xU2YYw+O5JGB+Z6d6R0AgAHmgID//9NxAA==
Date: Tue, 17 Nov 2015 13:37:06 +0000
Message-ID: <5306935A-66EC-4DA2-8408-4F87C439A798@alcatel-lucent.com>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com> <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com> <20151117081635.GY49988@da0602a-dhcp129.apple.com>
In-Reply-To: <20151117081635.GY49988@da0602a-dhcp129.apple.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.151008
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="utf-8"
Content-ID: <CED85F1856F63D45BC5CC42F3A102DD2@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/1SmoYpe9GvFCzeQceTRRYyp19O0>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 13:37:23 -0000

Q2hyaXN0b3BoLCBhcyBhbHJlYWR5IGNsYXJpZmllZCBieSBtZWQgdGhlIGlkZWEgaXMgbm90IHRv
IGJ1bmRsZSBtdWx0aXBsZSB0Y3Agc3RyZWFtIGluIGEgc2luZ2xlIE1QLVRDUCBjb25uZWN0aW9u
LiANCg0KDQoNCg0KT24gMTcvMTEvMTUgMDA6MTYsICJjcGFhc2NoQGFwcGxlLmNvbSBvbiBiZWhh
bGYgb2YgQ2hyaXN0b3BoIFBhYXNjaCIgPGNwYWFzY2hAYXBwbGUuY29tPiB3cm90ZToNCg0KPk9u
IDE2LzExLzE1IC0gMTE6MTU6MjEsIEhlbmRlcmlja3gsIFdpbSAoV2ltKSB3cm90ZToNCj4+IENo
cmlzdG9waCwgbXkgMiBjZW50czoNCj4+IC0gVGhlIHByb3Bvc2FsIHRlcm1pbmF0ZXMgdGhlIHNl
cXVlbmNlIG51bWJlcnMgYW5kIHByb3ZpZGVzIGEgdHJ1ZSBwcm94eSBhbmQgaGVuY2UgcmV3cml0
ZXMgdGhlIHNlcXVlbmNlIG51bWJlcnMgYXQgdGhlIHByb3h5IHBvaW50cy4NCj4NCj5PaywgSSBz
ZWUuIFRoYW5rcyBmb3IgY2xhcmlmeWluZy4NCj4NCj4+IC0gSSBhbSBub3Qgc3VyZSB3aGF0IHlv
dSBtZWFuIHdpdGggdGhlIG1lc3NhZ2UgYm91bmRhcmllcy4gQ2FuIHlvdSBjbGFyaWZ5Pw0KPg0K
PkZyb20gTW9oYW1lZCdzIGRvY3VtZW50IEkgdW5kZXJzdGFuZCB0aGF0IGhlIHdhbnRzIHRvIHR1
bm5lbCBtdWx0aXBsZSBUQ1ANCj5zdHJlYW1zIG9uIHRvcCBvZiBhIHNpbmdsZSBNUFRDUCBjb25u
ZWN0aW9uLg0KPlRoaXMgbWVhbnMsIHRoYXQgZGlmZmVyZW50IFRDUCBjb25uZWN0aW9ucyB3aXRo
IGRpZmZlcmVudCBkZXN0aW5hdGlvbnMgd2lsbA0KPmJlIHNlbnQgb24gdGhlIHNhbWUgTVBUQ1At
Y29ubmVjdGlvbi4gVGh1cywgZWFjaCBvZiB0aG9zZSBzZWdtZW50cyB3aWxsIGhhdmUNCj5hIGRp
ZmZlcmVudCBNUFRDUCBQbGFpbiBNb2RlIG9wdGlvbiwgd2hpY2ggaW1wbGllcyB0aGF0IHRoZXNl
IHNlZ21lbnRzDQo+Y2Fubm90IGdldCBzcGxpdC9jb2FsZXNjZWQgYXMgb3RoZXJ3aXNlIGRhdGEg
d2lsbCBiZSBkZWxpdmVyZWQgdG8gdGhlIHdyb25nDQo+ZGVzdGluYXRpb24gYmVoaW5kIHRoZSBj
b25jZW50cmF0b3IuIEFuZCBpdCBhbHNvIGltcGxpZXMgdGhhdCBNUFRDUCB3aWxsDQo+dGFrZSBp
bnRvIGFjY291bnQgdG8gd2hpY2ggVENQLWNvbm5lY3Rpb24gZGF0YSBpbiB0aGUgc2VuZC1idWZm
ZXIgYmVsb25ncw0KPnRvLCB0aHVzIGl0IGVmZmVjdGl2ZWx5IGhhcyB0byBndWFyYW50ZWUgdGhl
IG1lc3NhZ2UgYm91bmRhcmllcyBieSB0aGUNCj5hcHBsaWNhdGlvbiB0aGF0IGlzIHdyaXRpbmcg
aW50byBpdHMgc2VuZC1idWZmZXIuDQo+DQo+SSBkbyBub3QgdGhpbmsgdGhhdCB0aGlzIGlzIHRo
ZSByaWdodCBhcHByb2FjaC4gSWYgd2Ugd2FudCB0byB0dW5uZWwNCj5tdWx0aXBsZSBUQ1Agc3Ry
ZWFtcyBvbiB0b3Agb2YgYSBzaW5nbGUgTVBUQ1AtY29ubmVjdGlvbiwgdGhlIGRlbXVsdGlwbGV4
aW5nDQo+c2hvdWxkIGVpdGhlciBiZSBiYWNrZWQgaW50byB0aGUgcGF5bG9hZCAoYWthLCBIVFRQ
LzItc3R5bGUpLCBvciBiZSBwYXJ0IG9mDQo+TVBUQ1AncyBEU1MtbWFwcGluZyAoYXMgdGhlIERT
UyBtYXBwaW5nIGd1YXJhbnRlZXMgdGhlIGJvdW5kYXJpZXMgb2YgaXRzDQo+bWFwcGluZykuIFRo
ZSBmb3JtZXIgaXMgZWFzeSB0byBhY2hpZXZlLCB3aGlsZSB0aGUgbGF0dGVyIGNvdWxkIGJlIGRv
bmUgYnkNCj5hZGRpbmcgYSAic3RyZWFtLWlkZW50aWZpZXIiIGludG8gdGhlIERTUy1vcHRpb24u
DQo+DQo+VGhlIGFkdmFudGFnZSBvZiB0aGlzIGlzIHRoYXQgdGhlIHRyYW5zcG9ydCAoTVBUQ1Ag
aW4gdGhpcyBjYXNlKSBpcyBmcmVlIHRvDQo+Y2hvb3NlIHRvIHNjaGVkdWxlIHRyYWZmaWMgaW4g
dGhlIG1vc3QgZWZmaWNpZW50IHdheSwgd2l0aG91dCBoYXZpbmcgdG8gdGFrZQ0KPmludG8gYWNj
b3VudCBtZXNzYWdlLWJvdW5kYXJpZXMgYW5kIGJlIGxpbWl0ZWQgYnkgdGhlIGNvbnN0cmFpbnQg
dGhhdCB0aGlzDQo+aW1wb3Nlcy4NCj4NCj4NCj4NCj5DaHJpc3RvcGgNCj4NCj4NCj4NCj4+IE9u
IDE1LzExLzE1IDE4OjIzLCAibXVsdGlwYXRodGNwIG9uIGJlaGFsZiBvZiBDaHJpc3RvcGggUGFh
c2NoIiA8bXVsdGlwYXRodGNwLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGNwYWFzY2hA
YXBwbGUuY29tPiB3cm90ZToNCj4+IA0KPj4gPkhlbGxvIE1vaGFtZWQsDQo+PiA+DQo+PiA+DQo+
PiA+SSB0cmllZCB0byB1bmRlcnN0YW5kIHRoZSBkcmFmdCwgYnV0IGl0J3Mgbm90IHlldCBjbGVh
ciB0byBtZSBob3cgdGhlDQo+PiA+cHJveHlpbmcgd291bGQgd29yay4NCj4+ID4NCj4+ID5BbSBJ
IHJpZ2h0IHRoYXQgdGhlIGRyYWZ0IGlzIHByb3Bvc2luZyBhIHNjaGVtZSB3aGVyZSB0aGUgUHJv
eGllcyAoQ1BFIGFuZA0KPj4gPmNvbmNlbnRyYXRvcikgYXJlIG5vdCB0ZXJtaW5hdGluZyB0aGUg
VENQLWNvbm5lY3Rpb25zPw0KPj4gPklmIHRoYXQncyB0aGUgY2FzZSwgSSBhbSB3b25kZXJpbmcg
aG93IHRoZSBUQ1Agc2VxdWVuY2UgbnVtYmVycyBhcmUgYmVpbmcNCj4+ID5oYW5kbGVkIGVuZC10
by1lbmQgKGZyb20gdGhlIGNsaWVudCdzIGRldmljZSB0byB0aGUgc2VydmVyKS4NCj4+ID4NCj4+
ID5GdXJ0aGVyLCBpdCBzZWVtcyB0byBtZSB0aGF0IHRoZSBhc3N1bXB0aW9uIGlzIHRoYXQgTVBU
Q1AgZ3VhcmFudGVlcyB0aGUNCj4+ID5tZXNzYWdlLWJvdW5kYXJpZXMsIGJlY2F1c2UgdGhlIFBs
YWluIE1vZGUgTVBUQ1Agb3B0aW9uIGlzIHB1dCBvbiBhDQo+PiA+cGVyLXNlZ21lbnQgYmFzaXMu
IEhvd2V2ZXIsIE1QVENQIGNhbm5vdCBndWFyYW50ZWUgdGhhdCB0aG9zZSBtZXNzYWdlDQo+PiA+
Ym91bmRhcmllcyBhcmUgcmVzcGVjdGVkLg0KPj4gPkluIG15IG9waW5pb24sIFBsYWluIE1vZGUg
TVBUQ1AncyBvcHRpb24gYmVsb25ncyBpbnRvIHRoZSBwYXlsb2FkLiBTbywNCj4+ID5iYXNpY2Fs
bHksIHRoaXMgd291bGQgYmUgbXVsdGlzdHJlYW1pbmcgKGUuZy4sIEhUVFAvMi1zdHlsZSkgb24g
dG9wIG9mIGENCj4+ID5yZWxpYWJsZSB0cmFuc3BvcnQgbGlrZSBNUFRDUC4NCj4+ID4NCj4+ID4N
Cj4+ID5DaGVlcnMsDQo+PiA+Q2hyaXN0b3BoDQo+PiA+DQo+PiA+DQo+PiA+T24gMDUvMTEvMTUg
LSAxMzo0NTo0MSwgbW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSB3cm90ZToNCj4+ID4+IFRo
aXMgaXMgYW4gdXBkYXRlIHRvIGEgcHJvcG9zYWwgdGhhdCBpbnRlbmRzIHRvIGF2b2lkIHJlcXVp
cmluZyBhbiBleHRyYSBlbmNhcHN1bGF0aW5nIHNjaGVtZSBiZXR3ZWVuIGEgQ1BFIGFuZCBhbiBN
UFRDUCBDb25jZW50cmF0b3IgbG9jYXRlZCBpbiB0aGUgcHJvdmlkZXIncyBuZXR3b3JrLiANCj4+
ID4+IA0KPj4gPj4gVGhlIGRvY3VtZW50IHN1Z2dlc3RzIGFsc28gcmVsYXlpbmcgVURQIHBhY2tl
dHMgaW50byBUQ1AtZm9ybWF0dGVkIHBhY2tldHMgaW4gdGhlIENQRS1Db25jZW50cmF0b3IgbGVn
LiBTb21lIGZlYXR1cmVzIG1heSBiZSBkaXNhYmxlZC9lbmFibGVkIGF0IHRoZSBDUEUvQ29uY2Vu
dHJhdG9yIHdoZW4gcHJvY2Vzc2luZyBVRFAgcGFja2V0cy4NCj4+ID4+IA0KPj4gPj4gVGhlIG1h
aW4gbW90aXZhdGlvbiBpcyB0byBlYXNlIGludGVncmF0aW5nIGFuIE1QVENQIENvbmNlbnRyYXRv
ciBpbnRvIGFuIG9wZXJhdGlvbmFsIG5ldHdvcmsgd2l0aG91dCByZXF1aXJpbmcgdXBkYXRpbmcg
aW50ZXJtZWRpYXRlIHNlcnZpY2UgZnVuY3Rpb25zIHRvIHN1cHBvcnQgYW5vdGhlciB5ZXQgZW5j
YXBzdWxhdGlvbiBzY2hlbWUuDQo+PiA+PiANCj4+ID4+IENvbW1lbnRzIGFyZSBtb3JlIHRoYW4g
d2VsY29tZS4gDQo+PiA+PiANCj4+ID4+IENoZWVycywNCj4+ID4+IE1lZA0KPj4gPj4gDQo+PiA+
PiA+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPj4gPj4gPiBEZSA6IEktRC1Bbm5vdW5j
ZSBbbWFpbHRvOmktZC1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnXSBEZSBsYSBwYXJ0IGRlDQo+
PiA+PiA+IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPj4gPj4gPiBFbnZvecOpIDogamV1ZGkg
NSBub3ZlbWJyZSAyMDE1IDE0OjMzDQo+PiA+PiA+IMOAIDogaS1kLWFubm91bmNlQGlldGYub3Jn
DQo+PiA+PiA+IE9iamV0IDogSS1EIEFjdGlvbjogZHJhZnQtYm91Y2FkYWlyLW1wdGNwLXBsYWlu
LW1vZGUtMDMudHh0DQo+PiA+PiA+IA0KPj4gPj4gPiANCj4+ID4+ID4gQSBOZXcgSW50ZXJuZXQt
RHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzDQo+PiA+
PiA+IGRpcmVjdG9yaWVzLg0KPj4gPj4gPiANCj4+ID4+ID4gDQo+PiA+PiA+ICAgICAgICAgVGl0
bGUgICAgICAgICAgIDogQW4gTVBUQ1AgT3B0aW9uIGZvciBOZXR3b3JrLUFzc2lzdGVkIE1QVENQ
DQo+PiA+PiA+IERlcGxveW1lbnRzOiBQbGFpbiBUcmFuc3BvcnQgTW9kZQ0KPj4gPj4gPiAgICAg
ICAgIEF1dGhvcnMgICAgICAgICA6IE1vaGFtZWQgQm91Y2FkYWlyDQo+PiA+PiA+ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgQ2hyaXN0aWFuIEphY3F1ZW5ldA0KPj4gPj4gPiAgICAgICAgICAg
ICAgICAgICAgICAgICAgIERlbmlzIEJlaGFnaGVsDQo+PiA+PiA+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgU3RlZmFubyBTZWNjaQ0KPj4gPj4gPiAJRmlsZW5hbWUgICAgICAgIDogZHJhZnQt
Ym91Y2FkYWlyLW1wdGNwLXBsYWluLW1vZGUtMDMudHh0DQo+PiA+PiA+IAlQYWdlcyAgICAgICAg
ICAgOiAxNA0KPj4gPj4gPiAJRGF0ZSAgICAgICAgICAgIDogMjAxNS0xMS0wNQ0KPj4gPj4gPiAN
Cj4+ID4+ID4gQWJzdHJhY3Q6DQo+PiA+PiA+ICAgIE9uZSBvZiB0aGUgcHJvbWlzaW5nIGRlcGxv
eW1lbnQgc2NlbmFyaW9zIGZvciBNdWx0aXBhdGggVENQIChNUFRDUCkNCj4+ID4+ID4gICAgaXMg
dG8gZW5hYmxlIGEgQ3VzdG9tZXIgUHJlbWlzZXMgRXF1aXBtZW50IChDUEUpIHRoYXQgaXMgY29u
bmVjdGVkIHRvDQo+PiA+PiA+ICAgIG11bHRpcGxlIG5ldHdvcmtzIChlLmcuLCBEU0wsIExURSwg
V0xBTikgdG8gb3B0aW1pemUgdGhlIHVzYWdlIG9mIGl0cw0KPj4gPj4gPiAgICBuZXR3b3JrIGF0
dGFjaG1lbnRzLiAgQmVjYXVzZSBvZiB0aGUgbGFjayBvZiBNUFRDUCBzdXBwb3J0IGF0IHRoZQ0K
Pj4gPj4gPiAgICBzZXJ2ZXIgc2lkZSwgc29tZSBzZXJ2aWNlIHByb3ZpZGVycyBub3cgY29uc2lk
ZXIgYSBuZXR3b3JrLWFzc2lzdGVkDQo+PiA+PiA+ICAgIG1vZGVsIHRoYXQgcmVsaWVzIHVwb24g
dGhlIGFjdGl2YXRpb24gb2YgYSBkZWRpY2F0ZWQgZnVuY3Rpb24gY2FsbGVkDQo+PiA+PiA+ICAg
IE1QVENQIENvbmNlbnRyYXRvci4gIFRoaXMgZG9jdW1lbnQgZm9jdXNlcyBvbiBhIGRlcGxveW1l
bnQgc2NoZW1lDQo+PiA+PiA+ICAgIHdoZXJlIHRoZSBpZGVudGl0eSBvZiB0aGUgTVBUQ1AgQ29u
Y2VudHJhdG9yKHMpIGlzIGV4cGxpY2l0bHkNCj4+ID4+ID4gICAgY29uZmlndXJlZCBvbiBjb25u
ZWN0ZWQgaG9zdHMuDQo+PiA+PiA+IA0KPj4gPj4gPiAgICBUaGlzIGRvY3VtZW50IHNwZWNpZmll
cyBhbiBNUFRDUCBvcHRpb24gdGhhdCBpcyB1c2VkIHRvIGF2b2lkIGFuDQo+PiA+PiA+ICAgIGVu
Y2Fwc3VsYXRpb24gc2NoZW1lIGJldHdlZW4gdGhlIENQRSBhbmQgdGhlIE1QVENQIENvbmNlbnRy
YXRvci4NCj4+ID4+ID4gICAgQWxzbywgdGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgaG93IFVEUCB0
cmFmZmljIGNhbiBiZSBkaXN0cmlidXRlZA0KPj4gPj4gPiAgICBhbW9uZyBhdmFpbGFibGUgcGF0
aHMgd2l0aG91dCByZXF1aXJpbmcgYW55IGVuY2Fwc3VsYXRpb24gc2NoZW1lLg0KPj4gPj4gPiAN
Cj4+ID4+ID4gDQo+PiA+PiA+IA0KPj4gPj4gPiBUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMg
cGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCj4+ID4+ID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9kb2MvZHJhZnQtYm91Y2FkYWlyLW1wdGNwLXBsYWluLW1vZGUvDQo+PiA+PiA+IA0KPj4g
Pj4gPiBUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj4+ID4+
ID4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWJvdWNhZGFpci1tcHRjcC1wbGFp
bi1tb2RlLTAzDQo+PiA+PiA+IA0KPj4gPj4gPiBBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVy
c2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+PiA+PiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2Rp
ZmY/dXJsMj1kcmFmdC1ib3VjYWRhaXItbXB0Y3AtcGxhaW4tbW9kZS0wMw0KPj4gPj4gPiANCj4+
ID4+ID4gDQo+PiA+PiA+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2Yg
bWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+PiA+PiA+IHN1Ym1pc3Npb24NCj4+ID4+ID4gdW50
aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5p
ZXRmLm9yZy4NCj4+ID4+ID4gDQo+PiA+PiA+IEludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFp
bGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj4+ID4+ID4gZnRwOi8vZnRwLmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy8NCj4+ID4+ID4gDQo+PiA+PiA+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+PiA+IEktRC1Bbm5vdW5jZSBtYWlsaW5nIGxp
c3QNCj4+ID4+ID4gSS1ELUFubm91bmNlQGlldGYub3JnDQo+PiA+PiA+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo+PiA+PiA+IEludGVybmV0LURy
YWZ0IGRpcmVjdG9yaWVzOiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sDQo+PiA+PiA+
IG9yIGZ0cDovL2Z0cC5pZXRmLm9yZy9pZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo+PiA+PiANCj4+
ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+
PiBtdWx0aXBhdGh0Y3AgbWFpbGluZyBsaXN0DQo+PiA+PiBtdWx0aXBhdGh0Y3BAaWV0Zi5vcmcN
Cj4+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNw
DQo+PiA+DQo+PiA+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4+ID5tdWx0aXBhdGh0Y3AgbWFpbGluZyBsaXN0DQo+PiA+bXVsdGlwYXRodGNwQGlldGYu
b3JnDQo+PiA+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tdWx0aXBhdGh0
Y3ANCg==


From nobody Tue Nov 17 07:28:50 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 982B71A9117; Tue, 17 Nov 2015 07:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qwxCI2PGpuz; Tue, 17 Nov 2015 07:28:46 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF261A9115; Tue, 17 Nov 2015 07:28:46 -0800 (PST)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id C6951DA0096; Tue, 17 Nov 2015 15:28:45 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Tue, 17 Nov 2015 07:28:46 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Niall O'Reilly" <niall.oreilly@ucd.ie>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4QAfEywwABV+PgAAAJveAAABmjuAAAmZWQAAA4EzgABdzasAAAB6MQAAAH71AAAB8nKAAAGZCQAANcBUAAC4qL4A///Yhsw=
Date: Tue, 17 Nov 2015 15:28:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A045A5@mbx-03.WIN.NOMINUM.COM>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk> <m237w9g80l.wl-Niall.oReilly@ucd.ie>, <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [71.233.41.235]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/y0Cj3XO4mSsdwuWAVuBPpnlNrTs>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 15:28:47 -0000

Neither text is correct.   If you are going to specify DHCP server behavior=
 with normative language, you are updating RFC 3315, which you almost certa=
inly do not want to do.   RFC 3315 already specifies the correct behavior. =
  Please remove this text.   RFC 7227 section 21.2 touches on this issue.
________________________________________
From: dhcwg [dhcwg-bounces@ietf.org] on behalf of mohamed.boucadair@orange.=
com [mohamed.boucadair@orange.com]
Sent: Tuesday, November 17, 2015 03:56
To: Niall O'Reilly
Cc: multipathtcp@ietf.org; dhcwg@ietf.org
Subject: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP=
)

Hi Niall,

Ok, noted.

Hope to hear more voices.

Cheers,
Med

> -----Message d'origine-----
> De : Niall O'Reilly [mailto:niall.oreilly@ucd.ie]
> Envoy=E9 : vendredi 13 novembre 2015 17:49
> =C0 : BOUCADAIR Mohamed IMT/OLN
> Cc : Simon Hobson; multipathtcp@ietf.org; dhcwg@ietf.org
> Objet : Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>
> On Thu, 12 Nov 2015 15:09:38 +0000,
> <mohamed.boucadair@orange.com> wrote:
> >
> > Re-,
> >
> > The change you asked for is as follows:
> >
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > OLD:
> >    The DHCP server MUST NOT reply with the DHCP MPTCP Concentrator
> >    option unless the client has explicitly requested for it.
> >
> > NEW:
> >    The DHCP server SHOULD NOT reply with the DHCP MPTCP Concentrator
> >    option unless the client has explicitly requested for it.
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > Comments from the wg about this change is welcome.
>
>   Yes, please!  I think Simon has explained the need already.
>
>   Best regards,
>   Niall O'Reilly
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg=


From nobody Tue Nov 17 10:49:21 2015
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3501A6EDC for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 10:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.676
X-Spam-Level: 
X-Spam-Status: No, score=-4.676 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KA-E1AzVZPmq for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 10:49:17 -0800 (PST)
Received: from mail-in5.apple.com (mail-out5.apple.com [17.151.62.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 142E01A21C2 for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 10:49:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple;  q=dns/txt; i=@apple.com; t=1447786156; x=2311699756; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=94XXFkEVmFVI17BD3YdaQF/6fQjexn/CSTZ0Pls9fkk=; b=1f/lfX0VfjvvFX+8Etk9s20H1jAXVD+y5DqYtxxk+zKH+Q5D+cN3tdJNsKIEi/mI JJxymcZG+TnXpyybKGAZhF7ONQUajs6FaZRCWFGAzHPxNbFXL8llELXd+Ic7ABZT 7EdSyfUQDI/BsQ7IHtrfMTSNC0pWEvXTEs8u9VUVuQu5bZ5llGlobXyWqyICL7a7 Na7RbOJM1OeMVxV9LZnCaBBXKTFKTiV/bgDDfPEhz5ZxsXKAARzrAYd+9cjEYxoZ C/7IAiqb/v1OK2GIEB8qNYm/NLZM+6757buqgqK1wh97CpTF/7bRB+w4MyCsR65w DMKhC9jYv04/7I2CKWPCaA==;
Received: from relay6.apple.com (relay6.apple.com [17.128.113.90]) by mail-in5.apple.com (Apple Secure Mail Relay) with SMTP id B7.FC.20021.CA67B465; Tue, 17 Nov 2015 10:49:16 -0800 (PST)
X-AuditID: 11973e13-f79196d000004e35-4e-564b76ac91a8
Received: from aniseed.apple.com (aniseed.apple.com [17.128.115.23]) (using TLS with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay6.apple.com (Apple SCV relay) with SMTP id AB.E0.29392.CA67B465; Tue, 17 Nov 2015 10:49:16 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=iso-8859-1
Received: from localhost ([17.149.224.34]) by aniseed.apple.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NXZ00ITS2Y4W950@aniseed.apple.com> for multipathtcp@ietf.org; Tue, 17 Nov 2015 10:49:16 -0800 (PST)
Sender: cpaasch@apple.com
Date: Tue, 17 Nov 2015 10:49:16 -0800
From: "cpaasch@apple.com" <cpaasch@apple.com>
To: mohamed.boucadair@orange.com
Message-id: <20151117184916.GB49988@da0602a-dhcp129.apple.com>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com> <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com> <20151117081635.GY49988@da0602a-dhcp129.apple.com> <787AE7BB302AE849A7480A190F8B933008C9F02F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-reply-to: <787AE7BB302AE849A7480A190F8B933008C9F02F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
User-Agent: Mutt/1.5.24 (08e81162482f) (2015-08-30)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUi2FAYpbumzDvMYPEvbYvPq6+zOTB6LFny kymAMYrLJiU1J7MstUjfLoEr49X6JpaC+fYVP4+cZGxgXGvQxcjBISFgIvHjpE8XIyeQKSZx 4d56ti5GLg4hgb2MEsefvmSBSJhIPJzziBkiMYtJon/XWyaQBK+AoMSPyfdYQAYxC8hLHLmU DRJmFpCWePR3BjuErSPR+/0bVG8nk8TS9YfBEsICkhLdd+4wg9gsAqoSjz58ZgWx2QR0JW68 Pc8GYosIKEjsa+tngRj0kVFi6i1WiN5QiZ/3z7FC3GAncXHaGyaIBZOZJZp6f4Et4BRIkVh3 by3YIFEBY4mmI3PArpAQ2MIm8eF/B+sERtFZSJ6YhfDELCRPzELyxAJGllWMQrmJmTm6mXmm eokFBTmpesn5uZsYQfEw3U54B+PpVVaHGAU4GJV4eAWOe4UJsSaWFVfmHmKU5mBREuc9Xuod JiSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGxJlrnQfqM+3ujO/yt94nz/oluX/l+f9lTo9P3 NacHc5zJPVZy9PDv1xdfPLVYbixzsavDoq5T+sEu7XnfH5y/nrZy4/ygiRubTNMzV95qiOdd ZX8yfn8/b8W822m1nys9P4QxT33Qm2/n9lRNerl/triJ9JlvqXdeFbGkemicO8MqWjkv4KOf EktxRqKhFnNRcSIAzuFyLmgCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUi2FAsrrumzDvMYOZUDYvPq6+zOTB6LFny kymAMYrLJiU1J7MstUjfLoEr49X6JpaC+fYVP4+cZGxgXGvQxcjJISFgIvFwziNmCFtM4sK9 9WxdjFwcQgKzmCT6d71lAknwCghK/Jh8j6WLkYODWUBe4silbJAws4C0xKO/M9ghbB2J3u/f mCF6O5kklq4/DJYQFpCU6L5zB2wBi4CqxKMPn1lBbDYBXYkbb8+zgdgiAgoS+9r6WSAGfWSU mHqLFaI3VOLn/XOsEDfYSVyc9oYJYsFkZomm3l9gCzgFUiTW3VsLNkhUwFii6cgc5gmMQrOQ 3D0L4e5ZSO6eheTuBYwsqxgFilJzEivN9BILCnJS9ZLzczcxggO4MGoHY8Nyq0OMAhyMSjy8 O454hQmxJpYVV+YeYpTgYFYS4eW08g4T4k1JrKxKLcqPLyrNSS0+xJgM9PBEZinR5HxgdOWV xBuamBiYGBubGRubm5iTJqwkzltfBLRVID2xJDU7NbUgtQhmCxMHp1QDI6eErezFPO8MJoOZ P6WijbZMPz1FnPHKJqN1XbW1fHdPKc6R1DXj/nC3xjS9OuWVn0qA4bK1XpJrXds8tQ1tTtc7 NzLlsk2vzOZPUJ78ktcvV2he+VrThM7rSwPMV51c1/i1YZXgpPmCMve23fe9kFdZty7Ucc5M pZ4tPa5Npx5yHV+l9uqXEktxRqKhFnNRcSIAva36Y6QCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/7wlnxvQHLxq_FNZLFX8qo_wUyzo>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 18:49:19 -0000

Hello Med,

On 17/11/15 - 08:55:10, mohamed.boucadair@orange.com wrote:
> > On 16/11/15 - 11:15:21, Henderickx, Wim (Wim) wrote:
> > > Christoph, my 2 cents:
> > > - The proposal terminates the sequence numbers and provides a true proxy
> > and hence rewrites the sequence numbers at the proxy points.
> > 
> > Ok, I see. Thanks for clarifying.
> > 
> > > - I am not sure what you mean with the message boundaries. Can you
> > clarify?
> > 
> > From Mohamed's document I understand that he wants to tunnel multiple TCP
> > streams on top of a single MPTCP connection.
> 
> [Med] No, sorry if this was not clear in the draft but we are not proposing that way for transforming TCP connections into MPTCP connections. Typically, there will be as many MPTCP connections as TCP connections that are "elected" to be distributed among multiple paths. 

so, in this case the MPTCP Plain Mode option would be set on which segment?
Why not simply doing a SOCKS-proxy?

I don't think there is a need for a new MPTCP subtype here.


Christoph

> 
> > This means, that different TCP connections with different destinations
> > will
> > be sent on the same MPTCP-connection. Thus, each of those segments will
> > have
> > a different MPTCP Plain Mode option, which implies that these segments
> > cannot get split/coalesced as otherwise data will be delivered to the
> > wrong
> > destination behind the concentrator. And it also implies that MPTCP will
> > take into account to which TCP-connection data in the send-buffer belongs
> > to, thus it effectively has to guarantee the message boundaries by the
> > application that is writing into its send-buffer.
> > 
> > I do not think that this is the right approach. If we want to tunnel
> > multiple TCP streams on top of a single MPTCP-connection, the
> > demultiplexing
> > should either be backed into the payload (aka, HTTP/2-style), or be part
> > of
> > MPTCP's DSS-mapping (as the DSS mapping guarantees the boundaries of its
> > mapping). The former is easy to achieve, while the latter could be done by
> > adding a "stream-identifier" into the DSS-option.
> > 
> > The advantage of this is that the transport (MPTCP in this case) is free
> > to
> > choose to schedule traffic in the most efficient way, without having to
> > take
> > into account message-boundaries and be limited by the constraint that this
> > imposes.
> > 
> > 
> > 
> > Christoph
> > 
> > 
> > 
> > > On 15/11/15 18:23, "multipathtcp on behalf of Christoph Paasch"
> > <multipathtcp-bounces@ietf.org on behalf of cpaasch@apple.com> wrote:
> > >
> > > >Hello Mohamed,
> > > >
> > > >
> > > >I tried to understand the draft, but it's not yet clear to me how the
> > > >proxying would work.
> > > >
> > > >Am I right that the draft is proposing a scheme where the Proxies (CPE
> > and
> > > >concentrator) are not terminating the TCP-connections?
> > > >If that's the case, I am wondering how the TCP sequence numbers are
> > being
> > > >handled end-to-end (from the client's device to the server).
> > > >
> > > >Further, it seems to me that the assumption is that MPTCP guarantees
> > the
> > > >message-boundaries, because the Plain Mode MPTCP option is put on a
> > > >per-segment basis. However, MPTCP cannot guarantee that those message
> > > >boundaries are respected.
> > > >In my opinion, Plain Mode MPTCP's option belongs into the payload. So,
> > > >basically, this would be multistreaming (e.g., HTTP/2-style) on top of
> > a
> > > >reliable transport like MPTCP.
> > > >
> > > >
> > > >Cheers,
> > > >Christoph
> > > >
> > > >
> > > >On 05/11/15 - 13:45:41, mohamed.boucadair@orange.com wrote:
> > > >> This is an update to a proposal that intends to avoid requiring an
> > extra encapsulating scheme between a CPE and an MPTCP Concentrator located
> > in the provider's network.
> > > >>
> > > >> The document suggests also relaying UDP packets into TCP-formatted
> > packets in the CPE-Concentrator leg. Some features may be disabled/enabled
> > at the CPE/Concentrator when processing UDP packets.
> > > >>
> > > >> The main motivation is to ease integrating an MPTCP Concentrator into
> > an operational network without requiring updating intermediate service
> > functions to support another yet encapsulation scheme.
> > > >>
> > > >> Comments are more than welcome.
> > > >>
> > > >> Cheers,
> > > >> Med
> > > >>
> > > >> > -----Message d'origine-----
> > > >> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part
> > de
> > > >> > internet-drafts@ietf.org
> > > >> > Envoyé : jeudi 5 novembre 2015 14:33
> > > >> > À : i-d-announce@ietf.org
> > > >> > Objet : I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
> > > >> >
> > > >> >
> > > >> > A New Internet-Draft is available from the on-line Internet-Drafts
> > > >> > directories.
> > > >> >
> > > >> >
> > > >> >         Title           : An MPTCP Option for Network-Assisted
> > MPTCP
> > > >> > Deployments: Plain Transport Mode
> > > >> >         Authors         : Mohamed Boucadair
> > > >> >                           Christian Jacquenet
> > > >> >                           Denis Behaghel
> > > >> >                           Stefano Secci
> > > >> > 	Filename        : draft-boucadair-mptcp-plain-mode-03.txt
> > > >> > 	Pages           : 14
> > > >> > 	Date            : 2015-11-05
> > > >> >
> > > >> > Abstract:
> > > >> >    One of the promising deployment scenarios for Multipath TCP
> > (MPTCP)
> > > >> >    is to enable a Customer Premises Equipment (CPE) that is
> > connected to
> > > >> >    multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage
> > of its
> > > >> >    network attachments.  Because of the lack of MPTCP support at
> > the
> > > >> >    server side, some service providers now consider a network-
> > assisted
> > > >> >    model that relies upon the activation of a dedicated function
> > called
> > > >> >    MPTCP Concentrator.  This document focuses on a deployment
> > scheme
> > > >> >    where the identity of the MPTCP Concentrator(s) is explicitly
> > > >> >    configured on connected hosts.
> > > >> >
> > > >> >    This document specifies an MPTCP option that is used to avoid an
> > > >> >    encapsulation scheme between the CPE and the MPTCP Concentrator.
> > > >> >    Also, this document specifies how UDP traffic can be distributed
> > > >> >    among available paths without requiring any encapsulation
> > scheme.
> > > >> >
> > > >> >
> > > >> >
> > > >> > The IETF datatracker status page for this draft is:
> > > >> > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-plain-mode/
> > > >> >
> > > >> > There's also a htmlized version available at:
> > > >> > https://tools.ietf.org/html/draft-boucadair-mptcp-plain-mode-03
> > > >> >
> > > >> > A diff from the previous version is available at:
> > > >> > https://www.ietf.org/rfcdiff?url2=draft-boucadair-mptcp-plain-mode-
> > 03
> > > >> >
> > > >> >
> > > >> > Please note that it may take a couple of minutes from the time of
> > > >> > submission
> > > >> > until the htmlized version and diff are available at
> > tools.ietf.org.
> > > >> >
> > > >> > Internet-Drafts are also available by anonymous FTP at:
> > > >> > ftp://ftp.ietf.org/internet-drafts/
> > > >> >
> > > >> > _______________________________________________
> > > >> > I-D-Announce mailing list
> > > >> > I-D-Announce@ietf.org
> > > >> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > > >> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > > >> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > > >>
> > > >> _______________________________________________
> > > >> multipathtcp mailing list
> > > >> multipathtcp@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/multipathtcp
> > > >
> > > >_______________________________________________
> > > >multipathtcp mailing list
> > > >multipathtcp@ietf.org
> > > >https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Tue Nov 17 14:24:11 2015
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 901151B33F1 for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 14:24:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.544
X-Spam-Level: **
X-Spam-Status: No, score=2.544 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diXVa0sRSAzs for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 14:24:07 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15DCD1B33E5 for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 14:24:06 -0800 (PST)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A12FD2782AB for <multipathtcp@ietf.org>; Wed, 18 Nov 2015 07:24:04 +0900 (JST)
Received: by obbnk6 with SMTP id nk6so18869464obb.2 for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 14:24:02 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.131.40 with SMTP id oj8mr9420491oeb.31.1447799042925; Tue, 17 Nov 2015 14:24:02 -0800 (PST)
Received: by 10.202.218.213 with HTTP; Tue, 17 Nov 2015 14:24:02 -0800 (PST)
Date: Tue, 17 Nov 2015 14:24:02 -0800
X-Gmail-Original-Message-ID: <CAO249yeQF1sMjaSh_QiRdm9=FMNwqnzGrDnk=R=40V0_GSjpFA@mail.gmail.com>
Message-ID: <CAO249yeQF1sMjaSh_QiRdm9=FMNwqnzGrDnk=R=40V0_GSjpFA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/V-UyvIsjIMlM6wRnp23ed9UiKHU>
Subject: [multipathtcp] draft minute for Yokohama meeting
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 22:24:08 -0000

Hello,

Sorry for the delay. We have uploaded a draft minute for Yokohama meeting.
Please check the following URL and please let us know if you have
correction or suggestions or comments.

https://www.ietf.org/proceedings/94/minutes/minutes-94-mptcp

We appreciate Pasi and Alan for precise note taking.
Thanks for very productive discussions!

--
Yoshi & Phil


From nobody Tue Nov 17 22:32:04 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A151ACEE4; Tue, 17 Nov 2015 22:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsjyHTw9hvv5; Tue, 17 Nov 2015 22:31:58 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61F471ACEE3; Tue, 17 Nov 2015 22:31:58 -0800 (PST)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id 902181902ED; Wed, 18 Nov 2015 07:31:56 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.27]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 691BF15805B; Wed, 18 Nov 2015 07:31:56 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0248.002; Wed, 18 Nov 2015 07:31:56 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4QAfEywwABV+PgAAAJveAAABmjuAAAmZWQAAA4EzgABdzasAAAB6MQAAAH71AAAB8nKAAAGZCQAANcBUAAC4qL4A///Yhsz//vXLcA==
Date: Wed, 18 Nov 2015 06:31:55 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9F851@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk> <m237w9g80l.wl-Niall.oReilly@ucd.ie>, <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630797A045A5@mbx-03.WIN.NOMINUM.COM>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630797A045A5@mbx-03.WIN.NOMINUM.COM>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.18.51517
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/lNIiblrBorzQ-hUQne2ldiXKSzo>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Niall O'Reilly <niall.oreilly@ucd.ie>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 06:32:01 -0000

Hi Ted,

Thank you for feedback. I see you are asking we revert back to what we had =
in -02.

I do confirm we don't want to update RFC3315. This is exactly why the title=
 of the section we are discussing is "DHCP Server Configuration Guidelines"=
, not "server behavior".=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Ted Lemon [mailto:Ted.Lemon@nominum.com]
> Envoy=E9=A0: mardi 17 novembre 2015 16:29
> =C0=A0: BOUCADAIR Mohamed IMT/OLN; Niall O'Reilly
> Cc=A0: multipathtcp@ietf.org; dhcwg@ietf.org
> Objet=A0: RE: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>=20
> Neither text is correct.   If you are going to specify DHCP server
> behavior with normative language, you are updating RFC 3315, which you
> almost certainly do not want to do.   RFC 3315 already specifies the
> correct behavior.   Please remove this text.   RFC 7227 section 21.2
> touches on this issue.
> ________________________________________
> From: dhcwg [dhcwg-bounces@ietf.org] on behalf of
> mohamed.boucadair@orange.com [mohamed.boucadair@orange.com]
> Sent: Tuesday, November 17, 2015 03:56
> To: Niall O'Reilly
> Cc: multipathtcp@ietf.org; dhcwg@ietf.org
> Subject: Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> (MPTCP)
>=20
> Hi Niall,
>=20
> Ok, noted.
>=20
> Hope to hear more voices.
>=20
> Cheers,
> Med
>=20
> > -----Message d'origine-----
> > De : Niall O'Reilly [mailto:niall.oreilly@ucd.ie]
> > Envoy=E9 : vendredi 13 novembre 2015 17:49
> > =C0 : BOUCADAIR Mohamed IMT/OLN
> > Cc : Simon Hobson; multipathtcp@ietf.org; dhcwg@ietf.org
> > Objet : Re: [dhcwg] DHCP Options for Network-Assisted Multipath TCP
> > (MPTCP)
> >
> > On Thu, 12 Nov 2015 15:09:38 +0000,
> > <mohamed.boucadair@orange.com> wrote:
> > >
> > > Re-,
> > >
> > > The change you asked for is as follows:
> > >
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > OLD:
> > >    The DHCP server MUST NOT reply with the DHCP MPTCP Concentrator
> > >    option unless the client has explicitly requested for it.
> > >
> > > NEW:
> > >    The DHCP server SHOULD NOT reply with the DHCP MPTCP Concentrator
> > >    option unless the client has explicitly requested for it.
> > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >
> > > Comments from the wg about this change is welcome.
> >
> >   Yes, please!  I think Simon has explained the need already.
> >
> >   Best regards,
> >   Niall O'Reilly
> >
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Tue Nov 17 22:54:27 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26161AD1FE for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 22:54:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OR5iP9z_R2U for <multipathtcp@ietfa.amsl.com>; Tue, 17 Nov 2015 22:54:23 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D52C51AD1C3 for <multipathtcp@ietf.org>; Tue, 17 Nov 2015 22:54:22 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 14C1A22C82C; Wed, 18 Nov 2015 07:54:21 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.69]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id E65C227C059; Wed, 18 Nov 2015 07:54:20 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%19]) with mapi id 14.03.0248.002; Wed, 18 Nov 2015 07:54:20 +0100
From: <mohamed.boucadair@orange.com>
To: "cpaasch@apple.com" <cpaasch@apple.com>
Thread-Topic: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
Thread-Index: AQHRIWir/mC9p3ZtTEWZx925FQ2eOZ6hUyhA
Date: Wed, 18 Nov 2015 06:54:20 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008C9F871@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com> <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com> <20151117081635.GY49988@da0602a-dhcp129.apple.com> <787AE7BB302AE849A7480A190F8B933008C9F02F@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20151117184916.GB49988@da0602a-dhcp129.apple.com>
In-Reply-To: <20151117184916.GB49988@da0602a-dhcp129.apple.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.18.60315
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/HnEnyJR-O7j4Az0QEE_rCvDXNgs>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 06:54:26 -0000

Hi Christoph,=20

Please see inline.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: cpaasch@apple.com [mailto:cpaasch@apple.com]
> Envoy=E9=A0: mardi 17 novembre 2015 19:49
> =C0=A0: BOUCADAIR Mohamed IMT/OLN
> Cc=A0: Henderickx, Wim (Wim); multipathtcp@ietf.org; Denis Behaghel
> (Denis.Behaghel@oneaccess-net.com) (Denis.Behaghel@oneaccess-net.com)
> Objet=A0: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-
> mode-03.txt
>=20
> Hello Med,
>=20
> On 17/11/15 - 08:55:10, mohamed.boucadair@orange.com wrote:
> > > On 16/11/15 - 11:15:21, Henderickx, Wim (Wim) wrote:
> > > > Christoph, my 2 cents:
> > > > - The proposal terminates the sequence numbers and provides a true
> proxy
> > > and hence rewrites the sequence numbers at the proxy points.
> > >
> > > Ok, I see. Thanks for clarifying.
> > >
> > > > - I am not sure what you mean with the message boundaries. Can you
> > > clarify?
> > >
> > > From Mohamed's document I understand that he wants to tunnel multiple
> TCP
> > > streams on top of a single MPTCP connection.
> >
> > [Med] No, sorry if this was not clear in the draft but we are not
> proposing that way for transforming TCP connections into MPTCP
> connections. Typically, there will be as many MPTCP connections as TCP
> connections that are "elected" to be distributed among multiple paths.
>=20
> so, in this case the MPTCP Plain Mode option would be set on which
> segment?
> Why not simply doing a SOCKS-proxy?
>=20

[Med] SOCKS and other encapsulation modes cane be used, indeed. But the int=
egration of an encapsulation-based solution may not be as that "simple" as =
you seem to suggest in your answer. Please keep in mind there are advanced =
service functions that are enabled in the network side and if you want to r=
euse those functions for the aggregated traffic, you may end up requiring t=
o update those intermediate service functions. So, integration tasks may no=
t be that simple. The same observation applies for updating CPE software pl=
atforms.=20

We touched about this point briefly in the document:

   The use of a plain transport mode does not require the upgrade of any
   intermediate function (security, TCP optimizer, etc.) that may be
   located on-path.  Thus, the introduction of MPTCP concentrators in
   operational networks to operate plain mode does not add any extra
   complexity as far as the operation of possible intermediate functions
   is concerned.

The situation is not black or white. Some operators will be happy with an e=
ncapsulation mode (SOCKS, GRE, MIP) while others may prefer the native plai=
n transport mode (this proposal).=20

> I don't think there is a need for a new MPTCP subtype here.

[Med] Fully agree. We don't need an option if SOCKS is used.=20

>=20
>=20
> Christoph
>=20
> >
> > > This means, that different TCP connections with different destination=
s
> > > will
> > > be sent on the same MPTCP-connection. Thus, each of those segments
> will
> > > have
> > > a different MPTCP Plain Mode option, which implies that these segment=
s
> > > cannot get split/coalesced as otherwise data will be delivered to the
> > > wrong
> > > destination behind the concentrator. And it also implies that MPTCP
> will
> > > take into account to which TCP-connection data in the send-buffer
> belongs
> > > to, thus it effectively has to guarantee the message boundaries by th=
e
> > > application that is writing into its send-buffer.
> > >
> > > I do not think that this is the right approach. If we want to tunnel
> > > multiple TCP streams on top of a single MPTCP-connection, the
> > > demultiplexing
> > > should either be backed into the payload (aka, HTTP/2-style), or be
> part
> > > of
> > > MPTCP's DSS-mapping (as the DSS mapping guarantees the boundaries of
> its
> > > mapping). The former is easy to achieve, while the latter could be
> done by
> > > adding a "stream-identifier" into the DSS-option.
> > >
> > > The advantage of this is that the transport (MPTCP in this case) is
> free
> > > to
> > > choose to schedule traffic in the most efficient way, without having
> to
> > > take
> > > into account message-boundaries and be limited by the constraint that
> this
> > > imposes.
> > >
> > >
> > >
> > > Christoph
> > >
> > >
> > >
> > > > On 15/11/15 18:23, "multipathtcp on behalf of Christoph Paasch"
> > > <multipathtcp-bounces@ietf.org on behalf of cpaasch@apple.com> wrote:
> > > >
> > > > >Hello Mohamed,
> > > > >
> > > > >
> > > > >I tried to understand the draft, but it's not yet clear to me how
> the
> > > > >proxying would work.
> > > > >
> > > > >Am I right that the draft is proposing a scheme where the Proxies
> (CPE
> > > and
> > > > >concentrator) are not terminating the TCP-connections?
> > > > >If that's the case, I am wondering how the TCP sequence numbers ar=
e
> > > being
> > > > >handled end-to-end (from the client's device to the server).
> > > > >
> > > > >Further, it seems to me that the assumption is that MPTCP
> guarantees
> > > the
> > > > >message-boundaries, because the Plain Mode MPTCP option is put on =
a
> > > > >per-segment basis. However, MPTCP cannot guarantee that those
> message
> > > > >boundaries are respected.
> > > > >In my opinion, Plain Mode MPTCP's option belongs into the payload.
> So,
> > > > >basically, this would be multistreaming (e.g., HTTP/2-style) on to=
p
> of
> > > a
> > > > >reliable transport like MPTCP.
> > > > >
> > > > >
> > > > >Cheers,
> > > > >Christoph
> > > > >
> > > > >
> > > > >On 05/11/15 - 13:45:41, mohamed.boucadair@orange.com wrote:
> > > > >> This is an update to a proposal that intends to avoid requiring
> an
> > > extra encapsulating scheme between a CPE and an MPTCP Concentrator
> located
> > > in the provider's network.
> > > > >>
> > > > >> The document suggests also relaying UDP packets into TCP-
> formatted
> > > packets in the CPE-Concentrator leg. Some features may be
> disabled/enabled
> > > at the CPE/Concentrator when processing UDP packets.
> > > > >>
> > > > >> The main motivation is to ease integrating an MPTCP Concentrator
> into
> > > an operational network without requiring updating intermediate servic=
e
> > > functions to support another yet encapsulation scheme.
> > > > >>
> > > > >> Comments are more than welcome.
> > > > >>
> > > > >> Cheers,
> > > > >> Med
> > > > >>
> > > > >> > -----Message d'origine-----
> > > > >> > De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la
> part
> > > de
> > > > >> > internet-drafts@ietf.org
> > > > >> > Envoy=E9 : jeudi 5 novembre 2015 14:33
> > > > >> > =C0 : i-d-announce@ietf.org
> > > > >> > Objet : I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
> > > > >> >
> > > > >> >
> > > > >> > A New Internet-Draft is available from the on-line Internet-
> Drafts
> > > > >> > directories.
> > > > >> >
> > > > >> >
> > > > >> >         Title           : An MPTCP Option for Network-Assisted
> > > MPTCP
> > > > >> > Deployments: Plain Transport Mode
> > > > >> >         Authors         : Mohamed Boucadair
> > > > >> >                           Christian Jacquenet
> > > > >> >                           Denis Behaghel
> > > > >> >                           Stefano Secci
> > > > >> > 	Filename        : draft-boucadair-mptcp-plain-mode-03.txt
> > > > >> > 	Pages           : 14
> > > > >> > 	Date            : 2015-11-05
> > > > >> >
> > > > >> > Abstract:
> > > > >> >    One of the promising deployment scenarios for Multipath TCP
> > > (MPTCP)
> > > > >> >    is to enable a Customer Premises Equipment (CPE) that is
> > > connected to
> > > > >> >    multiple networks (e.g., DSL, LTE, WLAN) to optimize the
> usage
> > > of its
> > > > >> >    network attachments.  Because of the lack of MPTCP support
> at
> > > the
> > > > >> >    server side, some service providers now consider a network-
> > > assisted
> > > > >> >    model that relies upon the activation of a dedicated
> function
> > > called
> > > > >> >    MPTCP Concentrator.  This document focuses on a deployment
> > > scheme
> > > > >> >    where the identity of the MPTCP Concentrator(s) is
> explicitly
> > > > >> >    configured on connected hosts.
> > > > >> >
> > > > >> >    This document specifies an MPTCP option that is used to
> avoid an
> > > > >> >    encapsulation scheme between the CPE and the MPTCP
> Concentrator.
> > > > >> >    Also, this document specifies how UDP traffic can be
> distributed
> > > > >> >    among available paths without requiring any encapsulation
> > > scheme.
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > The IETF datatracker status page for this draft is:
> > > > >> > https://datatracker.ietf.org/doc/draft-boucadair-mptcp-plain-
> mode/
> > > > >> >
> > > > >> > There's also a htmlized version available at:
> > > > >> > https://tools.ietf.org/html/draft-boucadair-mptcp-plain-mode-0=
3
> > > > >> >
> > > > >> > A diff from the previous version is available at:
> > > > >> > https://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-mptcp-plai=
n-
> mode-
> > > 03
> > > > >> >
> > > > >> >
> > > > >> > Please note that it may take a couple of minutes from the time
> of
> > > > >> > submission
> > > > >> > until the htmlized version and diff are available at
> > > tools.ietf.org.
> > > > >> >
> > > > >> > Internet-Drafts are also available by anonymous FTP at:
> > > > >> > ftp://ftp.ietf.org/internet-drafts/
> > > > >> >
> > > > >> > _______________________________________________
> > > > >> > I-D-Announce mailing list
> > > > >> > I-D-Announce@ietf.org
> > > > >> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > > > >> > Internet-Draft directories: http://www.ietf.org/shadow.html
> > > > >> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > > > >>
> > > > >> _______________________________________________
> > > > >> multipathtcp mailing list
> > > > >> multipathtcp@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/multipathtcp
> > > > >
> > > > >_______________________________________________
> > > > >multipathtcp mailing list
> > > > >multipathtcp@ietf.org
> > > > >https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Wed Nov 18 01:08:55 2015
Return-Path: <c.raiciu@cs.ucl.ac.uk>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0498E1B2A94 for <multipathtcp@ietfa.amsl.com>; Wed, 18 Nov 2015 01:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level: 
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czCGXHys9ajB for <multipathtcp@ietfa.amsl.com>; Wed, 18 Nov 2015 01:08:52 -0800 (PST)
Received: from bells2.cs.ucl.ac.uk (bells2.cs.ucl.ac.uk [128.16.5.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E946F1B2A7E for <multipathtcp@ietf.org>; Wed, 18 Nov 2015 01:08:51 -0800 (PST)
Received: from [141.85.37.157] (helo=[10.0.0.110]) by bells2.cs.ucl.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (C.Raiciu authenticated) (Exim 4.54) id 1ZyyjK-000Al2-UZ; Wed, 18 Nov 2015 09:08:43 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Costin Raiciu <c.raiciu@cs.ucl.ac.uk>
In-Reply-To: <20150910144318.GH69323@Chimay.local>
Date: Wed, 18 Nov 2015 11:08:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <33067B42-9794-4E87-8237-F9AF9230291E@cs.ucl.ac.uk>
References: <20150908035557.GB73228@Chimay.local> <55F098DB.8020201@uclouvain.be> <20150910022151.GF42530@Chimay.local> <55F15586.3000003@uclouvain.be> <20150910144318.GH69323@Chimay.local>
To: Christoph Paasch <cpaasch@apple.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/AsNsXFLMvsVUmD6xGrRhd5E-GUU>
Cc: MultiPath WG <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] New Version Notification for draft-paasch-mptcp-loadbalancer-00.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 09:08:55 -0000

Christoph,

First, I=E2=80=99d like to say that solving the loadbalancer issue is =
very important. I have spoken to Microsoft people that said that can=E2=80=
=99t use MPTCP because it doesn=E2=80=99t work through their =
loadbalancers.

I have finally had a careful look at your draft. I find the second =
proposed solution, the one that changes the token derivation algorithm, =
to be very interesting. I fully support it, and I think we should =
mandate it is 6824bis, even if this increases the MPTCP version number.

Here at UPB we are actively working on a scalable load balancer for =
MPTCP - we=E2=80=99ll keep you posted once we have something to show.

Cheers.
Costin




> On 10 Sep 2015, at 17:43, Christoph Paasch <cpaasch@apple.com> wrote:
>=20
> On 10/09/15 - 12:03:50, Olivier Bonaventure wrote:
>>> I really like this idea.
>>>=20
>>> Very often, IP-in-IP encapsulation is done from the loadbalancer to =
the
>>> server. Thus, the key could even be placed in an IP-option. As =
everything is
>>> local to the data-center there shouldn't be an issue with adding a =
new
>>> IP-option.
>>>=20
>>>=20
>>> But as you point out in the other mail, when multiple loadbalancers =
are
>>> being used we have an issue again. Maybe, there is a way to generate =
the key
>>> in such a way that we can guarantee uniqueness across the =
loadbalancers?
>>>=20
>>=20
>> This is one possibility, but I'm not sure that we need to specify =
that
>> unless we want load balancers from different vendors to cooperate.
>=20
> I was more thinking of it in case we do not modify anything in the
> MPTCP-handshake. In that case, the different loadbalancers will be
> generating the keys independently. The loadbalancers can easily
> make sure that they generate different keys, however because the token =
is a
> hash of the key, collisions are possible.
>=20
> Thus, we would need a way to guarantee uniqueness of the token across =
the
> loadbalancers.
>=20
>> The load balancing problem could be an opportunity to rethink the =
three-way
>> handshake used by Multipath TCP so that it can work well with =
tomorrow's
>> target protocol stack, likely HTTP/2 / TLS / MPTCP / IPv6
>=20
> +1 on TLS
>=20
> For IPv6 I'm a bit concerned because we are yet far away from full =
IPv6
> deployment and IPv4 is proably never going away.
>=20
>> To deal with security issues, we have included keys in clear inside =
the SYN
>> and SYN+ACK segments. Then the limited TCP option space has forced us =
to use
>> hash functions to compute the IDSN and the tokens. Using a hash to =
compute
>> the tokens creates difficulties when one wants to coordinate token
>> allocations between a set of load balancers.
>>=20
>> I wonder whether we should not explore again the work documented in
>> =
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html=
_draft-2Dpaasch-2Dmptcp-2Dlowoverhead-2D00&d=3DBQIC-g&c=3DeEvniauFctOgLOKG=
JOplqw&r=3DfSuJ9mpJ1IB1Lz-sIp_MCe23kZIFT6UKt4EhsewNEmA&m=3Dd1DAUSnnbQyUTC9=
DUvPR9YgBw1illvfDq55MXrewq0M&s=3D2Xd614qho-KOJFy_LZtqx000U8div7FG31UhLM9V6=
WY&e=3D
>> and
>> =
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html=
_draft-2Dpaasch-2Dmptcp-2Dssl-2D00&d=3DBQIC-g&c=3DeEvniauFctOgLOKGJOplqw&r=
=3DfSuJ9mpJ1IB1Lz-sIp_MCe23kZIFT6UKt4EhsewNEmA&m=3Dd1DAUSnnbQyUTC9DUvPR9Yg=
Bw1illvfDq55MXrewq0M&s=3DSiCZMS9Xpc2g-z1tPdqDgzwTK2evfjTpi-2OBM4Z9R4&e=3D
>>=20
>>=20
>> Let us first ignore the security issues and make the toke explicit in =
the
>> handshake.
>>=20
>>=20
>>               Host A                               Host B
>>              ----------                           ----------
>>              Address A1                           Address B1
>>              ----------                           ----------
>>                  |                                    |
>>                  |  SYN+MP_CAPABLE(Token-A)           |
>>                  |----------------------------------->|
>>                  |                                    |
>>                  |SYN/ACK+MP_CAPABLE(Token-B)         |
>>                  |<-----------------------------------|
>>                  |                                    |
>>                  |  ACK+MP_CAPABLE(Token-A, Token-B)  |
>>                  |----------------------------------->|
>>=20
>>=20
>> It might also be possible to remove Token-A from the initial SYN =
since there
>> is little benefit from the server to know this token at this stage.
>=20
> Yes, if the MP_CAPABLE becomes reliable in the third ACK, we can =
probably
> remove the token from the SYN (although we have to be creative for TFO =
in
> that case).
>=20
>> The IDSN
>> could be derived as TokenA|TokenB in one direction and TokenB|TokenA =
in the
>> other or better a hash of these values.
>>=20
>> The benefit of this approach is that the Token chosen by the server =
is not
>> explicitelt sent in the SYN/ACK. Load balancers can coordinate to =
have one
>> pool of tokens for each LB and pass them to the servers.
>>=20
>> The next step is to authenticate the establishment of subflows. The =
best
>> approach with HTTP/2 / TLS  is clearly to derive MPTCP keys from the =
master
>> TLS key and use them to authenticate the subflows with the HMAC =
mechanism
>> already defined. With this, we leverage the security properties of =
TLS and
>> do not anymore depend on "keys" that are sent in clear in the SYN =
segments
>> and consume precious option space. Of course, a drawback of this =
approach is
>> that you cannot create a subflow until the end of the TLS handshake, =
but TLS
>> is moving towards faster handshakes.
>=20
> I think this is the best way to go (if the working-group is fine with
> introducing a rather big change to RFC6824bis).
>=20
> It frees up space in the handshake, enables MPTCP behind loadbalancers
> (independent of IPv4 or IPv6) and also gives incentives to enable =
TLS/SSL.
> Additionally to that, it enables low-overhead deployments of MPTCP for
> data-center environments.
>=20
>=20
> Christoph
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Wed Nov 18 07:11:58 2015
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06C601B3246; Wed, 18 Nov 2015 07:11:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xOXS2xzcKX29; Wed, 18 Nov 2015 07:11:55 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E6C61B326C; Wed, 18 Nov 2015 07:11:55 -0800 (PST)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id BA78DDA00A9; Wed, 18 Nov 2015 15:11:54 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Wed, 18 Nov 2015 07:08:00 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
Thread-Index: AdEbBmKTbwftk3lYQ+2W8C9ebSXh4QAfEywwABV+PgAAAJveAAABmjuAAAmZWQAAA4EzgABdzasAAAB6MQAAAH71AAAB8nKAAAGZCQAANcBUAAC4qL4A///Yhsz//vXLcIACpWOi
Date: Wed, 18 Nov 2015 15:07:59 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A048D5@mbx-03.WIN.NOMINUM.COM>
References: <D2660C4C.7A833%dan.seibel@telus.com> <787AE7BB302AE849A7480A190F8B933008C9AC74@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <m2pozifd2f.wl-Niall.oReilly@ucd.ie> <787AE7BB302AE849A7480A190F8B933008C9AD6A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <D8E99AD3-A93A-4C43-9E6D-9E3015EF4670@thehobsons.co.uk> <787AE7BB302AE849A7480A190F8B933008C9AEFD@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F8FA02F0-952D-472B-8016-71C3B62DA04B@thehobsons.co.uk> <m237w9g80l.wl-Niall.oReilly@ucd.ie>, <787AE7BB302AE849A7480A190F8B933008C9F043@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630797A045A5@mbx-03.WIN.NOMINUM.COM>, <787AE7BB302AE849A7480A190F8B933008C9F851@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008C9F851@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [71.233.41.235]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/gAQT4qiGztH7uViVmkhi6KQ6jv0>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Niall O'Reilly <niall.oreilly@ucd.ie>
Subject: Re: [multipathtcp] [dhcwg] DHCP Options for Network-Assisted Multipath TCP (MPTCP)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 15:11:56 -0000

Thanks, Med.   The new text (or lack thereof!) is fine!


From nobody Sun Nov 22 23:48:52 2015
Return-Path: <cpaasch@apple.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ADAC1B36D9 for <multipathtcp@ietfa.amsl.com>; Sun, 22 Nov 2015 23:48:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.676
X-Spam-Level: 
X-Spam-Status: No, score=-4.676 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bPZZzmNI5sQX for <multipathtcp@ietfa.amsl.com>; Sun, 22 Nov 2015 23:48:49 -0800 (PST)
Received: from mail-in2.euro.apple.com (mail-in.euro.apple.com [17.72.148.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D23CF1B2FA3 for <multipathtcp@ietf.org>; Sun, 22 Nov 2015 23:48:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple;  q=dns/txt; i=@apple.com; t=1448264926; x=2312178526; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HfRPcA8x7T1irbk5Vxg6gXkYcgoASWtI5v3QgenwxQQ=; b=yWx2xJ/K/+aJN+3yBhyp2w2pI48o1L+jIkq45JLnLa7Bt4nulYPWkvu/5hvAuHH4 wKYbZuP5Y8Xh2rOJkZj5vhufvBcvSyI40OqoNjj+htqcvO+sDdKzBLXCm3afw7tw wpFcbfKr7Myn0dngcbHgWTBg3dP5F5avTN5Qxfq5HWTNsPm/N117UneloXzY2Q1E iZLuO47iIYLyoF7+tCsCeIUheIRDLWiKUzb27fPC9pEEJcC0GkQCiqB7Zthb2d51 kHTVc0PaQmEjzwFvv08ELAPtRTfeh3Pg02I09b/YjG67dvT8XwCgCZHdFzDU1pk8 7RakgbP3tE6cAbFUEdFbqg==;
Received: from relay1.euro.apple.com (relay1.euro.apple.com [17.66.55.11]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail-in2.euro.apple.com (Symantec Mail Security) with SMTP id ED.9C.09341.ED4C2565; Mon, 23 Nov 2015 07:48:46 +0000 (GMT)
X-AuditID: 1148940c-f79ce6d00000247d-3a-5652c4de4839
Received: from crk-mmpp-sz01 (crk-mmpp-sz01.euro.apple.com [17.66.12.154]) (using TLS with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay1.euro.apple.com (Symantec Mail Security) with SMTP id 5F.99.04348.ED4C2565; Mon, 23 Nov 2015 07:48:46 +0000 (GMT)
Received: from localhost ([17.78.241.34]) by crk-mmpp-sz01.euro.apple.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NY900LI6CDBHN40@crk-mmpp-sz01.euro.apple.com> for multipathtcp@ietf.org; Mon, 23 Nov 2015 07:48:48 +0000 (GMT)
Sender: cpaasch@apple.com
Date: Mon, 23 Nov 2015 08:48:45 +0100
From: "cpaasch@apple.com" <cpaasch@apple.com>
To: mohamed.boucadair@orange.com
Message-id: <20151123074845.GF98334@Chimay.local>
References: <20151105133319.27130.76692.idtracker@ietfa.amsl.com> <20be1fd0-7b6a-4a53-b204-6d13412289fa@OPEXCLILM23.corporate.adroot.infra.ftgroup> <20151116022310.GI49988@da0602a-dhcp129.apple.com> <2D8185A7-9D28-42EF-A4BB-B402BB516FDB@alcatel-lucent.com> <20151117081635.GY49988@da0602a-dhcp129.apple.com> <787AE7BB302AE849A7480A190F8B933008C9F02F@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <20151117184916.GB49988@da0602a-dhcp129.apple.com> <787AE7BB302AE849A7480A190F8B933008C9F871@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
In-reply-to: <787AE7BB302AE849A7480A190F8B933008C9F871@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
User-Agent: Mutt/1.5.24 (08e81162482f) (2015-08-30)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUi6GTOrXvvSFCYwYLLRhafV19nc2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxpr/RgUvJCuWrd/P0sC4S6SLkYNDQsBEYu0Eni5GTiBTTOLC vfVsXYxcHEIC65gkmjeeZodImEgcXXOIBSKxhkniT+tOqKp5TBIzL65gBakSFpCU6L5zhxnE ZhFQlXg0sZcFxGYT0JW48fY8G4gtIqAgsa+tHyzOLPCRUWLqLajeUImf98+B2bwChhJ/H/Wy QyxYwCIxe8cJdoiEoMSPyfegmrUk1u88zgRhS0s8+jsDrIZTIEVi7blesEGiAsYSTUfmMIMM khD4ySqxZPonxgmMIrOQzJqFZNYsJLMWMDKvYhTPTczM0c3MM9JLLS3K10ssKMhJ1UvOz93E CAp1jyk8OxgvHjQ8xCjAwajEw6u6KShMiDWxrLgy9xCjBAezkgjvka1AId6UxMqq1KL8+KLS nNTiQ4zSHCxK4ryGsq5hQgLpiSWp2ampBalFMFkmDk6pBkYrp/okpoLkS4Kdoh1C6+bOeJm7 tHXq9qmVO3a9XsF7d0ZiSs47w2Jha6cXPSydc5u6j5z5uEY4+3fXv08eejc3HKvSUfr6tG4O W+2O49kLLWeeCXA5XXVgb+vbXg8xH9vePabC0XOX/jzxPLz8iuSsfc6bLWP/+J/nlHoS+VaF 96fy2f3c6xSUWIozEg21mIuKEwEw0+recQIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOLMWRmVeSWpSXmKPExsUi6MQzS/fekaAwg8VTDCw+r77O5sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujDX/jQpeSFYsW7+fpYFxl0gXIyeHhICJxNE1h1ggbDGJC/fW s3UxcnEICaxhkvjTuhPKmcckMfPiClaQKmEBSYnuO3eYQWwWAVWJRxN7wbrZBHQlbrw9zwZi iwgoSOxr6weLMwt8ZJSYeguqN1Ti5/1zYDavgKHE30e97BALFrBIzN5xgh0iISjxY/I9qGYt ifU7jzNB2NISj/7OAKvhFEiRWHuuF2yQqICxRNOROcwTGAVnIWmfhaR9FpL2BYzMqxhFi1Jz EisN9VJLi/L1EgsKclL1kvNzNzGCg9Ocewfj8d2GhxgFOBiVeHglNgWFCbEmlhVX5h5ilOBg VhLhPbIVKMSbklhZlVqUH19UmpNafIhRmoNFSZw3PVY2TEggPbEkNTs1tSC1CCbLxMEp1cBY XXgw1vfFyqgPHYeYWzZ+OqYRN//djOcthfcmykxNOVeq8/zZzANrf4vGML/U47Ap2GZ7VzrS anVqJ9OE7VptC2b9V107d9rm94dMPj+oVzup9Stm9Z+Jc+LEOFfOZlqfMjX92S419/j0GxnH OJk/tyziFzyx5XCQeHXHhs/RHSzHIhIOy3lfUGIpzkg01GIuKk4EAI1yGnpKAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/rLEry37kKBPOOqbZngHg555-Akw>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "Denis Behaghel \(Denis.Behaghel@oneaccess-net.com\) \(Denis.Behaghel@oneaccess-net.com\)" <Denis.Behaghel@oneaccess-net.com>
Subject: Re: [multipathtcp] TR: I-D Action: draft-boucadair-mptcp-plain-mode-03.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 07:48:51 -0000

Hello Med,


On 18/11/15 - 06:54:20, mohamed.boucadair@orange.com wrote:
> > > > > Christoph, my 2 cents:
> > > > > - The proposal terminates the sequence numbers and provides a true
> > proxy
> > > > and hence rewrites the sequence numbers at the proxy points.
> > > >
> > > > Ok, I see. Thanks for clarifying.
> > > >
> > > > > - I am not sure what you mean with the message boundaries. Can you
> > > > clarify?
> > > >
> > > > From Mohamed's document I understand that he wants to tunnel multiple
> > TCP
> > > > streams on top of a single MPTCP connection.
> > >
> > > [Med] No, sorry if this was not clear in the draft but we are not
> > proposing that way for transforming TCP connections into MPTCP
> > connections. Typically, there will be as many MPTCP connections as TCP
> > connections that are "elected" to be distributed among multiple paths.
> > 
> > so, in this case the MPTCP Plain Mode option would be set on which
> > segment?
> > Why not simply doing a SOCKS-proxy?
> > 
> 
> [Med] SOCKS and other encapsulation modes cane be used, indeed. But the integration of an encapsulation-based solution may not be as that "simple" as you seem to suggest in your answer. Please keep in mind there are advanced service functions that are enabled in the network side and if you want to reuse those functions for the aggregated traffic, you may end up requiring to update those intermediate service functions. So, integration tasks may not be that simple. The same observation applies for updating CPE software platforms. 
> 
> We touched about this point briefly in the document:
> 
>    The use of a plain transport mode does not require the upgrade of any
>    intermediate function (security, TCP optimizer, etc.) that may be
>    located on-path.  Thus, the introduction of MPTCP concentrators in
>    operational networks to operate plain mode does not add any extra
>    complexity as far as the operation of possible intermediate functions
>    is concerned.
> 
> The situation is not black or white. Some operators will be happy with an encapsulation mode (SOCKS, GRE, MIP) while others may prefer the native plain transport mode (this proposal). 

I think, the document would benefit of giving a more precise example of how
the Plain Mode option will be used. E.g., on which segment should the plain
mode option be placed (from what I see, it only is really needed on
SYN-segments). The document in its current form does not really help in
understanding this - Figure 3 seems to treat MPTCP more like a datagram
service than a connected byte-stream service. I think much of the confusion
comes from there.
Maybe you can give an example on how Plain Mode will be used (taking into
account the 3-way handshake of MPTCP and the available TCP option-space)?

Further, more information on what exactly would go wrong with alternative
solutions of providing the IP-addresses in the payload. Especially, because
TCP optimizers, intrusion detection systems,... anyways will have issues when
faced with an MPTCP-flow. Thus, I'm not sure in what way a SOCKS-like
approach (or which ever way of putting the IP-address in the payload) will be
an additional issue as MPTCP is already a "problem" for those devices.



Cheers,
Christoph

