Last Call: <draft-ietf-avtcore-monarch-17.txt> (Guidelines for Use of the RTP Monitoring Framework) to Informational RFC

The IESG <> Thu, 19 July 2012 20:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F034621F8772; Thu, 19 Jul 2012 13:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Zkxh8whL-vkD; Thu, 19 Jul 2012 13:00:00 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 40A1421F8655; Thu, 19 Jul 2012 13:00:00 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-avtcore-monarch-17.txt> (Guidelines for Use of the RTP Monitoring Framework) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <>
Date: Thu, 19 Jul 2012 13:00:00 -0700
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 Jul 2012 20:00:01 -0000

The IESG has received a request from the Audio/Video Transport Core
Maintenance WG (avtcore) to consider the following document:
- 'Guidelines for Use of the RTP Monitoring Framework'
  <draft-ietf-avtcore-monarch-17.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2012-08-02. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   This memo proposes an extensible RTP monitoring framework for
   extending 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 which 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 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.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.