{"service":"corpus","corpus":"rfc","source":"RFC Editor","license":"IETF Trust / RFC Editor terms","record":{"id":"10079","title":"Updates to the SFrame Cipher Suites Registry","text":"﻿\n\n\n\nInternet Engineering Task Force (IETF)                         R. Barnes\nRequest for Comments: 10079                                        Cisco\nUpdates: 9605                                                   E. Omara\nCategory: Standards Track                                   A. Rosenberg\nISSN: 2070-1721                                                    Apple\n                                                           November 2026\n\n\n              Updates to the SFrame Cipher Suites Registry\n\nAbstract\n\n   This document addresses two omissions in the Secure Frame (SFrame)\n   protocol specification.  First, the definition of the IANA \"SFrame\n   Cipher Suites\" registry in RFC 9605 omits several important fields.\n   This document updates the IANA registry by adding those fields and\n   defining the contents of those fields for current entries.  Second,\n   the Authenticated Encryption with Associated Data (AEAD) construction\n   based on AES-CTR and HMAC is defined only for the 128-bit security\n   level.  This document registers parallel constructions at the 256-bit\n   security level.\n\nStatus of This Memo\n\n   This is an Internet Standards Track document.\n\n   This document is a product of the Internet Engineering Task Force\n   (IETF).  It represents the consensus of the IETF community.  It has\n   received public review and has been approved for publication by the\n   Internet Engineering Steering Group (IESG).  Further information on\n   Internet Standards is available in Section 2 of RFC 7841.\n\n   Information about the current status of this document, any errata,\n   and how to provide feedback on it may be obtained at\n   https://www.rfc-editor.org/info/rfc10079.\n\nCopyright Notice\n\n   Copyright (c) 2026 IETF Trust and the persons identified as the\n   document authors.  All rights reserved.\n\n   This document is subject to BCP 78 and the IETF Trust's Legal\n   Provisions Relating to IETF Documents\n   (https://trustee.ietf.org/license-info) in effect on the date of\n   publication of this document.  Please review these documents\n   carefully, as they describe your rights and restrictions with respect\n   to this document.  Code Components extracted from this document must\n   include Revised BSD License text as described in Section 4.e of the\n   Trust Legal Provisions and are provided without warranty as described\n   in the Revised BSD License.\n\nTable of Contents\n\n   1.  Introduction\n   2.  AES-256-CTR with HMAC-SHA512\n   3.  Security Considerations\n   4.  IANA Considerations\n     4.1.  Updates to the SFrame Cipher Suites Registry\n     4.2.  Cipher Suites for AES-256-CTR with HMAC-SHA512\n   5.  References\n     5.1.  Normative References\n     5.2.  Informative References\n   Appendix A.  Test Vectors\n     A.1.  AEAD Encryption/Decryption Using AES-CTR and HMAC\n     A.2.  SFrame Encryption/Decryption\n   Authors' Addresses\n\n1.  Introduction\n\n   This document addresses two omissions in the Secure Frame (SFrame)\n   protocol specification [RFC9605].  First, in Section 8.1 of\n   [RFC9605], the definition of the IANA \"SFrame Cipher Suites\" registry\n   omits several important fields.  This document defines the required\n   fields and the contents of those fields for current entries.  IANA\n   has updated the registry accordingly.  Second, the AEAD construction\n   based on AES-CTR and HMAC (in Section 4.5.1 of [RFC9605]) is defined\n   only for the 128-bit security level.  This document registers\n   parallel constructions at the 256-bit security level.\n\n2.  AES-256-CTR with HMAC-SHA512\n\n   Section 4.5.1 of [RFC9605] defines a compound authenticated\n   encryption construction, using the unauthenticated Counter (CTR) mode\n   of AES for encryption and HMAC for authentication.\n\n   The original specification only defines cipher suite values for\n   instances of this construction using AES-128-CTR and HMAC-SHA256.\n   The construction works the same way when used with AES-256-CTR and\n   HMAC-SHA512.  The only differences are in the lengths of some SFrame\n   intermediate values:\n\n   *  The keys generated by SFrame key derivation (derive_key_salt) are\n      longer to match the needs of AES-256-CTR and HMAC-SHA512 (96 bytes\n      vs. 48 bytes for AES-128-CTR and HMAC-SHA256).\n\n   *  The initial tag value tag in compute_tag is 64 bytes instead of 32\n      bytes.\n\n   Identifiers for cipher suites using AES-256-CTR and HMAC-SHA512 are\n   defined in Section 4.2.\n\n3.  Security Considerations\n\n   The registry changes in this document have no effect on the security\n   of SFrame.\n\n   The new algorithms registered by this document allow the construction\n   combining AES-CTR with HMAC to be used in environments that require a\n   256-bit security level.\n\n4.  IANA Considerations\n\n   Per this document, IANA has updated the columns in the \"SFrame Cipher\n   Suites\" registry (see Section 4.1), added entries to the updated\n   registry for the new cipher suites defined in this document (see\n   Section 4.2), and added this document as an additional reference for\n   this registry.\n\n4.1.  Updates to the SFrame Cipher Suites Registry\n\n   IANA has added the following columns to the \"SFrame Cipher Suites\"\n   registry.  This document also updates the registration template in\n   Section 8.1 of [RFC9605] to include these fields, which are placed\n   between the \"Name\" and \"Recommended\" fields.\n\n   *  Nh: The size in bytes of the output of the hash function.\n\n   *  Nka: For cipher suites using the compound AEAD described in\n      Section 4.5.1 of [RFC9605], the size in bytes of a key for the\n      underlying encryption algorithm; for other cipher suites, the\n      value is \"n/a\".\n\n   *  Nk: The size in bytes of a key for the encryption algorithm.\n\n   *  Nn: The size in bytes of a nonce for the encryption algorithm.\n\n   *  Nt: The overhead in bytes of the encryption algorithm (typically\n      the size of a \"tag\" that is added to the plaintext).\n\n   The registration procedures in Section 8.1 of [RFC9605] are otherwise\n   unchanged.\n\n   Table 1 illustrates the new structure of the registry and provides\n   the required values for the previously registered entries.\n\n   +======+==========================+==+===+==+==+==+=+=========+=====+\n   |Value |Name                      |Nh|Nka|Nk|Nn|Nt|R|Reference|Ch   |\n   |      |                          |  |   |  |  |  | |         |Contr|\n   +======+==========================+==+===+==+==+==+=+=========+=====+\n   |0x0000|Reserved                  |- |-  |- |- |- |-|RFC 9605 |IETF |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0001|AES_128_CTR_HMAC_SHA256_80|32|16 |48|12|10|Y|RFC 9605,|IETF |\n   |      |                          |  |   |  |  |  | |RFC 10079|     |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0002|AES_128_CTR_HMAC_SHA256_64|32|16 |48|12|8 |Y|RFC 9605,|IETF |\n   |      |                          |  |   |  |  |  | |RFC 10079|     |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0003|AES_128_CTR_HMAC_SHA256_32|32|16 |48|12|4 |Y|RFC 9605,|IETF |\n   |      |                          |  |   |  |  |  | |RFC 10079|     |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0004|AES_128_GCM_SHA256_128    |32|n/a|16|12|16|Y|RFC 9605,|IETF |\n   |      |                          |  |   |  |  |  | |RFC 10079|     |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0005|AES_256_GCM_SHA512_128    |64|n/a|32|12|16|Y|RFC 9605,|IETF |\n   |      |                          |  |   |  |  |  | |RFC 10079|     |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0xF000|Reserved for Private Use  |- |-  |- |- |- |-|RFC 9605 |IETF |\n   |-     |                          |  |   |  |  |  | |         |     |\n   |0xFFFF|                          |  |   |  |  |  | |         |     |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n\n      Table 1: New Structure and Contents of the SFrame Cipher Suites\n                                  Registry\n\n4.2.  Cipher Suites for AES-256-CTR with HMAC-SHA512\n\n   IANA has added the following new entries to the \"SFrame Cipher\n   Suites\" registry:\n\n   +======+==========================+==+===+==+==+==+=+=========+=====+\n   |Value |Name                      |Nh|Nka|Nk|Nn|Nt|R|Reference|Ch   |\n   |      |                          |  |   |  |  |  | |         |Contr|\n   +======+==========================+==+===+==+==+==+=+=========+=====+\n   |0x0006|AES_256_CTR_HMAC_SHA512_80|64|32 |96|12|10|Y|RFC 10079|IETF |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0007|AES_256_CTR_HMAC_SHA512_64|64|32 |96|12|8 |Y|RFC 10079|IETF |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n   |0x0008|AES_256_CTR_HMAC_SHA512_32|64|32 |96|12|4 |Y|RFC 10079|IETF |\n   +------+--------------------------+--+---+--+--+--+-+---------+-----+\n\n         Table 2: New Entries in the SFrame Cipher Suites Registry\n\n5.  References\n\n5.1.  Normative References\n\n   [RFC9605]  Omara, E., Uberti, J., Murillo, S. G., Barnes, R., Ed.,\n              and Y. Fablet, \"Secure Frame (SFrame): Lightweight\n              Authenticated Encryption for Real-Time Media\", RFC 9605,\n              DOI 10.17487/RFC9605, August 2024,\n              <https://www.rfc-editor.org/info/rfc9605>.\n\n5.2.  Informative References\n\n   [TestVectors]\n              \"test-vectors-aes256.json\", commit 78680b9, 18 September\n              2025, <https://github.com/bifurcation/sframe-iana-\n              256/blob/main/test-vectors/test-vectors-aes256.json>.\n\nAppendix A.  Test Vectors\n\n   This appendix provides a set of test vectors that implementations can\n   use to verify that they correctly implement SFrame encryption and\n   decryption with the cipher suites registered in this document.  Test\n   vectors are provided for both the AES-256-CTR-HMAC construction and\n   full SFrame encryption with the new cipher suites.\n\n   All values are either numeric or byte strings.  Numeric values are\n   represented as hex values, prefixed with 0x.  Byte strings are\n   represented in hex encoding.\n\n   Line breaks and whitespace within values are inserted to conform to\n   the width requirements of the RFC format.  They should be removed\n   before use.\n\n   These test vectors are also available in JSON format at\n   [TestVectors].  In the JSON test vectors, numeric values are JSON\n   numbers and byte string values are JSON strings containing the hex\n   encoding of the byte strings.\n\nA.1.  AEAD Encryption/Decryption Using AES-CTR and HMAC\n\n   For each case, we provide:\n\n   *  cipher_suite: The index of the cipher suite in use (see\n      Section 4.1)\n\n   *  key: The key input to encryption/decryption\n\n   *  enc_key: The encryption subkey produced by the derive_subkeys()\n      algorithm\n\n   *  auth_key: The authentication subkey produced by the\n      derive_subkeys() algorithm\n\n   *  nonce: The nonce input to encryption/decryption\n\n   *  aad: The aad input to encryption/decryption\n\n   *  pt: The plaintext\n\n   *  ct: The ciphertext\n\n   An implementation should verify that the following are true, where\n   AEAD.Encrypt and AEAD.Decrypt are as defined in Section 4.5.1 of\n   [RFC9605]:\n\n   *  AEAD.Encrypt(key, nonce, aad, pt) == ct\n\n   *  AEAD.Decrypt(key, nonce, aad, ct) == pt\n\n   The other values in the test vector are intermediate values provided\n   to facilitate debugging of test failures.\n\nA.2.  SFrame Encryption/Decryption\n\n   For each case, we provide:\n\n   *  cipher_suite: The index of the cipher suite in use (see\n      Section 4.1)\n\n   *  kid: A Key ID (KID) value\n\n   *  ctr: A Counter (CTR) value\n\n   *  base_key: The base_key input to the derive_key_salt algorithm\n\n   *  sframe_key_label: The label used to derive sframe_key in the\n      derive_key_salt algorithm\n\n   *  sframe_salt_label: The label used to derive sframe_salt in the\n      derive_key_salt algorithm\n\n   *  sframe_secret: The sframe_secret variable in the derive_key_salt\n      algorithm\n\n   *  sframe_key: The sframe_key value produced by the derive_key_salt\n      algorithm\n\n   *  sframe_salt: The sframe_salt value produced by the derive_key_salt\n      algorithm\n\n   *  metadata: The metadata input to the SFrame encrypt algorithm\n\n   *  pt: The plaintext\n\n   *  ct: The SFrame ciphertext\n\n   An implementation should verify that the following are true, where\n   encrypt and decrypt are as defined in Section 4.4 of [RFC9605], using\n   an SFrame context initialized with base_key assigned to kid:\n\n   *  encrypt(ctr, kid, metadata, plaintext) == ct\n\n   *  decrypt(metadata, ct) == pt\n\n   The other values in the test vector are intermediate values provided\n   to facilitate debugging of test failures.\n\n   cipher_suite: 0x0006\n   kid: 0x0000000000000123\n   ctr: 0x0000000000004567\n   base_key: 000102030405060708090a0b0c0d0e0f\n   sframe_key_label: 534672616d6520312e30205365637265\n                     74206b65792000000000000001230006\n   sframe_salt_label: 534672616d6520312e30205365637265\n                      742073616c7420000000000000012300\n                      06\n   sframe_secret: 0fc3ea6de6aac97a35f194cf9bed94d4\n                  b5230f1cb45a785c9fe5dce9c188938a\n                  b6ba005bc4c0a19181599e9d1bcf7b74\n                  aca48b60bf5e254e546d809313e083a3\n   sframe_key: 3c343886ec1c79278836863e00fe934c\n               8894460cfa367ebdc4856b0a9268a4f4\n               fb99437876819394ef90b10ee12602d0\n               23f7128ee50f2314c2cc3cff4c56616d\n               2fe03ad2a254cc2ed29b2a4d3f2534c0\n               dda9e7c391ad1917ea07aa221dd4b224\n   sframe_salt: e082f7ce012ad30c87c49e3f\n   metadata: 4945544620534672616d65205747\n   nonce: e082f7ce012ad30c87c4db58\n   aad: 99012345674945544620534672616d65\n        205747\n   pt: 64726166742d696574662d736672616d\n       652d656e63\n   ct: 9901234567b369e03ec6467ad505ddc8\n       4914115069280c5c797555be6e32cde6\n       ac25bc9e\n\n   cipher_suite: 0x0007\n   kid: 0x0000000000000123\n   ctr: 0x0000000000004567\n   base_key: 000102030405060708090a0b0c0d0e0f\n   sframe_key_label: 534672616d6520312e30205365637265\n                     74206b65792000000000000001230007\n   sframe_salt_label: 534672616d6520312e30205365637265\n                      742073616c7420000000000000012300\n                      07\n   sframe_secret: 0fc3ea6de6aac97a35f194cf9bed94d4\n                  b5230f1cb45a785c9fe5dce9c188938a\n                  b6ba005bc4c0a19181599e9d1bcf7b74\n                  aca48b60bf5e254e546d809313e083a3\n   sframe_key: 7271d6c6cbccd2e2343d480ebea65718\n               a7bb379eefcf3f8d107c1e2a76e75529\n               3a497fd9e4e8291b965161987ef4ef24\n               983eabb06cb0a392defaab18654780a3\n               9c106ffa4a47d4183a6e593cd0c1bcab\n               2b9c6dcf049215845bfb7580c4dea80e\n   sframe_salt: 46b4367993a314910d4d9f3d\n   metadata: 4945544620534672616d65205747\n   nonce: 46b4367993a314910d4dda5a\n   aad: 99012345674945544620534672616d65\n        205747\n   pt: 64726166742d696574662d736672616d\n       652d656e63\n   ct: 990123456797cb5644d8831ff8bdc080\n       249990b24b569144cab2a87be22c20d9\n       7976\n\n   cipher_suite: 0x0008\n   kid: 0x0000000000000123\n   ctr: 0x0000000000004567\n   base_key: 000102030405060708090a0b0c0d0e0f\n   sframe_key_label: 534672616d6520312e30205365637265\n                     74206b65792000000000000001230008\n   sframe_salt_label: 534672616d6520312e30205365637265\n                      742073616c7420000000000000012300\n                      08\n   sframe_secret: 0fc3ea6de6aac97a35f194cf9bed94d4\n                  b5230f1cb45a785c9fe5dce9c188938a\n                  b6ba005bc4c0a19181599e9d1bcf7b74\n                  aca48b60bf5e254e546d809313e083a3\n   sframe_key: afe92c81e0df8c00fab619e0559fe5ae\n               efce1ef77789d4c728af1b1c1f2e3552\n               c405d274415a5291ec075c2d9954c450\n               fbd36682a4e978494808b703ce78b409\n               f9fec29b91e6e703a75c4131377c80c9\n               d51b8906088092452e2593eb142eea2d\n   sframe_salt: f6de647bac1263524cfb6533\n   metadata: 4945544620534672616d65205747\n   nonce: f6de647bac1263524cfb2054\n   aad: 99012345674945544620534672616d65\n        205747\n   pt: 64726166742d696574662d736672616d\n       652d656e63\n   ct: 9901234567112a94a288b85b49ffef1d\n       279f2830165c39d76cac8884011c\n\nAuthors' Addresses\n\n   Richard Barnes\n   Cisco\n   Email: rlb@ipv.sx\n\n\n   Emad Omara\n   Apple\n   Email: emad.omara@gmail.com\n\n\n   Aron Rosenberg\n   Apple\n   Email: aron.rosenberg@apple.com\n","snippet":"","snippet_marked":"","source":"RFC Editor","citation":"https://www.rfc-editor.org/rfc/rfc10079","license":"IETF Trust / RFC Editor terms","year":"","url":"/record/10079","fields":{"status":"PROPOSED STANDARD","stream":"IETF","wg":"NON WORKING GROUP","date":"November 2026","obsoletes":"","updates":"RFC9605"}},"generated_at":"2026-11-22T18:59:29Z"}