Message Authentication Code
CTR OMAC GOST R 34.12-2015 "Magma"
Recommendations
Leading client applications do not use this type of message authentication code
[128][129][130][131]. Unless your application or requirements specifically call for their use, it is generally safer to avoid cipher suites that are not adopted and supported by a critical mass of the industry. If your application or requirements specifically call for the use of that encryption algorithm prefer a message authentication code
[128][129][130][131] that does provide authenticated encryption
[563] prefer cipher suites that are adopted and supported by a critical mass of the industry, like message authentication code
[128][129][130][131] Poly1305
[289][290] that proved authenticated encryption or block cipher mode of operation
[293][294][295][296][297] counter with CBC-MAC
[266][267][268] or Galois/Counter Mode
[65][66][67][68] or which also provides authenticated encryption
[563]. In case of a hashed message authentication code
[418][419][420][421][422][423][424] prefer message authentication code
[128][129][130][131] based on Secure Hash Algorithm 2
[71][72][73] over the ones based on other cryptographic hash function
[510][511][512][513].