The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload and Authentication Header
RFC 4359, “The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload and Authentication Header”, is a Proposed Standard document published in January 2006 by B. Weis. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4359 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4358 A Uniform Resource Name Namespace for the Open Mobile Alliance
- RFC 4360 BGP Extended Communities Attribute
- RFC 4357 Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms
- RFC 4361 Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four
- RFC 4356 Mapping Between the Multimedia Messaging Service and Internet Mail
- RFC 4362 RObust Header Compression : A Link-Layer Assisted Profile for IP/UDP/RTP
- RFC 4355 IANA Registration for Enumservices email, fax, mms, ems, and sms
- RFC 4363 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions