RFC 6209

Addition of the ARIA Cipher Suites to Transport Layer Security (TLS)

📅 published April 2011, from ietf

RFC 6209 ✨ Part 1 of 2

Addition of the ARIA Cipher Suites to Transport Layer Security (TLS) 🎀

Stream: Internet Engineering Task Force (IETF) 🌸
Authors: W. Kim, J. Lee, J. Park, D. Kwon (all from NSRI) 💅
Category: Informational (this is not a Standards Track doc, it's just published for info) 📖
ISSN: 2070-1721
Date: April 2011 🗓️
Obsoletes / Updates: the title block doesn't list anything this one obsoletes or updates 🦋

Abstract ✨

okay so this doc defines a bunch of cipher suites for TLS so it can use the ARIA encryption algorithm as a block cipher. bestie, that's the whole pitch 💖

Status of This Memo 📜

this doc is NOT an Internet Standards Track spec. it's published for informational purposes, so it's giving "FYI" energy 🫶

this doc is a product of the Internet Engineering Task Force (IETF). it represents the consensus of the IETF community. it got public review and was approved for publication by the Internet Engineering Steering Group (IESG). not every doc the IESG approves is a candidate for any level of Internet Standard, so see Section 2 of RFC 5741 for that 🧚

info about the current status of this doc, any errata, and how to send feedback lives at http://www.rfc-editor.org/info/rfc6209 🍓

Copyright Notice 💜

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as in effect on the date of publication. please actually read these, bestie, they spell out your rights and restrictions for this doc 🙈

if you extract Code Components from this doc, they MUST include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they're provided without warranty as described in the Simplified BSD License 🔥

Table of Contents 🗂️

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
  1.1.  ARIA  . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
  1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2.  Proposed Cipher Suites  . . . . . . . . . . . . . . . . . . . . 3
  2.1.  HMAC-Based Cipher Suites  . . . . . . . . . . . . . . . . . 3
  2.2.  GCM-Based Cipher Suites . . . . . . . . . . . . . . . . . . 3
  2.3.  PSK Cipher Suites . . . . . . . . . . . . . . . . . . . . . 4
3.  Cipher Suite Definitions  . . . . . . . . . . . . . . . . . . . 5
  3.1.  Key Exchange  . . . . . . . . . . . . . . . . . . . . . . . 5
  3.2.  Cipher  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
  3.3.  PRFs  . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
  3.4.  PSK Cipher Suites . . . . . . . . . . . . . . . . . . . . . 5
4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
  6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
  6.2.  Informative References  . . . . . . . . . . . . . . . . . . 8

1. Introduction ✨

okay so this doc specifies cipher suites for the Transport Layer Security (TLS) [RFC5246] protocol so it can use the ARIA [RFC5794] encryption algorithm as a block cipher 🎀 the suites include variants that use the SHA-2 family of hash functions and ARIA in Galois Counter Mode. elliptic curve cipher suites and pre-shared key (PSK) cipher suites are defined here too 🌈

the cipher suites with SHA-1 are NOT included in this doc. because of recent analytic work on SHA-1 [Wang05], the IETF is gradually moving away from SHA-1 and toward stronger hash algorithms. that's a whole glow-up 🦋

1.1. ARIA

ARIA is a general-purpose block cipher algorithm that Korean cryptographers developed in 2003 🇰🇷 it's an iterated block cipher with 128-, 192-, and 256-bit keys, and it encrypts 128-bit blocks in 12, 14, and 16 rounds depending on the key size. it's secure and suitable for most software and hardware implementations on 32-bit and 8-bit processors 💪

it was established as a Korean standard block cipher algorithm in 2004 [ARIAKS] and has been widely used in Korea, especially for government-to-public services. it was included in PKCS #11 in 2007 [ARIAPKCS] ✨ the algorithm specification and object identifiers are described in [RFC5794] 📚

1.2. Terminology

the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this doc are to be interpreted as described in [RFC2119]. bestie, these are the official words, so they keep their exact meaning 🫶

2. Proposed Cipher Suites 🍓

2.1. HMAC-Based Cipher Suites

the first twenty cipher suites use ARIA [RFC5794] in Cipher Block Chaining (CBC) mode with a SHA-2 family Hashed Message Authentication Code (HMAC). eight out of those twenty use elliptic curves 🧚

CipherSuite TLS_RSA_WITH_ARIA_128_CBC_SHA256         = { 0xC0,0x3C };
CipherSuite TLS_RSA_WITH_ARIA_256_CBC_SHA384         = { 0xC0,0x3D };
CipherSuite TLS_DH_DSS_WITH_ARIA_128_CBC_SHA256      = { 0xC0,0x3E };
CipherSuite TLS_DH_DSS_WITH_ARIA_256_CBC_SHA384      = { 0xC0,0x3F };
CipherSuite TLS_DH_RSA_WITH_ARIA_128_CBC_SHA256      = { 0xC0,0x40 };
CipherSuite TLS_DH_RSA_WITH_ARIA_256_CBC_SHA384      = { 0xC0,0x41 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x42 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x43 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x44 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x45 };
CipherSuite TLS_DH_anon_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x46 };
CipherSuite TLS_DH_anon_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x47 };

CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_128_CBC_SHA256 = { 0xC0,0x48 };
CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_256_CBC_SHA384 = { 0xC0,0x49 };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_128_CBC_SHA256  = { 0xC0,0x4A };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_256_CBC_SHA384  = { 0xC0,0x4B };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_128_CBC_SHA256   = { 0xC0,0x4C };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_256_CBC_SHA384   = { 0xC0,0x4D };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_128_CBC_SHA256    = { 0xC0,0x4E };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_256_CBC_SHA384    = { 0xC0,0x4F };

2.2. GCM-Based Cipher Suites

the next twenty cipher suites use the same asymmetric algorithms as the ones in the previous section, but they use the authenticated encryption modes defined in TLS 1.2 with ARIA in Galois Counter Mode (GCM) [GCM] 🌸

CipherSuite TLS_RSA_WITH_ARIA_128_GCM_SHA256         = { 0xC0,0x50 };
CipherSuite TLS_RSA_WITH_ARIA_256_GCM_SHA384         = { 0xC0,0x51 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x52 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x53 };
CipherSuite TLS_DH_RSA_WITH_ARIA_128_GCM_SHA256      = { 0xC0,0x54 };
CipherSuite TLS_DH_RSA_WITH_ARIA_256_GCM_SHA384      = { 0xC0,0x55 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x56 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x57 };
CipherSuite TLS_DH_DSS_WITH_ARIA_128_GCM_SHA256      = { 0xC0,0x58 };
CipherSuite TLS_DH_DSS_WITH_ARIA_256_GCM_SHA384      = { 0xC0,0x59 };
CipherSuite TLS_DH_anon_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x5A };
CipherSuite TLS_DH_anon_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x5B };

CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_128_GCM_SHA256 = { 0xC0,0x5C };
CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_256_GCM_SHA384 = { 0xC0,0x5D };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_128_GCM_SHA256  = { 0xC0,0x5E };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_256_GCM_SHA384  = { 0xC0,0x5F };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256   = { 0xC0,0x60 };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384   = { 0xC0,0x61 };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_128_GCM_SHA256    = { 0xC0,0x62 };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_256_GCM_SHA384    = { 0xC0,0x63 };

2.3. PSK Cipher Suites

the next fourteen cipher suites describe PSK cipher suites. eight of them use an HMAC and six use ARIA Galois Counter Mode 🔑

CipherSuite TLS_PSK_WITH_ARIA_128_CBC_SHA256         = { 0xC0,0x64 };
CipherSuite TLS_PSK_WITH_ARIA_256_CBC_SHA384         = { 0xC0,0x65 };
CipherSuite TLS_DHE_PSK_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x66 };
CipherSuite TLS_DHE_PSK_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x67 };
CipherSuite TLS_RSA_PSK_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x68 };
CipherSuite TLS_RSA_PSK_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x69 };
CipherSuite TLS_PSK_WITH_ARIA_128_GCM_SHA256         = { 0xC0,0x6A };
CipherSuite TLS_PSK_WITH_ARIA_256_GCM_SHA384         = { 0xC0,0x6B };
CipherSuite TLS_DHE_PSK_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x6C };
CipherSuite TLS_DHE_PSK_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x6D };
CipherSuite TLS_RSA_PSK_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x6E };
CipherSuite TLS_RSA_PSK_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x6F };
CipherSuite TLS_ECDHE_PSK_WITH_ARIA_128_CBC_SHA256   = { 0xC0,0x70 };
CipherSuite TLS_ECDHE_PSK_WITH_ARIA_256_CBC_SHA384   = { 0xC0,0x71 };

