How about this, practicality. Let's say we can kill all NAT's by sunset,
Sunday. Who can make stop all the NAT's poping up Monday morning? They
might be up all night building experimental network, with red eyes?
Pan Jung
-----Original Message-----
From: Iliff, Tina [mailto:Tina(_dot_)Iliff(_at_)WCOM(_dot_)Com]
Sent: Friday, December 15, 2000 10:48 AM
To: 'Dave Robinson'; Keith Moore
Cc: M Dev; Sean Doran; ietf(_at_)ietf(_dot_)org; iab(_at_)iab(_dot_)org
Subject: RE: NATs *ARE* evil!
Yes! TCP breaks due to the fact that "true" source/destination sockets
cannot be defined. The destination would not know where to send a response
except in the case where DNS is used...unless I need to do more reading
Tina Iliff
-----Original Message-----
From: Dave Robinson [mailto:drobinson(_at_)endtoend(_dot_)com]
Sent: Friday, December 15, 2000 11:11 AM
To: Keith Moore
Cc: M Dev; Sean Doran; ietf(_at_)ietf(_dot_)org; iab(_at_)iab(_dot_)org
Subject: RE: NATs *ARE* evil!
What's the problem with locally significant addresses? Having thousands of
10 networks will never present a problem unless those networks at some point
would like to talk to each other. Is that where this whole discussion is
going (or coming from) - that ultimately the more NAT'ing we do, the more
headaches we're creating for ourselves en route to true global connectivity?
Dave
-----Original Message-----
From: Keith Moore [mailto:moore(_at_)cs(_dot_)utk(_dot_)edu]
Sent: Friday, December 15, 2000 10:56 AM
To: Dave Robinson
Cc: Keith Moore; M Dev; Sean Doran; ietf(_at_)ietf(_dot_)org;
iab(_at_)iab(_dot_)org
Subject: Re: NATs *ARE* evil!
because in a NATted network the same addresses are used in different
parts of the network. addresses are meaningless.