PWG> FW: RFC 4142 on Full-mode Fax Profile for Internet Mail (FFPIM)

PWG> FW: RFC 4142 on Full-mode Fax Profile for Internet Mail (FFPIM)

PWG> FW: RFC 4142 on Full-mode Fax Profile for Internet Mail (FFPIM)

McDonald, Ira imcdonald at
Sat Nov 19 10:55:33 EST 2005

-----Original Message-----
From: owner-ietf-fax at [mailto:owner-ietf-fax at]On
Behalf Of rfc-editor at
Sent: Friday, November 18, 2005 6:17 PM
To: ietf-announce at
Cc: rfc-editor at; ietf-fax at
Subject: RFC 4142 on Full-mode Fax Profile for Internet Mail (FFPIM)

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

        RFC 4142

        Title:      Full-mode Fax Profile for Internet Mail (FFPIM)
        Author(s):  D. Crocker, G. Klyne
        Status:     Standards Track
        Date:       November 2005
        Mailbox:    dcrocker at, GK-IETF at
        Pages:      9
        Characters: 16791
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-fax-ffpim-09.txt


Classic facsimile document exchange represents both a set of
technical specifications and a class of service.  Previous work has
replicated some of that service class as a profile within Internet
mail.  The current specification defines "full mode" carriage of
facsimile data over the Internet, building upon that previous work
and adding the remaining functionality necessary for achieving
reliability and capability negotiation for Internet mail, on a par
with classic T.30 facsimile.  These additional features are designed
to provide the highest level of interoperability with the
standards-compliant email infrastructure and mail user agents, while
providing a level of service that approximates what is currently
enjoyed by fax users.

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

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.

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: Sat, 19 Nov 2005 07:55:34 -0800
Size: 869

More information about the Pwg mailing list