From: dantes@vif.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Network design question
Date: Tue, 8 Jun 2004 23:57:42 -0400 [thread overview]
Message-ID: <40C68AB6.2040809@vif.com> (raw)
Hello everyone,
I'm currently writing a batch of presentations about distributed
systems, and I was of course having a look at Plan 9, especially on its
network and communication implementation. I've been through the papers,
and here is what I understood.
Just to be sure I don't include erroneous data, could you please confirm
(or oppose, but then please explain :) those assertions:
- from the OSI point of view, the layers 4, 5 and 6 have a custom
protocol implementation: 9P.
- 9P offers an interface at layer 5 (messages, local)
- 9P offers an interface at layer 6 (RPC, local)
- a service does translation from 9P to TCP for external communication
(at level 4?).
Where does IL fit in all this?
Hmm, still a bit confused.
Sorry if the question seem a bit lousy, and thanks a lot for any help!
Best regards
Jef
next reply other threads:[~2004-06-09 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 3:57 dantes [this message]
2004-06-09 9:29 ` vdharani
2004-06-09 4:39 ` dantes
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=40C68AB6.2040809@vif.com \
--to=dantes@vif.com \
--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).