- From: Cullen Jennings <fluffy@cisco.com>
- Date: Mon, 13 Feb 2012 09:02:18 -0700
- To: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Feb 13, 2012, at 6:08 AM, Stefan Hakansson LK wrote: >> >> >>> * The API should allow the application to check if data is being >>> buffered (so that it can adjust the send rate) >> >> uh - I have no idea what this even means. Of course it is buffered - >> it's a transport. Need to know more. > > The app should be able to determine if more and more data is being buffered locally - that is a sign that the app is trying to send more data than the channel can carry. So the user land SCTP is going to be buffering, and at the same time dropping out UDP packets which the kernel will be buffering then there is the nic cards, routers, etc that all buffer. What makes sense to me is a way to find the current depth of the SCTP buffer. Trying to figure out how much UDP data the kernel/nic had buffered seems like it could get hard but it could be a large number so it perhaps you have to know this to make things really work. Given some of the SCTP streams may be reliable, some unreliable, and there are multiple at the same time, It's not clear to me if you want to report just the buffered data for single SCTP stream or for the aggregate buffering across the SCTP association.
Received on Monday, 13 February 2012 16:02:56 UTC