From: David Brownell <david-b@pacbell.net>
To: jamal <hadi@cyberus.ca>, Stefan Rompf <srompf@isg.de>
Cc: netdev@oss.sgi.com
Subject: Re: Patch: Device operative state notification against 2.5.7
Date: Mon, 08 Apr 2002 10:48:51 -0700 [thread overview]
Message-ID: <035c01c1df3b$17243d40$6800000a@brownell.org> (raw)
In-Reply-To: Pine.GSO.4.30.0204071623470.12041-100000@shell.cyberus.ca
> > The only useful state transitions are to/from IFOP_DOWN_NOCARRIER
> > in my opinion. What do you think?
>
> I meant this view from a "listener" perspective; example from an
> SNMP NMS perspective or even a dynamic route daemon, this is the only
> really interesting state transition. So IMO, it only makes sense to send
> netlink messages for these.
But ... how about "carrier on"? What else would be able to trigger
software to bring the interface up (so it could be routed or bridged)
if there were no notification for "carrier on"? Not expecting some
administrator to be initating it (or eyeballing some status display);
one can ignore alerts, but one can't create them from nothing.
This is where my "asymmetry in design" alert triggers. It's usually
been a good early warning system for trouble ... :)
- Dave
next prev parent reply other threads:[~2002-04-08 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CACB9BC.4D585C25@isg.de>
2002-04-07 20:16 ` Patch: Device operative state notification against 2.5.7 jamal
2002-04-07 20:26 ` jamal
2002-04-08 17:48 ` David Brownell [this message]
2002-04-07 22:11 ` Michael Richardson
2002-04-08 11:59 ` jamal
2002-04-09 11:28 ` Stefan Rompf
2002-04-11 11:24 ` jamal
2002-04-12 10:12 ` Stefan Rompf
2002-04-09 11:43 ` QoS _put, _get and _delete class ops semantic Martin Devera
2002-04-11 12:35 ` jamal
2002-04-11 13:41 ` Martin Devera
2002-04-11 14:42 ` jamal
[not found] <Pine.GSO.4.30.0203302133110.7012-100000@shell.cyberus.ca>
2002-03-31 10:23 ` Patch: Device operative state notification against 2.5.7 Stefan Rompf
2002-03-31 10:23 ` Stefan Rompf
2002-03-31 16:21 ` jamal
2002-04-01 14:44 ` Stefan Rompf
2002-04-01 16:25 ` jamal
2002-04-01 20:31 ` David Brownell
2002-04-02 3:05 ` jamal
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='035c01c1df3b$17243d40$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=srompf@isg.de \
/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;
as well as URLs for NNTP newsgroup(s).