[rbridge] Comments on: http://www.ietf.org/internet-drafts/draft-ietf-trill-rbridge-arch-01.txt

sgai at nuovasystems.com (Silvano Gai) Tue, 31 October 2006 22:35 UTC

From: "sgai at nuovasystems.com"
Date: Tue, 31 Oct 2006 14:35:50 -0800
Subject: [rbridge] Comments on: http://www.ietf.org/internet-drafts/draft-ietf-trill-rbridge-arch-01.txt
Message-ID: <34BDD2A93E5FD84594BB230DD6C18EA2B4B9AE@nuova-ex1.hq.nuovaimpresa.com>

Eric,

Inline

> -----Original Message-----
> From: Gray, Eric [mailto:Eric.Gray at marconi.com]
> Sent: Tuesday, October 31, 2006 9:43 AM
> To: Silvano Gai
> Cc: rbridge at postel.org
> Subject: RE: [rbridge] Comments on: http://www.ietf.org/internet-
> drafts/draft-ietf-trill-rbridge-arch-01.txt
> 
> Silvano,
> 
> 	Please see below...
> 
> --
> Eric
> 
> -- [snip] --
> -->
> --> Sgai 3> It is very important to say that this protocol must
provide a
> --> loop free topology for multicast/broadcast under any condition,
> including
> --> transient loops, to prevent multicast/broadcast storm.
> -- [snip] --
> 
> I think I know what you're trying to say here, but "topology" is not
> the right word.  This is probably a point of confusion - based on the
> way STP works - that you're bringing up and I may need to fix.  I do
> not recall using "topology" in this specific context, however (L2 link
> topology refers to "physical topology" and specifically to discovery).
> 
> What I think you're trying to say is that it is important to say that
> the protocol must ensure loop free delivery - particularly in regard
> to multicast, broadcast and flooded frames.
> 

AGREED

-- Silvano


> -- [snip --