RFC 6114: The 128-Bit Blockcipher CLEFIA
In plain English — editorial summary, not part of the RFC
This document describes the specification of the blockcipher CLEFIA. CLEFIA is a 128-bit blockcipher, with key lengths of 128, 192, and 256 bits, which is compatible with the interface of the Advanced Encryption Standard (AES). The algorithm of CLEFIA was published in 2007, and its security has been scrutinized in the public community. CLEFIA is one of the new-generation lightweight blockcipher algorithms designed after AES. Among them, CLEFIA offers high performance in software and hardware as well as lightweight implementation in hardware. CLEFIA will be of benefit to the Internet, which will be connected to more distributed and constrained devices. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6114
- Published
- March 2011
- Authors
- M. Katagi; S. Moriai
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6139Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) ScenariosCurrent
February 2011
- RFC 6218Cisco Vendor-Specific RADIUS Attributes for the Delivery of Keying MaterialCurrent
April 2011
- RFC 7076P6R's Secure Shell Public Key SubsystemCurrent
November 2013
- RFC 7397Report from the Smart Object Security WorkshopCurrent
December 2014
- RFC 7489Domain-based Message Authentication, Reporting, and Conformance (DMARC)Obsoleted
March 2015
- RFC 4503A Description of the Rabbit Stream Cipher AlgorithmCurrent
May 2006
- RFC 7943A Method for Generating Semantically Opaque Interface Identifiers (IIDs) with the Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
September 2016
- RFC 3610Counter with CBC-MAC (CCM)Current
September 2003
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?