RFC 4161: Guidelines for Optional Services for Internet Fax Gateways
In plain English — editorial summary, not part of the RFC
To allow connectivity between the general switched telephone network facsimile service (GSTN fax) and the e-mail-based Internet Fax service (i-fax), an "Internet Fax Gateway" is required. This document provides guidelines for the optional functionality of Internet Fax Gateways. In this context, an "offramp gateway" provides facsimile data transmission from i-fax to GSTN fax; vice versa, an "onramp gateway" provides data transmission from GSTN fax to i-fax. The recommendations in this document apply to the integrated service including Internet Fax terminals, computers with i-fax software on the Internet, and GSTN fax terminals on the GSTN. This document supplements the recommendation for minimal features of an Internet Fax Gateway. In particular, it covers techniques for dropping duplicated fax messages, automatic fax re-transmission, error, return notice, and log handling, and possible authorization methods by DTMF (Dual Tone Multi-Frequency) for onramp gateways. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4161
- Published
- September 2005
- Authors
- K. Mimura; K. Yokoyama; T. Satoh; K. Watanabe; C. Kanaide
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4160Internet Fax Gateway RequirementsCurrent
September 2005
- RFC 4154Voucher Trading System Application Programming Interface (VTS-API)Current
September 2005
- RFC 4153XML Voucher: Generic Voucher LanguageCurrent
September 2005
- RFC 4143Facsimile Using Internet Mail (IFAX) Service of ENUMUpdated
November 2005
- RFC 4142Full-mode Fax Profile for Internet Mail (FFPIM)Current
November 2005
- RFC 4141SMTP and MIME Extensions for Content ConversionCurrent
November 2005
- RFC 4112Electronic Commerce Modeling Language (ECML) Version 2 SpecificationCurrent
June 2005
- RFC 4236HTTP Adaptation with Open Pluggable Edge Services (OPES)Current
November 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?