3950
DRAFT STANDARD
Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration
Authors: L. McIntyre, G. Parsons, J. Rafferty
Date: February 2005
Area: app
Working Group: fax
Stream: IETF
Obsoletes:
RFC 3250
Abstract
This document describes the registration of the MIME sub-type image/tiff-fx. The encodings are defined by File Format for Internet Fax and its extensions. [STANDARDS-TRACK]
RFC 3950
DRAFT STANDARD
Network Working Group L. McIntyre
Request for Comments: 3950 Consultant
Obsoletes: <a href="./rfc3250">3250</a> G. Parsons
Category: Standards Track Nortel Networks
J. Rafferty
Brooktrout Technology
February 2005
<span class="h1">Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx</span>
<span class="h1">MIME Sub-type Registration</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes the registration of the MIME sub-type
image/tiff-fx. The encodings are defined by File Format for Internet
Fax and its extensions.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document describes the registration of the MIME sub-type
image/tiff-fx. The encodings are defined by File Format for Internet
Fax [<a href="#ref-TIFF-FX" title=""File Format for Internet Fax"">TIFF-FX</a>] and its extensions.
This document is a product of the IETF Internet Fax Working Group.
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 <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>
[<a href="#ref-REQ" title=""Key words for use in RFCs to Indicate Requirement Levels"">REQ</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. TIFF-FX Definition</span>
Tag Image File Format Fax eXtended (TIFF-FX), is defined in detail by
<a href="./rfc3949">RFC 3949</a>, "File Format for Internet Fax" [<a href="#ref-TIFF-FX" title=""File Format for Internet Fax"">TIFF-FX</a>].
<span class="grey">McIntyre, et al. Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
While a brief scope and feature description is provided in this
section as background information, the reader is directed to the
original TIFF-FX specification (File Format for Internet Fax) to
obtain complete feature and technical details.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. TIFF-FX Scope</span>
This document defines a TIFF-based file format specification for
enabling standardized messaging-based fax over the Internet. It
specifies the TIFF fields and field values required for compatibility
with the existing ITU-T Recommendations for Group 3 black-and-white,
grayscale and color facsimile. TIFF has historically been used for
handling fax image files in applications such as store-and-forward
messaging. Implementations that support this file format
specification for import/export may elect to support it as a native
format. This document recommends a TIFF file structure that is
compatible with low-memory and page-level streaming implementations.
Unless otherwise noted, the current TIFF specification [<a href="#ref-TIFF" title="June 3">TIFF</a>] and
selected TIFF Technical Notes [<a href="#ref-TTN1" title="1995">TTN1</a>, <a href="#ref-TTN2" title="2002">TTN2</a>] are the primary references
for describing TIFF and defining TIFF fields. This document is the
primary reference for defining TIFF field values for fax
applications.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. TIFF-FX Features</span>
Some of the features of TIFF-FX are:
- TIFF-FX is capable of describing bilevel, grayscale, palette-
color, full-color and mixed content image data.
- TIFF-FX includes a number of compression schemes that allow
developers to choose the best space or time tradeoff for their
applications.
- TIFF-FX is designed to be extensible and to evolve gracefully as
new needs arise.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MIME Definition</span>
This document defines the image/tiff-fx MIME sub-type to refer to
TIFF-FX Profiles J, C, L and M encoded image data and any future
TIFF-FX extensions, or a subset. The image/tiff-fx content type MAY
be used when black-and-white image data is encoded using TIFF-FX
Profiles S or F, or a subset, however, the image/tiff content type
SHOULD be used.
<span class="grey">McIntyre, et al. Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Registration</span>
To: [email protected]
Subject: Registration of Standard MIME media type image/tiff-fx
MIME media type name: image
MIME subtype name: tiff-fx
Required parameters: none
Optional parameters: none
Encoding Considerations:
This media type consists of binary data. The base64 encoding
should be used on transports that cannot accommodate binary data
directly.
Security considerations:
TIFF-FX utilizes a structure which can store image data and
attributes of this image data. The fields defined in the TIFF-FX
specification are of a descriptive nature and provide information
that is useful to facilitate viewing and rendering of images by a
recipient. As such, the fields currently defined in the TIFF-FX
specification do not in themselves create additional security
risks, since the fields are not used to induce any particular
behavior by the recipient application.
TIFF-FX has an extensible structure, so that it is theoretically
possible that fields could be defined in the future which could be
used to induce particular actions on the part of the recipient,
thus presenting additional security risks, but this type of
capability is not supported in the referenced TIFF-FX
specification. Indeed, the definition of fields which would
include such processing instructions is inconsistent with the
goals and spirit of the TIFF-FX specification.
The MIME type and file extension defined by this document MUST NOT
be used to blindly select a processing program. It is up to the
implementation to determine the application (if necessary) and
render the image to the user.
<span class="grey">McIntyre, et al. Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
Interoperability considerations:
The ability of implementations to handle all the defined
applications (or profiles within applications) of TIFF-FX may not
be ubiquitous. As a result, implementations may decode and
attempt to display the encoded TIFF-FX image data only to
determine that the image cannot be rendered.
Published specification:
TIFF-FX (Tag Image File Format Fax eXtended) is defined in:
<a href="./rfc3949">RFC 3949</a>, "File Format for Internet Fax", February 2005, Buckley,
R., Venable, D., McIntyre, L., Parsons, G., and J. Rafferty.
Applications which use this media type:
Imaging, fax, messaging and multi-media
Additional information:
Magic number(s):
II (little-endian): 49 49 2A 00 hex
MM (big-endian): 4D 4D 00 2A hex
File extension(s): .TFX
Macintosh File Type Code(s): TFX
Person & email address to contact for further information:
Lloyd McIntyre
[email protected]
Glenn W. Parsons
[email protected]
James Rafferty
[email protected]
Intended usage: COMMON
Change controller: Lloyd McIntyre
<span class="grey">McIntyre, et al. Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
TIFF-FX utilizes a structure which can store image data and
attributes of this image data. The fields defined in the TIFF-FX
specification are of a descriptive nature and provide information
that is useful to facilitate viewing and rendering of images by a
recipient. As such, the fields currently defined in the TIFF-FX
specification do not in themselves create additional security risks,
since the fields are not used to induce any particular behavior by
the recipient application.
TIFF-FX has an extensible structure, so that it is theoretically
possible that fields could be defined in the future which could be
used to induce particular actions on the part of the recipient, thus
presenting additional security risks, but this type of capability is
not supported in the referenced TIFF-FX specification. Indeed, the
definition of fields which would include such processing instructions
is inconsistent with the goals and spirit of the TIFF-FX
specification.
The MIME type and file extension defined by this document MUST NOT be
used to blindly select a processing program. It is up to the
implementation to determine the application (if necessary) and render
the image to the user.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-TIFF-FX">TIFF-FX</a>] Buckley, R., Venable, D., McIntyre, L., Parsons, G., and J.
Rafferty, "File Format for Internet Fax", <a href="./rfc3949">RFC 3949</a>,
February 2005.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-TIFF">TIFF</a>] Adobe Developers Association, TIFF (TM) Revision 6.0 -
Final, June 3, 1992.
[<a id="ref-REQ">REQ</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-TTN1">TTN1</a>] Adobe PageMaker 6.0 TIFF Technical Notes, Sept. 14, 1995,
<a href="http://partners.adobe.com/asn/developer/pdfs/tn/TIFFPM6.pdf">http://partners.adobe.com/asn/developer/pdfs/tn/TIFFPM6.pdf</a>
[<a id="ref-TTN2">TTN2</a>] Adobe Photoshop TIFF Technical Notes, Replacement TIFF/JPEG
specification, March 22, 2002,
<a href="http://partners.adobe.com/asn/developer/pdfs/tn/TIFFphotoshop.pdf">http://partners.adobe.com/asn/developer/pdfs/tn/</a>
<a href="http://partners.adobe.com/asn/developer/pdfs/tn/TIFFphotoshop.pdf">TIFFphotoshop.pdf</a>
<span class="grey">McIntyre, et al. Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
Annex A. List of edits to <a href="./rfc3250">RFC 3250</a>
+----+---------+-------------------------------------------------+
| No.| Section | Edit |
+----+---------+-------------------------------------------------+
| 1. | All | Updated references from <a href="./rfc2301">RFC 2301</a> to |
| | | <a href="./draft-ietf-fax-tiff-fx-13.txt">draft-ietf-fax-tiff-fx-13.txt</a> |
+----+---------+-------------------------------------------------+
| 2. | 5 | MIME Definition - added a "SHOULD" statement to |
| | | stress that image/tiff is the preferred content |
| | | type when representing Profiles S and/or F. |
+----+---------+-------------------------------------------------+
| 3. | 7 | Revise security considerations. |
+----+---------+-------------------------------------------------+
| 4. | 3 | Merged sections <a href="#section-2">2</a> & 3 and renumbered. |
+----+---------+-------------------------------------------------+
<span class="grey">McIntyre, et al. Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
Authors' Addresses
Lloyd McIntyre
10328 S. Stelling Road
Cupertino, CA 95014 USA
Phone: +1-408-725-1624
EMail: [email protected] or
[email protected]
Glenn W. Parsons
Nortel Networks
P.O. Box 3511, Station C
Ottawa, ON K1Y 4H7
Canada
Phone: +1-613-763-7582
Fax: +1-613-967-5060
EMail: [email protected]
James Rafferty
Brooktrout Technology
410 First Avenue
Needham, MA 02494
USA
Phone: +1-781-433-9462
Fax: +1-781-433-9268
EMail: [email protected]
<span class="grey">McIntyre, et al. Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc3950">RFC 3950</a> image/tiff-fx February 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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 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 IETF's procedures with respect to rights in IETF Documents can
be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
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
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
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-
[email protected].
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
McIntyre, et al. Standards Track [Page 8]
Annotations
Select text to annotate