Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Dave Taht
On Tue, Nov 18, 2014 at 4:12 PM, Juliusz Chroboczek wrote: >> I do note that the default 4 sec update interval bugs me. > > It's probably the Hello interval that's biting you, not the Update > interval. Sure. >> crank up the update interval by a factor of, say, 1, to see what >> happens. > >

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Juliusz Chroboczek
> I do note that the default 4 sec update interval bugs me. It's probably the Hello interval that's biting you, not the Update interval. > crank up the update interval by a factor of, say, 1, to see what > happens. You cannot, Babel won't go below 10ms. (Hard-wired in the on-wire encoding,

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Juliusz Chroboczek
> I think I understand. If there is the potential for a loop (advertised > distance >= babel router’s former distance), babel will wait for the > next sequenced route from the source. Exactly. >So, the loop-free guarantee is at the expense of potentially faster >convergence. In principle, yes.

Re: [homenet] I-D Action: draft-ietf-homenet-front-end-naming-delegation-00.txt

2014-11-18 Thread James Woodyatt
Home gateways are typically not recursive resolvers. They're usually just translators for non-recursive DNS query/responses. Some have forwarding servers. There might be some that are recursive resolvers, but there are lot of good reasons not to put one there, starting with the fact that some servi

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Dave Taht
On Tue, Nov 18, 2014 at 7:33 AM, Acee Lindem (acee) wrote: > Hi Juliusz, > I think I understand. If there is the potential for a loop (advertised > distance >= babel router’s former distance), babel will wait for the next > sequenced route from the source. So, the loop-free guarantee is at the

[homenet] while we are distracted by IoT

2014-11-18 Thread Dave Taht
Anybody know anything about Allseen? http://linuxgizmos.com/open-iot-alliance-to-tackle-smart-connected-leds/ and for that matter, AllJoyn? https://developer.qualcomm.com/mobile-development/create-connected-experiences/intelligent-proximal-connectivity-alljoyn -- Dave Täht http://www.bufferbl

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Acee Lindem (acee)
Hi Juliusz, I think I understand. If there is the potential for a loop (advertised distance >= babel router’s former distance), babel will wait for the next sequenced route from the source. So, the loop-free guarantee is at the expense of potentially faster convergence. Correct? Thanks, Acee

[homenet] Stub-only Babel revisited

2014-11-18 Thread Juliusz Chroboczek
[This is cross-posted between babel-users and Homenet@IETF, please choose your followups wisely.] You might remember the stub-only implementation of Babel that I published last week-end: https://github.com/jech/sbabeld After playing some more with it, I've come to the conclusion that it could

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Juliusz Chroboczek
> What feature of babel keeps traffic from looping during re-convergence? Please see http://www.pps.univ-paris-diderot.fr/~jch/software/babel/babel-20140311.pdf slides 7 and 11-17. I'll be more than happy to clarify anything that's not obvious from the slides. -- Juliusz ___

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Dave Taht
so by my lights the thermostat has a simply astonishing amount of flash (38MB), and an A8 class processor... https://learn.sparkfun.com/tutorials/nest-thermostat-teardown- Peeking at the board from the pics I cant see how much memory it has, and the OS seems to be quite small (1.5MB) but I have t

Re: [homenet] Next Steps for Routing Protocol

2014-11-18 Thread Acee Lindem (acee)
On 11/18/14, 1:46 AM, "Teco Boot" wrote: > >> Op 17 nov. 2014, om 17:53 heeft Margaret Wasserman >> het volgende geschreven: >> >> >> On Nov 16, 2014, at 8:44 PM, Teco Boot wrote: >>> It could be long enough to get in trouble. There could be more than >>>two neighbors, loaded wireless links