[e2e] 100% NAT - a DoS proof internet

[Joe Touch]

alok wrote:
> Yes but I do not understand why there is a double association between a
> "$who and $where"
> 
> For example if I wish to talk to "Tim" via my cell phone, I would simply
> look for the name "Tim"
> 
> It would also need a change in the way end hosts make associations as of
> date,
> Last I checked, sockets use "IPs" to identify end points. It does not have a
> default "gethostbyname()" in it.

It's trivial to write a new "sendbyname" and embed gethostbyname in it.

> Back in the dial up days I remember I used to get a nice name as:
> 
> Ppp1.ispras.myisp.com
> 
> In more modern DSL days, simply giving my name street address/my telephone
> directory entry as my port identifier (we get our DSL over our POTS) would
> not be so bad would it? 
> 
> But would any OS stack out there support this sort of a transaction, based
> completely on "$who-->send data" instead of the recursive "$who-->$where and
> then send data"?

The OS isn't what needs to support it; the name needs to go in the IP
packet. Which means routing on DNS names. See TRIAD.

With respect to NATs, you're just asking to have names rewritten; this
doesn't solve anything.

Joe