RFC 4359: The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload (ESP) and Authentication Header (AH)
In plain English — editorial summary, not part of the RFC
This memo describes the use of the RSA digital signature algorithm as an authentication algorithm within the revised IP Encapsulating Security Payload (ESP) as described in RFC 4303 and the revised IP Authentication Header (AH) as described in RFC 4302. The use of a digital signature algorithm, such as RSA, provides data origin authentication in applications when a secret key method (e.g., HMAC) does not provide this property. One example is the use of ESP and AH to authenticate the sender of an IP multicast packet. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4359
- Published
- January 2006
- Authors
- B. Weis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent
May 2006
- RFC 4056Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)Current
June 2005
- RFC 3653XML-Signature XPath Filter 2.0Current
December 2003
- RFC 5652Cryptographic Message Syntax (CMS)Updated
September 2009
- RFC 7797JSON Web Signature (JWS) Unencoded Payload OptionCurrent
February 2016
- RFC 8708Use of the HSS/LMS Hash-Based Signature Algorithm in the Cryptographic Message Syntax (CMS)Obsoleted
February 2020
- RFC 8778Use of the HSS/LMS Hash-Based Signature Algorithm with CBOR Object Signing and Encryption (COSE)Current
April 2020
- RFC 8812CBOR Object Signing and Encryption (COSE) and JSON Object Signing and Encryption (JOSE) Registrations for Web Authentication (WebAuthn) AlgorithmsCurrent
August 2020
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?