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

2007-03-21 Thread Harald Tveit Alvestrand
--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

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

2007-03-21 Thread Pekka Savola
On Wed, 21 Mar 2007, Harald Tveit Alvestrand wrote: --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

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

2007-03-21 Thread Eric Gray (LO/EUS)
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.

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

2007-03-21 Thread Silvano Gai
This document has some issues that need to be corrected before it can pass an IESG last call. In order of importance: 1) The document equates Ethernet with IEEE 802 and this is clearly incorrect, since IEEE 802 includes also technologies like Token Ring, DQDB, Wireless that are clearly outside