RFC 1994: PPP Challenge Handshake Authentication Protocol (CHAP)
In plain English — editorial summary, not part of the RFC
This document defines a method for Authentication using PPP, which uses a random Challenge, with a cryptographically hashed Response which depends upon the Challenge and a secret key. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1994
- Published
- August 1996
- Authors
- W. Simpson
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1993PPP Gandalf FZA Compression ProtocolCurrent
August 1996
- RFC 1990The PPP Multilink Protocol (MP)Current
August 1996
- RFC 1989PPP Link Quality MonitoringCurrent
August 1996
- RFC 1979PPP Deflate ProtocolCurrent
August 1996
- RFC 1978PPP Predictor Compression ProtocolCurrent
August 1996
- RFC 1977PPP BSD Compression ProtocolCurrent
August 1996
- RFC 1976PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)Current
August 1996
- RFC 1975PPP Magnalink Variable Resource CompressionCurrent
August 1996
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?