L3VPN became usable with 6.2, e.g. Mikrotik fixed the L3VPN withdrawl bug. As for Route Leaking, it has always worked for us, Maybe Tomas was doing something different from us…
However there are still some major bugs in RouterOS v6 routing. e.g. BGP NLRI’s are not sent when a route received via PE-CE BGP becomes active over a L3VPN received route.
These will not be fixed until we see “new routing” which will only appear in the next major RouterOS version, which unfortunately has no ETA
Do you mean OSPF as a PE-CE protocol in a VRF? If so, then yes, this works. However I would not reccomend it, L3VPN is flaky enough without adding another variable…
If I remember correctly, inter AS MPLS will work as long as you enable BGP multi hop over OSPF and run LDP between the two peers. While this isn’t the same solution you using with the Cisco routers, it should allow you to exchange labels.
Also, VRF leaking does work. We’ve built a number of production environments that rely on VRF leaking.
Some time ago I had to connect a Mikrotik MPLS with a Cisco MPLS for VPNv4 service. I was not brave enough to even think about trying inter-as option B. I did read about the RouterOS difficulties in BGP PE-CE (or inter-as option a, which is basically the same), so I decided to use OSPF PE-CE as the choice I believed to be the safest.
May I ask you to make more clear statement? The LDP do not pass over BGP because LDP nature. LDP can use IGP routing protocol only (OSPF or ISIS).
I tried to use separate OSPF instance for inter-AS connection in parallel with BGP connection but It was (a) wrong by design, (b) routes did not passed (c) it was just mess