RFC 8121: Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3 (KAM3)
In plain English — editorial summary, not part of the RFC
This document specifies cryptographic algorithms for use with the Mutual user authentication method for the Hypertext Transfer Protocol (HTTP).
Document record
- Document ID
- RFC8121
- Published
- April 2017
- Authors
- Y. Oiwa; H. Watanabe; H. Takagi; K. Maeda; T. Hayashi; Y. Ioku
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8120Mutual Authentication Protocol for HTTPCurrent
April 2017
- RFC 6819OAuth 2.0 Threat Model and Security ConsiderationsUpdated
January 2013
- RFC 2660The Secure HyperText Transfer ProtocolCurrent
August 1999
- RFC 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoleted
September 2015
- RFC 7236Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme RegistrationsCurrent
June 2014
- RFC 5397WebDAV Current Principal ExtensionCurrent
December 2008
- RFC 8332Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) ProtocolCurrent
March 2018
- RFC 7804Salted Challenge Response HTTP Authentication MechanismCurrent
March 2016
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?