SNMP-USM-HMAC-SHA2-MIB(7)

💖 NAME

SNMP-USM-HMAC-SHA2-MIB — bestie, this is section 7 of the MIB manual, and it's the MIB that lays out the Object Identities you need so SNMP's User-based Security Model can do HMAC-SHA2 auth protocols. That's the whole thing. Iconic, honestly. 🌸

---

✨ SYNOPSIS

Like, the literal module header + what it imports, no edits:

SNMP-USM-HMAC-SHA2-MIB DEFINITIONS ::= BEGIN
    IMPORTS
       MODULE-IDENTITY, OBJECT-IDENTITY,
           mib-2 FROM SNMPv2-SMI -- RFC 2578
           snmpAuthProtocols FROM SNMP-FRAMEWORK-MIB; -- RFC 3411

So MODULE-IDENTITY and OBJECT-IDENTITY come in from SNMPv2-SMI (that's RFC 2578), and snmpAuthProtocols comes in from SNMP-FRAMEWORK-MIB (RFC 3411). Slay. 💅

---

👑 DESCRIPTION — the module identity moment

The main character here is snmpUsmHmacSha2MIB, and its MODULE-IDENTITY block is giving very official-document energy:

• LAST-UPDATED — "201604180000Z" (that's 18 April 2016, midnight, for the timezone girlies 🕛)
• ORGANIZATION — "SNMPv3 Working Group"
• CONTACT-INFO — the receipts, all of them:
  • WG email: OPSAWG@ietf.org
  • Subscribe: https://www.ietf.org/mailman/listinfo/opsawg
  • Editor: Johannes Merkle, secunet Security Networks
  • Postal: Mergenthaler Allee 77, D-65760 Eschborn, Germany
  • Phone: +49 20154543091
  • Email: johannes.merkle@secunet.com
  • Co-Editor: Manfred Lochter, Bundesamt fuer Sicherheit in der Informationstechnik (BSI)
  • Postal: Postfach 200363, D-53133 Bonn, Germany
  • Phone: +49 228 9582 5643
  • Email: manfred.lochter@bsi.bund.de

And the DESCRIPTION itself, in its own words: this thing defines Object Identities needed for the use of HMAC-SHA2 Authentication Protocols by SNMP's User-based Security Model.

📜 Copyright + license (do NOT skip, this part is legally load-bearing)

Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).

Fr fr, don't skim the license. It's short, it's real, and it's the reason you're allowed to touch this at all. 💖

🕰️ REVISIONS (a glow-up timeline)

1. REVISION "201604180000Z" — 18 April 2016, midnight — "Version correcting the MODULE-IDENTITY value, published as RFC 7860"
2. REVISION "201510140000Z" — 14 October 2015, midnight — "Initial version, published as RFC 7630"

And the module sticks itself into the tree right here:

::= { mib-2 235 }

---

🎀 THE OBJECT IDENTITIES (the four auth protocol girlies)

All four of these are STATUS current, all four point at snmpAuthProtocols under a different sub-number, and all four cite the exact same two references:

• Krawczyk, H., Bellare, M., and R. Canetti, HMAC: Keyed-Hashing for Message Authentication, RFC 2104.
• National Institute of Standards and Technology, Secure Hash Standard (SHS), FIPS PUB 180-4, 2012.

🦋 usmHMAC128SHA224AuthProtocol — ::= { snmpAuthProtocols 4 }

This Authentication Protocol uses HMAC-SHA-224 and truncates output to 128 bits. Cute, small, efficient. 💅

::= { snmpAuthProtocols 4 }

🌈 usmHMAC192SHA256AuthProtocol — ::= { snmpAuthProtocols 5 }

This Authentication Protocol uses HMAC-SHA-256 and truncates output to 192 bits.

::= { snmpAuthProtocols 5 }

⭐ usmHMAC256SHA384AuthProtocol — ::= { snmpAuthProtocols 6 }

This Authentication Protocol uses HMAC-SHA-384 and truncates output to 256 bits. Ate, no crumbs.

::= { snmpAuthProtocols 6 }

💜 usmHMAC384SHA512AuthProtocol — ::= { snmpAuthProtocols 7 }

This Authentication Protocol uses HMAC-SHA-512 and truncates output to 384 bits. Big key, big vibes, still truncating because that's the assignment. 😌

::= { snmpAuthProtocols 7 }

---

🫶 SEE ALSO

Bestie, there are no SEE ALSO cross-references on this page — the pointers live inside the module as the RFC/FIPS references above (RFC 2104, FIPS PUB 180-4, 2012, RFC 2578, RFC 3411, RFC 7860, RFC 7630) and as the OID parents SNMPv2-SMI and SNMP-FRAMEWORK-MIB. That's the whole web. 🕸️

And that's a wrap on the module — it literally ends with END. Periodt.

---

✨ p.s. this whole page ships with Erlang/OTP — the SNMP part of it — so if you ever need to cite your sources in a group chat, that's who to @. 🎀 Erlang/OTP · SNMP · SNMP-USM-HMAC-SHA2-MIB(7) — mwah, talk later bestie 💖🦋🌸