From: Harald Welte <laforge@gnumonks•org>
To: Jonas Bonn <jonas@norrbonn•se>
Cc: Pravin Shelar <pravin.ovn@gmail•com>,
Linux Kernel Network Developers <netdev@vger•kernel.org>,
Pablo Neira Ayuso <pablo@netfilter•org>
Subject: Re: [PATCH net-next v2 10/12] gtp: add IPv6 support
Date: Sat, 12 Dec 2020 12:05:35 +0100 [thread overview]
Message-ID: <X9Sj/15ebQ9GrKoH@nataraja> (raw)
In-Reply-To: <a52c6960-cf72-9c7a-6c44-cf03711d65f6@norrbonn.se>
Hi Jonas,
On Sat, Dec 12, 2020 at 08:05:40AM +0100, Jonas Bonn wrote:
> Yes, you're probably right. Given that IPv6 isn't really optional in
> contexts where this driver is relevant, [...]
I strongly contest this statement. GTP is used in a lot of legacy contexts
without any IPv6 requirements whatsoever. _particularly_ so on the outer/
transport level, where even GSMA IR.34 in still states:
> The IPX Provider's and Service Provider's networks must support IPv4
> addressing and routing. IPv6 addressing and routing is recommended.
So there is (still) no requirement for IPv6 on the transport level
between cellular operators.
The fact that this gtp module has existed until today with pure IPv4
support has something to say about that.
I'm of course all in support of finally getting IPv6 support merged (via
your patches!) - but I see absolutely no reason why a GTP kernel module
would have a mandatory dependency on IPv6.
--
- Harald Welte <laforge@gnumonks•org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2020-12-12 11:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 12:26 [PATCH net-next v2 00/12] gtp: IPv6 support Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 01/12] gtp: set initial MTU Jonas Bonn
2020-12-12 9:38 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 02/12] gtp: include role in link info Jonas Bonn
2020-12-12 9:40 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 03/12] gtp: really check namespaces before xmit Jonas Bonn
2020-12-12 9:41 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 04/12] gtp: drop unnecessary call to skb_dst_drop Jonas Bonn
2020-12-12 9:50 ` Harald Welte
2020-12-12 11:38 ` Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 05/12] gtp: set device type Jonas Bonn
2020-12-12 9:51 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 06/12] gtp: rework IPv4 functionality Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 07/12] gtp: use ephemeral source port Jonas Bonn
2020-12-12 5:35 ` Pravin Shelar
2020-12-12 7:49 ` Jonas Bonn
2020-12-12 10:07 ` Harald Welte
2020-12-12 13:40 ` Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 08/12] gtp: set dev features to enable GSO Jonas Bonn
2020-12-12 5:31 ` Pravin Shelar
2020-12-12 7:50 ` Jonas Bonn
2020-12-13 18:25 ` Pravin Shelar
2020-12-11 12:26 ` [PATCH net-next v2 09/12] gtp: support GRO Jonas Bonn
2020-12-11 15:43 ` kernel test robot
2020-12-11 12:26 ` [PATCH net-next v2 10/12] gtp: add IPv6 support Jonas Bonn
2020-12-12 5:51 ` Pravin Shelar
2020-12-12 7:05 ` Jonas Bonn
2020-12-12 11:05 ` Harald Welte [this message]
2020-12-12 11:22 ` Harald Welte
2020-12-12 13:59 ` Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 11/12] gtp: netlink update for ipv6 Jonas Bonn
2020-12-12 11:25 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 12/12] gtp: add dst_cache to tunnels Jonas Bonn
2020-12-11 17:25 ` kernel test robot
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=X9Sj/15ebQ9GrKoH@nataraja \
--to=laforge@gnumonks$(echo .)org \
--cc=jonas@norrbonn$(echo .)se \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
--cc=pravin.ovn@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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