Ethereal-dev: Re: [Ethereal-dev] Compound RTCP messages not decoded

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 28 Oct 2003 02:01:23 -0800
On Thu, Oct 23, 2003 at 08:53:26PM -0500, Martin Renschler (CA/EWU) wrote:
> RTCP supports stacked messages, called compound RTCP.  The first
> message is an RR message, but others, like SDES will then follow. 
> Ethereal stops displaying after the first RR message (which is usually
> a dummy with no reports) and shows the beginning of the next RTCP
> message as "Sender SSRC". 

Are you saying that the sender SSRC isn't always present in an RR
packet?  Where does it say that's valid (except perhaps by implication,
with a length of 0 meaning that the SSRC isn't present, as that means
the packet is 1)?  RFC 1889 seems to suggest that the sender SSRC would
be part of the fixed header; it doesn't say what an empty RR is other
than one that has a count of 0 (meaning no report blocks).