Harald, A couple of suggestions: - This uses RTCP Payload-specific feedback messages, with the Application Layer feedback (AFB) FMT parameter and a 4 octet unique identifier (REMB) inside the feedback section. The AFB message was intended to be private for a particular application, and not something that should be standard. This would be better registered as a new FMT value within the payload-specific feedback messages. Doing so would also save 4 octets, since you wouldn't need to unique identifier field. - You have an SSRC feedback field but don't use the SSRC of media source. Would it make sense to use the SSRC of media source to hold the first entry of the SSRC feedback field, and put the others in the payload? Again, saves 4 octets, and avoids a wasted field. Colin On 17 Jan 2012, at 12:55, Harald Alvestrand wrote:
This is the broken-out version of the REMB message that was published in an appendix of the congestion-control draft I posted just before Taipei.
After discussions inside Google, we decided that the timestamp header extension didn't offer enough value over the RFC 5450 send-time offset header extension, so we dropped it from the draft.
Harald
-------- Original Message -------- Subject: New Version Notification for draft-alvestrand-rmcat-remb-00.txt Date: Tue, 17 Jan 2012 04:54:00 -0800 From: internet-drafts@ietf.org To: harald@alvestrand.no CC: harald@alvestrand.no
A new version of I-D, draft-alvestrand-rmcat-remb-00.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.
Filename: draft-alvestrand-rmcat-remb Revision: 00 Title: RTCP message for Receiver Estimated Maximum Bitrate Creation date: 2012-01-17 WG ID: Individual Submission Number of pages: 7
Abstract: This document proposes an RTCP message for use in experimentally- deployed congestion control algorithms for RTP-based media flows.
The IETF Secretariat
_______________________________________________ Rtp-congestion mailing list Rtp-congestion@alvestrand.no http://www.alvestrand.no/mailman/listinfo/rtp-congestion
-- Colin Perkins http://csperkins.org/