[multipathtcp] AD review is coming

Mirja Kuehlewind <ietf@kuehlewind.net> Fri, 12 April 2019 16:40 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 74195120670; Fri, 12 Apr 2019 09:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id sfhzEgwUH8dm; Fri, 12 Apr 2019 09:40:26 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 EDA6B120395; Fri, 12 Apr 2019 09:40:22 -0700 (PDT)
Received: from 200116b82c2d0c00555562f7a1ad4d5a.dip.versatel-1u1.de ([2001:16b8:2c2d:c00:5555:62f7:a1ad:4d5a]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hEzDw-0007Ax-4i; Fri, 12 Apr 2019 18:40:20 +0200
From: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Message-Id: <11187BAE-5E91-410D-9BDA-33F8A60D2458@kuehlewind.net>
Date: Fri, 12 Apr 2019 18:40:19 +0200
Cc: multipathtcp@ietf.org
To: draft-ietf-mptcp-rfc6824bis.all@ietf.org
X-Mailer: Apple Mail (2.3445.104.8)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1555087226;dc0a5bd4;
X-HE-SMSGID: 1hEzDw-0007Ax-4i
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/m9dFAsXtaWvqlJEei7vqLGWfdkY>
Subject: [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: Fri, 12 Apr 2019 16:40:34 -0000

Hi authors, hi shepherd/Phil,

Just wanted to quickly let you know that I’ve started the IETF last call just now in order to hopefully get this document on the telechat in 3 weeks. 

I’ve not finished my AD review completely but I am nearly done and convinced that this doc is ready to start IETF last call. So far I have only some editorial or smallish comments and nits which I will send in detail beginning of next week and can be address during or after IETF last call.

Only one request for now (mostly with an eye on the IESG evaluation): The draft says that changes are made which are not backward compatible (see sec 3.1). That’s fine, however, it would be good to also explain a little bit in the draft as well as in the shepherd write up (!) why this is okay. My understanding is that in case of a v0 server the connection will “just" fall-back to non-MPTCP capable and that this is acceptable in current deployment situation. Please confirm and at least update the write-up accordingly as soon as possible!