[Top] [All Lists]

WG Action: RECHARTER: Sieve Mail Filtering Language (sieve)

2008-09-03 17:28:47

The charter of the Sieve Mail Filtering Language (sieve) working group in
the Applications Area of the IETF has been updated.  For additional
information, please contact the Area Directors or the working group

Sieve Mail Filtering Language (sieve)
Current Status: Active Working Group


 Cyrus Daboo (cyrus(_at_)daboo(_dot_)name)
 Alexey Melnikov (alexey(_dot_)melnikov(_at_)isode(_dot_)com)

Applications Area Directors:

  Chris Newman (chris(_dot_)newman(_at_)sun(_dot_)com)
  Lisa Dusseault (lisa(_at_)osafoundation(_dot_)org)

Applications Area Advisor:

  Lisa Dusseault (lisa(_at_)osafoundation(_dot_)org)

Mailing Lists:

  General Discussion: ietf-mta-filters(_at_)imc(_dot_)org
  To Subscribe: ietf-mta-filters-request(_at_)imc(_dot_)org
  In Body: body=subscribe

Description of Working Group:

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) Notify mailto (draft-ietf-sieve-notify-mailto)
    (c) Mime loops (draft-ietf-sieve-mime-loop)
    (d) Refuse/reject (draft-ietf-sieve-refuse-reject)

(2) Finalize and publish the following SIEVE extensions as proposed
    (a) iHave (draft-freed-sieve-ihave)
    (b) Notary (draft-freed-sieve-notary)
    (c) SIEVE in XML (draft-freed-sieve-in-xml)
    (d) Notify-sip (draft-melnikov-sieve-notify-sip-message)
    (e) ManageSIEVE (draft-martin-managesieve)
    (f) RegEx (draft-ietf-sieve-regex)
    (g) Meta-data (draft-melnikov-sieve-imapext-metadata)
    (h) Include/multi-script (draft-daboo-sieve-include)
    (i) Address data (draft-melnikov-sieve-external-lists)
    (j) Support for Sieve in IMAP (draft-ietf-lemonade-imap-sieve)

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 specification to describe how EAI/IDN issues should be
handled in SIEVE.

(4) Work on a "Benefits of SIEVE" guide for client and server vendors
    (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.

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

Goals and Milestones:

July 2008:
 Submit notify-mailto to IESG
 Submit refuse-reject to IESG

August 2008:
 Submit mime-loops to IESG
 WGLC iHave

September 2008:
 Submit iHave to IESG
 WGLC Notary

October 2008:
 WGLC sieve-in-xml
 Submit Notary to IESG

November 2008:
 Submit sieve-in-xml to IESG

December 2008:
 Submit ManageSIEVE to IESG
 WGLC Notify-sip

January 2009:
 Submit Notify-sip to IESG
 WGLC Metadata

February 2009:
 Submit Metadata to IESG

March 2009
 Submit RegEx to IESG
 WGLC Include/multi-script

April 2009:
 Submit Include/multi-script to IESG
 WGLC external-lists

May 2009:
 Submit external-lists to IESG
 WGLC eai-issues

June 2009:
 Submit eai-issues to IESG
 WGLC benefits

July 2009:
 Submit benefits to IESG
 WGLC test-scripts

August 2009:
 Submit test-scripts to IESG

<Prev in Thread] Current Thread [Next in Thread>
  • WG Action: RECHARTER: Sieve Mail Filtering Language (sieve), The IESG <=