Not to mention MPLS is very broken on MikroTik.... After years of dealing with sporadic mismatches in forwarding table that causes unreachable customers/devices/routers i've resorted to completely ripping MPLS out of our MikroTik network. It's just not the right way to run a business having to randomly reboot up to half the routers in the network to re-establish connectivity for 1 client, solely because MPLS has a forwarding table bug
Agreed. MPLS works, but you have to suffer a lot of issues to learn what you can and can't do and compensate. It's certainly not seamless. It's also layers on layers, just makes for more complex training to get techs to handle it.
SPB is a bridge that has better logging in it's most basic form and uses IS-IS on layer 2 which is also basically just 'turn it on' in it's most basic form.
For an *ISP it's a preconfiguration for the most part and then adding extra metric on backup/slower interfaces. More complex solutions also possible but I think the simplest model is good enough for the 90% and would really help a lot of operators. It could help expand the technical pool to maintain things for sure. I would for me, i can train someone to look at the SPB logs to see a problem and more importantly they can solve link issues without worrying about getting IP addresses and VLANs correct etc.
I think SPB is the better and more widely supported protocol so I pick that over TRILL or LISP and it's already supported in the hardware on some of the mikrotik models with Marvell chips.
IMO, SPB is the easiest thing to implement on mikrotik on specific hardware because it's just exposing hardware features and writing front end for the most part. Only real concern is if they had to pull in a software implementation for unsupported devices. This is why I also request SRv6. IS-IS+IPv6+SRv6 is also really simple to implement and can provide tunneling and traffic engineering.