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

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 26 March 2015 16:05 UTC

Return-Path: <rachel.huang@huawei.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 32D7C1AD259 for <xrblock@ietfa.amsl.com>; Thu, 26 Mar 2015 09:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.078
X-Spam-Level: **
X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 q4J4hev9Fnoo for <xrblock@ietfa.amsl.com>; Thu, 26 Mar 2015 09:05:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E634B1AD151 for <xrblock@ietf.org>; Thu, 26 Mar 2015 09:05:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUE17228; Thu, 26 Mar 2015 16:05:24 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 26 Mar 2015 16:05:23 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Fri, 27 Mar 2015 00:05:20 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Varun Singh <vsingh.ietf@gmail.com>, Roni Even <ron.even.tlv@gmail.com>
Thread-Topic: [xrblock] I-D Action: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01.txt
Thread-Index: AQHQU5fQPyzjkQdDmUuumKfAFiJIFZ0ucR2AgAAZJgCAAIsp8A==
Date: Thu, 26 Mar 2015 16:05:19 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB863097D9@nkgeml501-mbs.china.huawei.com>
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>
In-Reply-To: <CAEbPqrwR10MbKx3badtsVHaEiJZ1EarBaz633z_nQEXawE5CAQ@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.148.229]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/wILh5JKPFzJzJchkGw8B0ONgvco>
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
Subject: [xrblock] =?gb2312?b?tPC4tDogIEktRCBBY3Rpb246IGRyYWZ0LWlldGYteHJi?= =?gb2312?b?bG9jay1ydGN3ZWItcnRjcC14ci1tZXRyaWNzLTAxLnR4dA==?=
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: Thu, 26 Mar 2015 16:05:41 -0000

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://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-me
>> trics/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-
>> 01
>>
>> A diff from the previous version is available at:
>>
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-xrblock-rtcweb-rtcp-xr-me
>> 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:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock
>
> --
> http://www.callstats.io



--
http://www.callstats.io

_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock