RFC 4308: Cryptographic Suites for IPsec
In plain English — editorial summary, not part of the RFC
The IPsec, Internet Key Exchange (IKE), and IKEv2 protocols rely on security algorithms to provide privacy and authentication between the initiator and responder. There are many such algorithms available, and two IPsec systems cannot interoperate unless they are using the same algorithms. This document specifies optional suites of algorithms and attributes that can be used to simplify the administration of IPsec when used in manual keying mode, with IKEv1 or with IKEv2. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4308
- Published
- December 2005
- Authors
- P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4304Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP)Current
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 9395Deprecation of the Internet Key Exchange Version 1 (IKEv1) Protocol and Obsoleted AlgorithmsCurrent
April 2023
- RFC 4307Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)Obsoleted
December 2005
- RFC 4430Kerberized Internet Negotiation of Keys (KINK)Current
March 2006
- RFC 3947Negotiation of NAT-Traversal in the IKECurrent
January 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?