From: Hangbin Liu <hangbin.liu@linux.dev>
To: Saphal Poudyal <mail@saphal.me>
Cc: Minhong He <heminhong@kylinos.cn>,
andrea.mayer@uniroma2.it, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, horms@kernel.org,
linux-kernel@vger.kernel.org,
Andrea Mayer <andrea@common-net.org>
Subject: Re: [PATCH net-next 0/3] seg6_local: add USP and USD flavors support (RFC 8986)
Date: Thu, 19 Nov 2026 08:46:09 +0800 [thread overview]
Message-ID: <av5G0UmlURQt65uW@fedora> (raw)
In-Reply-To: <3dd85ab7-2270-422d-9595-c7f1d9612e82@saphal.me>
Hi Saphal,
On Thu, Nov 19, 2026 at 12:25:14AM +0000, Saphal Poudyal wrote:
> On 11/4/26 01:22, Hangbin Liu wrote:
>
> > Kernel changes alone are not sufficient, we also need selftest updates for
> > this new feature. So I’ve begun adding PSP support for End.X, along with the
> > corresponding selftests. The USP/USD kernel updates are already in my local
> > tree.
> Hi Hangbin,
>
> Good to hear that work has been started on this. For USD, this series
> only defines USD for decapsulating behaviors (End.DX4, End.DT6 etc.). I
> wanted to confirm if your USD work covers End, End.X and End.T as
> specified in RFC 8986 section 4.16.3.
Yes, the USD flavor should work with End, End.X, and End.T as RFC defines.
>
> It's a piece I need to make SRv6 TI-LFA work (terminate the repair
> tunnels). I'm working through FRR's SRv6 TI-LFA and it leaves out the
> decapsulation part on the Q-node.
>
> I'd be glad to test your series with FRR once it's posted.
Good to know there’s a use case. I’ll post the series and Cc you once the
PSP series work is finished.
Thanks
Hangbin
next prev parent reply other threads:[~2026-11-19 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 0:25 Saphal Poudyal
2026-11-19 0:46 ` Hangbin Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-03 6:38 Minhong He
2026-11-04 7:22 ` Hangbin Liu
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=av5G0UmlURQt65uW@fedora \
--to=hangbin.liu@linux.dev \
--cc=andrea.mayer@uniroma2.it \
--cc=andrea@common-net.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=heminhong@kylinos.cn \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@saphal.me \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®