Comment 2 for bug 1710850

I'd be fine if we implement this feature without a dedicated spec.

SNMPv3-related options would be:

* snmp_usm_user: user name (string)
* snmp_usm_auth_protocol: tokens like md5, sha
* snmp_usm_auth_key: ascii string
* snmp_usm_priv_protocol: tokens like des, aes
* snmp_usm_priv_key: ascii string
* snmp_context_name: SNMP context (string) to address possibly many instances of the same MIB behind a single SNMP agent

I do not see that any of the Ironic projects rely on PyCrypto. But there is the PyCryptodomex (notice `x` at the end) which installs under its own name (Cryptodome), not under the name of Crypto like PyCryptodome (without x) does being a drop-in replacement for PyCrypto.

Since the newer pysnmp (4.4.x) has switched to PyCryptodomex, Ironic can theoretically introduce the new PyCryptodomex dependency which could co-exist with PyCrypto/PyCryptodome [1] so that the rest of the OpenStack projects to eventually migrate to PyCryptodomex.

1. https://www.pycryptodome.org/en/latest/src/installation.html