> One alternative that was raised at the mic, but that has not (to my > knowledge actually been proposed anywhere) was the use of unicast > ND for cases when you want to configure different routes on different > nodes. Are there problems in this space that would not be solved by > doing that? If so, what are they? If not, perhaps we need to write > up a unicast ND mechanism?
We talked about Unicast RA in Taipei as well. It does solve the problem, but it is only really useful in cases where you have a single router or a small number of routers that need to be configured with these unicast ND routes. In a large network with many routers, the information distribution problem becomes truly painful. This is a specific use case for something like a DHCP route option, and I was suprised not to see it mentioned yesterday. It's true, as Jari said, that this can be accomplished in other ways, and maybe it would be better if it would. If there were some better central management solution for populating unicast RA mappings on the router, then unicast RA would indeed address the exact use case that I think we care about. But without the mechanism for populating routers, we still have a poorly-addressed use case. And then the question is, do we want to develop a whole new protocol just to solve this one small problem? It might be worth developing the protocol just to put this issue to bed. _______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif
