RFC 4869: Suite B Cryptographic Suites for IPsec
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6379.
Current version: RFC 6379 — Suite B Cryptographic Suites for IPsec
In plain English — editorial summary, not part of the RFC
This document proposes four optional cryptographic user interface suites ("UI suites") for IPsec, similar to the two suites specified in RFC 4308. The four new suites provide compatibility with the United States National Security Agency's Suite B specifications. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4869
- Published
- May 2007
- Authors
- L. Law; J. Solinas
- Status
- HISTORIC
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 6379
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 8423Reclassification of Suite B Documents to Historic StatusCurrent
July 2018
- RFC 5114Additional Diffie-Hellman Groups for Use with IETF StandardsCurrent
January 2008
- RFC 6954Using the Elliptic Curve Cryptography (ECC) Brainpool Curves for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2013
- RFC 7836Guidelines on the Cryptographic Algorithms to Accompany the Usage of Standards GOST R 34.10-2012 and GOST R 34.11-2012Current
March 2016
- RFC 4753ECP Groups For IKE and IKEv2Obsoleted
January 2007
- RFC 4430Kerberized Internet Negotiation of Keys (KINK)Current
March 2006
- RFC 4308Cryptographic Suites for IPsecCurrent
December 2005
- RFC 4307Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)Obsoleted
December 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?