CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 11:32:44 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=agre9g.LmoW2qfa0bRzIB3fYz1s8i7ZPNOpeM1juYUQ-1760095964-1.0.1.1-_Hz6Yu3sc_UfvW5FmE.3o3JanB3WOssK6KRPN1ZF4puPe7DVWGgyXG.vrNPXhsg0nnDrsnHQ19l0Wo0OIW8aoq9hy1jpOO3rNcv8ybvplf0; path=/; expires=Fri, 10-Oct-25 12:02:44 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c5cc7b1a039ac4-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8037 » RFC Editor
Search RFCs
RFC 8037
CFRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE), January 2017
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8037
Discuss this RFC: Send questions or comments to the mailing list jose@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8037
Abstract
This document defines how to use the Diffie-Hellman algorithms "X25519" and "X448" as well as the signature algorithms "Ed25519" and "Ed448" from the IRTF CFRG elliptic curves work in JSON Object Signing and Encryption (JOSE).
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