ents in Figure 16.10. Examples of such measurement agents would include the ones listed above for service monitoring, control plane monitoring, or packet capture. Measurement agents would in turn interface to ONAP as follows: 1. Configuration via the use of a model-based NETCONF or RESTCONF north-bound API. This would include configuration of the measurements within the context of a specific measurement agent, as well as configuration of the reporting of the measurement results via the API. 2. Retrieval of measurement results via polling, utilizing a model-based NETCONF, or RESTCONF north-bound API. Such an interface is limited to supporting low volume retrieval from measurement agents, and would be utilized in case of a diagnostic situation. 3. Retrieval of measurement results via a streaming telemetry interface, utilizing a model- based APACHE AVRO [11] API. This interface is designed to support retrieval of mea- surement results from measurement agents at a high volume and is based on a publish/ subscribe paradigm. 4. SDN models that provide the following functions: a. The ability to schedule measurements for each of the measurement agents via the con- figuration interface, as well as schedule reporting of the measurement results via the polled or streaming telemetry interfaces. Measurement-specific models that encapsulate the measurement agent function within a YANG model. An example of such a model would be the TWAMP YANG model [13]. CONFIGURATION POLLED STATE STREAMING TELEMETRY (NETCONF/ (NETCONF/RESTCONF/ STATE RESTCONF/YANG) YANG) (APACHE AVRO/YANG) SDN-Mon MODELS (YANG) [SCHEDULING, AGENT #1 MODEL, AGENT #2 MODEL, etc.] MEASUREMENT MEASUREMENT MEASUREMENT AGENT TYPE-#1 AGENT TYPE-#2 AGENT TYPE #N FIGURE 16.10 AT&T's SDN-Mon framework. Network Measurements The framework allows for a flexible deployment of the various SDN-Mon functions. For exam- ple, in one instance, supporting a bundled deployment model, wherein the entire framework and measurement agents would be deployed as one single integrated compo