RFC 7008: A Description of the KCipher-2 Encryption Algorithm
In plain English — editorial summary, not part of the RFC
This document describes the KCipher-2 encryption algorithm. KCipher-2 is a stream cipher with a 128-bit key and a 128-bit initialization vector. Since the algorithm for KCipher-2 was published in 2007, security and efficiency have been rigorously evaluated through academic and industrial studies. As of the publication of this document, no security vulnerabilities have been found. KCipher-2 offers fast encryption and decryption by means of simple operations that enable efficient implementation. KCipher-2 has been used for industrial applications, especially for mobile health monitoring and diagnostic services in Japan.
Document record
- Document ID
- RFC7008
- Published
- August 2013
- Authors
- S. Kiyomoto; W. Shin
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5794A Description of the ARIA Encryption AlgorithmCurrent
March 2010
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 1829The ESP DES-CBC TransformCurrent
August 1995
- RFC 8998ShangMi (SM) Cipher Suites for TLS 1.3Current
March 2021
- RFC 3610Counter with CBC-MAC (CCM)Current
September 2003
- RFC 7350Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)Current
August 2014
- RFC 6655AES-CCM Cipher Suites for Transport Layer Security (TLS)Updated
July 2012
- RFC 7402Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)Current
April 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?