[SNMP4J] notify method in NotificationOriginatorImpl

[Frank Fock]

Muralidharan Narayanan wrote:

>>Yes, it is a normal OID. To facilitate sending SNMPv1 traps, the OID
>>should have a zero sub-identifier as the second to last sub-ID, e.g.:
>>1.3.6.1.2.1.47.2.0.1 (enConfigChange from the ENTITY-MIB)
>>    
>>
>
>Thanks Frank for your reply.
>
>1) Is there any restriction or rules for choosing the last sub-ID. In other
>words, can last sub-ID simply start from "1"? I saw the enConfigChange
>example from the ENTITY-MIB. But since enConfigChange was the only trap I
>was not able to deduce anything about the last sub-ID.
>
>  
>
The last sub-ID can be any sub-ID, but "0" should be avoided.

>2) Will this trap/notification format hold for all SNMP versions (v1, v2c,
>v3) at this time? I see that you are working on conformance between versions
>in next release of agent.
>  
>
When the second to last sub-ID is zero, then the trap is compatible
with all versions. Other notifications cannot be sent using SNMPv1
at the moment.

Frank