IETF Logo Mail Archive

Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt

Aaron Stone <aaron@serendipity.cx> Wed, 10 October 2012 20:34 UTC

Return-Path: <aaron@serendipity.cx>
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 5087421F85A4 for <sieve@ietfa.amsl.com>; Wed, 10 Oct 2012 13:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.193
X-Spam-Level:
X-Spam-Status: No, score=-101.193 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_45=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HON4iUvK0JD2 for <sieve@ietfa.amsl.com>; Wed, 10 Oct 2012 13:34:17 -0700 (PDT)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 05E9421F859F for <sieve@ietf.org>; Wed, 10 Oct 2012 13:34:10 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id C9CD194002 for <sieve@ietf.org>; Wed, 10 Oct 2012 13:29:52 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so1110134pbb.31 for <sieve@ietf.org>; Wed, 10 Oct 2012 13:33:52 -0700 (PDT)
Received: by 10.68.213.1 with SMTP id no1mr60164803pbc.123.1349901232051; Wed, 10 Oct 2012 13:33:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.51.69 with HTTP; Wed, 10 Oct 2012 13:33:31 -0700 (PDT)
In-Reply-To: <5075D84B.8030007@rename-it.nl>
References: <20120915020634.9588.76361.idtracker@ietfa.amsl.com> <CAC4RtVDUxusjA-dG=-aQfpdWQ_qXKueOZF+qwzxiqLUQ7cf76A@mail.gmail.com> <5075D84B.8030007@rename-it.nl>
From: Aaron Stone <aaron@serendipity.cx>
Date: Wed, 10 Oct 2012 13:33:31 -0700
Message-ID: <CAEdAYKVtR+LvFfeYbcPeTC0HpT7DvCyFNHaQk1dJSfjDNBUFTg@mail.gmail.com>
To: Stephan Bosch <stephan@rename-it.nl>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Barry Leiba <barryleiba@computer.org>, sieve@ietf.org
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Wed, 10 Oct 2012 20:34:18 -0000

On Wed, Oct 10, 2012 at 1:19 PM, Stephan Bosch <stephan@rename-it.nl> wrote:
> On 9/15/2012 2:33 PM, Barry Leiba wrote:
>>
>> It looks like this is the final version that will go to the RFC
>> Editor.
>
>
> Just a question, how are we going to handle the approval of the following
> IMAP extension?
>
> https://tools.ietf.org/html/draft-ietf-imapmove-command-01
>
> Intuitively, I would say that adds a new imap.cause item called "MOVE" and I
> guess at some point this (or something else) would need to be documented.
> Would it still be possible for the editor to hammer it into the current
> yet-to-be-RFC imapsieve document if IMAP MOVE (somehow) makes it to RFC
> first?

IMAP Sieve is already in the Editor's Queue, so it's surely ahead of IMAP MOVE.

IMAP MOVE itself says that the command is equivalent to:
"""
   The UID MOVE command has the same effect as a sequence of UID COPY,
   UID STORE +FLAGS.SILENT \DELETED and UID EXPUNGE ...
"""

One could argue that "copy" is a viable value for imap.cause.

Aaron

v2.23.0 | Report a Bug | By Email