Just throwing an argument that comes into my mind here. HNCP advertises configuration. Long-lived things. It is likely that DNCP is quite inefficient when it comes to changing things all the time. Metrics can evolve. Particularly wifi links metrics. So we probably do not want to put that in DNCP.
- Pierre > Le 22 juil. 2015 à 15:23, Ted Lemon <[email protected]> a écrit : > > On Jul 22, 2015, at 9:22 AM, Mikael Abrahamsson <[email protected] > <mailto:[email protected]>> wrote: >> May I ask why this design decision was made? For me a routing protocol >> doesn't autoconfigure its metrics, but I now realise that this is probably >> what babel does? I thought the mechanism of configuring the metrics was >> separated logically, but I now realise this isn't how it has been done in >> babel? > > HNCP doesn’t have the information it needs to set a metric. Babel figures > out the metric using an adaptive mechanism that could be put into HNCP, but > isn’t currently in HNCP. > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
