RFC 4130, "MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)", July 2005Source of RFC: ediint (app)
Errata ID: 2973
Publication Format(s) : TEXT
Reported By: Kyle Meadors
Date Reported: 2011-09-16
Rejected by: Pete Resnick
Date Rejected: 2011-11-12
Section 7.3 says:
The currently supported values for MIC algorithm <micalg> values are: Algorithm Value Used --------- ------- SHA-1 sha1 MD5 md5
It should say:
The currently supported values for MIC algorithm <micalg> values are: Algorithm Value Used --------- ------- SHA-1 sha-1 or sha1 MD5 md5 SHA-224 sha-224 SHA-256 sha-256 SHA-384 sha-384 SHA-512 sha-512
The proper spelling is "sha-1" per http://www.iana.org/assignments/hash-function-text-names/hash-function-text. However, "sha1" should still be accepted to support backwards compatibility. The other hashes are newer ones since the RFC was published.
A separate erratum was issued with the SHA1/SHA-1 fix. The additional algorithms cannot be added in an erratum.