From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: Re: [9fans] on TCP vs IL
Date: Fri, 23 Nov 2001 13:18:21 -0500 [thread overview]
Message-ID: <20011123181821.1572F3FE56@quanstro.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
>"Thomas Bushnell, BSG" wrote:
>> dhog@plan9.bell-labs.com (David Gordon Hogan) writes:
>> > Do you really want each byte to have its own IP address?
>> Yes, frankly, I would love that. It might be too expensive, but if
>> not, it would truly be wonderful to have.
>
>Personally I wish each *bit* in the universe had a unique address.
sure. we can do that. how about this mapping:
10.0.0.0 = 0
10.0.0.1 = 1
☺
reply other threads:[~2001-11-23 18:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011123181821.1572F3FE56@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).