Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!GYRE.UMD.EDU!chris
From: chris@GYRE.UMD.EDU (Chris Torek)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Telephone Access Controllers (TACs) and SLIP...
Message-ID: <8711150720.AA04413@gyre.umd.edu>
Date: Sun, 15-Nov-87 02:20:44 EST
Article-I.D.: gyre.8711150720.AA04413
Posted: Sun Nov 15 02:20:44 1987
Date-Received: Sun, 22-Nov-87 08:43:48 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 24


	From: dlw%opal.Berkeley.EDU@violet.berkeley.edu (David Wasley)

	... The protocol would be to "log in" to the system (validation
	and all that) and be given an IP address & mask for the duration
	of the session. After that, it is all IP until carrier drops.
	Is there a well defined, documented protocol for this initial
	dialogue?

Not as far as I know; but I had something like this in mind when I
rewired Rick Adams's version of SLIP for 4.3BSD.  That is why slattach
waits `forever' in a sigpause(): to find out about carrier loss.  If
you are a client of some dialup IP server, you might want to redial
automatically.

(Those of you with 4.3BSD source can look at /usr/src/etc/slattach.c to
see how the attach works.  It should be easy enough to write dialup and
protocol code that would run first.)

	How would you deal with dynamic name/address mapping?

I will leave this one for others.

Chris