Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-13.txt
Qin Wu <bill.wu@huawei.com> Mon, 13 January 2014 06:24 UTC
Return-Path: <bill.wu@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 C34441ADF10 for <xrblock@ietfa.amsl.com>; Sun, 12 Jan 2014 22:24:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level:
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 nzB9QMp-Try6 for <xrblock@ietfa.amsl.com>; Sun, 12 Jan 2014 22:24:34 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA431AE03F for <xrblock@ietf.org>; Sun, 12 Jan 2014 22:24:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCK79843; Mon, 13 Jan 2014 06:24:21 +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.3.158.1; Mon, 13 Jan 2014 06:22:57 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 06:23:33 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 14:23:30 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-13.txt
Thread-Index: AQHPDXsZQLtdzm937kqTtDM2MbNoKJqCM7iw
Date: Mon, 13 Jan 2014 06:23:30 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C72374@nkgeml501-mbs.china.huawei.com>
References: <20140109204057.18456.66170.idtracker@ietfa.amsl.com>
In-Reply-To: <20140109204057.18456.66170.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-13.txt
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: Mon, 13 Jan 2014 06:24:37 -0000
Hi, The proposed changes look good. Regarding overall cleanup, since we remove mostype attribute from SDP, mos type related text should go away as well. OLD TEXT: " Section 4.2 A mosref attribute and mos type attribute MAY be included in an calgextmap; without it, the mosref and most type attribute implicitly inherits, of course, from the name attribute (e.g., P.1201.1 [P.1201.1] indicates lower resolution used while P.1201.2 [P.1201.2] indicates higher resolution used) or payload type carried in the segment extension (e.g.,EVRC-WB [RFC5188] indicates using Wideband Codec). However not all payload types or MOS algorithm names indicate resolution to be used and mos type to be used. " NEW TEXT: " Section 4.2 A mosref attribute MAY be included in an calgextmap; without it, the mosref attribute implicitly inherits, of course, from the name attribute (e.g., P.1201.1 [P.1201.1] indicates lower resolution used while P.1201.2 [P.1201.2] indicates higher resolution used) or payload type carried in the segment extension (e.g.,EVRC-WB [RFC5188] indicates using Wideband Codec). However not all payload types or MOS algorithm names indicate resolution to be used. " Regards! -Qin -----Original Message----- From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Friday, January 10, 2014 4:41 AM To: i-d-announce@ietf.org Cc: xrblock@ietf.org Subject: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-13.txt 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) Blocks for MOS Metric Reporting Authors : Alan Clark Qin Wu Roland Schott Glen Zorn Filename : draft-ietf-xrblock-rtcp-xr-qoe-13.txt Pages : 23 Date : 2014-01-09 Abstract: This document defines an RTP Control Protocol (RTCP) Extended Report (XR) Block including two new segment types and associated SDP parameters that allow the reporting of MOS Metrics for use in a range of RTP applications. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-qoe/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-qoe-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-xrblock-rtcp-xr-qoe-13 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