4142
PROPOSED STANDARD
Full-mode Fax Profile for Internet Mail (FFPIM)
Authors: D. Crocker, G. Klyne
Date: November 2005
Area: app
Working Group: fax
Stream: IETF
Abstract
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. [PROPOSED STANDARD]
RFC 4142
PROPOSED STANDARD
Network Working Group D. Crocker
Request for Comments: 4142 Brandenburg
Category: Standards Track G. Klyne
Nine by Nine
November 2005
<span class="h1">Full-mode Fax Profile for Internet Mail (FFPIM)</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
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.
<span class="grey">Crocker & Klyne Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Content Negotiation . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. UA-based Content Negotiation. . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. ESMTP-based Content Negotiation . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Interactions between UA and ESMTP Negotiation Mechanisms. . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Content Format . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5.1">5.1</a>. Normative References. . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5.2">5.2</a>. Informative References. . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#appendix-A">A</a>. Direct Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#appendix-B">B</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This specification defines "full mode" carriage of facsimile data
over the Internet, building upon previous work in A Simple Mode of
Facsimile Using Internet Mail [<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>] and Extended Facsimile Using
Internet Mail [<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>]. This specification also adds the remaining
functionality necessary to achieve reliable and capable negotiation
for Internet mail, on par with classic [<a href="#ref-T30" title=""Procedures for Document Facsimile Transmission in the General Switched Telephone Network"">T30</a>] 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 closely
approximates the level of service currently enjoyed by fax users.
Basic terminology is discussed in [<a href="./rfc2542" title=""Terminology and Goals for Internet Fax"">RFC2542</a>]. Implementations that
conform to this specification MUST also conform to [<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>] and
[<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>].
The new features are designed to be interoperable with the existing
base of mail transfer agents (MTAs) and mail user agents (MUAs), and
to take advantage of existing standards for optional functionality
(e.g., positive delivery confirmation and disposition notification).
Enhancements described in this document utilize the existing Internet
email messaging infrastructure, where possible, instead of creating
fax-specific features that are unlikely to be implemented in non-fax
messaging software.
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="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Crocker & Klyne Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Content Negotiation</span>
Classic facsimile service is interactive, such that a sending station
can discover the capabilities of the receiving station, prior to
sending a facsimile of a document. This permits the sender to
transmit the best quality of facsimile supported by both the sending
station and the receiving station. Internet mail is
store-and-forward, with potentially long latency, such that
before-the-fact negotiation is problematic.
Use of a negotiation mechanism permits senders to transfer a richer
document form than is permitted when using the safer-but-universal
default form. Without this mechanism, the sender of a document
cannot be certain that the receiving station will be able to support
the form.
The capabilities that can be negotiated by an FFPIM participant are
specified in [<a href="./rfc2534" title=""Media Features for Display, Print, and Fax"">RFC2534</a>] and [<a href="./rfc2879" title=""Content Feature Schema for Internet Fax (V2)"">RFC2879</a>]. Implementations that are
conformant to FFPIM MUST support content negotiation as described
there.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. UA-based Content Negotiation</span>
One method for exchanging the capabilities information uses a
post-hoc technique, which permits an originator to send the best
version known to be supported by the recipient, and to also send a
better suited version if the recipient requests it. This mechanism
is specified in [<a href="./rfc3297" title=""Content Negotiation for Messaging Services based on Email"">RFC3297</a>]. FFPIM implementations MUST support this
mechanism.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. ESMTP-based Content Negotiation</span>
Another method uses an ESMTP option specified in [<a href="./rfc4141" title=""SMTP and MIME Extensions for Content Conversion"">RFC4141</a>]. It
requires support for content negotiation along the entire path the
email travels. Using this mechanism, receiving ESMTP servers are
able to report capabilities of the addresses (mailboxes) they
support, and sending email clients are able to signal both permission
and constraints on conversions.
FFPIM participants MAY support this mechanism.
NOTE: This specification provides for content conversion by
unspecified intermediaries. Use of this mechanism carries
significant risk. Although intermediaries always have the ability
to perform damaging transformations, use of this specification
could result in more exploitation of that potential and,
therefore, more misbehavior. Use of intermediaries is discussed
in [<a href="./rfc3238" title=""IAB Architectural and Policy Considerations for Open Pluggable Edge Services"">RFC3238</a>].
<span class="grey">Crocker & Klyne Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Interactions between UA and ESMTP Negotiation Mechanisms</span>
FFPIM participants must ensure that their use of the UA and ESMTP
methods for content negotiation is compatible. For example, two
mechanisms might consult two different repositories of capabilities
information, and those repositories might contain different
information. Presumably, this means that at least one of these
repositories is inaccurate. Therefore, the larger problem is one of
correctness, rather than synchronization.
This specification does not require a particular method of using the
mechanisms together.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Content Format</span>
FFPIM allows the transfer of enhanced TIFF data relative to [<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>]
and [<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>]. The details for these enhancements are contained in
[<a href="./rfc3949" title=""File Format for Internet Fax"">RFC3949</a>]. Implementations that are conformant to FFPIM SHOULD
support TIFF enhancements.
It should also be noted that the content negotiation mechanism
permits a sender to know the full range of content types that are
supported by the recipient. Therefore, requirements for support of
TIFF represent a functional minimum for FFPIM.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
As this document is an extension of [<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>] and [<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>], the
Security Considerations sections of [<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>] and [<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>] apply to
this document, including discussion of PGP and S/MIME use for
authentication and privacy.
It appears that the mechanisms added by this specification do not
introduce new security considerations. However, the concerns raised
in [<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>] are particularly salient for these new mechanisms.
Use of this specification should occur with particular attention to
the following security concerns:
* Negotiation can be used as a denial of service attack.
* Negotiation may lead to the use of an unsafe data format.
* Negotiation discloses information and therefore raises privacy
concerns.
<span class="grey">Crocker & Klyne Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
Use of the ESMTP CONNEG option permits content transformation by an
intermediary, along the mail transfer path. When the contents are
encrypted, the intermediary cannot perform the conversion, because it
is not expected to have access to the relevant secret keying
material. When the contents are signed, but not encrypted,
conversion will invalidate the signature. Therefore, permission to
convert SHOULD NOT normally be used with signed or sealed messages.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-RFC4141">RFC4141</a>] Toyoda, K. and D. Crocker, "SMTP and MIME Extensions for
Content Conversion", <a href="./rfc4141">RFC 4141</a>, November 2005.
[<a id="ref-RFC3949">RFC3949</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.
[<a id="ref-RFC2119">RFC2119</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-RFC2532">RFC2532</a>] Masinter, L. and D. Wing, " Extended Facsimile Using
Internet Mail", <a href="./rfc2532">RFC 2532</a>, March 1999.
[<a id="ref-RFC2534">RFC2534</a>] Masinter, L., Wing, D., Mutz, A., and K. Holtman, "Media
Features for Display, Print, and Fax", <a href="./rfc2534">RFC 2534</a>, March
1999.
[<a id="ref-RFC2542">RFC2542</a>] Masinter, L., "Terminology and Goals for Internet Fax", <a href="./rfc2542">RFC</a>
<a href="./rfc2542">2542</a>, March 1999.
[<a id="ref-RFC2879">RFC2879</a>] Klyne, G. and L. McIntyre, "Content Feature Schema for
Internet Fax (V2)", <a href="./rfc2879">RFC 2879</a>, August 2000.
[<a id="ref-RFC3297">RFC3297</a>] Klyne, G., Iwazaki, R., and D. Crocker, "Content
Negotiation for Messaging Services based on Email", <a href="./rfc3297">RFC</a>
<a href="./rfc3297">3297</a>, July 2002.
[<a id="ref-RFC3965">RFC3965</a>] Toyoda, K., Ohno, H., Murai, J., and D. Wing, "A Simple
Mode of Facsimile Using Internet Mail", <a href="./rfc3965">RFC 3965</a>, December
2004.
<span class="grey">Crocker & Klyne Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-RFC3238">RFC3238</a>] Floyd, S. and L. Daigle, "IAB Architectural and Policy
Considerations for Open Pluggable Edge Services", <a href="./rfc3238">RFC 3238</a>,
January 2002.
[<a id="ref-T30">T30</a>] ITU-T (CCITT), "Procedures for Document Facsimile
Transmission in the General Switched Telephone Network",
Recommendation T.30, July 1996.
<span class="grey">Crocker & Klyne Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Direct Mode</span>
Email is a store-and-forward service, typically with highly variable
delay between the time a message leaves the sender's realm and the
time it arrives in the receiver's realm. The number of relays
between sender and receiver is also unknown and variable. By
contrast, facsimile is generally considered to be direct and
immediate.
An email profile that fully emulates facsimile must solve several
different problems. One is to ensure that the document
representation semantics are faithful. Another is that the
interaction between sender and receiver is similar to that of
telephony-based facsimile. In particular, it must ensure the
timeliness of the interaction. The specifications for FFPIM and its
predecessors enable email to emulate the former, the information
(semantics) activities of facsimile.
The ESMTP CONNEG option sets the stage for achieving the latter, with
email-based facsimile transfer that has interactive negotiations, on
a par with telephony-based facsimile. The key, additional
requirement is to achieve timeliness. Ultimately, timeliness
requires configuring sender and receiver email servers to interact
directly. The sender's MTA must directly contact the receiver's MTA.
With typical email service configurations, the content and
interaction semantics of facsimile can be emulated quite well, but
timeliness cannot be assured.
To achieve direct sending, the originating MTA must not use
sending-side intermediaries such as outbound enterprise MTAs.
Instead, it must be configured to do transmissions directly to hosts
specified in email addresses, based on queries to the public DNS. To
achieve direct receiving, the target MTAs must have DNS A records,
without MX records. That is, they also must be configured not to use
intermediaries.
The sender may then use ESMTP Conneg to determine the capabilities of
the receiver. Afterwards the sender will use the capabilities
information to tailor the TIFF message content it sends.
<span class="grey">Crocker & Klyne Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 2005</span>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Acknowledgements</span>
The IETF Fax working group, in collaboration with the IETF and the
ITU, has diligently participated in a multi-year effort to produce
Internet-based emulation of classic facsimile via email profiles.
The effort benefited from the group's willingness to provide an
initial, minimal mechanism, and then develop the specification to
include more facsimile features as implementation and operation
experience was gained.
Authors' Addresses
Dave Crocker
Brandenburg InternetWorking
675 Spruce Drive
Sunnyvale, CA 94086
USA
Phone: +1.408.246.8253
EMail: [email protected]
Graham Klyne
Nine by Nine
UK
Phone:
EMail: [email protected]
<span class="grey">Crocker & Klyne Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc4142">RFC 4142</a> FFPIM November 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 procedures with respect to rights in RFC 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.
Crocker & Klyne Standards Track [Page 9]
Annotations
Select text to annotate