How Rapid STP reacts to change - Proposal/agreement process

Rapid STP: proposal/agreement process Today I will talk about how Rapid Spanning Tree Protocol uses proposal/agreement negotiation process to handle network topology changes. This video is part 2 of the Rapid Spanning Tree protocol. Rapid STP proposal and agreement process is very quick because it does not depend on traditional BPDU timers as the standard Spanning Tree Protocol does. Instead, a switch negotiates its neighbors directly. Rapid Spanning Tree protocol provides faster topology change detection and much faster convergence time than the standard spanning tree protocol. It is widely used in a large network with many switches. My whole playlists: https://www.youtube.com/user/sunnylearning/playlists Related Playlists Ethernet Basics: https://www.youtube.com/watch?v=FkH_J-IZbpU&list=PLSNNzog5eydvAxPHJiDybPomC1fFHf1KE IPv4 Basics: https://www.youtube.com/watch?v=vcArZIAmnYQ&list=PLSNNzog5eydt_plAtt3k_LYuIXrAS4aDZ OSI Model and related: https://www.youtube.com/watch?v=nFnLPGk8WjA&list=PLSNNzog5eydtQcezP4OrrLL5preHLLkGA Rapid Spanning Tree protocol, IEEE802.1W, RSTP, handshake, negotiations, convergence, proposal/agreement, synchronization, blocking state, edge port, p2p link, BPDU flags, BPDU timers, Bridging Protocol Data Unit, alternate port, designated port.