As per Relevance of the word recipient, we have this rfc below:
Network Working Group L.
Request for Comments: 2542 Xerox
Category: Informational March 1999
Terminology and Goals for Internet
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document defines a number of terms useful for the discussion
Internet Fax. In addition, it describes the goals of the Internet
working group and establishes a baseline of desired
against which protocols for Internet Fax can be judged.
encompasses the goals for all modes of facsimile delivery,
'real-time', 'session', and 'store and forward'. Different levels
desirability are indicated throughout the document
Table of
1. Introduction .................................................. 2
2. Definitions and Operational Modes ............................. 3
2.1 User model of fax ........................................... 3
2.2 Definition of Internet Fax .................................. 4
2.3 Internet Fax Roles .......................................... 5
2.4 Internet Fax Devices ........................................ 5
2.5 Operational modes ........................................... 8
3. Goals for Internet Fax ........................................ 8
4. Operational Goals for Internet Fax ............................ 9
4.1 Functionality ............................................... 9
4.2 Interoperability ............................................ 9
4.3 Confirmation ................................................ 10
4.4 Quick Delivery .............................................. 11
4.5 Capabilities ................................................ 12
4.6 Simplicity .................................................. 12
4.7 Security .................................................... 13
4.8 Reliability ................................................. 14
4.9 Fax-like use ................................................ 14
4.10 Legal ...................................................... 15
Masinter Informational [Page 1]
RFC 2542 Terminology and Goals for Internet Fax March 1999
5. Functional Goals for Internet Fax ............................. 15
5.1 Goals for image data representation ......................... 15
5.2 Goals for transmission ...................................... 16
5.3 Goals for addressing ........................................ 16
5.4 Goals for security .......................................... 17
5.5 Goals for capability exchange ............................... 17
6. Security Considerations ....................................... 18
7. Acknowledgements .............................................. 18
8. Author's Address .............................................. 18
9. References .................................................... 19
10. Full Copyright Statement ..................................... 20
1.
Facsimile (Fax) has a long tradition as a telephony application
sending a document from one terminal device to another
Many mechanisms for sending fax documents over the Internet have
demonstrated and deployed and are currently in use. The
application of using the Internet for facsimile is called "
Fax".
This document defines a number of terms useful for the discussion
Internet Fax. In addition, it describes the goals for Internet Fax
establishes a baseline of desired functionality against
protocols for Internet Fax can be judged. It encompasses the goals
all modes of facsimile delivery, including "real-time", "session",
"store and forward" (terms defined in Section 2 of this document).
1.1 Terminology used within this
Within this document, different levels of desirability for a
for Internet Fax are indicated by different priorities, indicated
{braces}:
{1} there is general agreement that this is a
characteristic of any definition of Internet Fax
{2} most believe that this is an important
of Internet Fax
{3} there is general belief that this is a useful
of Internet Fax, but that other factors might override
a definition that does not provide this element
acceptable
Masinter Informational [Page 2]
RFC 2542 Terminology and Goals for Internet Fax March 1999
In addition, the following terms are used
"service" An operational service offered by a service provider
"application" A use of systems to perform a particular function
"terminal" The endpoint of a communication application
"goal" An objective of the standarization process
2. Definitions and Operation
This section defines some of the basic terms for Internet Fax
2.1 User model of fax and basic
The phrase "traditional facsimile" or "G3Fax" is used to
implementations of [T.30]. Facsimile (fax) is a telephony
for sending a document from one terminal device to another
The telephone network is often referred to as the Public
Telephone Network (PSTN) or Global Switched Telephone Network (GSTN).
Communication over the telephone network is accomplished
modems. The transmission of data end-to-end is accompanied
negotiation (to ensure that the scanned data can be rendered at
recipient) and confirmation of delivery (to give the sender
that the final data has been received and processed.) Over time
facsimile has been extended to allow for PCs using fax modems to
and receive fax, to send data other than scanned facsimile images.
addition, there have been many extensions to the basic image model
to allow for additional compression methods and for representation
images with grey-scale and color. Other delivery extensions
included sub-addressing (additional signals after the call
established to facilitate automated routing of faxes to desktops
mailboxes), and enhanced features such as fax-back and polling
Typically, the terminal device consists of a paper input
(scanner), a paper output device (printer), with (a limited
of) processing power. Traditional facsimile has a simple
operational model; the
1) inserts paper into a
2) dials a number corresponding to the
3) presses the 'start' button on the
4) the sending device connects to the receiving device using
telephone
5) the sending device scans the paper and transmits the image
the
6) simultaneously, the remote device receives the transmission
prints the image on
Masinter Informational [Page 3]
RFC 2542 Terminology and Goals for Internet Fax March 1999
7) upon completion of transmission and successful processing
the recipient, the sending user is notified of
Although not usually visible to the user, the operation (5)
transmission consists
5a) negotiation: the capabilities of the recipient are obtained
and suitable mutually available parameters for
communication are
5b) scanning: creating digitized images of pages of a
5c) compression: the image data is encoded using a
compression
5d) transmission: the data is sent from one terminal to the
In addition, the terminiation of operations (5d) and (6) may
characterized as consisting of
6a) completed delivery: the message has completed
6b) completed receipt: the message has been accepted by
6c) processing and disposition: the message has been
From a protocol perspective, the information conveyed in
transmission consists of both "protocol" (control information
capabilities, identification) and also "document content".
The document content consists primarily of the "document image"
additional metadata accompanying the image. The means by which
image of a document is encoded within the fax content is the "
data representation".
When the fax has been successfully transmitted, the sender receives
"confirmation": an indication that the fax content was delivered
This "confirmation" is an internal signal and is not normally
to the sending user, although some error messages are visible,
allow a page to be retransmitted
2.2 Definition of Internet
The phrase "Internet Fax" is used to denote an application
supports an approximation to the user model of fax (Section 2.1),
where Internet protocols are used instead of the telephone
for (some portion of) the transmission. The exact modes
operations of traditional facsimile need not be duplicated exactly
Masinter Informational [Page 4]
RFC 2542 Terminology and Goals for Internet Fax March 1999
2.3 Internet Fax
Internet Fax is a document transmission mechanism between
different devices and roles. Those devices and roles might come in
wide variety of configurations. To allow for a wide variety
configurations, it is useful to separate out the roles, as they
be made available separately or in combination. These roles are
* Network
A device that can scan a paper document and transmit the
image via the
* Network
A device that can accept an image transmission via the
and print the received document
* Fax onramp
A device that can accept a facsimile telephone call
automatically forward it via the
* Fax offramp
A device that can accept a transmission from the Internet
forward it to a traditional fax
In addition, other traditional Internet applications might
participate in Internet Fax, including Internet mail users,
browsers, Internet printing hosts
2.4 Internet Fax
The Internet Fax roles may be embedded in a variety of
and configurations within devices and larger applications. They
be combined with other elements, e.g., a traditional T.30 fax device
Many different configurations of applications and systems should {2}
be able to participate in Internet Fax; the specification should
unnecessarily restrict the range of devices, applications
services that can participate
A device that supports Internet Fax might support any combination
the roles defined in 2.3.
2.4.1 Gateway
A traditional fax terminal has a telephone line connection (GSTN
with a fax modem used to connect over the telephone network.
connect a fax terminal to the Internet requires a service
offers connections on one side to the GSTN using standard
signals, and on the other side to the Internet. This role might
Masinter Informational [Page 5]
RFC 2542 Terminology and Goals for Internet Fax March 1999
performed by a "relay" (e.g., transmitting T.30 signals over real
time controlled TCP connections) or a "gateway" (e.g.,
T.30 to TIFF/email).
With these applications, the role of Internet Fax is to transport
fax content across the Internet, e.g.,
[fax-term]-GSTNfax->[onramp]-Internet Fax->[recipient
[sender]-Internet Fax->[offramp]-GSTNFax->[fax-term
A onramp and/or offramp application may be local to a single
terminal. For example, the gateway application might exist within
small device which has a telephone interface on one side and
network connection on the other. To the fax machine, it looks like
telephone connection, although it might shunt some or all
to Internet Fax instead (Such devices are called "Bump-in-cord.")
An onramp or offramp application may be a local facility serving
fax terminals. For example, outgoing telephone fax calls through
company telephone PBX could be rerouted through a local onramp.
internet to telephone outbound connection could be part of a "
Fax" package
Onramps and offramps may serve a wider area or broader collection
users, e.g., services run by service bureaus, offering
services; the telephone sender or the recipient might subscribe
the service
The target of an offramp may be a "hunt group": a set of
numbers, each of which have a possibly different fax
attached
2.4.2 New "Internet Fax"
Manufacturers may offer new devices which support any combination
the roles defined in setion 2.3. In particular, a device resembling
traditional fax terminal, built out of similar components (scanner
processor, and printer), could offer a similar functionality to
traditional facsimile terminal, but be designed to connect to
Internet rather than, or in addition to, a telephone line connection
Such devices might have a permanent Internet connection (through
LAN connection) or might have occasional connectivity through
(data) modem to an Internet Service Provider
Masinter Informational [Page 6]
RFC 2542 Terminology and Goals for Internet Fax March 1999
2.4.3 Internet
Internet users using Internet hosts with standard application
must {1} be able to exchange faxes with other participants
Internet Fax, with minimum required enhancements to their
environment
Interoperability with Internet mail users, either as Internet
senders or recipients, is highly desirable {2}.
Internet users might receive faxes over the Internet and display
on their screens, or have them automatically printed when received
Similarly, the Internet Fax messages originating from the user
be the output of a software application which would normally print
or specially constructed fax-sending software, or may be
directly from a scanner attached to the user's terminal
The Internet Fax capability might be integrated into
fax/network fax software or email software, e.g., by the addition
printer drivers that would render the document to the
content-type and cause it to be delivered using an Internet
protocol
In some cases, the user might have a multi-function peripheral
integrated a scanner and printer and which gave operability
to that of the stand-alone fax terminal
2.4.4 Internet
In Internet mail, there are a number of components that operate
the infrastructure to perform additional functions beyond
store-and-forward. Interoperability with these components is
consideration for the store and forward profile of Internet Fax.
example, mailing list software accepts mail to a single address
forwards it to a distribution list of many users. Mail
software creates repositories of searchable messages. Mail
operate at organizational boundaries and scan incoming messages
malicious or harmful mail attachments. Vacation programs send
messages to the senders of messages when the recipient is on
and not available to respond
2.4.5 Universal
Many software vendors are now promoting software packages
support "universal messaging": a combined communication package
combines electronic mail, voice mail, and fax
Masinter Informational [Page 7]
RFC 2542 Terminology and Goals for Internet Fax March 1999
2.5 Operational Modes for Internet
Facsimile over the Internet can occur in several modes
"Store and forward" Internet Fax entails a process of storing
entire document at a staging point, prior to transmitting it to
next staging point. Store and forward can be directly between
and recipient or can have a series of intermediary staging points
The intermediate storage may involve an intermediate agent
sequence of agents in the communication
"Session" Internet Fax is defined such that delivery notification
provided to the transmitting terminal prior to disconnection.
"store and forward", there is an expection that direct communication
negotiation, and retransmission can take place between the
endpoints
"Real-time" Internet Fax allows for two [T.30] standard
terminals to engage in a document transmission in a way that all
the essential elements of the [T.30] communication protocol
preserved and there is minimal elongation of the session as
to Group 3 fax over the GSTN
These modes are different in the end-user expectation of immediacy
reliability, and in the ease of total compatibility with legacy
traditional facsimile terminals; the modes may have
requirements on operational infrastructure connecting sender
recipient
3. Goals for Internet
Facsimile over the Internet must define the mechanisms by which
document is transmitted from a sender to a recipient, and must {1}
specify the following elements
- Transmission protocol: what Internet protocol(s) and
are used? What options are available in that transmission
- Data formats: what image data representation(s) are used
appropriate, required, within the transmission protocol?
other data representations are supported
- Addressing: How are Internet Fax recipients identified? How
recipient identification be represented in user directories?
are traditional fax terminals addressed
Masinter Informational [Page 8]
RFC 2542 Terminology and Goals for Internet Fax March 1999
- Capabilities: The capabilities of the sender to
different kinds of image data representations may be known
the recipient, and the capabilities, preferences,
characteristics of the recipient may be known to the sender.
are the capabilities, preferences, and characteristics
senders and recipients expressed, and communicated to
other
- Security: Faxes may be authenticated as to their origin,
secured to protect the privacy of the message. How may
authenticity of a fax be determined by the recipient? How
the privacy of a message be guaranteed
Specific goals for these elements are described in section 5.
4. Operational Goals for Internet
This section lists the necessary and desirable traits of an
Fax protocol
4.1
Traditionally, images sent between fax machines are transmitted
the global switched telephone network. An Internet Fax protocol
{1} provide for a method to accomplish the most commonly
features of traditional fax using only Internet protocols. It
desirable {3} for Internet Fax to support all standard features
modes of standard facsimile
4.2
It is essential {1} that Internet Fax support
between most of the devices and applications listed in section 2,
desirable {3} to support all of them. To "support interoperability
means that a compliant sender attempting to send to a
recipient will not fail because of incompatibility
Overall interoperability requires {1} interoperability for all of
protocol elements: the image data representations must be understood
the transport protocol must function, it must be possible to
all manner of terminals, the security mechanism must not
manual operations in devices that are intended for
operation, and so forth
Interoperability with Internet mail user agents is a requirement {1}
only for the "store-and-forward" facsimile, although it would
useful {3} for "session" and "real-time" modes of delivery
Internet Fax
Masinter Informational [Page 9]
RFC 2542 Terminology and Goals for Internet Fax March 1999
The requirement for interoperability has strong implications for
protocol design. Interoperability must not {1} depend on having
same kind of networking equipment at each end
As with most Internet application protocols, interoperability
{1} be independent of the nature of the networking link, whether
simple IP-based LAN, an internal private IP networks, or the
Internet. The standard for Internet Fax must {1} be "global":
is, a single specification which does not have or require
features of the transport mechanism for local operations
If Internet Fax is to use the Internet mail transport mechanisms,
must {1} interoperate consistently with the current Internet
environment, and, in particular, with the non-terminal devices
in section 2.4.4. If Internet Fax messages might arrive in user'
mailboxes, it is required {1} that the protocol
successfully with common user practices for mail messages:
them in databases, retransmission, forwarding, creation of
digests, replay of old messages at times long after the
receipt, and replying to messages using non-fax equipment
It is desirable {3} that the Internet Fax standard support
facilitate universal messaging systems described in section 2.4.5.
If Internet Fax requires additions to the operational
(services, firewall support, gateways, quality of service,
extensions), then it is preferable {3} if those additions are
for other applications than Fax. Features shared with other
applications (voice mail, short message service, paging, etc.)
desirable {3}, so as not to require different operational changes
other applications
4.3
In almost all applications of traditional fax, it is considered
important that the user can get an assurance that the
data was received by a terminal at the address dialed by the user
This goal translates to the Internet environment. The 'Internet Fax
application must {1} define the mechanisms by which a sender
request notification of the completion of transmission of
message, and receive a determinate response as to whether the
was delivered, not delivered, or that no confirmation of delivery
possible
Originally, fax "confirmation" implied that the message was
and processed, e.g., delivered to the output paper tray of
recipient fax device. In reality, this implication was relying
Masinter Informational [Page 10]
RFC 2542 Terminology and Goals for Internet Fax March 1999
a signal produced by the receiving terminal that the incoming
had been inspected and was determined to be of reasonable (
unacceptable) quality, via an unspecified algorithm
In later devices which support error correction mode, the ECM
(per [T.30]) enabled error checking via a specific algorithm
providing a more exact indication that the bits within the
image were not corrupted during transmission. With the addition
memory buffering, PC-based fax modems and the more common use
error correction mode, traditional fax confirmation still
some assurance of processability; (e.g., a fax modem would not
able to receive an incoming fax if it required compression
that were not supported) without reporting on whether the image
been printed or viewed
Consequently, the fax confirmation is not the same as a
that the message was "read": that a human had confirmed that
message was received. It is desirable {3}, but not required,
Internet Fax support confirmation that a message has been read (
and beyond the confirmation that the message has been delivered).
4.4 Quick
In many cases, fax transmission is used for delivery of
where there is a strong user requirement for timeliness, with
guarantees that if transmission begins at all, it will
quickly. For example, it is a common practice to fax documents
discussion to other participants in a telephone conference call
to the call
Internet Fax should {2} allow the sender of a document to
immediate delivery, if such delivery is possible. In such cases,
should {2} be possible for the sender of a message to avoid
the message at all, if quick delivery is not available for
particular recipient
It is desirable {3} to have the protocol for requesting
delivery be the same as, or similar to, the protocol for
delivery, so that two separate mechanisms are not required
For real-time fax delivery, immediate delivery is the norm, since
protocol must guarantee that when the session connecting sender
recipient has terminated, the message has been delivered to
ultimate recipient
Masinter Informational [Page 11]
RFC 2542 Terminology and Goals for Internet Fax March 1999
4.5 Capabilities: reliable, upgrade
Traditionally, facsimile has guaranteed interworking between
and recipients by having a strict method of negotiation of
capabilities between the two devices. The image representation
facsimile originally was a relatively low resolution, but
increasingly offered additional capabilities (higher resolution
color) as options
The use of fax has grown in an evolving world (from 'Group 1'
'Group 2', to 'Group 3' facsimile) because of two elements: (a)
useful baseline of capabilities that all terminals implemented,
(b) the use of capabilities exchange to go beyond that
To accommodate current use as well as future growth, Internet
should {2} have a simple minimum set of required features that
guarantee interoperability, as well as a mechanism by which
capability devices can be deployed into a network of lower
devices while ensuring interoperability. If recipients with
capabilities were, for example, to merely drop non-minimum
without warning, the result would be that no non-minimum
could be sent reliably. This situation can be avoided in a variety
ways, e.g., through communication of recipient capabilities or
sending multiple renditions
The exchange of capabilities in Internet Fax should {2} be robust.
accomplish this, recipients should {2} be encouraged to
capabilities, even while senders must {1} have a way to send
to recipients whose capabilities are unknown
Even minimum-capability recipients of messages should {2} be
to provide a capability indication in some reliable way. This
be accomplished by providing an entry in a directory service,
offering automatic or semi-automatic replies, or by sending
indication of in a reply to a message with multiple renditions, or
an addition to a negative acknowledgement requiring retransmission
On the other hand, for reliability, senders cannot rely on
information of recipients before transmission. That is,
reliability, senders should {2} have an operational mode which
function when capabilities are not present, even when recipients
always provide capabilities
4.6
Internet Fax should not {2} require terminals to possess a
amount of processing power, and a base level implementation must {1}
interoperate, even if it does not offer complex processing
Masinter Informational [Page 12]
RFC 2542 Terminology and Goals for Internet Fax March 1999
Internet Fax should {2} allow interoperability with recipient
which have limited buffering capabilities and cannot buffer an
fax message prior to printing, or cannot buffer an entire set of
pages before beginning transmission of scanned pages
Different operational modes (real-time, session, store and forward
might use different protocols, in order to preserve the simplicity
each
It is preferable {3} to make as few restrictions and additions
existing protocols as possible while satisfying the
requirements. It is important {2} that it be possible to
Internet Fax end-to-end in the current Internet environment
any changes to the existing infrastucture, although some features
require adoption of existing standards
4.7 Security: Cause No Harm, Allow for
The widespread introduction of Internet Fax must {1} not cause harm
either to its users or to others. For example, an automatic
for returning notification of delivery or capabilities of
recipients by email must {1} not expose the users or others to
loops, bombs, or replicated delivery. Automatic capability
based on email might not be sufficiently robust and,
sufficient precautions, might expose users to denial of
attacks, or merely the bad effects of errors on the part of
administrators. Similar considerations apply in these areas to
that have been addressed by work on electronic mail
acknowledgements [RFC 2298].
Internet Fax should {2} not, by default, release information that
users consider private, e.g., as might be forthcoming in response
a broadcast requests for capabilities to a company's Internet
devices. Public recipients of Internet Fax (e.g., public
which accept facsimile messages) should {2} not be required
broadcast messages with capability statements to all
senders in order to receive facsimile messages appropriate for
capabilities of their device
The possibility for "causing harm" might be created by a
of facilities and other features which individually may be viewed
harmless. Thus, the overall operation of a network full of
Fax devices must {1} be considered
Interoperation with ITU defined T.30 fax security methods, as well
standard Internet e-mail security methods is desirable {3}.
Masinter Informational [Page 13]
RFC 2542 Terminology and Goals for Internet Fax March 1999
4.8
The Internet Fax protocol should {2} operate reliably over a
of configurations and situations
In particular, operations which rely on time-delayed
might result in inconsistent information, and the protocol should
robust even in such situations
For example, in a store-and-forward message environment,
capabilities and preferences of a fax recipient might be used by
sender to construct an appropriate message, e.g., sending a color
to a color device but a black and white fax to a device that does
have color capability. However, the information about
capabilities must be accessible to the sender even when the
cannot be contacted directly. Thus, the sender must access
capabilities in some kind of storage mechanism, e.g., a directory.
directory of recipient capabilities is a kind of
database, and would be subject to all of the well-known failure
of distributed databases. For example, update messages
capability descriptions might be delivered out of order, from
archives, might be lost, non-authenticated capability
might be spoofed or widely distributed by malicious senders.
Internet Fax protocol should {2} be robust in these situations
messages should {2} not be lost or misprocessed even when
sender's knowledge of recipient capabilities are wrong, and
mechanisms for delivery of recipient capabilities should {2} be used
4.9 User
The primary user experience with fax is
immediate
delivery
ease of
The primary user experience with email is
delayed
no delivery
ability to reply to
easy to send to multiple
An Internet Fax standard should {2} attempt to reconcile
differences between the two environments
Masinter Informational [Page 14]
RFC 2542 Terminology and Goals for Internet Fax March 1999
4.10
An Internet Fax standard should {2} accomodate the legal
for facsimile, and attempt to support functionality similar to
legally required even for devices that do not operate over the
switched telephone network
The United States Federal Communication Commission
(applicable only within the USA) state
Identification Required on Fax
The FCC's rules require that any message sent to a fax
must clearly mark on the first page or on each page of
message
* the date and time the transmission is sent
* the identity of the sender;
* the telephone number of the sender or of the sending
machine
All fax machines manufactured on or after December 20, 1992
all facsimile modem boards manufactured on or after December 13,
1995 must have the capability to clearly mark such
information on the first page or on each page of
transmission."
5. Functional Goals for Internet
These goals for specific elements of Internet Fax follow from
operational goals described in section 4.
5.1 Goals for image and other data
Interoperability with Internet Mail or other transmission
that cause data files to appear in Internet terminal
requires {1} that Internet Fax use a format for images that is
wide use
Interoperability with Internet Mail requires {2} that Internet
recipients handle those message types that are common in the
environment, including a minimum set of MIME mail formats
Interoperability with traditional fax terminals requires {1} that
data format be capable of representing the commonly used
mechanisms defined for traditional facsimile; support for _all
standard formats defined for traditional facsimile is
desirable {2}. In addition, interoperability with 'private use
Masinter Informational [Page 15]
RFC 2542 Terminology and Goals for Internet Fax March 1999
facsimile messages suggests {3} that the standard
arbitrary bit sequences
5.2 Goals for
It is necessary {1} that Internet Fax to work in the context of
current Internet, Intranet, and the combination across firewalls
A single protocol with various extensions is preferable {3}
multiple separate protocols, if there are devices that might require
at different times and for different recipients, different protocols
5.3 Goals for
Interoperability with the terminal types in section 2 requires {1}
the ability to address each of the kinds of recipient devices.
address of a recipient must give sufficient information to allow
sender to initiate communication
Interoperability with offramps to legacy fax terminals requires {1}
that the message contain some way of addressing the final
of facsimile messages, including telephone numbers, various
addressing modes, and facsimile sub-addresses
Interoperability with Internet Mail requires {1} that it be
to address Internet Fax to any email address. Interworking
Internet mail also requires {1} that the addressing is in the
addressing headers, including mail transport envelope [RFC1123]
RFC822 headers, as appropriate. The information must {1}
nowhere else
Sending devices might not have local storage for directories
addresses, and addresses might be cumbersome for users to type in
For these reasons, Internet Fax devices may require configuration
locate directories of recipients and their capabilities
The source of a fax message must {1} be clearly identified.
address of the appropriate return message (whether via fax or
email) should {2} be clearly identified in a way that is visible
all manner of recipients. In the case of Internet Fax delivered
email, it should {2} be possible to use the normal 'reply'
for email to return a message to the sender
Traditionally, it is common for the first page of a fax message
to a facsimile terminal to contain an (image) representation of
name, address, return number, etc. of the sender of the document
Some legal jurisdictions for facsimile require an identification
the sender on every page. The standard for Internet Fax should {2}
Masinter Informational [Page 16]
RFC 2542 Terminology and Goals for Internet Fax March 1999
cover the issues of sender and recipient identification in the
where fax messages are re-routed, forwarded, sent through gateways
5.4 Goals for
Users typically use GSTN-based fax for confidential
transmission, assuming a similar or higher level of
and protection from both deliberate and inadvertent eavesdropping
holds for telephone conversations; the higher level
confidentiality arising from the requirement for non-
equipment to intercept and interpret an overheard fax transmission
Similarly, in traditional fax there is an expectation (and, in
contexts, a legally recognized assurance) that the received fax
unaltered from the document originally transmitted
It is important {2} that Internet Fax give users a level of
for privacy and integrity that is as good or better than
available for telephone-based fax. The Internet Fax standard
{2} specify how secure messages can be sent, in an
fashion. The Internet Fax protocol should {2} encourage
introduction of security features, e.g., by requiring that
capability devices still accept signed messages (even if ignoring
signature.)
In the case where the sender is responsible for payment for
services in a remote location, it is desirable {3} to provide
authentication and authorization of the sender, as well as
billing related information from the offramp to be
securely
5.5 Goals for capabilities
Traditional fax supports a wide range of devices, including
resolution ("Superfine"); recent enhancements include methods
color and a variety of compression mechanisms. Fax messaging
the capability for "non-standard frames", which allow vendors
introduce proprietary data formats. In addition, facsimile
"binary file transfer": a method of sending arbitrary binary data
a fax message
To support interoperability with these mechanisms, it should {2}
possible to express a wide variety of fax capabilities
Capability support has three elements: expression of the
of the sender (as far as a particular message is concerned),
expressing the capabilities of a recipient (in advance of
transmission of the message), and then the protocol by
Masinter Informational [Page 17]
RFC 2542 Terminology and Goals for Internet Fax March 1999
capabilities are exchanged
The Internet Fax standard should {2} specify a uniform mechanism
capabilities expression. If capabilities are being sent at
other than the time of message transmission, then capabilities
{2} include sufficient information to allow it to be validated
authenticated, etc
The Internet Fax standard may {3} include one or several methods
transmission, storage, or distribution of capabilities
A request for capability information, if sent to a recipient at
time other than the immediate time of delivery of the message,
{2} clearly identify the sender, the recipient whose capabilities
being requested, and the time of the request. Som kind of
would be useful, too
A capability assertion (sent from recipient to sender) should {2}
clearly identify the recipient and some indication of the date/
or range of validity of the information inside. To be secure
capability assertions should {2} be protected against
and the substitution of valid data by invalid data
6. Security
This document describes the goals for the Internet Fax protocol
including the security goals. An Internet Fax protocol must {1}
address the security goals and provide adequate measures to
users with expected security features
7.
The author gratefully acknowledges the contributions of Graham Klyne
Vivian Cancio, Dan Wing, Jim Dahmen, Neil Joffe, Mike Lake,
McIntyre, Richard Shockey, Herman Silbiger, Nadesan Narenthiran
George Pajari and Dave Crocker for their valuable comments on
document
8. Author's
Larry
Xerox
3333 Coyote Hill
Palo Alto, CA 94304
http://www.parc.xerox.com/
Fax: (650) 812-4333
EMail: masinter@parc.xerox.
Masinter Informational [Page 18]
RFC 2542 Terminology and Goals for Internet Fax March 1999
9.
[T.30] "Procedures for Document Facsimile Transmission in
General Switched Telephone Network", ITU-T (CCITT),
Recommendation T.30, July, 1996.
[F.185] "Internet facsimile: Guidelines for the support of
communication of facsimile documents", ITU-T (CCITT),
Recommendation F.185, 1998.
[T.37] "Procedures for the transfer of facsimile data via store
and-forward on the Internet", ITU-T (CCITT),
T.37, 1998.
[T.38] "Procedures for real time Group 3 facsimile
between terminals using IP Networks", ITU-T (CCITT),
Recommendation T.38, 1998.
[RFC2305] Toyoda, K., Ohno, H., Murai, J. and D. Wing, "A Simple
of Facsimile Using Internet Mail", RFC 2305, March 1998.
[RFC2298] Fajman, R., "An Extensible Message Format for
Disposition Notifications", RFC 2298, March 1998.
[RFC1123] Braden, R., "Requirements for Internet hosts -
and Support", STD 3, RFC 1123, October 1989.
Masinter Informational [Page 19]
RFC 2542 Terminology and Goals for Internet Fax March 1999
10. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Masinter Informational [Page 20]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
