Hi, I've read the revised-datastores-00 document, in general I like it, here are my initial comments and questions:
1. Even if <intended> is valid, it can still be in conflict with the actual content of <applied> that may come from e.g. dynamic configuration protocols. How are such cases supposed to be resolved? 2. What is the distinction between dynamic configuration protocols and control-plane protocols? 3. Shared <candidate> has known problems. Maybe it's time to part with it in this new datastore model? 4. Templates are briefly mentioned in several places, it would be useful to explain this concept in more detail. 5. Is it necessary that "<operational-state> datastore contains all configuration data actually used by the system"? For example, static routes should appear in RIBs, so having them separately in operational state seems redundant. Lada -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
