]> Amazon Web Services

Canada campagna@amazon.com

Ericsson

Sweden alexander.maximov@ericsson.com

Ericsson

Sweden john.mattsson@ericsson.com

IRTF Crypto Forum next generation unicorn sparkling distributed ledger This document defines the Galois Counter Mode with Secure Short Tags (GCM-SST) Authenticated Encryption with Associated Data (AEAD) algorithm. GCM-SST can be used with any keystream generator, not just 128-bit block ciphers. The main differences from GCM are the use of an additional subkey Q, the derivation of fresh subkeys H and Q for each nonce, and the replacement of the GHASH function with the POLYVAL function from AES-GCM-SIV. This enables truncated tags with near-ideal forgery probabilities and significantly decreases the probability of multiple forgeries. GCM-SST is designed for unicast security protocols with replay protection and addresses the strong industry demand for fast encryption with secure short tags. This document registers several instances of GCM-SST using Advanced Encryption Standard (AES) and Rijndael-256-256. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Crypto Forum Research Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction Advanced Encryption Standard (AES) in Galois Counter Mode (AES-GCM) is a widely used AEAD algorithm due to its attractive performance in both software and hardware as well as its provable security. During the NIST standardization, Ferguson pointed out two weaknesses in the GCM authentication function , particularly problematic when short tags are used. The first weakness significantly increases the probability of successful forgery. The second weakness reveals the subkey H if an attacker succeeds in creating forgeries. Once H is known, the attacker can consistently forge subsequent messages, drastically increasing the probability of multiple successful forgeries. In a comment to NIST, Nyberg et al. explained how small changes based on proven theoretical constructions mitigate these weaknesses. Unfortunately, NIST did not follow the advice from Nyberg et al. and instead specified additional requirements for use with short tags in Appendix C of . NIST did not give any motivations for the parameter choices or the assumed security levels. Mattsson et al. later demonstrated that attackers can almost always obtain feedback on the success or failure of forgery attempts, contradicting the assumptions NIST made for short tags. Furthermore, NIST appears to have relied on non-optimal attacks when calculating the parameters. Rogaway criticizes the use of GCM with short tags and recommends prohibiting tags shorter than 96 bits. Reflecting the critique, NIST is planning to remove support for GCM with tags shorter than 96 bits . While Counter with CBC-MAC (CCM) with short tags has forgery probabilities close to ideal, its performance is lower than that of GCM. Short tags are widely used, 32-bit tags are standard in most radio link layers including 5G , 64-bit tags are very common in transport and application layers of the Internet of Things, and 32-, 64-, and 80-bit tags are common in media-encryption applications. Audio packets are small, numerous, and ephemeral. As such, they are highly sensitive to cryptographic overhead, but forgery of individual packets is not a big concern as it typically is barely noticeable as each packet often only encodea 20 ms of audio. Due to its weaknesses, GCM is typically not used with short tags. The result is either decreased performance from larger than needed tags , or decreased performance from using much slower constructions such as AES-CTR combined with HMAC . Short tags are also useful to protect packets whose payloads are secured at higher layers, protocols where the security is given by the sum of the tag lengths, and in constrained radio networks, where the low bandwidth preclude many repeated trial. For all applications of short tags it is essential that the MAC behaves like an ideal MAC, i.e., the forgery probability is ≈ 2^-tag_length even after many generated MACs, many forgery attempts, and after a successful forgery. For a comprehensive discussion on the use cases and requirements of short tags, see . This document defines the Galois Counter Mode with Secure Short Tags (GCM-SST) Authenticated Encryption with Associated Data (AEAD) algorithm following the recommendations from Nyberg et al. . GCM-SST is defined with a general interface, allowing it to be used with any keystream generator, not just 128-bit block ciphers. The main differences from GCM are the introduction of an additional subkey Q, the derivation of fresh subkeys H and Q for each nonce, and the replacement of the GHASH function with the POLYVAL function from AES-GCM-SIV , see . These changes enable truncated tags with forgery probability close to ideal and significantly decreases the probability of multiple successful forgeries, see . GCM-SST is designed for use in unicast security protocols with replay protection. Its performance is similar to GCM , with the two additional AES invocations compensated by the use of POLYVAL, the ”little-endian version” of GHASH, which is faster on little-endian architectures. GCM-SST retains the additive encryption characteristic of GCM, which enables efficient implementations on modern processor architectures, see and Section 2.4 of . This document registers several GCM-SST instances using Advanced Encryption Standard (AES) and Rijndael with 256-bit keys and blocks (Rijndael-256-256) in counter mode as keystream generators, see . 3GPP has standardized the use of Rijndael-256-256 for authentication and key generation in 3GPP TS 35.234–35.237 . NIST is anticipated to standardize Rijndael-256-256 , although there may be revisions to the key schedule. GCM-SST was originally developed by ETSI SAGE, under the name Mac5G, following a request from 3GPP, with several years of discussion and refinement contributing to its design . 3GPP has decided to standardize GCM-SST for use with AES-256 , SNOW 5G , and ZUC-256 in 3GPP TS 35.240–35.248 .

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The following notation is used in the document:

