RFC 6379: Suite B Cryptographic Suites for IPsec
In plain English — editorial summary, not part of the RFC
This document proposes four cryptographic user interface suites ("UI suites") for IP Security (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 document obsoletes RFC 4869, which presented earlier versions of these suites. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6379
- Published
- October 2011
- Authors
- L. Law; J. Solinas
- Status
- HISTORIC
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoletes:
- RFC 4869
Topics
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 6954Using the Elliptic Curve Cryptography (ECC) Brainpool Curves for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2013
- RFC 5114Additional Diffie-Hellman Groups for Use with IETF StandardsCurrent
January 2008
- 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 6467Secure Password Framework for Internet Key Exchange Version 2 (IKEv2)Current
December 2011
- RFC 6027IPsec Cluster Problem StatementCurrent
October 2010
- RFC 5996Internet Key Exchange Protocol Version 2 (IKEv2)Obsoleted
September 2010
- RFC 5903Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2Current
June 2010
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?