6 TLS Working Group Hyangjin Lee(KISA)
7 INTERNET-DRAFT Jaeho Yoon(KISA)
8 Document: draft-lee-tls-seed-01.txt Jaeil Lee(KISA)
9 Expiration Date: July 2005 January 2005
12 Addition of SEED Ciphersuites to Transport Layer Security (TLS)
14 <draft-lee-tls-seed-01.txt>
19 By submitting this Internet-Draft, I certify that any applicable
20 patent or other IPR claims of which I am aware have been disclosed,
21 or will be disclosed, and any of which I become aware will be
22 disclosed, in accordance with RFC 3668.
24 Internet-Drafts are working documents of the Internet Engineering
25 Task Force (IETF), its areas, and its working groups. Note that
26 other groups may also distribute working documents as Internet-
29 Internet-Drafts are draft documents valid for a maximum of six months
30 and may be updated, replaced, or obsoleted by other documents at any
31 time. It is inappropriate to use Internet-Drafts as reference
32 material or to cite them other than as "work in progress".
34 The list of current Internet-Drafts can be accessed at
35 http://www.ietf.org/ietf/1id-abstracts.txt.
37 The list of Internet-Draft Shadow Directories can be accessed at
38 http://www.ietf.org/shadow.html.
42 This document proposes the addition of new cipher suites to the
43 Transport Layer Security (TLS) protocol to support the SEED
44 encryption algorithm as a bulk cipher algorithm.
48 This document proposes the addition of new cipher suites to the TLS
49 protocol [TLS] to support the SEED encryption algorithm as a bulk
57 Lee, et. al. Expires - July 2005 [Page 1]
63 INTERNET-DRAFT SEED Ciphersuites to TLS January 2005
68 SEED is a symmetric encryption algorithm that had been developed by
69 KISA(Korea Information Security Agency) and a group of experts since
70 1998. The input/output block size of SEED is 128-bit and the key
71 length is also 128-bit. SEED has the 16-round Feistel structure. A
72 128-bit input is divided into two 64-bit blocks and the right 64-bit
73 block is an input to the round function with a 64-bit subkey
74 generated from the key scheduling.
76 SEED is easily implemented in various software and hardware because
77 it is designed to increase the efficiency of memory storage and the
78 simplicity in generating keys without degrading the security of the
79 algorithm. In particular, it can be effectively adopted to a
80 computing environment with a restricted resources such as a mobile
81 devices, smart cards and so on.
83 SEED is a national industrial association standard [TTASSEED] and is
84 widely used in South Korea for electronic commerce and financial
85 services operated on wired & wireless PKI.
87 The algorithm specification and object identifiers are described in
88 [SEED-ID]. The SEED homepage,
89 http://www.kisa.or.kr/seed/seed_eng.html, contains a wealth of
90 information about SEED, including detailed specification, evaluation
91 report, test vectors, and so on.
95 The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT",
96 "RECOMMENDED", "MAY", and "OPTIONAL" in this document (in uppercase,
97 as shown) are to be interpreted as described in [RFC2119].
99 2. Proposed Cipher Suites
101 The new ciphersuites proposed here have the following definitions:
103 CipherSuite TLS_RSA_WITH_SEED_CBC_SHA = { 0x00, 0x96};
104 CipherSuite TLS_DH_DSS_WITH_SEED_CBC_SHA = { 0x00, 0x97};
105 CipherSuite TLS_DH_RSA_WITH_SEED_CBC_SHA = { 0x00, 0x98};
106 CipherSuite TLS_DHE_DSS_WITH_SEED_CBC_SHA = { 0x00, 0x99};
107 CipherSuite TLS_DHE_RSA_WITH_SEED_CBC_SHA = { 0x00, 0x9A};
108 CipherSuite TLS_DH_anon_WITH_SEED_CBC_SHA = { 0x00, 0x9B};
110 3. CipherSuite Definitions
117 Lee, et. al. Expires - July 2005 [Page 2]
123 INTERNET-DRAFT SEED Ciphersuites to TLS January 2005
128 All the ciphersuites described here use SEED in cipher block
129 chaining(CBC) mode as a bulk cipher algorithm. SEED is a 128-bit
130 block cipher with 128-bit key size.
134 All the ciphersuites described here use SHA-1 [SHA-1] in an HMAC
135 construction as described in section 5 of [TLS].
139 The ciphersuites defined here differ in the type of certificate and
140 key exchange method. They use the following options:
142 CipherSuite Key Exchange Algorithm
144 TLS_RSA_WITH_SEED_CBC_SHA RSA
145 TLS_DH_DSS_WITH_SEED_CBC_SHA DH_DSS
146 TLS_DH_RSA_WITH_SEED_CBC_SHA DH_RSA
147 TLS_DHE_DSS_WITH_SEED_CBC_SHA DHE_DSS
148 TLS_DHE_RSA_WITH_SEED_CBC_SHA DHE_RSA
149 TLS_DH_anon_WITH_SEED_CBC_SHA DH_anon
151 For the meanings of the terms RSA, DH_DSS, DH_RSA, DHE_DSS, DHE_RSA
152 and DH_anon, please refer to sections 7.4.2 and 7.4.3 of [TLS].
154 4. IANA considerations
156 IANA does not currently have a registry for TLS-related numbers, so
157 there are no IANA actions associated with this document.
159 5. Security Considerations
161 It is not believed that the new ciphersuites are ever less secure
162 than the corresponding older ones. No security problem has been found
163 on SEED. SEED is robust against known attacks including Differential
164 cryptanalysis, Linear cryptanalysis and related key attacks, etc.
165 SEED has gone through wide public scrutinizing procedures.
166 Especially, it has been evaluated and also considered
167 cryptographically secure by trustworthy organizations such as ISO/IEC
168 JTC 1/SC 27 and Japan CRYPTREC (Cryptography Research and Evaluation
169 Committees) [ISOSEED][CRYPTREC]. SEED has been submitted to other
170 several standardization bodies such as ISO(ISO/IEC 18033-3), IETF
171 S/MIME Mail Security [SEED-SMIME] and it is under consideration. For
172 further security considerations, the reader is encouraged to read
177 Lee, et. al. Expires - July 2005 [Page 3]
183 INTERNET-DRAFT SEED Ciphersuites to TLS January 2005
186 For other security considerations, please refer to the security of
187 the corresponding older ciphersuites described in [TLS] and [AES-
192 6.1 Normative Reference
194 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
195 Requirement Levels", BCP 14, RFC 2119, March 1997.
197 [SEED] KISA, "SEED Algorithm Specification",
198 http://www.kisa.or.kr/seed/seed_eng.html"
200 [TLS] T. Dierks, and C. Allen, "The TLS Protocol Version 1.0",
201 RFC 2246, January 1999.
203 6.2 Informative Reference
205 [AES-TLS] P. Chown, "Advanced Encryption Standard (AES)
206 Ciphersuites for Transport Layer Security (TLS)",
209 [CRYPTREC] Information-technology Promotion Agency (IPA), Japan,
210 CRYPTREC. "SEED Evaluation Report", February, 2002
211 http://www.kisa.or.kr/seed/seed_eng.html
213 [ISOSEED] ISO/IEC JTC 1/SC 27, "National Body contributions on
214 NP 18033 "Encryption Algorithms" in Response to SC 27
215 N2563 (ATT.3 Korea Contribution)", ISO/IEC JTC 1/SC 27
216 N2656r1 (n2656_3.zip), October, 2000
218 [SEED-EVAL] KISA, "Self Evaluation Report",
219 http://www.kisa.or.kr/seed/seed_eng.html"
221 [SEED-ID] Jongwook Park, Sungjae Lee, Jeeyeon Kim, Jaeil Lee,
222 "The SEED Encryption Algorithm", draft-park-seed-01.txt,
225 [SEED-SMIME] Jongwook Park, Sungjae Lee, Jeeyeon Kim, Jaeil Lee,
226 "Use of the SEED Encryption Algorithm in CMS",
227 draft-ietf-smime-cms-01.txt, April, 2004.
229 [SHA-1] FIPS PUB 180-1, "Secure Hash Standard", National Institute
230 of Standards and Technology, U.S. Department of Commerce,
233 [TTASSEED] Telecommunications Technology Association (TTA),
237 Lee, et. al. Expires - July 2005 [Page 4]
243 INTERNET-DRAFT SEED Ciphersuites to TLS January 2005
246 South Korea, "128-bit Symmetric Block Cipher (SEED)",
247 TTAS.KO-12.0004, September, 1998 (In Korean)
248 http://www.tta.or.kr/English/new/main/index.htm
250 7. Authorsí¯ Addresses
253 Korea Information Security Agency
254 Phone: +82-2-405-5446
256 Email: jiinii@kisa.or.kr
259 Korea Information Security Agency
260 Phone: +82-2-405-5434
262 Email: jhyoon@kisa.or.kr
265 Korea Information Security Agency
266 Phone: +82-2-405-5300
268 Email: jilee@kisa.or.kr
271 Intellectual Property Statement
273 The IETF takes no position regarding the validity or scope of any
274 Intellectual Property Rights or other rights that might be claimed
275 to pertain to the implementation or use of the technology described
276 in this document or the extent to which any license under such
277 rights might or might not be available; nor does it represent that
278 it has made any independent effort to identify any such rights.
279 Information on the IETFí¯s procedures with respect to rights in IETF
280 Documents can be found in BCP 78 and BCP 79.
282 Copies of IPR disclosures made to the IETF Secretariat and any
283 assurances of licenses to be made available, or the result of an
284 attempt made to obtain a general license or permission for the use
285 of such proprietary rights by implementers or users of this
286 specification can be obtained from the IETF on-line IPR repository
287 at http://www.ietf.org/ipr.
289 The IETF invites any interested party to bring to its attention any
290 copyrights, patents or patent applications, or other proprietary
291 rights that may cover technology that may be required to implement
292 this standard. Please address the information to the IETF at
297 Lee, et. al. Expires - July 2005 [Page 5]
303 INTERNET-DRAFT SEED Ciphersuites to TLS January 2005
306 Disclaimer of Validity
308 This document and the information contained herein are provided on an
309 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
310 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
311 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
312 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
313 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
314 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
318 Copyright (C) The Internet Society (2005). This document is subject
319 to the rights, licenses and restrictions contained in BCP 78, and
320 except as set forth therein, the authors retain all their rights.
324 Funding for the RFC Editor function is currently provided by the
357 Lee, et. al. Expires - July 2005 [Page 6]