IETF Logo Mail Archive

Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-08.txt

Alan Ford <alan.ford@gmail.com> Mon, 03 July 2017 18:23 UTC

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 1D4C412ECAD for <multipathtcp@ietfa.amsl.com>; Mon, 3 Jul 2017 11:23:13 -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 jJ-p1QxVsf5U for <multipathtcp@ietfa.amsl.com>; Mon, 3 Jul 2017 11:23:11 -0700 (PDT)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 4526A1316EA for <multipathtcp@ietf.org>; Mon, 3 Jul 2017 11:23:10 -0700 (PDT)
Received: by mail-wr0-x231.google.com with SMTP id k67so237719378wrc.2 for <multipathtcp@ietf.org>; Mon, 03 Jul 2017 11:23:10 -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=o/wLzakWD1Yr6vkjJymAwP8pTwU/MMNANEUVFUmcMDQ=; b=hR7ga6zyKlFaK4Z2FaYsj2t3wRfLZ60MlA8olKQ//cUo4LnaS24E6a0xsmkvPjwIdK pRSWuRy56qcx7xoTs18UruHdmo1U43z6Et7Db2ItA1g3S+0TV4tFcRar5/0Ez4fftxOm 75lxWjDTUNAp0pS2nrrF/aCaN8MdXWv99aYmCcZ70TZ04OHNugQYMRrT0qMZTqEtBk5e G99fHurKQ96xkUUCv7KrHCmlK+48kz6JZHqByy9ygqRSSV9Qy2BOvDjcJX3HyxspVZib /A1+Y0JrG6JLDIyEYIZFdFOg0yKBFZ7BAvPHSlaBYXpu3Rk9geW3H4J0V4Dwky5poudR SS4A==
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=o/wLzakWD1Yr6vkjJymAwP8pTwU/MMNANEUVFUmcMDQ=; b=FRc1e08wOxvUo+VoWX203FfbsJ5pO9oce8IM/FD4tb11inyX9bFDlBVJ/FakXkofA2 29V13fupA0VNaAxtbmNzsaHGBN0T47A2q3JhAzpNSga5Ph7U8sjHpEV85VSVrS2fgRUP cw30bcT7VbsYln4mgGD0mI/vuV1hCJ8+XrrUX0ak2z5eo0+X5isoP7yJ6O3As5V+9bqw e9jNzXMQNazc+LKfS6vZ4091g+gLmlu+jK4iC01N7Pu5uTK/8rCtD/6bnq6AWhRsvJvK t4xipx99nzzfsU4IT/J6NrV4MSUn9S2QLcH+H5BwgQUHQjqLDBvDqopfrSMpxOam5F0f QBgQ==
X-Gm-Message-State: AKS2vOxLIv6KIZLua8nKksX690+COrq0wTH0mhPTaL8FRALXkKQjKMIu Z+/GG8SIapm6dLQiQzs=
X-Received: by 10.223.183.36 with SMTP id l36mr27248991wre.115.1499106188526; Mon, 03 Jul 2017 11:23:08 -0700 (PDT)
Received: from alans-mbp.lan (173.177.159.143.dyn.plus.net. [143.159.177.173]) by smtp.gmail.com with ESMTPSA id 55sm23934634wrt.36.2017.07.03.11.23.07 for <multipathtcp@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 03 Jul 2017 11:23:07 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <149910604728.22726.12262054079948108111@ietfa.amsl.com>
Date: Mon, 03 Jul 2017 19:23:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9FDA84C-4A44-498A-B6BC-37121BE7EBE6@gmail.com>
References: <149910604728.22726.12262054079948108111@ietfa.amsl.com>
To: multipathtcp <multipathtcp@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/GBoNlyr-2cpO9rQTjtzPZWR9nM8>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-08.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: Mon, 03 Jul 2017 18:23:13 -0000

Hi all,

This rev of 6824bis contains the clarifications brought forward by Christoph’s and Olivier’s implementation experiences - notably clarifying the interchangeabiltiy of MP_CAPABLE and DSS for initial Data Sequence Mappings, and the sending of TCP RSTs in FASTCLOSE situation. This revision also now refers to SHA-256 as the hash algorithm.

Regards,
Alan

> On 3 Jul 2017, at 19:20, 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 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-08.txt
> 	Pages           : 73
> 	Date            : 2017-07-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-08
> https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-08
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-08
> 
> 
> 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

v2.23.0 | Report a Bug | By Email