From 2a6af2e8b5776318f9f8602166eb5710ec6c7f84 Mon Sep 17 00:00:00 2001 From: Richard Barnes Date: Sun, 19 Nov 2023 09:17:16 -0500 Subject: [PATCH] Remove use of 'IV' --- draft-ietf-sframe-enc.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/draft-ietf-sframe-enc.md b/draft-ietf-sframe-enc.md index d504443..b7cd8dc 100644 --- a/draft-ietf-sframe-enc.md +++ b/draft-ietf-sframe-enc.md @@ -103,9 +103,6 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", BCP 14 {{!RFC2119}} {{!RFC8174}} when, and only when, they appear in all capitals, as shown here. -IV: -: Initialization Vector - MAC: : Message Authentication Code @@ -231,7 +228,7 @@ the parties in the conference. Keys for SFrame might be distributed over an existing E2E-secure channel (see {{sender-keys}}), or derived from an E2E-secure shared secret (see {{mls}}). The key management system MUST ensure that each key used for encrypting media is used by exactly one media sender, in order to -avoid reuse of IVs. +avoid reuse of nonces. ## SFrame Ciphertext @@ -275,7 +272,7 @@ The SFrame header specifies two values from which encryption parameters are derived: * A Key ID (KID) that determines which encryption key should be used -* A counter (CTR) that is used to construct the IV for the encryption +* A counter (CTR) that is used to construct the nonce for the encryption Applications MUST ensure that each (KID, CTR) combination is used for exactly one encryption operation. A typical approach to achieving this guarantee is