[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZVEsLPhykZId7Opz@Antony2201.local>
Date: Sun, 12 Nov 2023 20:49:00 +0100
From: Antony Antony <antony@...nome.org>
To: Christian Hopps <chopps@...pps.org>
Cc: devel@...ux-ipsec.org, netdev@...r.kernel.org,
Christian Hopps <chopps@...n.net>
Subject: Re: [devel-ipsec] [RFC ipsec-next 1/8] iptfs: config: add
CONFIG_XFRM_IPTFS
On Fri, Nov 10, 2023 at 06:37:12AM -0500, Christian Hopps via Devel wrote:
> From: Christian Hopps <chopps@...n.net>
>
> Signed-off-by: Christian Hopps <chopps@...n.net>
> ---
> net/xfrm/Kconfig | 9 +++++++++
> net/xfrm/Makefile | 1 +
> 2 files changed, 10 insertions(+)
>
> diff --git a/net/xfrm/Kconfig b/net/xfrm/Kconfig
> index 3adf31a83a79..d07852069e68 100644
> --- a/net/xfrm/Kconfig
> +++ b/net/xfrm/Kconfig
> @@ -134,6 +134,15 @@ config NET_KEY_MIGRATE
>
> If unsure, say N.
>
> +config XFRM_IPTFS
> + bool "IPsec IPTFS (RFC 9347) encapsulation support"
RFC use "IP-TFS"? in the text use consistanly.
> + depends on XFRM
> + help
> + Information on the IPTFS encapsulation can be found
> + in RFC 9347.
Add details what is actually supported when enabling this options. RFC 9347
has several combinations. Are all combinations supported?
> +
> + If unsure, say N.
> +
> config XFRM_ESPINTCP
> bool
>
> diff --git a/net/xfrm/Makefile b/net/xfrm/Makefile
> index cd47f88921f5..9b870a3274a7 100644
> --- a/net/xfrm/Makefile
> +++ b/net/xfrm/Makefile
> @@ -20,4 +20,5 @@ obj-$(CONFIG_XFRM_USER) += xfrm_user.o
> obj-$(CONFIG_XFRM_USER_COMPAT) += xfrm_compat.o
> obj-$(CONFIG_XFRM_IPCOMP) += xfrm_ipcomp.o
> obj-$(CONFIG_XFRM_INTERFACE) += xfrm_interface.o
> +obj-$(CONFIG_XFRM_IPTFS) += xfrm_iptfs.o
> obj-$(CONFIG_XFRM_ESPINTCP) += espintcp.o
> --
> 2.42.0
>
> --
> Devel mailing list
> Devel@...ux-ipsec.org
> https://linux-ipsec.org/mailman/listinfo/devel
Powered by blists - more mailing lists