• K is the key as defined in
• N is the nonce as defined in
• A is the associated data as defined in
• P is the plaintext as defined in
• Z is the keystream
• ct is the ciphertext
• tag is the authentication tag
• = is the assignment operator
• != is the inequality operator
• x || y is concatenation of the octet strings x and y
• XOR is the bitwise exclusive OR operator
• len(x) is the length of x in bits.
• zeropad(x) right pads an octet string x with zeroes to a multiple of 128 bits
• truncate(x, t) is the truncation operation. The first t bits of x are kept
• n is the number of 128-bit chunks in zeropad(P)
• m is the number of 128-bit chunks in zeropad(A)
• POLYVAL is defined in
• BE32(x) is the big-endian encoding of 32-bit integer x
• LE64(x) is the little-endian encoding of 64-bit integer x
• V[y] is the 128-bit chunk with index y in the array V; the first chunk has index 0.
• V[x:y] are the range of chunks x to y in the array V

Galois Counter Mode with Secure Short Tags (GCM-SST) This section defines the Galois Counter Mode with Secure Short Tags (GCM-SST) AEAD algorithm following the recommendations from Nyberg et al. . GCM-SST is defined with a general interface so that it can be used with any keystream generator, not just a 128-bit block cipher. GCM-SST adheres to an AEAD interface and the encryption function takes four variable-length octet string parameters. A secret key K, a nonce N, the associated data A, and a plaintext P. The keystream generator is instantiated with K and N. The keystream MAY depend on P and A. The minimum and maximum lengths of all parameters depend on the keystream generator. The keystream generator produces a keystream Z consisting of 128-bit chunks where the first three chunks Z[0], Z[1], and Z[2] are used as the three subkeys H, Q, and M. The following keystream chunks Z[3], Z[4], ..., Z[n + 2] are used to encrypt the plaintext. Instead of GHASH , GCM-SST makes use of the POLYVAL function from AES-GCM-SIV , which results in more efficient software implementations on little-endian architectures. GHASH and POLYVAL can be defined in terms of one another . The subkeys H and Q are field elements used in POLYVAL while the subkey M is used for the final masking of the tag. Both encryption and decryption are only defined on inputs that are a whole number of octets. Figures illustrating the GCM-SST encryption and decryption functions are shown in .

Authenticated Encryption Function The encryption function Encrypt(K, N, A, P) encrypts a plaintext and returns the ciphertext along with an authentication tag that verifies the authenticity of the plaintext and associated data, if provided. Prerequisites and security:

• The key MUST be randomly chosen from a uniform distribution.
• For a given key, a nonce MUST NOT be reused under any circumstances.
• Each key MUST be restricted to a single tag_length.
• Definitions of supported input-output lengths.

Inputs:

• Key K (variable-length octet string)
• Nonce N (variable-length octet string)
• Associated data A (variable-length octet string)
• Plaintext P (variable-length octet string)

Outputs:

• Ciphertext ct (variable-length octet string)
• Tag tag (octet string with length tag_length)

Steps:

1. If the lengths of K, N, A, P are not supported return error and abort
2. Initiate keystream generator with K and N
3. Let H = Z[0], Q = Z[1], M = Z[2]
4. Let ct = P XOR truncate(Z[3:n + 2], len(P))
5. Let S = zeropad(A) || zeropad(ct)
6. Let L = LE64(len(ct)) || LE64(len(A))
7. Let X = POLYVAL(H, S[0], S[1], ...)
8. Let full_tag = POLYVAL(Q, X XOR L) XOR M
9. Let tag = truncate(full_tag, tag_length)
10. Return (ct, tag)

Authenticated Decryption Function The decryption function Decrypt(K, N, A, ct, tag) decrypts a ciphertext, verifies that the authentication tag is correct, and returns the plaintext on success or an error if the tag verification failed. Prerequisites and security:

• The calculation of the plaintext P (step 10) MAY be done in parallel with the tag verification (step 3-9). If the tag verification fails, the plaintext P and the expected_tag MUST NOT be given as output.
• For a given key, a nonce for which a plaintext has been returned MUST NOT be reused under any circumstances.
• Each key MUST be restricted to a single tag_length.
• Definitions of supported input-output lengths.

Inputs:

• Key K (variable-length octet string)
• Nonce N (variable-length octet string)
• Associated data A (variable-length octet string)
• Ciphertext ct (variable-length octet string)
• Tag tag (octet string with length tag_length)

Outputs:

• Plaintext P (variable-length octet string) or an error indicating that the authentication tag is invalid for the given inputs.

Steps:

1. If the lengths of K, N, A, or ct are not supported, or if len(tag) != tag_length return error and abort
2. Initiate keystream generator with K and N
3. Let H = Z[0], Q = Z[1], M = Z[2]
4. Let S = zeropad(A) || zeropad(ct)
5. Let L = LE64(len(ct)) || LE64(len(A))
6. Let X = POLYVAL(H, S[0], S[1], ...)
7. Let full_tag = POLYVAL(Q, X XOR L) XOR M
8. Let expected_tag = truncate(full_tag, tag_length)
9. If tag != expected_tag, return error and abort
10. Let P = ct XOR truncate(Z[3:n + 2], len(ct))
11. Return P

The comparison of tag and expected_tag in step 9 MUST be performed in constant time to prevent any information leakage about the position of the first mismatched byte.

Encoding (ct, tag) Tuples Applications MAY keep the ciphertext and the authentication tag in distinct structures or encode both as a single octet string C. In the latter case, the tag MUST immediately follow the ciphertext ct: C = ct || tag

AES and Rijndael-256-256 in GCM-SST This section defines Advanced Encryption Standard (AES) and Rijndael with 256-bit keys and blocks (Rijndael-256-256) in Galois Counter Mode with Secure Short Tags.

AES-GCM-SST When GCM-SSM is instantiated with AES (AES-GCM-SST), the keystream generator is AES in counter mode Z[i] = ENC(K, N || BE32(i)) where ENC is the AES Cipher function .

Rijndael-GCM-SST When GCM-SST is instantiated with Rijndael-256-256 (Rijndael-GCM-SST), the keystream generator is Rijndael-256-256 in counter mode Z[2i] = ENC(K, N || BE32(i))[0] Z[2i+1] = ENC(K, N || BE32(i))[1] where ENC is the Rijndael-256-256 Cipher function .

AEAD Instances and Constraints We define nine AEAD instances, in the format of , that use AES-GCM-SST and Rijndael-GCM-SST. The tag lengths 32, 64, and 80 have been chosen to align with secure media frames . The key length and tag length are related to different security properties, and an application encrypting audio packets with small tags might require 256-bit confidentiality. AEAD Algorithms

Numeric ID	Name	K_LEN (bytes)	tag_length (bits)
TBD1	AEAD_AES_128_GCM_SST_4	16	32
TBD2	AEAD_AES_128_GCM_SST_8	16	64
TBD3	AEAD_AES_128_GCM_SST_10	16	80
TBD4	AEAD_AES_256_GCM_SST_4	32	32
TBD5	AEAD_AES_256_GCM_SST_8	32	64
TBD6	AEAD_AES_256_GCM_SST_10	32	80
TBD7	AEAD_RIJNDAEL_GCM_SST_4	32	32
TBD8	AEAD_RIJNDAEL_GCM_SST_8	32	64
TBD9	AEAD_RIJNDAEL_GCM_SST_10	32	80

Common parameters for the six AEAD instances:

