Requirements for Password-Authenticated Key Agreement (PAKE) Schemes
RFC 8125
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Password', 'Key Agreement', 'Password-Authenticated Key Agreement', 'Cryptographic Protocol']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "J. Schmidt": changed name from "Joern-Marc Schmidt" to "J. Schmidt", cleared country (was "Germany"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2017-04-19
|
(System) | Received changes through RFC Editor sync (created alias RFC 8125, changed title to 'Requirements for Password-Authenticated Key Agreement (PAKE) Schemes', changed abstract to 'Password-Authenticated … Received changes through RFC Editor sync (created alias RFC 8125, changed title to 'Requirements for Password-Authenticated Key Agreement (PAKE) Schemes', changed abstract to 'Password-Authenticated Key Agreement (PAKE) schemes are interactive protocols that allow the participants to authenticate each other and derive shared cryptographic keys using a (weaker) shared password. This document reviews different types of PAKE schemes. Furthermore, it presents requirements and gives recommendations to designers of new schemes. It is a product of the Crypto Forum Research Group (CFRG).', changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-04-19, changed IRTF state to Published RFC) |
|
2017-04-19
|
(System) | RFC published |