[AVTCORE] 答复: I-D Action: draft-ietf-avtcore-monarch-06.txt

Qin Wu <bill.wu@huawei.com> Tue, 15 November 2011 06:23 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DB011E821F for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.53
X-Spam-Level:
X-Spam-Status: No, score=-0.53 tagged_above=-999 required=5 tests=[AWL=-2.979, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ywyGDLuKL-Z4 for <avt@ietfa.amsl.com>; Mon, 14 Nov 2011 22:23:20 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id F143F11E8291 for <avt@ietf.org>; Mon, 14 Nov 2011 22:23:19 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO0006PV2V2Y@szxga03-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:23:19 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO00DKMV2JL3@szxga03-in.huawei.com> for avt@ietf.org; Tue, 15 Nov 2011 14:23:19 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEZ58171; Tue, 15 Nov 2011 14:23:18 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 Nov 2011 14:23:15 +0800
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.67]) by szxeml401-hub.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0323.003; Tue, 15 Nov 2011 14:23:09 +0800
Date: Tue, 15 Nov 2011 06:23:09 +0000
From: Qin Wu <bill.wu@huawei.com>
In-reply-to: <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org>
X-Originating-IP: [172.24.2.41]
To: Colin Perkins <csp@csperkins.org>
Message-id: <B8F9A780D330094D99AF023C5877DABA334193@szxeml523-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="gb2312"
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt
Thread-index: AQHMomQlgYg5GwZpqEWyT0P+dDCZN5WrnRG+gAFKOACAAJDvbw==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <20111114002647.19680.14547.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA3338A2@szxeml523-mbs.china.huawei.com> <7D0E5A6C-5F70-42BF-B3AB-B405FC37A62E@csperkins.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: [AVTCORE] 答复: I-D Action: draft-ietf-avtcore-monarch-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2011 06:23:20 -0000

Thanks Colin for your review and quick comments.
As for IANA section, the proposed change is based on Magnus's suggestion.
I am okay to change back if nobody is against having no IANA action.

For section 5.3, the answer is yes. Thank for your suggestion.

Regards!
-Qin
________________________________________
发件人: Colin Perkins [csp@csperkins.org]
发送时间: 2011年11月15日 13:40
到: Qin Wu
Cc: avt@ietf.org
主题: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-06.txt

I have two quick comments on this version.

This new IANA Considerations text says:

   At the time of writing, the consumption of XR block code points isn't
   a major issue.  However when XR block codes points is really close to
   run out of space, it might be desirable to define new fields encoded
   as TLV elements in the XR report block or define one XR block type
   for vendor-specific extensions, with an enterprise number included to
   identify the vendor making the extension.

This is not actionable by IANA, so I think it should be changed back to the previous wording of "There is no IANA action in this document".

Section 5.3 "proposes to define a new XR block". This would probably be better phrased as "draft-… defines a new XR block", since the definition has already happened.

Colin


On 14 Nov 2011, at 10:05, Qin Wu wrote:
> Hi, Folks:
> We have just submitted a new version of monarch document.
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>
> We talk with chairs and think it has been ready for WGLC.
> Chairs, would you like to use this version as baseline to raise WGLC?
>
>
> Regards!
> -Qin
> _______________________________________
> 发件人: i-d-announce-bounces@ietf.org [i-d-announce-bounces@ietf.org] 代表 internet-drafts@ietf.org [internet-drafts@ietf.org]
> 发送时间: 2011年11月14日 8:26
> 到: i-d-announce@ietf.org
> Cc: avt@ietf.org
> 主题: I-D Action: draft-ietf-avtcore-monarch-06.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.
>
>        Title           : Monitoring Architectures for RTP
>        Author(s)       : Qin Wu
>                          Geoff Hunt
>                          Philip Arden
>        Filename        : draft-ietf-avtcore-monarch-06.txt
>        Pages           : 25
>        Date            : 2011-11-13
>
>   This memo proposes an architecture for extending RTCP with a new RTCP
>   XR (RFC3611) block type to report new metrics regarding media
>   transmission or reception quality, following RTCP guideline
>   established in RFC5968.  This memo suggests that a new block should
>   contain a single metric or a small number of metrics relevant to a
>   single parameter of interest or concern, rather than containing a
>   number of metrics which attempt to provide full coverage of all those
>   parameters of concern to a specific application.  Applications may
>   then &quot;mix and match&quot; to create a set of blocks which covers their set
>   of concerns.  Where possible, a specific block should be designed to
>   be re-usable across more than one application, for example, for all
>   of voice, streaming audio and video.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-06.txt
> _______________________________________________
> 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
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt