2.1.f Implement and troubleshoot spanning-tree

802.1d was improved dramatically with 802.1w… the impact is faster convergence… 802.1w rolled into it 802.1d’s disabled, blocking and listening states and renamed this new state discarding… what is the difference since cisco’s 802.1w implementation still notes this operationally as BLK in it’s output… functionally it is faster…  is it blocking? sure… ultimately the big difference is the port state  is called discarding, and it’s faster getting to learning and forwarding… should i stop caring? probably, although it seemed like a big deal for ccnp… i’m going to shut up now…