
From iesg-secretary@ietf.org  Thu Dec  1 08:22:15 2011
Return-Path: <iesg-secretary@ietf.org>
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 E2FEC11E825A; Thu,  1 Dec 2011 08:22:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAOKs6K+pX+X; Thu,  1 Dec 2011 08:22:14 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0F711E8287; Thu,  1 Dec 2011 08:21:59 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111201162159.1194.53589.idtracker@ietfa.amsl.com>
Date: Thu, 01 Dec 2011 08:21:59 -0800
Cc: sieve@ietf.org
Subject: [sieve] Last Call: <draft-ietf-sieve-include-13.txt> (Sieve Email Filtering:	Include Extension) to Proposed Standard
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Thu, 01 Dec 2011 16:22:16 -0000

The IESG has received a request from the Sieve Mail Filtering Language WG
(sieve) to consider the following document:
- 'Sieve Email Filtering: Include Extension'
  <draft-ietf-sieve-include-13.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-12-15. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The Sieve Email Filtering "include" extension permits users to
   include one Sieve script inside another.  This can make managing
   large scripts or multiple sets of scripts much easier, and allows a
   site and its users to build up libraries of scripts.  Users are able
   to include their own personal scripts or site-wide scripts.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-sieve-include/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-sieve-include/


No IPR declarations have been submitted directly on this I-D.



From internet-drafts@ietf.org  Thu Dec  1 09:43:42 2011
Return-Path: <internet-drafts@ietf.org>
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 F0BE91F0CAA; Thu,  1 Dec 2011 09:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zm0en5Rx1fVH; Thu,  1 Dec 2011 09:43:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9636A1F0C36; Thu,  1 Dec 2011 09:43:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111201174341.3962.4826.idtracker@ietfa.amsl.com>
Date: Thu, 01 Dec 2011 09:43:41 -0800
Cc: sieve@ietf.org
Subject: [sieve] I-D Action: draft-ietf-sieve-convert-06.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: Thu, 01 Dec 2011 17:43:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Sieve Mail Filtering Language Working=
 Group of the IETF.

	Title           : Sieve Extension for Converting Messages Before Delivery
	Author(s)       : Alexey Melnikov
                          Qian Sun
                          Barry Leiba
                          Kepeng Li
	Filename        : draft-ietf-sieve-convert-06.txt
	Pages           : 9
	Date            : 2011-12-01

   This document describes how the "CONVERT" IMAP extension can be used
   within the Sieve mail filtering language to transform messages before
   final delivery.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-convert-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-sieve-convert-06.txt


From iesg-secretary@ietf.org  Mon Dec  5 10:17:03 2011
Return-Path: <iesg-secretary@ietf.org>
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 5748611E80AD; Mon,  5 Dec 2011 10:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwaCecD6LyZQ; Mon,  5 Dec 2011 10:17:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A73BA11E80B1; Mon,  5 Dec 2011 10:17:02 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111205181702.7209.666.idtracker@ietfa.amsl.com>
Date: Mon, 05 Dec 2011 10:17:02 -0800
Cc: sieve mailing list <sieve@ietf.org>, sieve chair <sieve-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [sieve] Protocol Action: 'Sieve Extension for Converting Messages Before	Delivery' to Proposed Standard (draft-ietf-sieve-convert-06.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: Mon, 05 Dec 2011 18:17:03 -0000

The IESG has approved the following document:
- 'Sieve Extension for Converting Messages Before Delivery'
  (draft-ietf-sieve-convert-06.txt) as a Proposed Standard

This document is the product of the Sieve Mail Filtering Language Working
Group.

The IESG contact persons are Pete Resnick and Peter Saint-Andre.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-sieve-convert/




Technical Summary

   This document describes how IMAP CONVERT can be used within Sieve to
   transform messages before final delivery.

Working Group Summary

    This extension started as an individual submission in 2008 and was
    adopted as a WG document in 2010. The basic premise has remained the
    same throughout all revisions of the document.
	
    This extension adds a new combined action and test to SIEVE to allow
    message parts to be converted to other types during delivery. One new
    behavior here is that this extension creates a new combined test and
    action. This is something new for SIEVE (though allowed by the base
    spec), and implementors were explicitly asked to comment on whether this
    approach was viable - with a positive response. The document has not
    received any reviews from non-WG members. However, many of the existing
    WG members had participated in the Lemonade WG IMAP CONVERT work, on
    which the SIEVE convert extension is heavily based, so from that
    standpoint we do have review from existing IMAP implementors.

Document Quality

    There are no known implementations of this extension at present. Various
    vendors have expressed interest in implementing this extension, however
    it is not currently a top priority for any of them.

Personnel

    Document Shepherd: Cyrus Daboo <mailto:cyrus@daboo.name>
    AD: Pete Resnick <mailto:presnick@qualcomm.com>

From stephan@rename-it.nl  Mon Dec 12 04:11:18 2011
Return-Path: <stephan@rename-it.nl>
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 7923421F8B42 for <sieve@ietfa.amsl.com>; Mon, 12 Dec 2011 04:11:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VEYHuosr1zNo for <sieve@ietfa.amsl.com>; Mon, 12 Dec 2011 04:11:18 -0800 (PST)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id 0341521F8AFE for <sieve@ietf.org>; Mon, 12 Dec 2011 04:11:16 -0800 (PST)
Received: from wlan236250.mobiel.utwente.nl ([130.89.236.250]:50514) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <stephan@rename-it.nl>) id 1Ra4il-00031l-QG for sieve@ietf.org; Mon, 12 Dec 2011 13:11:14 +0100
Message-ID: <4EE5EF4C.1000000@rename-it.nl>
Date: Mon, 12 Dec 2011 13:10:52 +0100
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Sieve mailing list <sieve@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-RenameIT-MailScanner-SpamScore: -2.3 (--)
X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=ham version=3.3.1
Subject: [sieve] Sieve counterpart of IMAP SPECIAL-USE (RFC 6154) ?
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: Mon, 12 Dec 2011 12:11:18 -0000

Hi,

On an IMAP server mailing list I participated in a discussion about the 
new the IMAP LIST Extension for Special-Use Mailboxes (RFC 6154). In a 
nutshell, this extension allows identifying special-use mailboxes to an 
IMAP client. Special-use can for instance be a junk, trash, drafts, or 
archive folder. This way clients can easily identify such folders and 
use them without explicit user configuration.

At some point, the idea was raised to extend the Sieve language with 
similar means. It could for instance be useful to have a special version 
of the fileinto command that files the message into the default folder 
for a particular special-use, e.g. `fileinto :special_use "\\Junk";'. 
This can be particularly useful for global scripts outside the user's 
control. Through metadata support it is already possible to find out 
whether a folder has a special-use tag, but conversely it is not 
possible to find out which folders have a particular tag or what folder 
would be the default choice for that tag (note that the notion of a 
default folder for a particular special-use is missing in RFC 6154, 
which may be a problem).

My question is: do you think it is useful to have a Sieve SPECIAL-USE 
counterpart? And in what form?

Regards,

Stephan.

From NED+mta-filters@mauve.mrochek.com  Mon Dec 12 13:26:53 2011
Return-Path: <NED+mta-filters@mauve.mrochek.com>
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 1289621F85A8 for <sieve@ietfa.amsl.com>; Mon, 12 Dec 2011 13:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xS9Y3CJG23g for <sieve@ietfa.amsl.com>; Mon, 12 Dec 2011 13:26:52 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 933CE21F858C for <sieve@ietf.org>; Mon, 12 Dec 2011 13:26:52 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O9HYJ5009S013E3U@mauve.mrochek.com> for sieve@ietf.org; Mon, 12 Dec 2011 13:26:46 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O9HT6GDZVK00XZ16@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Mon, 12 Dec 2011 13:26:40 -0800 (PST)
From: NED+mta-filters@mauve.mrochek.com
Message-id: <01O9HYJ1V9LU00XZ16@mauve.mrochek.com>
Date: Mon, 12 Dec 2011 11:13:33 -0800 (PST)
In-reply-to: "Your message dated Mon, 12 Dec 2011 13:10:52 +0100" <4EE5EF4C.1000000@rename-it.nl>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <4EE5EF4C.1000000@rename-it.nl>
To: Stephan Bosch <stephan@rename-it.nl>
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Sieve counterpart of IMAP SPECIAL-USE (RFC 6154) ?
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: Mon, 12 Dec 2011 21:26:53 -0000

> Hi,

> On an IMAP server mailing list I participated in a discussion about the
> new the IMAP LIST Extension for Special-Use Mailboxes (RFC 6154). In a
> nutshell, this extension allows identifying special-use mailboxes to an
> IMAP client. Special-use can for instance be a junk, trash, drafts, or
> archive folder. This way clients can easily identify such folders and
> use them without explicit user configuration.

> At some point, the idea was raised to extend the Sieve language with
> similar means. It could for instance be useful to have a special version
> of the fileinto command that files the message into the default folder
> for a particular special-use, e.g. `fileinto :special_use "\\Junk";'.
> This can be particularly useful for global scripts outside the user's
> control. Through metadata support it is already possible to find out
> whether a folder has a special-use tag, but conversely it is not
> possible to find out which folders have a particular tag or what folder
> would be the default choice for that tag (note that the notion of a
> default folder for a particular special-use is missing in RFC 6154,
> which may be a problem).

> My question is: do you think it is useful to have a Sieve SPECIAL-USE
> counterpart? And in what form?

I asked around here at Oracle; everyone things this is a great idea and the
:special_use approach seems fine.

RFC 5228 already allows lots of flexibility in handling fileinto error
conditions, I suggest continuing that approach in handling special
use name failures. FWIW, our implementation fall back to INBOX delivery
when presented with a fileinto that's found to be problematic for some case.

				Ned

From alexey.melnikov@isode.com  Tue Dec 13 03:54:27 2011
Return-Path: <alexey.melnikov@isode.com>
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 1872F21F84FD for <sieve@ietfa.amsl.com>; Tue, 13 Dec 2011 03:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level: 
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oqAQk60LOW01 for <sieve@ietfa.amsl.com>; Tue, 13 Dec 2011 03:54:26 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 29B4021F84FB for <sieve@ietf.org>; Tue, 13 Dec 2011 03:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1323777265; d=isode.com; s=selector; i=@isode.com; bh=XmfCzXmu/b2CviWBdW6QXfGpvOVlvnFZ7s1u6wrAlSE=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=OVpj8ZCN2UVBE5Zq6gVk6NqYSe2yB8KZnRsh0/4nemHFYTzGhjR6Jr5t7SC+YGo4WdwUEj rO7HhNdw1FqeEpawhQW1ZUE4l9JM7p2+hoC755fJ/lNF/yNPVqi6dirSi98++xfNFJAqJ3 hMArgSyfOlVqlKnnoVKANI6d9JCLzxE=;
Received: from [192.168.1.144] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <Tuc88ABaKxK8@rufus.isode.com>; Tue, 13 Dec 2011 11:54:25 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4EE73CF0.3070406@isode.com>
Date: Tue, 13 Dec 2011 11:54:24 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Stephan Bosch <stephan@rename-it.nl>
References: <4EE5EF4C.1000000@rename-it.nl>
In-Reply-To: <4EE5EF4C.1000000@rename-it.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Sieve counterpart of IMAP SPECIAL-USE (RFC 6154) ?
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: Tue, 13 Dec 2011 11:54:27 -0000

