
From nobody Wed Oct  3 07:23:37 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 DB16A13129E; Wed,  3 Oct 2018 07:23:35 -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.85.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: multipathtcp@ietf.org
Message-ID: <153857661587.9120.4590608359579290440@ietfa.amsl.com>
Date: Wed, 03 Oct 2018 07:23:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/qRMAhEal33Z_UJ0fnsWmxuMn0PA>
Subject: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 14:23:36 -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-12.txt
	Pages           : 80
	Date            : 2018-10-03

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-12
https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-12

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


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 Wed Oct  3 07:25:49 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 CF7371312B3 for <multipathtcp@ietfa.amsl.com>; Wed,  3 Oct 2018 07:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 wWGFxtFHm1Pq for <multipathtcp@ietfa.amsl.com>; Wed,  3 Oct 2018 07:25:45 -0700 (PDT)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 6A67B1312AC for <multipathtcp@ietf.org>; Wed,  3 Oct 2018 07:25:45 -0700 (PDT)
Received: by mail-wm1-x335.google.com with SMTP id z25-v6so7799082wmf.1 for <multipathtcp@ietf.org>; Wed, 03 Oct 2018 07:25:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=bNAnBQHGlGlwpC8ot/mv3HaHqFpwsaOsUVfytq9LJTw=; b=nlyuJ7fl8omzABD3UborJsWJnoIW9wUpqFLT/AiE1//thX6bbyXTyIG06/uEeedG7P oJCnhhW1lLEZ72pGd0RlnTBldjp81LNKfb8M/OMG8gWjPm5BtpnlJJ5yPkyR4H7cOl8k 841HagYiNC+bE/anTmEQdtB1vzqh3Ya0yaIEGnWzL2BSBO9VicGq2NQYb2hQh2qIBEpr +WaKvWK8//24WPQx2LkA8r+rw16mqdGJdA0GQUQA8d6a4s7o9/9Cp+YaD/96xu2zXgUg Jww3ZozR2JvC9JM05yDU9CSAjwsXM3CJ/nTbCWqbiMQbDnX65KWdtXZ4Sl3Vnlu3Xrhi SLYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=bNAnBQHGlGlwpC8ot/mv3HaHqFpwsaOsUVfytq9LJTw=; b=pwBgJQX2kKOVpAA2nSX/gQST2e8bkjuXHDEoZ52zCgGZ61L4MUv0b6aBAvVWwNOezL jeO33WLdJDt2+j+L/cehX74Wu/nqhOiOfiUhg4QvpWKhG6UJUsCylJYQ1BONXPBHy8Z7 eZ4Fjk5BBYQJppzeY34RRJ1XpIrronnD9Wz4TXqWsR82MaITuLBQdBCaN6nmTIDfyabt gL54/bOOKe7ztFBTKxThnU6UA5i2A+7CsSzp6cg+7T1iIHdj3kENx7z+higMBNN6Uav0 7FlfOrGAgAVbXdugmtZ6baBJ9ICHCtR5uWzGxxf8xDNoCiBbrKydOkj3I4bkf9a4mDh0 Ut0g==
X-Gm-Message-State: ABuFfogmf6lV4xSB6QfIUwe+tpgyUvfFKPvkw9V+VlF5yHm0PpNvZk9C TpN0/KtAAHQ4dM26EMIoZ6azrLur
X-Google-Smtp-Source: ACcGV60lAs0sKJgJojd+0JBrU1JFNNLt25Jyhf/PMbmGmXf5sHZXebT686GhsGTkg/ULQVgnRoitcQ==
X-Received: by 2002:a1c:90d0:: with SMTP id s199-v6mr1595351wmd.45.1538576743561;  Wed, 03 Oct 2018 07:25:43 -0700 (PDT)
Received: from alans-mbp.lan ([83.216.156.250]) by smtp.gmail.com with ESMTPSA id x186-v6sm3680441wmx.24.2018.10.03.07.25.42 for <multipathtcp@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Oct 2018 07:25:42 -0700 (PDT)
From: Alan Ford <alan.ford@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 3 Oct 2018 15:25:41 +0100
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com>
To: multipathtcp <multipathtcp@ietf.org>
In-Reply-To: <153857661587.9120.4590608359579290440@ietfa.amsl.com>
Message-Id: <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/Q6bC98QaTmsVV-9zRMfvrCVmC5k>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Oct 2018 14:25:48 -0000

Hi all,

I believe this new version addresses all last call/review comments we =
received for rfc6824bis, with the exception of adding a possible =
=E2=80=9Cchanges since RFC6824=E2=80=9D section.

Could all reviewers please check this new version and ensure we have =
handled your review comments appropriately?

Many thanks,
Alan

> On 3 Oct 2018, at 15:23, 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-12.txt
> 	Pages           : 80
> 	Date            : 2018-10-03
>=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-12
> https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-12
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-12
>=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 Thu Oct  4 08:53:36 2018
Return-Path: <x.defoy.ietf@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 6EBDD130E6F for <multipathtcp@ietfa.amsl.com>; Thu,  4 Oct 2018 08:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-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 uLv6lNvf7dVK for <multipathtcp@ietfa.amsl.com>; Thu,  4 Oct 2018 08:53:32 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 CA598130E63 for <multipathtcp@ietf.org>; Thu,  4 Oct 2018 08:53:31 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id y10-v6so7174662lfj.1 for <multipathtcp@ietf.org>; Thu, 04 Oct 2018 08:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aCGLwd4If8DM75rOaVeFJxrs6cqIPbRjqWW87tabYwc=; b=sh68yo4Hxd57AgxCaxMGX1b81PVbe65gpSMjaNzce3PHtYt4T+k/tZw6MAQykzouXc KZoIut+iXMOJBZeZJd40e8iecITrfJ6YYf21fOMaFptzUhPshLV4cYnPv9W0oOdEi36b HM4vMTbnG7AOUI54Wn7LK93C2NpGoozeZWFN4hHPL+Qw7iCInOC7fdxfw84hT7Pk67Qf cJS+3OXNbrfTMcVI3YU0rO6NtfrkiwY5vke1FN6sn+TV9RWizRZ5+kMPooBbKPhnWjlz 21azm5gJtFeq7SpopUZQ94XJV9o5enTkeC6zrHv1m9dtKQ83YdQkGkXNHyhsNnHunkSe gZww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aCGLwd4If8DM75rOaVeFJxrs6cqIPbRjqWW87tabYwc=; b=snAtf2J/3cgz9XuPWni6ypl8GNcyspRBfzvqhY9LOA+RsIBa856e29NYwZrktu9Ui6 qJ6HgkY6mjLfMyuilTyceQwnSRiz5gBWUZimcYI3OWrmf2yKxfH39RiV192+HqYWtBHl TbPgBcTHYs3stBSzFWp3RvoIHG9krqG7N2uvNW7Wk9DMOucEDDseBV9WCocGhUKyCjwx LmEKyjdx6mQ38VPU4ZeR5lUD8OmXfV7RnJ4WTfzgPXRAiVqbdGAryi9HEyq4mzYoq8lJ juXxugE+tXFZ8oHDq9ckbMPEJtrPuhLeCdhwVG9dPd6SLRckd6QnGrRQUC9F5GJ9KuXQ mWkQ==
X-Gm-Message-State: ABuFfohaexNuOZBinDhi1CttzVMer4+aA/0gvj6xvQ/7OPCLYZ0gMAG/ zqXSx2FyScWvDxVbDvADG6Y1LPMwJ71rRgcSpRU=
X-Google-Smtp-Source: ACcGV619K2I1evaFJ1rUFK4tTIWNsIZIq/SLSJrPHgI1XP5Htoprs+4VfeDc2rtSu4xX81ABvi1k0k0j5+87ynwYVfk=
X-Received: by 2002:a19:1588:: with SMTP id 8-v6mr4397203lfv.36.1538668409962;  Thu, 04 Oct 2018 08:53:29 -0700 (PDT)
MIME-Version: 1.0
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com> <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
In-Reply-To: <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
From: Xavier de Foy <x.defoy.ietf@gmail.com>
Date: Thu, 4 Oct 2018 11:53:16 -0400
Message-ID: <CAHYjOTbjsWQQcbqey=t7RpUDT7qo87jo0gE-aGZmtQir3ynqsw@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000000c3df05776928b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/rtnlG6jGMGysCDFP_EQj_ipJPDc>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Oct 2018 15:53:34 -0000

--00000000000000c3df05776928b4
Content-Type: text/plain; charset="UTF-8"

Thanks Alan,

Could all reviewers please check this new version and ensure we have
> handled your review comments appropriately?
>

Yes, I think my review comments have been handled appropriately.
Best Regards,
Xavier.

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

<div dir=3D"ltr"><div>Thanks Alan,</div><div><br></div><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
Could all reviewers please check this new version and ensure we have handle=
d your review comments appropriately?<br></blockquote></div><div class=3D"g=
mail_quote"><br></div><div class=3D"gmail_quote">Yes, I think my review com=
ments have been handled appropriately.</div><div class=3D"gmail_quote">Best=
 Regards,</div><div class=3D"gmail_quote">Xavier.<br></div></div>

--00000000000000c3df05776928b4--


From nobody Mon Oct  8 06:49:32 2018
Return-Path: <rahul.jadhav@huawei.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 045D3130DC0 for <multipathtcp@ietfa.amsl.com>; Mon,  8 Oct 2018 06:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ux3_o-fyFHUo for <multipathtcp@ietfa.amsl.com>; Mon,  8 Oct 2018 06:49:26 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 27C4712F1A5 for <multipathtcp@ietf.org>; Mon,  8 Oct 2018 06:49:26 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 7C2EBC10C0886 for <multipathtcp@ietf.org>; Mon,  8 Oct 2018 14:49:22 +0100 (IST)
Received: from BLREML407-HUB.china.huawei.com (10.20.4.45) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.399.0; Mon, 8 Oct 2018 14:49:18 +0100
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.224]) by BLREML407-HUB.china.huawei.com ([10.20.4.45]) with mapi id 14.03.0399.000; Mon, 8 Oct 2018 19:19:09 +0530
From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
To: Alan Ford <alan.ford@gmail.com>, multipathtcp <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
Thread-Index: AQHUWyS1tUifss7J80qV8iz2l/pvMaUNN2+AgAgkreA=
Date: Mon, 8 Oct 2018 13:49:09 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5DCBF6F0@BLREML503-MBX.china.huawei.com>
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com> <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
In-Reply-To: <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
Accept-Language: en-IN, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.157.44]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/qN0Mzr3juwy_mXn_5IaD0Bt_gis>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Oct 2018 13:49:30 -0000

