I doubt it.
It has been said many times by various MT staff. Once they stop using the routing engine embedded in the Linux kernel and rewrite all their own routing code, they can then add the code to support IPV6
Routing marks. Yes, we were first promised it was coming in v6. Now we're being told v7. Like all companies, they have constantly shifting priorities which are led from a number of external and internal factors. So it will be released when they're ready and they believe it's stable (ish!).
Sadly however it's not just the lack of routing mark
functionality that is stopping us using IPV6
in our WISP. There is also missing support with the PPPoE Server and Radius which means we can only provide a IPV4 address to the CPE. Until full IPV6
Radius Attribute functionality is working, we are stuck with using just IPV4 at the moment.