From internet-drafts@ietf.org Thu Jun 9 07:30:24 2011 Return-Path: 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 1CB6111E80EC; Thu, 9 Jun 2011 07:30:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.589 X-Spam-Level: X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c1FikU18JIVx; Thu, 9 Jun 2011 07:30:23 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97DA811E80DB; Thu, 9 Jun 2011 07:30:23 -0700 (PDT) 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.55 Message-ID: <20110609143023.31952.12286.idtracker@ietfa.amsl.com> Date: Thu, 09 Jun 2011 07:30:23 -0700 Cc: sieve@ietf.org Subject: [sieve] I-D Action: draft-ietf-sieve-external-lists-10.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 14:30:24 -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: Externally Stored Lists Author(s) : Alexey Melnikov Barry Leiba Filename : draft-ietf-sieve-external-lists-10.txt Pages : 18 Date : 2011-06-09 The Sieve email filtering language can be used to implement email whitelisting, blacklisting, personal distribution lists, and other sorts of list matching. Currently, this requires that all members of such lists be hardcoded in the script itself. Whenever a member of a list is added or deleted, the script needs to be updated and possibly uploaded to a mail server. This document defines a Sieve extension for accessing externally stored lists -- lists whose members are stored externally to the script, such as using LDAP (RFC 4510), ACAP (RFC 2244), CardDAV (work in progress), or relational databases. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sieve-external-lists-10.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-external-lists-10.txt From iesg-secretary@ietf.org Mon Jun 13 09:28:20 2011 Return-Path: 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 ABEA021F853D; Mon, 13 Jun 2011 09:28:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.545 X-Spam-Level: X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3cfS7-NSWqFG; Mon, 13 Jun 2011 09:28:20 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 188EE21F853F; Mon, 13 Jun 2011 09:28:19 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 3.55 Message-ID: <20110613162819.15209.98729.idtracker@ietfa.amsl.com> Date: Mon, 13 Jun 2011 09:28:19 -0700 Cc: sieve mailing list , sieve chair , RFC Editor Subject: [sieve] Protocol Action: 'Sieve Extension: Externally Stored Lists' to Proposed Standard (draft-ietf-sieve-external-lists-10.txt) X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2011 16:28:20 -0000 The IESG has approved the following document: - 'Sieve Extension: Externally Stored Lists' (draft-ietf-sieve-external-lists-10.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-external-lists/ Technical Summary The Sieve scripting language can be used to implement whitelisting, blacklisting, personal distribution lists, and other sorts of list matching. Currently, this requires that all members of such lists be hardcoded in the script itself. Whenever a member of a list is added or deleted, the script needs to be updated and possibly uploaded to a mail server. This document defines a Sieve extension for accessing externally stored lists -- lists whose members are stored externally to the script, such as using LDAP (RFC 4510), ACAP (RFC 2244), CardDAV (work in progress), or relational databases. Working Group Summary This extension started as an individual submission in 2007 and was adopted as a WG document in July 2009. The basic premise has remained the same throughout all revisions of the document. Much of the WG discussion surrounded refining the syntax and the nature of the value used to represent an external list. The WG came to consensus on the use of a URI, and then defined a new URI scheme for its own use. However, subsequent review and discussion on the URI review mailing list lead to the WG dropping its proposal for a new URI scheme. Instead the WG created a new URN sub-namespace for sieve parameters and defined how that is used in the extension (with an abbreviated syntactic form required for script compactness). The URN approach now represents WG consensus. In addition, an apps review team review was done. The one major issue from that review was addressed by the addition of text to the Security Considerations section. The one minor issue was discussed and no action was deemed necessary. Document Quality At least one commercial implementation of this specification exists (fully updated to the latest version). One other commercial vendor, and one open source vendor have indicated they will support this specification. Personnel Document Shepherd: Cyrus Daboo AD: Pete Resnick From cyrus@daboo.name Mon Jun 20 08:08:06 2011 Return-Path: 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 E0A5921F8513 for ; Mon, 20 Jun 2011 08:08:06 -0700 (PDT) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4cFWYBj9RJHW for ; Mon, 20 Jun 2011 08:08:06 -0700 (PDT) Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id D054D21F850E for ; Mon, 20 Jun 2011 08:08:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 8152BF8EEDE for ; Mon, 20 Jun 2011 11:08:03 -0400 (EDT) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbFdwO-rARNt for ; Mon, 20 Jun 2011 11:08:02 -0400 (EDT) Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 4CB0EF8EED1 for ; Mon, 20 Jun 2011 11:08:00 -0400 (EDT) Date: Mon, 20 Jun 2011 11:07:52 -0400 From: Cyrus Daboo To: SIEVE Message-ID: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=4430 Subject: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2011 15:08:07 -0000 Hi folks, I wanted to give a status update of the WG and also ask a few questions of everyone to see where we want to go. This comes at the prompting of our new AD who wants to judge the "energy level" of this WG to determine whether it makes sense for the WG to continue. Note that I did request a 1 hour session for the upcoming meeting in Quebec City The last face-to-face WG meeting was last July. Since then the following drafts have been through IETF processing and are now in the RFC editor queue: draft-ietf-sieve-autoreply draft-ietf-sieve-external-lists draft-ietf-sieve-notify-presence draft-ietf-sieve-vacation-seconds These should all be published soon (having mostly been blocked on external-lists which was recently approved). Thanks to everyone for their work on these. There has been a WG last call on the draft-ietf-sieve-include document and an update to that will be available very shortly so that we can continue with IETF processing of that. All our other drafts are currently expired. From our charter, here are the outstanding items that have previous had drafts published: (1) Finish work on existing in-progress Working Group documents: (b) Notify SIP (draft-ietf-sieve-notify-sip-message) (c) RegEx (draft-ietf-sieve-regex) (e) Sieve in IMAP (draft-ietf-sieve-imap-sieve) (2) Finalize and publish the following SIEVE extensions as proposed standards: (d) Convert messages (draft-melnikov-sieve-convert) Can the authors of these documents please provide a status update and indicate whether they intend to continue work on them? Can we also have other people comment on whether they intend to implement, or at least review or help with, any of these drafts? If the WG does shut down, it seems reasonable for any of these drafts to continue on as individual contributions. At the very least, if we are going to continue work on them I would like to see updates published in time for discussion at the IETF meeting (July 11th cut-off for draft submission). We have a bunch of other items on our charter which I have listed below with some of my own comments on what I think should happen with them. Please comment on these yourselves so we can decide whether to continue or drop these from the charter if we decide the WG should continue on. (3) Work on a specification for iCalendar and vCard extraction, and cooperate with the VCARDDAV WG for address book tests in Sieve. I suspect I might have been one of the primary movers for this particular topic, but at this point I don't it is relevant any more. So I would be in favor of dropping this. (4) Work on a specification to describe how EAI/IDN issues should be handled in SIEVE. We have periodically asked about this, and most of the time there seemed very little that needed to be done in SIEVE to deal with this. One option going forward is for the WG to drop this item in favor of it being picked up in the EAI WG. (5) Work on a "Benefits of SIEVE" guide for client and server vendors that: (a) Describes the SIEVE protocol and its suite of extensions. (b) Explains the benefits of server-side filtering in practical terms. (c) Shows how client-side filtering can be migrated to SIEVE. Whilst there was a lot of initial enthusiasm for this when we originally did a re-charter, there has been no progress in developing a document. At this point I would propose we drop this from the charter. (6) Produce one or more informational RFCs containing a set of test scripts and test email messages that are to be filtered by the scripts, and the expected results of that filtering. This will serve as the basis of a interoperability test suite to help determine the suitability of moving the base specification and selected extensions to Draft status. Again there was initial enthusiasm for this, but nothing has materialized, so I would also propose dropping this from the charter. Next question: does anyone have any new SIEVE work they would like to propose at this time? I don't think anyone can deny this WG has been successful over the years in addressing the needs of SIEVE implementations, even if at our own, sometimes slow, pace. Shutting it down now would not be unreasonable, but I think we do need to prove the utility of keeping it alive. So please chime in with your thoughts. -- Cyrus Daboo From barryleiba.mailing.lists@gmail.com Mon Jun 20 10:59:44 2011 Return-Path: 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 3C43A11E8168 for ; Mon, 20 Jun 2011 10:59:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.898 X-Spam-Level: X-Spam-Status: No, score=-102.898 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35V+rDUs9nji for ; Mon, 20 Jun 2011 10:59:43 -0700 (PDT) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 69E3911E815E for ; Mon, 20 Jun 2011 10:59:43 -0700 (PDT) Received: by gxk19 with SMTP id 19so3280341gxk.31 for ; Mon, 20 Jun 2011 10:59:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=15tpIwPqY4oIJ7YXCwfhQcrWG5zp4o0CxLSVZRSp1lM=; b=wIPi+RPDaC/WwLcsk71aSFzP3cJ2R6eMb7VQT20YCq1k85UnpxCc8TOCOZr8+PT+Co LVkpscHYQAO3R0In+3mKNo/ZXXl+QrU1F5r1gDn+uM0ZVAKoGY6Dvl3FeCGxcvWV6mtH GdMok7UVMJsD50Fk2xyhmLi4esPKZCmJvtJiU= DomainKey-Signature: a=rsa-sha1; c=nofws; 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 :content-transfer-encoding; b=UgxGzQnXP0HnY3MHoEQfO2EBygnHI0RnKmp+numGESqlAHZ9jkjwWSISipE9lXSefR nCXydfJ/22+rMzjG2fJqVtyGTGnCyhGhfMB/gmPFnX6kvizLuAfqlfYh0I0eWxmV8yAb QzHVI0rzyfSlGO8OmaKQAQ7U/CtCFVBYIoDWM= MIME-Version: 1.0 Received: by 10.150.8.9 with SMTP id 9mr2099138ybh.186.1308592782789; Mon, 20 Jun 2011 10:59:42 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.147.99.3 with HTTP; Mon, 20 Jun 2011 10:59:42 -0700 (PDT) In-Reply-To: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> Date: Mon, 20 Jun 2011 13:59:42 -0400 X-Google-Sender-Auth: fr04yczVhonzvPjrpfUNGxaojfc Message-ID: From: Barry Leiba To: Cyrus Daboo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2011 17:59:44 -0000 Hi, Cyrus, and thanks for the update. > draft-ietf-sieve-autoreply > draft-ietf-sieve-external-lists > draft-ietf-sieve-notify-presence > draft-ietf-sieve-vacation-seconds > > These should all be published soon (having mostly been blocked on > external-lists which was recently approved). Thanks to everyone for their > work on these. We can actually ask the ADs to release the hold on the three earlier drafts. They were not actually waiting on a normative reference to external-lists. It was an AD-requested hold to make sure that the external-lists URI questions were settled down so that the examples would be correct. Now that external-lists is in the RFC-ed queue, the other three docs can go ahead. I'm copying Pete, asking him to ask the RFC Editor to go ahead and process autoreply, notify-presence, and vacation-seconds, and I will correct the examples in AUTH48. > =A0(1) Finish work on existing in-progress Working Group documents: > =A0 =A0 =A0(b) Notify SIP (draft-ietf-sieve-notify-sip-message) > =A0 =A0 =A0(c) RegEx (draft-ietf-sieve-regex) > =A0 =A0 =A0(e) Sieve in IMAP (draft-ietf-sieve-imap-sieve) > > =A0(2) Finalize and publish the following SIEVE extensions as proposed > =A0standards: > =A0 =A0 =A0(d) Convert messages (draft-melnikov-sieve-convert) For (b) and (d), one of the authors (Sun Qian from Huawei) now has other responsibilities. My Huawei colleague Kepeng Li and I have taken over his part of the work, and Kepeng has done an update on them both. We're now waiting for me to do a pass on them, which I expect to get to this week or next. So these will soon have a new version, and we can finish them up. For (e), I have an almost-ready version that's been almost ready for a while. I will finish it up and submit it after I get the aforementioned two done, so expect it, also, within the next two weeks. It should address all of Ned's comments from the last round of reviews, and so it should be pretty close to being a finished version... I hope. > =A0(3) Work on a specification for iCalendar and vCard extraction, and > =A0cooperate with the VCARDDAV WG for address book tests in Sieve. External-lists probably does all we really need for address book tests, and I agree with dropping this one. > =A0(4) Work on a specification to describe how EAI/IDN issues should be > =A0handled in SIEVE. I don't really see EAI picking this up, but I think there isn't much, if anything, that needs to be done, and we can address it later, either in the working group (if it hadn't been closed by then) or as an individual submission. > =A0(5) Work on a "Benefits of SIEVE" guide for client and server vendors I agree with dropping this, unless someone can get a reasonable first draft put together before Qu=E9bec. > =A0(6) Produce one or more informational RFCs containing a set of test > =A0scripts and test email messages that are to be filtered by the scripts= , > =A0and the expected results of that filtering. This will serve as the bas= is > =A0of a interoperability test suite to help determine the suitability of > =A0moving the base specification and selected extensions to Draft status. It seems to me that no one thinks it's important to move the base spec to DS. In any case, the huge number of extensions makes it seem a bit pointless to move base to DS by itself, without bringing a suite of the most useful/important extensions with it, and that's not happening soon, I don't think. Yes, let's drop this. > Next question: does anyone have any new SIEVE work they would like to > propose at this time? I think we have what we need, and we should wrap up what we're doing, declare success, and drink lots of beer. (That said, I don't think there's a need to hurry to close it without finishing the work in progress, and (except perhaps for RegEx) we will soon finish it. I should say we'd have the remaining open docs (except perhaps for RegEx) to the IESG by the end of August. Barry From barryleiba.mailing.lists@gmail.com Mon Jun 20 11:00:30 2011 Return-Path: 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 D381421F8462 for ; Mon, 20 Jun 2011 11:00:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.903 X-Spam-Level: X-Spam-Status: No, score=-102.903 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iG1RMLCkc2QE for ; Mon, 20 Jun 2011 11:00:30 -0700 (PDT) Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id E135121F845E for ; Mon, 20 Jun 2011 11:00:24 -0700 (PDT) Received: by gxk19 with SMTP id 19so3280734gxk.31 for ; Mon, 20 Jun 2011 11:00:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vOMVrP6JMMuG6XE/NVXijcRIKOz8N+4UtqFdLvyfVaw=; b=xLkplu2O9Fh37CV+QSW4TMlvH3yc/18o9girff899uUqraSlFGRWCYkfngvEwaRFKe nvVVJjfpaUaxTMvBV2NZJJQ/ykihhFQo7aut3QDbnAgF+uXTIWkiIzBBAByt8j8EnPHm +m4XHG9vQ99JKQ3uRt5LFoIOcRgsUynVdHK8E= DomainKey-Signature: a=rsa-sha1; c=nofws; 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 :content-transfer-encoding; b=KgewPPBwECdm+abTbO2IuWFUGv/5x4AOw6CXSPoK4mo7Smtv4/T3yJQqrSASXUIEaf sugH8E88yydVQd0uNOfIiLrpZZQ2HjQ4BSHDIvjgwImJu40M+TOOkTZksGhHFYCnkkBp yro9lATo8279uhPxFaHvMJ09vFIj5bigHotIs= MIME-Version: 1.0 Received: by 10.236.168.99 with SMTP id j63mr7869089yhl.117.1308592824270; Mon, 20 Jun 2011 11:00:24 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.147.99.3 with HTTP; Mon, 20 Jun 2011 11:00:24 -0700 (PDT) In-Reply-To: References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> Date: Mon, 20 Jun 2011 14:00:24 -0400 X-Google-Sender-Auth: aAbIKmpyRECICcU5A0yN4XfmfbU Message-ID: From: Barry Leiba To: Cyrus Daboo , Pete Resnick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2011 18:00:30 -0000 On Mon, Jun 20, 2011 at 1:59 PM, Barry Leiba wrot= e: > Hi, Cyrus, and thanks for the update. > >> draft-ietf-sieve-autoreply >> draft-ietf-sieve-external-lists >> draft-ietf-sieve-notify-presence >> draft-ietf-sieve-vacation-seconds >> >> These should all be published soon (having mostly been blocked on >> external-lists which was recently approved). Thanks to everyone for thei= r >> work on these. > > We can actually ask the ADs to release the hold on the three earlier > drafts. =A0They were not actually waiting on a normative reference to > external-lists. =A0It was an AD-requested hold to make sure that the > external-lists URI questions were settled down so that the examples > would be correct. =A0Now that external-lists is in the RFC-ed queue, the > other three docs can go ahead. =A0I'm copying Pete, asking him to ask > the RFC Editor to go ahead and process autoreply, notify-presence, and > vacation-seconds, and I will correct the examples in AUTH48. But, of course, I forgot to copy Pete. Doing that this time. Barry From likepeng@huawei.com Mon Jun 20 18:24:11 2011 Return-Path: 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 860529E8005 for ; Mon, 20 Jun 2011 18:24:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.499 X-Spam-Level: X-Spam-Status: No, score=-4.499 tagged_above=-999 required=5 tests=[AWL=2.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVnr6wTWeoPa for ; Mon, 20 Jun 2011 18:24:10 -0700 (PDT) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 837659E8007 for ; Mon, 20 Jun 2011 18:24:10 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LN4008HL9672Q@szxga04-in.huawei.com> for sieve@ietf.org; Tue, 21 Jun 2011 09:22:55 +0800 (CST) Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LN4004OR966U6@szxga04-in.huawei.com> for sieve@ietf.org; Tue, 21 Jun 2011 09:22:55 +0800 (CST) Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ABB74135; Tue, 21 Jun 2011 09:22:53 +0800 (CST) Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 21 Jun 2011 09:19:51 +0800 Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.112]) by szxeml410-hub.china.huawei.com ([169.254.184.109]) with mapi id 14.01.0270.001; Tue, 21 Jun 2011 09:19:55 +0800 Date: Tue, 21 Jun 2011 01:19:54 +0000 From: Likepeng In-reply-to: X-Originating-IP: [10.70.109.110] To: Barry Leiba , Cyrus Daboo Message-id: <34966E97BE8AD64EAE9D3D6E4DEE36F22B6B2E@szxeml506-mbx.china.huawei.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-language: zh-CN Content-transfer-encoding: quoted-printable Accept-Language: zh-CN, en-US Thread-topic: [sieve] SIEVE WG Status Thread-index: AQHML1xfXspHgNudYUG2xb84au92iJTGAtQAgAD/fyA= X-MS-Has-Attach: X-MS-TNEF-Correlator: X-CFilter-Loop: Reflected References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2011 01:24:11 -0000 >That said, I don't think there's a need to hurry to close it without finis= hing the work in >progress, and (except perhaps for RegEx) we will soon finish it. I >should say we'd have the remaining open docs (except perhaps for >RegEx) to the IESG by the end of August. +1. We are working hard offline for the remaining drafts (b, d, e). Thanks, Kind Regards Kepeng -----Original Message----- From: sieve-bounces@ietf.org [mailto:sieve-bounces@ietf.org] On Behalf Of B= arry Leiba Sent: Tuesday, June 21, 2011 2:00 AM To: Cyrus Daboo Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status Hi, Cyrus, and thanks for the update. > draft-ietf-sieve-autoreply > draft-ietf-sieve-external-lists > draft-ietf-sieve-notify-presence > draft-ietf-sieve-vacation-seconds > > These should all be published soon (having mostly been blocked on > external-lists which was recently approved). Thanks to everyone for their > work on these. We can actually ask the ADs to release the hold on the three earlier drafts. They were not actually waiting on a normative reference to external-lists. It was an AD-requested hold to make sure that the external-lists URI questions were settled down so that the examples would be correct. Now that external-lists is in the RFC-ed queue, the other three docs can go ahead. I'm copying Pete, asking him to ask the RFC Editor to go ahead and process autoreply, notify-presence, and vacation-seconds, and I will correct the examples in AUTH48. > =A0(1) Finish work on existing in-progress Working Group documents: > =A0 =A0 =A0(b) Notify SIP (draft-ietf-sieve-notify-sip-message) > =A0 =A0 =A0(c) RegEx (draft-ietf-sieve-regex) > =A0 =A0 =A0(e) Sieve in IMAP (draft-ietf-sieve-imap-sieve) > > =A0(2) Finalize and publish the following SIEVE extensions as proposed > =A0standards: > =A0 =A0 =A0(d) Convert messages (draft-melnikov-sieve-convert) For (b) and (d), one of the authors (Sun Qian from Huawei) now has other responsibilities. My Huawei colleague Kepeng Li and I have taken over his part of the work, and Kepeng has done an update on them both. We're now waiting for me to do a pass on them, which I expect to get to this week or next. So these will soon have a new version, and we can finish them up. For (e), I have an almost-ready version that's been almost ready for a while. I will finish it up and submit it after I get the aforementioned two done, so expect it, also, within the next two weeks. It should address all of Ned's comments from the last round of reviews, and so it should be pretty close to being a finished version... I hope. > =A0(3) Work on a specification for iCalendar and vCard extraction, and > =A0cooperate with the VCARDDAV WG for address book tests in Sieve. External-lists probably does all we really need for address book tests, and I agree with dropping this one. > =A0(4) Work on a specification to describe how EAI/IDN issues should be > =A0handled in SIEVE. I don't really see EAI picking this up, but I think there isn't much, if anything, that needs to be done, and we can address it later, either in the working group (if it hadn't been closed by then) or as an individual submission. > =A0(5) Work on a "Benefits of SIEVE" guide for client and server vendors I agree with dropping this, unless someone can get a reasonable first draft put together before Qu=E9bec. > =A0(6) Produce one or more informational RFCs containing a set of test > =A0scripts and test email messages that are to be filtered by the scripts= , > =A0and the expected results of that filtering. This will serve as the bas= is > =A0of a interoperability test suite to help determine the suitability of > =A0moving the base specification and selected extensions to Draft status. It seems to me that no one thinks it's important to move the base spec to DS. In any case, the huge number of extensions makes it seem a bit pointless to move base to DS by itself, without bringing a suite of the most useful/important extensions with it, and that's not happening soon, I don't think. Yes, let's drop this. > Next question: does anyone have any new SIEVE work they would like to > propose at this time? I think we have what we need, and we should wrap up what we're doing, declare success, and drink lots of beer. (That said, I don't think there's a need to hurry to close it without finishing the work in progress, and (except perhaps for RegEx) we will soon finish it. I should say we'd have the remaining open docs (except perhaps for RegEx) to the IESG by the end of August. Barry _______________________________________________ sieve mailing list sieve@ietf.org https://www.ietf.org/mailman/listinfo/sieve From stephan@rename-it.nl Mon Jun 20 18:25:19 2011 Return-Path: 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 448E921F8463 for ; Mon, 20 Jun 2011 18:25:18 -0700 (PDT) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86Ll453kXP3N for ; Mon, 20 Jun 2011 18:25:17 -0700 (PDT) Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [87.249.120.243]) by ietfa.amsl.com (Postfix) with ESMTP id 292AF21F8444 for ; Mon, 20 Jun 2011 18:25:17 -0700 (PDT) Received: from klara.student.utwente.nl ([130.89.162.218]:3408 helo=[10.168.3.2]) by drpepper.rename-it.nl with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1QYpiJ-0000Fu-Q7 for sieve@ietf.org; Tue, 21 Jun 2011 03:25:14 +0200 Message-ID: <4DFFF2FE.30908@rename-it.nl> Date: Tue, 21 Jun 2011 03:25:18 +0200 From: Stephan Bosch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: sieve@ietf.org References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> In-Reply-To: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.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] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2011 01:25:19 -0000 Hi, On 6/20/2011 5:07 PM, Cyrus Daboo wrote: > Next question: does anyone have any new SIEVE work they would like to > propose at this time? > > I don't think anyone can deny this WG has been successful over the > years in addressing the needs of SIEVE implementations, even if at our > own, sometimes slow, pace. Shutting it down now would not be > unreasonable, but I think we do need to prove the utility of keeping > it alive. So please chime in with your thoughts. > There is one thing I've noticed: the more user-friendly GUIs and web interfaces allow users to edit Sieve scripts as a set of intuitive (structurally pre-defined) mail filter rules. This avoids the need to learn Sieve and write detailed Sieve scripts directly, which can be daunting for the less capable mail user. However, Sieve has no real concept of a `mail filter rule', so a translation is necessary from the rules defined in the editor and the Sieve script on the server. Also, a convention is to name the mail filters to provide an indication of their purpose. Other forms of such metadata are imaginable, such as creation date, name of the creating software etc. The problem is that such data needs to be stored somewhere. Some solutions involve storing the metadata along with the rules themselves in a database or another form of storage external to Sieve. The Sieve script is then created from this storage once the rules change. On the one hand, this avoids the complexity of parsing Sieve scripts to regain access to the original rules and metadata, but, on the other hand, it completely blocks using multiple different interfaces for editing the same Sieve scripts. Direct changes to the Sieve scripts would simply be lost once the rules change. Alternatively, some script generators encode such metadata in Sieve comments and parse the Sieve script itself to extract the rules. This way, the Sieve script itself is the only means of storage, theoretically allowing multiple distinct Sieve generators (GUIs and web interfaces) to inter-operate with the same Sieve scripts. Unfortunately, I've seen little or no coordination between the script generator authors, which probably means that scripts generated by one interface cannot be edited through an alternative one, mostly because the encoded comments are going to be incompatible. Of course, the Sieve code itself can also be incompatible if the Sieve generators don't support the same set of Sieve features or if some code structure is not recognized. However, I think this could be mended quite easily by presenting rules that cannot be handled by the GUI itself as custom or external; not to be touched by that particular interface. The main requirement would be that individual rules in the script can be annotated with a name and that a parsing GUI can distinguish where rules begin and end. A standardized means to achieve this could, in my opinion, increase interoperability between Sieve script generators. However, I have only implemented a Sieve interpreter so far (which obviously doesn't care about metadata encoded in comments) and I therefore have no experience with Sieve GUIs and web interfaces and the complexities involved. I haven't seen much discussion about this subject and I am wondering whether this is currently perceived as a concern at all. I vaguely remember a short discussion about this in a thread related to Sieve in XML, but nothing else. Are users expected to use only one interface/method for editing their (active) scripts? Would it be useful to provide a specification on how to encode meta-data in Sieve script comments? Regards, Stephan. From presnick@qualcomm.com Tue Jun 21 09:19:19 2011 Return-Path: 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 4698521F8477 for ; Tue, 21 Jun 2011 09:19:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.468 X-Spam-Level: X-Spam-Status: No, score=-106.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XxTaDSxT2e1e for ; Tue, 21 Jun 2011 09:19:18 -0700 (PDT) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id BBEFF21F8475 for ; Tue, 21 Jun 2011 09:19:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1308673158; x=1340209158; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E00C40D.7030109@qualcomm.com>|Date:=20Tu e,=2021=20Jun=202011=2011:17:17=20-0500|From:=20Pete=20Re snick=20|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:=20Barry=20Leiba=20|CC:=20Cyrus=20Daboo=20,=20S IEVE=20|Subject:=20Re:=20[sieve]=20SIEVE =20WG=20Status|References:=20<816FC375A4D2F1E3CCDEEAA2@ca ldav.corp.apple.com>=20|In-Reply-To:=20|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=MOvdAs0FBRFmCiWWnas30vybu9T1hNoB+g5sle8zt/I=; b=mP6DHd5hbDwF3eyZdgOmlxdWrXbbw1MzoLvuJ9OBcbn3KDYcNlos+x7G 5XIZ1BUIwZ8mSI6KhGDxHdNPZ8zTrN8SQGCB99AM58I17oEWnFcQcPaka wVP9LaLT6DBItGslv4levwDLFO6OwsKBlvgwfEryH9X6fWdMadI80umSp I=; X-IronPort-AV: E=McAfee;i="5400,1158,6384"; a="98929828" Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 21 Jun 2011 09:17:19 -0700 X-IronPort-AV: E=Sophos;i="4.65,401,1304319600"; d="scan'208";a="37750692" Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 21 Jun 2011 09:17:19 -0700 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.270.1; Tue, 21 Jun 2011 09:17:19 -0700 Message-ID: <4E00C40D.7030109@qualcomm.com> Date: Tue, 21 Jun 2011 11:17:17 -0500 From: Pete Resnick 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: Barry Leiba References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [172.30.48.1] Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2011 16:19:19 -0000 On 6/20/11 12:59 PM, Barry Leiba wrote: >> draft-ietf-sieve-autoreply >> draft-ietf-sieve-external-lists >> draft-ietf-sieve-notify-presence >> draft-ietf-sieve-vacation-seconds >> >> These should all be published soon (having mostly been blocked on >> external-lists which was recently approved). Thanks to everyone for their >> work on these. >> > We can actually ask the ADs to release the hold on the three earlier > drafts. They were not actually waiting on a normative reference to > external-lists. It was an AD-requested hold to make sure that the > external-lists URI questions were settled down so that the examples > would be correct. Now that external-lists is in the RFC-ed queue, the > other three docs can go ahead. I'm copying Pete, asking him to ask > the RFC Editor to go ahead and process autoreply, notify-presence, and > vacation-seconds, and I will correct the examples in AUTH48. > Pete acks. pr -- Pete Resnick Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 From alexey.melnikov@isode.com Tue Jun 21 14:57:38 2011 Return-Path: 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 CB8869E800B for ; Tue, 21 Jun 2011 14:57:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.394 X-Spam-Level: X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XJ7f-PLQIFuT for ; Tue, 21 Jun 2011 14:57:38 -0700 (PDT) Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id A7A36228006 for ; Tue, 21 Jun 2011 14:57:37 -0700 (PDT) Received: from [188.29.183.175] (188.29.183.175.threembb.co.uk [188.29.183.175]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Tue, 21 Jun 2011 22:57:35 +0100 Message-ID: <4E0113BB.2070400@isode.com> Date: Tue, 21 Jun 2011 22:57:15 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Cyrus Daboo , Pete Resnick References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> In-Reply-To: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2011 21:57:39 -0000 Cyrus Daboo wrote: > Hi folks, Hi Cyrus, > I wanted to give a status update of the WG and also ask a few > questions of everyone to see where we want to go. This comes at the > prompting of our new AD who wants to judge the "energy level" of this > WG to determine whether it makes sense for the WG to continue. > > Note that I did request a 1 hour session for the upcoming meeting in > Quebec City > > The last face-to-face WG meeting was last July. Since then the > following drafts have been through IETF processing and are now in the > RFC editor queue: > > draft-ietf-sieve-autoreply > draft-ietf-sieve-external-lists > draft-ietf-sieve-notify-presence > draft-ietf-sieve-vacation-seconds I think these drafts were past AUTH48 when I stopped them from being published (due to the reference to draft-ietf-sieve-external-lists). So the RFC Editor should be told that we want to review/fix examples before publishing. > These should all be published soon (having mostly been blocked on > external-lists which was recently approved). Thanks to everyone for > their work on these. > > There has been a WG last call on the draft-ietf-sieve-include document > and an update to that will be available very shortly so that we can > continue with IETF processing of that. > > All our other drafts are currently expired. From our charter, here are > the outstanding items that have previous had drafts published: > > (1) Finish work on existing in-progress Working Group documents: > (b) Notify SIP (draft-ietf-sieve-notify-sip-message) > (c) RegEx (draft-ietf-sieve-regex) > (e) Sieve in IMAP (draft-ietf-sieve-imap-sieve) > > (2) Finalize and publish the following SIEVE extensions as proposed > standards: > (d) Convert messages (draft-melnikov-sieve-convert) I am particularly interested in (c) and (e) at this point. I would really appreciate somebody showing interest in (b) and (d). > Can the authors of these documents please provide a status update and > indicate whether they intend to continue work on them? Can we also > have other people comment on whether they intend to implement, or at > least review or help with, any of these drafts? > > If the WG does shut down, it seems reasonable for any of these drafts > to continue on as individual contributions. Does our esteemed AD agree? > At the very least, if we are going to continue work on them I would > like to see updates published in time for discussion at the IETF > meeting (July 11th cut-off for draft submission). > > We have a bunch of other items on our charter which I have listed > below with some of my own comments on what I think should happen with > them. Please comment on these yourselves so we can decide whether to > continue or drop these from the charter if we decide the WG should > continue on. > > (3) Work on a specification for iCalendar and vCard extraction, and > cooperate with the VCARDDAV WG for address book tests in Sieve. > > I suspect I might have been one of the primary movers for this > particular topic, but at this point I don't it is relevant any more. > So I would be in favor of dropping this. My idea behind this was to have a test that can reach inside XML body parts, possibly using XPath or similar. > (4) Work on a specification to describe how EAI/IDN issues should be > handled in SIEVE. > > We have periodically asked about this, and most of the time there > seemed very little that needed to be done in SIEVE to deal with this. > One option going forward is for the WG to drop this item in favor of > it being picked up in the EAI WG. I declare this to be Pete's problem either way ;-). Doing this in EAI would be fine. > (5) Work on a "Benefits of SIEVE" guide for client and server vendors > that: > (a) Describes the SIEVE protocol and its suite of extensions. > (b) Explains the benefits of server-side filtering in practical > terms. > (c) Shows how client-side filtering can be migrated to SIEVE. > > Whilst there was a lot of initial enthusiasm for this when we > originally did a re-charter, there has been no progress in developing > a document. At this point I would propose we drop this from the charter. With some sadness, I have to agree. > (6) Produce one or more informational RFCs containing a set of test > scripts and test email messages that are to be filtered by the scripts, > and the expected results of that filtering. This will serve as the > basis > of a interoperability test suite to help determine the suitability of > moving the base specification and selected extensions to Draft status. > > Again there was initial enthusiasm for this, but nothing has > materialized, so I would also propose dropping this from the charter. Right. > Next question: does anyone have any new SIEVE work they would like to > propose at this time? > > I don't think anyone can deny this WG has been successful over the > years in addressing the needs of SIEVE implementations, even if at our > own, sometimes slow, pace. Shutting it down now would not be > unreasonable, but I think we do need to prove the utility of keeping > it alive. So please chime in with your thoughts. From presnick@qualcomm.com Tue Jun 21 15:12:44 2011 Return-Path: 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 68D4222800E for ; Tue, 21 Jun 2011 15:12:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.476 X-Spam-Level: X-Spam-Status: No, score=-106.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39bOqEZQZYeq for ; Tue, 21 Jun 2011 15:12:43 -0700 (PDT) Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFA622800D for ; Tue, 21 Jun 2011 15:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1308694363; x=1340230363; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E011719.2010205@qualcomm.com>|Date:=20Tu e,=2021=20Jun=202011=2017:11:37=20-0500|From:=20Pete=20Re snick=20|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:=20Alexey=20Melnikov=20|CC:=20Cyrus=20Daboo=20,=20SIEVE=20|Subject:=20Re:=20[sieve]=20 SIEVE=20WG=20Status|References:=20<816FC375A4D2F1E3CCDEEA A2@caldav.corp.apple.com>=20<4E0113BB.2070400@isode.com> |In-Reply-To:=20<4E0113BB.2070400@isode.com> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.48.1]; bh=dK8TG+MZHhpzVVtyBh+tzAX15Q7qYkFPiJv5eJ2pFLY=; b=vPQoYcvTmQx8M6PkCL1lFYKmPOT2Z5+9jNSbJL+S1kdcGK2/nys1RHja MacBniVTS+HUGAfHZdBpPZ5Ug3NJYhnxRlxB0IOdEnJq9Z4pTr84iqQcX kFx2OuBf+c1xlIL2oHiwsBowG6ih/ZlWDnC2a35jBr6ChGoEcIJTvLYc9 U=; X-IronPort-AV: E=McAfee;i="5400,1158,6384"; a="99206431" Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 21 Jun 2011 15:12:42 -0700 X-IronPort-AV: E=Sophos;i="4.65,401,1304319600"; d="scan'208";a="80943559" Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 21 Jun 2011 15:12:42 -0700 Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 21 Jun 2011 15:11:39 -0700 Message-ID: <4E011719.2010205@qualcomm.com> Date: Tue, 21 Jun 2011 17:11:37 -0500 From: Pete Resnick 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: Alexey Melnikov References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> <4E0113BB.2070400@isode.com> In-Reply-To: <4E0113BB.2070400@isode.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [172.30.48.1] Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2011 22:12:44 -0000 On 6/21/11 4:57 PM, Alexey Melnikov wrote: > Cyrus Daboo wrote: > >> I wanted to give a status update of the WG and also ask a few >> questions of everyone to see where we want to go. This comes at the >> prompting of our new AD who wants to judge the "energy level" of this >> WG to determine whether it makes sense for the WG to continue. >> >> Note that I did request a 1 hour session for the upcoming meeting in >> Quebec City >> >> The last face-to-face WG meeting was last July. Since then the >> following drafts have been through IETF processing and are now in the >> RFC editor queue: >> >> draft-ietf-sieve-autoreply >> draft-ietf-sieve-external-lists >> draft-ietf-sieve-notify-presence >> draft-ietf-sieve-vacation-seconds > > I think these drafts were past AUTH48 when I stopped them from being > published (due to the reference to draft-ietf-sieve-external-lists). > So the RFC Editor should be told that we want to review/fix examples > before publishing. They are all showing in "EDIT" now. But I already let the RFC Editor know that they are no longer on AD hold, so you may want to email them to check on status. >> If the WG does shut down, it seems reasonable for any of these drafts >> to continue on as individual contributions. > Does our esteemed AD agree? Your humble and curmudgeonly AD is going to ask lots of questions about what kind of review (both small and IETF-wide) these documents are going to get before he is thrilled out of his mind to take them on as individual submissions through the AD and declare them "consensus documents". If you can't generate interest in getting them reviewed in a WG, I'm not entirely convinced how you're going to get enough review without one. And I hate dealing with individual submission documents, especially if I've got to do all of the legwork to get them reviewed. >> (4) Work on a specification to describe how EAI/IDN issues should be >> handled in SIEVE. >> >> We have periodically asked about this, and most of the time there >> seemed very little that needed to be done in SIEVE to deal with this. >> One option going forward is for the WG to drop this item in favor of >> it being picked up in the EAI WG. > > I declare this to be Pete's problem either way ;-). > Doing this in EAI would be fine. Let's start by making it Klensin's and Yee's problem if it comes to that. They can make it my problem in due time. pr -- Pete Resnick Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 From NED+mta-filters@mauve.mrochek.com Wed Jun 22 11:01:03 2011 Return-Path: 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 613BB21F859C for ; Wed, 22 Jun 2011 11:01:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYR1lAaAXYZY for ; Wed, 22 Jun 2011 11:01:02 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 42BC621F859B for ; Wed, 22 Jun 2011 11:01:02 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O2S503RF8000XS87@mauve.mrochek.com> for sieve@ietf.org; Wed, 22 Jun 2011 11:00:33 -0700 (PDT) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O2PCIBD7WW00RCTX@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Wed, 22 Jun 2011 11:00:27 -0700 (PDT) From: NED+mta-filters@mauve.mrochek.com Message-id: <01O2S500WIYY00RCTX@mauve.mrochek.com> Date: Wed, 22 Jun 2011 10:54:05 -0700 (PDT) In-reply-to: "Your message dated Tue, 21 Jun 2011 03:25:18 +0200" <4DFFF2FE.30908@rename-it.nl> MIME-version: 1.0 Content-type: TEXT/PLAIN; Format=flowed References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> <4DFFF2FE.30908@rename-it.nl> To: Stephan Bosch DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1308765265; i=@mrochek.com; bh=vq6r/5MbDc8jPLjemS+ROVzRDRi2oUPWrKI/J5RtmQA=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=c498IH9EsiaRfw2LfD1Jl009wj+7U98t73oYfHYzF0N4UTzNI+D/rZuQX6NE5QikT JDH4raihL3PUrT3lmDhZLN2sXfhwCXB7G4UWV7H3pnOOdGety5DdjNb2otwMoEDb3l HohkrckWQWX7+b7AAQHC2mT7gqr+DtyALofdHo/0= Cc: sieve@ietf.org Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2011 18:01:03 -0000 > Hi, > On 6/20/2011 5:07 PM, Cyrus Daboo wrote: > > Next question: does anyone have any new SIEVE work they would like to > > propose at this time? > > > > I don't think anyone can deny this WG has been successful over the > > years in addressing the needs of SIEVE implementations, even if at our > > own, sometimes slow, pace. Shutting it down now would not be > > unreasonable, but I think we do need to prove the utility of keeping > > it alive. So please chime in with your thoughts. > > > There is one thing I've noticed: the more user-friendly GUIs and web > interfaces allow users to edit Sieve scripts as a set of intuitive > (structurally pre-defined) mail filter rules. This avoids the need to > learn Sieve and write detailed Sieve scripts directly, which can be > daunting for the less capable mail user. However, Sieve has no real > concept of a `mail filter rule', so a translation is necessary from the > rules defined in the editor and the Sieve script on the server. Also, a > convention is to name the mail filters to provide an indication of their > purpose. Other forms of such metadata are imaginable, such as creation > date, name of the creating software etc. The base Sieve language may not have these constructs (and IMO should not), but that doesn't mean they haven't been defined. See RFC 5784. > The problem is that such data needs to be stored somewhere. Some > solutions involve storing the metadata along with the rules themselves > in a database or another form of storage external to Sieve. The Sieve > script is then created from this storage once the rules change. On the > one hand, this avoids the complexity of parsing Sieve scripts to regain > access to the original rules and metadata, but, on the other hand, it > completely blocks using multiple different interfaces for editing the > same Sieve scripts. Direct changes to the Sieve scripts would simply be > lost once the rules change. > Alternatively, some script generators encode such metadata in Sieve > comments and parse the Sieve script itself to extract the rules. This is the approach taken in RFC 5784. Note that the format is defined for both the XML form and native form of Sieve, as well as the rules for converting between the two. > This > way, the Sieve script itself is the only means of storage, > theoretically allowing multiple distinct Sieve generators (GUIs and web > interfaces) to inter-operate with the same Sieve scripts. Unfortunately, > I've seen little or no coordination between the script generator > authors, which probably means that scripts generated by one interface > cannot be edited through an alternative one, mostly because the encoded > comments are going to be incompatible. Yes, this is a problem, and it partially addressed in RFC 5784: Structuring conventions are defined so that at least the basic rule structure can be shared. But sharing of specific rule semantics is a lot trickier. > Of course, the Sieve code itself > can also be incompatible if the Sieve generators don't support the same > set of Sieve features or if some code structure is not recognized. > However, I think this could be mended quite easily by presenting rules > that cannot be handled by the GUI itself as custom or external; not to > be touched by that particular interface. RFC 5463 provides some solutions for these issues. Ned From barryleiba.mailing.lists@gmail.com Wed Jun 22 13:38:18 2011 Return-Path: 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 E5F7021F84D4 for ; Wed, 22 Jun 2011 13:38:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.908 X-Spam-Level: X-Spam-Status: No, score=-102.908 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTyGMQK+PEml for ; Wed, 22 Jun 2011 13:38:18 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3B27821F84B1 for ; Wed, 22 Jun 2011 13:38:18 -0700 (PDT) Received: by yxp4 with SMTP id 4so151505yxp.31 for ; Wed, 22 Jun 2011 13:38:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0B7BYcUcEmT2Zy2orOvoC4MrUJs2ZzgZskq6evlWQDU=; b=tpB9NoK4drR6Y3YqHir1Dvoj5lZIe7YL0jG9leMi7rlSCeXF54jwPHig9uTU5aRWMC tYhqbt+X+eFpb0WgB4GiYp35z2HDoRILO/bzq5L3s5YCF9hVkE6jaitUQY/6iLyBibTi tQTuk21JjLaYPc8d+PCle2YGQh6UJSMXoKXhQ= DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=rROvLHWCwbWTJ40+sOxbHQNICWZouWT62dw7NEQVorgBo2lO7kKgU84Om1b/bx4OdS uNVYyMYND4GwdozbVXI/vdwnXefpvbV28GpWQ/Vcg/b8+dJorLf9n+JBQzuP5KCeEkL3 Ug/FNTgIWO7CDo+593v5AmElKHgJk2D8r6Ols= MIME-Version: 1.0 Received: by 10.236.80.69 with SMTP id j45mr1961936yhe.50.1308775097568; Wed, 22 Jun 2011 13:38:17 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.147.170.15 with HTTP; Wed, 22 Jun 2011 13:38:17 -0700 (PDT) In-Reply-To: <4E011719.2010205@qualcomm.com> References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> <4E0113BB.2070400@isode.com> <4E011719.2010205@qualcomm.com> Date: Wed, 22 Jun 2011 16:38:17 -0400 X-Google-Sender-Auth: IHtuJhiTpORhGn9wh6nPz3lyJd8 Message-ID: From: Barry Leiba To: Pete Resnick Content-Type: text/plain; charset=ISO-8859-1 Cc: SIEVE Subject: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2011 20:38:19 -0000 >> I think these drafts were past AUTH48 when I stopped them from being >> published (due to the reference to draft-ietf-sieve-external-lists). So the >> RFC Editor should be told that we want to review/fix examples before >> publishing. > > They are all showing in "EDIT" now. But I already let the RFC Editor know > that they are no longer on AD hold, so you may want to email them to check > on status. So emailed. >>> If the WG does shut down, it seems reasonable for any of these drafts to >>> continue on as individual contributions. >> >> Does our esteemed AD agree? > > Your humble and curmudgeonly AD is going to ask lots of questions about what > kind of review (both small and IETF-wide) these documents are going to get > before he is thrilled out of his mind to take them on as individual > submissions through the AD and declare them "consensus documents". If you > can't generate interest in getting them reviewed in a WG, I'm not entirely > convinced how you're going to get enough review without one. And I hate > dealing with individual submission documents, especially if I've got to do > all of the legwork to get them reviewed. I agree with Pete: we should make every effort to keep the WG open to work on them. If we can't do that, then we clearly don't have enough interest to do them outside the WG. In that case, they could go to the ISE, and come out as informational, describing a planned standardization that didn't happen. I hope it doesn't come to that, and that we can have enough enthusiasm left to finish them here. Barry From stephan@rename-it.nl Thu Jun 23 02:33:19 2011 Return-Path: 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 CED8B21F8531 for ; Thu, 23 Jun 2011 02:33:19 -0700 (PDT) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OltX7dnNfxQd for ; Thu, 23 Jun 2011 02:33:19 -0700 (PDT) Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [87.249.120.243]) by ietfa.amsl.com (Postfix) with ESMTP id 47ED121F84D7 for ; Thu, 23 Jun 2011 02:33:17 -0700 (PDT) Received: from wlan227132.mobiel.utwente.nl ([130.89.227.132]:49421) by drpepper.rename-it.nl with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1QZgHh-0003BC-My for sieve@ietf.org; Thu, 23 Jun 2011 11:33:15 +0200 Message-ID: <4E030853.9050005@rename-it.nl> Date: Thu, 23 Jun 2011 11:33:07 +0200 From: Stephan Bosch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: sieve@ietf.org References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> <4DFFF2FE.30908@rename-it.nl> <01O2S500WIYY00RCTX@mauve.mrochek.com> In-Reply-To: <01O2S500WIYY00RCTX@mauve.mrochek.com> 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: Re: [sieve] SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2011 09:33:19 -0000 Op 22-6-2011 19:54, Ned Freed schreef: > > The base Sieve language may not have these constructs (and IMO should > not), but > that doesn't mean they haven't been defined. See RFC 5784. Damn, now why did I miss this part? Yes, RFC 5784 pretty much covers most of the issue. Apparently, it has been a while since I last read this. Sorry for the noise. Regards, Stephan. From cyrus@daboo.name Thu Jun 30 08:09:53 2011 Return-Path: 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 C60C511E817E for ; Thu, 30 Jun 2011 08:09:52 -0700 (PDT) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BN-UMvM80QKo for ; Thu, 30 Jun 2011 08:09:51 -0700 (PDT) Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id A72F311E816F for ; Thu, 30 Jun 2011 08:09:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 24003122D8A3 for ; Thu, 30 Jun 2011 11:09:48 -0400 (EDT) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYVgO5nhZLEg for ; Thu, 30 Jun 2011 11:09:47 -0400 (EDT) Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 46C1C122D898 for ; Thu, 30 Jun 2011 11:09:47 -0400 (EDT) Date: Thu, 30 Jun 2011 11:09:44 -0400 From: Cyrus Daboo To: SIEVE Message-ID: <750B7DFB79E79E5B1CCA18C5@caldav.corp.apple.com> In-Reply-To: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> References: <816FC375A4D2F1E3CCDEEAA2@caldav.corp.apple.com> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=651 Subject: [sieve] Update, was Re: SIEVE WG Status X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 15:09:53 -0000 Hi , After consultation with our AD, the current plan is to go ahead with the meeting in Quebec City next month. However, the level of activity/interest in on going work expressed at that meeting (and in the intervening time) will be used to determine whether we continue with a Working Group or shut it down in favor of individual submissions. Please submit updates to all drafts that you would like to see discussed in Quebec, and post a list of discussion items for those (so I can start to put together an agenda). Note we only have a 1 hour slot so we need to concentrate on key issues that need "face time" discussions. -- Cyrus Daboo