[imapext] [Errata Verified] RFC7889 (5726)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 20 May 2019 22:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5301201DD; Mon, 20 May 2019 15:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_QUOTING=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9R6eD9pvBN5; Mon, 20 May 2019 15:36:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DFE3120225; Mon, 20 May 2019 15:36:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B7DDFB82E6D; Mon, 20 May 2019 15:35:59 -0700 (PDT)
To: stan@glyphein.mailforce.net, jayantheesh.sb@gmail.com, narendrasingh.bisht@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: barryleiba@computer.org, iesg@ietf.org, imapext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190520223559.B7DDFB82E6D@rfc-editor.org>
Date: Mon, 20 May 2019 15:35:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/PGZj8KNwi8I__eeB84QCghA4Idg>
Subject: [imapext] [Errata Verified] RFC7889 (5726)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2019 22:36:27 -0000
The following errata report has been verified for RFC7889, "The IMAP APPENDLIMIT Extension". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5726 -------------------------------------- Status: Verified Type: Editorial Reported by: Stan Kalisch <stan@glyphein.mailforce.net> Date Reported: 2019-05-20 Verified by: Barry Leiba (IESG) Section: 3.2 Original Text ------------- C: t1 LIST "" % RETURN (STATUS (APPENDLIMIT)) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (APPENDLIMIT 257890) S: t1 OK List completed. Corrected Text -------------- C: t1 LIST "" % RETURN (STATUS (APPENDLIMIT)) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (APPENDLIMIT 257890) S: t1 OK List completed. Notes ----- Line 198 contains two spaces between ""."" and ""INBOX"" instead of one. While I had the instinct to mark this as editorial, this sample server response, whose genesis appears to be RFC 5819, ended up in two IDs (which were corrected before they became RFCs) as well. In any event, given that this response also violates the ABNF, and given the RFC Ed.'s guideline on ambiguity, I'm just marking it as technical. I'll leave it to others more familiar with the practical issues for various implementers to make the final determination on how to label it. ----- Verifier notes ----- Yes, this is an error: it comes from a combination of the RFC Editor style of double-spacing between sentences, the construction of the examples in XML in a manner that doesn't distinguish them from sentences, and the fact that it's nearly impossible to notice the situation when one is giving a final review. Editorial, though, because it's in examples. The ABNF is the authoritative place, and that's correct. -------------------------------------- RFC7889 (draft-ietf-imapapnd-appendlimit-extension-10) -------------------------------------- Title : The IMAP APPENDLIMIT Extension Publication Date : May 2016 Author(s) : J. SrimushnamBoovaraghamoorthy, N. Bisht Category : PROPOSED STANDARD Source : IMAP APPEND Extensions Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
- [imapext] [Errata Verified] RFC7889 (5726) RFC Errata System
- Re: [imapext] [Errata Verified] RFC7889 (5726) Stan Kalisch
- Re: [imapext] [Errata Verified] RFC7889 (5726) Barry Leiba