Re: [Extra] Opsdir last call review of draft-ietf-extra-sieve-fcc-08

Dan Romascanu <dromasca@gmail.com> Wed, 09 January 2019 11:27 UTC

Return-Path: <dromasca@gmail.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 4D3B8130DC7; Wed, 9 Jan 2019 03:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OWOpgMqNIvC8; Wed, 9 Jan 2019 03:27:47 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 688D012950A; Wed, 9 Jan 2019 03:27:47 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id l14so5735368ioj.5; Wed, 09 Jan 2019 03:27:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nGkJwsxahYr36CQ3Hk4La6rPDjDcKzuqLgMQG7w9iuo=; b=EAAZzWG7ZYx+xUc3cgtRprf34Ht7sEw3x/aD/bRfE3V1OIIoxOow1nqhlQBnJoqLVI RsXZA0Ek0vJwunUd91RC1pRhod+1ebxV9Uy+La+bstiwZzqMAQulKe8rNAZhedNTL7QT dxyr0Rd0VQTvHT7ypUxvA8fCYtF2NsNTp2URd6kZmANJJXyOVQQXar4/mVVvRWMDkrhV RZZI0q9JgvvPzNWiWzEZmGGfZkW+DffhuY980caqko1nOHP8zkZyYU/4S2Pq5vujAObX 0p9a/Tnj/q19M/zbXxg/t2xXHJhxd8HahJfkf45oDf1P9vLPEBMZyolVmfgPgGPlYOgx uX9g==
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; bh=nGkJwsxahYr36CQ3Hk4La6rPDjDcKzuqLgMQG7w9iuo=; b=DnMIeGULJtX5nwnYv7QLWr9T40e3rJBhhFTZF4HFss++unHTqRZZasexjwKlQe25UZ XMhXk5CjZKqpoe4vOGiz647iBJcMKL5PF5xGkjDlppo7gv7KMKI3cPT2sMEt8udwe7p+ ABBGgYJ3DBMKWShWGHdqUcHefuOE67vECMjWlZ9dX3S4QH5IGLSxyed7LbgGxPv4VQ48 bjCAXY1VGUDeBkrsR0FYtvK8UkGUQ88z+POSl7DXyTx9KEQrvHFIWOufmeL2qfHY6eyX HbaxZEUk0D69YOUxg89MHEWq0icW3R93U+1qEMlp3s0F9bHBhzHi74cNZGmg3+soETIP 9WhA==
X-Gm-Message-State: AJcUukfK771UifWeEQvxx7x2aIJ9yhLQusvQQiDhwqktfJHMATZmeagD hgymLEXp8F6I65k45J0XmFX6BOXPXCNUDYs9omU=
X-Google-Smtp-Source: ALg8bN6QruySPV3PZF5lPQZnL9/owzDCXPhAC7gF7H8kdi7WXW4E7gbRCnzjQ3vszW9dNr1L9VVvgkFeE2rh/4U+z0k=
X-Received: by 2002:a5d:9a84:: with SMTP id c4mr3604661iom.123.1547033266617; Wed, 09 Jan 2019 03:27:46 -0800 (PST)
MIME-Version: 1.0
References: <154702622280.7446.9285138848727921959@ietfa.amsl.com> <1547031913.1905154.1629702968.4FBE79B8@webmail.messagingengine.com>
In-Reply-To: <1547031913.1905154.1629702968.4FBE79B8@webmail.messagingengine.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Wed, 9 Jan 2019 13:27:34 +0200
Message-ID: <CAFgnS4VK=FS89pYdcYv=PpQbzVrg-BaMMKy+f1Qy-7z9bRvokw@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: ops-dir@ietf.org, extra@ietf.org, ietf <ietf@ietf.org>, draft-ietf-extra-sieve-fcc.all@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005004c3057f04c072"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/OITpy6_yO7_r5jzwyDiKvXFL1Bk>
Subject: Re: [Extra] Opsdir last call review of draft-ietf-extra-sieve-fcc-08
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 09 Jan 2019 11:27:49 -0000

Hi Alexey,

Thanks for the answer. It helps indeed. It would help better if this is
documented with one paragraph in the text of the document. While developers
know well the details, users and operators may be less familiar with these.

Regards,

Dan


On Wed, Jan 9, 2019 at 1:05 PM Alexey Melnikov <aamelnikov@fastmail.fm>;
wrote:

> Hi Dan,
> Thank you for your review.
>
> On Wed, Jan 9, 2019, at 9:30 AM, Dan Romascanu wrote:
> > Reviewer: Dan Romascanu
> > Review result: Has Issues
> >
> > The document extends the Sieve Email Filtering Language [RFC5228] by
> providing
> > a number of action commands, some of which can generate additional
> messages of
> > behalf of the user. It is a clear document, its target being developers
> and
> > users of the protocol. I liked the fact that the authors included a
> > 'Compatibility with Other Actions' section that describes the
> interoperability
> > with existing deployed versions of the protocol, as well as the
> inclusion of a
> > temporary section about Implementation Status. I am missing however some
> > information about possible impact of the new action commands on
> deployment and
> > operations on servers already in operation. I assume that scalability and
> > compatibility between older and newer versions (including or not the new
> > defined commands) were assessed, but this is not documented.
>
> As :fcc is controlled by Sieve extension mechanism, Sieve scripts need to
> be updated before :fcc can be used. This means that either users need to
> manually update scripts and/or implementations that would use :fcc
> automatically need to be updated.
> So older (nonextended) implementations are not affected by this extension.
>
> Does this help or did I miss the point you are trying to convey?
>
> Thank you,
> Alexey
>
> > Some confirmation,
> > warnings (if any) and useful information that operators should know at
> > deployment would be useful. I suggest that you consider adding such a
> paragraph
> > or short section.
> >
>