Indeed. It’s not like DataMiner specifically has a capability to take an SNMP trap in one version and to convert it straight into another one and send it out again, but it does provide that capability to receive SNMP traps in any version and process that into a DataMiner alarm, and that DataMiner alarm can be send out again as an SNMPv3 trap. So it that sense it receives an SNMPv1/v2 trap and sends out a corresponding SNMPv3 trap. But if the expectation would for example be that both the incoming and outgoing trap have the same set of bindings, then this would not be the case (i.e. the bindings of the incoming trap are processed by DataMiner and mapped onto a DataMiner alarm object, and that is then translated into a standard DataMiner northbound trap, which has it’s own standard set of pre-defined bindings which are linked to properties of the DataMiner alarm object).