Harald,
As it was originally chartered, the TRILL working group allowed
scope for definition of TRILL bridges that could be cheaply produced,
modulo the inclusion of a ink-state routing protocol as a complicating
factor. It is not clear at this point that this has changed.
Consequently, at least some of the people working on this are
thinking that a <well-known but not named here> work group switch may
very well be replaced by a TRILL capable bridge - possibly made by the
same vendor, at the same manufacturing facility.
--
Eric
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Harald Tveit
> Alvestrand
> Sent: Wednesday, March 21, 2007 3:59 AM
> To: Silvano Gai; [email protected]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [rbridge] Last Call:
> draft-ietf-trill-routing-reqs (TRILL RoutingRequirements in
> Support of RBridges) to Informational RFC
>
>
>
> --On 20. mars 2007 09:35 -0700 Silvano Gai
> <[EMAIL PROTECTED]> 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
>
> _______________________________________________
> rbridge mailing list
> [EMAIL PROTECTED]
> http://mailman.postel.org/mailman/listinfo/rbridge
>
_______________________________________________
Ietf mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf