Hello,
Pipelining as specified in chapter 4.5 of RFC 6241 , meaning that a given RPC on a given NETCONF Session is pipelined until the previous RPC ( on the same NETCONF Session ) ended.
But there remains an ambiguity in the RFC in the case where the two parallel RPCs are in different NETCONF Sessions. Could you confirm that ConfD does not perform pipelining between two NETCONF Sessions ?
Regards.
Christian.
Could you confirm that ConfD does not perform pipelining between two NETCONF Sessions ?
Yes for reading and no when writing.
“Pipelining” is performed as defined in RFC 6241: “NETCONF <rpc> requests MUST be processed serially by the managed device.” between sessions when you write data to ConfD using, for example, RFC 6241 <edit-config> or RFC 8526 <edit-data> RPCs. The ConfD transaction manager will serialize those write requests.
When reading data using <get>, <get-data>, etc. RPCs the requests from different sessions are not processed serially by ConfD, i.e. they are processed in parallel.
Regards
1 Like