Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration

The image/tiff-fx sub-type is defined to cover Profiles J, C, L and M (and future extensions) while deferring to image/tiff for the simpler black-and-white Profiles S and F, preserving backward compatibility with existing TIFF deployments.

Implementations may not universally support all defined TIFF-FX profiles; a receiver may decode and attempt to display TIFF-FX image data only to find it cannot render the image due to unsupported profile features.

The image/tiff-fx content type MAY be used when black-and-white image data is encoded using TIFF-FX Profiles S or F, however the image/tiff content type SHOULD be used instead.

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 and render the image to the user.

security

Binary encoding of image/tiff-fx data requires base64 encoding on transports that cannot accommodate binary data directly.

Registers the MIME sub-type image/tiff-fx for TIFF-FX encoded image data. Required parameters: none. Optional parameters: none. File extension: .TFX. Magic numbers: 49 49 2A 00 (little-endian) and 4D 4D 00 2A (big-endian).

registry

TIFF-FX fields are descriptive in nature and do not induce particular behavior by the recipient application, so they do not in themselves create additional security risks. However, TIFF-FX's extensible structure means future fields could theoretically induce recipient actions, though this is inconsistent with the specification's goals.

security