Re: [multipathtcp] draft minutes for montreal meeting
Yoshifumi Nishida <nsd.ietf@gmail.com> Mon, 26 August 2019 07:28 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 2137D1200FB for <multipathtcp@ietfa.amsl.com>; Mon, 26 Aug 2019 00:28:23 -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 IjQ9BmShOkQu for <multipathtcp@ietfa.amsl.com>; Mon, 26 Aug 2019 00:28:21 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 24EB6120019 for <multipathtcp@ietf.org>; Mon, 26 Aug 2019 00:28:21 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id q12so14206879wrj.12 for <multipathtcp@ietf.org>; Mon, 26 Aug 2019 00:28:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qzuktThGAvMIeERUcowe0/TLLLOGF1LIq780O1JZtqQ=; b=Z9MssZKStn5NYjWzZixPRj1Wq7f/FdhuoqCXnGZR6TSF9FDGjUGy5e9/8+wI4iHcNq hHLy6jpBN89lBWglEMHDYX6+jzBKU7jMUPXnceJ+RKJ3AZz2bXeaw2YlC1VCbqQh22fJ 9c6sDTiIoy0I+qJZbjYKQOmZ+GzVNSYsqgAEZCn/ZH2mFRkZX6OvMUPGa+SoTCup9vQp o03xusKlY08Wp6cWjtPJnGao6w3t0O1vW5kJd6NWE25xcX/q4p+eEFwqW2JWLztZlq+O TR8gRwaU4k0O1lUj4tzgo7c6l149V/to9j8HHaLzKMmWq6AVDwRfht2fLPPWUOQlzmNg YGog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qzuktThGAvMIeERUcowe0/TLLLOGF1LIq780O1JZtqQ=; b=dwooFVV6C1h6mwcspBiyHpPH07eZWDVTud50IWlqXiOGLK8ntRM2Z/j0yG5a6A3iUi CxpmX2tjbIrQqUvJnZDWLnFZYGwZAibkwqJNB3aqENoWQ56IN8Sf6gyxqnGVv5XlKzIp WxEeZJGuD7bmh0KvGSv2VM68xXkGTHqLp8cB+b9M2JVAiilCI0LTGduMmv6xLidj9tNK DqPIWKeMHXDhB9Fdy5rIe+qS5kuge88y/n3IWdT4hzhU3GKTpriV+meeoOqjG/PlW6nI QS9pFXMqVTuG4MABcK1h/SM2ZJvTrgJ+26PNfz8JyZn167GRcQ2hWsFldwnqJc7yL9VH ikbw==
X-Gm-Message-State: APjAAAWz1c2vVzI1tKQYJZXlxdbGgGRdGNG36JsJDNpruvdWVnBRrKF1 pAD/2q11mJuaQHtXlJl2ixaBjIuob2lmYIhZViFIkQ==
X-Google-Smtp-Source: APXvYqwAUNPMjPG5eTgyj0c0JwMAhTbiY41Ch0Op4exdj7Mm62EevyM6gM3MPLIGchKHkfTK37EmjljefVJYV9zIzGs=
X-Received: by 2002:adf:dbcd:: with SMTP id e13mr19688874wrj.314.1566804499759; Mon, 26 Aug 2019 00:28:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAAK044TujtMGw0zLXWLwe_04r=Kde1v1WVL59tpL6UFz33kQcw@mail.gmail.com> <008f46d7-dd99-3158-535e-91efe1acb2f7@uclouvain.be>
In-Reply-To: <008f46d7-dd99-3158-535e-91efe1acb2f7@uclouvain.be>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Mon, 26 Aug 2019 00:28:08 -0700
Message-ID: <CAAK044R5zu4FvoZ3YQ5KwYPL6PTpNvLUTkHBPcLR9APm_XRt8Q@mail.gmail.com>
To: Olivier Bonaventure <olivier.bonaventure@uclouvain.be>
Cc: multipathtcp <multipathtcp@ietf.org>, Mathieu Jadin <mathieu.jadin@uclouvain.be>
Content-Type: multipart/alternative; boundary="000000000000a40782059100195c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/4bo2iwHQKfK_QpReYD2OX8TnXsE>
Subject: Re: [multipathtcp] draft minutes for montreal meeting
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, 26 Aug 2019 07:28:23 -0000
Hi Olivier, Thanks for the reply. On Wed, Aug 21, 2019 at 8:31 AM Olivier Bonaventure < olivier.bonaventure@uclouvain.be> wrote: > Yoshi, > > > Sorry for the delay. I uploaded a draft minutes for montreal meeting. > > You can take a look at the URL below. > > Please let the chairs know if you have corrections, suggestions or > > questions. > > > > https://datatracker.ietf.org/doc/minutes-105-mptcp/ > > Thanks for sharing these detailed minutes. I have some comments after > having read them. > > > > > Keith Moore: > > Is there support in the room for working on a secure (encrypted) > version > > of MPTCP? > > > > Chairs: > > Show of hands: How many would be willing to work on an encrypted > version. > > We proposed such a design in an infocom paper, see > > https://inl.info.ucl.ac.be/publications/secure-multipath-tcp-design-impementation.html > There was running code on Linux but we have not maintained it since > publication. > Thanks for the pointer. I think this is an interesting approach. As far as I know this has not been presented at the WG yet, not written in an I-D. Am I correct? > > > Mirja (as individual): > > If you want encryption, use QUIC. > > > > Chairs: > > Would work on be a bad idea? > > (a couple) and why? > > > > Nicolas P: > > I think it's too heavy. Would require encryption of options. > > > Yoshi: > > TCPINC was oribinally intended to be used for MPTCP. But, it does > not > > encrypt options. Do we want to create an updated version? > > > > Mirja: > > There is zero deployment of TCPINC. I would suggest to first get > > deployment experience. > > If people want to experiment with our implementation, this should be > possible. My personal viewpoint is that adding full security to MPTCP is > probably too difficult at this stage if the objective is to have a > deployable solution. > Thanks for the inputs. Just to be clear, is this approach to extend ENO as described in the infocomm paper? -- Yoshi
- [multipathtcp] draft minutes for montreal meeting Yoshifumi Nishida
- Re: [multipathtcp] draft minutes for montreal mee… philip.eardley
- Re: [multipathtcp] draft minutes for montreal mee… Olivier Bonaventure
- Re: [multipathtcp] draft minutes for montreal mee… Yoshifumi Nishida
- Re: [multipathtcp] draft minutes for montreal mee… Yoshifumi Nishida