From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Fri Sep 02 2005 - 13:19:04 EDT
-----Original Message-----
From: owner-ietf-fax@mail.imc.org [mailto:owner-ietf-fax@mail.imc.org]On
Behalf Of rfc-editor@rfc-editor.org
Sent: Thursday, September 01, 2005 2:24 PM
To: ietf-announce@ietf.org
Cc: rfc-editor@rfc-editor.org; ietf-fax@imc.org
Subject: RFC 4160 on Internet Fax Gateway Requirements
A new Request for Comments is now available in online RFC libraries.
RFC 4160
Title: Internet Fax Gateway Requirements
Author(s): K. Mimura, K. Yokoyama, T. Satoh, C. Kanaide,
C. Allocchio
Status: Informational
Date: August 2005
Mailbox: mimu@miyabi-labo.net, keiyoko@msn.com,
zsatou@t-ns.co.jp, icemilk77@yahoo.co.jp,
Claudio.Allocchio@garr.it
Pages: 13
Characters: 24930
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-fax-gateway-protocol-12.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4160.txt
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
recommendations for the 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 form 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 is a product of the Internet Fax Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@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@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.
attached mail follows:
This archive was generated by hypermail 2.1.4 : Thu Apr 16 2009 - 10:55:40 EDT