From: Yuya Kusakabe <yuya.kusakabe@gmail.com>
To: dsahern@kernel.org
Cc: Yuya Kusakabe <yuya.kusakabe@gmail.com>, netdev@vger.kernel.org
Subject: [PATCH iproute2-next v2 0/6] seg6: SRv6 Mobile User Plane (RFC 9433)
Date: Tue, 05 May 2026 01:10:40 +0900 [thread overview]
Message-ID: <20260505-seg6-mobile-v2-0-93291b7b0134@gmail.com> (raw)
This series adds the iproute2 frontend for the SRv6 Mobile User Plane
(MUP) endpoint behaviors of RFC 9433. It is sent in parallel with the
matching kernel net-next series; each commit here is self-contained
and brings in the seg6local UAPI bits it needs from the in-progress
kernel UAPI header (include/uapi/linux/seg6_local.h):
Section 6.2 End.MAP
Section 6.3 End.M.GTP6.D
Section 6.4 End.M.GTP6.D.Di
Section 6.5 End.M.GTP6.E
Section 6.6 End.M.GTP4.E
Section 6.7 H.M.GTP4.D
The series adds these seg6local CLI keywords:
src IPv6 source-address template
v4_mask_len length of the IPv4 DA portion of the SID, in
bits (1..32)
sr_prefix_len locator length of the egress End.M.GTP*.E SID,
in bits (1..88, leaving 40 bits for the
Args.Mob.Session field)
v6_src_prefix_len Source UPF Prefix length P in the IPv6 SA
template (1..127, defaults to 64); requires
P + v4_mask_len <= 128
pdu_type GTP-U PDU Session Container PDU Type (3GPP
TS 38.415 Section 5.5.2): downlink|dl|uplink|ul
or 0..15. When omitted, the egress emits a
short GTPv1-U header (no PDU Session Container)
regardless of the QFI in the SID; 5G N3
deployments must set pdu_type explicitly.
The matching kernel series has been posted to net-next:
https://lore.kernel.org/r/20260504-srv6-mup-v1-v1-0-e0a6791575cb@gmail.com
Link: https://datatracker.ietf.org/doc/html/rfc9433
Changes since v1:
- Drop the per-action userspace attribute validator entirely per
Stephen Hemminger's review. invarg() expects the offending value
as its second argument, but the validator runs after parsing and
has no argv to pass; the kernel already returns a clean EINVAL via
netlink extack for the same conditions, matching how every other
seg6local action is structured.
- Link to v1: https://lore.kernel.org/netdev/20260503154510.912576-1-yuya.kusakabe@gmail.com/
Signed-off-by: Yuya Kusakabe <yuya.kusakabe@gmail.com>
---
Yuya Kusakabe (6):
seg6: add support for the End.MAP behavior
seg6: add support for the End.M.GTP4.E behavior
seg6: add support for the End.M.GTP6.E behavior
seg6: add support for the End.M.GTP6.D behavior
seg6: add support for the End.M.GTP6.D.Di behavior
seg6: add support for the H.M.GTP4.D behavior
include/uapi/linux/seg6_local.h | 17 +++++
ip/iproute.c | 9 ++-
ip/iproute_lwtunnel.c | 149 +++++++++++++++++++++++++++++++++++++-
man/man8/ip-route.8.in | 154 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 326 insertions(+), 3 deletions(-)
---
base-commit: 4f5de57e2ff11a5925dacdf3deeeabee7ba9502a
change-id: 20260504-seg6-mobile-5345055f6608
Best regards,
--
Yuya Kusakabe <yuya.kusakabe@gmail.com>
next reply other threads:[~2026-05-04 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 16:10 Yuya Kusakabe [this message]
2026-05-04 16:10 ` [PATCH iproute2-next v2 1/6] seg6: add support for the End.MAP behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 2/6] seg6: add support for the End.M.GTP4.E behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 3/6] seg6: add support for the End.M.GTP6.E behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 4/6] seg6: add support for the End.M.GTP6.D behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 5/6] seg6: add support for the End.M.GTP6.D.Di behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 6/6] seg6: add support for the H.M.GTP4.D behavior Yuya Kusakabe
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=20260505-seg6-mobile-v2-0-93291b7b0134@gmail.com \
--to=yuya.kusakabe@gmail.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
/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