Diffie-Hellman Proof-of-Possession Algorithms
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 23
- Abstract
- This document describes two methods for producing an integrity check value from a Diffie-Hellman key pair. [STANDARDS-TRACK]
- Publication Date
- 2000-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2875- Link
- https://doi.org/10.17487/RFC2875
- Author(s)
- Hemma PrafullchandraJim Schaad
- Keyword(s)
- Diffie-Hellman, Security Encryption
Latest version of IETF RFC 2875
Document Versions — IETF RFC 2875
-
▶ IETF RFC 2875 (2000-07-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- NIST.FIPS.186 — DSS EXTERNAL
- IETF RFC 2104 [Active, Amended*]
- IETF RFC 2314 [Superseded*]
- IETF RFC 2459 [Superseded*]
- IETF RFC 2631 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2875.json
Superseded by:
IETF RFC 6955 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2875, Diffie-Hellman Proof-of-Possession Algorithms. Available at https://doi.org/10.17487/RFC2875
Snippet:
IETF RFC 2875, Diffie-Hellman Proof-of-Possession Algorithms. Available at https://doi.org/10.17487/RFC2875
HTML (ISO 690 compliant)
Preview:
IETF RFC 2875, Diffie-Hellman Proof-of-Possession Algorithms. Available at https://doi.org/10.17487/RFC2875
Snippet:
<span class="citation"><cite>IETF RFC 2875</cite>, Diffie-Hellman Proof-of-Possession Algorithms. Available at <a href="https://doi.org/10.17487/RFC2875" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2875</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2875, Diffie-Hellman Proof-of-Possession Algorithms
doi: 10.17487/RFC2875
url: https://doi.org/10.17487/RFC2875
doi: 10.17487/RFC2875
url: https://doi.org/10.17487/RFC2875
Snippet:
<li> <cite id="bib-rfc2875">IETF RFC 2875</cite>, Diffie-Hellman Proof-of-Possession Algorithms <span class="doi">10.17487/RFC2875</span> </li>
Referenced By
- IETF RFC 4211 [Active*]
- IETF RFC 5272 [Superseded*]
- IETF RFC 5274 [Superseded*]
- IETF RFC 5906 [Active*]
- IETF RFC 6955 [Active*]
- IETF RFC 7299 [Active*]