Updating STP to work with VLANs and including the feature for switch chips is a big step for mikrotik in the switching bit but will loop detect work on the layer 3 switching component as well? One of the issues i have with the CRS switches is that when multiple layer 3 subnets operate on the same switch that may or may not be related, the switch (not routerOS itself) ends up freezing like as if it is in a loop with the only solution being a reboot despite being able to access management of the switch itself. The switch would require reboot every week or 2 because of this.
I would also like the request LACP on the CRS at the switch level as well and some sort of learning for layer 3 because if i change the port my router is connected to on the CRS i lose internet connectivity as the switch still would think that the router is connected on the old port. I do hope this has been fixed.
It is hard for me to recommend the CRS to anyone over semi managed and ubiquiti switches without switch level LACP and for the switch not to stop forwarding when things change on layer 3 or any of the random problems i get on the switch. The layer 3 segmentation i did was entirely seperate, 2 subnets, 1 with internet access controlled elsewhere and another subnet private which accesses internet via a web proxy on a mikrotik routerboard connected to CRS with more CPU. LACP is commonly used and being able to forward using both mac and IP is great for offloading the load of local traffic to the switch for layer 3 rather than the router.
On the low end both static and LACP are used widely with LACP only used on various inexpensive hardware even prosumer hardware like the latest generations of “performance” wifi routers and NAS.