dpp: ethernet README

README.md

@@ -711,6 +711,8 @@ improvement in the map-controller `status` UBUS API.
 
 ## DPP Easy Connect
 
+### Wi-Fi QR Code based Onboarding
+
 NOTE: The enrollee and the controller/configurator device must be operating at
 the same channel, as off channeling listening for DPP Chirp messages is
 currently not supported.
@@ -765,6 +767,28 @@ are not yet implemented, fronthaul configurations relies on AP-Autoconfiguration
 which does not support passing DPP AKMs. With this said, it is possible to onboard
 via DPP only AKMs and establish a connection.
 
+### Ethernet QR Code based Onboarding
+
+DPP Ethernet onboarding is implemented leveraging
+[libdpp](https://dev.iopsys.eu/multi-ap/libdpp).
+
+For DPP Ethernet onboarding, no additional configuration sections needs to be
+present, but map-controller must be compiled with the CLFAGS including `USE_LIBDPP`.
+
+The credentials that are provisioned are picked up based on the backhaul `ap`
+sections in the map-controller configuration file.
+
+To perform DPP Ethernet onboarding, the enrollees bootstrap information must
+provided to the map-controller via its UBUS API `dpp_enrollee_uri_eth`:
+
+```
+ubus call map.controller dpp_enrollee_uri_eth '{"uri":"DPP:C:81/1,115/36;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgACcwPoTjXxtZ2IJAjyZeH1kECGHXGhxhEEyPzcnpFo2ms=;;"}'
+```
+
+Once provided, map-controller will be able to perform DPP Ethernet onboarding,
+triggered by AP-Autoconfig Search and DPP Direct Encapsulated messages.
+
+
 ## UBUS APIs
 
 Map-controller offers a variety of UBUS APIs, most of them map to CMDU request