SGVsbG8gQWxhbiwNCg0KTW9zdCBvZiBteSBjb21tZW50cyBmcm9tIFsxXSBhcmUgaGFuZGxlZC4g
VGhhbmsgeW91Lg0KDQpTb21lIGNvbW1lbnRzIGJhc2VkIG9uIHRoZSB1cGRhdGVkIHRleHQ6DQox
LiBBY2NlcHRlZCBjb21tZW50IzggaW4gWzFdIGRvZXMgbm90IHNlZW0gdG8gYmUgaGFuZGxlZC4g
SSB0aGluayBpdCBpcyBpbXBvcnRhbnQgdG8gYmUgY2xhcmlmaWVkIHRoYXQgdGhlIHZhbHVlIG9m
ICJBZGRyZXNzIElEIiBoYXMgc2lnbmlmaWNhbmNlIG5vdCBvbmx5IHdpdGhpbiBhIHNpbmdsZSBj
b25uZWN0aW9uIGJ1dCBhbHNvIG9ubHkgb24gdGhlIHBlZXIgd2hvIGdlbmVyYXRlcyB0aGUgSUQu
IFRodXMgaXQgaXMgcG9zc2libGUgZm9yIHBlZXJzIHRvIGdlbmVyYXRlIHRoZSBzYW1lIEFkZHJl
c3MgSUQgd2l0aGluIGEgY29ubmVjdGlvbiBhcyB3ZWxsLg0KMi4gVGhhbmsgeW91IGZvciByZW1v
dmluZyB0aGUgdGVybSAicGFzc2l2ZSBvcGVuZXIiIHRocm91Z2hvdXQgdGhlIGRvY3VtZW50LiBU
aGUgbmV3IHRleHQgaXMgbXVjaCBlYXNpZXIgdG8gdW5kZXJzdGFuZC4NCjMuIExvb2tzIGxpa2Ug
Y29tbWVudCMyIGZvciBleHBsaWNpdGx5IG1lbnRpb25pbmcgdGhlIFJlYXNvbiBDb2RlIGZvciBN
UF9UQ1BSU1Qgd2FzIG5vdCBhY2NlcHRlZC4gSSB1bmRlcnN0YW5kIHdlIGhhdmVu4oCZdCByZWFs
bHkgZ290IGFueSBmZWVkYmFjayBmcm9tIHRoZSBXRyBvbiB0aGlzIHBvaW50IGJ1dCB0aGVuIEkg
ZmVlbCBpdCBpcyBuZWNlc3NhcnkgdG8gZG8gdGhpcy4NCjQuICJtYWtlLWJlZm9yZS1icmVhayBz
ZXNzaW9uIiB0ZXJtIGlzIGludHJvZHVjZWQgYWZ0ZXIgcmV3b3JkaW5nIC4uLiBJIGZlZWwgdGhp
cyB0ZXJtIHNob3VsZCBiZSBleHBsYWluZWQgaW4gdGVybWlub2xvZ3kgc2VjdGlvbi4NCg0KQmVz
dCwNClJhaHVsDQoNClsxXSBodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL211
bHRpcGF0aHRjcC9ocHNxaWZiUjAweFJXSk5aZS1DWVI3VXRUeVUNCg0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IG11bHRpcGF0aHRjcCBbbWFpbHRvOm11bHRpcGF0aHRj
cC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4gQWxhbiBGb3JkDQo+IFNlbnQ6IDAz
IE9jdG9iZXIgMjAxOCAxOTo1Ng0KPiBUbzogbXVsdGlwYXRodGNwIDxtdWx0aXBhdGh0Y3BAaWV0
Zi5vcmc+DQo+IFN1YmplY3Q6IFJlOiBbbXVsdGlwYXRodGNwXSBJLUQgQWN0aW9uOiBkcmFmdC1p
ZXRmLW1wdGNwLXJmYzY4MjRiaXMtMTIudHh0DQo+IA0KPiBIaSBhbGwsDQo+IA0KPiBJIGJlbGll
dmUgdGhpcyBuZXcgdmVyc2lvbiBhZGRyZXNzZXMgYWxsIGxhc3QgY2FsbC9yZXZpZXcgY29tbWVu
dHMgd2UNCj4gcmVjZWl2ZWQgZm9yIHJmYzY4MjRiaXMsIHdpdGggdGhlIGV4Y2VwdGlvbiBvZiBh
ZGRpbmcgYSBwb3NzaWJsZSDigJxjaGFuZ2VzDQo+IHNpbmNlIFJGQzY4MjTigJ0gc2VjdGlvbi4N
Cj4gDQo+IENvdWxkIGFsbCByZXZpZXdlcnMgcGxlYXNlIGNoZWNrIHRoaXMgbmV3IHZlcnNpb24g
YW5kIGVuc3VyZSB3ZSBoYXZlDQo+IGhhbmRsZWQgeW91ciByZXZpZXcgY29tbWVudHMgYXBwcm9w
cmlhdGVseT8NCj4gDQo+IE1hbnkgdGhhbmtzLA0KPiBBbGFuDQo+IA0KPiA+IE9uIDMgT2N0IDIw
MTgsIGF0IDE1OjIzLCBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgd3JvdGU6DQo+ID4NCj4gPg0K
PiA+IEEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIElu
dGVybmV0LURyYWZ0cw0KPiBkaXJlY3Rvcmllcy4NCj4gPiBUaGlzIGRyYWZ0IGlzIGEgd29yayBp
dGVtIG9mIHRoZSBNdWx0aXBhdGggVENQIFdHIG9mIHRoZSBJRVRGLg0KPiA+DQo+ID4gICAgICAg
IFRpdGxlICAgICAgICAgICA6IFRDUCBFeHRlbnNpb25zIGZvciBNdWx0aXBhdGggT3BlcmF0aW9u
IHdpdGggTXVsdGlwbGUNCj4gQWRkcmVzc2VzDQo+ID4gICAgICAgIEF1dGhvcnMgICAgICAgICA6
IEFsYW4gRm9yZA0KPiA+ICAgICAgICAgICAgICAgICAgICAgICAgICBDb3N0aW4gUmFpY2l1DQo+
ID4gICAgICAgICAgICAgICAgICAgICAgICAgIE1hcmsgSGFuZGxleQ0KPiA+ICAgICAgICAgICAg
ICAgICAgICAgICAgICBPbGl2aWVyIEJvbmF2ZW50dXJlDQo+ID4gICAgICAgICAgICAgICAgICAg
ICAgICAgIENocmlzdG9waCBQYWFzY2gNCj4gPiAJRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0
Zi1tcHRjcC1yZmM2ODI0YmlzLTEyLnR4dA0KPiA+IAlQYWdlcyAgICAgICAgICAgOiA4MA0KPiA+
IAlEYXRlICAgICAgICAgICAgOiAyMDE4LTEwLTAzDQo+ID4NCj4gPiBBYnN0cmFjdDoNCj4gPiAg
IFRDUC9JUCBjb21tdW5pY2F0aW9uIGlzIGN1cnJlbnRseSByZXN0cmljdGVkIHRvIGEgc2luZ2xl
IHBhdGggcGVyDQo+ID4gICBjb25uZWN0aW9uLCB5ZXQgbXVsdGlwbGUgcGF0aHMgb2Z0ZW4gZXhp
c3QgYmV0d2VlbiBwZWVycy4gIFRoZQ0KPiA+ICAgc2ltdWx0YW5lb3VzIHVzZSBvZiB0aGVzZSBt
dWx0aXBsZSBwYXRocyBmb3IgYSBUQ1AvSVAgc2Vzc2lvbiB3b3VsZA0KPiA+ICAgaW1wcm92ZSBy
ZXNvdXJjZSB1c2FnZSB3aXRoaW4gdGhlIG5ldHdvcmsgYW5kLCB0aHVzLCBpbXByb3ZlIHVzZXIN
Cj4gPiAgIGV4cGVyaWVuY2UgdGhyb3VnaCBoaWdoZXIgdGhyb3VnaHB1dCBhbmQgaW1wcm92ZWQg
cmVzaWxpZW5jZSB0bw0KPiA+ICAgbmV0d29yayBmYWlsdXJlLg0KPiA+DQo+ID4gICBNdWx0aXBh
dGggVENQIHByb3ZpZGVzIHRoZSBhYmlsaXR5IHRvIHNpbXVsdGFuZW91c2x5IHVzZSBtdWx0aXBs
ZQ0KPiA+ICAgcGF0aHMgYmV0d2VlbiBwZWVycy4gIFRoaXMgZG9jdW1lbnQgcHJlc2VudHMgYSBz
ZXQgb2YgZXh0ZW5zaW9ucyB0bw0KPiA+ICAgdHJhZGl0aW9uYWwgVENQIHRvIHN1cHBvcnQgbXVs
dGlwYXRoIG9wZXJhdGlvbi4gIFRoZSBwcm90b2NvbCBvZmZlcnMNCj4gPiAgIHRoZSBzYW1lIHR5
cGUgb2Ygc2VydmljZSB0byBhcHBsaWNhdGlvbnMgYXMgVENQIChpLmUuLCByZWxpYWJsZQ0KPiA+
ICAgYnl0ZXN0cmVhbSksIGFuZCBpdCBwcm92aWRlcyB0aGUgY29tcG9uZW50cyBuZWNlc3Nhcnkg
dG8gZXN0YWJsaXNoDQo+ID4gICBhbmQgdXNlIG11bHRpcGxlIFRDUCBmbG93cyBhY3Jvc3MgcG90
ZW50aWFsbHkgZGlzam9pbnQgcGF0aHMuDQo+ID4NCj4gPiAgIFRoaXMgZG9jdW1lbnQgc3BlY2lm
aWVzIHYxIG9mIE11bHRpcGF0aCBUQ1AsIG9ic29sZXRpbmcgdjAgYXMNCj4gPiAgIHNwZWNpZmll
ZCBpbiBSRkM2ODI0IFtSRkM2ODI0XSB0aHJvdWdoIGNsYXJpZmljYXRpb25zIGFuZA0KPiA+ICAg
bW9kaWZpY2F0aW9ucyBwcmltYXJpbHkgZHJpdmVuIGJ5IGRlcGxveW1lbnQgZXhwZXJpZW5jZS4N
Cj4gPg0KPiA+DQo+ID4gVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMg
ZHJhZnQgaXM6DQo+ID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0
Zi1tcHRjcC1yZmM2ODI0YmlzLw0KPiA+DQo+ID4gVGhlcmUgYXJlIGFsc28gaHRtbGl6ZWQgdmVy
c2lvbnMgYXZhaWxhYmxlIGF0Og0KPiA+IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLW1wdGNwLXJmYzY4MjRiaXMtMTINCj4gPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RvYy9odG1sL2RyYWZ0LWlldGYtbXB0Y3AtcmZjNjgyNGJpcy0xMg0KPiA+DQo+ID4gQSBk
aWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KPiA+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLW1wdGNwLXJmYzY4MjRiaXMt
MTINCj4gPg0KPiA+DQo+ID4gUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBv
ZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2YNCj4gPiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1s
aXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+
ID4NCj4gPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBG
VFAgYXQ6DQo+ID4gZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCj4gPg0KPiA+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gbXVs
dGlwYXRodGNwIG1haWxpbmcgbGlzdA0KPiA+IG11bHRpcGF0aHRjcEBpZXRmLm9yZw0KPiA+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXVsdGlwYXRodGNwDQo+IA0KPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtdWx0aXBh
dGh0Y3AgbWFpbGluZyBsaXN0DQo+IG11bHRpcGF0aHRjcEBpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcA0K


From nobody Mon Oct  8 13:58:38 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 C2EC5130EE9 for <multipathtcp@ietfa.amsl.com>; Mon,  8 Oct 2018 13:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 qhnlCRbbnlDu for <multipathtcp@ietfa.amsl.com>; Mon,  8 Oct 2018 13:58:33 -0700 (PDT)
Received: from mail-lj1-x241.google.com (mail-lj1-x241.google.com [IPv6:2a00:1450:4864:20::241]) (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 BE706130E96 for <multipathtcp@ietf.org>; Mon,  8 Oct 2018 13:58:32 -0700 (PDT)
Received: by mail-lj1-x241.google.com with SMTP id y71-v6so19111858lje.9 for <multipathtcp@ietf.org>; Mon, 08 Oct 2018 13:58:32 -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 :content-transfer-encoding:message-id:references:to; bh=00miwJ1dEnmdAbFNHc9Rnp62Zm3pZZpfExo++q+Z9pY=; b=DE+DAWbs7+GS1pam0n77XyAwn+2FZT/ztuwusEzsfh2GnRPcQD24w8J9fegCW9TBdN DD9gUS201JPHNLe9j+KE/us6fxAEMG2GetRLZA4fjzS/pLnwbJKVvPN+JONPXWpVijFL 7OC5uvcpbdrAmiykJTISxFGNMtMHZp+ruz+WY7fu+jkkKHlcAVpHpUsVkpaPiDqBavsu VZ/erhV6SN0M81TnlC5Y15OqvnJwKvqSpS0j6qa88OUsxYhul5Rs2HNOW5ZBPfmFl5V1 9wpfi4El6TqWO9VABlnNXw4U/WiNZvXSFDloo2tGRCxwSFcy1ewxldl2yw1JUNtXthZk GRcQ==
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 :content-transfer-encoding:message-id:references:to; bh=00miwJ1dEnmdAbFNHc9Rnp62Zm3pZZpfExo++q+Z9pY=; b=GVJ4kOgZIcvwv2xl/3kVA58cVqEeCFSXnd02u/vIjyBToi3NJy74MOF6P90gTGiDO6 SNFHz1Az4Xm9y1vIAAEQShZ0Vh40aWBuEQq1BRiibqLK64x3VjFK1qS8BkrA+hMVBsbj hf56NEV10nmbPTip/KU7gaCMOeTGYOMD8gH5TvmggVK3umhd8goEkUUgKbnnSzMS0QeL 6/pYR+mS0BZYho5ErqIerQglCY58sxnI19sr+0e6k0J2wIUiwX/C8xAextSpOQK8Q/27 6YLKXkoRtOtglhx3yQSiUMQw+uK9EHp9m0/V7DnOUZNbxlRLXHDgr0ibXe5Q3MCI9XKP lfYg==
X-Gm-Message-State: ABuFfoiByW+D5ssV8DUhS7ecXOp/lS1xkOGp9nKh4lHHX5o/Q7q61ilv n72bi/tA9LjBhWp18qRND1JQFSfm
X-Google-Smtp-Source: ACcGV63bopt/VYyOUlu6qwBr8t02pqv33DErXcRtdLj2HFfDzA+me5FoxQJVNzIDXMbv31TGT9uAoA==
X-Received: by 2002:a2e:1b9c:: with SMTP id c28-v6mr15455950ljf.73.1539032310857;  Mon, 08 Oct 2018 13:58:30 -0700 (PDT)
Received: from [192.168.1.66] ([83.216.156.196]) by smtp.gmail.com with ESMTPSA id g14-v6sm4204083lja.96.2018.10.08.13.58.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Oct 2018 13:58:30 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <982B626E107E334DBE601D979F31785C5DCBF6F0@BLREML503-MBX.china.huawei.com>
Date: Mon, 8 Oct 2018 21:58:28 +0100
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3228CDD-E9AA-4BE8-857B-9BDC7F637E51@gmail.com>
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com> <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com> <982B626E107E334DBE601D979F31785C5DCBF6F0@BLREML503-MBX.china.huawei.com>
To: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/1AMvYPdh70_G7T7JwzizfZTmuSc>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Oct 2018 20:58:37 -0000

Hi Rahul,

Thank you for double-checking, it is much appreciated!

1. Fixing text on Address ID, I hope the following is acceptable:

        The MP_JOIN option includes an "Address ID".  This is an =
identifier
        generated by the sender of the option, used to identify the =
source address=20
        of this packet, even if the IP header has been changed in =
transit by a middlebox.
        The numeric value of this field is generated by the sender and =
must map uniquely=20
        to a source IP address for the sending host.

3. It was left for further comment, and no further comment was =
forthcoming. I personally am not sure of any need to add a MP_TCPRST =
here since both ends should know why the subflow is being torn down - =
one sent the REMOVE_ADDR, and the other acted on it. If the REMOVE_ADDR =
was spoofed, the safety nets should mean the subflow is not torn down. =
So I see no benefit in signalling the reason here.

4. At the first appearance of =E2=80=9Cmake-before-break", we can add:

	, where new subflows are added before the previously used ones =
are closed

Regards,
Alan

> On 8 Oct 2018, at 14:49, Rahul Arvind Jadhav <rahul.jadhav@huawei.com> =
wrote:
>=20
> Hello Alan,
>=20
> Most of my comments from [1] are handled. Thank you.
>=20
> Some comments based on the updated text:
> 1. Accepted comment#8 in [1] does not seem to be handled. I think it =
is important to be clarified that the value of "Address ID" has =
significance not only within a single connection but also only on the =
peer who generates the ID. Thus it is possible for peers to generate the =
same Address ID within a connection as well.
> 2. Thank you for removing the term "passive opener" throughout the =
document. The new text is much easier to understand.
> 3. Looks like comment#2 for explicitly mentioning the Reason Code for =
MP_TCPRST was not accepted. I understand we haven=E2=80=99t really got =
any feedback from the WG on this point but then I feel it is necessary =
to do this.
> 4. "make-before-break session" term is introduced after rewording ... =
I feel this term should be explained in terminology section.
>=20
> Best,
> Rahul
>=20
> [1] =
https://mailarchive.ietf.org/arch/msg/multipathtcp/hpsqifbR00xRWJNZe-CYR7U=
tTyU
>=20
>=20
>> -----Original Message-----
>> From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf =
Of
>> Alan Ford
>> Sent: 03 October 2018 19:56
>> To: multipathtcp <multipathtcp@ietf.org>
>> Subject: Re: [multipathtcp] I-D Action: =
draft-ietf-mptcp-rfc6824bis-12.txt
>>=20
>> Hi all,
>>=20
>> I believe this new version addresses all last call/review comments we
>> received for rfc6824bis, with the exception of adding a possible =
=E2=80=9Cchanges
>> since RFC6824=E2=80=9D section.
>>=20
>> Could all reviewers please check this new version and ensure we have
>> handled your review comments appropriately?
>>=20
>> Many thanks,
>> Alan
>>=20
>>> On 3 Oct 2018, at 15:23, 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-12.txt
>>> 	Pages           : 80
>>> 	Date            : 2018-10-03
>>>=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-12
>>> https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-12
>>>=20
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-12
>>>=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
>>=20
>> _______________________________________________
>> multipathtcp mailing list
>> multipathtcp@ietf.org
>> https://www.ietf.org/mailman/listinfo/multipathtcp


From nobody Tue Oct  9 10:05:27 2018
Return-Path: <rahul.ietf@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 1AF7A13135D for <multipathtcp@ietfa.amsl.com>; Tue,  9 Oct 2018 10:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, 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 QCQJQzRsabYM for <multipathtcp@ietfa.amsl.com>; Tue,  9 Oct 2018 10:05:22 -0700 (PDT)
Received: from mail-vk1-xa44.google.com (mail-vk1-xa44.google.com [IPv6:2607:f8b0:4864:20::a44]) (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 93795131332 for <multipathtcp@ietf.org>; Tue,  9 Oct 2018 10:05:21 -0700 (PDT)
Received: by mail-vk1-xa44.google.com with SMTP id b80-v6so566488vke.3 for <multipathtcp@ietf.org>; Tue, 09 Oct 2018 10:05:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GL2msCZugJFswnnFFltL/YQGXG9hRhwad41NJF8wy3I=; b=PLXN0Opcak/uckc2jWJ/vl7mYh8dPHHiBhLfMB9aV4XLPtIRG6i5Ku6ru7/atpbqRl sdpomEhzwuIoBqu1RpFjK/Qje9cOpNM0XUtfi0TEiyFihUt8nHulTel0Us4TTJpiyVJV yTV6kJX/oNdhzpSAYea54vBWdcO7NBDMb8QQSXJzzUgffevedTSGkXheUBeswYja07JS r2CQ8otthLsE48BeuUP8FnKbepKRR23gJAwaKa3TbvhD+KHkP96Z7dijIqr+LZVrruKr gAUfO9pgpWcbeCyxDo3OadTm6xqh3JeRU+EOCbjbtw77z8Q3Kf+3V1gbJNjtbgAb2T2X P+7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GL2msCZugJFswnnFFltL/YQGXG9hRhwad41NJF8wy3I=; b=nIJRFd2LPmgJ3bGaU35gZuCwZNw+x6MljIuY0ict+xSxn3KuqPpgLwS7cOy0IzPTyc LhgBUamTCLzKzHTCsgDd3/IWTtd0UbqyDWJCeBQ+loW+KICaFGPfOjZHitGt4z293iPq FTvr29WRCt8tQCq15NtR2WyH1BQCzn4f6Pk/i7MblRfsRXCktHfYQXXE2mi81KV0frYV OjTR896FYyd7ReK3rB0OfZ1Y+ttRAjkhtJKL9YTUzLWFeUNzxJX7xFYXa8ZWDrGO3Yjt YDX83HvSq5vvGhwygHEQAYMFHkxRLh+3fTyDZByKlfJLCio+JixYtNk3ZimFkk2hY0Ci 3t8A==
X-Gm-Message-State: ABuFfojdo9CnpzLLNIctz0QiiWItoKWJJqm3hID5Xlagospsmu0gWUUb 8z+o0MlNKzkYAwL8qy2Owd9ZO79AJmxNYw02rmyF6g==
X-Google-Smtp-Source: ACcGV6014k38t7tQqu9TTNG9AqMyLsQWo6odK8Arqv0hnX1klHWnlnHySTmmkaoCg7GUggAFIpq4XTdtNXnZm4UJles=
X-Received: by 2002:a1f:1887:: with SMTP id 129mr1931788vky.92.1539104719578;  Tue, 09 Oct 2018 10:05:19 -0700 (PDT)
MIME-Version: 1.0
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com> <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com> <982B626E107E334DBE601D979F31785C5DCBF6F0@BLREML503-MBX.china.huawei.com> <A3228CDD-E9AA-4BE8-857B-9BDC7F637E51@gmail.com>
In-Reply-To: <A3228CDD-E9AA-4BE8-857B-9BDC7F637E51@gmail.com>
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Tue, 9 Oct 2018 22:34:33 +0530
Message-ID: <CAO0Djp36VQ5f-Mr8HVdpX77Yzsvxb0x1A7h1EmOZSEfSd6Qj=A@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001529f80577cebe8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/LIcTFWXMS6sPYCY16WrGZVThAcA>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 09 Oct 2018 17:05:26 -0000

--0000000000001529f80577cebe8d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The suggested text looks good. I have no further comments.

Thanks,
Rahul

On Tue, 9 Oct 2018 at 2:28 AM, Alan Ford <alan.ford@gmail.com> wrote:

> Hi Rahul,
>
> Thank you for double-checking, it is much appreciated!
>
> 1. Fixing text on Address ID, I hope the following is acceptable:
>
>         The MP_JOIN option includes an "Address ID".  This is an identifi=
er
>         generated by the sender of the option, used to identify the sourc=
e
> address
>         of this packet, even if the IP header has been changed in transit
> by a middlebox.
>         The numeric value of this field is generated by the sender and
> must map uniquely
>         to a source IP address for the sending host.
>
> 3. It was left for further comment, and no further comment was
> forthcoming. I personally am not sure of any need to add a MP_TCPRST here
> since both ends should know why the subflow is being torn down - one sent
> the REMOVE_ADDR, and the other acted on it. If the REMOVE_ADDR was spoofe=
d,
> the safety nets should mean the subflow is not torn down. So I see no
> benefit in signalling the reason here.
>
> 4. At the first appearance of =E2=80=9Cmake-before-break", we can add:
>
>         , where new subflows are added before the previously used ones ar=
e
> closed
>
> Regards,
> Alan
>
> > On 8 Oct 2018, at 14:49, Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
> wrote:
> >
> > Hello Alan,
> >
> > Most of my comments from [1] are handled. Thank you.
> >
> > Some comments based on the updated text:
> > 1. Accepted comment#8 in [1] does not seem to be handled. I think it is
> important to be clarified that the value of "Address ID" has significance
> not only within a single connection but also only on the peer who generat=
es
> the ID. Thus it is possible for peers to generate the same Address ID
> within a connection as well.
> > 2. Thank you for removing the term "passive opener" throughout the
> document. The new text is much easier to understand.
> > 3. Looks like comment#2 for explicitly mentioning the Reason Code for
> MP_TCPRST was not accepted. I understand we haven=E2=80=99t really got an=
y feedback
> from the WG on this point but then I feel it is necessary to do this.
> > 4. "make-before-break session" term is introduced after rewording ... I
> feel this term should be explained in terminology section.
> >
> > Best,
> > Rahul
> >
> > [1]
> https://mailarchive.ietf.org/arch/msg/multipathtcp/hpsqifbR00xRWJNZe-CYR7=
UtTyU
> >
> >
> >> -----Original Message-----
> >> From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of
> >> Alan Ford
> >> Sent: 03 October 2018 19:56
> >> To: multipathtcp <multipathtcp@ietf.org>
> >> Subject: Re: [multipathtcp] I-D Action:
> draft-ietf-mptcp-rfc6824bis-12.txt
> >>
> >> Hi all,
> >>
> >> I believe this new version addresses all last call/review comments we
> >> received for rfc6824bis, with the exception of adding a possible
> =E2=80=9Cchanges
> >> since RFC6824=E2=80=9D section.
> >>
> >> Could all reviewers please check this new version and ensure we have
> >> handled your review comments appropriately?
> >>
> >> Many thanks,
> >> Alan
> >>
> >>> On 3 Oct 2018, at 15:23, 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-12.txt
> >>>     Pages           : 80
> >>>     Date            : 2018-10-03
> >>>
> >>> 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-12
> >>> https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-12
> >>>
> >>> A diff from the previous version is available at:
> >>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-12
> >>>
> >>>
> >>> 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
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>

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

<div><div dir=3D"auto">The suggested text looks good. I have no further com=
ments.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks,</div></di=
v><div dir=3D"auto">Rahul=C2=A0</div><div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr">On Tue, 9 Oct 2018 at 2:28 AM, Alan Ford &lt;<a href=3D"mail=
to:alan.ford@gmail.com">alan.ford@gmail.com</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">Hi Rahul,<br>
<br>
Thank you for double-checking, it is much appreciated!<br>
<br>
1. Fixing text on Address ID, I hope the following is acceptable:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The MP_JOIN option includes an &quot;Address ID=
&quot;.=C2=A0 This is an identifier<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 generated by the sender of the option, used to =
identify the source address <br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 of this packet, even if the IP header has been =
changed in transit by a middlebox.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The numeric value of this field is generated by=
 the sender and must map uniquely <br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to a source IP address for the sending host.<br=
>
<br>
3. It was left for further comment, and no further comment was forthcoming.=
 I personally am not sure of any need to add a MP_TCPRST here since both en=
ds should know why the subflow is being torn down - one sent the REMOVE_ADD=
R, and the other acted on it. If the REMOVE_ADDR was spoofed, the safety ne=
ts should mean the subflow is not torn down. So I see no benefit in signall=
ing the reason here.<br>
<br>
4. At the first appearance of =E2=80=9Cmake-before-break&quot;, we can add:=
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 , where new subflows are added before the previ=
ously used ones are closed<br>
<br>
Regards,<br>
Alan<br>
<br>
&gt; On 8 Oct 2018, at 14:49, Rahul Arvind Jadhav &lt;<a href=3D"mailto:rah=
ul.jadhav@huawei.com" target=3D"_blank">rahul.jadhav@huawei.com</a>&gt; wro=
te:<br>
&gt; <br>
&gt; Hello Alan,<br>
&gt; <br>
&gt; Most of my comments from [1] are handled. Thank you.<br>
&gt; <br>
&gt; Some comments based on the updated text:<br>
&gt; 1. Accepted comment#8 in [1] does not seem to be handled. I think it i=
s important to be clarified that the value of &quot;Address ID&quot; has si=
gnificance not only within a single connection but also only on the peer wh=
o generates the ID. Thus it is possible for peers to generate the same Addr=
ess ID within a connection as well.<br>
&gt; 2. Thank you for removing the term &quot;passive opener&quot; througho=
ut the document. The new text is much easier to understand.<br>
&gt; 3. Looks like comment#2 for explicitly mentioning the Reason Code for =
MP_TCPRST was not accepted. I understand we haven=E2=80=99t really got any =
feedback from the WG on this point but then I feel it is necessary to do th=
is.<br>
&gt; 4. &quot;make-before-break session&quot; term is introduced after rewo=
rding ... I feel this term should be explained in terminology section.<br>
&gt; <br>
&gt; Best,<br>
&gt; Rahul<br>
&gt; <br>
&gt; [1] <a href=3D"https://mailarchive.ietf.org/arch/msg/multipathtcp/hpsq=
ifbR00xRWJNZe-CYR7UtTyU" rel=3D"noreferrer" target=3D"_blank">https://maila=
rchive.ietf.org/arch/msg/multipathtcp/hpsqifbR00xRWJNZe-CYR7UtTyU</a><br>
&gt; <br>
&gt; <br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: multipathtcp [mailto:<a href=3D"mailto:multipathtcp-bounces@=
ietf.org" target=3D"_blank">multipathtcp-bounces@ietf.org</a>] On Behalf Of=
<br>
&gt;&gt; Alan Ford<br>
&gt;&gt; Sent: 03 October 2018 19:56<br>
&gt;&gt; To: multipathtcp &lt;<a href=3D"mailto:multipathtcp@ietf.org" targ=
et=3D"_blank">multipathtcp@ietf.org</a>&gt;<br>
&gt;&gt; Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bi=
s-12.txt<br>
&gt;&gt; <br>
&gt;&gt; Hi all,<br>
&gt;&gt; <br>
&gt;&gt; I believe this new version addresses all last call/review comments=
 we<br>
&gt;&gt; received for rfc6824bis, with the exception of adding a possible =
=E2=80=9Cchanges<br>
&gt;&gt; since RFC6824=E2=80=9D section.<br>
&gt;&gt; <br>
&gt;&gt; Could all reviewers please check this new version and ensure we ha=
ve<br>
&gt;&gt; handled your review comments appropriately?<br>
&gt;&gt; <br>
&gt;&gt; Many thanks,<br>
&gt;&gt; Alan<br>
&gt;&gt; <br>
&gt;&gt;&gt; On 3 Oct 2018, at 15:23, <a href=3D"mailto:internet-drafts@iet=
f.org" target=3D"_blank">internet-drafts@ietf.org</a> wrote:<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; A New Internet-Draft is available from the on-line Internet-Dr=
afts<br>
&gt;&gt; directories.<br>
&gt;&gt;&gt; This draft is a work item of the Multipath TCP WG of the IETF.=
<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: TCP Extensions for Multipath Operation with Multiple<br>
&gt;&gt; Addresses<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Alan Ford<br>
&gt;&gt;&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=A0Costin Raiciu<br>
&gt;&gt;&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=A0Mark Handley<br>
&gt;&gt;&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=A0Olivier Bonaventure<br>
&gt;&gt;&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=A0Christoph Paasch<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft=
-ietf-mptcp-rfc6824bis-12.txt<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 80<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : 2018-10-03<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Abstract:<br>
&gt;&gt;&gt;=C2=A0 TCP/IP communication is currently restricted to a single=
 path per<br>
&gt;&gt;&gt;=C2=A0 connection, yet multiple paths often exist between peers=
.=C2=A0 The<br>
&gt;&gt;&gt;=C2=A0 simultaneous use of these multiple paths for a TCP/IP se=
ssion would<br>
&gt;&gt;&gt;=C2=A0 improve resource usage within the network and, thus, imp=
rove user<br>
&gt;&gt;&gt;=C2=A0 experience through higher throughput and improved resili=
ence to<br>
&gt;&gt;&gt;=C2=A0 network failure.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;=C2=A0 Multipath TCP provides the ability to simultaneously use=
 multiple<br>
&gt;&gt;&gt;=C2=A0 paths between peers.=C2=A0 This document presents a set =
of extensions to<br>
&gt;&gt;&gt;=C2=A0 traditional TCP to support multipath operation.=C2=A0 Th=
e protocol offers<br>
&gt;&gt;&gt;=C2=A0 the same type of service to applications as TCP (i.e., r=
eliable<br>
&gt;&gt;&gt;=C2=A0 bytestream), and it provides the components necessary to=
 establish<br>
&gt;&gt;&gt;=C2=A0 and use multiple TCP flows across potentially disjoint p=
aths.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;=C2=A0 This document specifies v1 of Multipath TCP, obsoleting =
v0 as<br>
&gt;&gt;&gt;=C2=A0 specified in RFC6824 [RFC6824] through clarifications an=
d<br>
&gt;&gt;&gt;=C2=A0 modifications primarily driven by deployment experience.=
<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br>
&gt;&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mptcp-r=
fc6824bis/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.o=
rg/doc/draft-ietf-mptcp-rfc6824bis/</a><br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; There are also htmlized versions available at:<br>
&gt;&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-mptcp-rfc682=
4bis-12" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/d=
raft-ietf-mptcp-rfc6824bis-12</a><br>
&gt;&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mp=
tcp-rfc6824bis-12" rel=3D"noreferrer" target=3D"_blank">https://datatracker=
.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-12</a><br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; A diff from the previous version is available at:<br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mptc=
p-rfc6824bis-12" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/=
rfcdiff?url2=3Ddraft-ietf-mptcp-rfc6824bis-12</a><br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Please note that it may take a couple of minutes from the time=
 of<br>
&gt;&gt;&gt; submission until the htmlized version and diff are available a=
t <a href=3D"http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">to=
ols.ietf.org</a>.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"norefer=
rer" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; multipathtcp mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">mul=
tipathtcp@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/multipathtcp</a><br>
&gt;&gt; <br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; multipathtcp mailing list<br>
&gt;&gt; <a href=3D"mailto:multipathtcp@ietf.org" target=3D"_blank">multipa=
thtcp@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/multipathtcp" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mul=
tipathtcp</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>

--0000000000001529f80577cebe8d--


From nobody Tue Oct 16 09:34:39 2018
Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29185130DFD for <multipathtcp@ietfa.amsl.com>; Tue, 16 Oct 2018 09:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btgroupcloud.onmicrosoft.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 U5fYqqylYwbv for <multipathtcp@ietfa.amsl.com>; Tue, 16 Oct 2018 09:34:36 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22792130DF6 for <multipathtcp@ietf.org>; Tue, 16 Oct 2018 09:34:35 -0700 (PDT)
Received: from tpw09926dag07h.domain1.systemhost.net (10.9.202.46) by RDW083A011ED67.bt.com (10.187.98.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 16 Oct 2018 17:35:34 +0100
Received: from tpw09926dag10g.domain1.systemhost.net (10.9.202.45) by tpw09926dag07h.domain1.systemhost.net (10.9.202.46) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 16 Oct 2018 17:34:32 +0100
Received: from RDW083A011ED67.bt.com (10.187.98.37) by tpw09926dag10g.domain1.systemhost.net (10.9.202.45) with Microsoft SMTP Server (TLS) id 15.0.1293.2 via Frontend Transport; Tue, 16 Oct 2018 17:34:32 +0100
Received: from GBR01-LO2-obe.outbound.protection.outlook.com (23.103.134.179) by smtpe1.intersmtp.com (62.239.224.235) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 16 Oct 2018 17:35:32 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=BTGroupCloud.onmicrosoft.com; s=selector1-bt-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=77PZ7q8/BeZr4z1ocBmwdCPhJI79f9CpnUmHZy0ZC/0=; b=Tt0Gfw85G825Q9JbVz56XK41InvVnERim5Xmgg/3ARMJLsZo/OJCIigcpiFyVBKoHv5gCJbeUOo4vDXDh2EAOtWVGIN4RoKoVavFAceasxutEEv6XJ4wMsDF6nPOQxSH08lAg/AjoRjJo1ac1IfPYh9jd6cudSpMQ1B6WDifhj8=
Received: from LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM (10.166.250.17) by LOXP123MB1272.GBRP123.PROD.OUTLOOK.COM (10.166.254.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1250.20; Tue, 16 Oct 2018 16:34:31 +0000
Received: from LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM ([fe80::f9a4:c705:e1f3:cc4b]) by LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM ([fe80::f9a4:c705:e1f3:cc4b%5]) with mapi id 15.20.1228.027; Tue, 16 Oct 2018 16:34:30 +0000
From: <philip.eardley@bt.com>
To: <alan.ford@gmail.com>, <multipathtcp@ietf.org>
Thread-Topic: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
Thread-Index: AQHUWyTA7RxEIYQSyEqvPi4YTQ/YNKUNk6OAgBSIFxA=
Date: Tue, 16 Oct 2018 16:34:30 +0000
Message-ID: <LOXP123MB080554CC37A2655A94A4C25EEBFE0@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com> <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
In-Reply-To: <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com; 
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; LOXP123MB1272; 6:+J3JZc5vbFLeVX38xPtPlxug+6OFvEcJaVP2W4Ez+AMAYpiyensNEGkYM3El4riZ67w8sM6LwxLOYXTXaQ28aFb7s+J0QYABm/9k635rbQfVVO19etQalsVjbYU/Y6mHYA23fN9OkggI+s9z+9sjSOhq5YouSxnCccs6eNBmtRgnGDfmtIQOAzTrySe5DIW4aYcK6zGBumgGyUdCQNM6mNCnRUJ/Y+/BzWtEQZ7X9YpQAVELCeWV1hWfLD2rOkujE82kCzhu6s4xKJyr/G32QREk8pOhAsXpTFjxSyR+WSSyOrms4ucQVo/qdmxZccxtv9mYVPgY997WcNtFYPyeExp//gX87gsbR8klO6v0LJjCdvHpIprF5OvJwdGkmznZWlcC0hw3NpXNXbEvmtrRSGoPRsiarq/8q0FGwZBb0NaFQ2SuEI+HK7rgdhJLTQDkbiDFurjnDOUy8E1LaRk/bg==; 5:cLhZUqdiuCBmRhybGX8eSVujRpu7dOPlu+girVxz7cTkSIMYNVBO00YP/STxdTZUxKqGqkniwcMeGV654ker11IniTJ7gKGvoSDMGwnTUIdw5pY5gkPU8zd6rasN8aoNDG6/btX1pjlSMqc8Hn75h/XaZv3k7RyDEynOLWa+Uac=; 7:KN0sI5DgnT+DaTNCCGr/3mULJjKhZYwz8ckmPZDbyH/sUg28joGnvH6RFRv9frk+GElxhZNi64D0eMtgL3OcV1ICS6JAXZZvW2i0netsCeeYcy1qGvLtmfVhkcDeBT4/pv7bS8R1TVFrr91oh56MtjuRXd8AGB2B3NpAxxws5O4oyC27NAniZnrsyQSRw7hYWr2IRrAmW1+Q+jfzTUs1Inw1kj67lQ+laJLLjcj4nh7zMVD4s71pldXSw7W6YF+B
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: c5008ee9-d8ad-49aa-cf15-08d633853f77
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:LOXP123MB1272; 
x-ms-traffictypediagnostic: LOXP123MB1272:
x-antispam-2: 1
x-microsoft-antispam-prvs: <LOXP123MB1272C9976119FDD27B1FFB53EBFE0@LOXP123MB1272.GBRP123.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:(278428928389397)(120809045254105);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231355)(944501410)(52105095)(3002001)(10201501046)(93006095)(93001095)(149066)(150057)(6041310)(20161123560045)(20161123558120)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051); SRVR:LOXP123MB1272; BCL:0; PCL:0; RULEID:; SRVR:LOXP123MB1272; 
x-forefront-prvs: 0827D7ACB9
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(366004)(346002)(376002)(39860400002)(53754006)(13464003)(199004)(189003)(76176011)(55016002)(6306002)(6436002)(53936002)(5250100002)(110136005)(99286004)(74316002)(6116002)(3846002)(2900100001)(9686003)(229853002)(7696005)(66066001)(86362001)(486006)(39060400002)(6246003)(478600001)(966005)(14454004)(33656002)(26005)(186003)(102836004)(446003)(6506007)(106356001)(11346002)(105586002)(53546011)(476003)(71190400001)(71200400001)(68736007)(5660300001)(316002)(2906002)(8676002)(7736002)(256004)(14444005)(8936002)(81156014)(81166006)(25786009)(305945005)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:LOXP123MB1272; H:LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: nqLaB4eSUsxRfG49NHoFl0KGDDKjNgLbTpP47RbWU+OwnYGnYArs60DsJTY66+wKhSn46tQ4wE0TkPqODFuzCH7NKvmWUI9DACx+K2gPn4wcFQicX7a9+yqePOHJX2sBUkg4At/ZdqGnYx5MV7pCAdWLYaNMsfB9EbXPpCuWUJ2SGueb56NyEbR2fGFQHY8ZrRnmoDydPZMnPK68mx9vm95CwVhcwnYXGrA8qgs72B03mURNiRmtclR04EqS1mmSOQy/w0nevJPD6qRm3YqzVxGREEZC1or7XII0f592GSi+1hBy3Vh0fTeEZVGk+24u3FHFALihjgREZqkyCUAOHwgLr6VVKHzxXpzdynOomAk=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c5008ee9-d8ad-49aa-cf15-08d633853f77
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2018 16:34:30.6596 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LOXP123MB1272
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/O92UanB_clfaB11jC7rjcXklyDU>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Oct 2018 16:34:39 -0000

QWxhbiwNCkxvb2tzIGdvb2QuDQoNCjEuIHRoZSBsaXN0IG9mIGNoYW5nZXMgL3JlYXNvbnMgY29t
cGFyZWQgd2l0aCByZmM2ODI0IG5vdCBpbmNsdWRlZC4gSSBjYW4gc3VibWl0IGFzIHNlcGFyYXRl
IGRyYWZ0LCBpZiB5b3UgcHJlZmVyIHRvIGluY2x1c2lvbiBpbiB5b3VyIGRvYy4NCg0KMi4gSSAg
bWFkZSBhIGNvbW1lbnQgb24gRmlnIDEyIChqdXN0IGNoZWNraW5nIHlvdSBtZWFudCB0byBpZ25v
cmUgaXQgLSBkb27igJl0IG1pbmQhKQ0KDQpBbmQgaW4gRmlnIDEyDQp8ICAgICAgICBUcnVuY2F0
ZWQgSE1BQyAoOCBvY3RldHMsIGlmIGxlbmd0aCA+IDEwIG9jdGV0cykgICAgICAgfA0KDQpDb3Vs
ZCB0aGlzIGJlIG1hZGUgbW9yZSBzdHJhaWdodGZvcndhcmQ/IEllIHNwZWxsIG91dCB3aGVuIGxl
bmd0aCBpcyA+MTAgb2N0ZXRzIGllIElQdjYgKGlmIEkgdW5kZXJzdGFuZCBpdCkuIFRoaXMgYWxz
byBzZWVtcyB0byBtZWFuIHRoYXQgSVB2NCBkb2VzbuKAmXQgaW5jbHVkZSB0aGUgSE1BQywgaXMg
dGhpcyByaWdodD8/DQoNCjMuIEkgbWFkZSBhIGNvbW1lbnQgb24gU2VjdGlvbiAyOiAgTmVlZCB0
byBhZGQgc3ViLXNlY3Rpb25zIG9uIGNsb3Npbmcgc3ViZmxvdyAmIGZhc3QgY2xvc2UgJiBmYWxs
YmFjaw0KV291bGQgYmUgbmljZSwgYnV0IEkgd29uJ3QgaW5zaXN0IGlmIGl0J3MgdG9vIG11Y2gg
d29yaw0KDQpUaGFua3MNCnBoaWwNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IG11bHRpcGF0aHRjcCBbbWFpbHRvOm11bHRpcGF0aHRjcC1ib3VuY2VzQGlldGYub3JnXSBPbiBC
ZWhhbGYgT2YgQWxhbiBGb3JkDQpTZW50OiAwMyBPY3RvYmVyIDIwMTggMTU6MjYNClRvOiBtdWx0
aXBhdGh0Y3AgPG11bHRpcGF0aHRjcEBpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbbXVsdGlwYXRo
dGNwXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLW1wdGNwLXJmYzY4MjRiaXMtMTIudHh0DQoNCkhp
IGFsbCwNCg0KSSBiZWxpZXZlIHRoaXMgbmV3IHZlcnNpb24gYWRkcmVzc2VzIGFsbCBsYXN0IGNh
bGwvcmV2aWV3IGNvbW1lbnRzIHdlIHJlY2VpdmVkIGZvciByZmM2ODI0YmlzLCB3aXRoIHRoZSBl
eGNlcHRpb24gb2YgYWRkaW5nIGEgcG9zc2libGUg4oCcY2hhbmdlcyBzaW5jZSBSRkM2ODI04oCd
IHNlY3Rpb24uDQoNCkNvdWxkIGFsbCByZXZpZXdlcnMgcGxlYXNlIGNoZWNrIHRoaXMgbmV3IHZl
cnNpb24gYW5kIGVuc3VyZSB3ZSBoYXZlIGhhbmRsZWQgeW91ciByZXZpZXcgY29tbWVudHMgYXBw
cm9wcmlhdGVseT8NCg0KTWFueSB0aGFua3MsDQpBbGFuDQoNCj4gT24gMyBPY3QgMjAxOCwgYXQg
MTU6MjMsIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyB3cm90ZToNCj4gDQo+IA0KPiBBIE5ldyBJ
bnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFm
dHMgZGlyZWN0b3JpZXMuDQo+IFRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIE11bHRp
cGF0aCBUQ1AgV0cgb2YgdGhlIElFVEYuDQo+IA0KPiAgICAgICAgVGl0bGUgICAgICAgICAgIDog
VENQIEV4dGVuc2lvbnMgZm9yIE11bHRpcGF0aCBPcGVyYXRpb24gd2l0aCBNdWx0aXBsZSBBZGRy
ZXNzZXMNCj4gICAgICAgIEF1dGhvcnMgICAgICAgICA6IEFsYW4gRm9yZA0KPiAgICAgICAgICAg
ICAgICAgICAgICAgICAgQ29zdGluIFJhaWNpdQ0KPiAgICAgICAgICAgICAgICAgICAgICAgICAg
TWFyayBIYW5kbGV5DQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBPbGl2aWVyIEJvbmF2ZW50
dXJlDQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBDaHJpc3RvcGggUGFhc2NoDQo+IAlGaWxl
bmFtZSAgICAgICAgOiBkcmFmdC1pZXRmLW1wdGNwLXJmYzY4MjRiaXMtMTIudHh0DQo+IAlQYWdl
cyAgICAgICAgICAgOiA4MA0KPiAJRGF0ZSAgICAgICAgICAgIDogMjAxOC0xMC0wMw0KPiANCj4g
QWJzdHJhY3Q6DQo+ICAgVENQL0lQIGNvbW11bmljYXRpb24gaXMgY3VycmVudGx5IHJlc3RyaWN0
ZWQgdG8gYSBzaW5nbGUgcGF0aCBwZXINCj4gICBjb25uZWN0aW9uLCB5ZXQgbXVsdGlwbGUgcGF0
aHMgb2Z0ZW4gZXhpc3QgYmV0d2VlbiBwZWVycy4gIFRoZQ0KPiAgIHNpbXVsdGFuZW91cyB1c2Ug
b2YgdGhlc2UgbXVsdGlwbGUgcGF0aHMgZm9yIGEgVENQL0lQIHNlc3Npb24gd291bGQNCj4gICBp
bXByb3ZlIHJlc291cmNlIHVzYWdlIHdpdGhpbiB0aGUgbmV0d29yayBhbmQsIHRodXMsIGltcHJv
dmUgdXNlcg0KPiAgIGV4cGVyaWVuY2UgdGhyb3VnaCBoaWdoZXIgdGhyb3VnaHB1dCBhbmQgaW1w
cm92ZWQgcmVzaWxpZW5jZSB0bw0KPiAgIG5ldHdvcmsgZmFpbHVyZS4NCj4gDQo+ICAgTXVsdGlw
YXRoIFRDUCBwcm92aWRlcyB0aGUgYWJpbGl0eSB0byBzaW11bHRhbmVvdXNseSB1c2UgbXVsdGlw
bGUNCj4gICBwYXRocyBiZXR3ZWVuIHBlZXJzLiAgVGhpcyBkb2N1bWVudCBwcmVzZW50cyBhIHNl
dCBvZiBleHRlbnNpb25zIHRvDQo+ICAgdHJhZGl0aW9uYWwgVENQIHRvIHN1cHBvcnQgbXVsdGlw
YXRoIG9wZXJhdGlvbi4gIFRoZSBwcm90b2NvbCBvZmZlcnMNCj4gICB0aGUgc2FtZSB0eXBlIG9m
IHNlcnZpY2UgdG8gYXBwbGljYXRpb25zIGFzIFRDUCAoaS5lLiwgcmVsaWFibGUNCj4gICBieXRl
c3RyZWFtKSwgYW5kIGl0IHByb3ZpZGVzIHRoZSBjb21wb25lbnRzIG5lY2Vzc2FyeSB0byBlc3Rh
Ymxpc2gNCj4gICBhbmQgdXNlIG11bHRpcGxlIFRDUCBmbG93cyBhY3Jvc3MgcG90ZW50aWFsbHkg
ZGlzam9pbnQgcGF0aHMuDQo+IA0KPiAgIFRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIHYxIG9mIE11
bHRpcGF0aCBUQ1AsIG9ic29sZXRpbmcgdjAgYXMNCj4gICBzcGVjaWZpZWQgaW4gUkZDNjgyNCBb
UkZDNjgyNF0gdGhyb3VnaCBjbGFyaWZpY2F0aW9ucyBhbmQNCj4gICBtb2RpZmljYXRpb25zIHBy
aW1hcmlseSBkcml2ZW4gYnkgZGVwbG95bWVudCBleHBlcmllbmNlLg0KPiANCj4gDQo+IFRoZSBJ
RVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPiBodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1wdGNwLXJmYzY4MjRiaXMvDQo+
IA0KPiBUaGVyZSBhcmUgYWxzbyBodG1saXplZCB2ZXJzaW9ucyBhdmFpbGFibGUgYXQ6DQo+IGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW1wdGNwLXJmYzY4MjRiaXMtMTIN
Cj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1pZXRmLW1wdGNw
LXJmYzY4MjRiaXMtMTINCj4gDQo+IEEgZGlmZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJzaW9uIGlz
IGF2YWlsYWJsZSBhdDoNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0
LWlldGYtbXB0Y3AtcmZjNjgyNGJpcy0xMg0KPiANCj4gDQo+IFBsZWFzZSBub3RlIHRoYXQgaXQg
bWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIA0KPiBzdWJtaXNz
aW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQg
dG9vbHMuaWV0Zi5vcmcuDQo+IA0KPiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxl
IGJ5IGFub255bW91cyBGVFAgYXQ6DQo+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiBtdWx0aXBhdGh0Y3AgbWFpbGluZyBsaXN0DQo+IG11bHRpcGF0aHRjcEBpZXRmLm9yZw0K
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcA0KDQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbXVsdGlwYXRo
dGNwIG1haWxpbmcgbGlzdA0KbXVsdGlwYXRodGNwQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL211bHRpcGF0aHRjcA0K


From nobody Thu Oct 18 07:49:33 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 8663D12D4EB for <multipathtcp@ietfa.amsl.com>; Thu, 18 Oct 2018 07:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 zBpoQJniZALj for <multipathtcp@ietfa.amsl.com>; Thu, 18 Oct 2018 07:49:29 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 A0261128CF2 for <multipathtcp@ietf.org>; Thu, 18 Oct 2018 07:49:28 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id z204-v6so588853wmc.5 for <multipathtcp@ietf.org>; Thu, 18 Oct 2018 07:49:28 -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 :content-transfer-encoding:message-id:references:to; bh=a0Cxqf/pU5M2Spz24Y3Jto4Mm8vhBqsGJPzugzvyOUs=; b=ZFJ7GefoR3nHRGM5zW5ULPR8LqGXt+irRWeU6djC7qXHUOAUwGqAj7QBu00wnqNVvQ lVlWVghib/FTnI+0/hEcUbrA1QYB+9itAedVxOP8pSq4QA0VYblmK8G1YAgiWafoSOST xttR/XY1HIApp+grM2OGmKNxq0UkH/eS1MBe0tkm7BA3wK755bwp79IbWigxViko1elu yB9/zD5jVeJVGYMMAAjSzorN21JY7rRndjrjNRaDUB6kwqkN6Q0p+X1UEoFxBIyNfqRC ky9ZupEFpeTXeiaUDyTKgtjbZYBZkh+XmACy/lKpM2IFfyhte0mvnDf3CV3mOLOTrCEs BlVg==
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 :content-transfer-encoding:message-id:references:to; bh=a0Cxqf/pU5M2Spz24Y3Jto4Mm8vhBqsGJPzugzvyOUs=; b=hWHIAXaVFJdqqSksT70XixQke2iT4NBRLm9dZyAnexXgHPEf7skTveoyqrJXdyvdQX 9M9IFuyg3cFf48l9UJQ7gQ+C0vIuQurm/51uLUfzk9LrVDnjycQ0apC5lJI7ipbWsR0x edq5ehA58mgS7TsUH9ZAFt0uUPPN9xgm+GJKRFOpNOuSRMa4ceDS3C1N0paGogYoab+2 f2R+BUHUvjEXDmA9V8Un1UMegDMTBJ2W7LJm8rfm+cvIPD5+am+NFsnLBRRghOn7GqKd 2LaZl3HZwInzLAwdTE5GIgCBhZ+gXg6eqFzJhKVTtolTdXr2D6sHVglDLVD+f42Tjig0 F8rw==
X-Gm-Message-State: ABuFfoiMZ3J+NlZ7X03XL+13QtX5iQXmfzD3q0mEFyiYOoj8+8sv1VwY 9ia++Fy4Q6M6xPrIluKDemo=
X-Google-Smtp-Source: ACcGV625S3FyvUdbQKYb6Mconw/tlNgWid8yWQaLWoOKNsUkPAUHdWeV/QjFmeMMsF6aSPckomqMnw==
X-Received: by 2002:a1c:870c:: with SMTP id j12-v6mr703656wmd.40.1539874166809;  Thu, 18 Oct 2018 07:49:26 -0700 (PDT)
Received: from [10.44.30.233] ([62.254.152.194]) by smtp.gmail.com with ESMTPSA id j2-v6sm15629523wrw.29.2018.10.18.07.49.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Oct 2018 07:49:24 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <LOXP123MB080554CC37A2655A94A4C25EEBFE0@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
Date: Thu, 18 Oct 2018 15:49:17 +0100
Cc: multipathtcp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC56EB70-ED8F-4287-A83B-3B5D324375DB@gmail.com>
References: <153857661587.9120.4590608359579290440@ietfa.amsl.com> <CC367F1F-06FC-4D12-83A2-81435191EA80@gmail.com> <LOXP123MB080554CC37A2655A94A4C25EEBFE0@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
To: "philip.eardley" <philip.eardley@bt.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/UBy-rpZ_eo9YpC6unkAtvTgooRg>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-12.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Oct 2018 14:49:31 -0000

Hi Phil, all,

Inline...

> On 16 Oct 2018, at 17:34, philip.eardley@bt.com wrote:
>=20
> Alan,
> Looks good.
>=20
> 1. the list of changes /reasons compared with rfc6824 not included. I =
can submit as separate draft, if you prefer to inclusion in your doc.

I do intend to add this, but have not yet got around to it. I am keen we =
keep the list clear, consistent, and simple, and focus only on =
implementation differences.

> 2. I  made a comment on Fig 12 (just checking you meant to ignore it - =
don=E2=80=99t mind!)
>=20
> And in Fig 12
> |        Truncated HMAC (8 octets, if length > 10 octets)       |
>=20
> Could this be made more straightforward? Ie spell out when length is =
>10 octets ie IPv6 (if I understand it). This also seems to mean that =
IPv4 doesn=E2=80=99t include the HMAC, is this right??

It=E2=80=99s wrong! It should say =E2=80=9CIf E =3D 0=E2=80=9D. =
Corrected.

> 3. I made a comment on Section 2:  Need to add sub-sections on closing =
subflow & fast close & fallback
> Would be nice, but I won't insist if it's too much work

Closing subflow and fast close are covered in the =E2=80=9CClosing an =
MPTCP Connection=E2=80=9D subsection. Fallback is too specialist for =
this introductory overview of signalling.

Best regards,
Alan


From nobody Fri Oct 19 08:04:48 2018
Return-Path: <x.defoy.ietf@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 B09C7130F06 for <multipathtcp@ietfa.amsl.com>; Fri, 19 Oct 2018 08:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, 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 l7EMPtJobZHg for <multipathtcp@ietfa.amsl.com>; Fri, 19 Oct 2018 08:04:45 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 8BCD9130EFA for <multipathtcp@ietf.org>; Fri, 19 Oct 2018 08:04:44 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id p143-v6so14447896lfp.13 for <multipathtcp@ietf.org>; Fri, 19 Oct 2018 08:04:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=b1UnXbATjSpW6ukBHRT8JGets1CzLmpKTQMKHb0Rkj4=; b=qrmhuI1emIDHsKU7DKXNV0iukZq4ZivrQ/08bpM8+CZxGqo2J4vbka0OYZKqLVtcLH 0NBdUYE1v8svRIKRWjntz5dC+I3FYS8T3NW4scIp2J1jX6N/ilI4RJ3Zkp37dGzzS9Ui R5fbm01hQPavV9kACEq+nYOGy0te0xdQh7y6xdeKl3xmlLZfhmS8q8yMALI0ttuhKNzb pGfz0ijw0Lfa5nxsms9cO9xVb7SSkHtrRDF+ZHW6/FG7ZXH0n59ciDrF/z8lrmK9vS/S VwUbF14Y/iU5TwktcBVQtCBAZthnPrh19wfAkUiWBTvmJE0SvN2dVu7N/d/flYa9v2Ki eEQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=b1UnXbATjSpW6ukBHRT8JGets1CzLmpKTQMKHb0Rkj4=; b=FARQSWUnX14If5wQrBMEzkGZuNUWmcAxosEqD+0eV0ud0QcJdSOAxV3V7rWdy11iaq M81HtbPZsB+u/NcGQaYrMGS9spTWW9CLyDSmnFtZJztlixKELQ1H9r0EZ5tEw6rf91fe jWkIFcgWrPn4TlgBlYlo/2S+j4+3/COxypZrU3fTBQnesEV+nSGV3lxBLsmr9c9N8NaO aBfO73v/3aslAL4mwU2uT2vygn1qKoMSLHJ5ObeqlPSUvpWcrarPxAdQzk3D1T35z1kl AkC2sS75AJto2YlM/yniWdvchF9MmsA0O/LD0hte8sPhW7X5K36SutXDGMyyx/nitJrX zCfQ==
X-Gm-Message-State: ABuFfognRqbF1gWZ89N+PQkdSp3MubEUCZeV1GzH7vq19hJ8Jw1yF6Mn W8/uHzTYdOk2y/RoWUPBck8gGhvtIWMl/akSg1qq+pvT
X-Google-Smtp-Source: ACcGV62TempkC1EDrpOP/vRhuPhY3xzGzolHgv7dnhMRPMMfz/vgi1UiYNs/6+DI9axZfocQxIpnL91CHsKIf41q6Io=
X-Received: by 2002:a19:ae11:: with SMTP id f17-v6mr3503930lfc.86.1539961482344;  Fri, 19 Oct 2018 08:04:42 -0700 (PDT)
MIME-Version: 1.0
References: <153996003773.6501.9694281350716033224.idtracker@ietfa.amsl.com> <BN7PR10MB2547E552BBEBBF55B2C8A445E5F90@BN7PR10MB2547.namprd10.prod.outlook.com>
In-Reply-To: <BN7PR10MB2547E552BBEBBF55B2C8A445E5F90@BN7PR10MB2547.namprd10.prod.outlook.com>
From: Xavier de Foy <x.defoy.ietf@gmail.com>
Date: Fri, 19 Oct 2018 11:04:30 -0400
Message-ID: <CAHYjOTaRcKK-Lgq8zgviooM8B2XOcjNTGbVNipqNSGoV5KrCTA@mail.gmail.com>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001f7d6705789639ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/M-t6J7ZutuOxn_Zz9-rLWamry04>
Subject: [multipathtcp] Fwd: FW: New Version Notification for draft-defoy-5g-session-continuity-support-in-mptcp-00.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Oct 2018 15:04:48 -0000

--0000000000001f7d6705789639ff
Content-Type: text/plain; charset="UTF-8"

Hi all,

  During the last few IETF meetings, multiple discussions took place about
the support of 5G session continuity. This new draft "5G Session Continuity
Support in MPTCP" provide a summary, focusing on MPTCP protocol impacts,
with the goal to provide some input for future discussions about MPTCP
evolution. Some information from the draft "Considerations for MPTCP
operation in 5G" was retained in appendix, but overall the new draft
narrows down the scope to potential MPTCP protocol changes (and session
continuity).

  Thank you to all contributors. Comments are welcome.

  Best Regards,
Xavier

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org>
Sent: Friday, October 19, 2018 10:41 AM
To: Uma Chunduri <uma.chunduri@huawei.com>; Olvera-Hernandez, Ulises
<Ulises.Olvera-Hernandez@InterDigital.com>; Olvera-Hernandez, Ulises
<Ulises.Olvera-Hernandez@InterDigital.com>; De Foy, Xavier
<Xavier.DeFoy@InterDigital.com>; De Foy, Xavier
<Xavier.DeFoy@InterDigital.com>
Subject: New Version Notification for
draft-defoy-5g-session-continuity-support-in-mptcp-00.txt


A new version of I-D,
draft-defoy-5g-session-continuity-support-in-mptcp-00.txt
has been successfully submitted by Xavier de Foy and posted to the IETF
repository.

Name:draft-defoy-5g-session-continuity-support-in-mptcp
Revision:00
Title:5G Session Continuity Support in MPTCP
Document date:2018-10-19
Group:Individual Submission
Pages:12
URL:
https://www.ietf.org/internet-drafts/draft-defoy-5g-session-continuity-support-in-mptcp-00.txt
Status:
https://datatracker.ietf.org/doc/draft-defoy-5g-session-continuity-support-in-mptcp/
Htmlized:
https://tools.ietf.org/html/draft-defoy-5g-session-continuity-support-in-mptcp-00
Htmlized:
https://datatracker.ietf.org/doc/html/draft-defoy-5g-session-continuity-support-in-mptcp


Abstract:
   This document describes how 5G session continuity can affect MPTCP.
   For now only potential performance issues are identified.  This
   document aims to document discussions that took place at the IETF on
   this subject, to facilitate future deployment of MPTCP over 5G.




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

[Banner]
This e-mail is intended only for the use of the individual or entity to
which it is addressed, and may contain information that is privileged,
confidential and/or otherwise protected from disclosure to anyone other
than its intended recipient. Unintended transmission shall not constitute
waiver of any privilege or confidentiality obligation. If you received this
communication in error, please do not review, copy or distribute it, notify
me immediately by email, and delete the original message and any
attachments. Unless expressly stated in this e-mail, nothing in this
message or any attachment should be construed as a digital or electronic
signature.

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi all,<br><br>=C2=A0 During the last few=
 IETF meetings, multiple discussions took place about the support of 5G ses=
sion continuity. This new draft &quot;5G Session Continuity Support in MPTC=
P&quot; provide a summary, focusing on MPTCP protocol impacts, with the goa=
l to provide some input for future discussions about MPTCP evolution. Some =
information from the draft &quot;Considerations for MPTCP operation in 5G&q=
uot; was retained in appendix, but overall the new draft narrows down the s=
cope to potential MPTCP protocol changes (and session continuity).</div><di=
v dir=3D"ltr"><br></div><div dir=3D"ltr">=C2=A0 Thank you to all contributo=
rs. Comments are welcome.<br>=C2=A0 <br>=C2=A0 Best Regards,<br>Xavier<br><=
br><div class=3D"gmail_quote">-----Original Message-----<br>
From: <a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">interne=
t-drafts@ietf.org</a> &lt;<a href=3D"mailto:internet-drafts@ietf.org" targe=
t=3D"_blank">internet-drafts@ietf.org</a>&gt;<br>
Sent: Friday, October 19, 2018 10:41 AM<br>
To: Uma Chunduri &lt;<a href=3D"mailto:uma.chunduri@huawei.com" target=3D"_=
blank">uma.chunduri@huawei.com</a>&gt;; Olvera-Hernandez, Ulises &lt;Ulises=
.Olvera-Hernandez@InterDigital.com&gt;; Olvera-Hernandez, Ulises &lt;Ulises=
.Olvera-Hernandez@InterDigital.com&gt;; De Foy, Xavier &lt;Xavier.DeFoy@Int=
erDigital.com&gt;; De Foy, Xavier &lt;Xavier.DeFoy@InterDigital.com&gt;<br>
Subject: New Version Notification for draft-defoy-5g-session-continuity-sup=
port-in-mptcp-00.txt<br>
<br>
<br>
A new version of I-D, draft-defoy-5g-session-continuity-support-in-mptcp-00=
.txt<br>
has been successfully submitted by Xavier de Foy and posted to the IETF rep=
ository.<br>
<br>
Name:draft-defoy-5g-session-continuity-support-in-mptcp<br>
Revision:00<br>
Title:5G Session Continuity Support in MPTCP<br>
Document date:2018-10-19<br>
Group:Individual Submission<br>
Pages:12<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-defoy-5g-session-continuity-support-in-mptcp-00.tx=
t" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/internet-draft=
s/draft-defoy-5g-session-continuity-support-in-mptcp-00.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-defoy-5g-session-continuity-support-in-mptcp/" rel=3D"noref=
errer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-defoy-5g-se=
ssion-continuity-support-in-mptcp/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-defoy-5g-session-continuity-support-in-mptcp-00" rel=3D"noreferrer" t=
arget=3D"_blank">https://tools.ietf.org/html/draft-defoy-5g-session-continu=
ity-support-in-mptcp-00</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-defoy-5g-session-continuity-support-in-mptcp" rel=3D"norefe=
rrer" target=3D"_blank">https://datatracker.ietf.org/doc/html/draft-defoy-5=
g-session-continuity-support-in-mptcp</a><br>
<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes how 5G session continuity can affect M=
PTCP.<br>
=C2=A0 =C2=A0For now only potential performance issues are identified.=C2=
=A0 This<br>
=C2=A0 =C2=A0document aims to document discussions that took place at the I=
ETF on<br>
=C2=A0 =C2=A0this subject, to facilitate future deployment of MPTCP over 5G=
.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at <a href=3D"http://to=
ols.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
[Banner]<br>
This e-mail is intended only for the use of the individual or entity to whi=
ch it is addressed, and may contain information that is privileged, confide=
ntial and/or otherwise protected from disclosure to anyone other than its i=
ntended recipient. Unintended transmission shall not constitute waiver of a=
ny privilege or confidentiality obligation. If you received this communicat=
ion in error, please do not review, copy or distribute it, notify me immedi=
ately by email, and delete the original message and any attachments. Unless=
 expressly stated in this e-mail, nothing in this message or any attachment=
 should be construed as a digital or electronic signature.<br>
<br>
</div></div></div>

--0000000000001f7d6705789639ff--

