Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt

Qin Wu <bill.wu@huawei.com> Thu, 13 December 2012 09:45 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 C728E21F8958 for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 01:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.681
X-Spam-Level:
X-Spam-Status: No, score=-4.681 tagged_above=-999 required=5 tests=[AWL=0.165, 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 Hvu6qx5+qC2m for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 01:45:53 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5D5C121F8934 for <xrblock@ietf.org>; Thu, 13 Dec 2012 01:45:52 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ANU42425; Thu, 13 Dec 2012 09:45:50 +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; Thu, 13 Dec 2012 09:44:52 +0000
Received: from SZXEML450-HUB.china.huawei.com (10.82.67.193) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 13 Dec 2012 17:45:45 +0800
Received: from w53375 (10.138.41.149) by szxeml450-hub.china.huawei.com (10.82.67.193) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 13 Dec 2012 17:45:39 +0800
Message-ID: <76CB4CC914C74AD792B1BED68B7914EB@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Glen Zorn <glenzorn@gmail.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA024844@AZ-FFEXMB04.global.avaya.com><6DC0D5A8-E781-4584-BA7A-38EC6F9134AA@csperkins.org><F97E5A20FEA344ABAA0997D0421AD03A@china.huawei.com> <50C996AB.7070006@gmail.com>
Date: Thu, 13 Dec 2012 17:45:38 +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
Cc: Colin Perkins <csp@csperkins.org>, xrblock@ietf.org
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.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, 13 Dec 2012 09:45:53 -0000

>> Also, one question: there are many reserved values for the jb cfg. Do we need to define how new values are to be registered in an IANA Registry,
>> or is the assumption that this draft is revised if new values are needed?

>> [Qin]:I am a little doubt about this. Do you have other values in mind besides the values for fixed jitter buffer method and adaptive jitter buffer method?
>> Also these values looks to me are just configuration parameters. They usually fixed upon they are set.
> 
> If the meaning of values not defined in this draft is unknown what use 
> are they?

[Qin]: I think the problem is we don't know how many new values we need to add. The current two values we defined in the draft  
are used to distinct measurement results that are using different jitter buffer method.
If we don't have any new value to be defined, we don't need to resort to IANA Registry,
if we do have many new values that need to be defined, I think IANA Registry is the right approach.

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