On Wed, 2016-08-03 at 14:49 +0200, Richard Cochran wrote:
> Contrary to the letter of the standard, we do not throw a state
> decision
> event every announce interval, but only when the inputs to the
> algorithm
> have changed. When a port on a BC forms a spanning tree by deciding
> between the
If a non-slave port on a boundary clock see an announce message, then it
must decide whether it should take on the MASTER or the PASSIVE role. When
the GM fields from the local clock are identical to those in the announce,
then the sender/receiver ports are used as a tie breaker.
Following a
