[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 draft-ietf-sieve-convert

Network Working Group                                        A. Melnikov
Internet-Draft                                             Isode Limited
Intended status: Standards Track                                  Q. Sun
Expires: January 6, 2009                             Huawei Technologies
                                                            July 5, 2008


        Sieve Extension for converting messages before delivery
                    draft-melnikov-sieve-convert-00

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 6, 2009.

Abstract

   This document describes how Lemonade CONVERT can be used to transform
   messages before final delivery.












Melnikov & Sun           Expires January 6, 2009                [Page 1]

Internet-Draft                Sieve CONVERT                    July 2008


Table of Contents

   1.  Conventions Used in this Document . . . . . . . . . . . . . . . 3

   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3

   3.  :converted tagged argument to the 'fileinto' action . . . . . . 3

   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4

   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4

   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4

   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4

       Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . 5
       Intellectual Property and Copyright Statements  . . . . . . . . 6































Melnikov & Sun           Expires January 6, 2009                [Page 2]

Internet-Draft                Sieve CONVERT                    July 2008


1.  Conventions Used in this Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

   Conventions for notations are as in [SIEVE] section 1.1, including
   the use of [ABNF].


2.  Introduction

   The [CONVERT] extension adds an IMAP command for performing client
   controlled conversions on whole messages or their body parts.  This
   document defines a similar extension to the SIEVE [SIEVE] mail
   filtering language, which reuses conversion parameters and framework
   established by [CONVERT].


3.  :converted tagged argument to the 'fileinto' action

   Usage:  :converted <quoted-from-mime-type: string>
           <quoted-to-mime-type: string>
           <transcoding-params: string-list>

   The :converted tag specifies that all body parts with "quoted-from-
   mime-type" MIME type should be converted to "quoted-to-mime-type"
   MIME type using conversion parameters specified in "transcoding-
   params".  Each conversion parameter value has the following syntax:
   "<transcoding-param>=<transcoding-param-value>", where <transcoding-
   param> and <transcoding-param-value> are defined in [CONVERT].
   Messages which don't have any body part with the "quoted-from-mime-
   type" MIME type are not affected by the conversion.

   [[anchor3: Should there be a way to specify/restrict which specific
   body parts need to be converted (e.g. only the second body part)?
   Should there be a way to specify multiple conversions (on differt
   body parts of the same message)?]]

   [[anchor4: Interaction with MIME Loops (e.g. if :converted is
   applicable to the replace action) should be specified.]]


4.  Examples

   In the following examples all "image/tiff" body parts of the message
   are converted to "image/jpeg" with image resolution of 320x480
   pixels.



Melnikov & Sun           Expires January 6, 2009                [Page 3]

Internet-Draft                Sieve CONVERT                    July 2008


       require ["fileinto", "convert"];

       fileinto :convert "image/tiff" "image/jpeg" "pix-x" "320"
                "pix-y" "480" "INBOX";

   Messages which don't have image/tiff body parts are delivered to
   INBOX as is.


5.  Security Considerations

   [[anchor6: TBD]]


6.  IANA Considerations

   IANA is requested to add the following registrations to the list of
   Sieve extensions:

   Capability name:  convert
   Description:  adds a new tag to the fileinto action that enables
      Sieve script to perform a conversion on the message being
      delivered.
   RFC number:  this RFC
   Contact address:  The Sieve discussion list
      <ietf-mta-filters@imc.org>


7.  Acknowledgements

   [[anchor9: TBD]].


8.  Normative References

   [ABNF]     Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", RFC 4234, October 2005.

   [CONVERT]  Melnikov, A., Ed. and P. Coates, Ed., "IMAP CONVERT
              extension", draft-ietf-lemonade-convert-20 (work in
              progress), May 2008.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", RFC 2119, BCP 14, March 1997.

   [SIEVE]    Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email
              Filtering Language", RFC 5228, January 2008.




Melnikov & Sun           Expires January 6, 2009                [Page 4]

Internet-Draft                Sieve CONVERT                    July 2008


Authors' Addresses

   Alexey Melnikov
   Isode Limited
   5 Castle Business Village
   36 Station Road
   Hampton, Middlesex  TW12 2BX
   UK

   Email: Alexey.Melnikov@isode.com
   URI:   http://www.melnikov.ca/


   Qian Sun
   Huawei Technologies
   Bantian Longgang
   Shenzhen, Guandong  518129
   P.R China

   Phone: +86 755 28780808
   Email: sunqian@huawei.com






























Melnikov & Sun           Expires January 6, 2009                [Page 5]

Internet-Draft                Sieve CONVERT                    July 2008


Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.











Melnikov & Sun           Expires January 6, 2009                [Page 6]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/