From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <35178.67.85.61.176.1086773361.squirrel@www.infernopark.com>
In-Reply-To: <40C68AB6.2040809@vif.com>
References: <40C68AB6.2040809@vif.com>
Date: Wed,  9 Jun 2004 04:29:21 -0500
Subject: Re: [9fans] Network design question
From: vdharani@infernopark.com
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Cc: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 99a44984-eacd-11e9-9e20-41e7f4b1d025


> - from the OSI point of view, the layers 4, 5 and 6 have a custom
> protocol implementation: 9P.
9p is similar to nfs protocol. the main difference is nfs is designed to
serve regular data files and so it treats data in terms of blocks. 9p
additionally takes care of device files and the data is treated as
messages of variable size (max is 8192). and 9p messages are not cached.

> - 9P offers an interface at layer 5 (messages, local)
>
> - 9P offers an interface at layer 6 (RPC, local)
i am not sure if 9p can be treated like this. i guess it is pretty much
the 4 layer tcp/ip with 9p sitting on top of tcp/ip. 9p is like nfs
protocol and uses rpc mechanism.

> - a service does translation from 9P to TCP for external communication
> (at level 4?).
>
> Where does IL fit in all this?
il is pretty much similar to tcp except that while tcp works in
byte-stream mode, il wrok in message-mode.

thanks
dharani