draft-ietf-avtcore-monarch-10.txt   draft-ietf-avtcore-monarch-11.txt 
Audio/Video Transport Working Group Q. Wu, Ed. Audio/Video Transport Working Group Q. Wu, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Informational G. Hunt Intended status: Informational G. Hunt
Expires: August 27, 2012 Unaffiliated Expires: September 3, 2012 Unaffiliated
P. Arden P. Arden
BT BT
February 24, 2012 March 2, 2012
Monitoring Architecture for RTP Monitoring Architecture for RTP
draft-ietf-avtcore-monarch-10.txt draft-ietf-avtcore-monarch-11.txt
Abstract Abstract
This memo proposes an architecture for extending RTP Control Protocol This memo proposes an architecture for extending RTP Control Protocol
(RTCP) with a new RTCP Extended Reports (XR) (RFC3611) block type to (RTCP) with a new RTCP Extended Reports (XR) (RFC3611) block type to
report new metrics regarding media transmission or reception quality, report new metrics regarding media transmission or reception quality,
following RTCP guideline established in RFC5968. This memo suggests following RTCP guideline established in RFC5968. This memo suggests
that a new block should contain a single metric or a small number of 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 metrics relevant to a single parameter of interest or concern, rather
than containing a number of metrics which attempt to provide full than containing a number of metrics which attempt to provide full
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 27, 2012. This Internet-Draft will expire on September 3, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. RTP monitoring architecture . . . . . . . . . . . . . . . . . 6 3. RTP monitoring architecture . . . . . . . . . . . . . . . . . 7
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2. RTCP Metric Block Report and associated parameters . . . . 9 3.2. RTCP Metric Block Report and associated parameters . . . . 10
3.3. RTP Sender/Receiver entities located in network nodes . . 10 3.3. RTP Sender/Receiver entities located in network nodes . . 11
4. Issues with reporting metric block using RTCP XR extension . . 11 4. Issues with reporting metric block using RTCP XR extension . . 12
5. Guideline for reporting metric block using RTCP XR . . . . . . 13 5. Guideline for reporting metric block using RTCP XR . . . . . . 14
5.1. Using single metrics blocks . . . . . . . . . . . . . . . 13 5.1. Using single metrics blocks . . . . . . . . . . . . . . . 14
5.2. Correlating RTCP XR with the non-RTP data . . . . . . . . 13 5.2. Correlating RTCP XR with the non-RTP data . . . . . . . . 14
5.3. Reducing Measurement information repetition . . . . . . . 14 5.3. Reducing Measurement information repetition . . . . . . . 15
5.4. Expanding the RTCP XR block namespace . . . . . . . . . . 14 5.4. Expanding the RTCP XR block namespace . . . . . . . . . . 15
6. An example of a metric block . . . . . . . . . . . . . . . . . 16 6. An example of a metric block . . . . . . . . . . . . . . . . . 17
7. Application to RFC 5117 topologies . . . . . . . . . . . . . . 17 7. Application to RFC 5117 topologies . . . . . . . . . . . . . . 18
7.1. Applicability to MCU . . . . . . . . . . . . . . . . . . . 17 7.1. Applicability to MCU . . . . . . . . . . . . . . . . . . . 18
7.2. Applicability to Translators . . . . . . . . . . . . . . . 18 7.2. Applicability to Translators . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 9. Security Considerations . . . . . . . . . . . . . . . . . . . 21
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 21 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 22
11. Informative References . . . . . . . . . . . . . . . . . . . . 22 11. Informative References . . . . . . . . . . . . . . . . . . . . 23
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25
A.1. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 24 A.1. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 25
A.2. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 24 A.2. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 25
A.3. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 24 A.3. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 25
A.4. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 25 A.4. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 26
A.5. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 25 A.5. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 26
A.6. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 25 A.6. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 26
A.7. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 26 A.7. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 27
A.8. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 26 A.8. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 27
A.9. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 26 A.9. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 27
A.10. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 26 A.10. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 27
A.11. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 26 A.11. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28 A.12. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
As the delivery of multimedia services using the Real-Time Transport As the delivery of multimedia services using the Real-Time Transport
Protocol (RTP) over IP network is gaining an increasing popularity, Protocol (RTP) over IP network is gaining an increasing popularity,
uncertainties in the performance and availability of these services uncertainties in the performance and availability of these services
are driving the need to support new standard methods for gathering are driving the need to support new standard methods for gathering
performance metrics from RTP applications. These rapidly emerging performance metrics from RTP applications. These rapidly emerging
standards, such as RTP Control Protocol Extended Reports (RTCP standards, such as RTP Control Protocol Extended Reports (RTCP
XR)[RFC3611] and other RTCP extension to Sender Reports (SR), XR)[RFC3611] and other RTCP extension to Sender Reports (SR),
skipping to change at page 4, line 43 skipping to change at page 5, line 43
de-jitter buffering, packet loss concealment, and the use of de-jitter buffering, packet loss concealment, and the use of
redundant streams (if any) for correction of error or loss. redundant streams (if any) for correction of error or loss.
Direct metrics Direct metrics
Metrics that can be directly measured or calculated and are not Metrics that can be directly measured or calculated and are not
dependent on other metric. dependent on other metric.
Composed metrics Composed metrics
Metrics that are calculated based on Direct metric that have been Metrics that are not directly measured and derived from other
measured or combination of Direct metrics that are identical to metrics. One example of such metrics is the ones calculated based
the metric being composed. on Direct metric that have been measured.
Interval metrics Interval metrics
It is referred to as the metrics of which the reported values It is referred to as the metrics of which the reported values
apply to the most recent measurement interval duration between apply to the most recent measurement interval duration between
successive metrics reports. successive metrics reports.
Cumulative metrics Cumulative metrics
It is referred to as the metrics of which the reported values It is referred to as the metrics of which the reported values
apply to the accumulation period characteristic of cumulative apply to the accumulation period characteristic of cumulative
measurements. measurements.
Sampled metrics Sampled metrics
It is referred to as the metrics of which the reported values only It is referred to as the metrics of which the reported values only
apply to the value of a continuously measured or calculated that apply to the value of a continuously measured or calculated that
has been sampled at end of the interval. has been sampled at any given instance of the interval.
3. RTP monitoring architecture 3. RTP monitoring architecture
There are many ways in which the performance of an RTP session can be There are many ways in which the performance of an RTP session can be
monitored. These include RTP-based mechanisms such as the RTP SNMP monitored. These include RTP-based mechanisms such as the RTP SNMP
MIB [RFC2959], or the SIP event package for RTCP summary reports MIB [RFC2959], or the SIP event package for RTCP summary reports
[RFC6035], or non-RTP mechanisms such as generic MIBs, NetFlow, [RFC6035], or non-RTP mechanisms such as generic MIBs, NetFlow,
IPFix, and so on. Together, these provide useful mechanisms for IPFix, and so on. Together, these provide useful mechanisms for
exporting data on the performance of an RTP session to non-RTP exporting data on the performance of an RTP session to non-RTP
network management systems. It is desirable to also perform in- network management systems. It is desirable to also perform in-
skipping to change at page 10, line 11 skipping to change at page 11, line 11
o Round-trip time reports o Round-trip time reports
o Statistics Summary Reports o Statistics Summary Reports
There are also various other scenarios in which it is desirable to There are also various other scenarios in which it is desirable to
send RTCP Metric reports more frequently. For example, the Audio/ send RTCP Metric reports more frequently. For example, the Audio/
Video Profile with Feedback [RFC4585] extends the standard Audio/ Video Profile with Feedback [RFC4585] extends the standard Audio/
Video Profile [RFC3551] to allow RTCP reports to be sent early Video Profile [RFC3551] to allow RTCP reports to be sent early
provided RTCP bandwidth allocation is respected. The following are provided RTCP bandwidth allocation is respected. The following are
four use cases but are not limited to: four use cases but are not limited to:
o RTCP NACK is used to provide feedback on the RTP sequence number o RTCP NACK is used to provide feedback on the RTP sequence numbers
on a subset of the lost packets or the total lost packets for a subset of the lost packets or all the currently lost packets
[RFC4585]. [RFC4585].
o RTCP is extended to convey requests for full intra-coded frames or o RTCP is extended to convey requests for full intra-coded frames or
select the reference picture, and signal changes in the desired select the reference picture, and signal changes in the desired
temporal/spatial trade-off and maximum media bit rate [RFC5104]. temporal/spatial trade-off and maximum media bit rate [RFC5104].
o RTCP or RTCP XR is extended to provide feedback on Explicit o RTCP or RTCP XR is extended to provide feedback on Explicit
Congestion Notification (ECN) statistics information [ECN]. Congestion Notification (ECN) statistics information [ECN].
o RTCP XR is extended to provide feedback on multicast acquisition o RTCP XR is extended to provide feedback on multicast acquisition
skipping to change at page 28, line 5 skipping to change at page 28, line 7
o Discuss what exist already for monitoring in section 3.1. o Discuss what exist already for monitoring in section 3.1.
o Provide benefit using RTCP XR based monitoring in section 3.1. o Provide benefit using RTCP XR based monitoring in section 3.1.
o add one new paragraph in section 3.1 to describe how monitoring o add one new paragraph in section 3.1 to describe how monitoring
architecture is applied to ASM/SSM. architecture is applied to ASM/SSM.
o Other Editorial Changes. o Other Editorial Changes.
A.12. draft-ietf-avtcore-monarch-11
The following are the major changes compared to 10:
o Editorial Changes.
Authors' Addresses Authors' Addresses
Qin Wu (editor) Qin Wu (editor)
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com Email: sunseawq@huawei.com
 End of changes. 9 change blocks. 
43 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/