• P_MAX (maximum size of the plaintext) is 2³⁶ - 48 octets.
• A_MAX (maximum size of the associated data) is 2³⁶ octets.
• N_MIN = N_MAX (minimum and maximum size of the nonce) is 12 octets for AES, while for Rijndael-256-256, it is 28 bytes.
• C_MAX (maximum size of the ciphertext and tag) is P_MAX + tag_length (in bytes)

The maximum size of the plaintext (P_MAX) has been adjusted from GCM as there is now three subkeys instead of two. The maximum size of the associated data (A_MAX) has been lowered from GCM to enable forgery probability close to ideal for larger tags even with maximum size plaintexts and associated data. Just like , AES-GCM-SST and Rijndael-GCM-SST only allow a fixed nonce length (N_MIN = N_MAX) of 96-bit and 224-bits respectively. For the AEAD algorithms in the worst-case forgery probability is bounded by ≈ 2^-tag_length . This is true for all allowed plaintext and associated data lengths.

Security Considerations GCM-SST introduces an additional subkey Q, alongside the subkey H. The inclusion of Q enables truncated tags with forgery probabilities close to ideal. Both Q and H are derived for each nonce, which significantly decreases the probability of multiple successful forgeries. These changes are based on proven theoretical constructions and follows the recommendations in . Inoue et al. prove that eGCM-SST is a provably secure authenticated encryption mode, with security guaranteed for evaluations under fresh nonces, even if some earlier nonces have been reused. GCM-SST MUST be used in a nonce-respecting setting: for a given key, a nonce MUST only be used once in the encryption function and the decryption function. The nonce MAY be public or predictable. It can be a counter, the output of a permutation, or a generator with a long period. Every key MUST be randomly chosen from a uniform distribution. GCM-SST MUST NOT be used with random nonces and MUST be used with replay protection. GCM-SST MUST NOT be used in multicast or broadcast. Reuse of nonces in the encryption function and the decryption function enable universal forgery . GCM-SST is designed for use in unicast security protocols with replay protection. Implementations MAY add randomness to the nonce by XORing a unique number like a sequence number with a per-key random secret salt. This improves security against pre-computation attacks and multi-key attacks . By increasing the nonce length from 96 bits to 224 bits, Rijndael-256-256-GCM-SST can offer significantly greater security against pre-computation and multi-key attacks compared to AES-256-GCM-SST. The GCM-SST tag_length SHOULD NOT be smaller than 4 bytes and cannot be larger than 16 bytes. For short tags with tag_length < 128 - log2(n + m + 1) bits, the worst-case forgery probability is bounded by ≈ 2^-tag_length . With the constraints listed in , n + m + 1 < 2³³ 128-bit blocks, and tags of length up to 95 bits therefore have an almost perfect security level. This is significantly better than GCM where the security level is only tag_length - log2(n + m + 1) bits . For a graph of the forgery probability, refer to Fig. 3 in . As one can note, for 128-bit tags and long messages, the forgery probability is not close to ideal and similar to GCM . If tag verification fails, the plaintext and expected_tag MUST NOT be given as output. In GCM-SST, the full_tag is independent of the specified tag length unless the application explicitly incorporates tag length into the keystream or the nonce. The confidentiality offered by AES-GCM-SST against passive attackers is equal to AES-GCM and given by the birthday bound. Regardless of key length, an attacker can mount a distinguishing attack with a complexity of approximately 2¹²⁹ / k, where k is the number of invocations of the AES encryption function. In contrast, the confidentiality offered by Rijndael-256-256-GCM-SST against passive attackers is significantly higher. The complexity of distinguishing attacks for Rijndael-256-256-GCM-SST is approximately 2²⁵⁷ / k, where k is the number of invocations of the Rijndael-256-256 encryption function. While Rijndael-256-256 in counter mode can provide strong confidentiality for plaintexts much larger than 2³⁶ octets, GHASH and POLYVAL do not offer adequate integrity for long plaintexts. To ensure robust integrity for long plaintexts, an AEAD mode would need to replace POLYVAL with a MAC that has better security properties, such as a Carter-Wegman MAC in a larger field or other alternatives such as . The confidentiality offered by AES-GCM-SST against active attackers is irectly linked to the forgery probability. Depending on the protocol and application, forgeries MAY significantly compromise privacy, in addition to affecting integrity and authenticity. It MUST be assumed that attackers always receive feedback on the success or failure of their forgery attempts. Therefore, attacks on integrity, authenticity, and confidentiality MUST all be carefully evaluated when selecting an appropriate tag length. In general, there is a very small possibility in GCM-SST that either or both of the subkeys H and Q are zero, so called weak keys. If H is zero, the authentication tag depends only on the length of P and A and not on their content. If Q is zero, the authentication tag does not depends on the field L encoding the length of P and A. There are no obvious ways to detect this condition for an attacker, and the specification admits this possibility in favor of complicating the flow with additional checks and regeneration of values. In AES-GCM-SST, H and Q are generated with a permutation on different input, so H and Q cannot both be zero.