5. IANA Considerations 🎀

okay so IANA went and grabbed a bunch of numbers from the TLS Cipher Suite Registry for ARIA 💖 here they are, all lined up and ready to go ✨

CipherSuite TLS_RSA_WITH_ARIA_128_CBC_SHA256         = { 0xC0,0x3C };
CipherSuite TLS_RSA_WITH_ARIA_256_CBC_SHA384         = { 0xC0,0x3D };
CipherSuite TLS_DH_DSS_WITH_ARIA_128_CBC_SHA256      = { 0xC0,0x3E };
CipherSuite TLS_DH_DSS_WITH_ARIA_256_CBC_SHA384      = { 0xC0,0x3F };
CipherSuite TLS_DH_RSA_WITH_ARIA_128_CBC_SHA256      = { 0xC0,0x40 };
CipherSuite TLS_DH_RSA_WITH_ARIA_256_CBC_SHA384      = { 0xC0,0x41 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x42 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x43 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x44 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x45 };
CipherSuite TLS_DH_anon_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x46 };
CipherSuite TLS_DH_anon_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x47 };

CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_128_CBC_SHA256 = { 0xC0,0x48 };
CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_256_CBC_SHA384 = { 0xC0,0x49 };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_128_CBC_SHA256  = { 0xC0,0x4A };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_256_CBC_SHA384  = { 0xC0,0x4B };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_128_CBC_SHA256   = { 0xC0,0x4C };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_256_CBC_SHA384   = { 0xC0,0x4D };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_128_CBC_SHA256    = { 0xC0,0x4E };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_256_CBC_SHA384    = { 0xC0,0x4F };

CipherSuite TLS_RSA_WITH_ARIA_128_GCM_SHA256         = { 0xC0,0x50 };
CipherSuite TLS_RSA_WITH_ARIA_256_GCM_SHA384         = { 0xC0,0x51 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x52 };
CipherSuite TLS_DHE_RSA_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x53 };
CipherSuite TLS_DH_RSA_WITH_ARIA_128_GCM_SHA256      = { 0xC0,0x54 };
CipherSuite TLS_DH_RSA_WITH_ARIA_256_GCM_SHA384      = { 0xC0,0x55 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x56 };
CipherSuite TLS_DHE_DSS_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x57 };
CipherSuite TLS_DH_DSS_WITH_ARIA_128_GCM_SHA256      = { 0xC0,0x58 };
CipherSuite TLS_DH_DSS_WITH_ARIA_256_GCM_SHA384      = { 0xC0,0x59 };
CipherSuite TLS_DH_anon_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x5A };
CipherSuite TLS_DH_anon_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x5B };

CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_128_GCM_SHA256 = { 0xC0,0x5C };
CipherSuite TLS_ECDHE_ECDSA_WITH_ARIA_256_GCM_SHA384 = { 0xC0,0x5D };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_128_GCM_SHA256  = { 0xC0,0x5E };
CipherSuite TLS_ECDH_ECDSA_WITH_ARIA_256_GCM_SHA384  = { 0xC0,0x5F };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256   = { 0xC0,0x60 };
CipherSuite TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384   = { 0xC0,0x61 };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_128_GCM_SHA256    = { 0xC0,0x62 };
CipherSuite TLS_ECDH_RSA_WITH_ARIA_256_GCM_SHA384    = { 0xC0,0x63 };
CipherSuite TLS_PSK_WITH_ARIA_128_CBC_SHA256         = { 0xC0,0x64 };
CipherSuite TLS_PSK_WITH_ARIA_256_CBC_SHA384         = { 0xC0,0x65 };
CipherSuite TLS_DHE_PSK_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x66 };
CipherSuite TLS_DHE_PSK_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x67 };
CipherSuite TLS_RSA_PSK_WITH_ARIA_128_CBC_SHA256     = { 0xC0,0x68 };
CipherSuite TLS_RSA_PSK_WITH_ARIA_256_CBC_SHA384     = { 0xC0,0x69 };
CipherSuite TLS_PSK_WITH_ARIA_128_GCM_SHA256         = { 0xC0,0x6A };
CipherSuite TLS_PSK_WITH_ARIA_256_GCM_SHA384         = { 0xC0,0x6B };
CipherSuite TLS_DHE_PSK_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x6C };
CipherSuite TLS_DHE_PSK_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x6D };
CipherSuite TLS_RSA_PSK_WITH_ARIA_128_GCM_SHA256     = { 0xC0,0x6E };
CipherSuite TLS_RSA_PSK_WITH_ARIA_256_GCM_SHA384     = { 0xC0,0x6F };
CipherSuite TLS_ECDHE_PSK_WITH_ARIA_128_CBC_SHA256   = { 0xC0,0x70 };
CipherSuite TLS_ECDHE_PSK_WITH_ARIA_256_CBC_SHA384   = { 0xC0,0x71 };

