Warning: This email is from an unusual correspondent.
Warning: Make sure this is someone you trust.

Hi Max,

On 1/23/26 7:24 AM, Maximilian Stinsky-Damke wrote:
> Hello,
>
> I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609:
>  https://urlsand.esvalabs.com/?u=https%3A%2F%2Fbugs.launchpad.net%2Fneutron%2F%2Bbug%2F1998609&e=50525cf7&h=c524c6f9&f=y&p=y ) and the associated
> patch ( https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F867513&e=50525cf7&h=986f6524&f=y&p=y ).
> As noted in the bug comments, Roberto Bartzen Acosta maintained this
> patch across multiple release cycles, but it hasn't received reviews
> from core maintainers and is currently blocked by merge conflicts.
> Roberto mentioned that the feature hasn't been getting traction despite
> the work put in.

Sorry, sometimes things fail to get reviewer traction for any number of
reasons, thanks for making us aware of this one.

> This feature would enable distributed routing for IPv6 GUA addresses in
> OVN deployments, similar to how IPv4 FIPs work with DVR today.
> The spec was approved and merged ( https://urlsand.esvalabs.com/?u=https%3A%2F%2Freview.opendev.org%2Fc%2F&e=50525cf7&h=05481b12&f=y&p=y 
> openstack/neutron-specs/+/867979), indicating community interest.
>
> Before I invest time rebasing the patch and resolving merge conflicts,
> I'd like to understand:
> 1. Are there technical or architectural concerns that have prevented review?
> 2. Is there a reason this hasn't been prioritized, or is it a matter of
> reviewer availability?
> 3. Would core maintainers be willing to review if the patch is rebased
> and updated?
>
> I'm happy to do the rebase work, but I'd prefer not to spend time on
> something that won't be merged.
> Any guidance on the status and viability of this feature would be
> appreciated.

I don't think there are any concerns with the team based on looking at
the spec and comments.

What I would recommend is to re-base and fix any merge conflicts, then
set the "Review Priority +1" flag on the review, that way it will show
up in our dashboard. Unfortunately every time you re-base you have to
set the flag again as it's not sticky.

Thanks,

-Brian

--
This message has been checked by Libraesva ESG and is found to be clean.
Follow this link to report as spam/bad:
https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/report-as-bad
Follow this link to blocklist sender:
https://mx10.wiit.cloud/action/4f0Qtf2fQfzTgMD/blocklist