Re: Guidance needed on well known ports

[Keith Moore <moore at cs.utk.edu>]

>     > From: "Spencer Dawkins" <spencer at mcsr-labs.org>
> 
>     > I have learned not to tell people (especially Keith and Noel)
> 
> Hey, I'm nowhere near as hypergolic on this as Keith is... :-)

"hypergolic"... great word! (even if a tad unflattering...)

>     > that DNS is the right answer to all questions,
> 
> Well, it works fine for what it was designed to do. Problem is, people get
> into this "hammer-nail" mode, and they have a problem to solve, and not enough
> (protocol) tools to do it with... (ARP used to suffer the same problem.)

very much agree.  the other problem with DNS is that the environment
has changed a lot since DNS was designed.  DNS worked fine in the days
when hosts were expensive, relatively few in number, in fixed
locations, and centrally maintained by dedicated staff.  these days when
hosts are numerous and cheap, highly mobile, and barely maintained at
all, DNS has a large potential to get out of sync with reality.
another factor is two-faced DNS or the tendency to use other lookup
services on local networks.  yet another factor is disconnected
networks.

in order to try to deal with all of these things we have numerous hacks
on top of DNS that don't really work well together, and as a result, we
don't have a common set of assumptions about what DNS means, what it's
good for and what it's not, how it interfaces with mobility,
autoconfiguration, etc. 

we really need a naming architecture that encompasses a modern view of
the Internet. 

>     > it is significantly difficult having most of the machines on the net
>     > impossible to locate from most of the other machines on the net.
> 
> That's more because of NAT, than anything else. 

I was going to say that, but you beat me to it.  thanks.

Keith

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf