Proposed charter change

[Cyrus Daboo <[e-mail]>]

Hi folks,
Below is a proposal for a new charter for the working group based on 
discussions at this weeks IETF meeting.

Please review this and comment.

We would like to see a "show of hands" from implementers on each of the new 
extensions being proposed so that we can judge the interest in each.

Note that we will need document authors/editors to step up for items (3) 
and (4) if we are to include these.

Once the WG has discussed this and decided on exactly what we will work on, 
Alexey and I will propose some milestones. I am hoping that we can complete 
all this work in 12 - 18 months. Note that some of the new drafts are 
already close to last call.

This is all subject to AD and IESG approval, of course.

---
The SIEVE email filtering language is specified in RFC 5228, together with 
a number of extensions.

The SIEVE working group is being re-chartered to:

(1) Finish work on existing in-progress Working Group documents:

	(a) Body (draft-ietf-sieve-body-07.txt)
	(b) Notify mailto (draft-ietf-sieve-notify-mailto.txt)
	(c) Edit header (draft-ietf-sieve-editheader-10.txt)
	(d) Mime loops (draft-ietf-sieve-mime-loop-04.txt)
	(e) Refuse/reject (draft-ietf-sieve-refuse-reject-06.txt)

(2) Finalize and publish the following SIEVE extensions as proposed 
standards:

	(a) Date/Index (draft-freed-sieve-date-index-08.txt)
	(b) iHave (draft-freed-sieve-ihave-01.txt)
	(c) Environment (draft-freed-sieve-environment-03.txt)
	(d) Notary (draft-freed-sieve-notary-01.txt)
	(e) SIEVE in XML (draft-freed-sieve-in-xml-01.txt)
	(f) Notify-sip (draft-melnikov-sieve-notify-sip-message-01.txt)
	(g) ManageSIEVE (draft-martin-managesieve-08.txt)
	(h) RegEx (draft-ietf-sieve-regex-00.txt)
	(j) Meta-data (draft-melnikov-sieve-imapext-metadata-03.txt)
	(k) Include/multi-script (draft-daboo-sieve-include-05.txt)
	(k) Address data (draft-melnikov-sieve-external-lists-01)

Additional drafts may be added to this list, but only via a charter
revision. There must also be demonstrable willingness in the SIEVE
development community to actually implement a given extension before
it can be added to this charter.

(3) 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.

(4) 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.


-- 
Cyrus Daboo