Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Terminating NULL chraracter in RTCP Bye reason string

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 5 Aug 2008 09:59:54 -0700


On Aug 5, 2008, at 7:23 AM, Vinod M wrote:

"Optionally, the BYE packet MAY include an 8-bit octet count followed
by that many octets of text indicating
the reason for leaving, e.g., "camera malfunction" or "RTP loop detected".
 The string has the same encoding as that described for SDES.
 If the string fills the packet to the next 32-bit boundary, the
string is not null terminated."

It sounds as if whoever wrote RFC 3550 needs to learn the difference between the words "padded" and "terminated" - they probably meant to say that the string is null-*padded* to a 4-byte boundary.

  • Follow-Ups:
    • Re: [Wireshark-dev] Terminating NULL chraracter in RTCP Byereason string
      • From: Neil Piercy
  • References:
    • [Wireshark-dev] Terminating NULL chraracter in RTCP Bye reason string
      • From: Vinod M
  • Prev by Date: Re: [Wireshark-dev] Terminating NULL chraracter in RTCP Bye reason string
  • Next by Date: [Wireshark-dev] Windows build environment changes
  • Previous by thread: Re: [Wireshark-dev] Terminating NULL chraracter in RTCP Bye reason string
  • Next by thread: Re: [Wireshark-dev] Terminating NULL chraracter in RTCP Byereason string
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation