Wireshark-dev: Re: [Wireshark-dev] Dissecting sua info string
Date: Tue, 10 Apr 2007 17:32:59 +0530
Hi Michael,
Thanks for the reply.
The definition of Info string, as you rightly pointed is character string only.
   The optional INFO String parameter can carry any meaningful UTF-8
   [3629] character string along with the message.  Length of the INFO
   String parameter is from 0 to 255 octets.  No procedures are
   presently identified for its use but service providers may use the
   INFO String for debugging purposes.
But as per the last line of the statement- "No procedures are  presently identified for its use but service providers may use the
   INFO String for debugging purposes."
My requirement is to use INFO string for debugging purpose, for that I want to dissect it further or verify it against a predefined format.
Is it possible? How can I do that?
From: Michael Tuexen <[email protected]>
Date: Mon, 9 Apr 2007 18:19:12 +0200

Hi Bhavani,

not sure what you want to achieve. The parameter is defined as a character string and is displayed as a string. So you can not analyze more. And it should be pretty readable right now. From an SUA implementation point of view, you can not assume
that the receiver does anything with it.

Best regards

On Apr 9, 2007, at 1:17 PM, <[email protected]> <[email protected]> wrote:


How to dissect the (proprietary) information present in SUA 'info string' part?
Should I create a separate dissector handle for that?

Please provide your inputs.
Thanks in advance.


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.