[SNMP4J] Incorrectly formatted SNMPv1

[PHIL BERGSTRESSER]

It is definitely correct to toss the trap, even though you would like to
have it anyway. If you start saying that anything is acceptable in spite
of the defined protocol, then you have defined a different protocol than
than standard SNMP. That is chaos. I see it attempted when it seems like
a lot of trouble to get it corrected, but the effort is required. Than
you won't have to handle this specialized code for each deviation.

You can take this kind of tolerance to any extreme with that philosophy
and gain the wrath of all those who properly implement the standard and
have working and manageable products.

Phil B


-----Original Message-----
From: snmp4j-bounces at agentpp.org [mailto:snmp4j-bounces at agentpp.org] On
Behalf Of Bellegante John-WLJB17
Sent: Thursday, October 06, 2005 12:18 PM
To: snmp4j at agentpp.org
Subject: [SNMP4J] Incorrectly formatted SNMPv1

Hi All,
 
I am seeing an issue where I am receiving SNMPv1 traps, and they are
being tossed because the timestamp data is not type TimeTicks.  I do
agree that this is an incorrectly formatted trap, and it is not
following the protocol.
In this particular case the data is an unsigned integer and set to 0
because it is not used.  I think it would be better to NOT toss it as
long it is an UnsignedInteger32, but log an error that the type was NOT
TimeTicks.
Another option might be to throw an exception all the way back to the
application and allow the implementer to handle it however they see fit.
My goal is to still have access to the data in this trap even if it is
formatted incorrectly.  What are your thoughts/comments on this.  Do you
still think it is necessary to toss the entire trap?
 
Thanks!
_______________________________________________
SNMP4J mailing list
SNMP4J at agentpp.org
http://lists.agentpp.org/mailman/listinfo/snmp4j