draft-ietf-avtcore-monarch-21.txt   draft-ietf-avtcore-monarch-22.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: March 25, 2013 Unaffiliated Expires: March 29, 2013 Unaffiliated
P. Arden P. Arden
BT BT
September 21, 2012 September 25, 2012
Guidelines for Use of the RTP Monitoring Framework Guidelines for Use of the RTP Monitoring Framework
draft-ietf-avtcore-monarch-21.txt draft-ietf-avtcore-monarch-22.txt
Abstract Abstract
This memo proposes an extensible Real-Time Protocol (RTP) monitoring This memo proposes an extensible Real-Time Protocol (RTP) monitoring
framework for extending RTP Control Protocol (RTCP) with a new RTCP framework for extending RTP Control Protocol (RTCP) with a new RTCP
Extended Reports (XR) block type to report new metrics regarding Extended Reports (XR) block type to report new metrics regarding
media transmission or reception quality. In this framework, a new XR media transmission or reception quality. In this framework, a new XR
block should contain a single metric or a small number of metrics block should contain a single metric or a small number of metrics
relevant to a single parameter of interest or concern, rather than relevant to a single parameter of interest or concern, rather than
containing a number of metrics which attempt to provide full coverage containing a number of metrics which attempt to provide full coverage
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 March 25, 2013. This Internet-Draft will expire on March 29, 2013.
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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
metric blocks . . . . . . . . . . . . . . . . . . . . . . 13 metric blocks . . . . . . . . . . . . . . . . . . . . . . 13
6. An Example of a Metric Block . . . . . . . . . . . . . . . . . 15 6. An Example of a Metric Block . . . . . . . . . . . . . . . . . 15
7. Application To RFC 5117 Topologies . . . . . . . . . . . . . . 16 7. Application To RFC 5117 Topologies . . . . . . . . . . . . . . 16
7.1. Applicability to Translators . . . . . . . . . . . . . . . 16 7.1. Applicability to Translators . . . . . . . . . . . . . . . 16
7.2. Applicability to MCU . . . . . . . . . . . . . . . . . . . 17 7.2. Applicability to MCU . . . . . . . . . . . . . . . . . . . 17
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 20 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 20
11. Informative References . . . . . . . . . . . . . . . . . . . . 21 11. Informative References . . . . . . . . . . . . . . . . . . . . 21
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23
A.1. draft-ietf-avtcore-monarch-21 . . . . . . . . . . . . . . 23 A.1. draft-ietf-avtcore-monarch-22 . . . . . . . . . . . . . . 23
A.2. draft-ietf-avtcore-monarch-20 . . . . . . . . . . . . . . 23 A.2. draft-ietf-avtcore-monarch-20 . . . . . . . . . . . . . . 23
A.3. draft-ietf-avtcore-monarch-19 . . . . . . . . . . . . . . 23 A.3. draft-ietf-avtcore-monarch-19 . . . . . . . . . . . . . . 23
A.4. draft-ietf-avtcore-monarch-18 . . . . . . . . . . . . . . 23 A.4. draft-ietf-avtcore-monarch-18 . . . . . . . . . . . . . . 23
A.5. draft-ietf-avtcore-monarch-17 . . . . . . . . . . . . . . 23 A.5. draft-ietf-avtcore-monarch-17 . . . . . . . . . . . . . . 23
A.6. draft-ietf-avtcore-monarch-16 . . . . . . . . . . . . . . 24 A.6. draft-ietf-avtcore-monarch-16 . . . . . . . . . . . . . . 24
A.7. draft-ietf-avtcore-monarch-15 . . . . . . . . . . . . . . 24 A.7. draft-ietf-avtcore-monarch-15 . . . . . . . . . . . . . . 24
A.8. draft-ietf-avtcore-monarch-14 . . . . . . . . . . . . . . 24 A.8. draft-ietf-avtcore-monarch-14 . . . . . . . . . . . . . . 24
A.9. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 24 A.9. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 24
A.10. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 25 A.10. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 25
A.11. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 25 A.11. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 25
skipping to change at page 4, line 26 skipping to change at page 4, line 26
measure and monitor Quality of Experience (QoE) [RFC6390]. measure and monitor Quality of Experience (QoE) [RFC6390].
However the proliferation of RTP/RTCP specific metrics for transport However the proliferation of RTP/RTCP specific metrics for transport
and application quality monitoring has been identified as a potential and application quality monitoring has been identified as a potential
problem for interoperability when using RTP/RTCP to communicate all problem for interoperability when using RTP/RTCP to communicate all
the parameters of concern to a specific application. Given that the parameters of concern to a specific application. Given that
different applications layered on RTP may have some monitoring different applications layered on RTP may have some monitoring
requirements in common, these metrics should be satisfied by a common requirements in common, these metrics should be satisfied by a common
design. design.
In the Performance Metrics Framework [RFC6390], guidelines for The objective of this document is to describe an extensible RTP
Considering New Performance Metric Development are provided. The
objective of this document is to describe an extensible RTP
monitoring framework to provide a small number of re-usable Quality monitoring framework to provide a small number of re-usable Quality
of Service (QoS) / QoE metrics which facilitate reduced of Service (QoS) / QoE metrics which facilitate reduced
implementation costs and help maximize inter-operability. The implementation costs and help maximize inter-operability. The
"Guidelines for Extending the RTP Control Protocol (RTCP)" [RFC5968] "Guidelines for Extending the RTP Control Protocol (RTCP)" [RFC5968]
has stated that, where RTCP is to be extended with a new metric, the has stated that, where RTCP is to be extended with a new metric, the
preferred mechanism is by the addition of a new RTCP XR [RFC3611] preferred mechanism is by the addition of a new RTCP XR [RFC3611]
block. This memo assumes that all the guidelines from RFC 5968 must block. This memo assumes that all the guidelines from RFC 5968 must
apply on top of the guidelines in this document. In the Performance apply on top of the guidelines in this document. Guidelines for
Metrics Framework [RFC6390], guidelines for Considering New developing new performance metrics are specified in [RFC6390]. New
Performance Metric Development are provided. When new performance RTCP XR report block definitions should not define new performance
metrics are specified, they must follow the RFC 6390 rules: metrics, but should rather refer to metrics defined elsewhere.
specifically, the performance metric definition template (see section
5.4.4, RFC 6390) must be used.
2. Terminology 2. Terminology
This memo is informative and as such contains no normative This memo is informative and as such contains no normative
requirements. requirements.
In addition, the following terms are defined: In addition, the following terms are defined:
Transport level metrics Transport level metrics
skipping to change at page 23, line 10 skipping to change at page 23, line 10
Performance Metric Development", RFC 6390, October 2011. Performance Metric Development", RFC 6390, October 2011.
[Y1540] ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and [Y1540] ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and
availability performance parameters", November 2007. availability performance parameters", November 2007.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-avtcore-monarch-21 A.1. draft-ietf-avtcore-monarch-22
The following are the major changes compared to 20: The following are the major changes compared to 20,21:
o Editorial changes based on Benoit's Review. o Editorial changes based on Benoit and WG Review.
A.2. draft-ietf-avtcore-monarch-20 A.2. draft-ietf-avtcore-monarch-20
The following are the major changes compared to 19: The following are the major changes compared to 19:
o Editorial changes based on IESG Review. o Editorial changes based on IESG Review.
o Some new text in the security section to clarify encryption issue o Some new text in the security section to clarify encryption issue
for third party monitoring. for third party monitoring.
 End of changes. 10 change blocks. 
17 lines changed or deleted 13 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/