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

[Vamsi, Krishna]

> -----Original Message-----
> From: Stepanov, Max [mailto:Max.Stepanov at intel.com]


> Assume we have per service CPT preference on an advertiser side. How should
> a seeker (making a final decision) select CPT bit for a follow on PD response if a
> follow on PD request contains a number of CPT bit options in a feature
> capability field? Definitely the seeker selection may not match an advertiser
> per service preference. My point is that perhaps we may need both per service
> CPT and a global CPT preference lists to cover your requirement. Per service
> CPT preference list is supposed to be used by an advertiser handling a direct PD
> request. (To be precise a per service CPT preference usage is restricted only for
> service advertisements having auto_accept == true and config_methods !=
> KEYPAD.) A global CPT preference list supposed to be used in other cases, e.g.
> by advertisers when per service preference list is not defined or by seekers on
> follow-on PD request.
> 
> What do you think?


I think P2P_ASP_PROVISIONING command can be used to provide the cpt to be used for responding to a follow-on PD req by seeker.

Let me write down my proposal on this.There are two cases:
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.

Thanks,
Vamsi