nice brief doc from Carrier... http://www.xpedio.carrier.com/idc/gr...808-417-01.pdf
MM looks like a way to not waste time looking for nodes that arent there...
APDU looks like how long to wait before deciding to move on because on no answer...
Max INFO frames seems like a limit on how much crap an MSTP device is allowed to talk before being compelled to pass the token.
Heres the thing ...Like every polling or master-slave or token passing bus, the physical medium must be solid or the whole system is going to fall down and not work
assuming the physical is correct and the comms is robust it makes me wonder WHY arent things like MM set automatically by the network?
Adding a new MSTP device should beautomatic in my opinion too. Considering that there is already a net-wide unique devID... should be able to hook it on the bus...everybody goes 'whoa dudes...new device here" and comms moves on...in fact why have a MAC at all?? why not shunt around the whole devID its only 2 or 3 bytes bigger than the MAC...ah, but of course because somebody in the committee needs a way to ID a device on the bus with a DIP switch ... so MSTP needs just one more little address space.