From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============2980736542363277455==" MIME-Version: 1.0 From: David Miller To: mptcp at lists.01.org Subject: [MPTCP] Re: [PATCH net-next 00/11] mptcp: Add port parameter to ADD_ADDR option Date: Wed, 09 Dec 2020 19:04:49 -0800 Message-ID: <20201209.190449.1520052078880395868.davem@davemloft.net> In-Reply-To: 20201209235128.175473-1-mathew.j.martineau@linux.intel.com X-Status: X-Keywords: X-UID: 7120 --===============2980736542363277455== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Mat Martineau Date: Wed, 9 Dec 2020 15:51:17 -0800 > The ADD_ADDR MPTCP option is used to announce available IP addresses > that a peer may connect to when adding more TCP subflows to an existing > MPTCP connection. There is an optional port number field in that > ADD_ADDR header, and this patch set adds capability for that port number > to be sent and received. > = > Patches 1, 2, and 4 refactor existing ADD_ADDR code to simplify implement= ation > of port number support. > = > Patches 3 and 5 are the main functional changes, for sending and > receiving the port number in the MPTCP ADD_ADDR option. > = > Patch 6 sends the ADD_ADDR option with port number on a bare TCP ACK, > since the extra length of the option may run in to cases where > sufficient TCP option space is not available on a data packet. > = > Patch 7 plumbs in port number support for the in-kernel MPTCP path > manager. > = > Patches 8-11 add some optional debug output and a little more cleanup > refactoring. Series applied, thanks. --===============2980736542363277455==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5ADD4C433FE for ; Thu, 10 Dec 2020 03:05:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 048CD2332A for ; Thu, 10 Dec 2020 03:05:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728148AbgLJDFb (ORCPT ); Wed, 9 Dec 2020 22:05:31 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:33056 "EHLO mail.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727988AbgLJDFa (ORCPT ); Wed, 9 Dec 2020 22:05:30 -0500 Received: from localhost (unknown [IPv6:2601:601:9f00:477:9e51:a893:b0fe:602a]) by mail.monkeyblade.net (Postfix) with ESMTPSA id 3F0294D259C1F; Wed, 9 Dec 2020 19:04:50 -0800 (PST) Date: Wed, 09 Dec 2020 19:04:49 -0800 (PST) Message-Id: <20201209.190449.1520052078880395868.davem@davemloft.net> To: mathew.j.martineau@linux.intel.com Cc: netdev@vger.kernel.org, kuba@kernel.org, geliangtang@gmail.com, mptcp@lists.01.org Subject: Re: [PATCH net-next 00/11] mptcp: Add port parameter to ADD_ADDR option From: David Miller In-Reply-To: <20201209235128.175473-1-mathew.j.martineau@linux.intel.com> References: <20201209235128.175473-1-mathew.j.martineau@linux.intel.com> X-Mailer: Mew version 6.8 on Emacs 27.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.monkeyblade.net [0.0.0.0]); Wed, 09 Dec 2020 19:04:50 -0800 (PST) Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org From: Mat Martineau Date: Wed, 9 Dec 2020 15:51:17 -0800 > The ADD_ADDR MPTCP option is used to announce available IP addresses > that a peer may connect to when adding more TCP subflows to an existing > MPTCP connection. There is an optional port number field in that > ADD_ADDR header, and this patch set adds capability for that port number > to be sent and received. > > Patches 1, 2, and 4 refactor existing ADD_ADDR code to simplify implementation > of port number support. > > Patches 3 and 5 are the main functional changes, for sending and > receiving the port number in the MPTCP ADD_ADDR option. > > Patch 6 sends the ADD_ADDR option with port number on a bare TCP ACK, > since the extra length of the option may run in to cases where > sufficient TCP option space is not available on a data packet. > > Patch 7 plumbs in port number support for the in-kernel MPTCP path > manager. > > Patches 8-11 add some optional debug output and a little more cleanup > refactoring. Series applied, thanks.