Howdy! I'm getting confused by the session semantics. What is the lifetime of operational data? More specifically, should NETCONF sessions behave as if the operational state has done a snapshot at a specific time, or is it intended to change between queries?
The actual problem arises with using leafrefs in operational data referring to another leaf inside the operational data tree. That is indeed possible to be queried by the XPath filtering, as specified in RFC 6241 ยง 8.9, yet that's an optional thing. Do I suppose correctly that the returned data is not required to be consistent between queries? Actually, should we even expect that the returned data is time-consistent inside itself? That is a valid question for various counters (e.g. packet count on an interface) where the data storage may not be accessible at the exact same time, and also for interface states if there is a lot of interfaces to query, but also for large route dumps. There is an implication for any answer to this question. Either the clients have to expect inconsistent results, or the servers have to freeze the states. Thank you for helping me out of this swamp. Have a nice day! Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
