< draft-ietf-fax-service-v2-04.txt   draft-ietf-fax-service-v2-05.txt >
Network Working Group K. Toyoda Network Working Group K. Toyoda
Internet Draft H. Ohno Internet Draft H. Ohno
September 3, 2001 J. Murai October 23, 2001 J. Murai
Expires March 2002 WIDE Project Expires April 2002 WIDE Project
Obsoletes: RFC2305 D. Wing Obsoletes: RFC2305 D. Wing
draft-ietf-fax-service-v2-04.txt Cisco draft-ietf-fax-service-v2-05.txt Cisco
A Simple Mode of Facsimile Using Internet Mail A Simple Mode of Facsimile Using Internet Mail
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. Internet-Drafts are with all provisions of Section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), working documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other groups may also its areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
To view the entire list of current Internet-Drafts, please check
the "1id-abstracts.txt" listing contained in the Internet-Drafts
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
(US West Coast).
This draft is a product of the IETF Internet Fax working group. To This draft is a product of the IETF Internet Fax working group. To
subscribe to the mailing list, send a message to subscribe to the mailing list, send a message to
ietf-fax-request@imc.org with the line "subscribe" in the body of the ietf-fax-request@imc.org with the line "subscribe" in the body of the
message. Archives are available from <http://www.imc.org/ietf-fax>. message. Archives are available from <http://www.imc.org/ietf-fax>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999,2000). All Rights Reserved. Copyright (C) The Internet Society (1999,2000). All Rights Reserved.
SUMMARY ABSTRACT
This document is a revised version of RFC 2305.
The revisions, summarized in the list attached as Appendix B to this
document, are based on the suggestions for improvements that have been
made since RFC 2305 was issued in March 1998. There are no technical
changes from RFC2305.
This specification provides for "simple mode" carriage of facsimile This specification provides for "simple mode" carriage of facsimile
data using Internet mail. Extensions to this document will follow. data using Internet mail. Extensions to this document will follow.
The current specification employs standard protocols and file formats The current specification employs standard protocols and file formats
such as TCP/IP, Internet mail protocols [1, 2, 3], MIME [4, 10, 11], such as TCP/IP, Internet mail protocols [1, 2, 3], MIME [4, 10, 11],
and TIFF for Facsimile [5, 12, 14]. It can send images not only to and TIFF for Facsimile [5, 12, 14]. It can send images not only to
other Internet-aware facsimile devices but also to Internet-native other Internet-aware facsimile devices but also to Internet-native
systems, such as PCs with common email readers which can handle MIME systems, such as PCs with common email readers which can handle MIME
mail and TIFF for Facsimile data. The specification facilitates mail and TIFF for Facsimile data. The specification facilitates
communication among existing facsimile devices, Internet mail agents, communication among existing facsimile devices, Internet mail agents,
and the gateways which connect them. and the gateways which connect them.
The IETF has been notified of intellectual property rights claimed in This document is a revision of RFC 2305. There have been no technical
regard to some or all of the specification contained in this changes.
document. For more information consult the online list of claimed
rights in <http://www.ietf.org/ipr.html>.
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 [13].
1 SCOPE 1 INTRODUCTION
This specification defines message-based facsimile communication This specification defines message-based facsimile communication
over the Internet. It describes a minimum set of capabilities, over the Internet. It describes a minimum set of capabilities,
taking into account those of typical facsimile devices and PCs that taking into account those of typical facsimile devices and PCs that
can generate facsimile data. can generate facsimile data.
A G3Fax device has substantial restrictions due to specifications in A G3Fax device has substantial restrictions due to specifications in
the standards, such as for timers. This specification defines a the standards, such as for timers. This specification defines a
profile for Internet mail, rather than creating a distinct "facsimile profile for Internet mail, rather than creating a distinct "facsimile
over the Internet" service. The semantics resulting from the profile over the Internet" service. The semantics resulting from the profile
skipping to change at page 3, line 16 skipping to change at page 2, line 52
A facsimile-capable device that uses T.4 [15] and the general switched A facsimile-capable device that uses T.4 [15] and the general switched
telephone network (GSTN) is called a "G3Fax device" in this telephone network (GSTN) is called a "G3Fax device" in this
specification. An "IFax device" is an Internet- accessible device specification. An "IFax device" is an Internet- accessible device
capable of sending, receiving or forwarding Internet faxes. A capable of sending, receiving or forwarding Internet faxes. A
message can be sent to an IFax device using an Internet mail message can be sent to an IFax device using an Internet mail
address. A message can be sent to a G3Fax device using an Internet address. A message can be sent to a G3Fax device using an Internet
mail address; the message MAY be forwarded via an IFax offramp mail address; the message MAY be forwarded via an IFax offramp
gateway. gateway.
1.2 Cases 1.2 Cases
This specification provides for communication between each of the This specification provides for communication between each of the
following combinations: following combinations:
Internet mail => Network printer Internet mail => Network printer
Internet mail => Offramp gateway (forward to Internet mail => Offramp gateway (forward to
G3Fax) G3Fax)
Network scanner => Network printer Network scanner => Network printer
Network scanner => Offramp gateway (forward to Network scanner => Offramp gateway (forward to
G3Fax) G3Fax)
Network scanner => Internet mail Network scanner => Internet mail
1.3 Intellectual Property
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights in <http://www.ietf.org/ipr.html>.
1.4 Key Words
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 [13].
2 COMMUNICATION PROTOCOLS 2 COMMUNICATION PROTOCOLS
The set of conventions necessary to achieve facsimile- compatible The set of conventions necessary to achieve facsimile- compatible
service covers basic data transport, document data formats, message service covers basic data transport, document data formats, message
(document) addressing, delivery confirmation, and message security. (document) addressing, delivery confirmation, and message security.
In this section, the first 4 are covered. The remainder are covered In this section, the first 4 are covered. The remainder are covered
in following sections, along with additional details for addressing in following sections, along with additional details for addressing
and formats. and formats.
2.1 Transport 2.1 Transport
skipping to change at page 12, line 40 skipping to change at page 12, line 40
| | | following references to make them very | | | | following references to make them very |
| | | non-normative. | | | | non-normative. |
| | | "OpenPGP Message Format", RFC2440 | | | | "OpenPGP Message Format", RFC2440 |
| | | "Securiy Architecture for the IP", RFC2401 | | | | "Securiy Architecture for the IP", RFC2401 |
| | | "SMTP Service Extensions for Secure SMTP over | | | | "SMTP Service Extensions for Secure SMTP over |
| | | TLS", RFC2487 | | | | TLS", RFC2487 |
| | | "S/MIME Version 2 Message Specification", | | | | "S/MIME Version 2 Message Specification", |
| | | RFC2311 | | | | RFC2311 |
+----+----------+-------------------------------------------------+ +----+----------+-------------------------------------------------+
| 4. |REFERENCES| Removed the following references because they | | 4. |REFERENCES| Removed the following references because they |
| | | are non-nomartive | | | | are non-normative |
| | | "SMTP Service Extensions for Delivery Status | | | | Notifications", RFC1891 | | | | "SMTP Service Extensions for Delivery Status |
| | | Notifications", RFC1891 |
| | | "Internet Message Access Protocol", RFC2060 | | | | "Internet Message Access Protocol", RFC2060 |
+----+----------+-------------------------------------------------+ +----+----------+-------------------------------------------------+
| 5. |REFERENCES| Separated REFERENCES to the normative and | | 5. |REFERENCES| Separated REFERENCES to the normative and |
| | | non-normative | | | | non-normative |
+----+----------+-------------------------------------------------+ +----+----------+-------------------------------------------------+
| 6. |Appendix | Changed the phrase from "NOT REQUIRED" to | | 6. |Appendix | Changed the phrase from "NOT REQUIRED" to |
| | A | "not required" | | | A | "not required" |
+----+----------+-------------------------------------------------+ +----+----------+-------------------------------------------------+
| 7. |Appendix | Added "Appendix B List of edits to RFC2305" | +----+----------+-------------------------------------------------+ | 7. |Appendix | Added "Appendix B List of edits to RFC2305" |
+----+----------+-------------------------------------------------+
10 Full Copyright Statement 10 Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
 End of changes. 12 change blocks. 
32 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/