Debian Codegraph @

rfc1789.html

raw
1 <pre>Network Working Group C. Yang
2 Request for Comments: 1789 University of North Texas
3 Category: Informational April 1995
4
5
6 <span class="h1">INETPhone: Telephone Services and Servers on Internet</span>
7
8 Status of this Memo
9
10 This memo provides information for the Internet community. It does
11 not specify an Internet standard of any kind. Distribution of this
12 memo is unlimited.
13
14 IESG Note
15
16 Internet Engineering Steering Group comment from the Transport Area
17 Director: Please note well that this memo is an individual product of
18 the author. Work on standards and technology related to this topic
19 is additionally taking place in the IETF in the Multiparty MUltimedia
20 SessIon Control Working Group (MMUSIC).
21
22 Abstract
23
24 INETPhone is a true telephone service through the Internet. It
25 integrates the local telephone networks and the Internet using
26 INETPhone servers. Thus a long distance call can be split into two
27 local calls and an Internet connection, which is transparent to end
28 users. Such a phone service through Internet will be a major step
29 towards integrated services on Internet. In order to support the
30 INETPhone and lay down the ground rules of the service, a scheme of
31 "open partnership" is proposed, so that the entire Internet community
32 can have the equal opportunity and benefits from the INETPhone
33 service.
34
35 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
36
37 The success of traditional Internet services, such as the electronic
38 mail, the file transfer, and the remote machine access, has inspired
39 a row of new network applications -- the world-wide information web,
40 voice and video conferencing, and network telemarketing are just a
41 few to mention. With the further development in infrastructure and
42 the architecture of integrated, multimedia information services
43 [<a href="#ref-1" title="&quot;Network Access to Multimedia Information&quot;">1</a>,<a href="#ref-2" title="&quot;Integrated Services in the Internet Architecture: an Overview&quot;">2</a>,<a href="#ref-3" title="&quot;A Vision of an Integrated Internet Information Service&quot;">3</a>], certainly the Internet will play a crucial role in shaping
44 up the future of so-called information super-highway.
45
46 Among many new applications, the voice communication through Internet
47 bears perhaps the most potential impact, since it competes directly
48 with the telephone communication, which has become an indispensable
49
50
51
52 <span class="grey">Yang [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1789">RFC 1789</a> Telephone Service and Servers on Internet April 1995</span>
55
56
57 part of the modern society. Recently, many software packages are
58 available, either commercially or as public free-ware, which supports
59 voice communication on Internet. Some of these products are targeted
60 directly as possible substitution for long distance telephone
61 services. However, so far, all such products only support voice
62 communications using a computer that is on the Internet or is
63 connected, via a SLIP link, to the Internet [<a href="#ref-4" title="&quot;Computer Telephone Integration&quot;">4</a>].
64
65 This RFC presents a true telephone service, called INETPhone, which
66 supports voice communication through the Internet. INETPhone
67 integrates the local phone network with the Internet. The phone
68 network provides local access of INETPhone service with the existing
69 telephone facilities, whereas the Internet delivers the packets of
70 voice communication over long distances. The service of INETPhone is
71 illustrated by the following scenario. Assuming a user at area A
72 wants to call another user in area B. The user first makes a local
73 call to an INETPhone server in area A. After the connection, the user
74 keys in the remote phone number in area B to the server. Then the
75 server in area A makes a connection to another INETPhone server in
76 area B, and requests the remote server to dial, as a local call, the
77 phone number in area B. Therefore, a long distance phone connection
78 between users in area A and B is established via two local phone
79 connections and one Internet connection between two INETPhone
80 servers.
81
82 The INETPhone provides a general service of voice communication on
83 Internet compatible to the existing telephone service. The
84 motivation in developing and experimenting the INETPhone service can
85 be two-folds: on the one hand, a general telephone service on the
86 Internet will be a major step towards integrated services on Internet
87 and a great challenge to the future development of Internet
88 infrastructure and protocol architecture; on the other hand, the
89 entire Internet community can take the advantage from the cheap and
90 convenient voice communication of the INETPhone service.
91
92 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Design Philosophy</span>
93
94 The design philosophy of the INETPhone differs from the most of
95 current voice communication services on Internet in three basic
96 aspects: integrating the existing telephone networks with the
97 Internet; using the INETPhone servers to carry out the task of voice
98 packet delivery on Internet; and an open-partnership of establishing
99 the INETPhone service on Internet. The discussion of each of these
100 aspects is given as follows.
101
102 The conventional telephone service is the most popular and convenient
103 means for voice communication across distances. Any serious effort to
104 integrate voice communication on the Internet should take the full
105
106
107
108 <span class="grey">Yang [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1789">RFC 1789</a> Telephone Service and Servers on Internet April 1995</span>
111
112
113 advantage of this well-established service. The INETPhone bridges
114 the existing telephone network with the Internet, so that the access
115 of the INETPhone service will be totally based on the local phone
116 services and facilities. This will lead to a much easier access and
117 broader user population than the approaches of computer-based access.
118
119 The INETPhone service is based on the client-server model, in which a
120 group of INETPhone servers are responsible for accepting/initiating
121 local calls and deliverying voice packets across the Internet. The
122 general users (as clients) can easily access the service through a
123 conventional phone with a local call. The creation of such INETPhone
124 servers eases the burden from general users, and provides services of
125 voice communication on the Internet in a more efficient and
126 manageable manner.
127
128 Hundreds even thousands of INETPhone servers will be required for the
129 wide coverage of INETPhone services on the Internet (to cover all
130 areas within US, at least one server needs to be installed in each
131 area of phone area code). Instead of letting few industrials
132 monopolize such a service on the Internet, an alternative approach
133 based on an open-partnership scheme of INETPhone service is proposed
134 (see <a href="#section-5">Section 5</a>), which will give equal opportunity and benefits to
135 the entire Internet community.
136
137 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. INETPhone Servers</span>
138
139 The central components of the INETPhone service are its servers on
140 Internet. The server acts as a gateway between the telephone network
141 and the Internet. For this purpose, the server will have both
142 interfaces to a computer network and the telephone network.
143 Currently, there are many commercial telephone interface cards
144 available on the market (such as Dialogic's Voice Boards [<a href="#ref-5" title="&quot;Voice Hardware Reference&quot;">5</a>]), which
145 support various telephone operations of detecting/generating
146 telephone signals (ring, DTMF, etc. [<a href="#ref-6" title="&quot;Introduction to Telephones and Telephone Systems&quot;">6</a>]), receiving/initiating phone
147 calls, recording (digitizing and compressing) or playing back audio
148 signals, and monitoring the progress of a phone call.
149
150 With the support of necessary hardware interfaces, the function of an
151 INETPhone server includes:
152
153 (a) Receive a local call or accept a connection from a remote
154 server;
155
156 (b) Identify the PIN of a local call and determine if to proceed
157 the call or not;
158
159 (c) Accept a phone number for remote dialing from a local call;
160
161
162
163
164 <span class="grey">Yang [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1789">RFC 1789</a> Telephone Service and Servers on Internet April 1995</span>
167
168
169 (d) Look up the local directory for a remote server of a
170 requested call;
171
172 (e) Make a connection to a remote server;
173
174 (f) Make a local phone call upon the request of a remote server;
175
176 (g) Maintain full-duplex, real-time exchanges of voice packets
177 via Internet;
178
179 (h) Maintain information exchanges with Directory Servers (see
180 <a href="#section-4">Section 4</a>);
181
182 (i) Handle exceptional conditions, such as long delay or drop of
183 voice packets;
184
185 (j) Monitor quality of service and keep accounting information.
186
187 The above listed functions represent probably the minimal
188 requirements for each INETPhone server. Some further important
189 features, such as compression/decompression, security, multicasting,
190 and voice mail need also to be considered when a real service of
191 INETPhone is launched on the Internet. Since a general public of the
192 Internet community might be involved in this proposed INETPhone
193 service, it is probably necessary to set an open standard in the
194 building of INETPhone servers (see <a href="#section-5">Section 5</a>).
195
196 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Directory Servers</span>
197
198 The main philosophy behind the INETPhone service is to reduce a long
199 distance phone call into two local calls and an Internet connection.
200 Therefore, an INETPhone server will always be identified by its IP
201 address with its local area code of the phone number (also possibly
202 with its sub-regional number). In order to support a dynamic
203 configuration of INETPhone servers on the Internet, a Directory
204 Server(s) (DS) will be required to map between IP address and area
205 code of INETPhone servers, which in some sense, is similar to the
206 functions of a Name Server (such as the BIND [<a href="#ref-7" title="&quot;DNS and BIND&quot;">7</a>]). After an
207 INETPhone server is installed on the Internet, it needs to register
208 itself with a DS. The mapping information at DS will be disseminated
209 to INETPhone servers for the search of a remote server in response to
210 a requested phone call. Local cache of mapping information may also
211 be maintained at INETPhone servers to alleviate communications
212 between INETPhone servers and Directory Server(s). Again, the
213 function of a Directory Server for the INETPhone may require another
214 open specification.
215
216
217
218
219
220 <span class="grey">Yang [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1789">RFC 1789</a> Telephone Service and Servers on Internet April 1995</span>
223
224
225 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Open Partnership</span>
226
227 Voice communication and telephone service are important parts for
228 providing integrated information services over the Internet. With
229 the current trends of commercialized services over the Internet,
230 sooner or later, some kind of telephone services will be launched on
231 the Internet by some private companies. On the other hand, the
232 operation of the INETPhone service will depend on the installment of
233 enough INETPhone servers over the Internet, which can be achieved
234 through a cooperative effort of the entire Internet community. This
235 RFC proposes an open-partnership scheme for the INETPhone service,
236 which provides equal opportunity and benefits to the entire Internet
237 community.
238
239 An outline of the proposed open-partnership scheme is listed as
240 follows:
241
242 (a) Any organization or individual person can join or withdraw
243 from this open-partnership on a voluntary base.
244
245 (b) In order to join the partnership (therefore becoming a member
246 of the partnership), an organization or a person should at
247 least install and maintain an INETPhone server on the
248 Internet with the equal capacity of lines for call-in and
249 dial-out services.
250
251 (c) Each member of the partnership has the equal right to use the
252 INETPhone service through any INETPhone servers on the
253 Internet. All services will bear the same charges based on
254 the number of bytes transmitted through the Internet and
255 whatever the rate (if any) laid down by the Internet
256 authority.
257
258 (d) A not-for-profit consortium will be formed from the
259 representatives of all members of the partnership. The main
260 task of the consortium is to establish all regulations and
261 specifications of the INETPhone service, and to coordinate
262 the execution of these rules by all the members.
263
264 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Recommendation</span>
265
266 If there is enough interests in the INETPhone service from the
267 Internet community, the IAB may need to consider forming a special
268 task force or working group to further look into the matter.
269
270
271
272
273
274
275
276 <span class="grey">Yang [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1789">RFC 1789</a> Telephone Service and Servers on Internet April 1995</span>
279
280
281 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
282
283 [<a id="ref-1">1</a>] Adie, C., "Network Access to Multimedia Information", <a href="./rfc1614">RFC 1614</a>,
284 Edinburgh University, May 1994.
285
286 [<a id="ref-2">2</a>] Braden, R., Clark, D., and S. Shenker, "Integrated Services in
287 the Internet Architecture: an Overview", <a href="./rfc1633">RFC 1633</a>, ISI, MIT,
288 Xerox PARC, June 1994.
289
290 [<a id="ref-3">3</a>] Weider, C., and P. Deutsch, "A Vision of an Integrated Internet
291 Information Service", <a href="./rfc1727">RFC 1727</a>, Bunyip Information Systems,
292 December 1994.
293
294 [<a id="ref-4">4</a>] Walters, R., "Computer Telephone Integration", Artech House
295 Publishers, Norwood, MA, 1994.
296
297 [<a id="ref-5">5</a>] Dialogic Corporation, "Voice Hardware Reference", Parsippany, NJ,
298 1994.
299
300 [<a id="ref-6">6</a>] Noll, M., "Introduction to Telephones and Telephone Systems", 2nd
301 Ed., Artech House Publishers, Norwood, MA, 1991.
302
303 [<a id="ref-7">7</a>] Albitz, P., and C. Liu, "DNS and BIND", O'Reilly &amp; Associates,
304 Sebastopol, Calif., 1992.
305
306 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
307
308 Security will be an important issue in the INETPhone service. As a
309 general proposal, however, this RFC chooses to leave this topic for
310 future discussions.
311
312 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgement</span>
313
314 This RFC is based on a currently undergoing project supported by the
315 Department of Computer Science, University of North Texas.
316
317 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Author's Address</span>
318
319 Cui-Qing Yang
320 Dept. of Computer Science
321 University of North Texas
322 P.O. Box 13886
323 Denton, TX 76203
324
325 Phone: (817) 565-2822
326 Fax: (817) 565-2799
327 EMail: [email protected]
328
329
330
331
332 Yang [Page 6]
333 </pre>