Re: [xrblock] Protocol Action: 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric Reporting' to Proposed Standard (draft-ietf-xrblock-rtcp-xr-qoe-17.txt)
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 27 February 2014 12:16 UTC
Return-Path: <dromasca@avaya.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 307791A0267 for <xrblock@ietfa.amsl.com>; Thu, 27 Feb 2014 04:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level:
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] 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 E5xgEpKQucvN for <xrblock@ietfa.amsl.com>; Thu, 27 Feb 2014 04:16:18 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 572651A025F for <xrblock@ietf.org>; Thu, 27 Feb 2014 04:16:18 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFACIsD1OHCzIm/2dsb2JhbABagmUhO1fAOE+BGhZ0giUBAQEBAwEBAQ8oMQMXBAIBCA0EBAEBCxQFBAcnCxQJCAIEEwgah1cBDJ50q1cXjiM4BoMdgRQEmWqFQIs3gW+BPoIq
X-IronPort-AV: E=Sophos;i="4.97,554,1389762000"; d="scan'208";a="51177927"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 27 Feb 2014 07:16:16 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 27 Feb 2014 07:03:03 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Thu, 27 Feb 2014 07:16:15 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] Protocol Action: 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric Reporting' to Proposed Standard (draft-ietf-xrblock-rtcp-xr-qoe-17.txt)
Thread-Index: AQHPM7VBejOADaR3hUSoLd2tqoti6ZrJA6hw
Date: Thu, 27 Feb 2014 12:16:14 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E43B9E5@AZ-FFEXMB04.global.avaya.com>
References: <20140227121246.8883.30861.idtracker@ietfa.amsl.com>
In-Reply-To: <20140227121246.8883.30861.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/uxo_W2qHhhIVKx7vabLZCpgwrvk
Subject: Re: [xrblock] Protocol Action: 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric Reporting' to Proposed Standard (draft-ietf-xrblock-rtcp-xr-qoe-17.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: Thu, 27 Feb 2014 12:16:20 -0000
Special thanks to the authors and congratulations to the whole WG for the approval of this document. Regards, Dan > -----Original Message----- > From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of The IESG > Sent: Thursday, February 27, 2014 2:13 PM > To: IETF-Announce > Cc: xrblock chair; xrblock mailing list; RFC Editor > Subject: [xrblock] Protocol Action: 'RTP Control Protocol (RTCP) Extended > Report (XR) Blocks for MOS Metric Reporting' to Proposed Standard (draft- > ietf-xrblock-rtcp-xr-qoe-17.txt) > > The IESG has approved the following document: > - 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric > Reporting' > (draft-ietf-xrblock-rtcp-xr-qoe-17.txt) as Proposed Standard > > This document is the product of the Metric Blocks for use with RTCP's > Extended Report Framework Working Group. > > The IESG contact persons are Gonzalo Camarillo and Richard Barnes. > > A URL of this Internet Draft is: > http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-qoe/ > > > > > Technical Summary > > 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. > > Working Group Summary > > The WG reviewed carefully the document several times and there is good > support behind it. > > Document Quality > > Two vendors indicated that they have similar functionality in their code and > intentions to implement the standard block when approved. > There was one important change to notice which resulted from the SDP > Expert Review which led to the change of the title of the document from QoE > to MOS Metric reporting, which defines better the scope of the document. > > Personnel > > Dan Romascanu is the Document Shepherd. Gonzalo Camarillo is the > Responsible Area Director. > > _______________________________________________ > xrblock mailing list > xrblock@ietf.org > https://www.ietf.org/mailman/listinfo/xrblock
- [xrblock] Protocol Action: 'RTP Control Protocol … The IESG
- Re: [xrblock] Protocol Action: 'RTP Control Proto… Romascanu, Dan (Dan)