RFC 2971: IMAP4 ID extension
In plain English — editorial summary, not part of the RFC
This document describes an ID extension which will enable Internet Message Access Protocol - Version 4rev1 (IMAP4rev1) to advertise what program a client or server uses to provide service. The ID extension allows the server and client to exchange identification information on their implementation in order to make bug reports and usage statistics more complete. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2971
- Published
- October 2000
- Authors
- T. Showalter
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3028Sieve: A Mail Filtering LanguageObsoleted
January 2001
- RFC 2852Deliver By SMTP Service ExtensionCurrent
June 2000
- RFC 3503Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP)Current
March 2003
- RFC 2349TFTP Timeout Interval and Transfer Size OptionsCurrent
May 1998
- RFC 2348TFTP Blocksize OptionCurrent
May 1998
- RFC 2347TFTP Option ExtensionCurrent
May 1998
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 1957Some Observations on Implementations of the Post Office Protocol (POP3)Current
June 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?