Re: [sieve] New Version Notification for draft-george-sieve-vacation-time-00

Aaron Stone <aaron@serendipity.cx> Thu, 04 February 2010 18:32 UTC

Return-Path: <aaron@serendipity.cx>
X-Original-To: sieve@core3.amsl.com
Delivered-To: sieve@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50EAE3A6DE6 for <sieve@core3.amsl.com>; Thu, 4 Feb 2010 10:32:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.643
X-Spam-Level:
X-Spam-Status: No, score=-1.643 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ca0X-nr7pAmF for <sieve@core3.amsl.com>; Thu, 4 Feb 2010 10:32:54 -0800 (PST)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by core3.amsl.com (Postfix) with ESMTP id 7DA0B3A6DC0 for <sieve@ietf.org>; Thu, 4 Feb 2010 10:32:54 -0800 (PST)
Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by slice.serendipity.cx (Postfix) with ESMTPSA id 6DA971100FE for <sieve@ietf.org>; Thu, 4 Feb 2010 10:39:36 -0800 (PST)
Received: by pxi16 with SMTP id 16so285487pxi.29 for <sieve@ietf.org>; Thu, 04 Feb 2010 10:33:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.115.37.10 with SMTP id p10mr932928waj.179.1265308419143; Thu, 04 Feb 2010 10:33:39 -0800 (PST)
In-Reply-To: <6c9fcc2a1002040707m78bd7e52u344df0497d3e9c7a@mail.gmail.com>
References: <20100130143437.BBE563A683B@core3.amsl.com> <9abf48a61001300646g712fe589uceff1033063c71cd@mail.gmail.com> <4B6984EC.1040807@aegee.org> <4B6989FA.6080206@gulbrandsen.priv.no> <6c9fcc2a1002031318l3b5afddoa895e292fadb0ff6@mail.gmail.com> <01NJ8NX41PDW004042@mauve.mrochek.com> <6c9fcc2a1002040707m78bd7e52u344df0497d3e9c7a@mail.gmail.com>
From: Aaron Stone <aaron@serendipity.cx>
Date: Thu, 04 Feb 2010 10:33:19 -0800
Message-ID: <1629dc8c1002041033g4a2010c1i1cc5a9622d0220c0@mail.gmail.com>
To: barryleiba@computer.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Sieve mailing list <sieve@ietf.org>, Ned Freed <ned.freed@mrochek.com>
Subject: Re: [sieve] New Version Notification for draft-george-sieve-vacation-time-00
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 04 Feb 2010 18:32:55 -0000

On Thu, Feb 4, 2010 at 7:07 AM, Barry Leiba
<barryleiba.mailing.lists@gmail.com> wrote:
>> Well, the obvious existing model for this sort  of thing is spamtest and
>> spamtestplus. In that case specifying spamtestplus implicitly sets spamtest.
>> The rationale, as I recall, is that since spamtestplus makes no sense
>> without spamtest, why make the require clause even longer than it needs to be?
>>
>> if there's a reason not to follow that approach here I don't see it.
>
> OK, I'll buy that.  Good.  So for the next version:
>
> 1. I will change ":time" to ":seconds".

Personal comments:

Since Ned has :hours, and here we're talking about :seconds, why not
also add :minutes?

> 2. I will change "vacation-time" to "vacation-seconds".

Thought experiment: what if :time referred to a time of day? All
vacation notices would be batched and sent at that time of day. What
might be a use case for this?

> 3. I will add text saying that "vacation-seconds" implies "vacation",
> and that a script that includes "vacation-time" in the "require" list
> MAY omit "vacation" from the list.

+1

>>> The other question is if the working group will adopt this.  Should
>>> the updated version (changing "time" to "seconds") become
>>> draft-ietf-sieve-vacation-seconds-00 ?
>>
>> WFM.
>
> I'll hold off on updating the draft for a day or two, and if the
> chairs tell me that they have approved
> "draft-ietf-sieve-vacation-seconds" as a working group draft, I will
> submit it that way.  Otherwise, I'll submit an -01 version with the
> current name.

Chair's comment:
I'm in general favor of making it a WG document, but I'd like to think
out if there are more changes to vacation that anybody has in mind.
Should we open an "evacation" can of worms? (Probably not.) Should we
consider that a couple of vacation extensions might come together and
should be profiled as "vacation2" or something like that?

> Other comments from participants (or chairs)?

I like it!

Aaron