6. References 📚

6.1. Normative References 💜

these are the must-read-first sources, the ones the spec is built on 🦋

[GCM]       Dworkin, M., "Recommendation for Block Cipher Modes of
            Operation: Galois/Counter Mode (GCM) and GMAC", NIST
            SP 800-38D, November 2007.

[RFC2119]   Bradner, S., "Key words for use in RFCs to Indicate
            Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC4279]   Eronen, P. and H. Tschofenig, "Pre-Shared Key
            Ciphersuites for Transport Layer Security (TLS)",
            RFC 4279, December 2005.

[RFC4785]   Blumenthal, U. and P. Goel, "Pre-Shared Key (PSK)
            Ciphersuites with NULL Encryption for Transport Layer
            Security (TLS)", RFC 4785, January 2007.

[RFC5116]   McGrew, D., "An Interface and Algorithms for
            Authenticated Encryption", RFC 5116, January 2008.

[RFC5246]   Dierks, T. and E. Rescorla, "The Transport Layer Security
            (TLS) Protocol Version 1.2", RFC 5246, August 2008.

[RFC5288]   Salowey, J., Choudhury, A., and D. McGrew, "AES Galois
            Counter Mode (GCM) Cipher Suites for TLS", RFC 5288,
            August 2008.

[RFC5289]   Rescorla, E., "TLS Elliptic Curve Cipher Suites with SHA-
            256/384 and AES Galois Counter Mode (GCM)", RFC 5289,
            August 2008.

[RFC5487]   Badra, M., "Pre-Shared Key Cipher Suites for TLS with
            SHA-256/384 and AES Galois Counter Mode", RFC 5487,
            March 2009.

[RFC5489]   Badra, M. and I. Hajjeh, "ECDHE_PSK Cipher Suites for
            Transport Layer Security (TLS)", RFC 5489, March 2009.

[RFC5794]   Lee, J., Lee, J., Kim, J., Kwon, D., and C. Kim, "A
            Description of the ARIA Encryption Algorithm", RFC 5794,
            March 2010.

6.2. Informative References 🌸

these ones are just for extra context, bestie, nice to have but not required 🫶

[ARIAKS]    Korean Agency for Technology and Standards, "128 bit
            block encryption algorithm ARIA - Part 1: General (in
            Korean)", KS X 1213-1:2009, December 2009.

[ARIAPKCS]  RSA Laboratories, "Additional PKCS #11 Mechanisms",
            PKCS #11 v2.20 Amendment 3 Revision 1, January 2007.

[Wang05]    Wang, X., Yin, Y., and H. Yu, "Finding Collisions in the
            Full SHA-1", CRYPTO 2005, LNCS vol.3621, pp.17-36,
            August 2005.

[YWL]       Li, Y., Wu, W., and L. Zhang, "Integral attacks on
            reduced-round ARIA block cipher", ISPEC 2010,
            LNCS Vol.6047, pp. 19-29, May 2010.

Authors' Addresses 👑

the squad behind this one, all from the National Security Research Institute 💅

Woo-Hwan Kim
National Security Research Institute
P.O.Box 1, Yuseong
Daejeon  305-350
Korea

EMail: whkim5@ensec.re.kr


Jungkeun Lee
National Security Research Institute
P.O.Box 1, Yuseong
Daejeon  305-350
Korea

EMail: jklee@ensec.re.kr


Je-Hong Park
National Security Research Institute
P.O.Box 1, Yuseong
Daejeon  305-350
Korea

EMail: jhpark@ensec.re.kr


Daesung Kwon
National Security Research Institute
P.O.Box 1, Yuseong
Daejeon  305-350
Korea

EMail: ds_kwon@ensec.re.kr

📦 where this page comes from

ietf: rfc6209 2011-04
💖 girlified by claude-haiku-5-5 on 2026-10-17: a language model's rewrite of the original, under its terms