IEEE P802.11 Wireless LANs A Convention for naming the SHA family of Hash Functions Date: 2014-10-29 Author(s): Name Affiliation Address Phone email 1322 Crossman ave, Sunnyvale, dharkins at aruba Dan Harkins Networks CA 94089 +1 408 227 4500 networks dot com United States of America CID Comment Proposed Change Resolution 3426 "HMAC-SHA-256" (6 instances) "HMAC-SHA256" Reject: yes, 256 is the is confusing as 256 is not the output length. And there is output length no confusion as the convention is: [HMAC-]SHA-<name>[-n] 3247 "HMAC-SHA1-128" "Truncate128(HMAC Revised: incorporate the text SHA1-160" for changes in 11-14/1357r1 consistency with other PMKIDs. Also at 1935.35 3429 Is it SHA256 or is it Pick one (or two, if the Revised: incorporate the text answers for the hash changes in 11-14/1357r1 Ditto name on its own and when combined to form a HMAC (e.g. HMAC- are different, to avoid confusion between the hash name and the output length)
IEEE P802.11 Wireless LANs A Convention for naming the SHA family of Hash Functions Date: 2014-10-29 Author(s): Name Affiliation Address Phone email Dan Harkins Networks 1322 Crossman ave, Sunnyvale, CA 94089 United States of America +1 408 227 4500 dharkins at aruba networks dot com CID Comment Proposed Change Resolution 3426 "HMAC-SHA-256" (6 instances) is confusing as 256 is not the output length "HMAC-SHA256" Reject: yes, 256 is the output length. And there is no confusion as the convention is: [HMAC-]SHA-<name>[-n] 3247 "HMAC-SHA1-128" "Truncate128(HMAC SHA1-160" for consistency with other PMKIDs. Also at 1935.35 Revised: incorporate the text changes in 11-14/1357r1 3429 Is it SHA256 or is it Ditto Pick one (or two, if the answers for the hash name on its own and when combined to form a HMAC (e.g. are different, to avoid confusion between the hash name and the output length) Revised: incorporate the text changes in 11-14/1357r1 HMAC-
11-14-1357-01-000m-convention-for-naming-sha-hashes.docx