From patchwork Thu Sep 24 14:35:01 2020
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Florian Westphal <fw@strlen.de>
X-Patchwork-Id: 1370699
Return-Path: <mptcp-bounces@lists.01.org>
X-Original-To: incoming@patchwork.ozlabs.org
Delivered-To: patchwork-incoming@bilbo.ozlabs.org
Authentication-Results: ozlabs.org;
 spf=none (no SPF record) smtp.mailfrom=lists.01.org
 (client-ip=2001:19d0:306:5::1; helo=ml01.01.org;
 envelope-from=mptcp-bounces@lists.01.org; receiver=<UNKNOWN>)
Authentication-Results: ozlabs.org;
 dmarc=none (p=none dis=none) header.from=strlen.de
Received: from ml01.01.org (ml01.01.org [IPv6:2001:19d0:306:5::1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits))
	(No client certificate requested)
	by ozlabs.org (Postfix) with ESMTPS id 4BxyJ84PGHz9sTg
	for <incoming@patchwork.ozlabs.org>; Fri, 25 Sep 2020 00:35:20 +1000 (AEST)
Received: from ml01.vlan13.01.org (localhost [IPv6:::1])
	by ml01.01.org (Postfix) with ESMTP id E3452152ADCB1;
	Thu, 24 Sep 2020 07:35:17 -0700 (PDT)
Received-SPF: Pass (mailfrom) identity=mailfrom;
 client-ip=2a0a:51c0:0:12e:520::1; helo=chamillionaire.breakpoint.cc;
 envelope-from=fw@breakpoint.cc; receiver=<UNKNOWN>
Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc
 [IPv6:2a0a:51c0:0:12e:520::1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(No client certificate requested)
	by ml01.01.org (Postfix) with ESMTPS id 6530C152ADCAE
	for <mptcp@lists.01.org>; Thu, 24 Sep 2020 07:35:15 -0700 (PDT)
Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92)
	(envelope-from <fw@breakpoint.cc>)
	id 1kLSL2-0007Ec-0K; Thu, 24 Sep 2020 16:35:12 +0200
From: Florian Westphal <fw@strlen.de>
To: <mptcp@lists.01.org>
Date: Thu, 24 Sep 2020 16:35:01 +0200
Message-Id: <20200924143505.27641-1-fw@strlen.de>
X-Mailer: git-send-email 2.26.2
MIME-Version: 1.0
Message-ID-Hash: ZY22OLIT3ODQO6N2TQRKRL7RHLGMO24L
X-Message-ID-Hash: ZY22OLIT3ODQO6N2TQRKRL7RHLGMO24L
X-MailFrom: fw@breakpoint.cc
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; nonmember-moderation; administrivia;
 implicit-dest; max-recipients; max-size; news-moderation; no-subject;
 suspicious-header
X-Mailman-Version: 3.1.1
Precedence: list
Subject: [MPTCP] [RFC PATCH 0/4] mptcp: add reset option support
List-Id: Discussions regarding MPTCP upstreaming <mptcp.lists.01.org>
Archived-At: 
 <https://lists.01.org/hyperkitty/list/mptcp@lists.01.org/message/ZY22OLIT3ODQO6N2TQRKRL7RHLGMO24L/>
List-Archive: <https://lists.01.org/hyperkitty/list/mptcp@lists.01.org/>
List-Help: <mailto:mptcp-request@lists.01.org?subject=help>
List-Post: <mailto:mptcp@lists.01.org>
List-Subscribe: <mailto:mptcp-join@lists.01.org>
List-Unsubscribe: <mailto:mptcp-leave@lists.01.org>

This series adds initial support for the RESET option.
First patch is a minor cleanup, I would propose to pass this to
net-next.

Second patch moves a few helpers around so they can be used
from tcp core (needed to add mtpcp reset option to 'active resets',
as those do not use the normal tcp output option path).

Third patch adds mptcp reset option, both for sending and receiving.

Last patch adds a call to the mptcp layer for inbound resets.

At this time, this is non-sensical, as nothing makes use of the
rest-option hint.

The option/reason code would have to be propagated to the PM so
it could use that for e.g. reconnect decisions.

We can discuss further steps in todays meeting.