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

Alan Ford <alan.ford@gmail.com> Sun, 17 February 2019 19:46 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 C4FCA12D7EA for <multipathtcp@ietfa.amsl.com>; Sun, 17 Feb 2019 11:46:48 -0800 (PST)
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 IN9GaNbOGuxe for <multipathtcp@ietfa.amsl.com>; Sun, 17 Feb 2019 11:46:46 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DFD312D4EF for <multipathtcp@ietf.org>; Sun, 17 Feb 2019 11:46:46 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id g80so12507381ljg.6 for <multipathtcp@ietf.org>; Sun, 17 Feb 2019 11:46:46 -0800 (PST)
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=OxboORK82IfQ0F9N6Y6fSuB7t9W7rvCBIk6b64ONgLQ=; b=r/zAOhwwPDnzrO0XZLSoken7Ceg/J1i9uFXpebnzaMjlKcQK8LiMSXyXotWOEjJpvC DeDgHrQb6UNMLM+nefsWhvaqKP0zCU4WdcrkVdaTQXXGf5niMAhag9g+UEq/GKIpTC1P WxuFgVLE7T39iOg/h1q3vDEqQCkqbJZDsKF/dDr+cddcDjyhyft0I3JPPGmDkBCEPGTl /VBZtihhBWjQLT/kF0ljm7YPvhnrZee0d/vp8/CWOKCa74MTa96fJ+y4sqHi9cKR/Yo4 vAKIqiOnqFt0JyowTehrmuFGpicwyU6/6Qzl42XFsJJxcS9YwK46ZT5tgb2jo0ccxknE IGmA==
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=OxboORK82IfQ0F9N6Y6fSuB7t9W7rvCBIk6b64ONgLQ=; b=RI4mNT0yaI/1mbO0cYqhJfpayS6sqGzKwgvKOLfLh0PFQwvFX5OXWieXGhylJrc8cn WzDqFg20GIVyXl1PdZ1A+WzH7ouX9mMi0af7fYpz/E/WeVmBKZZpaoopIF+R7Dl/TZjE 2eOGAC1Y1WmJ2/vcHDKYmHt2tjjmtr3eva9ZIQn2aohFtygIWa5YiftFu7vAtfscsO/K hgz+X9wMXO0AyKVpcLHrfJHBC4vN0p2v6ctYjcw94XV7Ko60K1cZZBwzHd3UKC4FAteM 4X88fdzR//Dw7hXDkOULEwnVI2+GK3YCdicBuIQ9etDrJT7wKws9NwEs9w0cDcpLx8Co 4cgg==
X-Gm-Message-State: AHQUAuZqyZrt0tcXORftWcPNkBw3HlVM8VvGZ80mcLkiG3gB2MDHlNeY PtnJpFSoDO6fGIwyQKpx7gVtk2BE
X-Google-Smtp-Source: AHgI3IaP/abgKbCriZutfG5mUYWZ5nSycSG+FZB1IUhH6/YUfXKIm8u9RWFTLSQikW7jusfH7lxHgA==
X-Received: by 2002:a2e:5cc4:: with SMTP id q187-v6mr10444750ljb.69.1550432804225; Sun, 17 Feb 2019 11:46:44 -0800 (PST)
Received: from [192.168.1.66] (79.35.115.87.dyn.plus.net. [87.115.35.79]) by smtp.gmail.com with ESMTPSA id q1sm2530747lfb.86.2019.02.17.11.46.43 for <multipathtcp@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 17 Feb 2019 11:46:43 -0800 (PST)
From: Alan Ford <alan.ford@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 17 Feb 2019 19:46:41 +0000
References: <155043266302.4092.6890185569294452065@ietfa.amsl.com>
To: multipathtcp <multipathtcp@ietf.org>
In-Reply-To: <155043266302.4092.6890185569294452065@ietfa.amsl.com>
Message-Id: <4F5A5080-E221-4A78-B6B7-3EF51A7FBC92@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/n93boFd-G4kcbiz49xcBboLRauE>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-13.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: Sun, 17 Feb 2019 19:46:49 -0000

Hi all,

This small revision of rfc6824bis takes into account review comments received from Klemens Schragel during WGLC, as well as some nits, and finally the long-promised changes-since-RFC6824 appendix.

Regards,
Alan

> On 17 Feb 2019, at 19:44, 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-13.txt
> 	Pages           : 81
> 	Date            : 2019-02-17
> 
> 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, 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-13
> https://datatracker.ietf.org/doc/html/draft-ietf-mptcp-rfc6824bis-13
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-13
> 
> 
> 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