
From nobody Wed May  2 00:10:07 2018
Return-Path: <session-request@ietf.org>
X-Original-To: multipathtcp@ietf.org
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A72AF12D877; Wed,  2 May 2018 00:10:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: multipathtcp@ietf.org, ietf@kuehlewind.net, nishida@sfc.wide.ad.jp, mptcp-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.79.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152524500562.11177.5615795684336347872.idtracker@ietfa.amsl.com>
Date: Wed, 02 May 2018 00:10:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/4oGDLgO08Gz1rXdteRo8Zf7n934>
Subject: [multipathtcp] mptcp - New Meeting Session Request for IETF 102
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 02 May 2018 07:10:06 -0000

A new meeting session request has just been submitted by Yoshifumi Nishida, a Chair of the mptcp working group.


---------------------------------------------------------
Working Group Name: Multipath TCP
Area Name: Transport Area
Session Requester: Yoshifumi Nishida

Number of Sessions: 1
Length of Session(s):  1.5 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 First Priority: ippm tcpinc tcpm tsvarea tsvwg tls
 Second Priority: taps iccrg rtcweb manet dmm
 Third Priority: nfvrg quic maprg


People who must be present:
  Yoshifumi Nishida
  Philip Eardley
  Mirja Kuehlewind

Resources Requested:

Special Requests:
  please avoid any transport area BoFs
---------------------------------------------------------


From nobody Tue May 15 11:39:20 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multipathtcp@ietf.org
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C373612E856; Tue, 15 May 2018 11:39:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: multipathtcp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152640955276.3687.258457311815714168@ietfa.amsl.com>
Date: Tue, 15 May 2018 11:39:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/_RpBF_VKpPIAeTvlKCHCno6Y8bY>
Subject: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-11.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 15 May 2018 18:39:13 -0000

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

        Title           : TCP Extensions for Multipath Operation with Multiple Addresses
        Authors         : Alan Ford
                          Costin Raiciu
                          Mark Handley
                          Olivier Bonaventure
                          Christoph Paasch
	Filename        : draft-ietf-mptcp-rfc6824bis-11.txt
	Pages           : 76
	Date            : 2018-05-15

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

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

   This document specifies v1 of Multipath TCP, obsoleting v0 as
   specified in RFC6824 [RFC6824] through clarifications and
   modifications primarily driven by deployment experience.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11
https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-11

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


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

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


