From: "Dennis Ritchie" <dmr@bell-labs.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Datakit documentation
Date: Thu, 11 Mar 2010 09:33:22 +0000 [thread overview]
Message-ID: <7vqujtFn43U2@mid.individual.net> (raw)
In-Reply-To: <alpine.BSF.2.00.1003090023380.2657@legolas.yyc.orthanc.ca>
"Lyndon Nerenberg" <lyndon@orthanc.ca> wrote in message
news:alpine.BSF.2.00.1003090023380.2657@legolas.yyc.orthanc.ca...
> What I'm mostly interested in are the network protocols and the routing
> and addressing schemes. But anything I can get my hands on is of interest.
> Anyone have suggestions on likely places to go searching for this?
I have a very detailed document on the transport protocol;
I haven't found the stuff I probably have on addressing
and how to use it. Let me know and I'll send the URP
specification paper by Fraser and Marshall, The
other paper you mentioned, by Fraser, probably
speaks more generally.
Dennis
prev parent reply other threads:[~2010-03-11 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 8:02 Lyndon Nerenberg
2010-03-09 15:00 ` Steve Simon
2010-03-11 9:33 ` Dennis Ritchie [this message]
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=7vqujtFn43U2@mid.individual.net \
--to=dmr@bell-labs.com \
--cc=9fans@9fans.net \
/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).