W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2012

Re: Proposal for Stats information

From: Aleksandr Avseyev <alexn74@gmail.com>
Date: Mon, 23 Jan 2012 15:21:37 -0800
Message-ID: <CALBppDgY3qdWM-hcgWhG40cp_g-c6MYf4znJss3wEF6y_u7ZLA@mail.gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Cc: public-webrtc@w3.org
   I wonder if anybody else mentioned to add metrics "fps" and "frames
dropped". They're very useful for video quality monitors. They may require
low level access to codec though.

On Mon, Jan 23, 2012 at 8:33 AM, Cullen Jennings <fluffy@cisco.com> wrote:

>
> On all of these, I'm a bit vague on if they are on a PeerConnection, or
> also a Stream or something else. Once it is clearer what each of the
> various objects are, I think it will be clear which objects these stats
> connect to.
>
>
> packetsSentToRemote - sender's packet count as defined in 3550 for this
> side (not remote side)
>
> packetsLostToRemote - cumulative number of packets lost as defined in 3550
> for the remote side
>
> bytesSentToRemote - sender's octet count as defined in 3550 for this side
> (not remote)
>
>
> packetsSentFromRemote - sender's packet count as defined in 3550 for the
> remote side
>
> packetsLostFromRemote - cumulative number of packets lost as defined in
> 3550 for local side
>
> bytesSentFromRemote - sender's octet count as defined in 3550 for the
> remote side
>
>
> roundTripDelay - round trip delay as defined in rfc 3611
>
>
> localJitterBufferNominalDelay - jitter buffer nominal delay as defined in
> rfc 3611for this side
>
> remoteJitterBufferNominalDelay - jitter buffer nominal delay as defined in
> rfc 3611for remote side
>
> localInterarrivalJitter - interarrival jitter defined in 3550 convered to
> units of ms for this side
>
>
>
>


-- 

------------------------------
Regards, Aleksandr Avseyev (Futurewei Research Lab)
www.pictures2.com
Received on Monday, 23 January 2012 23:22:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 January 2012 23:22:06 GMT