[multipathtcp] comments on draft-amend-mptcp-robe-00

Yoshifumi Nishida <nsd.ietf@gmail.com> Mon, 15 July 2019 08:40 UTC

Return-Path: <nsd.ietf@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 F30C012004D for <multipathtcp@ietfa.amsl.com>; Mon, 15 Jul 2019 01:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 RVK81GNzrLon for <multipathtcp@ietfa.amsl.com>; Mon, 15 Jul 2019 01:40:41 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 3A99912001E for <multipathtcp@ietf.org>; Mon, 15 Jul 2019 01:40:41 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id a15so14227702wmj.5 for <multipathtcp@ietf.org>; Mon, 15 Jul 2019 01:40:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=yfq+mUDob0uvtBjmEepWaokJUyV1R3agc03PGtZ8X0g=; b=CCDVJU9YxX6eytwMsAa2NGBk6iKxn05k2cEof3wy3dYeXvdFBRef1aMP5y/UrP1agn mvqG7BF1OtEfrvTnnX142NDLC9fvIbhuJyNSTgtD3Bb3YKdu9P9SO6vFzkTizQijpiTw XgC5cvRc9m2yI8gmKIzslHrmCfBobWXbMEgspnwxhTp6ZeodVaUbU1c9cUevfOxcO+z/ IrjeyRZtDQ5zvO8vGBKEJxzXvWAHT3SxdXOhjuUHzpUJdcEbcRMZ7cSnC09LEvzLJPcn CeZ59pUlKBqZ1G7QU1hA7Z39XVgKsOrrKk+raUeh6QVyafPXD2/hOzDf3e2F669MlbzP 21eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yfq+mUDob0uvtBjmEepWaokJUyV1R3agc03PGtZ8X0g=; b=kaVCW7JpEtpaIJ0FA66/MElaC5sVuy5UqO3l+do+WsHAoTxvFdavCPz1hupn+GcyLP fUEkLqlFZX6RKuO3yGHTbxSMRqpz1qxr40HJOiXoWzRYq5q0yIAOQVDl8GfMeRS8SB3K 6Bf6qXqmD4ErtdSTE152rV2K7WHbqLYaS7ZAgYVnLkoi9PdprTwPSa5AeHtZs3iFR71Q EEEc0KVhjihBEb40vW8bBcfYo2SBEVQmHgqw4/T47Lp+V/ybISBSF1GaHxm8ddUxCNG1 P5cfOfStqTu6xSUkjKnBL6RriMHnHKRnJYufMKtQizGQvWCLvEr64y5dNIIffN6ygcXV sX7w==
X-Gm-Message-State: APjAAAUxPjlAjhTJs1+utM0RboeJ3IVHp/oXMqXmmfCL+WQuY3IpUY+r IrR9ziaCzg6xa/4fPemkfaUfVL2GHdap8dXTqkXfRQ==
X-Google-Smtp-Source: APXvYqzAcudDrhNxfs/YGfZhJYkxRaVjOmQeemQShlVvcytLy/EjEI55g/My95wJqfLEVtjzncIbGUnnddNh3DKsx3M=
X-Received: by 2002:a05:600c:1008:: with SMTP id c8mr23512028wmc.133.1563180039612; Mon, 15 Jul 2019 01:40:39 -0700 (PDT)
MIME-Version: 1.0
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Mon, 15 Jul 2019 01:40:28 -0700
Message-ID: <CAAK044S6U05Vh2V5-TQt6Rr=n0t3_Fp9vBoJG0TGK1CjH9cBEg@mail.gmail.com>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fb3109058db43682"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/drfJ_e0V_hpXQy3jg1LMQIUddhA>
Subject: [multipathtcp] comments on draft-amend-mptcp-robe-00
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: Mon, 15 Jul 2019 08:40:43 -0000

Hi,
I've read this draft and I personally like the idea in the draft. Thanks
for an interesting proposal.
Bellows are my comments on the draft.
1: I'm trying to understand the rationale behinds the format of
MP_JOIN_CAP, such as the purpose of Key-B_fast_cash and the calculation of
HMAC_keys. Could you elaborate?
2: Don't we have a certain ACK mechanism for MP_JOIN_CAP such as ADD_ADDR?
Otherwise, we cannot confirm that the peer has agreed with sender's
intention and it can cause errors in the mptcp session.

Thanks,
--
Yoshi