My assumption is that, there are at least 3 levels: L0: The laptop will have a certain level of collaborative functionality (preloaded, tailored to the sponsoring nation/school/...) even without ever having an internet connection.
L1: Occasional connectivity - In this case content/collaborative apps can be cached (and refreshed whenever appropriate connectivity is available). Need to be bandwidth sensitive. L2: Fully connected - at school or at home with internet connectivity. In this scenario, kids can participate in school activities, internet level activities et al. L0 - apps would in C and py; most probably running directly L1,L2 - Web scripting, AJAX, py et al; most probably thru a browser. Thoughts ? <k/> > -----Original Message----- > From: Richard Dietrich [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 06, 2006 12:33 PM > To: Krishna Sankar (ksankar) > Cc: [email protected]; MBurns > Subject: Re: [OLPC Networking] Mesh network? > > I think you have misunderstood.. what if there is no > connection to the internet even for the first laptop? > How do you provide it? > R > On 6 Sep 2006, at 20:26, Krishna Sankar ((ksankar)) wrote: > > > ;o) Good question. In simple my mind, the connectivity and > deployment > > scenarios are as follows: > > > > A) Mesh connection to each other, enabling kids to play together, > > games, learning, writing, music et al. For example introducing the > > chamber music masters and try to form an orchestra together > ! Another > > example is using a Wiki collectively to write stories or essays .... > > Annotation, IM, .. All requires connectivity ... > > > > B) At school, running school software, connected to each other and > > to the class room server > > > > C) And of course the traditional scenario, at school or home, > > connected to internet. > > > > D) I have only very limited exposure, but methinks, Internet is > > more pervasive. And the hope is that Internet will reach > more and more > > into areas (OLPC being one of the catalysts) > > > > Thoughts ? > > > > <k/> > > > >> -----Original Message----- > >> From: Richard Dietrich [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, September 06, 2006 12:18 PM > >> To: Krishna Sankar (ksankar) > >> Cc: [email protected]; MBurns > >> Subject: Re: [OLPC Networking] Mesh network? > >> > >> All very well guys - but go back one stage > >> > >> What are you going to connect it too? > >> > >> I want to put them in a South African township of 1 > million people, > >> so the school kids can use them.. but there is no internet > >> connection. > >> And if thats in a township.. what chance do you stand in > rural areas? > >> The mesh has to link into something. > >> > >> So yes, technically interesting.. but? > >> > >> Richard > >> On 6 Sep 2006, at 20:10, Krishna Sankar ((ksankar)) wrote: > >> > >>> Interesting question. Actually I was also thinking about the same > >>> issue ! From my (limited) view : > >>> > >>> a) There will be py level interfaces - dials, gages, switches > >>> and control knobs and a coherent programming model. We do > >> need APIs at > >>> that layer. > >>> b) But the majority of the work would be done at the L1/2/3. > >>> c) The mesh (802.11s) will be implemented as a Layer1/L2 > >>> artifact > >>> d) The mesh mobility networking primitives would be more of > >>> OLSR/AODV/DYMO (more of DYMO/OLSR than AODV) than normal > >> OSPF. Could > >>> be OSPF v3 with mobility as well. > >>> e) We also would need to work with D-Bus, the Avahi > >>> layer(mDNS, local network forming et al) as well as the twisted > >>> framework (if that is part of the distribution) > >>> f) And we should not forget IPv6 ! > >>> > >>> > >>> Cheers > >>> <k/> > >>> > >>> > >>> ________________________________ > >>> > >>> From: [EMAIL PROTECTED] > >>> [mailto:[EMAIL PROTECTED] On Behalf Of MBurns > >>> Sent: Wednesday, September 06, 2006 11:42 AM > >>> To: [email protected] > >>> Subject: [OLPC Networking] Mesh network? > >>> > >>> > >>> Has there been a clear plan on how to achieve the mesh network? > >>> Will it be some python script/framework that acts like a router, > >>> maintaing a routing table and OSPF of available nodes? Or > >> is even that > >>> too high-level, and the mesh capabilities will be done at > >> some lower > >>> layer? > >>> > >>> I am generally interested in how it will be > >> implemented, either from > >>> scratch or from existing technology. > >>> > >>> Michael Burns > >>> Network Engineering > >>> Oregon State University > >>> > >>> _______________________________________________ > >>> Networking mailing list > >>> [email protected] > >>> http://mailman.laptop.org/mailman/listinfo/networking > >>> > >>> > >> > > > > > _______________________________________________ Networking mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/networking
