Re: [Babel-users] babel and zeroconf

2008-06-05 Thread Brad Neuberg
Hi Luke and Juliusz! Good to hear from you. Ah, P2P DNS... thats near and dear to my heart... What's the context of the giant email thread below? I can glean bits and pieces but am not sure of what the overall discussion is about. On Wed, May 14, 2008 at 11:23 AM, Luke Kenneth Casson Leighton < [

Re: [Babel-users] babel and zeroconf

2008-06-05 Thread Luke Kenneth Casson Leighton
On Wed, Jun 4, 2008 at 11:00 PM, Brad Neuberg <[EMAIL PROTECTED]> wrote: > Hi Luke and Juliusz! Good to hear from you. Ah, P2P DNS... thats near and > dear to my heart... :) > What's the context of the giant email thread below? I can glean bits and > pieces but am not sure of what the overall di

Re: [Babel-users] babel and zeroconf

2008-05-19 Thread Luke Kenneth Casson Leighton
>> so - a network comprising two WIMAX networks which are geographically >> too far apart to be connected together (more than 2 miles) but a few >> of the nodes can use GPRS / 3G to get data across between the two, >> thus connecting the two networks together. >> >> ... does that work? > > Yep.

Re: [Babel-users] babel and zeroconf

2008-05-19 Thread Juliusz Chroboczek
>> That's called policy routing, and there's a lot of published >> papers on the subject. Babel doesn't do policy routing right now, >> but if you convince me why it's needed, I'm quite willing to add >> it. > ... what you're saying is that it's not straightforward to identify / > separate t

Re: [Babel-users] babel and zeroconf

2008-05-14 Thread Luke Kenneth Casson Leighton
On Wed, May 14, 2008 at 8:28 PM, Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > > soo... http://wiki.laptop.org/go/Mesh_Network_Details#Experimenting - > > they've ... oh. they cheated. they got marvell to do some of the > > low-level mesh networking. > > It was my understanding that OLPC and

Re: [Babel-users] babel and zeroconf

2008-05-14 Thread Juliusz Chroboczek
> soo... http://wiki.laptop.org/go/Mesh_Network_Details#Experimenting - > they've ... oh. they cheated. they got marvell to do some of the > low-level mesh networking. It was my understanding that OLPC and Marvell collaborated on the job. In particular, I believe that Michail Bletsas invested a

Re: [Babel-users] babel and zeroconf

2008-05-14 Thread Luke Kenneth Casson Leighton
On Wed, May 14, 2008 at 12:15 AM, Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > > getting proper WAN-wide name registration and defending is _hard_. > > Yes, if you want to be distributed. You can always fake it with > a centralised server. yuk :) yes. e.g. WINS servers. WINS servers - a

Re: [Babel-users] babel and zeroconf

2008-05-13 Thread Juliusz Chroboczek
> getting proper WAN-wide name registration and defending is _hard_. Yes, if you want to be distributed. You can always fake it with a centralised server. > it takes about _three years_ to get it right - as no less than three > of us found out for samba. Yeah, but you needed to be bug-compati

Re: [Babel-users] babel and zeroconf

2008-05-13 Thread Luke Kenneth Casson Leighton
hi juliusz, thanks very much for responding! On Tue, May 13, 2008 at 10:34 PM, Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > > delighted to have accidentally encountered babel. > > Welcome on board. thank you :) > > > i was wondering if anyone has had any experience deploying babel > > sim

Re: [Babel-users] babel and zeroconf

2008-05-13 Thread Juliusz Chroboczek
> delighted to have accidentally encountered babel. Welcome on board. > i was wondering if anyone has had any experience deploying babel > simultaneously with zeroconf (!) on e.g. a truly wireless adhoc > network. Zeroconf is a purely link-local protocol -- it doesn't reach beyond the local link

[Babel-users] babel and zeroconf

2008-05-13 Thread Luke Kenneth Casson Leighton
folks, hi, delighted to have accidentally encountered babel. i was wondering if anyone has had any experience deploying babel simultaneously with zeroconf (!) on e.g. a truly wireless adhoc network. or, is the role of zeroconf subsumed by that of babel when used in a wireless mesh environment (do