Re: [sieve] [Editorial Errata Reported] RFC5804 (6345)

Barry Leiba <barryleiba@computer.org> Mon, 30 November 2020 15:13 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87B63A0D86 for <sieve@ietfa.amsl.com>; Mon, 30 Nov 2020 07:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 jm4mv05m99cs for <sieve@ietfa.amsl.com>; Mon, 30 Nov 2020 07:13:51 -0800 (PST)
Received: from mail-vk1-f179.google.com (mail-vk1-f179.google.com [209.85.221.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4382C3A0D7D for <sieve@ietf.org>; Mon, 30 Nov 2020 07:13:51 -0800 (PST)
Received: by mail-vk1-f179.google.com with SMTP id e127so2774612vkb.5 for <sieve@ietf.org>; Mon, 30 Nov 2020 07:13:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BSxCeYhBte9TyBtk6AFzNo7GVCH/OxZ2Qj//+aAEzLY=; b=CexinQO6pNzdJYPI55bDrfFbGWO+gHHw7wTqoY20rPOijKidF6oedWsou2UZx5nDyJ lfboxPwqMBZh0hIFTyJy3bvEkMgSA1E04NXTTSPabDPT6y2uAy+7K5DnwsI/NjW8EYl6 oDHrm2Pcyc2hcmOqjR3sh6Zu+PIUjQPwK/m4Yjsxtmj8xlkCekpgZbo+uqTOrS9fISGx 6BcyeOh5DGy0J7ZWDYmb+XvBkevuYeipvzwTRWtq+FkXzXvAnMwFtoMKfrZf68Tux2K5 iL5HiyfwUfQAOYqMr+LRq/t4Sw2izc5iIqmBS8dzd+QAm/1VdgLxkADmcPgvTVrArPwZ nVPA==
X-Gm-Message-State: AOAM530sUmZrl8Mqm02kZYnHJJAnPq6pRERkT/9R7p+xWMJGZfzCo7tP 4wobyh53++f/6whz09bcX7755/YcYdELaQjaahyc1wjjKDUC0g==
X-Google-Smtp-Source: ABdhPJwbCIyBmLzsH9U80mGeCeYzSuSiKFfN/la7Z2n2Wm/TOabXMmqRwzcYa+w1NKT2MsFWxLb72T+rLVOX/qiKVdw=
X-Received: by 2002:a1f:b291:: with SMTP id b139mr15681730vkf.0.1606749230078; Mon, 30 Nov 2020 07:13:50 -0800 (PST)
MIME-Version: 1.0
References: <20201130090507.61F6EF4074C@rfc-editor.org>
In-Reply-To: <20201130090507.61F6EF4074C@rfc-editor.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 30 Nov 2020 10:13:38 -0500
Message-ID: <CALaySJ+A4Fe8mP_NaAb5SEb2GB37MeJBJ6m7eZ_Hfw2KA3w=AA@mail.gmail.com>
To: Alexey Melnikov <Alexey.Melnikov@isode.com>, Tim Martin <timmartin@alumni.cmu.edu>
Cc: Murray Kucherawy <superuser@gmail.com>, Cyrus Daboo <cyrus@daboo.name>, Aaron Stone <aaron@serendipity.cx>, me@kasparetter.com, Sieve mailing list <sieve@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sieve/nn6em0hcYFy00rDIYrLxi799sZE>
Subject: Re: [sieve] [Editorial Errata Reported] RFC5804 (6345)
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sieve/>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2020 15:13:53 -0000

This report is correct that the "110" count in the second example (the
first example cited in the report) is incorrect, and should be 99.

The report's second point is a tricky one.  I think the report is also
correct about that, and here's why:

Section 1.1 says this:

   All interactions transmitted by client and server are in the form of
   lines, that is, strings that end with a CRLF.  The protocol receiver
   of a ManageSieve client or server is either reading a line or reading
   a sequence of octets with a known count followed by a line.

That means that each line of the example implicitly includes "CRLF" at
the end of it, and the count includes the final one of those.  And
then there has to be another CRLF to end the command itself.  In the
first example, that's represented by the empty line, "C:".  The second
and third examples lack that.

I intend to resolve this errata report as "Verified".  Does anyone on
this list think otherwise?

Barry

On Mon, Nov 30, 2020 at 4:05 AM RFC Errata System
<rfc-editor@rfc-editor.org> wrote:
>
> The following errata report has been submitted for RFC5804,
> "A Protocol for Remotely Managing Sieve Scripts".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6345
>
> --------------------------------------
> Type: Editorial
> Reported by: Kaspar Etter <me@kasparetter.com>
>
> Section: 2.6
>
> Original Text
> -------------
> Examples:
> […]
>        C: Putscript "mysievescript" {110+}
>        C: require ["fileinto"];
>        C:
>        C: if envelope :contains "to" "tmartin+sent" {
>        C:   fileinto "INBOX.sent";
>        C: }
>        S: OK
>
>        C: Putscript "myforwards" {190+}
>        C: redirect "111@example.net";
>        C:
>        C: if size :under 10k {
>        C:     redirect "mobile@cell.example.com";
>        C: }
>        C:
>        C: if envelope :contains "to" "tmartin+lists" {
>        C:     redirect "lists@groups.example.com";
>        C: }
>        S: OK (WARNINGS) "line 8: server redirect action
>                limit is 2, this redirect might be ignored"
>
> Corrected Text
> --------------
> Examples:
> […]
>        C: Putscript "mysievescript" {99+}
>        C: require ["fileinto"];
>        C:
>        C: if envelope :contains "to" "tmartin+sent" {
>        C:   fileinto "INBOX.sent";
>        C: }
>        C:
>        S: OK
>
>        C: Putscript "myforwards" {190+}
>        C: redirect "111@example.net";
>        C:
>        C: if size :under 10k {
>        C:     redirect "mobile@cell.example.com";
>        C: }
>        C:
>        C: if envelope :contains "to" "tmartin+lists" {
>        C:     redirect "lists@groups.example.com";
>        C: }
>        C:
>        S: OK (WARNINGS) "line 8: server redirect action
>                limit is 2, this redirect might be ignored"
>
> Notes
> -----
> The octet count of the second example is wrong. Additionally, both the second and the third example should have an empty client line after the code like the first example. Otherwise, the octet count of the last example is also wrong.
>
> 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.
>
> --------------------------------------
> RFC5804 (draft-ietf-sieve-managesieve-09)
> --------------------------------------
> Title               : A Protocol for Remotely Managing Sieve Scripts
> Publication Date    : July 2010
> Author(s)           : A. Melnikov, Ed., T. Martin
> Category            : PROPOSED STANDARD
> Source              : Sieve Mail Filtering Language
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG