idnits 2.17.1 draft-ietf-sieve-convert-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 24, 2010) is 5054 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Melnikov 3 Internet-Draft Isode Limited 4 Intended status: Standards Track Q. Sun 5 Expires: December 26, 2010 Huawei Technologies 6 June 24, 2010 8 Sieve Extension for converting messages before delivery 9 draft-ietf-sieve-convert-00 11 Abstract 13 This document describes how Lemonade CONVERT can be used to transform 14 messages before final delivery. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on December 26, 2010. 33 Copyright Notice 35 Copyright (c) 2010 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Conventions Used in this Document . . . . . . . . . . . . . . . 3 52 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. :converted tagged argument to the 'fileinto' action . . . . . . 3 56 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 62 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 64 8. Normative References . . . . . . . . . . . . . . . . . . . . . 4 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Conventions Used in this Document 70 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 71 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 72 document are to be interpreted as described in RFC 2119 [RFC2119]. 74 Conventions for notations are as in [SIEVE] section 1.1, including 75 the use of [ABNF]. 77 2. Introduction 79 The [CONVERT] extension adds an IMAP command for performing client 80 controlled conversions on whole messages or their body parts. This 81 document defines a similar extension to the SIEVE [SIEVE] mail 82 filtering language, which reuses conversion parameters and framework 83 established by [CONVERT]. 85 3. :converted tagged argument to the 'fileinto' action 87 Usage: :converted 88 89 91 The :converted tag specifies that all body parts with "quoted-from- 92 mime-type" MIME type should be converted to "quoted-to-mime-type" 93 MIME type using conversion parameters specified in "transcoding- 94 params". Each conversion parameter value has the following syntax: 95 "=", where and are defined in [CONVERT]. 97 Messages which don't have any body part with the "quoted-from-mime- 98 type" MIME type are not affected by the conversion. 100 [[anchor3: Should there be a way to specify/restrict which specific 101 body parts need to be converted (e.g. only the second body part)? 102 Should there be a way to specify multiple conversions (on different 103 body parts of the same message)?]] 105 [[anchor4: Interaction with MIME Loops (e.g. if :converted is 106 applicable to the replace action) should be specified.]] 108 4. Examples 110 In the following examples all "image/tiff" body parts of the message 111 are converted to "image/jpeg" with image resolution of 320x480 112 pixels. 114 require ["fileinto", "convert"]; 116 fileinto :converted "image/tiff" "image/jpeg" "pix-x" "320" 117 "pix-y" "480" "INBOX"; 119 Messages which don't have image/tiff body parts are delivered to 120 INBOX as is. 122 5. Security Considerations 124 [[anchor6: TBD]] 126 6. IANA Considerations 128 IANA is requested to add the following registrations to the list of 129 Sieve extensions: 131 Capability name: convert 132 Description: adds a new tag to the fileinto action that enables 133 Sieve script to perform a conversion on the message being 134 delivered. 135 RFC number: this RFC 136 Contact address: The Sieve discussion list 137 139 7. Acknowledgements 141 [[anchor9: TBD]]. 143 8. Normative References 145 [ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 146 Specifications: ABNF", RFC 5234, January 2008. 148 [CONVERT] Melnikov, A., Ed. and P. Coates, Ed., "Internet Message 149 Access Protocol - CONVERT Extension", RFC 5259, July 2008. 151 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 152 Requirement Levels", RFC 2119, BCP 14, March 1997. 154 [SIEVE] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email 155 Filtering Language", RFC 5228, January 2008. 157 Authors' Addresses 159 Alexey Melnikov 160 Isode Limited 161 5 Castle Business Village 162 36 Station Road 163 Hampton, Middlesex TW12 2BX 164 UK 166 Email: Alexey.Melnikov@isode.com 167 URI: http://www.melnikov.ca/ 169 Qian Sun 170 Huawei Technologies 171 Bantian Longgang 172 Shenzhen, Guandong 518129 173 P.R China 175 Phone: +86 755 28780808 176 Email: sunqian@huawei.com