From: Simon Horman <horms@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, laforge@osmocom.org,
pespin@sysmocom.de, osmith@sysmocom.de
Subject: Re: [PATCH net-next,v3 05/12] gtp: use IPv6 address /64 prefix for UE/MS
Date: Thu, 9 May 2024 13:15:57 +0100 [thread overview]
Message-ID: <20240509121557.GO1736038@kernel.org> (raw)
In-Reply-To: <20240506235251.3968262-6-pablo@netfilter.org>
On Tue, May 07, 2024 at 01:52:44AM +0200, Pablo Neira Ayuso wrote:
> Harald Welte reports that according to 3GPP TS 29.060:
>
> PDN Connection: the association between a MS represented by one IPv4
> address and/or one IPv6 prefix and a PDN represented by an APN.
>
> this clearly states that IPv4 is a single address while IPv6 is a single prefix.
>
> Then, 3GPP TS 29.061, Section 11.2.1.3:
>
> For APNs that are configured for IPv6 address allocation, the GGSN/P-GW
> shall only use the Prefix part of the IPv6 address for forwarding of mobile
> terminated IP packets. The size of the prefix shall be according to the maximum
> prefix length for a global IPv6 address as specified in the IPv6 Addressing
> Architecture, see RFC 4291 [82].
>
> RFC 4291 section 2.5.4 states
>
> All Global Unicast addresses other than those that start with binary 000
> have a 64-bit interface ID field (i.e., n + m = 64) ...
>
> 3GPP TS 29.61 Section 11.2.1.3.2a:
>
> In the procedure in the cases of using GTP-based S5/S8, P-GW acts as an
> access router, and allocates to a UE a globally unique /64 IPv6 prefix if the
> PLMN allocates the prefix.
>
> Therefore, compare IPv6 address /64 prefix only since MS/UE is not a single
> address like in the IPv4 case.
>
> Reject IPv6 address with EADDRNOTAVAIL if it lower 64 bits of the IPv6 address
> from the control plane are set.
>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-05-09 12:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 23:52 [PATCH net-next,v3 00/12] gtp updates for net-next (v3) Pablo Neira Ayuso
2024-05-06 23:52 ` [PATCH net-next,v3 01/12] gtp: remove useless initialization Pablo Neira Ayuso
2024-05-09 10:19 ` Simon Horman
2024-05-10 13:10 ` patchwork-bot+netdevbpf
2024-05-06 23:52 ` [PATCH net-next,v3 02/12] gtp: properly parse extension headers Pablo Neira Ayuso
2024-05-09 12:14 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 03/12] gtp: prepare for IPv6 support Pablo Neira Ayuso
2024-05-09 12:15 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 04/12] gtp: add " Pablo Neira Ayuso
2024-05-09 12:15 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 05/12] gtp: use IPv6 address /64 prefix for UE/MS Pablo Neira Ayuso
2024-05-09 12:15 ` Simon Horman [this message]
2024-05-06 23:52 ` [PATCH net-next,v3 06/12] gtp: pass up link local traffic to userspace socket Pablo Neira Ayuso
2024-05-09 12:16 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 07/12] gtp: move debugging to skbuff build helper function Pablo Neira Ayuso
2024-05-09 12:16 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 08/12] gtp: remove IPv4 and IPv6 header from context object Pablo Neira Ayuso
2024-05-09 12:17 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 09/12] gtp: add helper function to build GTP packets from an IPv4 packet Pablo Neira Ayuso
2024-05-09 12:17 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 10/12] gtp: add helper function to build GTP packets from an IPv6 packet Pablo Neira Ayuso
2024-05-09 12:17 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 11/12] gtp: support for IPv4-in-IPv6-GTP and IPv6-in-IPv4-GTP Pablo Neira Ayuso
2024-05-09 12:18 ` Simon Horman
2024-05-06 23:52 ` [PATCH net-next,v3 12/12] gtp: identify tunnel via GTP device + GTP version + TEID + family Pablo Neira Ayuso
2024-05-09 12:19 ` Simon Horman
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=20240509121557.GO1736038@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=laforge@osmocom.org \
--cc=netdev@vger.kernel.org \
--cc=osmith@sysmocom.de \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=pespin@sysmocom.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).