Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!sri-spam!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: <8705111722.AA07335@opal.berkeley.edu>
Date: Mon, 11-May-87 13:22:19 EDT
Article-I.D.: opal.8705111722.AA07335
Posted: Mon May 11 13:22:19 1987
Date-Received: Thu, 14-May-87 01:05:39 EDT
References: <[A.ISI.EDU]11-May-87.12:38:35.CERF>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 39

How I would do TCP/IP from a micro over a phone line:

    1.  The user dials up their favorite IP host (TIP?).
    2.  The user logs in.
    3.  The user invokes, simultaneously on both sides, programs
	which place a remote procedure call interface over the
	wire, with reliability.  The program on the IP host is,
	basically, just a user application.
    4.  Then, the remote procedure call interface "gives" the
	user programs on his micro, the ability to access the
	hosts standard TCP/IP services.

Ttalking to a 4.2 system, if after establishing the dial-up
logon, I have a program which says:

    {
	...
	s = socket(....);
	if (s == -1) {
	    ...
	}
	if (connect(s, ...) == -1) {
	    ...
	}
	if (recv(s, ...) == -1) {
	    ...
	}
    }

all of the calls "socket", "connect", "recv", etc., would be performed via
remote procedure call to the IP host.

(Better, possibly, would be to implement a standard set of TCP-over-dial
remote calls (like LU6.2 verbs) that everyone would recognize once
the system dependent call setup/login/invocation was performed.)

Note that in this way, we get out of having to assign a new IP
address to the client machine, and the user gets to move his/her
TCP/whatever programs down to his/her micro.