Re: [imapext] [Errata Verified] RFC7889 (5726)

"Stan Kalisch" <stan@glyphein.mailforce.net> Mon, 20 May 2019 23:09 UTC

Return-Path: <stan@glyphein.mailforce.net>
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 8413B120046; Mon, 20 May 2019 16:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mailforce.net header.b=NW8401/M; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=mjPC5Jl+
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 cl_k6seQc8kL; Mon, 20 May 2019 16:09:46 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65B6A12007C; Mon, 20 May 2019 16:09:46 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 7D7CA617; Mon, 20 May 2019 19:09:45 -0400 (EDT)
Received: from imap6 ([10.202.2.56]) by compute7.internal (MEProxy); Mon, 20 May 2019 19:09:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=ZteylFM7PJTzJM/KOar1J27/6HTo u8vEyYiEoh1lhwU=; b=NW8401/MGStakJeGy9rolUVNWCDno8tcsSrnNou5hHjN MGIg4o3Ra2+O7BB5I6wwhHogg6gc61YJwi+usfCBZYBBj+soOV6DQd2Ot0Jinx8Y Xzf0clnZo6cyl/+4SB/ghNRFMfldzqt5zacg/Xq+HguVwvbspYh3aZIsw8yNFwCc jjLVeHnInNCIu8DD0jnTnNHrMWsH3v1YGwofuQ0B8/wppCZMYz15HCPnSNco79H3 aUf0bbWuW7UgM3tB+3nyWWTcsL+dtmbfWhc94MhDt/L4EHL9PDQ0lAcLaLRqIP13 VRlqkgmDuVCZrOrf8JKQskJ394rqeHLCE+lCasFBqA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ZteylF M7PJTzJM/KOar1J27/6HTou8vEyYiEoh1lhwU=; b=mjPC5Jl+Y790U3PN8lCVWf F1A2f8krrVlBVDu9/OUY7SEaofxDYYyxDmwYb5smsmvHM91PVmFzUwfRnvHtceN5 lBaYfeAeF1EUwHfCA+6HFVoRtLWdjguOr1WRraJeXe3jpMdGoxtKPhKeGPDioBav Ssx+h1Pm85AMLOq72nfKG4tZU+Myb+eFDpYk5FiD4cWnYUJlmNVp12BU3M6p+WtC x9AoyeRZkG8kW1k2fQWjRou/aiAzwYpzjYfYs+GKh47BWAqYD/jXF24aASQoFFeD TY/tpXlgWczfigwlPRG3jg/8cAg63wRU82AF1oPLmPNaRSasiDZU8Bfen64tooxQ ==
X-ME-Sender: <xms:uDPjXK8XKXQ252F_iIFIzdYGsoa1bL4jE65rFOfY9FkkH5oShHMNvg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddtledgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfufhtrghnucfmrghlihhstghhfdcuoehsthgrnhesghhl hihphhgvihhnrdhmrghilhhfohhrtggvrdhnvghtqeenucfrrghrrghmpehmrghilhhfrh homhepshhtrghnsehglhihphhhvghinhdrmhgrihhlfhhorhgtvgdrnhgvthenucevlhhu shhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:uDPjXFlrFm5g5hpFTeG9o94KtX4OMUEIf2Ec9LH5LQQ4PM88ZWM4Bg> <xmx:uDPjXKP2b_n6vxP0vLsMoLXKtuiaeVlwZRNHbJVXWxvB6tarEOtUsQ> <xmx:uDPjXEKzhVRrNMudQBC_aRValMMfz613FdlVg74nrPhaH_EBJqws7w> <xmx:uTPjXAkb_1kdt6Zkod3gqv-tma2hqyVnTLPGE63FTVYbb6KFItow_w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8247282150; Mon, 20 May 2019 19:09:44 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-549-ge400f56-fmstable-20190516v3
Mime-Version: 1.0
Message-Id: <c07db880-06ef-45de-b8ca-74ab3c0583a8@www.fastmail.com>
In-Reply-To: <20190520223559.B7DDFB82E6D@rfc-editor.org>
References: <20190520223559.B7DDFB82E6D@rfc-editor.org>
Date: Mon, 20 May 2019 19:09:44 -0400
From: Stan Kalisch <stan@glyphein.mailforce.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>, jayantheesh.sb@gmail.com, narendrasingh.bisht@gmail.com
Cc: barryleiba@computer.org, iesg@ietf.org, imapext@ietf.org
Content-Type: multipart/alternative; boundary="5a432961747a4ca0900d684be6384d66"
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/FlK1urMZI_LpleM6rXi384_2_oY>
Subject: Re: [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 23:09:50 -0000

On Mon, May 20, 2019, at 6:36 PM, RFC Errata System wrote:
> ----- 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.

This is helpful to know, and when you put it like that, makes complete sense to me. I suppose part of my confusion stems from the fact that I reported an erratum for an example in an RFC about two years ago and it was verified as technical. Is this something that varies across disciplines? This may be helpful information for those who report errors but are not as familiar as others with the IETF and RFC Editor's process.


Thanks,
Stan

> 
> --------------------------------------
> 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
>