>> I.e., a router on wifi announces wifi and when a router that is on wired >> receives an announcement from a router on wifi it knows that there >> a bridge somewhere. > >Not a bad idea, but I'm a little hesitant to implement that, since it >would require defining a taxonomy of interface types at the protocol >level. (Currently the taxonomy exists in the implementation, but it >doesn't appear in the protocol -- the protocol only knows about metrics.)
It is probably not such a good idea to literally say 'wifi', but if a set of metrics could be defined that describe that expected stability of a link then a router could annouce which it has configured or discovered. One thing to consider though, in my experience lossy links make for a very bad user experience. So if a disconnect happens as a result of user action, say moving a wifi device from one room to another, then losing the link is not a bad deal. If links just come and go then ultimately users will just complain that the internet is bad. If bad links are unavoidable, it is better to run a tunneling protocol on top of those links with forward error correction or other mechanism to make the link more reliable. (I.e, it might better if babel degrades gracefully, instead of trying to make bad links 'work') _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet