Monitoring Architecture for RTP
draft-ietf-avtcore-monarch-13

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2012-05-15 (latest revision 2012-05-01)
Replaces draft-hunt-avtcore-monarch
Stream IETF
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Revised I-D Needed - Issue raised by WGLC
Document shepherd Magnus Westerlund
Shepherd write-up Show (last changed 2012-05-03)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
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: November 3, 2012                                   Unaffiliated
                                                                P. Arden
                                                                      BT
                                                             May 2, 2012

                    Monitoring Architecture for RTP
                   draft-ietf-avtcore-monarch-13.txt

Abstract

   This memo proposes an architecture for extending RTP Control Protocol
   (RTCP) with a new RTCP Extended Reports (XR) (RFC3611) block type to
   report new metrics regarding media transmission or reception quality,
   following RTCP guideline established in RFC5968.  This memo suggests
   that a new 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 November 3, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Wu, et al.              Expires November 3, 2012                [Page 1]
Internet-Draft         RTP Monitoring Architecture              May 2012

   document authors.  All rights reserved.

   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 November 3, 2012                [Page 2]
Internet-Draft         RTP Monitoring Architecture              May 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  RTP monitoring architecture  . . . . . . . . . . . . . . . . .  7
     3.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  7
     3.2.  RTCP Metric Block Report and associated parameters . . . . 10
     3.3.  RTP Sender/Receiver entities located in network nodes  . . 11
   4.  Issues with reporting metric block using RTCP XR extension . . 12
   5.  Guideline for reporting metric block using RTCP XR . . . . . . 14
     5.1.  Using single metrics blocks  . . . . . . . . . . . . . . . 14
     5.2.  Correlating RTCP XR with RTP data  . . . . . . . . . . . . 14
     5.3.  Correlating RTCP XR with the non-RTP data  . . . . . . . . 15
     5.4.  Reducing Measurement information repetition  . . . . . . . 15
     5.5.  Expanding the RTCP XR block namespace  . . . . . . . . . . 16
   6.  An example of a metric block . . . . . . . . . . . . . . . . . 17
   7.  Application to RFC 5117 topologies . . . . . . . . . . . . . . 18
     7.1.  Applicability to MCU . . . . . . . . . . . . . . . . . . . 18
     7.2.  Applicability to Translators . . . . . . . . . . . . . . . 19
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 20
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 21
   10. Acknowledgement  . . . . . . . . . . . . . . . . . . . . . . . 22
   11. Informative References . . . . . . . . . . . . . . . . . . . . 23
   Appendix A.  Change Log  . . . . . . . . . . . . . . . . . . . . . 25
     A.1.  draft-ietf-avtcore-monarch-13  . . . . . . . . . . . . . . 25
     A.2.  draft-ietf-avtcore-monarch-12  . . . . . . . . . . . . . . 25
Show full document text