Re: [multipathtcp] Changes to RFC6824bis
<philip.eardley@bt.com> Tue, 05 September 2017 16:31 UTC
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 C5B06132D86 for <multipathtcp@ietfa.amsl.com>; Tue, 5 Sep 2017 09:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=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 067NRNrQCeQg for <multipathtcp@ietfa.amsl.com>; Tue, 5 Sep 2017 09:31:46 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.138]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F58F132D6F for <multipathtcp@ietf.org>; Tue, 5 Sep 2017 09:31:45 -0700 (PDT)
Received: from EPDAG01D-UKBR.domain1.systemhost.net (193.113.197.205) by EVMED04-UKBR.bt.com (10.216.161.34) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 5 Sep 2017 17:31:42 +0100
Received: from rew09926dag03a.domain1.systemhost.net (10.55.202.18) by EPDAG01D-UKBR.domain1.systemhost.net (193.113.197.205) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 5 Sep 2017 17:31:41 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03a.domain1.systemhost.net (10.55.202.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 5 Sep 2017 17:31:41 +0100
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1293.004; Tue, 5 Sep 2017 17:31:40 +0100
From: philip.eardley@bt.com
To: philip.eardley@bt.com, multipathtcp@ietf.org
Thread-Topic: Changes to RFC6824bis
Thread-Index: AdMF4tNWzyK6qEchQXuzuihLvNQscwggXS1g
Date: Tue, 05 Sep 2017 16:31:40 +0000
Message-ID: <7a02a641ed684b3c8aa8e7899e5624ee@rew09926dag03b.domain1.systemhost.net>
References: <6ad50c5f057742c096fdd1f9088e551d@rew09926dag03b.domain1.systemhost.net>
In-Reply-To: <6ad50c5f057742c096fdd1f9088e551d@rew09926dag03b.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.202.233]
Content-Type: multipart/alternative; boundary="_000_7a02a641ed684b3c8aa8e7899e5624eerew09926dag03bdomain1sy_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/nAVfwxa7AorJc8BOzPT_HWZtPxA>
Subject: Re: [multipathtcp] Changes to RFC6824bis
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, 05 Sep 2017 16:31:49 -0000
Just wanted to check where we are re these 3 changes. #1 - thanks to Alan for making this change #2 - Christoph, Olivier - any news? #3 - Quentin - any news? Thanks! Phil From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com Sent: 26 July 2017 08:51 To: multipathtcp@ietf.org Subject: [multipathtcp] Changes to RFC6824bis Hi, During the discussions in Prague, we had good agreement about the following change to the bis. This is a change to the wire protocol. Please say as soon as possible if you disagree with this change, otherwise we'll go ahead and make this change:- Remove address identifier from MP-PRIO, as it can be used as an attack. Explanation at https://mailarchive.ietf.org/arch/msg/multipathtcp/WWWaQ3AKWEMgsBSPKc_R9Ct_YoI and follow up emails. The issue was briefly summarised during the Friday meeting in Prague - eg see the etherpad for a summary http://etherpad.tools.ietf.org:9000/p/notes-ietf-99-mptcp?useMonospaceFont=true Alan - are you ok to make this change please? -- In addition, we agreed in principle to the following (informational) changes to the bis - exact text to be proposed. 2. Guidance about MPTCP & TFP interactions, based on https://www.ietf.org/proceedings/99/slides/slides-99-mptcp-sessb-mptcp-tfo-00.pdf - Christoph & Olivier, please propose text. 3. There was a suggestion, arising from the hackathon, to discuss on the list whether clarifications or extra 'reason codes' would be useful in the context of reset option. Quentin (& others), please make a proposal. Best wishes, Phil & Yoshi
- [multipathtcp] Changes to RFC6824bis philip.eardley
- Re: [multipathtcp] Changes to RFC6824bis philip.eardley
- Re: [multipathtcp] Changes to RFC6824bis philip.eardley
- Re: [multipathtcp] Changes to RFC6824bis Christoph Paasch