idnits 2.17.1 draft-melnikov-lemonade-convert-params-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 7, 2009) is 5522 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) == Unused Reference: 'ABNF' is defined on line 560, but no explicit reference was found in the text == Unused Reference: 'MIME-IMT' is defined on line 590, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'EXIF' Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Melnikov 3 Internet-Draft Isode Ltd 4 Intended status: Standards Track March 7, 2009 5 Expires: September 8, 2009 7 Conversion parameters for IMAP CONVERT 8 draft-melnikov-lemonade-convert-params-03.txt 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. This document may contain material 14 from IETF Documents or IETF Contributions published or made publicly 15 available before November 10, 2008. The person(s) controlling the 16 copyright in some of this material may not have granted the IETF 17 Trust the right to allow modifications of such material outside the 18 IETF Standards Process. Without obtaining an adequate license from 19 the person(s) controlling the copyright in such materials, this 20 document may not be modified outside the IETF Standards Process, and 21 derivative works of it may not be created outside the IETF Standards 22 Process, except to format it for publication as an RFC or to 23 translate it into languages other than English. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on September 8, 2009. 43 Copyright Notice 45 Copyright (c) 2009 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents in effect on the date of 50 publication of this document (http://trustee.ietf.org/license-info). 51 Please review these documents carefully, as they describe your rights 52 and restrictions with respect to this document. 54 Abstract 56 This is a companion document to the IMAP CONVERT (RFC 5259) extension 57 defined by the Lemonade Working Group. It defines additional 58 conversion parameters for conversions of images, audio, video and 59 textual body parts. It also demonstrates additional CONVERT usage 60 scenarios. 62 Table of Contents 64 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 65 2. Additional conversion parameters applicable to multiple 66 MIME types . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 3. Additional conversion parameters for image and video 68 conversions . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 4. Additional conversion parameters for conversions to text . . . 3 70 5. Additional conversion parameters for audio and video 71 conversions . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 74 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 76 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 77 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 78 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 80 1. Requirements notation 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in [RFC2119]. 86 In examples, "C:" and "S:" indicate lines sent by the client and 87 server respectively. If a single "C:" or "S:" label applies to 88 multiple lines, then the line breaks between those lines are for 89 editorial clarity only and are not part of the actual protocol 90 exchange. The five characters [...] means that something has been 91 elided. 93 [[anchor2: Editorial comments and questions are marked like this.]] 95 2. Additional conversion parameters applicable to multiple MIME types 97 The sizeLimit defines the maximum size (in bytes) of the converted 98 body part. It can be used with any conversion (including the 99 "default conversion"). 101 3. Additional conversion parameters for image and video conversions 103 Width and heigth of the resulting image can be specified using using 104 the PIX-X and PIX-Y parameters defined in [DISPLAY-FEATURES]. If 105 only one of the parameters is specified, the aspect ratio of the 106 resulting image MUST be maintained. 108 Number of different colors per image pixel (depth) can be controlled 109 by the "color-levels" conversion parameter [DISPLAY-FEATURES]. This 110 would typically be combined with the "color" conversion parameter 111 [DISPLAY-FEATURES], which controls color encoding scheme, such as 112 Mapped (palette or otherwise mapped color), Grey (grey-scale only) or 113 Full (full continuous-tone color) 115 4. Additional conversion parameters for conversions to text 117 The FORMAT conversion parameter can be used when converting a body 118 part to TEXT/PLAIN. It can contain one of two values: "FLOWED" or 119 "FIXED". When this parameter is not specified the default is 120 "FIXED". This parameter is the most useful when converting from 121 TEXT/HTML. See [RFC3676] for more details on the exact meaning of 122 this conversion parameter. 124 The ExifData conversion parameter can be used when extracting Exif 125 information in textual format, i.e. when converting a JPEG image to 126 TEXT/PLAIN. It can contain one of two values: "TRUE" or "FALSE". 127 When this parameter is not specified the default value is "FALSE". 128 The resulting TEXT/PLAIN body part is similar in format to the header 129 field section of an email message [RFC5322]. Each header field name 130 is as defined in section 4.6 (4.6.4 D and 4.6.6) of [EXIF] and each 131 value is UTF-8 representation of the corresponding value. 133 5. Additional conversion parameters for audio and video conversions 135 A conversion may change codec bitrate by specifying the "bitrate" 136 conversion parameter, which is a non-negative integer specifying bits 137 per second. The "encoding-method" conversion parameter can control 138 whether fixed bitrate or variable bitrate encoding is used. It might 139 have one of the two values: "FBR" (for fixed bit rate) or "VBR" (for 140 variable bit rate). For variable bit rate encodings the "min-bit- 141 rate" parameter can also be specified. Its value is a non-negative 142 integer specifying the minimum bits per second. 144 The "frameRate" conversion parameter can specify the maximum frame 145 rate in frames per second, expressed as a rational (>0) number, for 146 example "49/2". 148 6. IANA Considerations 150 IANA is requested to add the following registrations to the registry 151 established by [MEDIAFEAT-REG]. 153 To: "Media feature tags mailing list" 154 155 Subject: Registration of media feature tag sizeLimit 157 Media feature tag name: 158 sizeLimit 160 ASN.1 identifier associated with feature tag: 161 New assignment by IANA 163 Summary of the media feature indicated by this feature tag: 164 The sizeLimit defines the maximum size (in bytes) of the 165 converted body part. It allows a client to control 166 resulting size of a body part conversion using IMAP 167 CONVERT [CONVERT]. 168 This feature tag can be used with any conversion 169 (including the "default conversion" [CONVERT]). 171 Values appropriate for use with this feature tag: 172 Signed Integer (only positive values are allowed) 174 The feature tag is intended primarily for use in the following 175 applications, protocols, services, or negotiation mechanisms: 176 IMAP CONVERT extension [CONVERT] 178 Examples of typical use: 179 C: b001 CONVERT 2 BINARY[3 ("image/jpeg" ("sizeLimit" 180 "16384"))] 182 Related standards or documents: 183 [CONVERT] 185 Considerations particular to use in individual applications, 186 protocols, services, or negotiation mechanisms: 187 None 189 Interoperability considerations: None 191 Security considerations: None 193 Additional information: None 195 Name(s) & email address(es) of person(s) to contact for further 196 information: 197 Alexey Melnikov 199 Intended usage: 200 COMMON 202 Author/Change controller: 203 IETF 205 Requested IANA publication delay: 206 None 208 Other information: 209 None 211 To: "Media feature tags mailing list" 212 213 Subject: Registration of media feature tag FORMAT 215 Media feature tag name: 216 FORMAT 218 ASN.1 identifier associated with feature tag: 219 New assignment by IANA 221 Summary of the media feature indicated by this feature tag: 222 The FORMAT media feature can be used when converting a body 223 part to TEXT/PLAIN media type. 224 See [RFC3676] for more details on the exact meaning of 225 this media feature. 227 Values appropriate for use with this feature tag: 228 Token (It can contain one of two values: "FLOWED" or "FIXED". 229 When this parameter is not specified the default is 230 "FIXED".) 232 The feature tag is intended primarily for use in the following 233 applications, protocols, services, or negotiation mechanisms: 234 IMAP CONVERT extension [CONVERT] 236 Examples of typical use: 237 C: b001 CONVERT 2 BINARY[3 ("text/plain" ("format" 238 "flowed"))] 240 Related standards or documents: 241 [CONVERT] 243 Considerations particular to use in individual applications, 244 protocols, services, or negotiation mechanisms: 245 None 247 Interoperability considerations: None 249 Security considerations: None 251 Additional information: None 253 Name(s) & email address(es) of person(s) to contact for further 254 information: 255 Alexey Melnikov 257 Intended usage: 258 COMMON 260 Author/Change controller: 261 IETF 263 Requested IANA publication delay: 264 None 266 Other information: 267 This parameter is the most useful when converting from 268 TEXT/HTML. 270 To: "Media feature tags mailing list" 271 272 Subject: Registration of media feature tag ExifData 274 Media feature tag name: 275 ExifData 277 ASN.1 identifier associated with feature tag: 278 New assignment by IANA 280 Summary of the media feature indicated by this feature tag: 281 The ExifData media feature can be used for extracting Exif 282 information in textual format, i.e. when converting a JPEG 283 image to TEXT/PLAIN. 284 The resulting TEXT/PLAIN body part is similar in format to 285 the header field section of an email message [RFC5322]. 286 Each header field name is as defined in section 4.6 287 (4.6.4 D and 4.6.6) of [EXIF] and each value is UTF-8 288 representation of the corresponding value. 290 Values appropriate for use with this feature tag: 291 Boolean (When this parameter is not specified the default 292 value is "FALSE".) 294 The feature tag is intended primarily for use in the following 295 applications, protocols, services, or negotiation mechanisms: 296 IMAP CONVERT extension [CONVERT] 298 Examples of typical use: 299 C: b001 CONVERT 2 BINARY[3 ("text/plain" ("ExifData" 300 "TRUE"))] 302 Related standards or documents: 303 [CONVERT] 305 Considerations particular to use in individual applications, 306 protocols, services, or negotiation mechanisms: 307 None 309 Interoperability considerations: None 311 Security considerations: None 312 Additional information: None 314 Name(s) & email address(es) of person(s) to contact for further 315 information: 316 Alexey Melnikov 318 Intended usage: 319 COMMON 321 Author/Change controller: 322 IETF 324 Requested IANA publication delay: 325 None 327 Other information: 328 None 330 To: "Media feature tags mailing list" 331 332 Subject: Registration of media feature tag bitrate 334 Media feature tag name: 335 bitrate 337 ASN.1 identifier associated with feature tag: 338 New assignment by IANA 340 Summary of the media feature indicated by this feature tag: 341 An IMAP CONVERT conversion may change codec bitrate by 342 specifying the "bitrate" conversion parameter, which is 343 a non-negative integer specifying bits per second. 345 Values appropriate for use with this feature tag: 346 Signed Integer (only positive values are allowed) 348 The feature tag is intended primarily for use in the following 349 applications, protocols, services, or negotiation mechanisms: 350 IMAP CONVERT extension [CONVERT] 352 Examples of typical use: 353 C: b001 CONVERT 2 BINARY[3 ("AUDIO/G719" ("bitrate" 354 "32768"))] 356 Related standards or documents: 357 [CONVERT] 359 Considerations particular to use in individual applications, 360 protocols, services, or negotiation mechanisms: 361 None 363 Interoperability considerations: None 365 Security considerations: None 367 Additional information: None 369 Name(s) & email address(es) of person(s) to contact for further 370 information: 371 Alexey Melnikov 373 Intended usage: 374 COMMON 376 Author/Change controller: 377 IETF 379 Requested IANA publication delay: 380 None 382 Other information: 383 None 385 To: "Media feature tags mailing list" 386 387 Subject: Registration of media feature tag encoding-method 389 Media feature tag name: 390 encoding-method 392 ASN.1 identifier associated with feature tag: 393 New assignment by IANA 395 Summary of the media feature indicated by this feature tag: 396 The "encoding-method" media feature can control 397 whether fixed bitrate or variable bitrate encoding is used. 399 Values appropriate for use with this feature tag: 400 Token ("FBR" (for fixed bit rate) or "VBR" (for variable 401 bit rate). 403 The feature tag is intended primarily for use in the following 404 applications, protocols, services, or negotiation mechanisms: 405 IMAP CONVERT extension [CONVERT] 407 Examples of typical use: 409 Related standards or documents: 410 [CONVERT] 412 Considerations particular to use in individual applications, 413 protocols, services, or negotiation mechanisms: 414 None 416 Interoperability considerations: None 418 Security considerations: None 420 Additional information: None 422 Name(s) & email address(es) of person(s) to contact for further 423 information: 424 Alexey Melnikov 426 Intended usage: 427 COMMON 429 Author/Change controller: 430 IETF 432 Requested IANA publication delay: 433 None 435 Other information: 436 None 438 To: "Media feature tags mailing list" 439 440 Subject: Registration of media feature tag min-bit-rate 442 Media feature tag name: 443 min-bit-rate 445 ASN.1 identifier associated with feature tag: 446 New assignment by IANA 448 Summary of the media feature indicated by this feature tag: 449 For variable bit rate encodings The "min-bit-rate" 450 media feature can be specified when "encoding-method" 451 has value "VBR". It is a positive integer 452 specifying bits per second. 454 Values appropriate for use with this feature tag: 455 Signed Integer (only positive values are allowed) 457 The feature tag is intended primarily for use in the following 458 applications, protocols, services, or negotiation mechanisms: 459 IMAP CONVERT extension [CONVERT] 461 Examples of typical use: 463 Related standards or documents: 464 [CONVERT] 466 Considerations particular to use in individual applications, 467 protocols, services, or negotiation mechanisms: 468 None 470 Interoperability considerations: None 472 Security considerations: None 474 Additional information: None 476 Name(s) & email address(es) of person(s) to contact for further 477 information: 478 Alexey Melnikov 480 Intended usage: 481 COMMON 483 Author/Change controller: 484 IETF 486 Requested IANA publication delay: 487 None 489 Other information: 490 None 492 To: "Media feature tags mailing list" 493 494 Subject: Registration of media feature tag frameRate 496 Media feature tag name: 497 frameRate 499 ASN.1 identifier associated with feature tag: 500 New assignment by IANA 502 Summary of the media feature indicated by this feature tag: 503 The "frameRate" media feature can specify the maximum frame 504 rate in frames per second, expressed as a rational (>0) 505 number, for example "49/2". 507 Values appropriate for use with this feature tag: 508 Rational number 510 The feature tag is intended primarily for use in the following 511 applications, protocols, services, or negotiation mechanisms: 512 IMAP CONVERT extension [CONVERT] 514 Examples of typical use: 515 C: b001 CONVERT 2 BINARY[3 ("VIDEO/MP4" ("frameRate" 516 "49/2"))] 518 Related standards or documents: 519 [CONVERT] 521 Considerations particular to use in individual applications, 522 protocols, services, or negotiation mechanisms: 523 None 525 Interoperability considerations: None 527 Security considerations: None 529 Additional information: None 531 Name(s) & email address(es) of person(s) to contact for further 532 information: 533 Alexey Melnikov 535 Intended usage: 536 COMMON 538 Author/Change controller: 539 IETF 541 Requested IANA publication delay: 542 None 544 Other information: 545 None 547 7. Security Considerations 549 [[anchor9: TBD]] 551 8. Acknowledgments 553 This document was reviewed and discussed in the Lemonade WG. Special 554 thanks to Zoltan Ordogh for comments on this document. 556 9. References 558 9.1. Normative References 560 [ABNF] Crocker, D., Ed. and P. Overell, Ed., "Augmented BNF for 561 Syntax Specifications: ABNF", RFC 5234, January 2008. 563 [EXIF] Japan Electronics and Information Technology Industries 564 Association, "Exchangeable image file format for digital 565 still cameras: Exif Version 2.2", JEITIA 2.2, April 2002. 567 [MEDIAFEAT-REG] 568 Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag 569 Registration Procedure", BCP 31, RFC 2506, March 1999. 571 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 572 Requirement Levels", BCP 14, RFC 2119, March 1997. 574 [RFC3676] Gellens, R., "The Text/Plain Format and DelSp Parameters", 575 RFC 3676, February 2004. 577 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 578 October 2008. 580 9.2. Informative References 582 [CONVERT] Melnikov, A. and P. Coates, "Internet Message Access 583 Protocol - CONVERT Extension", RFC 5259, July 2008. 585 [DISPLAY-FEATURES] 586 Masinter, L., Wing, D., Mutz, A., and K. Holtman, "Media 587 Features for Display, Print, and Fax", RFC 2534, 588 March 1999. 590 [MIME-IMT] 591 Freed, N. and N. Borenstein, "MIME (Multipurpose Internet 592 Mail Extensions) Part Two: Media Types", RFC 2046, 593 November 1996. 595 Author's Address 597 Alexey Melnikov 598 Isode Ltd 599 5 Castle Business Village 600 36 Station Road 601 Hampton, Middlesex TW12 2BX 602 UK 604 Email: Alexey.Melnikov@isode.com