IETF Logo Mail Archive

Re: [xrblock] Fw: I-D Action: draft-ietf-xrblock-rtcp-xr-jb-06.txt

Qin Wu <bill.wu@huawei.com> Fri, 11 January 2013 01:00 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 C279D21F88B0 for <xrblock@ietfa.amsl.com>; Thu, 10 Jan 2013 17:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.846
X-Spam-Level:
X-Spam-Status: No, score=-4.846 tagged_above=-999 required=5 tests=[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 w69ZdKcNGqk6 for <xrblock@ietfa.amsl.com>; Thu, 10 Jan 2013 17:00:42 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 75EFB21F8556 for <xrblock@ietf.org>; Thu, 10 Jan 2013 17:00:41 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ANJ41509; Fri, 11 Jan 2013 01:00:40 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 Jan 2013 00:59:24 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 Jan 2013 09:00:39 +0800
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; Fri, 11 Jan 2013 09:00:34 +0800
Message-ID: <6B8FB43C2E194F489D8F49D39683F957@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, xrblock@ietf.org
References: <217E1B5D0584495D884BEE81E98E5BC1@china.huawei.com> <9904FB1B0159DA42B0B887B7FA8119CA05E31B@AZ-FFEXMB04.global.avaya.com>
Date: Fri, 11 Jan 2013 09:00:33 +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-D Action: draft-ietf-xrblock-rtcp-xr-jb-06.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: Fri, 11 Jan 2013 01:00:42 -0000

I have clarified the issues raised by Glen and Kevin on the list. 
But I haven't got confirmation from them, especially on change back 2 bit jitter buffer configuration field into one. 

In my understanding, this version is ready for submission to IESG unless they have additional proposed
text or change.

Regards!
-Qin
----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Qin Wu" <bill.wu@huawei.com>; <xrblock@ietf.org>
Sent: Thursday, January 10, 2013 7:54 PM
Subject: RE: [xrblock] Fw: I-D Action: draft-ietf-xrblock-rtcp-xr-jb-06.txt


Thanks, Qin. 

Is this ready now for submission to the IESG? 

Regards,

Dan




> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Qin Wu
> Sent: Thursday, January 10, 2013 11:45 AM
> To: xrblock@ietf.org
> Subject: [xrblock] Fw: I-D Action: draft-ietf-xrblock-rtcp-xr-jb-06.txt
> 
> On 10 January , 2012 5:23 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           : RTP Control Protocol (RTCP) Extended Report (XR)
> Block for Jitter Buffer Metric Reporting
> > Author(s)       : Alan Clark
> >                          Varun Singh
> >                          Qin Wu
> > Filename        : draft-ietf-xrblock-rtcp-xr-jb-06.txt
> > Pages           : 16
> > Date            : 2013-01-10
> >
> > Abstract:
> >   This document defines an RTP Control Protocol (RTCP) Extended Report
> >   (XR) Block that allows the reporting of Jitter Buffer metrics for a
> >   range of RTP applications.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-jb
> 
> [Qin]: This version reflects one minor change based on recent discussion
> with Kevin and Glen on the list.
> One main change is to  change 2bit jitter buffer configuration field
> back into1 bit field since adaptive jitter buffer in my understanding
> should always change buffer size to react to some events and can not
> have a fixed buffer size.
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

v2.23.0 | Report a Bug | By Email