Re: [xrblock] FW:I-DAction:draft-alvestrand-rtcweb-stats-registry-00.txt

Qin Wu <bill.wu@huawei.com> Thu, 27 September 2012 01:19 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA9121F8645 for <xrblock@ietfa.amsl.com>; Wed, 26 Sep 2012 18:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.963
X-Spam-Level:
X-Spam-Status: No, score=-4.963 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLgZAmibFVxA for <xrblock@ietfa.amsl.com>; Wed, 26 Sep 2012 18:19:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB3E21F8643 for <xrblock@ietf.org>; Wed, 26 Sep 2012 18:19:34 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALB84744; Thu, 27 Sep 2012 01:19:33 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 27 Sep 2012 02:18:49 +0100
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 27 Sep 2012 02:19:32 +0100
Received: from w53375 (10.138.41.149) by szxeml406-hub.china.huawei.com (10.82.67.93) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 27 Sep 2012 09:19:21 +0800
Message-ID: <474E342A1F134FD5B462E652A527DD5E@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, xrblock@ietf.org
References: <EDC652A26FB23C4EB6384A4584434A04081AB2D9@307622ANEX5.global.avaya.com><3C8D9E30D9654AD0A3E1F21668D1CBFB@china.huawei.com><EDC652A26FB23C4EB6384A4584434A04081AB4AD@307622ANEX5.global.avaya.com><20E112E82D30472AA48E653041BC0A78@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A04081AB5BE@307622ANEX5.global.avaya.com>
Date: Thu, 27 Sep 2012 09:19:20 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] FW:I-DAction:draft-alvestrand-rtcweb-stats-registry-00.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Sep 2012 01:19:36 -0000

Sure, I will. I also am aware Albrecht has already helped forward the message.
Thanks Albrecht.

Regards!
-Qin
----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
Sent: Wednesday, September 26, 2012 5:57 PM
Subject: Re: [xrblock] FW:I-DAction:draft-alvestrand-rtcweb-stats-registry-00.txt


> Hi Qin,
> 
> If you subscribed to the rtcweb list it would be best that you forward
> directly your comments there - does this seem OK? 
> 
> Dan
> 
> 
> 
> 
>> -----Original Message-----
>> From: Qin Wu [mailto:bill.wu@huawei.com]
>> Sent: Wednesday, September 26, 2012 3:45 AM
>> To: Romascanu, Dan (Dan); xrblock@ietf.org
>> Subject: Re: [xrblock] FW: I-DAction:draft-alvestrand-rtcweb-stats-
>> registry-00.txt
>> 
>> Hi, Dan:
>> I am happy to see my comments being forwarded to rtcweb@ietf.org if
> they
>> are interested and want to more input from XRBLOCK WG. However I am
> not
>> sure how much of their work is related to XRBLOCK work? Do they only
>> look for some basic metrics obtained from SR/RR. But I agree with you
>> consistency between the metrics used by RTCP XR and RTCWEB is a good
>> thing.
>> It will be great to see metrics used by RTCP XR can be used in RTCWEB
> as
>> well.
>> 
>> BTW: I have subscribed to rtcweb list and am interest to join the
>> discussion as I said and expected.
>> 
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>> To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
>> Sent: Tuesday, September 25, 2012 5:45 PM
>> Subject: Re: [xrblock] FW: I-DAction:draft-alvestrand-rtcweb-stats-
>> registry-00.txt
>> 
>> 
>> > Hi Qin,
>> >
>> > Would you like me to forward your comments to rtcweb@ietf.org? You
> can
>> > also subscribe to the list to follow the responses and participate
> in
>> > the discussions, but I should warn you that performance statistics
> are
>> a
>> > fraction of the many problems this very active WG have on their
> hands.
>> >
>> > Dan
>> >
>> >
>> >
>> >> -----Original Message-----
>> >> From: Qin Wu [mailto:bill.wu@huawei.com]
>> >> Sent: Tuesday, September 25, 2012 4:17 AM
>> >> To: Romascanu, Dan (Dan); xrblock@ietf.org
>> >> Subject: Re: [xrblock] FW: I-D
> Action:draft-alvestrand-rtcweb-stats-
>> >> registry-00.txt
>> >>
>> >> Interesting -00 draft.
>> >> Have a quick look at this draft, I have the folowing comments:
>> >> 1. Jitter should also refers to PDV draft since PDV draft provide
>> >> another two measurement methods with different measurement
> precision
>> >> which are different from "inter-arrival jitter" described in
> RFC3550.
>> >> In the early version of PDV draft, we also accomodate
> "inter-arrival
>> >> jitter" and support reporting inter-arrival jitter. However we
> remove
>> >> inter-arrival jitter from this draft based on WG review since
> inter-
>> >> arrival jitter use different measurement unit and has wider range.
>> >> 2.ReceivedPacketCount
>> >> Loss RLE report block can be used to report the packet received. It
>> is
>> >> more staightfoward to calculate ReceivedPacket Count based on  Loss
>> > RLE
>> >> report block defined in RFC3611 rather than based on MIB
> information
>> >> defined in RFC2959. Also in some case, WebClient may not support
>> SNMP.
>> >> So I suggest to refer to section 4.1, RFC3611.
>> >> 3. RecevedOctetCount
>> >> Same as RecevedPacketCount. I think Loss RLE report block also can
> be
>> >> used to calculate RecevedOctetCount.
>> >> It is better to refer to section 4.1, RFC3611.
>> >> 4. Section 4.2 Transport variable
>> >> It is not clear how Transport variable is relate to Variables from
>> > basic
>> >> RTCP SR/RR defined in section 4.1, how transport vaiable is
>> > calculated,
>> >> e.g., what's the relationship between ReceivedPackets and
>> >> ReceivedPacketcount? Are they the same variable?
>> >> Is 4 transport variable defined in section 4.2 sufficient to
> measure
>> > the
>> >> performance of media stream? Why not refer to some variable defined
>> in
>> >> XRBLOCK WG?
>> >>
>> >> Regards!
>> >> -Qin
>> >>
>> >>  ----- Original Message -----
>> >> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>> >> To: <xrblock@ietf.org>
>> >> Sent: Monday, September 24, 2012 7:48 PM
>> >> Subject: [xrblock] FW: I-D Action:draft-alvestrand-rtcweb-stats-
>> >> registry-00.txt
>> >>
>> >>
>> >> >I believe that this I-D (individual submission targeting the
> RTCWEB
>> > WG)
>> >> > is of interest for some of the folks who participate in XRBLOCK.
>> >> > Reaching consistency between the metrics used by RTCP XR and
> RTCWEB
>> >> > (when relevant) seems to be desirable.
>> >> >
>> >> > Regards,
>> >> >
>> >> > Dan
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > -----Original Message-----
>> >> > From: i-d-announce-bounces@ietf.org
>> >> > [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
>> >> > internet-drafts@ietf.org
>> >> > Sent: Monday, September 24, 2012 12:17 PM
>> >> > To: i-d-announce@ietf.org
>> >> > Subject: I-D Action:
> draft-alvestrand-rtcweb-stats-registry-00.txt
>> >> >
>> >> >
>> >> > A New Internet-Draft is available from the on-line
> Internet-Drafts
>> >> > directories.
>> >> >
>> >> >
>> >> > Title           : A Registry for WebRTC statistics identifiers
>> >> > Author(s)       : Harald T. Alvestrand
>> >> > Filename        : draft-alvestrand-rtcweb-stats-registry-00.txt
>> >> > Pages           : 8
>> >> > Date            : 2012-09-24
>> >> >
>> >> > Abstract:
>> >> >   This memo describes a registration procedure for statistics
>> >> >   identifiers used in the WebRTC Javascript API to access
>> > statistical
>> >> >   information about a PeerConnection.
>> >> >
>> >> >   It also gives some identifiers that will, when approved, form
> the
>> >> >   initial content of this registry.
>> >> >
>> >> >
>> >> >
>> >> > The IETF datatracker status page for this draft is:
>> >> > https://datatracker.ietf.org/doc/draft-alvestrand-rtcweb-stats-
>> >> registry
>> >> >
>> >> > There's also a htmlized version available at:
>> >> >
> http://tools.ietf.org/html/draft-alvestrand-rtcweb-stats-registry-
>> 00
>> >> >
>> >> >
>> >> > Internet-Drafts are also available by anonymous FTP at:
>> >> > ftp://ftp.ietf.org/internet-drafts/
>> >> >
>> >> > _______________________________________________
>> >> > I-D-Announce mailing list
>> >> > I-D-Announce@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/i-d-announce
>> >> > Internet-Draft directories: http://www.ietf.org/shadow.html or
>> >> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> >> > _______________________________________________
>> >> > xrblock mailing list
>> >> > xrblock@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/xrblock
>> > _______________________________________________
>> > xrblock mailing list
>> > xrblock@ietf.org
>> > https://www.ietf.org/mailman/listinfo/xrblock
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock