DC:
HB: At 3:47 PM 4/9/95, Howard Berkowitz wrote:
HB: Perhaps it's appropriate to say that before implementing
HB: RFC1597 addresses, it is appropriate to plan how you will
:
DC: excellent suggestion.
:
HB: convert from them if necessary. DHCP is one good alternative,
HB: if supported.
:
DC: DHCP does somewhat less than many people may realize. It relieves
DC: you from having to changes tables in each user host; this is wonderful.
DC: However, you still must have a server -- on each net or available via
DC: relaying routers -- with the necessary tables configured to hand out the
DC: values for the user hosts.
DC:
HB: Dave, I'm not sure why you feel a server is a negative thing to
have, other than the obvious cost factors. IMHO, it is far better
to use a more centralized address assignment mechanism than to rely
on schemes where address assignment has to be delegated down to the
workstation level.
The Internet -- and I mean by this "the set of systems that use
rational, if not legal, IP addresses" -- is in a period of extreme
growth, and the growth of network adminstrator skills and availability
has not necessarily kept pace.
There have been too many Class C networks used because the admin
"could get away without subnetting;" there have been too many Class
B networks used so "there could be a nice clean subnet byte," etc.
Most legacy networks, especially those that have involved
organizational mergers, needs some level of address redesign if
they want to avoid serious scaling problems.
Too many current networks also confuse the roles of addressing
and naming, trying to put non-topological/routing information into
addresses. Thankfully, a reasonable of networks do have DNS
servers, which gives them a starting set of tools to evolve
to a rational address plan. Some type of host configuration server,
be it DHCP, a proprietary remote configuration tool, etc., is a
logical next step.
Howard Berkowitz
PSC International, a Cisco Training Partner
(703)998-5819 voice (703)998-5017 home (703)998-5058 fax
PS: I do like the idea of a routing and addressing list separate from
firewalls.
References:
|
|