IANA Considerations IANA is requested to assign the entries in the first two columns of to the "AEAD Algorithms" registry under the "Authenticated Encryption with Associated Data (AEAD) Parameters" heading with this document as reference.

References Normative References This document defines algorithms for Authenticated Encryption with Associated Data (AEAD), and defines a uniform interface and a registry for such algorithms. The interface and registry can be used as an application-independent set of cryptoalgorithm suites. This approach provides advantages in efficiency and security, and promotes the reuse of crypto implementations. [STANDARDS-TRACK] This memo specifies two authenticated encryption algorithms that are nonce misuse resistant -- that is, they do not fail catastrophically if a nonce is repeated. This document is the product of the Crypto Forum Research Group. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP). [STANDARDS-TRACK] This document describes the Secure Frame (SFrame) end-to-end encryption and authentication mechanism for media frames in a multiparty conference call, in which central media servers (Selective Forwarding Units or SFUs) can access the media metadata needed to make forwarding decisions without having access to the actual media. This mechanism differs from the Secure Real-Time Protocol (SRTP) in that it is independent of RTP (thus compatible with non-RTP media transport) and can be applied to whole media frames in order to be more bandwidth efficient. Fastly Inc. Individual Contributor This document describes the AEGIS-128L, AEGIS-256, AEGIS-128X, and AEGIS-256X AES-based authenticated encryption algorithms designed for high-performance applications. The document is a product of the Crypto Forum Research Group (CFRG). It is not an IETF product and is not a standard. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/cfrg/draft-irtf-cfrg-aegis-aead.

AES-GCM-SST Test Vectors

AES-GCM-SST Test #1 (128-bit key)

Case #1a

Case #1b

Case #1c

Case #1d

Case #1e

AES-GCM-SST Test #2 (128-bit key)

AES-GCM-SST Test #3 (256-bit key)

Case #3a

Case #3b

Case #3c

Case #3d

Case #3e

AES-GCM-SST Test #4 (256-bit key)

Change Log Changes from -03 to -04:

• Reference to Inoue et al. for security proof, forgery probability graph, and improved attack when GCM-SST is used without replay protection.
• Editorial changes.

Changes from -03 to -04:

• Added that GCM-SST is designed for unicast protocol with replay protection
• Update info on use cases for short tags
• Updated info on ETSI and 3GPP standardization of GCM-SST
• Added Rijndael-256-256
• Added that replay is required and that random nonces, multicast, and broadcast are forbidden based on attack from Yehuda Lindell
• Security considerations for active attacks on privacy as suggested by Thomas Bellebaum
• Improved text on H and Q being zero.
• Editorial changes.

Changes from -02 to -03:

• Added performance information and considerations.
• Editorial changes.

Changes from -01 to -02:

• The length encoding chunk is now called L
• Use of the notation POLYVAL(H, X_1, X_2, ...) from RFC 8452
• Removed duplicated text in security considerations.

Changes from -00 to -01:

• Link to NIST decision to remove support for GCM with tags shorter than 96-bits based on Mattsson et al.
• Mention that 3GPP 5G Advance will use GCM-SST with AES-256 and SNOW 5G.
• Corrected reference to step numbers during decryption
• Changed T to full_tag to align with tag and expected_tag
• Link to images from the NIST encryption workshop illustrating the GCM-SST encryption and decryption functions.
• Updated definitions
• Editorial changes.

Acknowledgments The authors thank , , , , , and for their valuable comments and feedback. Some of the formatting and text were inspired by and borrowed from .