Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt

"Roni Even" <> Thu, 26 March 2015 14:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 193271ACDA2 for <>; Thu, 26 Mar 2015 07:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OoMVZ4xT8Ofq for <>; Thu, 26 Mar 2015 07:14:53 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 07C681ACE9A for <>; Thu, 26 Mar 2015 07:14:50 -0700 (PDT)
Received: by wiaa2 with SMTP id a2so24504067wia.0 for <>; Thu, 26 Mar 2015 07:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:thread-index:content-language; bh=Gi9tSdH4nvPyMHJWr/0xmH6vc8uZq83xkHEwFtBtWPA=; b=cG3mZBId++MAOXCP0wPogO+Ju0fKVLIuozvdQu3CaqNA4R2Hgx7OG/GKVsAkFyuIn6 xF/Sn5gHy0DUdWUSsaS7DzfPxS4BunqPbWF9YuPjJahKHKfJqn6XhQYOUm0f5SpDBzmC NECZmSqgydxoH/pAH86SBme+ZzikD48uXUHL6OWUW2l4amFvlLzSynYOnCMEFvfY6hli HfchO1wA7yMCdOEFPis1d0p1opXXl0JCufGNvs9vu9XejYZFrlrPyp1EQ3HjDn7UrEbY Q0fXSd01i68JKOPc/oqbHU2BcVXfXYUX2M8QwV13bXWxojD1SqBr1KkLN8s8K6mS/56E SX1A==
X-Received: by with SMTP id gc2mr21317391wib.34.1427379289630; Thu, 26 Mar 2015 07:14:49 -0700 (PDT)
Received: from RoniE ([2001:67c:370:136:f4be:a22f:60cf:9b4a]) by with ESMTPSA id o10sm21816664wiy.18.2015. (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 26 Mar 2015 07:14:48 -0700 (PDT)
From: Roni Even <>
To: 'Varun Singh' <>,
References: <> <>
In-Reply-To: <>
Date: Thu, 26 Mar 2015 16:14:43 +0200
Message-ID: <005f01d067cf$36e1e710$a4a5b530$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0060_01D067DF.FA6BA170"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLhqxgr0qJSgiauWsHDEfnaOI1O2QKx058lmva4/yA=
Content-Language: en-us
Archived-At: <>
Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Mar 2015 14:14:56 -0000

Hi Varun,

I think that we can keep 6.7 and remove 6.8. Having the actual numbers allows for calculating rate and other statistics, so I find it more useful

Roni Even


From: xrblock [] On Behalf Of Varun Singh
Sent: 28 February, 2015 10:48 PM
Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt


Hi all,

The -01 draft incorporates the changes discussed at IETF 91.
- new registry defined for WebRTC Statistics API
- added the SR and RR metrics, which were earlier in draft-alvestrand-rtcweb-stats-registry
- changed the TitleCased identifiers to camelCase, to keep consistency with the W3C document.

OPEN ISSUE (burst metrics):
The document currently defines two sets of burst metrics
- Section 6.7: Reports cumulative packets in a burst and the corresponding burst counts. 
- Section 6.8.: Reports the average fraction of packets lost in a burst/gap.

>From section 6.7, we can infer the average burst of packet loss/discards by dividing the total_packets_lost_in_burst/burst_count.
>From section 6.8, we can infer the impact of the burst packet loss, i.e., total_burst_loss/totel_expected_packets/burst_count

Do we keep both? or pick one? 

Thoughts and comments on the open issue and the document in general are appreciated. 

Varun (on behalf of the authors)

On Sat, Feb 28, 2015 at 7:22 PM, <> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Metric Blocks for use with RTCP's Extended Report Framework Working Group of the IETF.
> Title : Considerations for Selecting RTCP Extended Report (XR) Metrics for the WebRTC Statistics API
> Authors : Varun Singh
> Rachel Huang
> Roni Even
> Dan Romascanu
> Lingli Deng
> Filename : draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt
> Pages : 17
> Date : 2015-02-28
> Abstract:
> This document describes monitoring features related to media streams
> in Web real-time communication (WebRTC). It provides a list of RTCP
> Sender Report, Receiver Report and Extended Report metrics, which may
> need to be supported by RTP implementations in some diverse
> environments. It also defines a new IANA registry, a list of
> identifiers for the WebRTC's statistics API. These identifiers are a
> set of RTCP SR, RR, and XR metrics related to the transport of
> multimedia flows.
> The IETF datatracker status page for this draft is:
> There's also a htmlized version available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> xrblock mailing list