Re: "straps [port]"

Cameron Laird (claird@Starbase.NeoSoft.COM)
Tue, 5 Nov 1996 06:07:46 -0600 (CST)

From schoenw@cs.utwente.nl Tue Nov 5 05:56:01 1996
.
.
.
limitation should be removed. However, this requires first to clearly
distinguish between manager and agent sessions. The -port session
option is currently completely overloaded (sometimes it defines the
destination port for a trap PDU, sometimes it defines the destination
port of SNMP requests, sometimes it defines the local port where a Tnm
agent receives requests). It is my intention to clearly distinguish
Indeed.
between SNMP manager and agent session and to add -trapaddress,
-trapport and -trapcommunity configuration options. This ensures that
these options will have well defined semantics.
Great!

However, I am not sure if this will all be implemented in the 2.2.0
release. (I can either delay the next release until this work is
finished or I can make a new release earlier and add these things as
one of the patches. Note that the second option will introduce small
incompatibilities in the Tcl API which is probably a bad thing to do
without incrementing the minor version number.)
My vote: do not delay the next release.
As much as I think developers will come
to use -trap{port,address,community} and
related enhancements, I suspect it's a
current issue for only very few of us.
You're better off making the rest of
2.2.0 available as soon as practical;
presumably its availability will also
reduce some of the maintenance and sup-
port overhead you incur now, and you'll
be able to address trap programming
with a bit more leisure.

Cameron Laird
Network Engineered Solutions http://starbase.neosoft.com/~bodi/nesi.html
claird@calladan.com +1 713 763 8366
claird@NeoSoft.com +1 713 996 8546 FAX
Houston WWW Business Guide: http://starbase.neosoft.com/~bodi/HouGuide.html
.
.
.