On Wed, 22 Jul 2015, Markus Stenberg wrote:
Agreed. I think we will remove routing protocol references from HNCP
just to be clear, as in practise what we really interact with is the
local route set and not the routing protocol itself anyway. I guess it
was easier to write the way it is, but as it causes confusion, rather
fix it and drop the RP dependency except for the border discovery result
triggering running / not running of 'a suitable routing protocol'
somewhere.
We still need to figure out how routing protocol metrics should be done.
For me, these are configured, indicating to me that HNCP should do it. If
we leave it out of HCNP, well then that's a requirement on the routing
protocol itself to implement a mechanism itself to do it without any prior
knowledge of what the world looks like.
I had a quick scan through the architecture document and it says that the
routing protocol is self configurable, so I guess this is why we have
differing views on what things are up to the routing protocol and what is
up to the rest of the architecture to set up and influence.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
