RFC 9586 on IMAP Extension for Using and Returning Unique Identifiers (UIDs) Only
rfc-editor@rfc-editor.org Thu, 30 May 2024 16:49 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45D9CC14F61F; Thu, 30 May 2024 09:49:25 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A12A57FA61; Thu, 30 May 2024 09:49:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9586 on IMAP Extension for Using and Returning Unique Identifiers (UIDs) Only
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240530164924.A12A57FA61@rfcpa.rfc-editor.org>
Date: Thu, 30 May 2024 09:49:24 -0700
Message-ID-Hash: GTKKUQ3ILTHF2HXS3SFXAQ2G3HN3TIDO
X-Message-ID-Hash: GTKKUQ3ILTHF2HXS3SFXAQ2G3HN3TIDO
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, extra@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/q-1pSqTDGBn5xYJhR3JtBf2T7mw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9586
Title: IMAP Extension for Using and
Returning Unique Identifiers (UIDs) Only
Author: A. Melnikov,
A. P. Achuthan,
V. Nagulakonda,
A. Singh,
L. Alves
Status: Experimental
Stream: IETF
Date: May 2024
Mailbox: alexey.melnikov@isode.com,
arunprakash@myyahoo.com,
nvikram_imap@yahoo.com,
ashutoshvsingh@yahoo.com,
luis.alves@lafaspot.com
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-extra-imap-uidonly-08.txt
URL: https://www.rfc-editor.org/info/rfc9586
DOI: 10.17487/RFC9586
The UIDONLY extension to the Internet Message Access Protocol (RFCs
3501 and 9051) allows clients to enable a mode in which information
about mailbox changes is returned using only Unique Identifiers
(UIDs). Message numbers are not returned in responses and cannot be
used in requests once this extension is enabled. This helps both
clients and servers to reduce resource usage required to maintain a
map between message numbers and UIDs.
This document defines an experimental IMAP extension.
This document is a product of the Email mailstore and eXtensions To Revise or Amend Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC