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

Varun Singh <vsingh.ietf@gmail.com> Mon, 18 May 2015 08:06 UTC

Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9A821A87A8 for <xrblock@ietfa.amsl.com>; Mon, 18 May 2015 01:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level:
X-Spam-Status: No, score=-0.799 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, J_CHICKENPOX_41=0.6, J_CHICKENPOX_92=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlyF2Okg1eAE for <xrblock@ietfa.amsl.com>; Mon, 18 May 2015 01:06:31 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E39C11A878E for <xrblock@ietf.org>; Mon, 18 May 2015 01:06:30 -0700 (PDT)
Received: by lagr1 with SMTP id r1so125692713lag.0 for <xrblock@ietf.org>; Mon, 18 May 2015 01:06:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=9TY+APrvjsFo/Dy3OT9iMfj4j81WJlLjR/qrVXi/wgg=; b=WS1dt8hDsrXMwUr48W5qUksMl/leKfBoQifrjUTSHyMgBYKNpnD9dsi0o3toaoyXEF tRtcMIw/EsFZ/wfTvS6i9drDoUv5C/OOArNA2JKUdigN8DziEOlDULh4H/kvoYNQoui4 YG6bbpM+lM8lXRfLw2tyUcuGOZtX4pTeKUFYE0Ir2dxN+xEEOiQBMD3SJ3sL893Bzj5e 3KHx9cVrg9IMG5zuwsuPkUV0JSrofHKB/24rguYubRZQqFdbh579LfriyobFEUfqybxd U1gPEUHwyuAjvAzGVdQl6iy2DMEPkKxMC55kyfrtgoOe/zP0kpgum81GAfptA0Nl/ZLd sUhw==
X-Received: by 10.152.6.39 with SMTP id x7mr16258375lax.18.1431936389317; Mon, 18 May 2015 01:06:29 -0700 (PDT)
MIME-Version: 1.0
References: <20150228172233.11376.10175.idtracker@ietfa.amsl.com> <CAEbPqrwxzBk4kr+XgFwdBOUDaiPyLz--22T3kx-uR8WX7JHsCw@mail.gmail.com> <005f01d067cf$36e1e710$a4a5b530$@gmail.com> <CAEbPqrwR10MbKx3badtsVHaEiJZ1EarBaz633z_nQEXawE5CAQ@mail.gmail.com> <51E6A56BD6A85142B9D172C87FC3ABBB863097D9@nkgeml501-mbs.china.huawei.com> <96D67F82-6E42-4057-87DA-C1C0E34AFA85@ntt-at.com> <CAEbPqrz3jBOgXvL-DPa=+z=9NV=pGS-QjJK-_2rNR70hPHPSag@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5CA31549@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5CA31549@AZ-FFEXMB04.global.avaya.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Mon, 18 May 2015 08:06:28 +0000
Message-ID: <CAEbPqrzodQGtKVtS7jAAabG6zqnZ2cDc94adtdxdadSg2vmUnQ@mail.gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Shida Schubert <shida@ntt-at.com>
Content-Type: multipart/alternative; boundary="089e013d1922d38b48051656ab26"
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/YwTzkfaoXkMvBw1-9nRZRqv7r2s>
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2015 08:06:35 -0000

Yes, however I would prefer we resolve the next steps for the eratta before
the meeting as the resulting reference may be needed for the webrtc-metrics
draft.

On Sun 17 May, 2015 16:14 Romascanu, Dan (Dan) <dromasca@avaya.com> wrote:

