IETF Logo Mail Archive

Re: [multipathtcp] RFC6824bis code available

<philip.eardley@bt.com> Thu, 09 May 2019 08:44 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 C01CD12002F for <multipathtcp@ietfa.amsl.com>; Thu, 9 May 2019 01:44:40 -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, HTML_MESSAGE=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 (1024-bit key) header.d=bt.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 iU0U3qiFwb_B for <multipathtcp@ietfa.amsl.com>; Thu, 9 May 2019 01:44:37 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6C00120020 for <multipathtcp@ietf.org>; Thu, 9 May 2019 01:44:36 -0700 (PDT)
Received: from tpw09926dag11e.domain1.systemhost.net (10.9.212.11) by RDW083A012ED68.bt.com (10.187.98.38) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 9 May 2019 09:44:53 +0100
Received: from tpw09926dag18e.domain1.systemhost.net (10.9.212.18) by tpw09926dag11e.domain1.systemhost.net (10.9.212.11) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 9 May 2019 09:44:33 +0100
Received: from RDW083A009ED65.bt.com (10.187.98.35) by tpw09926dag18e.domain1.systemhost.net (10.9.212.18) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 9 May 2019 09:44:33 +0100
Received: from GBR01-LO2-obe.outbound.protection.outlook.com (104.47.21.53) by smtpe1.intersmtp.com (62.239.224.236) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 9 May 2019 09:41:42 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QsBGjN+6XBEcWaREvqhso8Y+5B03JCF6OfaDbiv7+EU=; b=n+/TOOcUzgSmrIPEUmcPyxn7zobGdjIuirP+QxV+o2SV1S0QB3U0bZuuFsOjHZLpMXxRPPOpDkM7rcrlnINo+82PbLVIOrcdmFgw+ZDPFpbIHhGfct5BqV6hwrI3K76CYu887NniCnC6H67FT6r8nXMddctZ7bAHzk7+9ZUhYS8=
Received: from LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM (20.176.157.10) by LO2P123MB1872.GBRP123.PROD.OUTLOOK.COM (20.176.155.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.14; Thu, 9 May 2019 08:44:32 +0000
Received: from LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM ([fe80::f4db:9f33:1c69:76c]) by LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM ([fe80::f4db:9f33:1c69:76c%4]) with mapi id 15.20.1856.012; Thu, 9 May 2019 08:44:32 +0000
From: philip.eardley@bt.com
To: multipathtcp@ietf.org
Thread-Topic: RFC6824bis code available
Thread-Index: AQHU7tgeo07eZaQ140afGCaNkqNEBqZip2sg
Date: Thu, 09 May 2019 08:44:32 +0000
Message-ID: <LO2P123MB1965574A6079F1B6040D8A71EB330@LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM>
References: <LO2P123MB1965F9D012479939464F5285EB2D0@LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM>
In-Reply-To: <LO2P123MB1965F9D012479939464F5285EB2D0@LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=philip.eardley@bt.com;
x-originating-ip: [193.113.37.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 87a7c60f-d4c6-4851-69c2-08d6d45a8eaa
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:LO2P123MB1872;
x-ms-traffictypediagnostic: LO2P123MB1872:
x-ms-exchange-purlcount: 1
x-antispam-2: 1
x-microsoft-antispam-prvs: <LO2P123MB1872A77A47EAA4A7CEBE2026EB330@LO2P123MB1872.GBRP123.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 003245E729
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(376002)(396003)(346002)(136003)(199004)(189003)(66066001)(53546011)(74316002)(64756008)(33656002)(2351001)(73956011)(478600001)(81156014)(6246003)(102836004)(71200400001)(71190400001)(21615005)(6506007)(5640700003)(14454004)(52536014)(68736007)(81166006)(76176011)(8676002)(86362001)(25786009)(5660300002)(7116003)(966005)(2906002)(316002)(1730700003)(8936002)(256004)(11346002)(6916009)(486006)(66946007)(53936002)(476003)(7736002)(66446008)(66556008)(76116006)(446003)(6306002)(54896002)(66476007)(55016002)(2501003)(606006)(9686003)(236005)(3846002)(229853002)(6436002)(186003)(7696005)(790700001)(6116002)(26005)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:LO2P123MB1872; H:LO2P123MB1965.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: vHyEryEPc+Wzwn1fwFmXIXCDQ7AKD/ON08YLir2ajwbGRvRRJlzID0Wj0i5qXnbkcP/9oRJ5oejFwSkPUdv9NOI91UWyzUs7YZdA3ZGtluJ7Kh7B1FupRS3NZZ8kGArfZ8zWu3xA5qib1naS53jXpwz+7kXBW45zj4nMI7hu9Nlx/VJKNckqCef7rc7kJCiXLyH2aD+j0rEOJAy7F+81fjam8iPZLnE0I8v+NSWdtOdVr92CMrXCk6YcnUeDR3VWGRhuNVlapdlfRt1cMZqubkbV0mmpTDLSHpfnQzitRzeIz+RiIwkq8FiGE3rj6RBLaMugPjsxoE+2DNqTF/0a/tpS5A+LSpjukAuWps5PJyytICdviBVuJkXjFCQYCx0Z1Tem2Io/3lqTYgzvn/xcDjyBM+YEx6watXkK+oar5Ks=
Content-Type: multipart/alternative; boundary="_000_LO2P123MB1965574A6079F1B6040D8A71EB330LO2P123MB1965GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 87a7c60f-d4c6-4851-69c2-08d6d45a8eaa
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2019 08:44:32.3850 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P123MB1872
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/U-7Dwfr-WJhKhizGaZZYSkJxKFs>
Subject: Re: [multipathtcp] RFC6824bis code available
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: Thu, 09 May 2019 08:44:41 -0000

Note my email is slightly inaccurate. The implementation that's been made public now includes the new MP_CAPABLE (which is, in my view, the main difference between RFC6824 and the bis). The new ADD_ADDR has been in the publicly available implementation for some time. The other new aspects of the bis are yet to be implemented.

Thanks to Christoph for this clarification, and sorry for any confusion.

Best wishes,
Phil

From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com
Sent: 09 April 2019 14:33
To: multipathtcp@ietf.org
Subject: [multipathtcp] RFC6824bis code available


To follow up on the good news from Prague - the RFC6824bis code is now available.

https://sympa-2.sipr.ucl.ac.be/sympa/arc/mptcp-dev/2019-04/msg00003.html



Many thanks to Christoph and Apple for writing the code and agreeing to release it.



It would be excellent if some people could test it out. Although the bis document is now with Mirja (publication requested), if issues are discovered, at the moment it's not too late to make changes or clarifications.



Best wishes,

phil

v2.29.0 | Report a Bug | By Email | System Status