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

Varun Singh <> Mon, 21 March 2016 18:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 75F1012DA0E for <>; Mon, 21 Mar 2016 11:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id we1TQttzpqqh for <>; Mon, 21 Mar 2016 11:06:49 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0957412D9E7 for <>; Mon, 21 Mar 2016 11:06:30 -0700 (PDT)
Received: by with SMTP id h198so113701557lfh.0 for <>; Mon, 21 Mar 2016 11:06:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3/IPhSfXC1aBYNJmQYYYnm9FMBKvD84jXCs+1RhVVEg=; b=tZqoboxqiP0dCtR5zMq/+56lUtXq5UdVoZ2ZPBSxvo2uohzW7mGefngV+2359uWJr6 rvM6HAiv30FpfLjoyQ3BXjU5+pXbTusB2KliuL/a6go2n70mIYOc15nPAu7KqMUlMrPQ gn5wk6yal7R65Ax8MSV3kb1VydVkVhnwTYtR6rUVg9UunVNthfj/WBuddOE7cpdBtM90 pgGvIcyb5cqtLLfFTrDZ3bdpX5pMnKgBfrBTyNR3JYKnPfw7g3q7hjbLz7SXelkopZPy +tKsrKx/0b5nix/rZflz8ttdRDbHOAGnhjUkomSK4eik9jArxGo7A3Kc57X37DTdciVf Ep8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3/IPhSfXC1aBYNJmQYYYnm9FMBKvD84jXCs+1RhVVEg=; b=ZlgLh4iWK2H+7Q2WVA6pOr0zL/GungPUClOJRdcDrwC33wXG7Qer9UQnLaXKGpNOy/ rKW/ihu2pkDhilaEfl7dHohebhLjM4O6jnQf/fII5d+tDVvreQteL7/A1X9rnwJ/fkv5 9a75liG6uLTx5w+3wWk+E6iZeoqMHVlDhrm2rc4sM5vUlqafAp7VKyvtLv1qLmECbAwx xfqcKNjtsAZdut5DDoRsD3aELPT/A86G8R4JFSpSATlWRofbaYIOvOubzFZNq9SZQhhI cCClDQiSDwD8YsEqdAXKTnlE20SVI/C4Mdt1ilXJ8EyGrg/vvRe7rKgneHvn/UyKdDHO c4Cw==
X-Gm-Message-State: AD7BkJLJ7R2y4oIK7glUgCBNtZY+mvt4NM5M4ZWecEp7qf//7MEfFu3yLvChhFUfwNjO9xxGYOwmAXyAs0UlWw==
X-Received: by with SMTP id p203mr9005238lfp.48.1458583588203; Mon, 21 Mar 2016 11:06:28 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 21 Mar 2016 11:06:08 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Varun Singh <>
Date: Mon, 21 Mar 2016 20:06:08 +0200
Message-ID: <>
To: "" <>, Colin Perkins <>
Content-Type: text/plain; charset=UTF-8
Archived-At: <>
Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-03.txt
X-Mailman-Version: 2.1.17
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: Mon, 21 Mar 2016 18:06:50 -0000

Hi all,

I updated the reference link and made the following recommendation
(based on the issue raised by Colin Perkins):

   In this document, we provide rationale for choosing additional RTP
   metrics for the WebRTC getStats() API [W3C.WD-webrtc-20150210].  The
   document also creates a registry containing identifiers from the
   metrics reported in the RTCP Sender, Receiver, and Extended Reports.
   All identifiers proposed in this document are RECOMMENDED to be
   implemented by an endpoint.  An endpoint MAY choose not to expose an
   identifier if it does not implement the corresponding RTCP Report.

I believe the document ought to make a stronger recommendation than OPTIONAL.
The document does provide enough rationale for implementing the additional

Although, in the end I went with "SHOULD implement if the
corresponding XRBLOCK is implemented."

Feedback on the above proposal is much appreciated.


On Mon, Mar 21, 2016 at 7:59 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 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-03.txt
>         Pages           : 18
>         Date            : 2016-03-21
> 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