IFX> FW: RFC 3250 on Tag Image File Format Fax eXtended (TIFF-FX) - im age/tiff-fx MIME Sub-type Registration

IFX> FW: RFC 3250 on Tag Image File Format Fax eXtended (TIFF-FX) - im age/tiff-fx MIME Sub-type Registration

Hastings, Tom N hastings at cp10.es.xerox.com
Thu Sep 26 12:08:00 EDT 2002



-----Original Message-----
From: rfc-editor at rfc-editor.org [mailto:rfc-editor at rfc-editor.org]
Sent: Wednesday, September 25, 2002 17:32
Cc: rfc-editor at rfc-editor.org; ietf-fax at imc.org
Subject: RFC 3250 on Tag Image File Format Fax eXtended (TIFF-FX) -
image/tiff-fx MIME Sub-type Registration



A new Request for Comments is now available in online RFC libraries.


        RFC 3250

        Title:	    Tag Image File Format Fax eXtended (TIFF-FX) -
                    image/tiff-fx MIME Sub-type Registration
        Author(s):  L. McIntyre, G. Parsons, J. Rafferty
        Status:	    Standards Track
	Date:       September 2002
        Mailbox:    lmcintyre at pahv.xerox.com,
                    gparsons at nortelnetworks.com, jraff at brooktrout.com
        Pages:      7
        Characters: 17876
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-fax-tiff-fx-reg-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3250.txt


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.

This document is a product of the Internet Fax Working Group of the
IETF.

This is now a Proposed 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

        help: ways_to_get_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
unlimited distribution.echo 
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
Subject: 
Date: Wed, 25 Sep 2002 23:28:22 -0700
Size: 869
Url: http://www.pwg.org/archives/ifx/attachments/20020926/0eb5c8d3/attachment-0001.mht


More information about the Ifx mailing list