IETF Logo Mail Archive

[Extra] [Technical Errata Reported] RFC9051 (7518)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 18 May 2023 17:48 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3EFC151533 for <extra@ietfa.amsl.com>; Thu, 18 May 2023 10:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.108
X-Spam-Level:
X-Spam-Status: No, score=-3.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.84, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9_DYwCHTXFVI for <extra@ietfa.amsl.com>; Thu, 18 May 2023 10:48:46 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 581ACC151535 for <extra@ietf.org>; Thu, 18 May 2023 10:48:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0A9418541C; Thu, 18 May 2023 10:48:46 -0700 (PDT)
To: Alexey.Melnikov@isode.com, barryleiba@computer.org, superuser@gmail.com, francesca.palombini@ericsson.com, yaojk@cnnic.cn, brong@fastmailteam.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: adam@jooadam.hu, extra@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230518174846.0A9418541C@rfcpa.amsl.com>
Date: Thu, 18 May 2023 10:48:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ooj015LIMaAyUBb6dt9FYFN2lLk>
Subject: [Extra] [Technical Errata Reported] RFC9051 (7518)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2023 17:48:50 -0000

The following errata report has been submitted for RFC9051,
"Internet Message Access Protocol (IMAP) - Version 4rev2".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7518

--------------------------------------
Type: Technical
Reported by: Joó Ádám <adam@jooadam.hu>

Section: 4.1.1.

Original Text
-------------
   A set of messages can be referenced by a sequence set containing
   either message sequence numbers or unique identifiers.  See Section 9
   for details.  A sequence set can contain ranges of sequence numbers
   (such as "5:50"), an enumeration of specific sequence numbers, or a
   combination of the above.  A sequence set can use the special symbol
   "*" to represent the maximum sequence number in the mailbox.  A
   sequence set never contains unique identifiers.

Corrected Text
--------------
Why am I required to fix someone else's sloppy writing?

Notes
-----
The first and last sentences are in direct contradiction. Clarification is needed.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC9051 (draft-ietf-extra-imap4rev2-30)
--------------------------------------
Title               : Internet Message Access Protocol (IMAP) - Version 4rev2
Publication Date    : August 2021
Author(s)           : A. Melnikov, Ed., B. Leiba, Ed.
Category            : PROPOSED STANDARD
Source              : Email mailstore and eXtensions To Revise or Amend
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email