On 12/12/2011 12:10, Stephan Bosch wrote:
> Hi,
Hi Stephan,
> On an IMAP server mailing list I participated in a discussion about 
> the new the IMAP LIST Extension for Special-Use Mailboxes (RFC 6154). 
> In a nutshell, this extension allows identifying special-use mailboxes 
> to an IMAP client. Special-use can for instance be a junk, trash, 
> drafts, or archive folder. This way clients can easily identify such 
> folders and use them without explicit user configuration.
>
> At some point, the idea was raised to extend the Sieve language with 
> similar means. It could for instance be useful to have a special 
> version of the fileinto command that files the message into the 
> default folder for a particular special-use, e.g. `fileinto 
> :special_use "\\Junk";'. This can be particularly useful for global 
> scripts outside the user's control. Through metadata support it is 
> already possible to find out whether a folder has a special-use tag, 
> but conversely it is not possible to find out which folders have a 
> particular tag or what folder would be the default choice for that tag 
> (note that the notion of a default folder for a particular special-use 
> is missing in RFC 6154, which may be a problem).
>
> My question is: do you think it is useful to have a Sieve SPECIAL-USE 
> counterpart? And in what form?
This looks interesting to me. Your proposal above looks fine to me.


From cyrus@daboo.name  Tue Dec 13 07:13:00 2011
Return-Path: <cyrus@daboo.name>
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 192E521F8B06 for <sieve@ietfa.amsl.com>; Tue, 13 Dec 2011 07:13:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0akqxA8KvkQV for <sieve@ietfa.amsl.com>; Tue, 13 Dec 2011 07:12:59 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 945EB21F8B02 for <sieve@ietf.org>; Tue, 13 Dec 2011 07:12:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id F37491E46CC6; Tue, 13 Dec 2011 10:12:57 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRw55K6GIoJi; Tue, 13 Dec 2011 10:12:56 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 971491E46CBB; Tue, 13 Dec 2011 10:12:55 -0500 (EST)
Date: Tue, 13 Dec 2011 10:12:52 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Stephan Bosch <stephan@rename-it.nl>
Message-ID: <233936B420638735B9E37ACC@caldav.corp.apple.com>
In-Reply-To: <4EE73CF0.3070406@isode.com>
References: <4EE5EF4C.1000000@rename-it.nl> <4EE73CF0.3070406@isode.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=930
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Sieve counterpart of IMAP SPECIAL-USE (RFC 6154) ?
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: Tue, 13 Dec 2011 15:13:00 -0000

Hi,

--On December 13, 2011 11:54:24 AM +0000 Alexey Melnikov 
<alexey.melnikov@isode.com> wrote:

>> My question is: do you think it is useful to have a Sieve SPECIAL-USE
>> counterpart? And in what form?
> This looks interesting to me. Your proposal above looks fine to me.

Individual Hat: +1. There might be one awkward part to this: RFC 6154 
introduces the concept of a "virtual mailbox", e.g., special use \Trash 
could be an aggregate of all messages in all mailboxes that have the 
\Deleted flag set. In that case a fileinto a virtual mailbox is not 
meaningful per se, but instead we would have to allow the sieve/imap system 
some latitude to do the right thing (i.e., for this example, apply the 
deleted flag and put the message somewhere appropriate - perhaps defaulting 
to inbox).

Chair Hat: Since SIEVE WG is not taking on any new work at this point, 
please make this an individual submission.

-- 
Cyrus Daboo


From aaron@serendipity.cx  Tue Dec 13 14:49:28 2011
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 DA28211E80AC; Tue, 13 Dec 2011 14:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.642
X-Spam-Level: 
X-Spam-Status: No, score=-101.642 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEn1IOOVSfX3; Tue, 13 Dec 2011 14:49:28 -0800 (PST)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 851E211E80A4; Tue, 13 Dec 2011 14:49:27 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id 0E25A11005F; Tue, 13 Dec 2011 14:47:27 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so163343vbb.31 for <multiple recipients>; Tue, 13 Dec 2011 14:49:23 -0800 (PST)
Received: by 10.52.29.75 with SMTP id i11mr2560614vdh.23.1323816563250; Tue, 13 Dec 2011 14:49:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.37.137 with HTTP; Tue, 13 Dec 2011 14:49:02 -0800 (PST)
In-Reply-To: <E02C28C0-E664-4197-9594-FB12EDA53F1E@nostrum.com>
References: <E02C28C0-E664-4197-9594-FB12EDA53F1E@nostrum.com>
From: Aaron Stone <aaron@serendipity.cx>
Date: Tue, 13 Dec 2011 14:49:02 -0800
Message-ID: <CAEdAYKWuHgqNE5NOLgsYUXAF0HgMEqEgKiPyGCjiAkF627XkMw@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=20cf307cfd4600150404b401102e
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, sieve@ietf.org
Subject: Re: [sieve] Gen-ART Last Call Review of draft-ietf-sieve-include-13
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: Tue, 13 Dec 2011 22:49:29 -0000

--20cf307cfd4600150404b401102e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Great comments, thank you!

Cheers,
Aaron


On Tue, Dec 13, 2011 at 2:13 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at <
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
> Document: draft-ietf-sieve-include-13
> Reviewer: Ben Campbell
> Review Date: 2011-12-13
> IETF LC End Date: 2011-12-15
>
> Summary: This draft is almost ready for publication as a proposed standar=
d
>
> Major issues:
>
> None
>
> Minor issues:
>
> -- section 3.1, paragraph 4: "Implementations MUST NOT generate errors fo=
r
> recursive inclusions at upload time, as this would force an upload orderi=
ng
> requirement upon script authors / generators.  However, if an active scri=
pt
> is replaced with a faulty script and would remain the active script, an
> error MUST be generated and the upload MUST fail."
>
> These two statements seem contradictory on a quick reading.  In
> particular, how can the latter assertion avoid an upload ordering
> requirement? Or do you mean faulty in some way other than being recursive=
?
>
> -- section 3.4.1, paragraph 5: "If a "global" command is given the name o=
f
> a variable that has previously been defined in the immediate script with
> "set", an error MUST be generated either when the script is uploaded or a=
t
> execution time."
>
> Does this conflict with the previous statement that it is okay for a
> global and a private variable to have the same name?
>
> -- section 3.4.2:
>
> Why do you need two ways to accomplish the same thing?
>
> Does the global namespace have the same "requires" requirement as the
> global command?
>
> -- section 4.2, paragraph 2:
>
> Can you elaborate on what permissions are proper? Is it different for an
> included script than for any other script?
>
> -- section 4.2, paragraph 3:
>
> Can you elaborate on what you mean by "safe for a storage system"?
>
> Nits/editorial comments:
>
> -- section 3.1, paragraph 4: "authors / generators"
>
> s/ "authors / generators " / "authors and generators"
>
> -- section 3.2, paragraph 9 (Top of page 6): "
> The included script MUST be a valid Sieve script.  Each script MUST
>   have its own "require" statements for all optional capabilities used
>   by that script. "
>
> Who do these normative statements apply to? As worded, it sounds like the=
y
> apply to the user. It might be better to say that the implementation MUST
> validate that=85
>
> -- section 3.4.2, paragraph 3: "Variables declared global and variables
> accessed via the global namespace MUST be one and the same."
>
> Plurality mismatch. I suggest something like "a variable declared as
> global and a variable accesses with the global namespace, otherwise havin=
g
> the same name=85"
>
> -- section 5:
>
> Please explicitly mention the name or URL of the registry table to which
> this should be added.
>
>
>

--20cf307cfd4600150404b401102e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Great comments, thank you!<div><br></div><div>Cheers,</div><div>Aaron</div>=
<div><br><br><div class=3D"gmail_quote">On Tue, Dec 13, 2011 at 2:13 PM, Be=
n Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com">ben@nos=
trum.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I am the assigned Gen-ART reviewer for this =
draft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br>


<br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br>
<br>
Document: draft-ietf-sieve-include-13<br>
Reviewer: Ben Campbell<br>
Review Date: 2011-12-13<br>
IETF LC End Date: 2011-12-15<br>
<br>
Summary: This draft is almost ready for publication as a proposed standard<=
br>
<br>
Major issues:<br>
<br>
None<br>
<br>
Minor issues:<br>
<br>
-- section 3.1, paragraph 4: &quot;Implementations MUST NOT generate errors=
 for recursive inclusions at upload time, as this would force an upload ord=
ering requirement upon script authors / generators. =A0However, if an activ=
e script is replaced with a faulty script and would remain the active scrip=
t, an error MUST be generated and the upload MUST fail.&quot;<br>


<br>
These two statements seem contradictory on a quick reading. =A0In particula=
r, how can the latter assertion avoid an upload ordering requirement? Or do=
 you mean faulty in some way other than being recursive?<br>
<br>
-- section 3.4.1, paragraph 5: &quot;If a &quot;global&quot; command is giv=
en the name of a variable that has previously been defined in the immediate=
 script with &quot;set&quot;, an error MUST be generated either when the sc=
ript is uploaded or at execution time.&quot;<br>


<br>
Does this conflict with the previous statement that it is okay for a global=
 and a private variable to have the same name?<br>
<br>
-- section 3.4.2:<br>
<br>
Why do you need two ways to accomplish the same thing?<br>
<br>
Does the global namespace have the same &quot;requires&quot; requirement as=
 the global command?<br>
<br>
-- section 4.2, paragraph 2:<br>
<br>
Can you elaborate on what permissions are proper? Is it different for an in=
cluded script than for any other script?<br>
<br>
-- section 4.2, paragraph 3:<br>
<br>
Can you elaborate on what you mean by &quot;safe for a storage system&quot;=
?<br>
<br>
Nits/editorial comments:<br>
<br>
-- section 3.1, paragraph 4: &quot;authors / generators&quot;<br>
<br>
s/ &quot;authors / generators &quot; / &quot;authors and generators&quot;<b=
r>
<br>
-- section 3.2, paragraph 9 (Top of page 6): &quot;<br>
The included script MUST be a valid Sieve script. =A0Each script MUST<br>
 =A0 have its own &quot;require&quot; statements for all optional capabilit=
ies used<br>
 =A0 by that script. &quot;<br>
<br>
Who do these normative statements apply to? As worded, it sounds like they =
apply to the user. It might be better to say that the implementation MUST v=
alidate that=85<br>
<br>
-- section 3.4.2, paragraph 3: &quot;Variables declared global and variable=
s accessed via the global namespace MUST be one and the same.&quot;<br>
<br>
Plurality mismatch. I suggest something like &quot;a variable declared as g=
lobal and a variable accesses with the global namespace, otherwise having t=
he same name=85&quot;<br>
<br>
-- section 5:<br>
<br>
Please explicitly mention the name or URL of the registry table to which th=
is should be added.<br>
<br>
<br>
</blockquote></div><br></div>

--20cf307cfd4600150404b401102e--

From ietf-ipr@ietf.org  Thu Dec 15 08:42:59 2011
Return-Path: <ietf-ipr@ietf.org>
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 E0CCE21F8AD2; Thu, 15 Dec 2011 08:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.357
X-Spam-Level: 
X-Spam-Status: No, score=-102.357 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oVKGIOouP0N1; Thu, 15 Dec 2011 08:42:59 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 542AC21F850E; Thu, 15 Dec 2011 08:42:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: alexey.melnikov@isode.com, sunqian@huawei.com, barryleiba@computer.org, likepeng@huawei.com, 
X-Test-IDTracker: no
Message-ID: <20111215164259.12810.39253.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2011 08:42:59 -0800
X-Mailman-Approved-At: Thu, 15 Dec 2011 08:55:34 -0800
Cc: presnick@qualcomm.com, sieve@ietf.org, ipr-announce@ietf.org
Subject: [sieve] IPR Disclosure: Huawei Technologies Co., Ltd's Statement about IPR related to	draft-ietf-sieve-notify-sip-message-08
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: Thu, 15 Dec 2011 16:43:00 -0000

Dear Alexey Melnikov, Qian Sun, Barry Leiba, Kepeng Li:

 An IPR disclosure that pertains to your Internet-Draft entitled "Sieve
Notification Mechanism: SIP MESSAGE" (draft-ietf-sieve-notify-sip-message) =
was
submitted to the IETF Secretariat on 2011-12-14 and has been posted on the =
"IETF
Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/1658/). The title of the IPR disclosure is
"Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-si=
eve-
notify-sip-message-08."");

The IETF Secretariat


From ietf-ipr@ietf.org  Thu Dec 15 08:44:04 2011
Return-Path: <ietf-ipr@ietf.org>
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 19A3021F8888; Thu, 15 Dec 2011 08:44:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.361
X-Spam-Level: 
X-Spam-Status: No, score=-102.361 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RApyzVs6fqPj; Thu, 15 Dec 2011 08:44:03 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F8F21F8591; Thu, 15 Dec 2011 08:44:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-ipr@ietf.org>
To: alexey.melnikov@isode.com, sunqian@huawei.com, barryleiba@computer.org, likepeng@huawei.com, 
X-Test-IDTracker: no
Message-ID: <20111215164403.12219.16403.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2011 08:44:03 -0800
X-Mailman-Approved-At: Thu, 15 Dec 2011 08:55:34 -0800
Cc: presnick@qualcomm.com, sieve@ietf.org, ipr-announce@ietf.org
Subject: [sieve] IPR Disclosure: Huawei Technologies Co., Ltd's Statement about IPR related to draft-ietf-sieve-convert-06
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: Thu, 15 Dec 2011 16:44:04 -0000

Dear Alexey Melnikov, Qian Sun, Barry Leiba, Kepeng Li:

 An IPR disclosure that pertains to your Internet-Draft entitled "Sieve
Extension for Converting Messages Before Delivery" (draft-ietf-sieve-conver=
t)
was submitted to the IETF Secretariat on 2011-12-14 and has been posted on =
the
"IETF Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/1657/). The title of the IPR disclosure is
"Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-si=
eve-
convert-06."");

The IETF Secretariat


From presnick@qualcomm.com  Thu Dec 15 13:29:24 2011
Return-Path: <presnick@qualcomm.com>
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 5427321F84C1 for <sieve@ietfa.amsl.com>; Thu, 15 Dec 2011 13:29:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level: 
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7uyK6OV8epBz for <sieve@ietfa.amsl.com>; Thu, 15 Dec 2011 13:29:23 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD2B21F84B2 for <sieve@ietf.org>; Thu, 15 Dec 2011 13:29:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1323984563; x=1355520563; h=message-id:date:from:user-agent:mime-version:to:subject: x-priority:content-type:content-transfer-encoding: x-originating-ip; z=Message-ID:=20<4EEA65E9.2050802@qualcomm.com>|Date:=20Th u,=2015=20Dec=202011=2015:26:01=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20SIEVE=20<sieve@ietf.org> |Subject:=20IPR=20Disclosures=20on=20draft-ietf-sieve-inc lude=20and=20draft-ietf-sieve-notify-sip-message |X-Priority:=202=20(High)|Content-Type:=20text/plain=3B =20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=RSXkzvvedrTc25lGxcCskHWW1yPgd0jnz4KLvEKJlRc=; b=SqGodQN99pPpYSpEJhNkSzbN50zNihNH2mIDrbgIoX92NRPffD4oN94S 5xIeQ2PRnTBzqvYm9+5vX1+xHXsJjjDEsEfr+egxH1XsLOgsck3Hwne+o r5D80WIusu4QnHM5nX3HS1JYxjhGFLvcasvEaaqLwgx5ah6ED4ENtvWwC 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,6561"; a="144885576"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 15 Dec 2011 13:29:15 -0800
X-IronPort-AV: E=Sophos;i="4.71,357,1320652800"; d="scan'208";a="219839913"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 15 Dec 2011 13:29:15 -0800
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Thu, 15 Dec 2011 13:26:03 -0800
Message-ID: <4EEA65E9.2050802@qualcomm.com>
Date: Thu, 15 Dec 2011 15:26:01 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: SIEVE <sieve@ietf.org>
X-Priority: 2 (High)
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Subject: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Thu, 15 Dec 2011 21:29:24 -0000

Folks,

As you have seen by now, the IETF has received 2 IPR disclosures, one 
regarding draft-ietf-sieve-convert and the other involving 
draft-ietf-sieve-notify-sip-message.

https://datatracker.ietf.org/ipr/1657/
https://datatracker.ietf.org/ipr/1658/


Unfortunately, we have been told that Qian Sun, one of the co-authors of 
the document, is the author of the patent in question, filed back in 
2008, and that he failed to disclose this at the time. I think this was 
pretty clearly a violation of RFC 3979, and the IESG will take up the 
question of what, if any, appropriate measures need to be taken because 
of that. Qian Sun is apparently no longer an active IETF participant, 
and his co-workers who are active IETF participants asked their company 
to disclose against the two documents as soon as they discovered what 
had happened. That's where were are now.

However, I did want to bring this to the attention of the working group 
and ask about the following:

Both of these drafts are already approved and in the RFC Editor queue. 
Right now, the RFC Editor has been asked to hold off publication for the 
moment until we decide the next steps. We could treat the IPR 
disclosures just as we would for any already published RFC (that is, we 
can simply say that it is out of our hands). However, since publication 
has not occurred, we can ask the RFC Editor to return the documents to 
the WG for further review, which as far as I can tell the RFC Editor 
always agrees to do. So, I ask that you all review the disclosures and 
ask the following question to the group:

After having reviewed the disclosures, does anyone in the WG wish to 
discuss the impact of these disclosures on the decision to publish these 
documents as they are? If so, I will likely ask the chairs to run a WGLC 
on the documents, and then I will run a new IETF Last Call with a 
pointer to the IPR disclosures. On the other hand, if there is *strong* 
consensus now on the list that it is fine go forward as-is, I will 
consider the matter settled and tell the RFC Editor to continue processing.

Please let us know what you think.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From barryleiba.mailing.lists@gmail.com  Sat Dec 17 12:38:37 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 03DDE21F850E for <sieve@ietfa.amsl.com>; Sat, 17 Dec 2011 12:38:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.996
X-Spam-Level: 
X-Spam-Status: No, score=-102.996 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wIy4Uyyw55+j for <sieve@ietfa.amsl.com>; Sat, 17 Dec 2011 12:38:36 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB8021F8441 for <sieve@ietf.org>; Sat, 17 Dec 2011 12:38:36 -0800 (PST)
Received: by yhjj72 with SMTP id j72so4155347yhj.31 for <sieve@ietf.org>; Sat, 17 Dec 2011 12:38:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=t1cgqoe16Nc4Rr+6MtlYGeq0RJRgMiXhzR2ITuuZLzY=; b=RPAfEPhM6dZtxQ8R4ro62VURSNI9gLzZk1mfM+Ki4RG6T09eHB1DhAmPMQo3BU+pdp rsB1m1YMsDZHsRK/rYWM6+VoHu215PTe4R6B+O9FPwqXy6FxjPZkAbILpA5bd2Rs5p8p fKXrTx2CvviWTNLt3aY6vwcJRdlHIR0SgIlDo=
MIME-Version: 1.0
Received: by 10.236.115.40 with SMTP id d28mr19645853yhh.37.1324154316051; Sat, 17 Dec 2011 12:38:36 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.146.225.26 with HTTP; Sat, 17 Dec 2011 12:38:35 -0800 (PST)
In-Reply-To: <4EEA65E9.2050802@qualcomm.com>
References: <4EEA65E9.2050802@qualcomm.com>
Date: Sat, 17 Dec 2011 15:38:35 -0500
X-Google-Sender-Auth: hJoUKrC6nj-tO5LkII2o7tjuM-Q
Message-ID: <CAC4RtVBYGkvmg5uqTTpG9i-+cipRMSCKTWfbj0=6ohSS7R+tOw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: SIEVE <sieve@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Sat, 17 Dec 2011 20:38:37 -0000

> As you have seen by now, the IETF has received 2 IPR disclosures, one
> regarding draft-ietf-sieve-convert and the other involving
> draft-ietf-sieve-notify-sip-message.
>
> https://datatracker.ietf.org/ipr/1657/
> https://datatracker.ietf.org/ipr/1658/
...
> Both of these drafts are already approved and in the RFC Editor queue. Right
> now, the RFC Editor has been asked to hold off publication for the moment
> until we decide the next steps. We could treat the IPR disclosures just as
> we would for any already published RFC (that is, we can simply say that it
> is out of our hands). However, since publication has not occurred, we can
> ask the RFC Editor to return the documents to the WG for further review,

I am, of course, not a lawyer, but as I read the terms, they don't
affect prospective implementations, and you need no license at all as
long as you don't want to assert your own patents back.  That's not to
say that this isn't annoying; it is, and I wish it hadn't happened.
It's just that I don't see it affecting any implementations of the
standard, which is what's most important here.

I'll also add that Huawei now has not just policies, but also active
procedures in place to do our best to make this not happen in future.
Our IETF participants are frequently reminded about the IETF IPR
policies, and there are people responsible for tracking things and
ensuring compliance.

In this case, I think that publishing these documents is the right
thing to do.  I think a working-group review is sufficient, and unless
WG participants particularly think we need to reach out to the
community at large for confirmation, we should just release the RFC Ed
hold on them after this consultation with the WG.

I'll add that the working group and the ADs need to have participants
speak up and say whether you think that's acceptable or not.  Silence
is not sufficient in this case.  Please tell us how you would like
this handled.

Barry

From alexey.melnikov@isode.com  Sat Dec 17 12:43:44 2011
Return-Path: <alexey.melnikov@isode.com>
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 E46DB21F84B3 for <sieve@ietfa.amsl.com>; Sat, 17 Dec 2011 12:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xchhlEcAisuW for <sieve@ietfa.amsl.com>; Sat, 17 Dec 2011 12:43:44 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id D8DCC21F84B0 for <sieve@ietf.org>; Sat, 17 Dec 2011 12:43:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1324154623; d=isode.com; s=selector; i=@isode.com; bh=sX0D3QuYpTM4G2AXu23t95KJFVj8CJ/4D7LbLnmKohI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=d2EgLfd5zUJF0kWDNe1SNZFgRrU0DAOH1GC60Vkteljc9apvfxPxiOfgshPVZecffQ7lzG SI9tfoMEIviKKU/XhPUfVgCgDssscS8Y+K55YUhUWyrJIP/KVIHxRxEkyGQFqdnId6WQ+P BtK92KH5PS0IL26+cnF9EMFjw36bIio=;
Received: from [188.28.202.132] (188.28.202.132.threembb.co.uk [188.28.202.132])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <Tuz-=QBaK5y2@rufus.isode.com>; Sat, 17 Dec 2011 20:43:42 +0000
Message-ID: <4EECFF05.8030303@isode.com>
Date: Sat, 17 Dec 2011 20:43:49 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Barry Leiba <barryleiba@computer.org>
References: <4EEA65E9.2050802@qualcomm.com> <CAC4RtVBYGkvmg5uqTTpG9i-+cipRMSCKTWfbj0=6ohSS7R+tOw@mail.gmail.com>
In-Reply-To: <CAC4RtVBYGkvmg5uqTTpG9i-+cipRMSCKTWfbj0=6ohSS7R+tOw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Sat, 17 Dec 2011 20:43:45 -0000

On 17/12/2011 20:38, Barry Leiba wrote:
>> As you have seen by now, the IETF has received 2 IPR disclosures, one
>> regarding draft-ietf-sieve-convert and the other involving
>> draft-ietf-sieve-notify-sip-message.
>>
>> https://datatracker.ietf.org/ipr/1657/
>> https://datatracker.ietf.org/ipr/1658/
> ...
>> Both of these drafts are already approved and in the RFC Editor queue. Right
>> now, the RFC Editor has been asked to hold off publication for the moment
>> until we decide the next steps. We could treat the IPR disclosures just as
>> we would for any already published RFC (that is, we can simply say that it
>> is out of our hands). However, since publication has not occurred, we can
>> ask the RFC Editor to return the documents to the WG for further review,
> I am, of course, not a lawyer, but as I read the terms, they don't
> affect prospective implementations, and you need no license at all as
> long as you don't want to assert your own patents back.  That's not to
> say that this isn't annoying; it is, and I wish it hadn't happened.
> It's just that I don't see it affecting any implementations of the
> standard, which is what's most important here.
>
> I'll also add that Huawei now has not just policies, but also active
> procedures in place to do our best to make this not happen in future.
> Our IETF participants are frequently reminded about the IETF IPR
> policies, and there are people responsible for tracking things and
> ensuring compliance.
>
> In this case, I think that publishing these documents is the right
> thing to do.  I think a working-group review is sufficient, and unless
> WG participants particularly think we need to reach out to the
> community at large for confirmation, we should just release the RFC Ed
> hold on them after this consultation with the WG.
>
> I'll add that the working group and the ADs need to have participants
> speak up and say whether you think that's acceptable or not.  Silence
> is not sufficient in this case.  Please tell us how you would like
> this handled.
I think we need at least WGLC. I think our responsible AD needs to 
decide whether to do IETF LC or not (I have no strong preference either 
way).


From alexey.melnikov@isode.com  Sat Dec 17 13:04:33 2011
Return-Path: <alexey.melnikov@isode.com>
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 B642421F86F6 for <sieve@ietfa.amsl.com>; Sat, 17 Dec 2011 13:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sjy4W301Oit2 for <sieve@ietfa.amsl.com>; Sat, 17 Dec 2011 13:04:33 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id A264721F86D0 for <sieve@ietf.org>; Sat, 17 Dec 2011 13:04:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1324155858; d=isode.com; s=selector; i=@isode.com; bh=33DO5trnSJbQpJRm6ZzFYVv+VkkeWUXNDOi/xIXm3lg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=OV/3V23pXTuCq6GpsoAEbMz3NtDsyu7j2i5jdIxDcGSl60b7n63JUrzFWtjPriQTksuevn aBbHgcxOYPs+IzyB3P+DB8gtcbkm4g3nSiyUmzFERfAaObyr9ibPQ/vqsBlTJp/Pe0sDNJ P5pLpsi1pfJAz9mHK4AhNKks88ZA/Ok=;
Received: from [188.28.202.132] (188.28.202.132.threembb.co.uk [188.28.202.132])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <Tu0D0ABaK7Az@rufus.isode.com>; Sat, 17 Dec 2011 21:04:17 +0000
Message-ID: <4EED03D9.9010305@isode.com>
Date: Sat, 17 Dec 2011 21:04:25 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Pete Resnick <presnick@qualcomm.com>
References: <4EEA65E9.2050802@qualcomm.com>
In-Reply-To: <4EEA65E9.2050802@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SIEVE <sieve@ietf.org>
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Sat, 17 Dec 2011 21:04:33 -0000

On 15/12/2011 21:26, Pete Resnick wrote:
> Folks,
>
> As you have seen by now, the IETF has received 2 IPR disclosures, one 
> regarding draft-ietf-sieve-convert and the other involving 
> draft-ietf-sieve-notify-sip-message.
I just want to point out that you made a typo in the subject line, but 
the above text is correct. An IPR declaration was filed on 
draft-ietf-sieve-convert and not draft-ietf-sieve-include.
>
> https://datatracker.ietf.org/ipr/1657/
> https://datatracker.ietf.org/ipr/1658/
>
>
> Unfortunately, we have been told that Qian Sun, one of the co-authors 
> of the document, is the author of the patent in question, filed back 
> in 2008, and that he failed to disclose this at the time. I think this 
> was pretty clearly a violation of RFC 3979, and the IESG will take up 
> the question of what, if any, appropriate measures need to be taken 
> because of that. Qian Sun is apparently no longer an active IETF 
> participant, and his co-workers who are active IETF participants asked 
> their company to disclose against the two documents as soon as they 
> discovered what had happened. That's where were are now.
>
> However, I did want to bring this to the attention of the working 
> group and ask about the following:
>
> Both of these drafts are already approved and in the RFC Editor queue. 
> Right now, the RFC Editor has been asked to hold off publication for 
> the moment until we decide the next steps. We could treat the IPR 
> disclosures just as we would for any already published RFC (that is, 
> we can simply say that it is out of our hands). However, since 
> publication has not occurred, we can ask the RFC Editor to return the 
> documents to the WG for further review, which as far as I can tell the 
> RFC Editor always agrees to do. So, I ask that you all review the 
> disclosures and ask the following question to the group:
>
> After having reviewed the disclosures, does anyone in the WG wish to 
> discuss the impact of these disclosures on the decision to publish 
> these documents as they are? If so, I will likely ask the chairs to 
> run a WGLC on the documents, and then I will run a new IETF Last Call 
> with a pointer to the IPR disclosures. On the other hand, if there is 
> *strong* consensus now on the list that it is fine go forward as-is, I 
> will consider the matter settled and tell the RFC Editor to continue 
> processing.
>
> Please let us know what you think.
>
> pr
>


From arnt@gulbrandsen.priv.no  Sun Dec 18 14:00:30 2011
Return-Path: <arnt@gulbrandsen.priv.no>
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 92D3B21F8B0F for <sieve@ietfa.amsl.com>; Sun, 18 Dec 2011 14:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2zEk0lZbLzHl for <sieve@ietfa.amsl.com>; Sun, 18 Dec 2011 14:00:30 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1383F21F8AFC for <sieve@ietf.org>; Sun, 18 Dec 2011 14:00:29 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 84D06FA00E0; Sun, 18 Dec 2011 22:00:26 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1324245624-93314-93313/8/122; Sun, 18 Dec 2011 23:00:24 +0100
Message-Id: <4EEE62D6.6090103@gulbrandsen.priv.no>
Date: Sun, 18 Dec 2011 23:01:58 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
Mime-Version: 1.0
To: sieve@ietf.org
References: <4EEA65E9.2050802@qualcomm.com>
In-Reply-To: <4EEA65E9.2050802@qualcomm.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Sun, 18 Dec 2011 22:00:30 -0000

What an unpleasant situation.

IMO, the documents can go forward as is, since there is a clear
assertion that the patents are defensive.

As I see it, there is no real difference between the mail Pete has
already sent and mail with subject "WGLC". "This needs WGLC" =E2=89=85 =
"strong
letter to follow".

Btw, I'd like to hear what procedures Huawei have instituted.

Arnt

From arnt@gulbrandsen.priv.no  Sun Dec 18 14:06:21 2011
Return-Path: <arnt@gulbrandsen.priv.no>
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 6E5E121F8B17 for <sieve@ietfa.amsl.com>; Sun, 18 Dec 2011 14:06:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X60xE0YHxAcB for <sieve@ietfa.amsl.com>; Sun, 18 Dec 2011 14:06:21 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id D878221F8B16 for <sieve@ietf.org>; Sun, 18 Dec 2011 14:06:20 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (kalyani.aox.org [79.140.39.164]) by strange.aox.org (Postfix) with ESMTP id 38985FA010A; Sun, 18 Dec 2011 22:06:20 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1324245979-93314-93313/8/123; Sun, 18 Dec 2011 23:06:19 +0100
Message-Id: <4EEE6439.7040209@gulbrandsen.priv.no>
Date: Sun, 18 Dec 2011 23:07:53 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
Mime-Version: 1.0
To: sieve@ietf.org
References: <4EEA65E9.2050802@qualcomm.com> <4EEE62D6.6090103@gulbrandsen.priv.no>
In-Reply-To: <4EEE62D6.6090103@gulbrandsen.priv.no>
Content-Type: text/plain; charset=utf-8
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Sun, 18 Dec 2011 22:06:21 -0000

But please allow another month or so to pass before publishing the RFCs.
Just in case someone's not reading mail and has something significant to
say.

Arnt

From cyrus@daboo.name  Sun Dec 18 18:23:06 2011
Return-Path: <cyrus@daboo.name>
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 2FA7421F8AF7 for <sieve@ietfa.amsl.com>; Sun, 18 Dec 2011 18:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJ8AWBWJiO1Y for <sieve@ietfa.amsl.com>; Sun, 18 Dec 2011 18:23:05 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id A48D521F8AF3 for <sieve@ietf.org>; Sun, 18 Dec 2011 18:23:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id ECBE11E8FC26; Sun, 18 Dec 2011 21:23:02 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VI-HXOp0M0jr; Sun, 18 Dec 2011 21:23:00 -0500 (EST)
Received: from [10.0.1.4] (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id D0E721E8FC12; Sun, 18 Dec 2011 21:22:59 -0500 (EST)
Date: Sun, 18 Dec 2011 21:23:00 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, sieve@ietf.org
Message-ID: <D38474A723269EB46ADD64F5@cyrus.local>
In-Reply-To: <4EEE6439.7040209@gulbrandsen.priv.no>
References: <4EEA65E9.2050802@qualcomm.com> <4EEE62D6.6090103@gulbrandsen.priv.no> <4EEE6439.7040209@gulbrandsen.priv.no>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=821
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Mon, 19 Dec 2011 02:23:06 -0000

Hi Arnt,

--On December 18, 2011 11:07:53 PM +0100 Arnt Gulbrandsen 
<arnt@gulbrandsen.priv.no> wrote:

> But please allow another month or so to pass before publishing the RFCs.
> Just in case someone's not reading mail and has something significant to
> say.

This is a legal matter that may require proper legal review be undertaken 
by implementers' organizations. Given the timing of this, with the upcoming 
holidays, and the fact that, in my experience, legal issues often take 
longer than one expects to be resolved, I do think we need to delay the 
documents sufficiently to account for that. My preference is for a last 
call that finishes at the end of January 2012. I don't mind whether that is 
a WG or IETF last call, though I am tempted to suggest this should go to 
the IETF as a whole.

-- 
Cyrus Daboo


From aaron@serendipity.cx  Mon Dec 19 08:18:50 2011
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 4FF4D21F88A0 for <sieve@ietfa.amsl.com>; Mon, 19 Dec 2011 08:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.737
X-Spam-Level: 
X-Spam-Status: No, score=-100.737 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_PBL=0.905, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKOVnROyLAci for <sieve@ietfa.amsl.com>; Mon, 19 Dec 2011 08:18:49 -0800 (PST)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id CB8D921F888A for <sieve@ietf.org>; Mon, 19 Dec 2011 08:18:49 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id 6A1F7110059 for <sieve@ietf.org>; Mon, 19 Dec 2011 08:16:42 -0800 (PST)
Received: by vbbfo1 with SMTP id fo1so3408626vbb.31 for <sieve@ietf.org>; Mon, 19 Dec 2011 08:18:45 -0800 (PST)
Received: by 10.52.110.2 with SMTP id hw2mr11883202vdb.18.1324311525299; Mon, 19 Dec 2011 08:18:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.29.72 with HTTP; Mon, 19 Dec 2011 08:12:01 -0800 (PST)
In-Reply-To: <D38474A723269EB46ADD64F5@cyrus.local>
References: <4EEA65E9.2050802@qualcomm.com> <4EEE62D6.6090103@gulbrandsen.priv.no> <4EEE6439.7040209@gulbrandsen.priv.no> <D38474A723269EB46ADD64F5@cyrus.local>
From: Aaron Stone <aaron@serendipity.cx>
Date: Mon, 19 Dec 2011 08:12:01 -0800
Message-ID: <CAEdAYKUnmyrmnA0jMiN5V=s_m9UB39B_pTN6fS0kz8TzEEAjpw@mail.gmail.com>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: multipart/alternative; boundary=bcaec548a47509962904b4744e96
Cc: sieve@ietf.org
Subject: Re: [sieve] IPR Disclosures on draft-ietf-sieve-include and draft-ietf-sieve-notify-sip-message
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: Mon, 19 Dec 2011 16:18:50 -0000

--bcaec548a47509962904b4744e96
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Dec 18, 2011 at 6:23 PM, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi Arnt,
>
>
> --On December 18, 2011 11:07:53 PM +0100 Arnt Gulbrandsen <
> arnt@gulbrandsen.priv.no> wrote:
>
>  But please allow another month or so to pass before publishing the RFCs.
>> Just in case someone's not reading mail and has something significant to
>> say.
>>
>
> This is a legal matter that may require proper legal review be undertaken
> by implementers' organizations. Given the timing of this, with the upcoming
> holidays, and the fact that, in my experience, legal issues often take
> longer than one expects to be resolved, I do think we need to delay the
> documents sufficiently to account for that. My preference is for a last
> call that finishes at the end of January 2012. I don't mind whether that is
> a WG or IETF last call, though I am tempted to suggest this should go to
> the IETF as a whole.


January sounds right to me, and I'm thinking an IETF LC is better. We'll
announce it of course on the WG list, but because the primary reason for
the call is a legal / organizational impact rather than a technical one, we
might not be as well equipped within the WG to comment with respect to the
layer 8 and 9 issues.

Cheers,
Aaron

--bcaec548a47509962904b4744e96
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Sun, Dec 18, 2011 at 6:23 PM, Cyrus D=
aboo <span dir=3D"ltr">&lt;<a href=3D"mailto:cyrus@daboo.name">cyrus@daboo.=
name</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hi Arnt,<div class=3D"im"><br>
<br>
--On December 18, 2011 11:07:53 PM +0100 Arnt Gulbrandsen &lt;<a href=3D"ma=
ilto:arnt@gulbrandsen.priv.no" target=3D"_blank">arnt@gulbrandsen.priv.no</=
a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
But please allow another month or so to pass before publishing the RFCs.<br=
>
Just in case someone&#39;s not reading mail and has something significant t=
o<br>
say.<br>
</blockquote>
<br></div>
This is a legal matter that may require proper legal review be undertaken b=
y implementers&#39; organizations. Given the timing of this, with the upcom=
ing holidays, and the fact that, in my experience, legal issues often take =
longer than one expects to be resolved, I do think we need to delay the doc=
uments sufficiently to account for that. My preference is for a last call t=
hat finishes at the end of January 2012. I don&#39;t mind whether that is a=
 WG or IETF last call, though I am tempted to suggest this should go to the=
 IETF as a whole.</blockquote>

<div><br></div><div>January sounds right to me, and I&#39;m thinking an IET=
F LC is better. We&#39;ll announce it of course on the WG list, but because=
 the primary reason for the call is a legal / organizational impact rather =
than a technical one, we might not be as well equipped within the WG to com=
ment with respect to the layer 8 and 9 issues.</div>

<div><br></div><div>Cheers,</div><div>Aaron</div></div>

--bcaec548a47509962904b4744e96--

From aaron@serendipity.cx  Mon Dec 19 09:05:05 2011
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 098331F0C47 for <sieve@ietfa.amsl.com>; Mon, 19 Dec 2011 09:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.737
X-Spam-Level: 
X-Spam-Status: No, score=-100.737 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_PBL=0.905, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MXML4L18bxeR for <sieve@ietfa.amsl.com>; Mon, 19 Dec 2011 09:05:04 -0800 (PST)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 34A3221F84CE for <sieve@ietf.org>; Mon, 19 Dec 2011 09:05:04 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id 364D1110059 for <sieve@ietf.org>; Mon, 19 Dec 2011 09:02:56 -0800 (PST)
Received: by vbbfo1 with SMTP id fo1so3458694vbb.31 for <sieve@ietf.org>; Mon, 19 Dec 2011 09:04:59 -0800 (PST)
Received: by 10.52.92.49 with SMTP id cj17mr12105197vdb.35.1324314299211; Mon, 19 Dec 2011 09:04:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.29.72 with HTTP; Mon, 19 Dec 2011 09:04:38 -0800 (PST)
In-Reply-To: <4E9C809D.90808@rename-it.nl>
References: <20110923192026.30531.70942.idtracker@ietfa.amsl.com> <4E7DDF5A.4060505@rename-it.nl> <CAEdAYKV+Kuys7mFbEJ7eq9YC_tpe02xT=43j2RKjrNaa9tSP2Q@mail.gmail.com> <4E9C809D.90808@rename-it.nl>
From: Aaron Stone <aaron@serendipity.cx>
Date: Mon, 19 Dec 2011 09:04:38 -0800
Message-ID: <CAEdAYKWSJy1_TQghiMd3FJWFz_F4CeAH2soXTuKG=fkW44CnBQ@mail.gmail.com>
To: Stephan Bosch <stephan@rename-it.nl>
Content-Type: multipart/alternative; boundary=20cf3071ce14601f2b04b474f35e
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-include-11.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: Mon, 19 Dec 2011 17:05:05 -0000

--20cf3071ce14601f2b04b474f35e
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Oct 17, 2011 at 12:23 PM, Stephan Bosch <stephan@rename-it.nl>wrote:

> On 9/27/2011 10:02 PM, Aaron Stone wrote:
>
>> On Sat, Sep 24, 2011 at 6:47 AM, Stephan Bosch<stephan@rename-it.nl>
>>  wrote:
>>
>>> So, from this I understand that the foreverypart context is passed down
>>> to
>>>
>>> any script included while in this context. This means that the behavior
>>> of
>>> the :mime-augmented tests in the included scripts is influenced
>>> accordingly.
>>>
>> I don't see why the context would be passed along, but I'll note
>> explicitly that it is not:
>>
>> OLD:
>> 255           The "include" command MAY appear anywhere in a script where
>> a
>> 256           control structure is legal, and MAY be used within another
>> control
>> 257           structure, e.g., within an "if" or "foreverypart" block
>> (<xref target='RFC5703'>MIME</xref>).
>>
>> NEW:
>> 255           The "include" command MAY appear anywhere in a script where
>> a
>> 256           control structure is legal, and MAY be used within another
>> control
>> 257           structure, e.g., within an "if" or "foreverypart" block
>> (<xref target='RFC5703'>MIME</xref>).
>> 258           The included script SHALL NOT have any special control over
>> the
>> 259           control structure it was included from, e.g., inclusion
>> from within a
>> 260           "foreverypart" block does not allow the included script
>> to directly
>> 261           terminate or continue flow of that block.
>>
>
> I've been pondering on this a little while. As it is now, this only solves
> part of the ambiguity imho. For instance in RFC 5703 Section 4.1 the
> following alternatives (amongst others) are described:
>
>   When used outside the context of a "foreverypart" iterator, and with
>   an ":anychild" tagged argument, the "header" test will examine all
>   MIME body parts and return true if any of them satisfies the test.
>
>   When used inside the context of a "foreverypart" iterator, and with
>   an ":anychild" tagged argument, the "header" test will examine the
>   current MIME part context and all its nested MIME body parts,
>   returning true if any of them satisfies the test.
>
> So, imagine the following situation.
>
> <toplevel>
> require "foreverypart";
> require "include";
>
> foreverypart {
>  if :mime :anychild "subject" "whatever" {
>     include "included";
>  }
> }
> </toplevel>
>
> <included>
> require "mime";
> require "fileinto";
>
> if header :mime :anychild :contenttype "Content-Type" "text/html"
> {
>  fileinto "INBOX.html";
> }
> </included>
>
> So, what does this do? Which of the two alternatives described above is
> used? Is the header test in the "included" script executed in the context
> of "foreverypart" in the "toplevel" script or not, i.e. is the foreverypart
> context passed down to included scripts? In my opinion, this is still bit
> ambiguous in the current wording. From your reply I infer that the context
> is not passed down, but perhaps the text should mention that explicitly. It
> is not only about the influence the includED script may have on the loop in
> the includING script, but also about the influence in the other direction.
>
>
My apologies for such a delayed reply. It took me a minute to get what you
were saying here -- you're correct that I was caught on the impact of the
included script on the including script, and I missed the question of
whether the including script can essentially set the scope of what the
included script sees as "the message" to actually be some inner MIME part,
without seeing the entire containing message.

I could see this being useful, and either way could be somewhat confusing
depending on what the user wants to do.

I was originally going to say, "no way, context is bad" but here are my two
arguments in favor of context:

RFC 5703 MIME Loops: I don't see a way to specify which MIME part another
piece of code should look at, which is kind of a bummer. Script A would not
be able to find some interesting mime part and then include script B with a
variable like "global.mime_part_to_look_at", where script B then grabs just
that part and does some useful transformation on it. So if you have a
script that makes a specific transformation, you have to set the context,
then call the script within that context.

RFC 5293 Edit Header: If a message is edited, it's edited. An included
script should see the edited message, not the original message. That means
the language already has some concept of context.

This may require a little bit of discussion! Anybody agree / disagree?

Aaron

--20cf3071ce14601f2b04b474f35e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Oct 17, 2011 at 12:23 PM, Stepha=
n Bosch <span dir=3D"ltr">&lt;<a href=3D"mailto:stephan@rename-it.nl">steph=
an@rename-it.nl</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"im">On 9/27/2011 10:02 PM, Aaron Stone wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im">
On Sat, Sep 24, 2011 at 6:47 AM, Stephan Bosch&lt;<a href=3D"mailto:stephan=
@rename-it.nl" target=3D"_blank">stephan@rename-it.nl</a>&gt; =A0wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
So, from this I understand that the foreverypart context is passed down to<=
div class=3D"im"><br>
any script included while in this context. This means that the behavior of<=
br>
the :mime-augmented tests in the included scripts is influenced accordingly=
.<br>
</div></blockquote><div class=3D"im">
I don&#39;t see why the context would be passed along, but I&#39;ll note<br=
>
explicitly that it is not:<br>
<br>
OLD:<br>
255 =A0 =A0 =A0 =A0 =A0 The &quot;include&quot; command MAY appear anywhere=
 in a script where a<br>
256 =A0 =A0 =A0 =A0 =A0 control structure is legal, and MAY be used within =
another control<br>
257 =A0 =A0 =A0 =A0 =A0 structure, e.g., within an &quot;if&quot; or &quot;=
foreverypart&quot; block<br>
(&lt;xref target=3D&#39;RFC5703&#39;&gt;MIME&lt;/xref&gt;).<br>
<br>
NEW:<br>
255 =A0 =A0 =A0 =A0 =A0 The &quot;include&quot; command MAY appear anywhere=
 in a script where a<br>
256 =A0 =A0 =A0 =A0 =A0 control structure is legal, and MAY be used within =
another control<br>
257 =A0 =A0 =A0 =A0 =A0 structure, e.g., within an &quot;if&quot; or &quot;=
foreverypart&quot; block<br>
(&lt;xref target=3D&#39;RFC5703&#39;&gt;MIME&lt;/xref&gt;).<br>
258 =A0 =A0 =A0 =A0 =A0 The included script SHALL NOT have any special cont=
rol over the<br>
259 =A0 =A0 =A0 =A0 =A0 control structure it was included from, e.g., inclu=
sion<br>
from within a<br>
260 =A0 =A0 =A0 =A0 =A0 &quot;foreverypart&quot; block does not allow the i=
ncluded script<br>
to directly<br>
261 =A0 =A0 =A0 =A0 =A0 terminate or continue flow of that block.<br>
</div></blockquote>
<br>
I&#39;ve been pondering on this a little while. As it is now, this only sol=
ves part of the ambiguity imho. For instance in RFC 5703 Section 4.1 the fo=
llowing alternatives (amongst others) are described:<br>
<br>
 =A0 When used outside the context of a &quot;foreverypart&quot; iterator, =
and with<br>
 =A0 an &quot;:anychild&quot; tagged argument, the &quot;header&quot; test =
will examine all<br>
 =A0 MIME body parts and return true if any of them satisfies the test.<br>
<br>
 =A0 When used inside the context of a &quot;foreverypart&quot; iterator, a=
nd with<br>
 =A0 an &quot;:anychild&quot; tagged argument, the &quot;header&quot; test =
will examine the<br>
 =A0 current MIME part context and all its nested MIME body parts,<br>
 =A0 returning true if any of them satisfies the test.<br>
<br>
So, imagine the following situation.<br>
<br>
&lt;toplevel&gt;<br>
require &quot;foreverypart&quot;;<br>
require &quot;include&quot;;<br>
<br>
foreverypart {<br>
 =A0if :mime :anychild &quot;subject&quot; &quot;whatever&quot; {<br>
 =A0 =A0 include &quot;included&quot;;<br>
 =A0}<br>
}<br>
&lt;/toplevel&gt;<br>
<br>
&lt;included&gt;<br>
require &quot;mime&quot;;<br>
require &quot;fileinto&quot;;<br>
<br>
if header :mime :anychild :contenttype &quot;Content-Type&quot; &quot;text/=
html&quot;<br>
{<br>
 =A0fileinto &quot;INBOX.html&quot;;<br>
}<br>
&lt;/included&gt;<br>
<br>
So, what does this do? Which of the two alternatives described above is use=
d? Is the header test in the &quot;included&quot; script executed in the co=
ntext of &quot;foreverypart&quot; in the &quot;toplevel&quot; script or not=
, i.e. is the foreverypart context passed down to included scripts? In my o=
pinion, this is still bit ambiguous in the current wording. From your reply=
 I infer that the context is not passed down, but perhaps the text should m=
ention that explicitly. It is not only about the influence the includED scr=
ipt may have on the loop in the includING script, but also about the influe=
nce in the other direction.<br>

<br></blockquote><div><br></div><div>My apologies for such a delayed reply.=
 It took me a minute to get what you were saying here -- you&#39;re correct=
 that I was caught on the impact of the included script on the including sc=
ript, and I missed the question of whether the including script can essenti=
ally set the scope of what the included script sees as &quot;the message&qu=
ot; to actually be some inner MIME part, without seeing the entire containi=
ng message.</div>

<div></div></div><br><div>I could see this being useful, and either way cou=
ld be somewhat confusing depending on what the user wants to do.</div><div>=
<br></div><div>I was originally going to say, &quot;no way, context is bad&=
quot; but here are my two arguments in favor of context:</div>

<div><br></div><div>RFC 5703 MIME Loops: I don&#39;t see a way to specify w=
hich MIME part another piece of code should look at, which is kind of a bum=
mer. Script A would not be able to find some interesting mime part and then=
 include script B with a variable like &quot;global.mime_part_to_look_at&qu=
ot;, where script B then grabs just that part and does some useful transfor=
mation on it. So if you have a script that makes a specific transformation,=
 you have to set the context, then call the script within that context.</di=
v>

<div><br></div><div>RFC 5293 Edit Header: If a message is edited, it&#39;s =
edited. An included script should see the edited message, not the original =
message. That means the language already has some concept of context.</div>

<div><br></div><div>This may require a little bit of discussion! Anybody ag=
ree / disagree?</div><div><br></div><div>Aaron</div>

--20cf3071ce14601f2b04b474f35e--

From aaron@serendipity.cx  Mon Dec 19 11:14:03 2011
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 15AC111E8097; Mon, 19 Dec 2011 11:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.189
X-Spam-Level: 
X-Spam-Status: No, score=-101.189 tagged_above=-999 required=5 tests=[AWL=0.452, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LUi8ADENp4P; Mon, 19 Dec 2011 11:14:02 -0800 (PST)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDC511E8081; Mon, 19 Dec 2011 11:14:02 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by slice.serendipity.cx (Postfix) with ESMTPSA id 3293F110068; Mon, 19 Dec 2011 11:11:54 -0800 (PST)
Received: by vcbfk13 with SMTP id fk13so4452058vcb.31 for <multiple recipients>; Mon, 19 Dec 2011 11:13:57 -0800 (PST)
Received: by 10.220.152.78 with SMTP id f14mr11601933vcw.30.1324322037235; Mon, 19 Dec 2011 11:13:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.29.72 with HTTP; Mon, 19 Dec 2011 11:13:35 -0800 (PST)
In-Reply-To: <E02C28C0-E664-4197-9594-FB12EDA53F1E@nostrum.com>
References: <E02C28C0-E664-4197-9594-FB12EDA53F1E@nostrum.com>
From: Aaron Stone <aaron@serendipity.cx>
Date: Mon, 19 Dec 2011 11:13:35 -0800
Message-ID: <CAEdAYKU7FrmRA0agwW0ux60VVhHGE9Dc_0hdj+TRPLW9DxFRLg@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>, Sieve mailing list <sieve@ietf.org>
Content-Type: multipart/alternative; boundary=f46d043c7b009900ac04b476c0b3
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Subject: Re: [sieve] Gen-ART Last Call Review of draft-ietf-sieve-include-13
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: Mon, 19 Dec 2011 19:14:03 -0000

--f46d043c7b009900ac04b476c0b3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 13, 2011 at 2:13 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at <
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
> Document: draft-ietf-sieve-include-13
> Reviewer: Ben Campbell
> Review Date: 2011-12-13
> IETF LC End Date: 2011-12-15
>
> Summary: This draft is almost ready for publication as a proposed standar=
d
>
> Major issues:
>
> None
>
> Minor issues:
>
> -- section 3.1, paragraph 4: "Implementations MUST NOT generate errors fo=
r
> recursive inclusions at upload time, as this would force an upload orderi=
ng
> requirement upon script authors / generators.  However, if an active scri=
pt
> is replaced with a faulty script and would remain the active script, an
> error MUST be generated and the upload MUST fail."
>
> These two statements seem contradictory on a quick reading.  In
> particular, how can the latter assertion avoid an upload ordering
> requirement? Or do you mean faulty in some way other than being recursive=
?
>

If you're replacing an active script, it has to be correct all the time,
and uploads are atomic only on a per-script basis. There's a risk that if
you're uploading a set of scripts that include one another, at some
intermediate stage while some scripts are uploaded but not others, they are
in an invalid state. The managesieve spec says that scripts must be
validated at upload time. The language above is trying to say that you can
upload all of the scripts that may include one another in any order without
generating errors immediately, however, if you're replacing an active
script or a script included by the active script, then you DO have to
upload a correct script right from the get-go.


> -- section 3.4.1, paragraph 5: "If a "global" command is given the name o=
f
> a variable that has previously been defined in the immediate script with
> "set", an error MUST be generated either when the script is uploaded or a=
t
> execution time."
>
> Does this conflict with the previous statement that it is okay for a
> global and a private variable to have the same name?
>

It doesn't conflict, because those variables live in separate namespaces.
The effect of the global command is to bind the two names. An error is
generated rather than specifying if the local overwrites the global value,
or the global overwrites the local value.


> -- section 3.4.2:
>
> Why do you need two ways to accomplish the same thing?
>

I might be making this up, but I think the original question was whether
the variables spec would have namespaces.


> Does the global namespace have the same "requires" requirement as the
> global command?
>

Yes, but this isn't explicitly stated.


> -- section 4.2, paragraph 2:
>
> Can you elaborate on what permissions are proper? Is it different for an
> included script than for any other script?
>
> -- section 4.2, paragraph 3:
>
> Can you elaborate on what you mean by "safe for a storage system"?
>
>
There are both somewhat vague warnings, basically, "Don't allow 'include
"./../..//etc/passwd"' and don't allow 'include "foo$(`rm star`)"'.


> Nits/editorial comments:
>
> -- section 3.1, paragraph 4: "authors / generators"
>
> s/ "authors / generators " / "authors and generators"
>

Ok.


> -- section 3.2, paragraph 9 (Top of page 6): "
> The included script MUST be a valid Sieve script.  Each script MUST
>   have its own "require" statements for all optional capabilities used
>   by that script. "
>
> Who do these normative statements apply to? As worded, it sounds like the=
y
> apply to the user. It might be better to say that the implementation MUST
> validate that=85
>

Ok.


> -- section 3.4.2, paragraph 3: "Variables declared global and variables
> accessed via the global namespace MUST be one and the same."
>
> Plurality mismatch. I suggest something like "a variable declared as
> global and a variable accesses with the global namespace, otherwise havin=
g
> the same name=85"
>

I might insert the word "each" after MUST to account for the plurality
without rewriting the sentence.


> -- section 5:
>
> Please explicitly mention the name or URL of the registry table to which
> this should be added.
>

Good catch, thank you.

Cheers,
Aaron

--f46d043c7b009900ac04b476c0b3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Dec 13, 2011 at 2:13 PM, Ben Cam=
pbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_b=
lank">ben@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">


I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</a>&gt;.<br>



<br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br>
<br>
Document: draft-ietf-sieve-include-13<br>
Reviewer: Ben Campbell<br>
Review Date: 2011-12-13<br>
IETF LC End Date: 2011-12-15<br>
<br>
Summary: This draft is almost ready for publication as a proposed standard<=
br>
<br>
Major issues:<br>
<br>
None<br>
<br>
Minor issues:<br>
<br>
-- section 3.1, paragraph 4: &quot;Implementations MUST NOT generate errors=
 for recursive inclusions at upload time, as this would force an upload ord=
ering requirement upon script authors / generators. =A0However, if an activ=
e script is replaced with a faulty script and would remain the active scrip=
t, an error MUST be generated and the upload MUST fail.&quot;<br>



<br>
These two statements seem contradictory on a quick reading. =A0In particula=
r, how can the latter assertion avoid an upload ordering requirement? Or do=
 you mean faulty in some way other than being recursive?<br></blockquote>

<div><br></div><div>If you&#39;re replacing an active script, it has to be =
correct all the time, and uploads are atomic only on a per-script basis. Th=
ere&#39;s a risk that if you&#39;re uploading a set of scripts that include=
 one another, at some intermediate stage while some scripts are uploaded bu=
t not others, they are in an invalid state. The managesieve spec says that =
scripts must be validated at upload time. The language above is trying to s=
ay that you can upload all of the scripts that may include one another in a=
ny order without generating errors immediately, however, if you&#39;re repl=
acing an active script or a script included by the active script, then you =
DO have to upload a correct script right from the get-go.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
-- section 3.4.1, paragraph 5: &quot;If a &quot;global&quot; command is giv=
en the name of a variable that has previously been defined in the immediate=
 script with &quot;set&quot;, an error MUST be generated either when the sc=
ript is uploaded or at execution time.&quot;<br>



<br>
Does this conflict with the previous statement that it is okay for a global=
 and a private variable to have the same name?<br></blockquote><div><br></d=
iv><div>It doesn&#39;t conflict, because those variables live in separate n=
amespaces. The effect of the global command is to bind the two names. An er=
ror is generated rather than specifying if the local overwrites the global =
value, or the global overwrites the local value.</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
-- section 3.4.2:<br>
<br>
Why do you need two ways to accomplish the same thing?<br></blockquote><div=
><br></div><div>I might be making this up, but I think the original questio=
n was whether the variables spec would have namespaces.</div><div>=A0</div>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Does the global namespace have the same &quot;requires&quot; requirement as=
 the global command?<br></blockquote><div><br></div><div>Yes, but this isn&=
#39;t explicitly stated.</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


-- section 4.2, paragraph 2:<br>
<br>
Can you elaborate on what permissions are proper? Is it different for an in=
cluded script than for any other script?<br>
<br>
-- section 4.2, paragraph 3:<br>
<br>
Can you elaborate on what you mean by &quot;safe for a storage system&quot;=
?<br>
<br></blockquote><div><br></div><div>There are both somewhat vague warnings=
, basically, &quot;Don&#39;t allow &#39;include &quot;./../..//etc/passwd&q=
uot;&#39; and don&#39;t allow &#39;include &quot;foo$(`rm star`)&quot;&#39;=
.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
Nits/editorial comments:<br>
<br>
-- section 3.1, paragraph 4: &quot;authors / generators&quot;<br>
<br>
s/ &quot;authors / generators &quot; / &quot;authors and generators&quot;<b=
r></blockquote><div><br></div><div>Ok.</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">


-- section 3.2, paragraph 9 (Top of page 6): &quot;<br>
The included script MUST be a valid Sieve script. =A0Each script MUST<br>
 =A0 have its own &quot;require&quot; statements for all optional capabilit=
ies used<br>
 =A0 by that script. &quot;<br>
<br>
Who do these normative statements apply to? As worded, it sounds like they =
apply to the user. It might be better to say that the implementation MUST v=
alidate that=85<br></blockquote><div><br></div><div>Ok.</div><div>=A0</div>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
-- section 3.4.2, paragraph 3: &quot;Variables declared global and variable=
s accessed via the global namespace MUST be one and the same.&quot;<br>
<br>
Plurality mismatch. I suggest something like &quot;a variable declared as g=
lobal and a variable accesses with the global namespace, otherwise having t=
he same name=85&quot;<br></blockquote><div><br></div><div>I might insert th=
e word &quot;each&quot; after MUST to account for the plurality without rew=
riting the sentence.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
-- section 5:<br>
<br>
Please explicitly mention the name or URL of the registry table to which th=
is should be added.<br></blockquote><div><br></div><div>Good catch, thank y=
ou.</div><div><br></div><div>Cheers,</div><div>Aaron=A0</div></div>

--f46d043c7b009900ac04b476c0b3--

From aaron@serendipity.cx  Mon Dec 19 11:23:32 2011
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 5766511E809D for <sieve@ietfa.amsl.com>; Mon, 19 Dec 2011 11:23:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.763
X-Spam-Level: 
X-Spam-Status: No, score=-99.763 tagged_above=-999 required=5 tests=[AWL=-1.276, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAZ+ClqOhQlH for <sieve@ietfa.amsl.com>; Mon, 19 Dec 2011 11:23:31 -0800 (PST)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id BA33A11E8081 for <sieve@ietf.org>; Mon, 19 Dec 2011 11:23:31 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by slice.serendipity.cx (Postfix) with ESMTPSA id 9A5EC110068 for <sieve@ietf.org>; Mon, 19 Dec 2011 11:21:23 -0800 (PST)
Received: by vcbfk13 with SMTP id fk13so4460760vcb.31 for <sieve@ietf.org>; Mon, 19 Dec 2011 11:23:26 -0800 (PST)
Received: by 10.220.39.9 with SMTP id d9mr11637315vce.10.1324322606771; Mon, 19 Dec 2011 11:23:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.29.72 with HTTP; Mon, 19 Dec 2011 11:23:05 -0800 (PST)
In-Reply-To: <4EE5EF4C.1000000@rename-it.nl>
References: <4EE5EF4C.1000000@rename-it.nl>
From: Aaron Stone <aaron@serendipity.cx>
Date: Mon, 19 Dec 2011 11:23:05 -0800
Message-ID: <CAEdAYKX7S7i-KQuc_eW7W=6qW=U4bOK3BKmMqPvhupv4XO0PdA@mail.gmail.com>
To: Stephan Bosch <stephan@rename-it.nl>
Content-Type: multipart/alternative; boundary=bcaec54ee7788b6d8a04b476e212
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Sieve counterpart of IMAP SPECIAL-USE (RFC 6154) ?
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: Mon, 19 Dec 2011 19:23:32 -0000

--bcaec54ee7788b6d8a04b476e212
Content-Type: text/plain; charset=ISO-8859-1

No kidding, I remember arguing to do exactly this kind of IMAP extension
years ago! As I recall, everyone said things to the effect of "You don't
want special folders, Mark doesn't like that idea much."

... though I might have been arguing for both special folders, "\Trash" as
well as magic folders, "\Outbox"... :)

Personal hat: I generally like but don't love the idea. If I were the
implementor, I'd already have a set of magic folder names, and fileinto
"Magic Name" would do as you're suggesting.

Anyhow, as Cyrus points out, an individual submission would be best, since
the WG is running slow lately and we should be wrapping it up.

Cheers,
Aaron

On Mon, Dec 12, 2011 at 4:10 AM, Stephan Bosch <stephan@rename-it.nl> wrote:

> Hi,
>
> On an IMAP server mailing list I participated in a discussion about the
> new the IMAP LIST Extension for Special-Use Mailboxes (RFC 6154). In a
> nutshell, this extension allows identifying special-use mailboxes to an
> IMAP client. Special-use can for instance be a junk, trash, drafts, or
> archive folder. This way clients can easily identify such folders and use
> them without explicit user configuration.
>
> At some point, the idea was raised to extend the Sieve language with
> similar means. It could for instance be useful to have a special version of
> the fileinto command that files the message into the default folder for a
> particular special-use, e.g. `fileinto :special_use "\\Junk";'. This can be
> particularly useful for global scripts outside the user's control. Through
> metadata support it is already possible to find out whether a folder has a
> special-use tag, but conversely it is not possible to find out which
> folders have a particular tag or what folder would be the default choice
> for that tag (note that the notion of a default folder for a particular
> special-use is missing in RFC 6154, which may be a problem).
>
> My question is: do you think it is useful to have a Sieve SPECIAL-USE
> counterpart? And in what form?
>
> Regards,
>
> Stephan.
> ______________________________**_________________
> sieve mailing list
> sieve@ietf.org
> https://www.ietf.org/mailman/**listinfo/sieve<https://www.ietf.org/mailman/listinfo/sieve>
>

