Rapid Spanning Tree Protocol (RSTP)

o STP ensures a loop-free network but has a slow network topology convergence speed, leading to
service deterioration. If the network topology changes frequently, the connections on the STP
capable network are frequently torn down, causing regular service interruption.

o RSTP employs a proposal and agreement process which allows for immediate negotiation of
links to take place, effectively removing the time taken for convergence based timers to expire
before spanning tree convergence can occur. The proposal and agreement process tends to
follow a cascading effect from the point of the root bridge through the switching network, as
each downstream switch begins to learn of the true root bridge and the path via which the root
bridge can be reached.

RSTP Edge Ports

- In RSTP, a designated port on the network edge is called an edge port. An edge port directly
connects to a terminal and does not connect to any other switching devices. An edge port does
not receive configuration BPDU, so it does not participate in the RSTP calculation.
- It can directly change from the Disabled state to the Forwarding state without any delay, just
like an STP-incapable port. If an edge port receives bogus configuration BPDU from attackers, it
is deprived of the edge port attributes and becomes a common STP port. The STP calculation is
implemented again, causing network flapping.

Port States of RSTP

- RSTP introduces a change in port states that are simplified from five to three types. These port
types are based on whether a port forwards user traffic and learns MAC addresses. If a port
 neither forwards user traffic nor learns MAC addresses, the port is in the Discarding state. The
port is considered to be in a learning state where a port does not forward user traffic but learns
MAC addresses. Finally where a port forwards user traffic and learns MAC addresses, the port is
said to be in the Forwarding state.

RSTP BPDU

In STP, after the topology becomes stable, the root bridge sends configuration BPDU at an interval set by
the Hello timer. A non-root bridge does not send configuration BPDU until it receives configuration
BPDU sent from the upstream device. This renders the STP calculation complicated and time-consuming.
In RSTP, after the topology becomes stable, a non-root bridge sends configuration BPDU at Hello
intervals, regardless of whether it has received the configuration BPDU sent from the root bridge; such
operations are implemented on each device independently.