draft-ietf-avtcore-monarch-16.txt   draft-ietf-avtcore-monarch-17.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: December 22, 2012 Unaffiliated Expires: December 30, 2012 Unaffiliated
P. Arden P. Arden
BT BT
June 20, 2012 June 28, 2012
Guidelines for Use of the RTP Monitoring Framework Guidelines for Use of the RTP Monitoring Framework
draft-ietf-avtcore-monarch-16.txt draft-ietf-avtcore-monarch-17.txt
Abstract Abstract
This memo proposes an extensible RTP monitoring framework for This memo proposes an extensible RTP monitoring framework for
extending RTP Control Protocol (RTCP) with a new RTCP Extended extending RTP Control Protocol (RTCP) with a new RTCP Extended
Reports (XR) (RFC3611) block type to report new metrics regarding Reports (XR) block type to report new metrics regarding media
media transmission or reception quality, following RTCP guidelines transmission or reception quality. In this framework, a new XR block
established in RFC5968. This memo suggests that a new block should should contain a single metric or a small number of metrics relevant
contain a single metric or a small number of metrics relevant to a to a single parameter of interest or concern, rather than containing
single parameter of interest or concern, rather than containing a a number of metrics which attempt to provide full coverage of all
number of metrics which attempt to provide full coverage of all those those parameters of concern to a specific application. Applications
parameters of concern to a specific application. Applications may may then "mix and match" to create a set of blocks which covers their
then "mix and match" to create a set of blocks which covers their set set of concerns. Where possible, a specific block should be designed
of concerns. Where possible, a specific block should be designed to to be re-usable across more than one application, for example, for
be re-usable across more than one application, for example, for all all of voice, streaming audio and video.
of voice, streaming audio and video.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 December 22, 2012. This Internet-Draft will expire on December 30, 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
skipping to change at page 3, line 32 skipping to change at page 3, line 32
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-16 . . . . . . . . . . . . . . 23 A.1. draft-ietf-avtcore-monarch-17 . . . . . . . . . . . . . . 23
A.2. draft-ietf-avtcore-monarch-15 . . . . . . . . . . . . . . 23 A.2. draft-ietf-avtcore-monarch-16 . . . . . . . . . . . . . . 23
A.3. draft-ietf-avtcore-monarch-14 . . . . . . . . . . . . . . 23 A.3. draft-ietf-avtcore-monarch-15 . . . . . . . . . . . . . . 23
A.4. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 24 A.4. draft-ietf-avtcore-monarch-14 . . . . . . . . . . . . . . 23
A.5. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 24 A.5. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 24
A.6. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 24 A.6. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 24
A.7. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 24 A.7. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 24
A.8. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 24 A.8. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 24
A.9. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 25 A.9. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 24
A.10. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 25 A.10. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 25
A.11. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 25 A.11. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 25
A.12. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 25 A.12. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 25
A.13. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 25 A.13. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 25
A.14. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 26 A.14. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 26
A.15. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 26 A.15. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 26
A.16. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 26 A.16. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 26
A.17. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 27 A.17. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 27
A.18. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
Multimedia services using the Real-Time Protocol (RTP) are seeing Multimedia services using the Real-Time Protocol (RTP) are seeing
increased use. Standard methods for gathering RTP performance increased use. Standard methods for gathering RTP performance
metrics from these applications are needed to manage uncertainties in metrics from these applications are needed to manage uncertainties in
the behavior and availability of their services. Standards , such as the behavior and availability of their services. Standards , such as
RTP Control Protocol Extended Reports (RTCP XR)[RFC3611] and other RTP Control Protocol Extended Reports (RTCP XR)[RFC3611] and other
RTCP extension to Sender Reports (SR), Receiver Reports (RR) RTCP extension to Sender Reports (SR), Receiver Reports (RR)
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.
The objective of this document is to define an extensible RTP 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 implementation of Service (QoS) / QoE metrics which facilitate reduced
costs and help maximize inter-operability. The "Guidelines for implementation costs and help maximize inter-operability. The
Extending the RTP Control Protocol (RTCP)" [RFC5968] has stated that, "Guidelines for Extending the RTP Control Protocol (RTCP)" [RFC5968]
where RTCP is to be extended with a new metric, the preferred has stated that, where RTCP is to be extended with a new metric, the
mechanism is by the addition of a new RTCP XR [RFC3611] block. This preferred mechanism is by the addition of a new RTCP XR [RFC3611]
memo assumes that any requirement for a new metric to be transported block. This memo assumes that any requirement for a new metric to be
in RTCP will use a new RTCP XR block. transported in RTCP will use a new RTCP XR block.
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 13, line 41 skipping to change at page 13, line 41
with the SSRC of the measured RTP stream which is included in the XR with the SSRC of the measured RTP stream which is included in the XR
Block header and 5-tuple to the network management system. Network Block header and 5-tuple to the network management system. Network
management system can then correlate this report using SSRC with management system can then correlate this report using SSRC with
other diagnostic information such as call detail records. other diagnostic information such as call detail records.
5.4. Reduce Measurement information repetition across metric blocks 5.4. Reduce Measurement information repetition across metric blocks
When multiple metric blocks are carried in one RTCP XR packet, When multiple metric blocks are carried in one RTCP XR packet,
reporting on the same stream from the same source for the same time reporting on the same stream from the same source for the same time
period, RTCP should use the SSRC to identify and correlate the period, RTCP should use the SSRC to identify and correlate the
multiple metric blocks between metric blocks. This memo proposes to multiple metric blocks between metric blocks. Measurement Identity
define a new XR Block (i.e., the Measurement information block and information Reporting using SDES item and XR Block"
[MEASI]) that will be used to convey the common time period and the [MEASI]enables an RTCP sender to convey the common time period and
number of packets sent during this period. If the measurement the number of packets sent during this period. If the measurement
interval for a metric is different from the RTCP reporting interval, interval for a metric is different from the RTCP reporting interval,
then this measurement duration in the Measurement information block then this measurement duration in the Measurement information block
should be used to specify the interval. When there may be multiple should be used to specify the interval. When there may be multiple
measurements information blocks with the same SSRC in one RTCP XR measurements information blocks with the same SSRC in one RTCP XR
compound packet, the measurement information block should be put in compound packet, the measurement information block should be put in
order and followed by all the metric blocks associated with this order and followed by all the metric blocks associated with this
measurement information block. New RTCP XR metric blocks that rely measurement information block. New RTCP XR metric blocks that rely
on the Measurement information block [MEASI] must specify the on the Measurement information block [MEASI] must specify the
response in case the new RTCP XR metric block is received without an response in case the new RTCP XR metric block is received without an
associated measurement information block. In most cases, it is associated measurement information block. In most cases, it is
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-16 A.1. draft-ietf-avtcore-monarch-17
The following are the major changes compared to 16:
o Some Editorial changes.
A.2. draft-ietf-avtcore-monarch-16
The following are the major changes compared to 15: The following are the major changes compared to 15:
o A few modification to the figure 1. o A few modification to the figure 1.
o Change RTCP XR reports into RTCP reports in the section 3.1. o Change RTCP XR reports into RTCP reports in the section 3.1.
o References Update. o References Update.
A.2. draft-ietf-avtcore-monarch-15 A.3. draft-ietf-avtcore-monarch-15
The following are the major changes compared to 14: The following are the major changes compared to 14:
o Add figure 1 in section 3 to describe RTP monitoring framework. o Add figure 1 in section 3 to describe RTP monitoring framework.
o Change the title as Guidelines for Use of the RTP Monitoring o Change the title as Guidelines for Use of the RTP Monitoring
Framework. Framework.
o Other editorial change to get in line with the title change in the o Other editorial change to get in line with the title change in the
section 3. section 3.
A.3. draft-ietf-avtcore-monarch-14 A.4. draft-ietf-avtcore-monarch-14
The following are the major changes compared to 13: The following are the major changes compared to 13:
o Incorporate the key points in the section 3.2 into overview o Incorporate the key points in the section 3.2 into overview
section. section.
o Remove the figure 1 and use the description instead. o Remove the figure 1 and use the description instead.
o Add description in the section 3.3 to discuss the possible o Add description in the section 3.3 to discuss the possible
location of the monitors and the types of metric at that location. location of the monitors and the types of metric at that location.
o Add the description to make the definition of Interval metrics/ o Add the description to make the definition of Interval metrics/
cumulative metrics/sampled metrics clear. cumulative metrics/sampled metrics clear.
o Editorial Changes. o Editorial Changes.
A.4. draft-ietf-avtcore-monarch-13 A.5. draft-ietf-avtcore-monarch-13
The following are the major changes compared to 12: The following are the major changes compared to 12:
o Editorial Changes. o Editorial Changes.
A.5. draft-ietf-avtcore-monarch-12 A.6. draft-ietf-avtcore-monarch-12
The following are the major changes compared to 11: The following are the major changes compared to 11:
o Editorial Changes based on Charles' Comments. o Editorial Changes based on Charles' Comments.
o Reference update. o Reference update.
o Add one new section 5.2 to discuss Correlating RTCP XR with RTP o Add one new section 5.2 to discuss Correlating RTCP XR with RTP
data. data.
o Add text in section 5.1 to highlight it is more appropriate to o Add text in section 5.1 to highlight it is more appropriate to
define each block in a separate draft. define each block in a separate draft.
A.6. draft-ietf-avtcore-monarch-11 A.7. draft-ietf-avtcore-monarch-11
The following are the major changes compared to 10: The following are the major changes compared to 10:
o Editorial Changes. o Editorial Changes.
A.7. draft-ietf-avtcore-monarch-10 A.8. draft-ietf-avtcore-monarch-10
The following are the major changes compared to 09: The following are the major changes compared to 09:
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.8. draft-ietf-avtcore-monarch-09 A.9. draft-ietf-avtcore-monarch-09
The following are the major changes compared to 07: The following are the major changes compared to 07:
o Rephrase application level metric definition. o Rephrase application level metric definition.
o Add one new section to clarify where to measure QoE related o Add one new section to clarify where to measure QoE related
parameters. parameters.
o Add text in section 5.3 to clarify the failure case when o Add text in section 5.3 to clarify the failure case when
measurement interval is not sent. measurement interval is not sent.
o Add text in section 5.3 to clarify how to deal with multiple o Add text in section 5.3 to clarify how to deal with multiple
measurements information blocks carried in the same packet. measurements information blocks carried in the same packet.
A.9. draft-ietf-avtcore-monarch-08 A.10. draft-ietf-avtcore-monarch-08
The following are the major changes compared to 07: The following are the major changes compared to 07:
o Editorial change to the reference. o Editorial change to the reference.
A.10. draft-ietf-avtcore-monarch-07 A.11. draft-ietf-avtcore-monarch-07
The following are the major changes compared to 06: The following are the major changes compared to 06:
o Clarify the XR block code points consumption issue in the section o Clarify the XR block code points consumption issue in the section
4 and new section 5.4. 4 and new section 5.4.
o Other editorial changes. o Other editorial changes.
A.11. draft-ietf-avtcore-monarch-06 A.12. draft-ietf-avtcore-monarch-06
The following are the major changes compared to 05: The following are the major changes compared to 05:
o Some editorial changes. o Some editorial changes.
A.12. draft-ietf-avtcore-monarch-05 A.13. draft-ietf-avtcore-monarch-05
The following are the major changes compared to 04: The following are the major changes compared to 04:
o Replace "chunk" with "new SDES item". o Replace "chunk" with "new SDES item".
o Add texts in security section to discussion potential security o Add texts in security section to discussion potential security
issues. issues.
o Add new sub-section 5.3 to discuss Reducing Measurement o Add new sub-section 5.3 to discuss Reducing Measurement
information repetition. information repetition.
o Other editorial changes. o Other editorial changes.
A.13. draft-ietf-avtcore-monarch-04 A.14. draft-ietf-avtcore-monarch-04
The following are the major changes compared to 03: The following are the major changes compared to 03:
o Update section 5.2 to clarify using SDES packet to carry o Update section 5.2 to clarify using SDES packet to carry
correlation information. correlation information.
o Remove section 5.3 since additional identity information goes to o Remove section 5.3 since additional identity information goes to
SDES packet and using SSRC to identify each block is standard RTP SDES packet and using SSRC to identify each block is standard RTP
feature. feature.
o Swap the last two paragraphs in the section 4 since identity o Swap the last two paragraphs in the section 4 since identity
information duplication can not been 100% avoided. information duplication can not been 100% avoided.
o Other editorial changes. o Other editorial changes.
A.14. draft-ietf-avtcore-monarch-03 A.15. draft-ietf-avtcore-monarch-03
The following are the major changes compared to 02: The following are the major changes compared to 02:
o Update bullet 2 in section 4 to explain the ill-effect of Identity o Update bullet 2 in section 4 to explain the ill-effect of Identity
Information duplication. Information duplication.
o Update bullet 3 in section 4 to explain why Correlating RTCP XR o Update bullet 3 in section 4 to explain why Correlating RTCP XR
with the non-RTP data is needed. with the non-RTP data is needed.
o Update section 5.2 to focus on how to reduce the identity o Update section 5.2 to focus on how to reduce the identity
information repetition information repetition
o Update section 5.3 to explain how to correlate identity o Update section 5.3 to explain how to correlate identity
information with the non-RTP data information with the non-RTP data
A.15. draft-ietf-avtcore-monarch-02 A.16. draft-ietf-avtcore-monarch-02
The following are the major changes compared to 01: The following are the major changes compared to 01:
o Deleting first paragraph of Section 1. o Deleting first paragraph of Section 1.
o Deleting Section 3.1, since the interaction with the management o Deleting Section 3.1, since the interaction with the management
application is out of scope of this draft. application is out of scope of this draft.
o Separate identity information correlation from section 5.2 as new o Separate identity information correlation from section 5.2 as new
section 5.3. section 5.3.
o Remove figure 2 and related text from section 5.2. o Remove figure 2 and related text from section 5.2.
o Editorial changes in the section 4 and the first paragraph of o Editorial changes in the section 4 and the first paragraph of
section 7. section 7.
A.16. draft-ietf-avtcore-monarch-01 A.17. draft-ietf-avtcore-monarch-01
The following are the major changes compared to 00: The following are the major changes compared to 00:
o Restructure the document by merging section 4 into section 3. o Restructure the document by merging section 4 into section 3.
o Remove section 4.1,section 5 that is out of scope of this o Remove section 4.1,section 5 that is out of scope of this
document. document.
o Remove the last bullet in section 6 and section 7.3 based on o Remove the last bullet in section 6 and section 7.3 based on
conclusion of last meeting. conclusion of last meeting.
skipping to change at page 27, line 21 skipping to change at page 27, line 27
o Update figure 1 and related text in section 3 according to the o Update figure 1 and related text in section 3 according to the
monitor definition in RFC3550. monitor definition in RFC3550.
o Revise section 9 to address monitor declaration issue. o Revise section 9 to address monitor declaration issue.
o Merge the first two bullet in section 6. o Merge the first two bullet in section 6.
o Add one new bullet to discuss metric block association in section o Add one new bullet to discuss metric block association in section
6. 6.
A.17. draft-ietf-avtcore-monarch-00 A.18. draft-ietf-avtcore-monarch-00
The following are the major changes compared to The following are the major changes compared to
draft-hunt-avtcore-monarch-02: draft-hunt-avtcore-monarch-02:
o Move Geoff Hunt and Philip Arden to acknowledgement section. o Move Geoff Hunt and Philip Arden to acknowledgement section.
Authors' Addresses Authors' Addresses
Qin Wu (editor) Qin Wu (editor)
Huawei Huawei
 End of changes. 26 change blocks. 
61 lines changed or deleted 67 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/