> Op 5 aug. 2015, om 08:50 heeft Mikael Abrahamsson <swm...@swm.pp.se> het > volgende geschreven: > > So again, with basic features like setting the metric depending on interface > speed and type (which has been around for 15-20 years for routing protocols > in all kinds of places), what is it that babel would actually give us in a > decently working homenet with wifi backbone?
Thanks for bringing me up more input for the requirements document: Seen the requirement to support a mix of link types in a homenet, with possibly indeterministic, asymmetric and non-transitive links, the RP MUST support per neighbor metics. The metric itself is provided by the sub-IP layer, or in case of lack of such capability, the RP MUST perform a best effort estimate. Example of estimates are the widely used ETX (community networks) or delay based estimates. The RP SHOULD implement hysteresis and dampening and SHOULD limit oscillations. Even if the sub-IP layer provides link metrics, the RP SHOULD validate correctness. For example, in a bridged environment the sub-IP layer might indicate a high speed high reliable link towards an IP neighbor, while this node is actually reachable over a lossy and low rate link. Examples of such is an WiFi access point topology, where stations do not know link metric between the AP and other possibly far stations, and an ethernet attached powerline repeater. Teco _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
