https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7639
--- Comment #37 from Michal Labedzki <michal.labedzki@xxxxxxxxx> 2012-09-05 05:01:15 PDT ---
(In reply to comment #36)
> A profile is really just a specification of the rules for how the protocols
> shall be used to accomplish a certain usage scenario. Profiles do not contain
> packet structure formats (except AVRCP, but that was a mistake). In some cases
> like GAVDP, A2DP, VDP and AVDTP, the profiles/protocols are so closely
> connected that they would never be used seperately.
> I think it has been common practise in the Wireshark development to have
> closely related dissectors in the same dissector file, see e.g. packet-ppp.c.
> Anyway, I just wanted to give you my reasons for putting the profile dissectors
> together with the protocol dissector.
In Bluetooth world often "traditional profile" contain own protocol (HFP, HCRP,
SAP, AVRCP, HID (?)) or use external protocol:
GNSS: NMEA-0183
DUN: AT commands
OPP, FTP, MAP, PBAP, BIP, BPP: Use OBEX
HDP: IEEE Std 11073-20601 TM -2008 Health informatics (By the way: Anyone see
free "specification" for that?)
So I am agree that SPP is not a protocol/profile, because there is nothing, but
can be useful to see data stream or used for "DecodeBy" feature of Wireshark..
and this one can be put together with RFCOMM. DUN, ok, use only AT command, so
this should be dissected by another dissector. But last one - HFP should be
excluded, because use specific AT command, for example:
-----------------------------
AT+BRSF (Bluetooth Retrieve Supported Features)
Bit Feature
0 EC and/or NR function
1 Call waiting and 3-way calling
2 CLI presentation capability
3 Voice recognition activation
4 Remote volume control
5 Enhanced call status
6 Enhanced call control
7-31 Reserved for future definition
-----------------------------
Do you agree with me? (HFP exclude from RFCOMM)
By the way: I will prepare "reversed" patchset to easy apply more minor changes
(OBEX, RFCOMM, colors) then controversy creating subdirectory in
epan/dissectors.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.