Re: [Extra] Benjamin Kaduk's Yes on draft-ietf-extra-sieve-special-use-04: (with COMMENT)

Ned Freed <ned.freed@mrochek.com> Fri, 11 January 2019 15:48 UTC

Return-Path: <ned.freed@mrochek.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 025CF124BF6; Fri, 11 Jan 2019 07:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Level:
X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.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 DM8QZriSyztG; Fri, 11 Jan 2019 07:48:35 -0800 (PST)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0C8812426E; Fri, 11 Jan 2019 07:48:35 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R1VMIP5RBK00DNTO@mauve.mrochek.com>; Fri, 11 Jan 2019 07:45:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1547221538; bh=ZAXhjALBq7FYkTJGv6cjCxyp9C7oP7FPx3k+gwK/dZc=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=M5K+AkB7qPh87c7nscDTuwYPFO0GI82feeeWnln2Ps9VdtkHb26vGMBlCdCc6cZKb XsyhdZhdF4S0EmcGNyS6hwUhOLTy94RcCDfOh8U6D33kagrqE8TNk1tWxAyQBu7cMq Mu+cY1ZKW/pM2eeuDIEy8Q+OXZi9ia2iTPjCMmMs=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01R1N39ADWKW00004L@mauve.mrochek.com>; Fri, 11 Jan 2019 07:45:34 -0800 (PST)
Cc: Ned Freed <ned.freed@mrochek.com>, The IESG <iesg@ietf.org>, extra@ietf.org, draft-ietf-extra-sieve-special-use@ietf.org, yaojk@cnnic.cn, extra-chairs@ietf.org
Message-id: <01R1VMIMRH5A00004L@mauve.mrochek.com>
Date: Fri, 11 Jan 2019 07:45:04 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 10 Jan 2019 15:45:58 -0600" <20190110214558.GQ28515@kduck.mit.edu>
References: <154708325763.4990.14007827148353808097.idtracker@ietfa.amsl.com> <01R1TR9L1OVU00004L@mauve.mrochek.com> <20190110214558.GQ28515@kduck.mit.edu>
To: Benjamin Kaduk <kaduk@mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/h5VD2EbfTH16mPiH5978QVGFWRU>
Subject: Re: [Extra] Benjamin Kaduk's Yes on draft-ietf-extra-sieve-special-use-04: (with COMMENT)
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: Fri, 11 Jan 2019 15:48:38 -0000

> On Wed, Jan 09, 2019 at 11:31:27PM -0800, Ned Freed wrote:
> > > Benjamin Kaduk has entered the following ballot position for
> > > draft-ietf-extra-sieve-special-use-04: Yes
> >
> > > When responding, please keep the subject line intact and reply to all
> > > email addresses included in the To and CC lines. (Feel free to cut this
> > > introductory paragraph, however.)
> >
> >
> > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > > The document, along with other ballot positions, can be found here:
> > > https://datatracker.ietf.org/doc/draft-ietf-extra-sieve-special-use/
> >
> >
> >
> > > ----------------------------------------------------------------------
> > > COMMENT:
> > > ----------------------------------------------------------------------
> >
> > > I'm balloting Yes because this document seems like it is going to do the
> > > right thing in helping to keep sieve up to date with IMAP.  But I do still
> > > have a few comments.
> >
> > > Section 4
> >
> > >                      Implementations SHOULD handle an invalid special-
> > >    use flag in the same way as an invalid mailbox name is handled.  The
> >
> > > (Does "invalid" mean "syntactically invalid" or "nonexistent" or something
> > > else?  Presumably this is just a sieve convention that I've not been
> > > exposed to yet...)
> >
> > Given that the preceeding sentence in the paragraph is "The special-use flag
> > specified with the ":specialuse" argument MUST conform to the "use-attr" syntax
> > described in Section 6 of RFC6154 [SIEVE-MAILBOX]." I think it's actually
> > pretty clear that this is talking about syntax and not something. I suppose
> > changing it to say "syntactically invalid" would not hurt, but I don't really
> > think it's necessary given the context.

> Okay.

> > What actually concerns me more here is the MUST in the first sentence. This use
> > of compliance language strikes me as misplaced. Sieve scripts are specified by
> > users one way or another and say what they say; when we talk about compliance
> > in these documents we're talking about what a Sieve implementation has to do,
> > like the SHOULD in the second sentence, which is actually dealing with the
> > case where the MUST is violated.

> It's probably clearer to say something descriptive like "[...] flag
> specified with the ':specialuse' argument conforms to the 'use-attr' syntax
> described in [...]"

Works for me.

				Ned