RFC 8474: IMAP Extension for Object Identifiers
In plain English — editorial summary, not part of the RFC
This document updates RFC 3501 (IMAP4rev1) with persistent identifiers on mailboxes and messages to allow clients to more efficiently reuse cached data when resources have changed location on the server.
Document record
- Document ID
- RFC8474
- Published
- September 2018
- Authors
- B. Gondwana
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
- Updates:
- RFC 3501
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7377IMAP4 Multimailbox SEARCH ExtensionCurrent
October 2014
- RFC 6154IMAP LIST Extension for Special-Use MailboxesCurrent
March 2011
- RFC 5788IMAP4 Keyword RegistryUpdated
March 2010
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 1730Internet Message Access Protocol - Version 4Obsoleted
December 1994
- RFC 8438IMAP Extension for STATUS=SIZECurrent
August 2018
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
- RFC 8514Internet Message Access Protocol (IMAP) - SAVEDATE ExtensionCurrent
January 2019
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?