All, Here's the email I mentioned regarding various request/response patterns for NETCONF/RESTCONF.
Cheers, Kent On 11/14/14, 5:17 PM, "Kent Watsen" <[email protected]> wrote: > > > >Regarding the "persistent", "fragmentation" and "datastore-push" drafts, >and related ideas floating around, I believe that there are the following >use-cases: > > >1) request for an unbounded number of periodic responses sent relatively >frequently (ping) > >2) request for a large YANG config=false list (retrieving interface >statistics) > >3) request for a large blob (file transfer) > >4) request for an action that takes a long time to perform (network link >performance validation) > >5) subscription request on subtree to receive on-change data notifications >(config false also) > > > > >The solution to these may or may not overlap. For instance, consider the >following: > >Options for #1: >A) use a never-ending rpc-reply; server pushes data as it becomes >available >B) initial response returns handle with which client polls for incremental >results and cancels the request > >Options for #2: >A) pagination, multiple rpcs to return subsets of list >B) break response into blocks returned independently > >Options for #3: >A) use a file-transfer protocol like SCP, SFTP, or FTPS >B) use a never-ending rpc-reply; server stream data as it becomes >available >C) break response into blocks returned independently > >Options for #4: >A) initial response returns handle which the client uses to monitor >progress, receive the final result, and cancel the request > >Options for #5: >A) use netconf notifications as is >B) use a modified version of netconf notifications for higher throughput >C) direct responses into a queue that the client can poll > > > >Thoughts? Any additions? > > >Thanks, >Kent > > >_______________________________________________ >netmod mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
