[rbridge] Last Call: draft-ietf-trill-routing-reqs (TRILL RoutingRequirements in Support of RBridges) to Informational RFC

[Harald Tveit Alvestrand]

--On 20. mars 2007 09:35 -0700 Silvano Gai <sgai at nuovasystems.com> wrote:

> 5) Introduction - Bridging limitation. The first paragraph refers to
> Ethernet networks used without Spanning Tree. This is irrelevant, since
> Spanning Tree is always deployed in conjunction with Ethernet. The
> correct contrast must be between Ethernet with Spanning Tree and
> Ethernet with TRILL. The claim of a single broadcast/flooding domain is
> incorrect since VLANs have solved this issue many years ago.

"always" is too strong, since most unmanaged bridges (intended for 
consumers' home networks, but often dangled off the edge of corporate 
networks as port expanders, without asking for permission) don't seem to be 
supporting Spanning Tree. However, these are not going to support TRILL 
either, so for the environments considered here, "always" is probably true.

               Harald