From: owner-ietf-fax at mail.imc.org [mailto:owner-ietf-fax at mail.imc.org]On
Behalf Of rfc-editor at rfc-editor.org
Sent: Wednesday, February 09, 2005 7:08 PM
To: ietf-announce at ietf.org
Cc: rfc-editor at rfc-editor.org; ietf-fax at imc.org
Subject: RFC 3949 on File Format for Internet Fax
A new Request for Comments is now available in online RFC libraries.
Title: File Format for Internet Fax
Author(s): R. Buckley, D. Venable, L. McIntyre, G. Parsons,
Status: Standards Track
Date: February 2005
Mailbox: rbuckley at crt.xerox.com, dvenable at crt.xerox.com,
lloyd10328 at pacbell.net, gparsons at nortel.com,
jraff at brooktrout.com
I-D Tag: draft-ietf-fax-tiff-fx-14.txt
This document is a revised version of RFC 2301. The revisions,
summarized in the list attached as Annex B, are based
on discussions and suggestions for improvements that have been
made since RFC 2301 was issued in March 1998, and on the results of
independent implementations and interoperability testing.
This RFC 2301 revision describes the Tag Image File Format (TIFF)
representation of image data specified by the International
Telecommunication Union (ITU-T) Recommendations for black-and-white
and color facsimile. This file format specification is commonly known
as TIFF for Fax eXtended (TIFF-FX). It formally defines minimal,
extended, and lossless Joint Bi-level Image experts Group (JBIG)
profiles (Profiles S, F, J) for black-and-white fax and base JPEG,
lossless JBIG, and Mixed Raster Content profiles (Profiles C, L, M)
for color and grayscale fax. These profiles correspond to the content
of the applicable ITU-T Recommendations.
This document is a product of the Internet Fax Working Group of the
This is now a Draft Standard Protocol.
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.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Date: Thu, 10 Feb 2005 05:32:44 -0800