Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: NITIN SS <hi.nitin2000@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Distributed RSTP
Date: Thu, 8 Oct 2009 23:01:41 -0700	[thread overview]
Message-ID: <20091008230141.32c57e6e@nehalam> (raw)
In-Reply-To: <88ed5400910071322l360fe50cn2986895549f60f82@mail.gmail.com>

On Wed, 7 Oct 2009 13:22:44 -0700
NITIN SS <hi.nitin2000@gmail.com> wrote:

> Hi,
> 
> I am new to this RSTP/Bridge group and currently planning on distributed
> RSTP.
> 
> First of all, Distributed RSTP mean as, we will have 8 linux RSTPs and they
> all will have the same Bridge ID.

So you plan to take a perfectly good spec 802.1d and break it.
Why?

> As all bridges will have the same Bridge ID so I need to sync many variables
> functions across all units.

You are off in never-never fantasy land. Stop and ask why are you
doing this? It is like the old joke: "Doctor it hurts when I hit
my head with my fist..."

> Additionally there should be only one root port for all the eight bridges.
> In this way there should be one master which would be maintaing bridge
> variables and controlling bridge operations.
> There is only point to point link between all bridges through master.
> Additioanlly most of the RSTP state machines are port based so it looks
> feasible.
> 
> As your guys are RSTP experts, so i think it would be the right place to get
> suggestions/comments.
> 
> -What would be the limitations/complex Issues?
> -Is it feasible?
>  At top level it looks like there would be lot of efforts with respect to
> final outcome.
> -Is there any implementation of distributed RSTP?
> 
> Appreciate your comments.
> 
> Regards,
> Nitin


-- 

      reply	other threads:[~2009-10-09  6:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 20:22 [Bridge] Distributed RSTP NITIN SS
2009-10-09  6:01 ` Stephen Hemminger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091008230141.32c57e6e@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=hi.nitin2000@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox