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

Alan Ford <alan.ford@gmail.com> Fri, 28 October 2016 20:25 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 81A701294E2 for <multipathtcp@ietfa.amsl.com>; Fri, 28 Oct 2016 13:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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] 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 ARig_WBD9JZH for <multipathtcp@ietfa.amsl.com>; Fri, 28 Oct 2016 13:25:24 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 4D086129485 for <multipathtcp@ietf.org>; Fri, 28 Oct 2016 13:25:24 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id 140so91910188wmv.0 for <multipathtcp@ietf.org>; Fri, 28 Oct 2016 13:25:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=N9Xk5ivDebszsWy2ucSQnKfZg3wtRkiIY6+s0lKZZXo=; b=m/cFXD3pDRmSWqb126YqDqL7NzWWpqyFgbTG9xu7nM+2JcPHAmQxps0st6MZbfhyMx aBc8DOYWF0A4257g1jUmXwo6l3+Lm/zP8fbOVtYMeKyCs6uZOfr/RFmvgIm++BiNi/Rg iYK5RZefpoZXCSpKwnSiWfBjBrkRxMLgHVGPzEXtvFwHCEvgEJkru1sjiqaSWtYZTJLw fQWSwruYuJypWOrvAGrMOjaKmW/Ha4ysMNgjAWN9q5rohEql9HfGoafYFaYlTkACJMbv PfNI+GuXkb0VHsSwG4vaSm/m2NCOBfDi6Wo3zSKtBm9C8spSLmTdY76WIlnySXBHyeUb N4Cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=N9Xk5ivDebszsWy2ucSQnKfZg3wtRkiIY6+s0lKZZXo=; b=UcYgiNsmGyAcVp4eTPzRns27qAEtKrn85eh+n2me3fDNiitKK982fddtCEoOoz8pnx 2XxlpCuwiVa6z8KESiqtBsUFMwiWwbNgVjvbGUHBNPMHvJ+79VVUDnV8dkzYzHugbVmJ 8FuAyPFtfR+pTwfBgp9dsual+jevKGejnfkp3FrpZTHrzPTidvLwuSS2Zb/Zm6XnlCDu sZT1TIIPedSKF7FB/t6JVVVwqdolesHe+1giBECqQcYaAUCSb/QygOwZ8+baYq2yhKL+ QCVKulJ+TyWmFmnRSvGl8u+q0YSEMQhqXdb6ztlikM23gGpNugEwtDhay3Bn/fosaqPr VNwA==
X-Gm-Message-State: ABUngvciJBvgEByiEm3PLtvW2G4GzfLrIbgsSURngZHbci7ouEfjys6Y5j1b9nmJlBZj/A==
X-Received: by 10.194.108.105 with SMTP id hj9mr13001052wjb.194.1477686322650; Fri, 28 Oct 2016 13:25:22 -0700 (PDT)
Received: from alans-mbp.lan ([37.152.254.14]) by smtp.gmail.com with ESMTPSA id 129sm10608319wmq.9.2016.10.28.13.25.21 for <multipathtcp@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 28 Oct 2016 13:25:22 -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: <147768612704.25003.10632486814751714234.idtracker@ietfa.amsl.com>
Date: Fri, 28 Oct 2016 21:25:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <27232502-18DE-4BA1-9AD3-B99F0341CB78@gmail.com>
References: <147768612704.25003.10632486814751714234.idtracker@ietfa.amsl.com>
To: multipathtcp@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/rBSyoYDZ76QBt3WdlebR0AqgiI4>
Subject: Re: [multipathtcp] I-D Action: draft-ietf-mptcp-rfc6824bis-07.txt
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Oct 2016 20:25:26 -0000

Hi all,

This small rev to rfc6824bis applies the two changes proposed by Fabien which had support on the list:

- The flag on MP_CAPABLE to say “do not connect back to this address” (proposal 1/5)
- The echo flag to make ADD_ADDR reliable (proposal 2/5)

The “do not use this address unless nothing else is available (proposal 3/5) did not appear to have much support on the list so has been left out for now.

Proposals 4 and 5 are MIA so have not been added at this stage ;-)

Cheers,
Alan

> On 28 Oct 2016, at 21:22, 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-07.txt
> 	Pages           : 73
> 	Date            : 2016-10-28
> 
> 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's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mptcp-rfc6824bis-07
> 
> 
> 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