CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 04:37:08 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=Pd63l5MOA6BOvsIQBlXdRl_S3plajiEC5iwtALr2B0c-1760157428-1.0.1.1-vxga9DvKTywnXWEXELgw0.CnWlw8Cwt7PcZPrXUXC3Ha1NgX86RuBdce7KE8Yu9lurTdEtb36aEnO2rMkUXJNmEEcNbqoRijMsvZBNNQCRo; path=/; expires=Sat, 11-Oct-25 05:07:08 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cba910bfeac537-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2412 » RFC Editor
Search RFCs
RFC 2412
The OAKLEY Key Determination Protocol, November 1998
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2412
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2412
Abstract
This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. This memo provides information for the Internet community.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us