ent framework to work with the NFV/SDN network: 1. Improving the customer service experience, including providing customer-specific reporting. 2. Meeting the service obligations, including a. SLA compliance monitoring for customers b. Meeting legal obligations C. Supporting day-to-day business operations 3. Helping reduce network capital expenditure (CAPEX), including optimizing network capacity and utilization. 4. Helping reduce network operating expense (OPEX), including a. Service impairment detection b. Diagnosing and isolation of network issues Abstraction of anonymized data close to where it is collected to reduce network load asso- ciated with transmitting raw measurement data. 6. Correlation between service and network measurement data, SO isolation can be done auto- matically. This enables the building of a targeted feed of anonymized data to subsequently generate key performance indicators (KPIs) and other metrics to automatically point to a network impairment. Building the Network of the Future 7. Keeping measurement network impact to a minimum (e.g., <0.5% of network bandwidth). 8. Minimizing the measurement instrumentation footprint needed to accomplish the objec- tive. For example, we could prefer using a single measurement stream to cover both perfor- mance and reachability measurements. 9. Focus on monitoring close to network operator's service boundary with the customer (i.e., network edge), versus within the core network. 10. Enabling flexibility to craft new measurement signatures to quickly validate customer experience for specific application traffic. Rapidly off-boarding measurement data. Such data would need to be forwarded to ONAP utilizing one or more standard, scalable, and secure methods. 12. Complying fully with new architectural specifications including configuration and report- ing, using NETCONF/YANG [9], RESTCONF/YANG [10], APACHE AVRO [11], or a functionality equivalent protocol such as Google remote procedure call (RPC) (gRPC) [12], highly leveraging open source software. 16.4.2 