Sieve Mail Filtering Language
charter-ietf-sieve-05

Document Charter Sieve Mail Filtering Language WG (sieve)
Title Sieve Mail Filtering Language
Last updated 2004-11-23
State Approved
WG State Concluded
IESG Responsible AD Pete Resnick
Charter Edit AD (None)
Send notices to (None)

Charter
charter-ietf-sieve-05

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) External lists (draft-ietf-sieve-external-lists)
       (b) Notify SIP (draft-ietf-sieve-notify-sip-message)
       (c) RegEx (draft-ietf-sieve-regex)
       (d) Include/multi-script (draft-ietf-sieve-include)
       (e) Sieve in IMAP (draft-ietf-sieve-imap-sieve)
  
   (2) Finalize and publish the following SIEVE extensions as proposed
   standards:
       (a) General Auto-reply (draft-george-sieve-autoreply)
       (b) Notify presence (draft-george-sieve-notify-presence)
       (c) Vacation time (draft-george-sieve-vacation-time)
       (d) Convert messages (draft-melnikov-sieve-convert)
  
   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 for iCalendar and vCard extraction, and
   cooperate with the VCARDDAV WG for address book tests in Sieve.
  
   (4) Work on a specification to describe how EAI/IDN issues should be
   handled in SIEVE.
  
   (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.
  
   (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.