RFC 4959: IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response
In plain English — editorial summary, not part of the RFC
To date, the Internet Message Access Protocol (IMAP) has used a Simple Authentication and Security Layer (SASL) profile which always required at least one complete round trip for an authentication, as it did not support an initial client response argument. This additional round trip at the beginning of the session is undesirable, especially when round-trip costs are high. This document defines an extension to IMAP which allows clients and servers to avoid this round trip by allowing an initial client response argument to the IMAP AUTHENTICATE command. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4959
- Published
- September 2007
- Authors
- R. Siemborski; A. Gulbrandsen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 5161The IMAP ENABLE ExtensionCurrent
March 2008
- RFC 5162IMAP4 Extensions for Quick Mailbox ResynchronizationObsoleted
March 2008
- RFC 5182IMAP Extension for Referencing the Last SEARCH ResultCurrent
March 2008
- RFC 4550Internet Email to Support Diverse Service Environments (Lemonade) ProfileObsoleted
June 2006
- RFC 4549Synchronization Operations for Disconnected IMAP4 ClientsCurrent
June 2006
- RFC 5464The IMAP METADATA ExtensionCurrent
February 2009
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
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?