[PATCH 13/19] P2PS: add p2ps_supported_cpt configuration property

Stepanov, Max Max.Stepanov at intel.com
Thu Jun 18 07:27:20 EDT 2015


>-----Original Message-----
>From: Vamsi, Krishna [mailto:vamsin at qti.qualcomm.com]
>1. auto_accept == true
>     Seeker sends "cpt configured through P2P_ASP_PROVISIOING command"
>in PD request. Advertiser uses "cpt configured through P2P_SERVICE_ADD
>command" to choose (based on intersection with whatever received in PD
>req) a transport mode and sends it in PD response.
>
>2. auto_acceot==false
>     Seeker sends "cpt configured through P2P_ASP_PROVISIOING command"
>in PD request. Advertiser uses "cpt configured through P2P_SERVICE_ADD
>command" to choose (based on intersection with whatever received in PD
>req) a transport mode and sends it in PD response(though this will not be
>used for service establishment). Advertiser reports the received feat_capa to
>the ASP sitting on top of it.
>    The Advertiser's ASP will configure the preferred cpt through
>P2P_ASP_PROVISIONING_RESP command which should be sent in follow-on
>PD req. The seeker can choose one transport mode to be used with that
>service instance based on the intersection of cpt received in follow-on PD
>request and the cpt configured earlier through P2P_ASP_PROVISIONING
>command (this can be saved in p2ps_prov structure until then).
>
>Let me know if you see some problem with the above.

It looks reasonable to me. I'll change my implementation and let you know.

Thanks,
Max


More information about the HostAP mailing list