Ethernet Bridge development
 help / color / mirror / Atom feed
From: Martino Fornasa <m.fornasa@cipi.unige.it>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] RSTP implementation status
Date: Tue, 08 Nov 2011 10:37:56 +0100	[thread overview]
Message-ID: <4EB8F874.8090408@cipi.unige.it> (raw)

Hi all.
I'm interested in RSTP implementation (and maybe in contributing to it).

I read this 
[http://lkml.indiana.edu/hypermail/linux/net/0807.1/0011.html] message, 
and I had a look on the ongoing RSTP project hosted at 
[https://github.com/shemminger/RSTP]. Is this project still running?

I noticed that such a ongoing project is based on rstplib 
[http://rstplib.sourceforge.net/]. By taking a brief look at the code, 
it seems to me that such a code is based on the obsolete 802.1w 
specification, while the newest specification for RSTP is contained in 
802.1D-2004; and such a specification (beside incorporating 
compatibility with STP) is radically different from 802.1w (e.g., 
different set of states on state machines...), and it is not easy to 
understand the amount of interoperability between the two.

I think that a serious issue in implementing network bridging/routing 
protocols is to proper validate and testing it. For example, I know that 
there are companies that offer commercial validation system for network 
protocol. As some RSTP implementations as been put in the past in the 
kernel, and STP is already in it, are such implementations have been 
tested and validated? How?

B.R., Martino Fornasa.


             reply	other threads:[~2011-11-08  9:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  9:37 Martino Fornasa [this message]
2011-11-08 10:32 ` [Bridge] RSTP implementation status Vitalii Demianets
2011-11-23 10:57   ` Martino Fornasa
2011-11-23 18:52     ` Vitalii Demianets

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=4EB8F874.8090408@cipi.unige.it \
    --to=m.fornasa@cipi.unige.it \
    --cc=bridge@lists.linux-foundation.org \
    /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