From nobody Tue May 15 11:42:19 2018
Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F6F12E86A for <multipathtcp@ietfa.amsl.com>; Tue, 15 May 2018 11:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 IH1ln3HHRynv for <multipathtcp@ietfa.amsl.com>; Tue, 15 May 2018 11:42:15 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::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 A42EF12E856 for <multipathtcp@ietf.org>; Tue, 15 May 2018 11:42:14 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id p85-v6so1743767lfg.7 for <multipathtcp@ietf.org>; Tue, 15 May 2018 11:42:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=FbicQ0c61yUPfL6jKJX97WPZ1HJfO7RojAK4XeMpGM0=; b=d6cptcD6Oo8tgulxju4tCze7XEaW7V/1Uw9nt/0xtGKw5drLBx6Q/tNYeX3vSJqvaE buLoSVHFirpDK8L8VwvDoXl4f+0WRcmHIXMRicptabno+BLVaPr5RxJjdCCWPq+uF4ph ZCoYTvL4XfdjM9bCzm8tcJeI/D0m7sguHseY+SMf5rL33ft+fuyCAfLMna5YsdRtYJrC L8SW0tqddPtkgniQ0hQlhmweOEk2Is+OGKY/WNUylykI+Vj9CA7XVofmHRf+mqedonAs nuh7IXJaIk9LCDuIxBrxRI0JUe3eGnJ71oxsfpLaf2p3u1eq65FOFIjWIgs+SoLB/VjK tilg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=FbicQ0c61yUPfL6jKJX97WPZ1HJfO7RojAK4XeMpGM0=; b=DhOBLUfa81g8VwlxI4ThMHSH2KmpfMSIJmf9uN2FqySrKCaM/1xC+5uxBaqSDK7giY E74pgA+ImDFskOG2VPBesFk/OnLVDGgwF8Z9B6DQosxYZCEmC7H9Cv/Ibtln2da8nqb6 /cKkcRFKKcrN2ufwJJ7yYSx7e11jbe8lYpGxwUpOlxtWiQX7b1ZBoigBhQ7Y1PQCEpHi mU1+eZoWT0iI8QQleNaWqYwsADsVgdSED8+TgtxdK3OK0YYQ3DMaJePwum/YUljhQ0w+ 4GVrsz7cfK6DAqh+9MG+bejvMZI/Ywd5SwYI0DVuz2bdaadTESvVDInAVqpXcoQWvvdZ /yZw==
X-Gm-Message-State: ALKqPwesacF482n6b5Sw14FijdYBz5joeM2KFQLmgBIDsXZahsgkA0an 3X0tqTVYFjM9hhWIu65o5u/jAlqv
X-Google-Smtp-Source: AB8JxZq+BHOvX7zEtb115fKzoRNZxfM/rlI6yXKsb4OTGySr1tsFyaYaN0BFxKb5eCk11LfcwaddMw==
X-Received: by 2002:a19:e549:: with SMTP id c70-v6mr13346649lfh.65.1526409732496;  Tue, 15 May 2018 11:42:12 -0700 (PDT)
Received: from [192.168.1.66] (160.177.159.143.dyn.plus.net. [143.159.177.160]) by smtp.gmail.com with ESMTPSA id e28-v6sm89232ljb.92.2018.05.15.11.42.11 for <multipathtcp@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 15 May 2018 11:42:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <152640955276.3687.258457311815714168@ietfa.amsl.com>
Date: Tue, 15 May 2018 19:42:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AB20475-9B04-408E-84E6-C16D83A5012D@gmail.com>
References: <152640955276.3687.258457311815714168@ietfa.amsl.com>
To: multipathtcp <multipathtcp@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/OKK0GXvYmLplFHLcCnPVayiYM9o>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-11.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2018 18:42:17 -0000

Hi all,

This update to rfc6824bis acts upon the feedback from IETF101 in London.

Specifically:

- Remove the Experimental option specification on request of Olivier =
(but keeping the option type reserved);
- Move TFO discussion to the Appendix since this is an Experimental =
specification;
- Add some clarification text regarding processing unexpected ACK =
numbers (which came out of the TFO discussion).

Regards,
Alan

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


From nobody Wed May 16 19:36:20 2018
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7526F12E895 for <multipathtcp@ietfa.amsl.com>; Wed, 16 May 2018 19:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBYq2hH0cu-k for <multipathtcp@ietfa.amsl.com>; Wed, 16 May 2018 19:36:15 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D0D612E88B for <multipathtcp@ietf.org>; Wed, 16 May 2018 19:36:14 -0700 (PDT)
Received: from mail-it0-f51.google.com (mail-it0-f51.google.com [209.85.214.51]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 75D9F278340 for <multipathtcp@ietf.org>; Thu, 17 May 2018 11:36:12 +0900 (JST)
Received: by mail-it0-f51.google.com with SMTP id q72-v6so7141961itc.0 for <multipathtcp@ietf.org>; Wed, 16 May 2018 19:36:12 -0700 (PDT)
X-Gm-Message-State: ALKqPweDJYPf+gLOQ4E3iBJQZFVwjKSfon5ERbgjpM000vKKgwx6zgpU pyDGDPqFHEVtGpVR6hYebvJuut5bWL6F754H2G4=
X-Google-Smtp-Source: AB8JxZrpy2hQpiBhxiNBzfgTiAoZSXKpz3VtOnbzElDZbSQJvt6NQohQtKP2P+yteQD+7iDHFclU+DNR3m50Iwe91FY=
X-Received: by 2002:a24:3555:: with SMTP id k82-v6mr802082ita.49.1526524571212;  Wed, 16 May 2018 19:36:11 -0700 (PDT)
MIME-Version: 1.0
References: <152640955276.3687.258457311815714168@ietfa.amsl.com> <3AB20475-9B04-408E-84E6-C16D83A5012D@gmail.com>
In-Reply-To: <3AB20475-9B04-408E-84E6-C16D83A5012D@gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Wed, 16 May 2018 22:35:59 -0400
X-Gmail-Original-Message-ID: <CAO249yfvvanP2pfF5WxGMc6Kmh8M7gr2TTRGhOTv1PYNv8Lrdg@mail.gmail.com>
Message-ID: <CAO249yfvvanP2pfF5WxGMc6Kmh8M7gr2TTRGhOTv1PYNv8Lrdg@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cedff7056c5db2c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/eNIjpBrizz-CN6auv5UDMQ6TpYw>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-11.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 02:36:19 -0000

--000000000000cedff7056c5db2c3
Content-Type: text/plain; charset="UTF-8"

Hi Alan, thanks for the updates!
I just would like to check that this version has addressed all remaining
outstanding comments from authers' point of view.
--
Yoshi

On Tue, May 15, 2018 at 2:42 PM Alan Ford <alan.ford@gmail.com> wrote:

> Hi all,
>
> This update to rfc6824bis acts upon the feedback from IETF101 in London.
>
> Specifically:
>
> - Remove the Experimental option specification on request of Olivier (but
> keeping the option type reserved);
> - Move TFO discussion to the Appendix since this is an Experimental
> specification;
> - Add some clarification text regarding processing unexpected ACK numbers
> (which came out of the TFO discussion).
>
> Regards,
> Alan
>
> > On 15 May 2018, at 19:39, internet-drafts@ietf.org wrote:
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Multipath TCP WG of the IETF.
> >
> >        Title           : TCP Extensions for Multipath Operation with
> Multiple Addresses
> >        Authors         : Alan Ford
> >                          Costin Raiciu
> >                          Mark Handley
> >                          Olivier Bonaventure
> >                          Christoph Paasch
> >       Filename        : draft-ietf-mptcp-rfc6824bis-11.txt
> >       Pages           : 76
> >       Date            : 2018-05-15
> >
> > Abstract:
> >   TCP/IP communication is currently restricted to a single path per
> >   connection, yet multiple paths often exist between peers.  The
> >   simultaneous use of these multiple paths for a TCP/IP session would
> >   improve resource usage within the network and, thus, improve user
> >   experience through higher throughput and improved resilience to
> >   network failure.
> >
> >   Multipath TCP provides the ability to simultaneously use multiple
> >   paths between peers.  This document presents a set of extensions to
> >   traditional TCP to support multipath operation.  The protocol offers
> >   the same type of service to applications as TCP (i.e., reliable
> >   bytestream), and it provides the components necessary to establish
> >   and use multiple TCP flows across potentially disjoint paths.
> >
> >   This document specifies v1 of Multipath TCP, obsoleting v0 as
> >   specified in RFC6824 [RFC6824] through clarifications and
> >   modifications primarily driven by deployment experience.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11
> > https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-11
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-11
> >
> >
> > 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/
> >
> > _______________________________________________
> > 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
>

--000000000000cedff7056c5db2c3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div><div dir=3D"auto">Hi Alan, thanks for the updates!</div></div></d=
iv><div dir=3D"auto">I just would like to check that this version has addre=
ssed all remaining outstanding comments from authers&#39; point of view.=C2=
=A0</div><div dir=3D"auto">--</div><div dir=3D"auto">Yoshi</div><div><div><=
br><div class=3D"gmail_quote"><div>On Tue, May 15, 2018 at 2:42 PM Alan For=
d &lt;<a href=3D"mailto:alan.ford@gmail.com" target=3D"_blank">alan.ford@gm=
ail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
This update to rfc6824bis acts upon the feedback from IETF101 in London.<br=
>
<br>
Specifically:<br>
<br>
- Remove the Experimental option specification on request of Olivier (but k=
eeping the option type reserved);<br>
- Move TFO discussion to the Appendix since this is an Experimental specifi=
cation;<br>
- Add some clarification text regarding processing unexpected ACK numbers (=
which came out of the TFO discussion).<br>
<br>
Regards,<br>
Alan<br>
<br>
&gt; On 15 May 2018, at 19:39, <a href=3D"mailto:internet-drafts@ietf.org" =
target=3D"_blank">internet-drafts@ietf.org</a> wrote:<br>
&gt; <br>
&gt; <br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.<br>
&gt; This draft is a work item of the Multipath TCP WG of the IETF.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: TCP Extensions for Multipath Operation with Multiple Addresses<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: =
Alan Ford<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Costin Raiciu<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Mark Handley<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Olivier Bonaventure<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Christoph Paasch<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-=
ietf-mptcp-rfc6824bis-11.txt<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 76<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : 2018-05-15<br>
&gt; <br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0TCP/IP communication is currently restricted to a single p=
ath per<br>
&gt;=C2=A0 =C2=A0connection, yet multiple paths often exist between peers.=
=C2=A0 The<br>
&gt;=C2=A0 =C2=A0simultaneous use of these multiple paths for a TCP/IP sess=
ion would<br>
&gt;=C2=A0 =C2=A0improve resource usage within the network and, thus, impro=
ve user<br>
&gt;=C2=A0 =C2=A0experience through higher throughput and improved resilien=
ce to<br>
&gt;=C2=A0 =C2=A0network failure.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0Multipath TCP provides the ability to simultaneously use m=
ultiple<br>
&gt;=C2=A0 =C2=A0paths between peers.=C2=A0 This document presents a set of=
 extensions to<br>
&gt;=C2=A0 =C2=A0traditional TCP to support multipath operation.=C2=A0 The =
protocol offers<br>
&gt;=C2=A0 =C2=A0the same type of service to applications as TCP (i.e., rel=
iable<br>
&gt;=C2=A0 =C2=A0bytestream), and it provides the components necessary to e=
stablish<br>
&gt;=C2=A0 =C2=A0and use multiple TCP flows across potentially disjoint pat=
hs.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0This document specifies v1 of Multipath TCP, obsoleting v0=
 as<br>
&gt;=C2=A0 =C2=A0specified in RFC6824 [RFC6824] through clarifications and<=
br>
&gt;=C2=A0 =C2=A0modifications primarily driven by deployment experience.<b=
r>
&gt; <br>
&gt; <br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bi=
s/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-mptcp-rfc6824bis/</a><br>
&gt; <br>
&gt; There are also htmlized versions available at:<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-iet=
f-mptcp-rfc6824bis-11</a><br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6=
824bis-11" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/html/draft-ietf-mptcp-rfc6824bis-11</a><br>
&gt; <br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc682=
4bis-11" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
url2=3Ddraft-ietf-mptcp-rfc6824bis-11</a><br>
&gt; <br>
&gt; <br>
&gt; Please note that it may take a couple of minutes from the time of subm=
ission<br>
&gt; until the htmlized version and diff are available at <a href=3D"http:/=
/tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<b=
r>
&gt; <br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" tar=
get=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; multipathtcp mailing list<br>
&gt; <a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">multipathtc=
p@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/multipa=
thtcp</a><br>
<br>
_______________________________________________<br>
multipathtcp mailing list<br>
<a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">multipathtcp@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/multipathtcp=
</a><br>
</blockquote></div></div></div>

--000000000000cedff7056c5db2c3--


From nobody Thu May 17 11:34:56 2018
Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A2E12E88C for <multipathtcp@ietfa.amsl.com>; Thu, 17 May 2018 11:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cbOamyC8HE5O for <multipathtcp@ietfa.amsl.com>; Thu, 17 May 2018 11:34:52 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 D75C812D94A for <multipathtcp@ietf.org>; Thu, 17 May 2018 11:34:51 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id h197-v6so10193052lfg.11 for <multipathtcp@ietf.org>; Thu, 17 May 2018 11:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=GerJCT4Wj+S6ub4hgX2L+cqrhEURpEDYvHgdAq83dmo=; b=tMxdDLn2HDbJUHCtwAspBUSO2/Y2XykB3/fISMw6OTzucfAf/XogOkfxeiU7PX/uEg 9ykpzybh6hRdRAWtPlYULsE1ydM2LbL6uAUIEy76MkbO6kNQvl+1rdGW3u8jPLUjfkEb uQ+8VK3yTrN+PfUoYz0MZmsNzUDHFfFuYDOyVjZgRo/HYdHRtFaepVy3lRGXRYbgMiE5 QYx6fQ92BH2EqRtXtexdwhzFWf2uxFTAnh3SY8G1wrYk6c3bbiuH/OXND1WpwdMOPSeW Dbh3AbMtLjpVJNfmOcaXEew2pLjFikI4ai3ScMemGHvyz2K5lyJgwxIfw6CxyXEsXAC/ UrYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=GerJCT4Wj+S6ub4hgX2L+cqrhEURpEDYvHgdAq83dmo=; b=cjCPNiBDgmMyaYtFLce+va/oMZvsc69dZJcohNPgMiVfQYMBdKjymFFU4T2QuAHut6 zTEb+cgxd58yMR043AP9EHa9hcTrm8hpHqqBW0zdRnBnXWrZRrOYJD0pFDGiglEGweQD IypGluVOeaVY1tHgRaTr3fsRAWtUARCZeRMzG4SQv3uUfroFBQya/4/Xk0qz1iUA44si 0jqrvzz+W+u4R4BN6Pk6PwxYLTvQe0pg5GTMkJPsv91fQMoec0oSf/5HYYNZgyzYIChD N+WDQXaJ4hle3Kt4Kj3rKZnzCLWxUkSCa1CiJTbrtVYaEFfoefHNICfLj0QFdRVKWYAk rT1w==
X-Gm-Message-State: ALKqPwecytZ6/WQVq/6Tx83AalMCBwPkYXR74rZytvQCFIMv9um0s3jm p9LytDQJQcZFKcAhJMRovsMkQmpe
X-Google-Smtp-Source: AB8JxZqIqMNNgDzyY+pcrPz9j/yj3wsvLj8/t4Epbyj2G2mR1J+H/SqTLfPNAgp4D9yyT3vP+6tuPw==
X-Received: by 2002:a2e:944d:: with SMTP id o13-v6mr3916952ljh.65.1526582090048;  Thu, 17 May 2018 11:34:50 -0700 (PDT)
Received: from [192.168.1.66] (160.177.159.143.dyn.plus.net. [143.159.177.160]) by smtp.gmail.com with ESMTPSA id p21-v6sm1368659lfc.70.2018.05.17.11.34.48 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 17 May 2018 11:34:49 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_504103E2-5B13-4E91-8442-FF0E9C405881"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <CAO249yfvvanP2pfF5WxGMc6Kmh8M7gr2TTRGhOTv1PYNv8Lrdg@mail.gmail.com>
Date: Thu, 17 May 2018 19:34:46 +0100
Cc: multipathtcp <multipathtcp@ietf.org>
Message-Id: <2405342D-A592-4201-96FC-3596D00EE945@gmail.com>
References: <152640955276.3687.258457311815714168@ietfa.amsl.com> <3AB20475-9B04-408E-84E6-C16D83A5012D@gmail.com> <CAO249yfvvanP2pfF5WxGMc6Kmh8M7gr2TTRGhOTv1PYNv8Lrdg@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/rcMbAipS9C2T-nRSoHSSdXInJ9I>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-11.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 18:34:55 -0000

--Apple-Mail=_504103E2-5B13-4E91-8442-FF0E9C405881
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Yoshi,

Yes, I am not aware of any other outstanding concerns from the author =
side, nor any that we have been made aware of.

If anyone in the WG feels we have missed any comments made in IETF101 or =
otherwise, please shout!

Best regards,
Alan

> On 17 May 2018, at 03:35, Yoshifumi Nishida <nishida@sfc.wide.ad.jp> =
wrote:
>=20
> Hi Alan, thanks for the updates!
> I just would like to check that this version has addressed all =
remaining outstanding comments from authers' point of view.=20
> --
> Yoshi
>=20
> On Tue, May 15, 2018 at 2:42 PM Alan Ford <alan.ford@gmail.com =
<mailto:alan.ford@gmail.com>> wrote:
> Hi all,
>=20
> This update to rfc6824bis acts upon the feedback from IETF101 in =
London.
>=20
> Specifically:
>=20
> - Remove the Experimental option specification on request of Olivier =
(but keeping the option type reserved);
> - Move TFO discussion to the Appendix since this is an Experimental =
specification;
> - Add some clarification text regarding processing unexpected ACK =
numbers (which came out of the TFO discussion).
>=20
> Regards,
> Alan
>=20
> > On 15 May 2018, at 19:39, internet-drafts@ietf.org =
<mailto:internet-drafts@ietf.org> wrote:
> >=20
> >=20
> > A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> > This draft is a work item of the Multipath TCP WG of the IETF.
> >=20
> >        Title           : TCP Extensions for Multipath Operation with =
Multiple Addresses
> >        Authors         : Alan Ford
> >                          Costin Raiciu
> >                          Mark Handley
> >                          Olivier Bonaventure
> >                          Christoph Paasch
> >       Filename        : draft-ietf-mptcp-rfc6824bis-11.txt
> >       Pages           : 76
> >       Date            : 2018-05-15
> >=20
> > Abstract:
> >   TCP/IP communication is currently restricted to a single path per
> >   connection, yet multiple paths often exist between peers.  The
> >   simultaneous use of these multiple paths for a TCP/IP session =
would
> >   improve resource usage within the network and, thus, improve user
> >   experience through higher throughput and improved resilience to
> >   network failure.
> >=20
> >   Multipath TCP provides the ability to simultaneously use multiple
> >   paths between peers.  This document presents a set of extensions =
to
> >   traditional TCP to support multipath operation.  The protocol =
offers
> >   the same type of service to applications as TCP (i.e., reliable
> >   bytestream), and it provides the components necessary to establish
> >   and use multiple TCP flows across potentially disjoint paths.
> >=20
> >   This document specifies v1 of Multipath TCP, obsoleting v0 as
> >   specified in RFC6824 [RFC6824] through clarifications and
> >   modifications primarily driven by deployment experience.
> >=20
> >=20
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/ =
<https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/>
> >=20
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11 =
<https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11>
> > https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-11 =
<https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-11>
> >=20
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-11 =
<https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-11>
> >=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 =
<http://tools.ietf.org/>.
> >=20
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/ =
<ftp://ftp.ietf.org/internet-drafts/>
> >=20
> > _______________________________________________
> > multipathtcp mailing list
> > multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> > https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>
>=20
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org <mailto:multipathtcp@ietf.org>
> https://www.ietf.org/mailman/listinfo/multipathtcp =
<https://www.ietf.org/mailman/listinfo/multipathtcp>


--Apple-Mail=_504103E2-5B13-4E91-8442-FF0E9C405881
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Yoshi,<div class=3D""><br class=3D""></div><div =
class=3D"">Yes, I am not aware of any other outstanding concerns from =
the author side, nor any that we have been made aware of.</div><div =
class=3D""><div><br class=3D""></div><div>If anyone in the WG feels we =
have missed any comments made in IETF101 or otherwise, please =
shout!</div><div><br class=3D""></div><div>Best =
regards,</div><div>Alan</div><div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D"">On 17 May 2018, at 03:35, Yoshifumi Nishida =
&lt;<a href=3D"mailto:nishida@sfc.wide.ad.jp" =
class=3D"">nishida@sfc.wide.ad.jp</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><div =
class=3D""><div dir=3D"auto" class=3D"">Hi Alan, thanks for the =
updates!</div></div></div><div dir=3D"auto" class=3D"">I just would like =
to check that this version has addressed all remaining outstanding =
comments from authers' point of view.&nbsp;</div><div dir=3D"auto" =
class=3D"">--</div><div dir=3D"auto" class=3D"">Yoshi</div><div =
class=3D""><div class=3D""><br class=3D""><div class=3D"gmail_quote"><div =
class=3D"">On Tue, May 15, 2018 at 2:42 PM Alan Ford &lt;<a =
href=3D"mailto:alan.ford@gmail.com" target=3D"_blank" =
class=3D"">alan.ford@gmail.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br class=3D"">
<br class=3D"">
This update to rfc6824bis acts upon the feedback from IETF101 in =
London.<br class=3D"">
<br class=3D"">
Specifically:<br class=3D"">
<br class=3D"">
- Remove the Experimental option specification on request of Olivier =
(but keeping the option type reserved);<br class=3D"">
- Move TFO discussion to the Appendix since this is an Experimental =
specification;<br class=3D"">
- Add some clarification text regarding processing unexpected ACK =
numbers (which came out of the TFO discussion).<br class=3D"">
<br class=3D"">
Regards,<br class=3D"">
Alan<br class=3D"">
<br class=3D"">
&gt; On 15 May 2018, at 19:39, <a href=3D"mailto:internet-drafts@ietf.org"=
 target=3D"_blank" class=3D"">internet-drafts@ietf.org</a> wrote:<br =
class=3D"">
&gt; <br class=3D"">
&gt; <br class=3D"">
&gt; A New Internet-Draft is available from the on-line Internet-Drafts =
directories.<br class=3D"">
&gt; This draft is a work item of the Multipath TCP WG of the IETF.<br =
class=3D"">
&gt; <br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;: TCP Extensions for Multipath Operation with Multiple =
Addresses<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; Authors&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;: Alan Ford<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; Costin Raiciu<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; Mark Handley<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; Olivier Bonaventure<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; Christoph Paasch<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp;Filename&nbsp; &nbsp; &nbsp; &nbsp; : =
draft-ietf-mptcp-rfc6824bis-11.txt<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp;Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;: 76<br class=3D"">
&gt;&nbsp; &nbsp; &nbsp; &nbsp;Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; : 2018-05-15<br class=3D"">
&gt; <br class=3D"">
&gt; Abstract:<br class=3D"">
&gt;&nbsp; &nbsp;TCP/IP communication is currently restricted to a =
single path per<br class=3D"">
&gt;&nbsp; &nbsp;connection, yet multiple paths often exist between =
peers.&nbsp; The<br class=3D"">
&gt;&nbsp; &nbsp;simultaneous use of these multiple paths for a TCP/IP =
session would<br class=3D"">
&gt;&nbsp; &nbsp;improve resource usage within the network and, thus, =
improve user<br class=3D"">
&gt;&nbsp; &nbsp;experience through higher throughput and improved =
resilience to<br class=3D"">
&gt;&nbsp; &nbsp;network failure.<br class=3D"">
&gt; <br class=3D"">
&gt;&nbsp; &nbsp;Multipath TCP provides the ability to simultaneously =
use multiple<br class=3D"">
&gt;&nbsp; &nbsp;paths between peers.&nbsp; This document presents a set =
of extensions to<br class=3D"">
&gt;&nbsp; &nbsp;traditional TCP to support multipath operation.&nbsp; =
The protocol offers<br class=3D"">
&gt;&nbsp; &nbsp;the same type of service to applications as TCP (i.e., =
reliable<br class=3D"">
&gt;&nbsp; &nbsp;bytestream), and it provides the components necessary =
to establish<br class=3D"">
&gt;&nbsp; &nbsp;and use multiple TCP flows across potentially disjoint =
paths.<br class=3D"">
&gt; <br class=3D"">
&gt;&nbsp; &nbsp;This document specifies v1 of Multipath TCP, obsoleting =
v0 as<br class=3D"">
&gt;&nbsp; &nbsp;specified in RFC6824 [RFC6824] through clarifications =
and<br class=3D"">
&gt;&nbsp; &nbsp;modifications primarily driven by deployment =
experience.<br class=3D"">
&gt; <br class=3D"">
&gt; <br class=3D"">
&gt; The IETF datatracker status page for this draft is:<br class=3D"">
&gt; <a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/</=
a><br class=3D"">
&gt; <br class=3D"">
&gt; There are also htmlized versions available at:<br class=3D"">
&gt; <a =
href=3D"https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-11</a><=
br class=3D"">
&gt; <a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-=
11" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824b=
is-11</a><br class=3D"">
&gt; <br class=3D"">
&gt; A diff from the previous version is available at:<br class=3D"">
&gt; <a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-11=
" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis=
-11</a><br class=3D"">
&gt; <br class=3D"">
&gt; <br class=3D"">
&gt; Please note that it may take a couple of minutes from the time of =
submission<br class=3D"">
&gt; until the htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org/" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">tools.ietf.org</a>.<br class=3D"">
&gt; <br class=3D"">
&gt; Internet-Drafts are also available by anonymous FTP at:<br =
class=3D"">
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">ftp://ftp.ietf.org/internet-drafts/</a><br =
class=3D"">
&gt; <br class=3D"">
&gt; _______________________________________________<br class=3D"">
&gt; multipathtcp mailing list<br class=3D"">
&gt; <a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a><br class=3D"">
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br =
class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
multipathtcp mailing list<br class=3D"">
<a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank" =
class=3D"">multipathtcp@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/multipathtcp</a><br =
class=3D"">
</blockquote></div></div></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_504103E2-5B13-4E91-8442-FF0E9C405881--

