RFC 2088: IMAP4 non-synchronizing literals
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7888.
Current version: RFC 7888 — IMAP4 Non-synchronizing Literals
In plain English — editorial summary, not part of the RFC
The Internet Message Access Protocol [STANDARDS-TRACK]
Document record
- Document ID
- RFC2088
- Published
- January 1997
- Authors
- J. Myers
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 2
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2095IMAP/POP AUTHorize Extension for Simple Challenge/ResponseObsoleted
January 1997
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2195IMAP/POP AUTHorize Extension for Simple Challenge/ResponseCurrent
September 1997
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?