Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!jade!ucbvax!OPAL.BERKELEY.EDU!dlw
From: dlw@OPAL.BERKELEY.EDU (David Wasley)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Telephone Access Controllers (TACs) and SLIP...
Message-ID: <8711100623.AA19378@opal.berkeley.edu>
Date: Tue, 10-Nov-87 01:23:43 EST
Article-I.D.: opal.8711100623.AA19378
Posted: Tue Nov 10 01:23:43 1987
Date-Received: Sun, 15-Nov-87 22:39:37 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21

I have a very strong interest in such a thing. I envision it as presenting
host addresses on a single subnet to the various ports. 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? How would you deal with dynamic name/address mapping?
I can see dynamic registry with a DNS, and timeout/de-registry. But what
about the email relay that wants to deliver to me and must be told that
I've just connected? (This is one reason I want real, secure validation.)

If such a thing existed, I can see supporting a "rotary" of 64 ports (min)
for general campus network access here. They should run up to 64Kb/s.
The line protocol should be SDLC with a well defined IP encapsulation
so my PC, uVax, MAC-II, or SUN can implement it. Etc. It should have logging
of course...

Maybe all this is obvious. Maybe there is one out there?? I haven't seen it.
(Yeah, we could make one, but I'd rather see a standard product :-)

	David Wasley
	U C Berkeley