--- 1/draft-ietf-opsawg-hmac-sha-2-usm-snmp-02.txt 2015-02-18 06:14:59.670680878 -0800 +++ 2/draft-ietf-opsawg-hmac-sha-2-usm-snmp-03.txt 2015-02-18 06:14:59.698681556 -0800 @@ -1,19 +1,19 @@ OPSAWG J. Merkle, Ed. Internet-Draft Secunet Security Networks Intended status: Standards Track M. Lochter -Expires: August 21, 2015 BSI - February 17, 2015 +Expires: August 22, 2015 BSI + February 18, 2015 HMAC-SHA-2 Authentication Protocols in USM for SNMP - draft-ietf-opsawg-hmac-sha-2-usm-snmp-02 + draft-ietf-opsawg-hmac-sha-2-usm-snmp-03 Abstract This memo specifies new HMAC-SHA-2 authentication protocols for the User-based Security Model (USM) for SNMPv3 defined in RFC 3414. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -21,21 +21,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on August 21, 2015. + This Internet-Draft will expire on August 22, 2015. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -58,27 +58,27 @@ 4.2.2. Processing an Incoming Message . . . . . . . . . . . 6 5. Key Localization and Key Change . . . . . . . . . . . . . . . 6 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 7.1. Relationship to SNMP-USER-BASED-SM-MIB . . . . . . . . . 7 7.2. Relationship to SNMP-FRAMEWORK-MIB . . . . . . . . . . . 7 7.3. MIB modules required for IMPORTS . . . . . . . . . . . . 7 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. Security Considerations . . . . . . . . . . . . . . . . . . . 9 9.1. Use of the HMAC-SHA-2 authentication protocols in USM . . 9 - 9.2. Cryptographic strength of the authentication protocols . 9 - 9.3. Derivation of keys from passwords . . . . . . . . . . . . 10 + 9.2. Cryptographic strength of the authentication protocols . 10 + 9.3. Derivation of keys from passwords . . . . . . . . . . . . 11 9.4. Access to the SNMP-USM-HMAC-SHA2-MIB . . . . . . . . . . 11 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 11.1. Normative References . . . . . . . . . . . . . . . . . . 12 - 11.2. Informative References . . . . . . . . . . . . . . . . . 12 + 11.2. Informative References . . . . . . . . . . . . . . . . . 13 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines additional authentication protocols for the User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) specified in RFC 3414 [RFC3414]. In RFC 3414, two different authentication protocols, HMAC-MD5-96 and @@ -192,22 +192,22 @@ 4.2. Processing This section describes the procedures for the HMAC-SHA-2 authentication protocols. The descriptions are based on the definition of services and data elements defined for HMAC-SHA-96 in RFC 3414 [RFC3414] with the deviations listed in Section 4.1. 4.2.1. Processing an Outgoing Message - Values of constants M (the length of the secret key) and N (the - length of the MAC output) used below, are: + Values of constants M (the length of the secret key in octets) and N + (the length of the MAC output in octets) used below, are: usmHMAC128SHA224AuthProtocol: M=28, N=16; usmHMAC192SHA256AuthProtocol: M=32, N=24; usmHMAC256SHA384AuthProtocol: M=48, N=32; usmHMAC384SHA512AuthProtocol: M=64, N=48. correspondingly. @@ -311,28 +311,30 @@ SNMP-USM-HMAC-SHA2-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, snmpModules FROM SNMPv2-SMI -- [RFC2578] snmpAuthProtocols FROM SNMP-FRAMEWORK-MIB; -- [RFC3411] snmpUsmHmacSha2MIB MODULE-IDENTITY LAST-UPDATED "201501150000Z" -- 25 January 2015, midnight ORGANIZATION "SNMPv3 Working Group" CONTACT-INFO "WG email: OPSAWG@ietf.org - Subscribe: https://www.ietf.org/mailman/listinfo/opsawg + 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" DESCRIPTION "Definitions of Object Identities needed @@ -345,65 +347,71 @@ see the RFC itself for full legal notices. Supplementary information may be available on http://www.ietf.org/copyrights/ianamib.html." -- RFC Ed.: replace TBD with actual RFC number & remove this line REVISION "201501150000Z" DESCRIPTION "Initial version, published as RFC TBD" -- RFC Ed.: replace TBD with actual RFC number & remove this line ::= { snmpModules nn } -- nn to be assigned by IANA --- RFC Ed.: replace nn with actual number assigned by IANA & remove this line +-- RFC Ed.: replace nn with actual number assigned by IANA & remove +-- this comment usmHMAC128SHA224AuthProtocol OBJECT-IDENTITY STATUS current - DESCRIPTION "The Authentication Protocol usmHMAC128SHA224AuthProtocol. - Uses HMAC-SHA-224 and truncates output to 128 bits." + DESCRIPTION "The Authentication Protocol usmHMAC128SHA224AuthProtocol + uses HMAC-SHA-224 and truncates output to 128 bits." REFERENCE "- 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." ::= { snmpAuthProtocols aa } -- aa to be assigned by IANA - -- RFC Ed.: replace aa with actual number assigned by IANA & remove this line + -- RFC Ed.: replace aa with actual number assigned by IANA & remove + -- this comment usmHMAC192SHA256AuthProtocol OBJECT-IDENTITY STATUS current - DESCRIPTION "The Authentication Protocol usmHMAC192SHA256AuthProtocol. - Uses HMAC-SHA-256 and truncates output to 192 bits." + DESCRIPTION "The Authentication Protocol usmHMAC192SHA256AuthProtocol + uses HMAC-SHA-256 and truncates output to 192 bits." REFERENCE "- 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." ::= { snmpAuthProtocols bb } -- bb to be assigned by IANA - -- RFC Ed.: replace cc with actual number assigned by IANA & remove this line + -- RFC Ed.: replace bb with actual number assigned by IANA & remove + -- this comment usmHMAC256SHA384AuthProtocol OBJECT-IDENTITY STATUS current - DESCRIPTION "The Authentication Protocol usmHMAC256SHA384AuthProtocol. - Uses HMAC-SHA-384 and truncates output to 256 bits." + DESCRIPTION "The Authentication Protocol usmHMAC256SHA384AuthProtocol + uses HMAC-SHA-384 and truncates output to 256 bits." REFERENCE "- 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." ::= { snmpAuthProtocols cc } -- cc to be assigned by IANA --- RFC Ed.: replace dd with actual number assigned by IANA & remove this line + -- RFC Ed.: replace cc with actual number assigned by IANA & remove + this comment usmHMAC384SHA12AuthProtocol OBJECT-IDENTITY STATUS current - DESCRIPTION "The Authentication Protocol usmHMAC384SHA512AuthProtocol. - Uses HMAC-SHA-512 and truncates output to 384 bits." + DESCRIPTION "The Authentication Protocol usmHMAC384SHA512AuthProtocol + uses HMAC-SHA-512 and truncates output to 384 bits." REFERENCE "- 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." ::= { snmpAuthProtocols dd } -- dd to be assigned by IANA --- RFC Ed.: replace ff with actual number assigned by IANA & remove this line + -- RFC Ed.: replace dd with actual number assigned by IANA & remove + this comment END 9. Security Considerations 9.1. Use of the HMAC-SHA-2 authentication protocols in USM The security considerations of [RFC3414] also apply to the use of all the HMAC-SHA-2 authentication protocols in USM. @@ -558,24 +566,20 @@ [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. [RFC3417] Presuhn, R., "Transport Mappings for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3417, December 2002. - [RFC4231] Nystrom, M., "Identifiers and Test Vectors for HMAC-SHA- - 224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512", RFC - 4231, December 2005. - [BCK] Bellare, M., Canetti, R., and H. Krawczyk, "Keyed Hash Functions for Message Authentication", Advances in Cryptology - CRYPTO 99, Lecture Notes in Computer Science 1109, Springer Verlag, 1996. Authors' Addresses Johannes Merkle (editor) Secunet Security Networks Mergenthaler Allee 77