Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!think!ames!ucbcad!ucbvax!OPAL.BERKELEY.EDU!minshall
From: minshall@OPAL.BERKELEY.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Dial-up TCP/IP (was interactive SMTP over phone lines)
Message-ID: <8705121740.AA16793@opal.berkeley.edu>
Date: Tue, 12-May-87 13:40:51 EDT
Article-I.D.: opal.8705121740.AA16793
Posted: Tue May 12 13:40:51 1987
Date-Received: Fri, 15-May-87 04:09:22 EDT
References: <8705121530.AA19026@armagnac.DEC.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 19

Chris,
	Yes, there are two issues here.  Circuit-switched IP is one.

	The other is, for me, how does one extend IP service to a
large number of micros, many of which are sitting in someone's home,
and connected via a dial-up phone line.

	My bias is that these do not need to have IP addresses assigned,
and so can piggy-back off some existing host.  Still, I think these
machines need various TCP/IP *client* services (FTP, telnet, SMTP maybe),
and I think the remote procedure call is valuable there.  Yes, it needs
a reliable data link layer, flow control, in-sequence delivery, etc.

	The user sitting at home would like to move files back and forth
between the home system and hosts on the IP network, share file systems
with other hosts, login over the network, etc.  The RPC mechanism seems,
to me, an interesting way of accomplishing that.

Greg Minshall