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

Barry Leiba <barryleiba.mailing.lists@gmail.com> Sat, 06 February 2010 20:45 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
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 5E7C33A6E0F for <sieve@core3.amsl.com>; Sat, 6 Feb 2010 12:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.907
X-Spam-Level:
X-Spam-Status: No, score=-2.907 tagged_above=-999 required=5 tests=[AWL=-0.308, BAYES_00=-2.599]
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 31FmWx3cN1kv for <sieve@core3.amsl.com>; Sat, 6 Feb 2010 12:45:48 -0800 (PST)
Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com [209.85.220.225]) by core3.amsl.com (Postfix) with ESMTP id 37BD13A6CD5 for <sieve@ietf.org>; Sat, 6 Feb 2010 12:45:48 -0800 (PST)
Received: by fxm25 with SMTP id 25so2434133fxm.32 for <sieve@ietf.org>; Sat, 06 Feb 2010 12:46:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=VLgEitaB55ipCd5wm8tAZtsOY/rUUjLv8E1PZrfjF9Y=; b=N39peVWs4wWKQmmXZBwlxpUkYl8VCHVjYfk6OyAxSMe4On0dbzHo0o1NTsVDwoLgMP OxYXd2MpnbisRSUbTYqvt+xh2LUSRwsoFN+xZRcLa7D3RHR3vmBVRcJCQD4rvrb8ogVB AClwZ4N7Nv+H+lN1jZdB+JgdoSJdd7q8iZrXo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=ntgpesKBj1Q5haleqUVZcmgjb9eim9nMQhRtgWHTifYAg9DpZXkobxncP/AF8yXVPn fpNaJlKfM2DPJnluRIsc0zzqt1ozPSnZsDSe5MHuOJ8BmWkIP/Y8vRAZ4+PFYlk0P/B6 jFNlDKXVFdx+00qzDU19Qkyh+Ikgpd0ic5T0s=
MIME-Version: 1.0
Received: by 10.223.101.148 with SMTP id c20mr270268fao.94.1265489200373; Sat, 06 Feb 2010 12:46:40 -0800 (PST)
In-Reply-To: <6c9fcc2a1002060852w4ac5bc24u9198632dd26dd6e8@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> <4B6D8963.3000508@aegee.org> <6c9fcc2a1002060852w4ac5bc24u9198632dd26dd6e8@mail.gmail.com>
Date: Sat, 06 Feb 2010 15:46:40 -0500
Message-ID: <6c9fcc2a1002061246o64383310wc7620271dfe00699@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Sieve mailing list <sieve@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
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
Reply-To: barryleiba@computer.org
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: Sat, 06 Feb 2010 20:45:49 -0000

To clarify, based on subsequent discussion:

> A few of us have already expressed preference for Arnt's text:
>
> "If the sieve processor recognises an address belonging to the sieve
> script's owner in the To or Cc fields, then it's better to use that
> address for the vacation reply than any other addresses the script
> owner may also have."
...
> I think we can submit that text as a clarification to the existing
> Vacation RFC, through the errata process.

Note that Arnt's text does not have any normative language, no 2119
words, in it.  I'm proposing that we add informative text, though an
erratum, that suggests a good way to determine what address to use.

Good implementations will take that into account.  But no one's saying
SHOULD or MUST, here.

Shall I submit an erratum against RFC 5230?  I'll appreciate a couple
of "+1", but in the absence of any "-1" I'll do it in a couple of
days.

Barry