Wireshark mailing list archives
Standard defined field names in Wireshark dissectors
From: Tomasz Moń <desowin () gmail com>
Date: Sun, 5 Jan 2020 16:40:36 +0100
Hello, I have noticed that some USB dissectors do follow the field names as defined in USB specification (e.g. standard descriptors), while others don't (e.g. USB Audio class descriptors). Is it generally preferred that Wireshark follows names from the specification (e.g. bTerminalID) instead of coming up with our own (e.g. Terminal ID)? Should we unify the fields so all descriptor fields always use the display names from the respective specification? Best Regards, Tomasz Moń ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Standard defined field names in Wireshark dissectors Tomasz Moń (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Graham Bloice (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Tomasz Moń (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Guy Harris (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Dario Lombardo (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Alexis La Goutte (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Tomasz Moń (Jan 05)
- Re: Standard defined field names in Wireshark dissectors Graham Bloice (Jan 05)