Re: [multipathtcp] AD review is coming

Olivier Bonaventure <olivier.bonaventure@uclouvain.be> Tue, 16 April 2019 13:12 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
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 21B3A12016B; Tue, 16 Apr 2019 06:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 RgamCncybrrr; Tue, 16 Apr 2019 06:12:45 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140100.outbound.protection.outlook.com [40.107.14.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D9AC12002E; Tue, 16 Apr 2019 06:12:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RvdzXgrhjlUu9Pa/0WagopIIOPli7UX0a7QAIeegLwg=; b=f108iCWnq1GVzhoHcs6HgrI9RkRDBpgB369dxAbu2Z54KqZDj9/ncKYccGToAENVDYrodMME8qaKaNCbP22QHOtSsNLanpKShjRB0su0653c4zH7+ZlnIHbJuQpL30ljhJa7eltiVyr6QHFiE0R+e3TJFJ0sFSXd/e6C1vxRCeo=
Received: from VE1PR03MB5824.eurprd03.prod.outlook.com (10.255.158.81) by VE1PR03MB5869.eurprd03.prod.outlook.com (10.255.159.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.11; Tue, 16 Apr 2019 13:12:42 +0000
Received: from VE1PR03MB5824.eurprd03.prod.outlook.com ([fe80::5018:fcbe:76e3:7dfb]) by VE1PR03MB5824.eurprd03.prod.outlook.com ([fe80::5018:fcbe:76e3:7dfb%6]) with mapi id 15.20.1792.018; Tue, 16 Apr 2019 13:12:42 +0000
From: Olivier Bonaventure <olivier.bonaventure@uclouvain.be>
To: Mirja Kuehlewind <ietf@kuehlewind.net>, Alan Ford <alan.ford@gmail.com>
CC: "draft-ietf-mptcp-rfc6824bis.all@ietf.org" <draft-ietf-mptcp-rfc6824bis.all@ietf.org>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Thread-Topic: AD review is coming
Thread-Index: AQHU8U51f/7AT+ZU1ESzRJjHjmQY1aY9dV2AgAEz8gCAACA3AA==
Date: Tue, 16 Apr 2019 13:12:42 +0000
Message-ID: <9050cf85-c0d8-0e1f-d3b5-ae5a2c10afa2@uclouvain.be>
References: <11187BAE-5E91-410D-9BDA-33F8A60D2458@kuehlewind.net> <5C08EA72-1AF7-4466-9070-B3F98E7D3017@gmail.com> <B004D5F3-6ADB-4EAE-95E1-D0128C51CFBD@kuehlewind.net>
In-Reply-To: <B004D5F3-6ADB-4EAE-95E1-D0128C51CFBD@kuehlewind.net>
Reply-To: Olivier Bonaventure <olivier.bonaventure@uclouvain.be>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LNXP265CA0003.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5e::15) To VE1PR03MB5824.eurprd03.prod.outlook.com (2603:10a6:803:110::17)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=olivier.bonaventure@uclouvain.be;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:6a8:308f:2:807b:1361:8c1:4744]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c7485102-776c-48eb-3910-08d6c26d3530
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600140)(711020)(4605104)(2017052603328)(7193020); SRVR:VE1PR03MB5869;
x-ms-traffictypediagnostic: VE1PR03MB5869:
x-microsoft-antispam-prvs: <VE1PR03MB586977F9A91FA2217F429FDA86240@VE1PR03MB5869.eurprd03.prod.outlook.com>
x-forefront-prvs: 000947967F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(376002)(346002)(136003)(39860400002)(189003)(199004)(51444003)(99286004)(478600001)(6486002)(3450700001)(229853002)(6436002)(52116002)(2906002)(305945005)(53936002)(6512007)(14454004)(7736002)(6116002)(105586002)(106356001)(186003)(25786009)(4326008)(76176011)(386003)(6506007)(46003)(36756003)(102836004)(31696002)(486006)(71190400001)(256004)(97736004)(71200400001)(3480700005)(86362001)(14444005)(786003)(476003)(54906003)(110136005)(316002)(2616005)(74482002)(11346002)(8936002)(8676002)(81166006)(81156014)(6246003)(31686004)(68736007)(43066004)(446003)(5660300002); DIR:OUT; SFP:1102; SCL:1; SRVR:VE1PR03MB5869; H:VE1PR03MB5824.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: uclouvain.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: LHzeBDuyZ/lGjHvBFoKicAg8DG6hbj2yfOAvZqXwdvwjdWq8FX/OZm7aUWUyosAKLfkse1GFSF/LK1yDT+RRttGhrd1aQkbuXl1lJO+dqJzA+JKwR2HXer5hJSCeWLMNyLCetWyAM1Mq44VjQuLKkx+oHvSLaiHn0rQRj7abvGHKCc1aO2K+iGrtNMZEqrR7RCHliwLQCS5gc6+AxvXAxOXwGuqG0b/90xZYXc8iABkFiUv1E4HW3FZK5bGfrqSTKhMSSoSdJli1dW8cDkdyS/NVDATAFGeRy1+fwcjRFwHOBHuQn3bKbLIq7SPBZzZRhnf1s5W/0ajTdcp8whEztRTJs23jCX13O26K1RpixnrS0b7aJEjKMnEUyxuvSuoqF085SW0gvnanVtExMcsKa1xc7A0mi/3lCCp00j6y+lM=
Content-Type: text/plain; charset="utf-8"
Content-ID: <5B56A1DC02C933428BAE3BF8A458597A@eurprd03.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: c7485102-776c-48eb-3910-08d6c26d3530
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2019 13:12:42.1972 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1PR03MB5869
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/7TQdISDNq4i_maHimy46jc4y9C4>
Subject: Re: [multipathtcp] AD review is coming
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: Tue, 16 Apr 2019 13:12:48 -0000

Mirja,
> 
> Yes, I was looking also for eventually a tiny update to the doc (while it would be most important to mention this in the write-up). I think the one thing that could be added below, is one more sentence or maybe even halve a sentence saying that this fallback to plain TCP (instead of v0) is okay, as general deployment is low and there is also an expectation that server get updated first or entities using MPTCP today actually have some control to update both client and server. 

Today, the largest deployments are :
- Apple (mainly their own services, but third party apps will appear)
- KT/... using SOCKS proxies
- Hybrid Access networks (where MPTCP is used between CPEs and proxies)

Huawei has started to deploy MPTCP in an end-to-end manner in China.

In December, a zmap scan of the entire IPv4 space onport 443 revealed 
than only about 10k hosts were responding with a valid MP_CAPABLE. Many 
of these were CPE routers that had MPTCP enabled and surprisingly open 
https servers.

> Or whatever you think is right to say. So the question to answers is why is it okay that fallback is to plain TCP instead of v0…?

I think that this would make sense given the limited deployment of MPTCP 
servers.


Olivier