--bcaec54ee7788b6d8a04b476e212
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

No kidding, I remember arguing to do exactly this kind of IMAP extension ye=
ars ago! As I recall, everyone said things to the effect of &quot;You don&#=
39;t want special folders, Mark doesn&#39;t like that idea much.&quot;<div>

<br></div><div>... though I might have been arguing for both special folder=
s, &quot;\Trash&quot; as well as magic folders, &quot;\Outbox&quot;... :)</=
div><div><br></div><div>Personal hat: I generally like but don&#39;t love t=
he idea. If I were the implementor, I&#39;d already have a set of magic fol=
der names, and fileinto &quot;Magic Name&quot; would do as you&#39;re sugge=
sting.</div>

<div><br></div><div>Anyhow, as Cyrus points out, an individual submission w=
ould be best, since the WG is running slow lately and we should be wrapping=
 it up.</div><div><br></div><div>Cheers,</div><div>Aaron<br><br><div class=
=3D"gmail_quote">

On Mon, Dec 12, 2011 at 4:10 AM, Stephan Bosch <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:stephan@rename-it.nl">stephan@rename-it.nl</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">

Hi,<br>
<br>
On an IMAP server mailing list I participated in a discussion about the new=
 the IMAP LIST Extension for Special-Use Mailboxes (RFC 6154). In a nutshel=
