Guidelines for Use of the RTP Monitoring Framework
draft-ietf-avtcore-monarch-17

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2012-08-02 (latest revision 2012-06-27)
Replaces draft-hunt-avtcore-monarch
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Other - see Comment Log
Consensus Unknown
Document shepherd Magnus Westerlund
Shepherd write-up Show (last changed 2012-07-18)
IESG IESG state Waiting for AD Go-Ahead
Telechat date
Responsible AD Robert Sparks
IESG note Magnus Westerlund (magnus.westerlund@ericsson.com) is the Document Shepherd
Send notices to avtcore-chairs@tools.ietf.org, draft-ietf-avtcore-monarch@tools.ietf.org
Audio/Video Transport Working Group                           Q. Wu, Ed.
Internet-Draft                                                    Huawei
Intended status: Informational                                   G. Hunt
Expires: December 30, 2012                                  Unaffiliated
                                                                P. Arden
                                                                      BT
                                                           June 28, 2012

           Guidelines for Use of the RTP Monitoring Framework
                   draft-ietf-avtcore-monarch-17.txt

Abstract

   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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 30, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Wu, et al.              Expires December 30, 2012               [Page 1]
Internet-Draft          RTP Monitoring Framework               June 2012

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Wu, et al.              Expires December 30, 2012               [Page 2]
Internet-Draft          RTP Monitoring Framework               June 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  RTP Monitoring Framework . . . . . . . . . . . . . . . . . . .  7
     3.1.  Overview of the RTP Monitoring Framework . . . . . . . . .  7
     3.2.  Location of RTP Monitors . . . . . . . . . . . . . . . . .  9
   4.  Issues with reporting metric block using RTCP XR extension . . 10
     4.1.  Using compound metrics block . . . . . . . . . . . . . . . 10
     4.2.  Correlating RTCP XR with the non-RTP data  . . . . . . . . 10
     4.3.  Measurement Information duplication  . . . . . . . . . . . 10
     4.4.  Consumption of XR block code points  . . . . . . . . . . . 11
   5.  Guidelines for reporting metric block using RTCP XR  . . . . . 12
     5.1.  Contain the single metrics in the Metric Block . . . . . . 12
     5.2.  Include the payload type in the Metric Block . . . . . . . 12
     5.3.  Use RTCP SDES to correlate XR reports with non-RTP data  . 13
     5.4.  Reduce Measurement information repetition across
           metric blocks  . . . . . . . . . . . . . . . . . . . . . . 13
   6.  An example of a metric block . . . . . . . . . . . . . . . . . 15
   7.  Application to RFC 5117 topologies . . . . . . . . . . . . . . 16
     7.1.  Applicability to Translators . . . . . . . . . . . . . . . 16
     7.2.  Applicability to MCU . . . . . . . . . . . . . . . . . . . 17
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
Show full document text