RFC 6955: Diffie-Hellman Proof-of-Possession Algorithms
In plain English — editorial summary, not part of the RFC
This document describes two methods for producing an integrity check value from a Diffie-Hellman key pair and one method for producing an integrity check value from an Elliptic Curve key pair. This behavior is needed for such operations as creating the signature of a Public-Key Cryptography Standards (PKCS) #10 Certification Request. These algorithms are designed to provide a Proof-of-Possession of the private key and not to be a general purpose signing algorithm. This document obsoletes RFC 2875.
Document record
- Document ID
- RFC6955
- Published
- May 2013
- Authors
- J. Schaad; H. Prafullchandra
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 43
- Also known as
- —
- Obsoletes:
- RFC 2875
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9142Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)Current
January 2022
- RFC 10015Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2Current
July 2026
- RFC 7636Proof Key for Code Exchange by OAuth Public ClientsCurrent
September 2015
- RFC 6162Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Asymmetric Key Package Content TypeCurrent
April 2011
- RFC 6161Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content TypeCurrent
April 2011
- RFC 7817Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related ProtocolsCurrent
March 2016
- RFC 5721POP3 Support for UTF-8Obsoleted
February 2010
- RFC 8270Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 BitsCurrent
December 2017
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?