From: Steffen Klassert <steffen.klassert@secunet.com>
To: Christian Hopps <chopps@chopps.org>
Cc: <devel@linux-ipsec.org>, <netdev@vger.kernel.org>,
Florian Westphal <fw@strlen.de>,
Sabrina Dubroca <sd@queasysnail.net>,
Simon Horman <horms@kernel.org>,
Antony Antony <antony@phenome.org>
Subject: Re: [PATCH ipsec-next v11 00/16] Add IP-TFS mode to xfrm
Date: Mon, 9 Sep 2024 10:45:30 +0200 [thread overview]
Message-ID: <Zt61qqs0eN3m20An@gauss3.secunet.de> (raw)
In-Reply-To: <20240907022412.1032284-1-chopps@chopps.org>
On Fri, Sep 06, 2024 at 10:23:56PM -0400, Christian Hopps wrote:
> * Summary of Changes:
>
> This patchset adds a new xfrm mode implementing on-demand IP-TFS. IP-TFS
> (AggFrag encapsulation) has been standardized in RFC9347.
>
> Link: https://www.rfc-editor.org/rfc/rfc9347.txt
We have to defer this to the next development cycle. This is
too complex for a last minute merge. net-next will shut down
on Sept 13th and I'm unable to do the final review until then.
prev parent reply other threads:[~2024-09-09 8:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 2:23 [PATCH ipsec-next v11 00/16] Add IP-TFS mode to xfrm Christian Hopps
2024-09-07 2:23 ` [PATCH ipsec-next v11 01/16] xfrm: config: add CONFIG_XFRM_IPTFS Christian Hopps
2024-09-07 2:23 ` [PATCH ipsec-next v11 02/16] include: uapi: add ip_tfs_*_hdr packet formats Christian Hopps
2024-09-07 2:23 ` [PATCH ipsec-next v11 03/16] include: uapi: add IPPROTO_AGGFRAG for AGGFRAG in ESP Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 04/16] xfrm: netlink: add config (netlink) options Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 05/16] xfrm: add mode_cbs module functionality Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 06/16] xfrm: add generic iptfs defines and functionality Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 07/16] xfrm: iptfs: add new iptfs xfrm mode impl Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 08/16] xfrm: iptfs: add user packet (tunnel ingress) handling Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 09/16] xfrm: iptfs: share page fragments of inner packets Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 10/16] xfrm: iptfs: add fragmenting of larger than MTU user packets Christian Hopps
2024-09-09 16:43 ` Antony Antony
2024-09-09 17:26 ` Christian Hopps
2024-09-09 17:26 ` Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 11/16] xfrm: iptfs: add basic receive packet (tunnel egress) handling Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 12/16] xfrm: iptfs: handle received fragmented inner packets Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 13/16] xfrm: iptfs: add reusing received skb for the tunnel egress packet Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 14/16] xfrm: iptfs: add skb-fragment sharing code Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 15/16] xfrm: iptfs: handle reordering of received packets Christian Hopps
2024-09-07 2:24 ` [PATCH ipsec-next v11 16/16] xfrm: iptfs: add tracepoint functionality Christian Hopps
2024-09-09 8:45 ` Steffen Klassert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zt61qqs0eN3m20An@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=antony@phenome.org \
--cc=chopps@chopps.org \
--cc=devel@linux-ipsec.org \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox