Hi Pushpa
According to 
http://www.net-snmp.org/wiki/index.php/Strong_Authentication_or_Encryption
1.3.6.1.4.1.14832.1.3 is not supported since not defined by RFC if I read well, 
but some other RFC defined OID were defined in rfc7860

Which if I am not wrong are:
snmpUsmHmacSha2MIB
1.3.6.1.2.1.235
               usmHMAC128SHA224AuthProtocol
1.3.6.1.6.3.10.1.1.4
               usmHMAC192SHA256AuthProtocol
1.3.6.1.6.3.10.1.1.5
               usmHMAC256SHA384AuthProtocol
1.3.6.1.6.3.10.1.1.6
               usmHMAC384SHA512AuthProtocol
1.3.6.1.6.3.10.1.1.7

Best regards,
Laurent Menase

From: Pushpa Thimmaiah <pushpa.thimma...@gmail.com>
Sent: Tuesday, February 18, 2025 10:49 AM
To: Net-SNMP Coders <net-snmp-coders@lists.sourceforge.net>
Subject: Regarding OID of AES192

Hi All,

I would like to understand why does oid of AES128 and AES192 not in same branch.
AES128  : .1.3.6.1.6.3.10.1.2.4
AES192 : .1.3.6.1.4.1.14832.1.3

I have seen a snmpagent package using 1.3.6.1.4.1.4976.2.2.x.x.x.  as OID of 
AES192.
Does snmptrap receiver  recognise OID   1.3.6.1.4.1.4976.2.2.x.x.x. as AES192?


Thank you,
Pushpa.T

_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
  • Regar... Pushpa Thimmaiah
    • ... Menase, Laurent (TS Engineering Resolution Team) via Net-snmp-coders
    • ... Magnus Fromreide
      • ... Pushpa Thimmaiah

Reply via email to