Re: [AVT] I-D ACTION:draft-ietf-avt-rtcp-non-compound-02.txt

[Colin Perkins <csp at csperkins.org>]

On 8 Feb 2008, at 23:45, Internet-Drafts at ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Audio/Video Transport Working  
> Group of the IETF.
>
> 	Title		: Support for non-compound RTCP, opportunities and  
> consequences
> 	Author(s)	: I. Johansson, M. Westerlund
> 	Filename	: draft-ietf-avt-rtcp-non-compound-02.txt
> 	Pages		: 16
> 	Date		: 2008-2-8
> 	
> This memo discusses benefits and issues that arise when allowing RTCP
> packets to be transmitted as non-compound packets, i.e not follow the
> rules of RFC 3550.  Based on that analysis this memo proposes changes
> to the rules to allow feedback messages to be sent as non-compound
> RTCP packets when using the RTP AVPF profile (RFC 4585) under certain
> conditions.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-non- 
> compound-02.txt

While I haven't had chance to read the analysis of the algorithmic  
changes, I have two comments on the other details:

Section 6.1: a simple test that non-compound packets are not rejected  
out-of-hand might be to send a non-compound SR packet, then check  
that the timestamp is echoed back in the corresponding RR packet?

Section 6.2.1: the first four bullet points are unnecessary, since  
non-compound packets can be detected by comparing their size with the  
size of the containing transport layer packet.

-- 
Colin Perkins
http://csperkins.org/


_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
http://www.ietf.org/mailman/listinfo/avt