[Rstplib-users] Q: Root port waits for 'slow' Designated Port in .1w ?

[<al...@nb...>]

Let's consider the following initial configuration: we
have 3 Bridges (A, B, C) ,
Bridge A has a Designated Port A2, connected to Root Port B1 of
Bridge B. Bridge B is connected to Port C1 of Bridge C via Designated
Port B2.
Bridge A has the "best" Bridge priority and always will be Root Bridge.
Bridge C has Bridge priority "better" then Bridge B and worse then Bridge A.

Now we will close the ring: connect Port C2 to A1.
Port C2 becomes Root Port of the C, Port C1 changes its role from
Root to Designated; on Bridge B Port B2 changes its role from Designated to
Alternate and becomes Discarding.

The problem is that Port C2 becomes Forwarding not immediately but
after FdDelay ("slow" hop)

Explanation.
Actually, the problem seems to be between C1 & B2. Port C1 goes
from Root to Designating, however since it was in Forwarding state and PRT
(17.23.2) doesn't go to DESIGNATED_PROPOSE, it waits for rrWhile
expiration (15 seconds). During this time Port C2 reRooted is equal False
due to rrWhile on port C1.

The question:
What is wrong ? Or: is it an appropriative behavior ?

Another related question:
I see, that when a Designated Port wants to change to Forwarding state,
but its partner is an Alternate port,
it waits for 'agreed' flag and makes *slow* state transition too.
I think, it is not a "big deal", since anyway the active topology doesn't
contain this connection. Am I right ?

Thanks for your help,
Alex