There are a couple reasons:a) VLACP is a link based protocol, vIST can use any NNI link that is up, so VLACP does not really make sense.b) we only want the vIST session to go down when the peer switch is really down, thus we have pretty long timers, in case there are some intermittent failures, VLACP would interfere with those timers. When vIST session goes down, then vIST nodes convert their SMLT ports to normal ports, thus intermittent IST link down events would increase the risk for loops.I hope this helps, Roger