[PATCH 0/7] P2PS fixes based on http://w1.fi/p/p2ps-pending/

Jouni Malinen j
Mon Aug 10 10:17:11 PDT 2015

On Sun, Aug 09, 2015 at 02:39:14PM +0000, Peer, Ilan wrote:
> Using the intended P2P interface address exchanged in the P2PS PD for deducting the P2P Client interface address might be wrong, as from our interpretation of the spec, the P2P Interface address attribute is intend to convey the address of the P2P GO and not that of the P2P Client. In addition, it is possible that the P2P interface address exchanged in the PD signaling would not be used once the P2PS PD is done. For example, in the case that one of the devices publishes support for (Cli, GO) and adds the address of a currently running P2P GO, it is possible that at the end of the PD signaling it would instantiate another P2P Client, in which case a new P2P interface address would be used.

Could you please point me to the exact spec language that supports such
interpretation? I don't see P2PS changing the definition of the Intended
P2P Interface Address attribute: the P2P Interface Address a P2P Device
intends to use in a P2P Group. This is an address on the device sending
the attribute regardless of whether the device becomes a GO or P2P

The original P2P definition most certainly expected the following group
formation to use the indicated address and not something else just
because the role "changed" in GO Negotiation. If P2PS changed that
design, it is quite unfortunate. However, I did not find any clear
statement in either spec indicating such a use case. I can only find
P2PS spec listing rules on when this attribute is included; not
indicating anything about it having different value than the P2P spec

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list