RFC1789 on Telephone Service and Servers on Internet
"Joyce K. Reynolds" <jkrey@isi.edu> Mon, 17 April 1995 18:43 UTC
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06607; 17 Apr 95 14:43 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10701; 17 Apr 95 14:43 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06572; 17 Apr 95 14:43 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06471; 17 Apr 95 14:39 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa10599; 17 Apr 95 14:39 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA18260>; Mon, 17 Apr 1995 11:39:44 -0700
Message-Id: <199504171839.AA18260@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1789 on Telephone Service and Servers on Internet
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 17 Apr 1995 11:41:09 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 1789: Title: INETPhone: Telephone Services and Servers on Internet Author: C. Yang Date: April 1995 Mailbox: cqyang@cs.unt.edu Pages: 6 Characters: 14,186 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1789.txt INETPhone is a true telephone service through the Internet. It integrates the local telephone networks and the Internet using INETPhone servers. Thus a long distance call can be split into two local calls and an Internet connection, which is transparent to end users. Such a phone service through Internet will be a major step towards integrated services on Internet. In order to support the INETPhone and lay down the ground rules of the service, a scheme of "open partnership" is proposed, so that the entire Internet community can have the equal opportunity and benefits from the INETPhone service. IESG Note: Internet Engineering Steering Group comment from the Transport Area Director: Please note well that this memo is an individual product of the author. Work on standards and technology related to this topic is additionally taking place in the IETF in the Multiparty MUltimedia SessIon Control Working Group (MMUSIC). 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@ISI.EDU 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 admin@DS.INTERNIC.NET. 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@ISI.EDU. Please consult RFC 1543, Instructions to RFC Authors, for further information. Joyce K. Reynolds 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.
- RFC1789 on Telephone Service and Servers on Inter… Joyce K. Reynolds