[xrblock] FW: [AVTCORE] RFC 6792 on Guidelines for Use of the RTP Monitoring Framework

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 25 November 2012 08:44 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0060521F84D9 for <xrblock@ietfa.amsl.com>; Sun, 25 Nov 2012 00:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.904
X-Spam-Status: No, score=-102.904 tagged_above=-999 required=5 tests=[AWL=-0.305, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id r5ZDUyMbGPlM for <xrblock@ietfa.amsl.com>; Sun, 25 Nov 2012 00:44:18 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4777621F84ED for <xrblock@ietf.org>; Sun, 25 Nov 2012 00:44:17 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="37487705"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Nov 2012 03:36:11 -0500
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Nov 2012 03:41:08 -0500
Received: from AZ-FFEXHC03.global.avaya.com ( by DC-US1HCEX4.global.avaya.com ( with Microsoft SMTP Server (TLS) id; Sun, 25 Nov 2012 03:44:03 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([]) with mapi id 14.02.0318.004; Sun, 25 Nov 2012 03:44:02 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [AVTCORE] RFC 6792 on Guidelines for Use of the RTP Monitoring Framework
Thread-Index: AQHNyaMFVNNcpjo1/0W9MEaVIfQbvJf6PrFQ
Date: Sun, 25 Nov 2012 08:44:02 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA01E680@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [xrblock] FW: [AVTCORE] RFC 6792 on Guidelines for Use of the RTP Monitoring Framework
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: Sun, 25 Nov 2012 08:44:19 -0000

-----Original Message-----
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
Sent: Friday, November 23, 2012 7:43 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: avt@ietf.org; rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 6792 on Guidelines for Use of the RTP Monitoring Framework

A new Request for Comments is now available in online RFC libraries.

        RFC 6792

        Title:      Guidelines for Use of the 
                    RTP Monitoring Framework 
        Author:     Q. Wu, Ed.,
                    G. Hunt, P. Arden
        Status:     Informational
        Stream:     IETF
        Date:       November 2012
        Mailbox:    sunseawq@huawei.com, 
        Pages:      17
        Characters: 42473
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avtcore-monarch-22.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6792.txt

This memo proposes an extensible Real-time Transport Protocol (RTP) monitoring framework for extending the RTP Control Protocol (RTCP) with a new RTCP Extended Reports (XR) block type to report new metrics regarding media transmission or reception quality.  In this framework, a new XR 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 that attempt to provide full coverage of all those parameters of concern to a specific application.  Applications may then "mix and match" to create a set of blocks that cover their set of concerns.  Where possible, a specific block should be designed to be reusable across more than one application, for example, for all of voice, streaming audio, and video.  This document is not an Internet Standards Track specification; it is published for informational purposes.

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

Audio/Video Transport Core Maintenance