Re: [xrblock] I-D Action: draft-ietf-xrblock-rtcp-xr-qoe-13.txt
Alan Clark <alan.d.clark@telchemy.com> Mon, 13 January 2014 15:11 UTC
Return-Path: <alan.d.clark@telchemy.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 3451A1AE196 for <xrblock@ietfa.amsl.com>; Mon, 13 Jan 2014 07:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 l9ajBTPKJUlh for <xrblock@ietfa.amsl.com>; Mon, 13 Jan 2014 07:11:40 -0800 (PST)
Received: from omx.cbeyond.com (omx.cbeyond.com [50.20.30.10]) by ietfa.amsl.com (Postfix) with ESMTP id 432931AE188 for <xrblock@ietf.org>; Mon, 13 Jan 2014 07:11:40 -0800 (PST)
X-SBRS: None
X-HAT: Sender Group ONNET_RELAY, Policy $ACCEPTED applied.
X-Hostname: omx03bay.sys.cbeyond.net
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al8FANMB1FJFD9PB/2dsb2JhbABagws4UIIytnJPgRMWdIIlAQEBBAEBATUvBwoBDAQLDQEDBAEBAQkWCAcJAwIBAgEVHwkIBgEMAQUCAQEFh3sFAwXFAhePBwcGhDEEiUOQBIU8iymDSx4
X-IronPort-AV: E=Sophos;i="4.95,653,1384318800"; d="scan'208";a="83677672"
Received: from unknown (HELO alans-mbp.telchemy.com) ([69.15.211.193]) by omx.cbeyond.com with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 13 Jan 2014 10:11:24 -0500
Message-ID: <52D4021C.6050007@telchemy.com>
Date: Mon, 13 Jan 2014 10:11:24 -0500
From: Alan Clark <alan.d.clark@telchemy.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>, "xrblock@ietf.org" <xrblock@ietf.org>
References: <20140109204057.18456.66170.idtracker@ietfa.amsl.com> <B8F9A780D330094D99AF023C5877DABA43C72374@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43C72374@nkgeml501-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 15:11:43 -0000
Thanks for your comments Qin - I'll wait to see if there are any additional points before sending out the -14. Regards Alan On 1/13/14, 1:23 AM, Qin Wu wrote: > 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 > . >