RFC 4434: The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)
In plain English — editorial summary, not part of the RFC
Some implementations of IP Security (IPsec) may want to use a pseudo-random function derived from the Advanced Encryption Standard (AES). This document describes such an algorithm, called AES-XCBC-PRF-128. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4434
- Published
- February 2006
- Authors
- P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 6
- Also known as
- —
- Obsoletes:
- RFC 3664
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
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 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 3776Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home AgentsUpdated
June 2004
- RFC 3602The AES-CBC Cipher Algorithm and Its Use with IPsecCurrent
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?