Fields registered to non-parent protocol (e.g. ftp and ftp-data)

[chuck c <bubbasnmp () gmail com>]

Is it a typo when fields are not registered to the parent protocol or
should README.dissector describe if/when this is acceptable?


> From README.dissector:
"abbrev (FIELDABBREV)

--------------------A string with an abbreviation of the field. The
abbreviation should startwith the abbreviation of the parent protocol
followed by a period as aseparator."


Protocol registration is handled by creating an instance of the

header_field_info struct (or an array of such structs), and
calling the registration function along with the registration ID of
the protocol that is the parent of the fields.

A few examples:
https://www.wireshark.org/docs/dfref/f/ftp.html
https://www.wireshark.org/docs/dfref/r/rtmac.html
https://www.wireshark.org/docs/dfref/w/wpan.html

___________________________________________________________________________
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