updating images and adding ecosystem

Author: inband-oam

README.md

@@ -97,7 +97,7 @@ route-record option defined in [RFC0791] can be considered an in-band OAM mechan
    In-band mechanisms also don't suffer from implementations, where
    probe traffic is handled differently (and potentially forwarded
    differently) by a router than regular data traffic.
-## ![](/images/ioam-telemetry.png)
+
 
 ## Overlay and underlay correlation
 
@@ -253,6 +253,16 @@ The figure below shows an example. Routers R1, R2, R3, R4 form a domain within w
 
 # iOAM solution ecosystem
 
+Below is an example iOAM solution ecosystem with IPv6 transport:
+
+- Forwaring plane: iOAM feature to insert, updata and remove metadata from the packets is implemented in VPP forwarding plane
+- Controller: Opendaylight controller and iOAM applications control and orchestrate iOAM processing and configuration 
+- Collectors: iOAM metadata is exported as netflow records and json objects as needed. This is collected using pmacctd netflow collector or published into message bus such as Apache Kafka
+- Analyzers: iOAM metadata collected is analyzed for anomalies using offbox or on-box applications
+- Visualization: iOAM metadata thus collected and insights derived from its analysis is used to visualize network state
+- Feedback loop: Insights derived from iOAM data is used to trigger more data collection or take corrective action via controller
+
+
 ## ![](/images/ioam-ecosystem.png)
 
 # References