Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!MATHOM.CISCO.COM!BILLW
From: BILLW@MATHOM.CISCO.COM (William Westfield)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Telephone Access Controllers (TACs) and SLIP...
Message-ID: <12353015644.15.BILLW@MATHOM.CISCO.COM>
Date: Mon, 23-Nov-87 19:21:36 EST
Article-I.D.: MATHOM.12353015644.15.BILLW
Posted: Mon Nov 23 19:21:36 1987
Date-Received: Fri, 27-Nov-87 22:50:15 EST
References: <8711151624.AA26353@uc.msc.umn.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26


    Rather than having the dialled-into system pick an address for its
    caller, how about if the caller asks for a particular IP address and
    authenticates itself with, say, a password?  That same calling host
    would always ask for the same address.  The name-address association
    could be permanent, only the connections would be temporary.

This makes routing a big problem (although routing protocols are already
dynamic in nature, it isn't clear that they are \that/ dynamic, and are
quite likely to have problems with the huge number of routes that may
suddenly appear).

You would also then have the requirment that each and every PC have
its own (sub)net number, which results in quite an address assignment
problem if you have (as someone mentioned) 3000+ PCs.

A compromise might be to have each SLIP server serve a number of
IP addresses on a particular subnet, and then when a PC dials in,
it can pick its own address from that pool...

It is NOT clear to me that SLIP will primarilly be used by dialin users,
and for hardwired connections to PCs, things are a lot easier.

Bill Westfield
cisco Systems.
-------