[e2e] 100% NAT - a DoS proof internet

[alok]

Hi,

Well, I meant something on the lines of modifying send() and recv () in the
sockets as:

Send($remote_servername,"foo bar")

Instead of:

Send($remote_ip,"foo bar")

Always make associations based on name rather than IP.

Of course it means one would have to modify every stack out there, but
things like skype etc could simply embed the method into their dlls etc when
installed.

-----Original Message-----
From: end2end-interest-bounces at postel.org
[mailto:end2end-interest-bounces at postel.org] On Behalf Of Joe Touch
Sent: Wednesday, February 22, 2006 4:38 AM
To: Jon Crowcroft
Cc: alok; end2end-interest at postel.org
Subject: Re: [e2e] 100% NAT - a DoS proof internet

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jon Crowcroft wrote:
> glib.
> 
> a nat could keep an algorithmic state variable but not maintain an
externally detectable
> mapping from localt o globalraeachable adress (read my orignal email in
this thread)
> OR
> it could keep state about actual e2e flows.

Sure.

> completely different things 

Except that state is state ;-) I read the suggestion as "stateless", not
"avoiding explicit per-connection state".

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD+51eE5f5cImnZrsRAgeeAKCWor8l1sJTDhc6ysBOyNjZWTFQcACgkybK
QJt6KNgOvW2mUZ1kirK00GI=
=PCIW
-----END PGP SIGNATURE-----