A 911 PSAP tooling team prefers simple HTTPS/JSON clients for routi…

Question

A 911 PSAP tooling team prefers simple HTTPS/JSON clients for routine reads but needs transactional candidate/running datastore commits for complex multi-leaf changes on IOS XE. Which protocol pairing matches those needs?

Accepted Answer

Prefer RESTCONF for straightforward HTTPS/JSON operations and NETCONF when full datastore transactions are required — RESTCONF is the easy HTTPS/JSON counter window; NETCONF is the escrow desk that holds a whole candidate config until you commit. Grab the simple reads over RESTCONF, and bring the multi-leaf surgery to NETCONF. SNMP SETs and telemetry streams are not that transaction desk.

Answer

Use only SNMP SETs for both simple reads and multi-leaf transactions

Answer

Use gRPC telemetry subscriptions to write candidate configurations

Answer

Rely on Guest Shell cron alone because neither NETCONF nor RESTCONF supports YANG

A 911 PSAP tooling team prefers simple HTTPS/JSON clients for routine reads but needs transactional candidate/running datastore commits for complex multi-leaf changes on IOS XE. Which protocol pairing matches those needs?

Short Explanation

Full Explanation