> Hi Varun,
>
> Thanks for following up. IMO we can go ahead with an errata.
>
> We are planning the agenda for a meeting at IETF 93 - should we include
> this on the agenda?
>
> Thanks and Regards,
>
> Dan
>
>
> > -----Original Message-----
> > From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Varun Singh
> > Sent: Sunday, May 17, 2015 2:01 PM
> > To: Shida Schubert
> > Cc: xrblock
> > Subject: Re: [xrblock] I-D Action:
> draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-
> > 01.txt
> >
> > Hi Shida, Dan,
> >
> > Following up on the email, what is the suggested next step? Should I go
> > ahead and report an errata?
> >
> > On Sat, Mar 28, 2015 at 7:53 PM, Shida Schubert <shida@ntt-at.com>
> wrote:
> > > Hi;
> > >
> > >  So looking at
> > >
> > >
> > > https://urldefense.proofpoint.com/v2/url?u=http-
> > 3A__www.ietf.org_iesg_
> > > statement_errata-
> > 2Dprocessing.html&d=AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r
> > >
> > =I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=EO2lZ9ZXM56Ouuop
> > 5sSOo6_
> > > J48bwWZeMPcbkas3y7GE&s=OExds-hSrs-
> > TVixjuKhfH84nufIZjBl_k3CDIYWVmII&e=
> > >
> > >  My feeling is that we can probably do this as an errata.
> > >
> > >  I do think some of the people contributing to this WG who have
> > > experience chairing long running WG where errata/bis are common can
> > > probably give better guidance though.
> > >
> > >  Thanks
> > >
> > >  Shida as co-chair
> > >
> > > On Mar 26, 2015, at 9:05 AM, Huangyihong (Rachel)
> > > <rachel.huang@huawei.com>
> > > wrote:
> > > Dear all,
> > >
> > > I prefer 6.7 too. As for the issue raised by Varun, will it be a
> > > technical errata to RFC7003 or a new draft to define the missing
> metric?
> > >
> > > BR,
> > > Rachel
> > >
> > > -----邮件原件-----
> > > 发件人: xrblock [mailto:xrblock-bounces@ietf.org] 代表 Varun Singh
> > > 发送时间: 2015年3月26日 23:45
> > > 收件人: Roni Even
> > > 抄送: xrblock@ietf.org
> > > 主题: Re: [xrblock] I-D Action:
> > > draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt
> > >
> > > Thank you Roni for the review and  feedback.
> > >
> > > I too prefer 6.7, however, 6.8 has gapDiscardRate and gapLossRate in
> > > addition to burstDiscardRate and burstLossRate, which cannot be
> > > derived by the raw information in 6.7.
> > > Would we be unhappy if the gapRates were removed or missing?
> > >
> > > The other minor issue/bug within 6.7, that there is no definition for
> > > burstDiscardCount in any XR draft. This would require a new draft and
> > > can be proceeded in parallel.
> > >
> > >
> > > -Varun
> > >
> > > On Thu, Mar 26, 2015 at 9:14 AM, Roni Even <ron.even.tlv@gmail.com>
> > wrote:
> > >
> > > 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 [mailto:xrblock-bounces@ietf.org] On Behalf Of Varun
> > > Singh
> > > Sent: 28 February, 2015 10:48 PM
> > > To: xrblock@ietf.org
> > > 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.
> > >
> > > Regards,
> > > Varun (on behalf of the authors)
> > >
> > >
> > >
> > >
> > > On Sat, Feb 28, 2015 at 7:22 PM, <internet-drafts@ietf.org> 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:
> > >
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.
> > > org_doc_draft-2Dietf-2Dxrblock-2Drtcweb-2Drtcp-2Dxr-
> > 2Dme&d=AwIGaQ&c=BF
> > >
> > pWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBs
> > FA&m=E
> > >
> > O2lZ9ZXM56Ouuop5sSOo6_J48bwWZeMPcbkas3y7GE&s=neenIlYE5xe8Vc4l
> > N15SD_GkT
> > > vEs0VYwnuG3ynro0xo&e=
> > > trics/
> > >
> > > There's also a htmlized version available at:
> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__tools.ietf.org_htm
> > > l_draft-2Dietf-2Dxrblock-2Drtcweb-2Drtcp-2Dxr-2Dmetrics-
> > 2D&d=AwIGaQ&c=
> > >
> > BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphp
> > BsFA&m
> > >
> > =EO2lZ9ZXM56Ouuop5sSOo6_J48bwWZeMPcbkas3y7GE&s=MYuqYpmmcQk
> > QUmrNbQTbBIY
> > > gCb8iwtXK_CWVlAHGXyU&e=
> > > 01
> > >
> > > A diff from the previous version is available at:
> > >
> > > https://urldefense.proofpoint.com/v2/url?u=http-
> > 3A__www.ietf.org_rfcdi
> > > ff-3Furl2-3Ddraft-2Dietf-2Dxrblock-2Drtcweb-2Drtcp-2Dxr-
> > 2Dme&d=AwIGaQ&
> > >
> > c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrp
> > hpBsFA
> > >
> > &m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwWZeMPcbkas3y7GE&s=WKAWKHL0J
> > yGPuxdTah1Fq
> > > -Vl8bUMurrLjjp8x2A6tFQ&e=
> > > trics-01
> > >
> > >
> > > Please note that it may take a couple of minutes from the time of
> > > submission until the htmlized version and diff are available at
> > > tools.ietf.org.
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_intern
> > > et-
> > 2Ddrafts_&d=AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJf
> > Qzvls
> > >
> > iLQfucBXRucPvdrphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwWZeMPcb
> > kas3y7GE&s
> > > =Wd1Y2mmuSsLPjjom7r4hja57VJm28DUZRdC-Y9QFoCg&e=
> > >
> > > _______________________________________________
> > > xrblock mailing list
> > > xrblock@ietf.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mail
> > >
> > man_listinfo_xrblock&d=AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> > R31OcNX
> > >
> > CJfQzvlsiLQfucBXRucPvdrphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwW
> > ZeMPcbka
> > > s3y7GE&s=RWAF5uzqT9QGJTnAXaZjq3ufFyTkivqnEqnJNbdXeV4&e=
> > >
> > >
> > > --
> > > https://urldefense.proofpoint.com/v2/url?u=http-
> > 3A__www.callstats.io&d
> > >
> > =AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucB
> > XRucPvd
> > >
> > rphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwWZeMPcbkas3y7GE&s=O_
> > P33m2YRIHra
> > > IvYOLkQ5T3XZbo_NoIOLig96SgWqCw&e=
> > >
> > >
> > >
> > >
> > > --
> > > https://urldefense.proofpoint.com/v2/url?u=http-
> > 3A__www.callstats.io&d
> > >
> > =AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucB
> > XRucPvd
> > >
> > rphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwWZeMPcbkas3y7GE&s=O_
> > P33m2YRIHra
> > > IvYOLkQ5T3XZbo_NoIOLig96SgWqCw&e=
> > >
> > > _______________________________________________
> > > xrblock mailing list
> > > xrblock@ietf.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mail
> > >
> > man_listinfo_xrblock&d=AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> > R31OcNX
> > >
> > CJfQzvlsiLQfucBXRucPvdrphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwW
> > ZeMPcbka
> > > s3y7GE&s=RWAF5uzqT9QGJTnAXaZjq3ufFyTkivqnEqnJNbdXeV4&e=
> > > _______________________________________________
> > > xrblock mailing list
> > > xrblock@ietf.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mail
> > >
> > man_listinfo_xrblock&d=AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> > R31OcNX
> > >
> > CJfQzvlsiLQfucBXRucPvdrphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6_J48bwW
> > ZeMPcbka
> > > s3y7GE&s=RWAF5uzqT9QGJTnAXaZjq3ufFyTkivqnEqnJNbdXeV4&e=
> > >
> > >
> >
> >
> >
> > --
> > https://urldefense.proofpoint.com/v2/url?u=http-
> > 3A__www.callstats.io&d=AwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> > R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=EO2lZ9ZXM56Ouuop5sSOo6
> > _J48bwWZeMPcbkas3y7GE&s=O_P33m2YRIHraIvYOLkQ5T3XZbo_NoIOLig96S
> > gWqCw&e=
> >
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mailman_listinfo_xrblock&d=AwIGaQ&c=BFpWQw8bsuK
> > pl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=EO2lZ
> > 9ZXM56Ouuop5sSOo6_J48bwWZeMPcbkas3y7GE&s=RWAF5uzqT9QGJTnAX
> > aZjq3ufFyTkivqnEqnJNbdXeV4&e=
>