From: Valdis.Kletnieks@vt.edu
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
Francois Romieu <romieu@fr.zoreil.com>,
Dushan Tcholich <dusanc@gmail.com>,
David Miller <davem@davemloft.net>
Subject: Re: [Bridge] [RFC] bridge: STP timer management range checking
Date: Sun, 31 Aug 2008 22:25:30 -0400 [thread overview]
Message-ID: <19455.1220235930@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 31 Aug 2008 10:43:09 PDT." <20080831104309.780cc01f@extreme>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
On Sun, 31 Aug 2008 10:43:09 PDT, Stephen Hemminger said:
> Warning: this may cause user backlash since apparently working but standards
> conforming configurations will get configuration errors that they didn't
> see before.
Did you mean "apparently working but *non*-standards conforming"?
Other than that, seems to be a sane application of "Be conservative in what you
send". Our network is some 30K cat-5 ports, 1100 switches, 1300 wireless
access points, and we appreciate it every time somebody makes things more
bulletproof. And yes, we prefer things to out-and-out *fail* rather than
run in a wonky configuration - hard failures usually get fixed in a few
minutes, wonkiness can drag on for months of mystifying symptoms...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-09-01 2:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.wTMiBcGRgw2fBtdHwtX7y0lkc8s@ifi.uio.no>
[not found] ` <48975BD3.6040709@shaw.ca>
[not found] ` <a08621850808041337k1d1deb6fk78098d9fcd4930dd@mail.gmail.com>
[not found] ` <20080807185802.GA16327@electric-eye.fr.zoreil.com>
[not found] ` <a08621850808101200n220afd2dve58abe67830b7a4f@mail.gmail.com>
[not found] ` <a08621850808110053j5cbf23e6xdf52c9e7440abf19@mail.gmail.com>
[not found] ` <a08621850808291848q5660148fx57d576ecfcbfce8@mail.gmail.com>
[not found] ` <a08621850808310151o143845h195a8658d02270d9@mail.gmail.com>
[not found] ` <20080831100537.6929c51e@extreme>
2008-08-31 17:43 ` [Bridge] [RFC] bridge: STP timer management range checking Stephen Hemminger
2008-08-31 22:02 ` Alan Cox
2008-08-31 23:29 ` Stephen Hemminger
2008-09-01 8:38 ` Alan Cox
2008-09-02 16:40 ` Rick Jones
2008-09-02 23:41 ` David Miller
2008-09-03 0:00 ` Rick Jones
2008-09-01 2:25 ` Valdis.Kletnieks [this message]
2008-09-03 0:28 ` David Miller
2008-09-04 22:47 ` [Bridge] [PATCH] bridge: don't allow setting hello time to zero Stephen Hemminger
2008-09-08 20:46 ` David Miller
2008-09-08 21:35 ` Dushan Tcholich
2008-09-08 22:33 ` Stephen Hemminger
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=19455.1220235930@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dusanc@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@vyatta.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