diff --git a/README.md b/README.md
index a1675262d..84bb4a258 100644
--- a/README.md
+++ b/README.md
@@ -16,6 +16,7 @@
          * [Verifying Pod network interfaces](#verifying-pod-network-interfaces)
       * [Using with Multus conf file](#using-with-multus-conf-file)
       * [Logging Options](#logging-options)
+      * [How to use with Network Device plugins?](#cni-running-with-network-device-plugin)
       * [Testing Multus CNI](#testing-multus-cni)
          * [Multiple flannel networks](#multiple-flannel-networks)
             * [Configure Kubernetes with CNI](#configure-kubernetes-with-cni)
@@ -492,7 +493,13 @@ You may configure the logging level by using the `LogLevel` option in your CNI c
 ```
     "LogLevel": "debug",
 ```
+## CNI running with Network device plugin
 
+Allocation of the Network device(such as SRIOV VFs) are done by Device plugins(Eg.SRIOV Network device plugin), Multus developed to work in the co-existence enviroment to work with device plugin by passing down the allocated device information to the CNI plugins.
+
+* [Device plugin & CNI, NUMA Manager alignment - technical architecture document](https://docs.google.com/document/d/1Ewe9Of84GkP0b2Q2PC0y9RVZNkN2WeVEagX9m99Nrzc/edit)
+* Reference implementation : [SRIOV Network devie plugin](https://github.com/intel/sriov-network-device-plugin)
+* Example: [How to make Multus work with device plugin?](https://github.com/intel/multus-cni/tree/master/examples#passing-down-device-information)
 ## Testing Multus CNI
 
 ### Multiple flannel networks