https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7639
--- Comment #36 from Allan M. Madsen <allan.m@xxxxxxxxx> 2012-09-03 07:12:54 PDT ---
(In reply to comment #35)
> (In reply to comment #34)
> HFP is protocol too. It based on AT commands, which can be dissected. Some
> command is Bluetooth specific. I will improve it later (after spiting). On the
> other hand these dissectors are currently separated dissectors, you can
> filtering frames by them. Please note that code of HFP will grove of some
> improvements.
> In my opinion Bluetooth Profiles should be treat as "protocols", for example:
> HFP, AVRCP, A2DP/VDP, SAP. There are very specific frames, which should be
> dissected.
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.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
