From: Yuya Kusakabe <yuya.kusakabe@gmail.com>
To: David Ahern <dsahern@kernel.org>, netdev@vger.kernel.org
Cc: Andrea Mayer <andrea.mayer@uniroma2.it>,
Andrea Mayer <andrea@common-net.org>,
Yuya Kusakabe <yuya.kusakabe@gmail.com>
Subject: [PATCH RFC iproute2-next 0/2] seg6: add support for the SRv6 End.MAP behavior
Date: Fri, 10 Jul 2026 21:18:17 +0900 [thread overview]
Message-ID: <20260710-seg6-mobile-end-map-v1-0-970275f3d80b@gmail.com> (raw)
This series adds support for the "seg6mobile" lightweight tunnel, the
iproute2 counterpart of the SRv6 Mobile User Plane (RFC 9433) kernel
RFC series [1], starting with the End.MAP behavior.
Patch 1 imports the new UAPI headers as a standalone patch so it can
be dropped once the matching kernel header lands. The selftest in
the kernel series needs the "seg6mobile" keyword to run.
[1] https://lore.kernel.org/netdev/20260710-seg6-mobile-end-map-v1-0-99be02d68143@gmail.com/
Signed-off-by: Yuya Kusakabe <yuya.kusakabe@gmail.com>
---
Yuya Kusakabe (2):
uapi: sync lwtunnel.h and add seg6_mobile.h
seg6: add support for the End.MAP behavior under seg6mobile encap
include/uapi/linux/lwtunnel.h | 1 +
include/uapi/linux/seg6_mobile.h | 58 +++++++++++++
ip/iproute.c | 6 +-
ip/iproute_lwtunnel.c | 173 +++++++++++++++++++++++++++++++++++++++
man/man8/ip-route.8.in | 24 ++++++
5 files changed, 260 insertions(+), 2 deletions(-)
---
base-commit: 37c491d82cebef070173878e167076a1956dcd92
change-id: 20260523-seg6-mobile-end-map-6f5560bfb68e
Best regards,
--
Yuya Kusakabe <yuya.kusakabe@gmail.com>
next reply other threads:[~2026-07-10 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 12:18 Yuya Kusakabe [this message]
2026-07-10 12:18 ` [PATCH RFC iproute2-next 1/2] uapi: sync lwtunnel.h and add seg6_mobile.h Yuya Kusakabe
2026-07-10 12:18 ` [PATCH RFC iproute2-next 2/2] seg6: add support for the End.MAP behavior under seg6mobile encap 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=20260710-seg6-mobile-end-map-v1-0-970275f3d80b@gmail.com \
--to=yuya.kusakabe@gmail.com \
--cc=andrea.mayer@uniroma2.it \
--cc=andrea@common-net.org \
--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