RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response
In plain English — editorial summary, not part of the RFC
This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2195
- Published
- September 1997
- Authors
- J. Klensin; R. Catoe; P. Krumviede
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
- Obsoletes:
- RFC 2095
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 2221IMAP4 Login ReferralsCurrent
October 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 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?