I cannot say when, but yes, this is the plan. IKEv1 is no longer secure enough, as per what the IETF stated a few years back - ref https://datatracker.ietf.org/doc/rfc9395/ - and IKEv2 can handle client addressing natively, so there's no more reason to keep using L2TP for it.
Expanded BGP attribute support to include outbound well-known and custom communities and increased route integrity with inbound filtering.
Keen to test this new functionality - does anybody know where the configuration option would be? Checked under SD-WAN > Routing and no new options there that I can see!
Within Security & SD-WAN > Routing, Outbound community string and Inbound route filter is now available within eBGP peers in the Route control section: