P2P: Provision discovery and Service discovery request frames to a P2P AutoGO

[Jouni Malinen]

On Fri, Jun 08, 2012 at 05:43:35AM +0000, Neeraj Kumar Garg wrote:
> Could you plz let us know why dst_addr and bssid addr are put as peer's p2p device address for Provision discovery request frames even if they are destined to P2P GO? It is not only just PD request frames, but also any other frames (e.g. Service discovery requests) which are destined to a peer (who is already part of a P2P group) having bssid as p2p_dev_addr.

Because that's the way the protocol works.. ;-)  These frames are used
in the P2P Device role, i.e., they are not part of group operation. As
such, they use the rules defined in the last paragraph of P2P spec
chapter 2.4.3.

> If it is intended, could you plz let us know the rationale behind it?

These are Public Action frames that are sent to the P2P Device, not the
GO role. Sure, it may sound a bit silly for Provision Discovery Request
frames in the case where they are used to notify the GO of a P2P client
that joins an operating group, but still, that is the way the protocol
was designed to work.

There are couple of P2P Action frames that are not Public Action frames
(e.g., P2P Presence Request/Response). Those use the P2P Interface
Address of the GO in the BSSID field.

-- 
Jouni Malinen                                            PGP id EFC895FA