https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5307
--- Comment #2 from Anders Broman <anders.broman@xxxxxxxxxxxx> 2010-10-18 03:46:53 PDT ---
The "problem" the function is trying to solve is when in a protocol something
is specified as OctetString or an opaque blob of octets. Some implementations
may chose to put a "text" string in there, when dissecting that "blob" it can
be nice to display the "string" in the protocol tree.
As noted it can be problematic with the text encoding but "Printable ASCII"
wolud probably cover most cases and if something else is reqired a new function
can be defined or the encoding to check for added as an in parameter.
To be more speciffic what broght this up is a case where an 3GPP AVP is
specified as "avp name="3GPP-CG-IPv6-Address type-name="OctetString"
an application could then chose to put the binary representation of the address
in the data or a string. In the case of a string it could be nice to have that
printed. The "solution" would be to put code in diameter-3gpp.c for this
AVP and check wheter it has ASCII printable text or not and put the
IPv6 address or the string in the tree.
We have similar checks in other dissectors which could use the new service
function insted.
Regards
Anders
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
