Service Query TLV(s)

[Neeraj Kumar Garg]

Hello Nishant,
0200->Is the length of the tlv. (2 bytes in this case)
00->protocol (00 is for protocol all, 02 is for upnp)
01->transaction_id. This is to differentiate between the requests in the air.
After this header, your normal service data will follow depending upon the length of TLV you have given.

Regards,
-Neeraj

From: hostap-bounces at lists.shmoo.com [mailto:hostap-bounces at lists.shmoo.com] On Behalf Of Nishant Sharma
Sent: Tuesday, January 08, 2013 10:43 AM
To: hostap at lists.shmoo.com
Subject: Service Query TLV(s)

Hi Jouni,
              To use the service discovery feature of wpa_supplicant for p2p,
the wpa_supplicant specification says :

p2p_serv_disc_req <addr> <TLV(hexdump)>

Schedule a P2P service discovery request. The parameters for this
command are the device address of the peer device (or 00:00:00:00:00:00
for wildcard query that is sent to every discovered P2P peer that
supports service discovery) and P2P Service Query TLV(s) as hexdump.
  I want to know which TLV represents which kind of request. I mean say if I am using

p2p_serv_disc_req <addr> 02000001
  then the value 02000001(hexdump) represents which kind of request . Please let me know from where I can get the complete list of TLV(hexdump) and their corresponding request information in details.

--
Thank you,
Nishant Sharma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20130111/169d4785/attachment.htm