jcs.org
jcs's openbsd hax
openbsd
1 SNMP-USM-HMAC-SHA2-MIB DEFINITIONS ::= BEGIN
2 IMPORTS
3 MODULE-IDENTITY, OBJECT-IDENTITY,
4 mib-2 FROM SNMPv2-SMI -- RFC 2578
5 snmpAuthProtocols FROM SNMP-FRAMEWORK-MIB; -- RFC 3411
6
7snmpUsmHmacSha2MIB MODULE-IDENTITY
8 LAST-UPDATED "201604180000Z" -- 18 April 2016, midnight
9 ORGANIZATION "SNMPv3 Working Group"
10 CONTACT-INFO "WG email: OPSAWG@ietf.org
11 Subscribe:
12 https://www.ietf.org/mailman/listinfo/opsawg
13 Editor: Johannes Merkle
14 secunet Security Networks
15 Postal: Mergenthaler Allee 77
16 D-65760 Eschborn
17 Germany
18 Phone: +49 20154543091
19 Email: johannes.merkle@secunet.com
20
21 Co-Editor: Manfred Lochter
22 Bundesamt fuer Sicherheit in der
23 Informationstechnik (BSI)
24 Postal: Postfach 200363
25 D-53133 Bonn
26 Germany
27 Phone: +49 228 9582 5643
28 Email: manfred.lochter@bsi.bund.de"
29 DESCRIPTION
30 "Definitions of Object Identities needed for the use of
31 HMAC-SHA2 Authentication Protocols by SNMP's User-based Security
32 Model.
33
34 Copyright (c) 2016 IETF Trust and the persons identified as
35 authors of the code. All rights reserved.
36
37 Redistribution and use in source and binary forms, with or
38 without modification, is permitted pursuant to, and subject
39 to the license terms contained in, the Simplified BSD License
40 set forth in Section 4.c of the IETF Trust's Legal Provisions
41
42 Relating to IETF Documents
43 (http://trustee.ietf.org/license-info)."
44
45 REVISION "201604180000Z" -- 18 April 2016, midnight
46 DESCRIPTION
47 "Version correcting the MODULE-IDENTITY value,
48 published as RFC 7860"
49
50 REVISION "201510140000Z" -- 14 October 2015, midnight
51 DESCRIPTION
52 "Initial version, published as RFC 7630"
53 ::= { mib-2 235 }
54
55usmHMAC128SHA224AuthProtocol OBJECT-IDENTITY
56 STATUS current
57 DESCRIPTION "The Authentication Protocol
58 usmHMAC128SHA224AuthProtocol uses HMAC-SHA-224 and
59 truncates output to 128 bits."
60 REFERENCE "- Krawczyk, H., Bellare, M., and R. Canetti,
61 HMAC: Keyed-Hashing for Message Authentication,
62 RFC 2104.
63 - National Institute of Standards and Technology,
64 Secure Hash Standard (SHS), FIPS PUB 180-4, 2012."
65 ::= { snmpAuthProtocols 4 }
66
67usmHMAC192SHA256AuthProtocol OBJECT-IDENTITY
68 STATUS current
69 DESCRIPTION "The Authentication Protocol
70 usmHMAC192SHA256AuthProtocol uses HMAC-SHA-256 and
71 truncates output to 192 bits."
72 REFERENCE "- Krawczyk, H., Bellare, M., and R. Canetti,
73 HMAC: Keyed-Hashing for Message Authentication,
74 RFC 2104.
75 - National Institute of Standards and Technology,
76 Secure Hash Standard (SHS), FIPS PUB 180-4, 2012."
77 ::= { snmpAuthProtocols 5 }
78
79usmHMAC256SHA384AuthProtocol OBJECT-IDENTITY
80 STATUS current
81 DESCRIPTION "The Authentication Protocol
82 usmHMAC256SHA384AuthProtocol uses HMAC-SHA-384 and
83 truncates output to 256 bits."
84 REFERENCE "- Krawczyk, H., Bellare, M., and R. Canetti,
85 HMAC: Keyed-Hashing for Message Authentication,
86 RFC 2104.
87 - National Institute of Standards and Technology,
88 Secure Hash Standard (SHS), FIPS PUB 180-4, 2012."
89 ::= { snmpAuthProtocols 6 }
90
91usmHMAC384SHA512AuthProtocol OBJECT-IDENTITY
92 STATUS current
93 DESCRIPTION "The Authentication Protocol
94 usmHMAC384SHA512AuthProtocol uses HMAC-SHA-512 and
95 truncates output to 384 bits."
96 REFERENCE "- Krawczyk, H., Bellare, M., and R. Canetti,
97 HMAC: Keyed-Hashing for Message Authentication,
98 RFC 2104.
99 - National Institute of Standards and Technology,
100 Secure Hash Standard (SHS), FIPS PUB 180-4, 2012."
101 ::= { snmpAuthProtocols 7 }
102
103END