RFC 3948: UDP Encapsulation of IPsec ESP Packets
In plain English — editorial summary, not part of the RFC
This protocol specification defines methods to encapsulate and decapsulate IP Encapsulating Security Payload (ESP) packets inside UDP packets for traversing Network Address Translators. ESP encapsulation, as defined in this document, can be used in both IPv4 and IPv6 scenarios. Whenever negotiated, encapsulation is used with Internet Key Exchange (IKE). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3948
- Published
- January 2005
- Authors
- A. Huttunen; B. Swander; V. Volpe; L. DiBurro; M. Stenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 2857The Use of HMAC-RIPEMD-160-96 within ESP and AHCurrent
June 2000
- RFC 2451The ESP CBC-Mode Cipher AlgorithmsCurrent
November 1998
- RFC 2410The NULL Encryption Algorithm and Its Use With IPsecCurrent
November 1998
- RFC 2403The Use of HMAC-MD5-96 within ESP and AHCurrent
November 1998
- RFC 3686Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP)Current
January 2004
- RFC 4303IP Encapsulating Security Payload (ESP)Current
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?