[imapext] [Technical Errata Reported] RFC7889 (5726)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 20 May 2019 21:58 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 E34AC12011C for <imapext@ietfa.amsl.com>; Mon, 20 May 2019 14:58:09 -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 oyfWtHGxsQ4g for <imapext@ietfa.amsl.com>; Mon, 20 May 2019 14:58:08 -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 4772D120058 for <imapext@ietf.org>; Mon, 20 May 2019 14:58:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 748E4B82D5D; Mon, 20 May 2019 14:57:48 -0700 (PDT)
To: jayantheesh.sb@gmail.com, narendrasingh.bisht@gmail.com, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, sm+ietf@elandsys.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: stan@glyphein.mailforce.net, imapext@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190520215748.748E4B82D5D@rfc-editor.org>
Date: Mon, 20 May 2019 14:57:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/Ne8cSFoYzUIRgj5d9KTQSHxThZw>
Subject: [imapext] [Technical Errata Reported] 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 21:58:10 -0000
The following errata report has been submitted for RFC7889, "The IMAP APPENDLIMIT Extension". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5726 -------------------------------------- Type: Technical Reported by: Stan Kalisch <stan@glyphein.mailforce.net> 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. 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. -------------------------------------- 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] [Technical Errata Reported] RFC7889 (57… RFC Errata System