RFC 4132: Addition of Camellia Cipher Suites to Transport Layer Security (TLS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5932.
Current version: RFC 5932 — Camellia Cipher Suites for TLS
In plain English — editorial summary, not part of the RFC
This document proposes the addition of new cipher suites to the Transport Layer Security (TLS) protocol to support the Camellia encryption algorithm as a bulk cipher algorithm. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4132
- Published
- July 2005
- Authors
- S. Moriai; A. Kato; M. Kanda
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 5932
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4134Examples of S/MIME MessagesCurrent
July 2005
- RFC 4121The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2Updated
July 2005
- RFC 4120The Kerberos Network Authentication Service (V5)Updated
July 2005
- RFC 4106The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)Current
June 2005
- RFC 4158Internet X.509 Public Key Infrastructure: Certification Path BuildingCurrent
September 2005
- RFC 4178The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation MechanismCurrent
October 2005
- RFC 4082Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform IntroductionCurrent
June 2005
- RFC 4059Internet X.509 Public Key Infrastructure Warranty Certificate ExtensionCurrent
May 2005
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?