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

["Eric Gray \(LO/EUS\)" <eric.gray at ericsson.com>]

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: rbridge-bounces at postel.org 
> [mailto:rbridge-bounces at postel.org] On Behalf Of Harald Tveit 
> Alvestrand
> Sent: Wednesday, March 21, 2007 3:59 AM
> To: Silvano Gai; ietf at ietf.org
> Cc: rbridge at postel.org
> 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 
> <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 soFrom ietf-bounces at ietf.org Wed Mar 21 05:36:19 2007
Return-path: <ietf-bounces at ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTxBz-0006bw-H9; Wed, 21 Mar 2007 05:33:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTxBy-0006ag-F8
	for ietf at ietf.org; Wed, 21 Mar 2007 05:33:14 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTxBr-0004dC-Jo
	for ietf at ietf.org; Wed, 21 Mar 2007 05:33:14 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l2L9w68G032638;
	Wed, 21 Mar 2007 03:58:07 -0600
Received: from eusrcmw721.eamcs.ericsson.se ([138.85.77.21]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 21 Mar 2007 04:33:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Mar 2007 04:32:55 -0500
Message-ID: <941D5DCD8C42014FAF70FB7424686DCF9EAE87 at eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <F98B60942429F3C001DF51B0 at [10.0.0.174]>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rbridge] Last Call: draft-ietf-trill-routing-reqs
	(TRILL	RoutingRequirements in Support of RBridges) to
	Informational RFC
Thread-Index: AcdrkMnZHwLXJBpAS9ixOUgLC+15IQAAe9VA
References: <E1HSKM4-0001KO-4Q at stiedprstage1.ietf.org><34BDD2A93E5FD84594BB230DD6C18EA2013B49F4 at nuova-ex1.hq.nuovaimpresa.com>
	<F98B60942429F3C001DF51B0 at [10.0.0.174]>
From: "Eric Gray \(LO/EUS\)" <eric.gray at ericsson.com>
To: "Harald Tveit Alvestrand" <harald at alvestrand.no>,
	"Silvano Gai" <sgai at nuovasystems.com>, <ietf at ietf.org>
X-OriginalArrivalTime: 21 Mar 2007 09:33:02.0092 (UTC)
	FILETIME=[EBA524C0:01C76B9B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: rbridge at postel.org
Subject: RE: [rbridge] Last Call: draft-ietf-trill-routing-reqs
	(TRILL	RoutingRequirements in Support of RBridges) to
	Informational RFC
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Errors-To: ietf-bounces at ietf.org

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: rbridge-bounces at postel.org 
> [mailto:rbridge-bounces at postel.org] On Behalf Of Harald Tveit 
> Alvestrand
> Sent: Wednesday, March 21, 2007 3:59 AM
> To: Silvano Gai; ietf at ietf.org
> Cc: rbridge at postel.org
> 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 
> <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
> 
> _______________________________________________
> rbridge mailing list
> rbridge at postel.org
> http://mailman.postel.org/mailman/listinfo/rbridge
> 

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf