Re: NATs *ARE* evil!

Jon Knight <J.P.Knight@lboro.ac.uk> Tue, 19 December 2000 19:00 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id OAA21583 for ietf-outbound.10@ietf.org; Tue, 19 Dec 2000 14:00:04 -0500 (EST)
Received: from mailer1.lut.ac.uk ([158.125.1.202]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20083 for <ietf@ietf.org>; Tue, 19 Dec 2000 13:05:20 -0500 (EST)
Received: from jon (helo=localhost) by mailer1.lut.ac.uk with local-smtp (Exim 2.10 #1) id 148R8E-0001y8-00; Tue, 19 Dec 2000 18:04:58 +0000
Date: Tue, 19 Dec 2000 18:04:52 +0000
From: Jon Knight <J.P.Knight@lboro.ac.uk>
X-Sender: jon@mailer1
To: V Guruprasad <prasad@watson.ibm.com>
cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: NATs *ARE* evil!
In-Reply-To: <20001219112023.A19099@bubble.watson.ibm.com>
Message-ID: <Pine.SOL.3.96.1001219174232.10101F-100000@mailer1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Lboro-Filtered: mailer1.lut.ac.uk, Tue, 19 Dec 2000 18:04:59 +0000
X-Loop: ietf@ietf.org

On Tue, 19 Dec 2000, V Guruprasad wrote:
> Could you please take a look at
> 	draft-guruprasad-addressless-internet-00.txt
> ?

I've just started to read it and in 1.1 it says:

  "- requiring e2e network knowledge (omniscience) at each node in the  
     form of e2e routing tables (Section 1.3);"

Erm, now I might be misunderstanding something here but our end nodes
(workstations, servers, PCs, etc) certainly don't have full e2e routing
knowledge.  They know what their address(es) is/are, what network(s) they
are on and what the address of their gateway router is.  Not exactly what
I'd call omniscience.

Also I note in section 1.2 it says:

  "Even if better dressed as IP addresses, network addresses are
   real addresses in that they locate physical destinations in the
   network, unlike memory addresses, which are routinely virtualised by
   host operating systems."

Surely DNS addresses are more equivalent to the virtual memory
addresses in host if you're going to take that analogy?  The whole point
of virtual memory is that it makes it easier for the user (well,
programmer) by hiding the nasty details of which physical address your
code and data live at.  The whole point of the DNS is that it makes it
easier for the user by hiding the nasty details of what IP address you
need to talk to.  And that's without getting into the situations where a
single IP address locates multiple hosts (broadcast addresses, multicast
addresses, etc).

Reading further into the draft I was left think "URNs".  The draft does
mention URNs at all and yet alot of what it seems to do appears similar to
the ideas behind the URN efforts of the IETF in the past.

Tatty bye,

Jim'll