l, this extension allows identifying special-use mailboxes to an IMAP clien=
t. Special-use can for instance be a junk, trash, drafts, or archive folder=
. This way clients can easily identify such folders and use them without ex=
plicit user configuration.<br>


<br>
At some point, the idea was raised to extend the Sieve language with simila=
r means. It could for instance be useful to have a special version of the f=
ileinto command that files the message into the default folder for a partic=
ular special-use, e.g. `fileinto :special_use &quot;\\Junk&quot;;&#39;. Thi=
s can be particularly useful for global scripts outside the user&#39;s cont=
rol. Through metadata support it is already possible to find out whether a =
folder has a special-use tag, but conversely it is not possible to find out=
 which folders have a particular tag or what folder would be the default ch=
oice for that tag (note that the notion of a default folder for a particula=
r special-use is missing in RFC 6154, which may be a problem).<br>


<br>
My question is: do you think it is useful to have a Sieve SPECIAL-USE count=
erpart? And in what form?<br>
<br>
Regards,<br>
<br>
Stephan.<br>
______________________________<u></u>_________________<br>
sieve mailing list<br>
<a href=3D"mailto:sieve@ietf.org" target=3D"_blank">sieve@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sieve" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/sieve</a><br>
</blockquote></div><br></div>

--bcaec54ee7788b6d8a04b476e212--

From alexey.melnikov@isode.com  Mon Dec 19 12:01:29 2011
Return-Path: <alexey.melnikov@isode.com>
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 96C3D11E80BC; Mon, 19 Dec 2011 12:01:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[AWL=0.698,  BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5THf3nXsWME; Mon, 19 Dec 2011 12:01:25 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id EF84B11E809D; Mon, 19 Dec 2011 12:01:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1324324884; d=isode.com; s=selector; i=@isode.com; bh=3ZvYvMPoJZDHozVqUBOr4Crmw1+9qY2yyw+iK8J5bho=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=t6luZywtOYqPvKx/YeA12X6rZ9W9Q2tyBbOqjCgJscMFaVR2yaVkuDp8blfC8rRAn9lk9v wkUwHJKaMChGhfmtHVSKLK79tyfsBl/3Hd5GWuluJVSuSJv/pyO7ie6/wDWjgc9Ie/fBQX 6VWWrSLUh4fZBraKURvzHbhoYYmpYTE=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <Tu-YEgB5QEZ5@rufus.isode.com>; Mon, 19 Dec 2011 20:01:23 +0000
Message-ID: <4EEF981F.1090905@isode.com>
Date: Mon, 19 Dec 2011 20:01:35 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Aaron Stone <aaron@serendipity.cx>
References: <E02C28C0-E664-4197-9594-FB12EDA53F1E@nostrum.com> <CAEdAYKU7FrmRA0agwW0ux60VVhHGE9Dc_0hdj+TRPLW9DxFRLg@mail.gmail.com>
In-Reply-To: <CAEdAYKU7FrmRA0agwW0ux60VVhHGE9Dc_0hdj+TRPLW9DxFRLg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------010601070103030800070603"
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Gen-ART Last Call Review of draft-ietf-sieve-include-13
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: Mon, 19 Dec 2011 20:01:29 -0000

This is a multi-part message in MIME format.
--------------010601070103030800070603
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Aaron,

On 19/12/2011 19:13, Aaron Stone wrote:
> On Tue, Dec 13, 2011 at 2:13 PM, Ben Campbell <ben@nostrum.com 
> <mailto:ben@nostrum.com>> wrote:
>
>     I am the assigned Gen-ART reviewer for this draft. For background
>     on Gen-ART, please see the FAQ at
>     <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>     Please resolve these comments along with any other Last Call
>     comments you may receive.
>
>     Document: draft-ietf-sieve-include-13
>     Reviewer: Ben Campbell
>     Review Date: 2011-12-13
>     IETF LC End Date: 2011-12-15
>
>     Summary: This draft is almost ready for publication as a proposed
>     standard
>
>     Major issues:
>
>     None
>
>     Minor issues:
>
>     -- section 3.1, paragraph 4: "Implementations MUST NOT generate
>     errors for recursive inclusions at upload time, as this would
>     force an upload ordering requirement upon script authors /
>     generators.  However, if an active script is replaced with a
>     faulty script and would remain the active script, an error MUST be
>     generated and the upload MUST fail."
>
>     These two statements seem contradictory on a quick reading.  In
>     particular, how can the latter assertion avoid an upload ordering
>     requirement? Or do you mean faulty in some way other than being
>     recursive?
>
>
> If you're replacing an active script, it has to be correct all the 
> time, and uploads are atomic only on a per-script basis. There's a 
> risk that if you're uploading a set of scripts that include one 
> another, at some intermediate stage while some scripts are uploaded 
> but not others, they are in an invalid state. The managesieve spec 
> says that scripts must be validated at upload time. The language above 
> is trying to say that you can upload all of the scripts that may 
> include one another in any order without generating errors 
> immediately, however, if you're replacing an active script or a script 
> included by the active script, then you DO have to upload a correct 
> script right from the get-go.
It looks like expanding the text to say what you explained above might 
be in order.


--------------010601070103030800070603
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Aaron,<br>
    <br>
    On 19/12/2011 19:13, Aaron Stone wrote:
    <blockquote
cite="mid:CAEdAYKU7FrmRA0agwW0ux60VVhHGE9Dc_0hdj+TRPLW9DxFRLg@mail.gmail.com"
      type="cite">On Tue, Dec 13, 2011 at 2:13 PM, Ben Campbell <span
        dir="ltr">&lt;<a moz-do-not-send="true"
          href="mailto:ben@nostrum.com" target="_blank">ben@nostrum.com</a>&gt;</span>
      wrote:<br>
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          I am the assigned Gen-ART reviewer for this draft. For
          background on Gen-ART, please see the FAQ at &lt;<a
            moz-do-not-send="true"
            href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
            target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br>
          <br>
          Please resolve these comments along with any other Last Call
          comments you may receive.<br>
          <br>
          Document: draft-ietf-sieve-include-13<br>
          Reviewer: Ben Campbell<br>
          Review Date: 2011-12-13<br>
          IETF LC End Date: 2011-12-15<br>
          <br>
          Summary: This draft is almost ready for publication as a
          proposed standard<br>
          <br>
          Major issues:<br>
          <br>
          None<br>
          <br>
          Minor issues:<br>
          <br>
          -- section 3.1, paragraph 4: "Implementations MUST NOT
          generate errors for recursive inclusions at upload time, as
          this would force an upload ordering requirement upon script
          authors / generators. &nbsp;However, if an active script is
          replaced with a faulty script and would remain the active
          script, an error MUST be generated and the upload MUST fail."<br>
          <br>
          These two statements seem contradictory on a quick reading.
          &nbsp;In particular, how can the latter assertion avoid an upload
          ordering requirement? Or do you mean faulty in some way other
          than being recursive?<br>
        </blockquote>
        <div><br>
        </div>
        <div>If you're replacing an active script, it has to be correct
          all the time, and uploads are atomic only on a per-script
          basis. There's a risk that if you're uploading a set of
          scripts that include one another, at some intermediate stage
          while some scripts are uploaded but not others, they are in an
          invalid state. The managesieve spec says that scripts must be
          validated at upload time. The language above is trying to say
          that you can upload all of the scripts that may include one
          another in any order without generating errors immediately,
          however, if you're replacing an active script or a script
          included by the active script, then you DO have to upload a
          correct script right from the get-go.<br>
        </div>
      </div>
    </blockquote>
    It looks like expanding the text to say what you explained above
    might be in order.<br>
    <br>
  </body>
</html>

--------------010601070103030800070603--

From stephan@rename-it.nl  Thu Dec 22 13:09:26 2011
Return-Path: <stephan@rename-it.nl>
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 C98B021F8490 for <sieve@ietfa.amsl.com>; Thu, 22 Dec 2011 13:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DR-6rvcuyN7J for <sieve@ietfa.amsl.com>; Thu, 22 Dec 2011 13:09:26 -0800 (PST)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id 2264821F8488 for <sieve@ietf.org>; Thu, 22 Dec 2011 13:09:24 -0800 (PST)
Received: from klara.student.utwente.nl ([130.89.162.218]:65122 helo=[10.168.3.2]) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <stephan@rename-it.nl>) id 1Rdpt8-0005do-Vj for sieve@ietf.org; Thu, 22 Dec 2011 22:09:22 +0100
Message-ID: <4EF39C67.7090803@rename-it.nl>
Date: Thu, 22 Dec 2011 22:08:55 +0100
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: sieve@ietf.org
References: <20111201174341.3962.4826.idtracker@ietfa.amsl.com>
In-Reply-To: <20111201174341.3962.4826.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RenameIT-MailScanner-SpamScore: -2.3 (--)
X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=ham version=3.3.1
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-convert-06.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: Thu, 22 Dec 2011 21:09:26 -0000

On 12/1/2011 6:43 PM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Sieve Mail Filtering Language Working Group of the IETF.
>
> 	Title           : Sieve Extension for Converting Messages Before Delivery
> 	Author(s)       : Alexey Melnikov
>                            Qian Sun
>                            Barry Leiba
>                            Kepeng Li
> 	Filename        : draft-ietf-sieve-convert-06.txt
> 	Pages           : 9
> 	Date            : 2011-12-01

I was just reading this specification again for some example text, and I 
noticed a small issue. This nit is about the following requirement from 
Section 6 of RFC 5228 (Sieve):

    Extensions MUST state how they interact with constraints defined in
    section 2.10, e.g., whether they cancel the implicit keep, and which
    actions they are compatible and incompatible with.

The latter part of this requirement is obviously explicitly met in 
Section 2.1. However, I miss an explicit statement about whether or not 
the new "convert" action cancels the implicit keep. Although it should 
be quite obvious and the examples provide various hints in the correct 
direction, I think an explicit sentence is in order. For example, I did 
find this for both new actions defined in the editheader specification 
(RFC5293), e.g. `The addheader action does not affect Sieve's implicit 
keep.' I think the situation is very similar in this case.

Regards,

Stephan.



From barryleiba.mailing.lists@gmail.com  Fri Dec 23 07:53:45 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 584FF21F8B04 for <sieve@ietfa.amsl.com>; Fri, 23 Dec 2011 07:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.391
X-Spam-Level: 
X-Spam-Status: No, score=-102.391 tagged_above=-999 required=5 tests=[AWL=0.586, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQaXrWVfepN7 for <sieve@ietfa.amsl.com>; Fri, 23 Dec 2011 07:53:45 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id D245621F8AFD for <sieve@ietf.org>; Fri, 23 Dec 2011 07:53:44 -0800 (PST)
Received: by ghbg18 with SMTP id g18so3154555ghb.31 for <sieve@ietf.org>; Fri, 23 Dec 2011 07:53:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=AVCj0MKkWfaBqXVFJPbruXW9Vxh/tIVKxEEaN8gnp/4=; b=vgdlre24jJXx+bIoe7vGh57H6BHUzTVzMZOnkrdHYWkt2dv1/3W48zInCGx1sKRsLL xuQsP42u6U1eGCL+kNccHa2x1wsK4jWZNWxkxkBglE0F5arorPFkork+yUhTTt5gL24r 4XwDU7mbHJZJJPe2c0l+VEsHG2s6DxSrpA+vs=
MIME-Version: 1.0
Received: by 10.236.115.40 with SMTP id d28mr21655737yhh.37.1324655624492; Fri, 23 Dec 2011 07:53:44 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.146.225.26 with HTTP; Fri, 23 Dec 2011 07:53:44 -0800 (PST)
In-Reply-To: <4EF39C67.7090803@rename-it.nl>
References: <20111201174341.3962.4826.idtracker@ietfa.amsl.com> <4EF39C67.7090803@rename-it.nl>
Date: Fri, 23 Dec 2011 10:53:44 -0500
X-Google-Sender-Auth: 8Op4Vu6uS8wCHLu6-_XSPv_qEkc
Message-ID: <CAC4RtVCabzhyd7TgHzdp_maYjk3pfLnf2u5rMqvLeojpM8ZMtw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Bosch <stephan@rename-it.nl>
Content-Type: text/plain; charset=ISO-8859-1
Cc: sieve@ietf.org
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-convert-06.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: Fri, 23 Dec 2011 15:53:45 -0000

> The latter part of this requirement is obviously explicitly met in Section
> 2.1. However, I miss an explicit statement about whether or not the new
> "convert" action cancels the implicit keep. Although it should be quite
> obvious and the examples provide various hints in the correct direction, I
> think an explicit sentence is in order.

A fair suggestion.  I will extend the last paragraph of section 2.1
when we go into AUTH48 (or Pete can put in an RFC Editor note now):

OLD
   Because the implicit keep (see Section 2.10.2 of [RFC5228]), if it is
   in effect, acts on the final state of the message, all conversions
   are performed before any implicit keep.

NEW
   Because the implicit keep (see Section 2.10.2 of [RFC5228]), if it is
   in effect, acts on the final state of the message, all conversions
   are performed before any implicit keep.  The "convert" actions
   themselves have no effect on the implicit keep status.

Barry

From alexey.melnikov@isode.com  Fri Dec 23 12:00:52 2011
Return-Path: <alexey.melnikov@isode.com>
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 56DC921F8B34 for <sieve@ietfa.amsl.com>; Fri, 23 Dec 2011 12:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHIeJDTxjhkz for <sieve@ietfa.amsl.com>; Fri, 23 Dec 2011 12:00:51 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1164D21F8AB8 for <sieve@ietf.org>; Fri, 23 Dec 2011 12:00:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1324670446; d=isode.com; s=selector; i=@isode.com; bh=bgyO+O6C5JMiTGZsh9Piyi4rbd5MP+AWUt9O6vz2a+E=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=IPjRVzG2vIGmHMb30fq+/mvclIMQUc87nTpjoZoD90MY0tKahniYcMX8DFhRDbTB6UN3ih b1gicci+WeuomjXTfETzQ00UBkbeGVq/ugLT43oKE4xgUcb1Ow1p/JE8G3wcidFXPzUvWk j1YT7eRfYDZFW7YuPipECtqJvruMW9M=;
Received: from [192.168.1.4] (ppp95-165-132-54.pppoe.spdop.ru [95.165.132.54]) by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <TvTd3gBr1wjl@rufus.isode.com>; Fri, 23 Dec 2011 20:00:42 +0000
Message-ID: <4EF4DDEC.8070701@isode.com>
Date: Fri, 23 Dec 2011 20:00:44 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: Barry Leiba <barryleiba@computer.org>
References: <20111201174341.3962.4826.idtracker@ietfa.amsl.com> <4EF39C67.7090803@rename-it.nl> <CAC4RtVCabzhyd7TgHzdp_maYjk3pfLnf2u5rMqvLeojpM8ZMtw@mail.gmail.com>
In-Reply-To: <CAC4RtVCabzhyd7TgHzdp_maYjk3pfLnf2u5rMqvLeojpM8ZMtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: sieve@ietf.org
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-convert-06.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: Fri, 23 Dec 2011 20:00:52 -0000

On 23/12/2011 15:53, Barry Leiba wrote:
>> The latter part of this requirement is obviously explicitly met in Section
>> 2.1. However, I miss an explicit statement about whether or not the new
>> "convert" action cancels the implicit keep. Although it should be quite
>> obvious and the examples provide various hints in the correct direction, I
>> think an explicit sentence is in order.
> A fair suggestion.  I will extend the last paragraph of section 2.1
> when we go into AUTH48 (or Pete can put in an RFC Editor note now):
>
> OLD
>     Because the implicit keep (see Section 2.10.2 of [RFC5228]), if it is
>     in effect, acts on the final state of the message, all conversions
>     are performed before any implicit keep.
>
> NEW
>     Because the implicit keep (see Section 2.10.2 of [RFC5228]), if it is
>     in effect, acts on the final state of the message, all conversions
>     are performed before any implicit keep.  The "convert" actions
>     themselves have no effect on the implicit keep status.
+1.

