Re: [xrblock] Pointer to Active Registry Draft and RTCP-XR example metric

Varun Singh <> Fri, 25 July 2014 17:06 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id ED57F1A03B1 for <>; Fri, 25 Jul 2014 10:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Z7Gu4ZpHbgav for <>; Fri, 25 Jul 2014 10:06:56 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2309A1A0371 for <>; Fri, 25 Jul 2014 10:06:56 -0700 (PDT)
Received: by with SMTP id y20so4079736ier.13 for <>; Fri, 25 Jul 2014 10:06:55 -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 :cc:content-type; bh=rP0qgvGfJaJvAPq52Be4i/djxuuUcFnkh3FrtlfKvCg=; b=dz8F4IW/prhSAt9G8s+/8Z/aCQa3Dk7IxUBmxdm+2hEtgat08gvuXnTmP7xRXYuDCF GQwi6sJdf01uH8fXYtNWQ4uvC5cbL0ETtZQX1LtRmaT0BIehZs4jMZns4pRHxpGr1h76 lpAAB4gETIp+EOLEbxf8wp6sj4IduGaGtUJ0c8jw5dxJCBRkhXEuA0DmXgW96FgPz76z 5Vlmuwh64FJCBxkV586mZnqAOYx1UAdfwK+iWjD3Mq+/bTleqZeNxd0r8dhU5JqSiEsd UtdkOf/lzLHtxDMHHZGFWSUoNfvH5WU3+HVeUCNxTkBi+Ih3s8nel2AIYjVF9uHYtBKK ISQw==
X-Received: by with SMTP id gy7mr7344865igb.15.1406308015539; Fri, 25 Jul 2014 10:06:55 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 25 Jul 2014 10:06:35 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Varun Singh <>
Date: Fri, 25 Jul 2014 13:06:35 -0400
Message-ID: <>
Content-Type: text/plain; charset="UTF-8"
Cc: "" <>
Subject: Re: [xrblock] Pointer to Active Registry Draft and RTCP-XR example metric
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: Fri, 25 Jul 2014 17:06:58 -0000

Hi Al,

I looked at the IPPM active registry draft and below are my thoughts:

The current rtcp-xr-metrics draft attempts to map the XR metrics to an
API identifier. These API identifiers would be exposed by the browser
to the Javascript application by the WebRTC StatsAPI. Hence, I think a
new registry would make more sense -- listing only the metric identifiers
related to WebRTC and their corresponding definition, data-type, and
measurement interval and value range.

Currently the recommended metrics for WebRTC are a subset of the
metrics defined in XRBLOCK.

The IPPM registry on the other hand imports the RFC6390 template from
each XRBLOCK document, I hope this new registry will eventually list all
the active metrics (not only the ones developed in XRBLOCK), and be a
good source to look for existing metrics before defining new ones.


On Tue, Jul 22, 2014 at 1:46 PM, MORTON, ALFRED C (AL) <> wrote:
> I'd like your feedback on this draft/example, as a co-author.
> It would be fine to post it to the ippm-list, too.
> note that the eventual plan is to combine passive and active registries.
> there are references in the draft above to the common draft, which
> will inherit all the active columns, etc. soon.
> Al
> _______________________________________________
> xrblock mailing list