The content of RTCP

590 views
Skip to first unread message

manphis chen

unread,
Jun 13, 2013, 9:11:06 PM6/13/13
to discuss...@googlegroups.com
Dear all,

Recently I am investigating the feedback mechanism for rate control in webrtc.

Does the receiver use RTCP to inform the sender about the information such as available bandwidth, lossy ratio, .., etc.?

Besides, is the rate control information, such as available bandwidth, appended to RTCP packets in the form of TMMBR (or REMB)?

I check the packet format by wireshark.
I found that RR (Receiver Report) is appended to SR (Sender Report), and there is extra information appended after RR, but wireshark cannot recognize it.

How can I know the exact information in RTCP control packets?

Does anyone has the same experience?
Or is there any document describing the details of the feedback mechanism or the format of the feedback packets in webrtc?

Many thanks

Dennis

unread,
Jun 14, 2013, 6:28:59 AM6/14/13
to discuss...@googlegroups.com
You're going to want to read the ietf drafts that describe usage of RTP and RTCP in WebRTC https://datatracker.ietf.org/wg/rtcweb/ , specifically the latest 'Web Real-Time Communication (WebRTC): Media Transport and Use of RTP' document.  As far as report blocks after sender reports, that is normal and expected with bi-directional sessions.  The "extra information" after the RTCP reports is related to security (SRTP/crypto/message auth data).  The reports themselves are encrypted so wireshark isn't going to help you out much as far as inspecting the data on the wire in SRs and RRs.  You're also going to want to read the ietf security drafts to learn more about how cryptography works with WebRTC.

Justin Uberti

unread,
Jun 16, 2013, 4:53:04 PM6/16/13
to discuss-webrtc
You can read the details on the REMB algorithm used in Chrome and Firefox here: http://tools.ietf.org/html/draft-alvestrand-rmcat-congestion-00


--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

ebu...@thrupoint.com

unread,
Jun 17, 2013, 6:01:39 AM6/17/13
to discuss...@googlegroups.com
When I was coding things related to RTCP I found the easiest way to work with wireshark was to compile Chromium with encryption/decryption turned off for RTCP. I also got the bytes to be printed out in logs at other times as this is what you are really working with.

Eric

Dong Fangshuo

unread,
Oct 14, 2013, 1:43:40 AM10/14/13
to discuss...@googlegroups.com
hello Eric,

I am trying to disable encryption/decryption for RTCP, but could not make it.
Could you give some help?

Thanks,

Wei

V

unread,
Apr 26, 2014, 10:26:42 PM4/26/14
to discuss...@googlegroups.com
Wei,

I'm not sure if you completed your investigating or even if whats in webrtc now resembles what you did back then.  I'm wondering if you could share some of your findings.


On Thursday, June 13, 2013 9:11:06 PM UTC-4, manphis chen wrote:
Reply all
Reply to author
Forward
0 new messages