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

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

Hi all,

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

Specifically:

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

Regards,
Alan

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