Re: [PATCH net-next 00/13] amt: add an IPv6 outer transport
From: Jakub Kicinski
Date: Tue Oct 20 2026 - 13:55:13 EST
On Tue, 20 Oct 2026 15:45:34 +0300 Omar Ramadan wrote:
> Yes. We currently use the existing IPv4 AMT relay and gateway
> implementation in a multicast delivery network (TreeDN
> <https://community.networking.hpe.com/blogs/lenny/2025/08/21/introduction-to-treedn>).
> Gateways on access networks send IGMP/MLD membership state through an AMT
> relay to reach downstream receivers. The IPv6 outer transport work is
> motivated by gateways whose access networks are IPv6-only; the inner
> multicast family remains independent of the outer transport.
Interesting, thanks for the context!
> My experience with the existing code is from operating and exercising this
> path, including reproducing the lifetime, authentication, teardown, and
> input-validation issues addressed by the net series. I
> agree that the patch stream exposed bugs in the existing implementation,
> and the reviews have helped separate those fixes from the IPv6 transport
> work. I’ll wait for net-next to reopen, then repost the IPv6 series with
> the net fixes as its prerequisite.