draft-ietf-avtcore-monarch-12.txt   draft-ietf-avtcore-monarch-13.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: October 20, 2012 Unaffiliated Expires: November 3, 2012 Unaffiliated
P. Arden P. Arden
BT BT
April 18, 2012 May 2, 2012
Monitoring Architecture for RTP Monitoring Architecture for RTP
draft-ietf-avtcore-monarch-12.txt draft-ietf-avtcore-monarch-13.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 October 20, 2012. This Internet-Draft will expire on November 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
skipping to change at page 3, line 29 skipping to change at page 3, line 29
5.5. Expanding the RTCP XR block namespace . . . . . . . . . . 16 5.5. Expanding the RTCP XR block namespace . . . . . . . . . . 16
6. An example of a metric block . . . . . . . . . . . . . . . . . 17 6. An example of a metric block . . . . . . . . . . . . . . . . . 17
7. Application to RFC 5117 topologies . . . . . . . . . . . . . . 18 7. Application to RFC 5117 topologies . . . . . . . . . . . . . . 18
7.1. Applicability to MCU . . . . . . . . . . . . . . . . . . . 18 7.1. Applicability to MCU . . . . . . . . . . . . . . . . . . . 18
7.2. Applicability to Translators . . . . . . . . . . . . . . . 19 7.2. Applicability to Translators . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 21 9. Security Considerations . . . . . . . . . . . . . . . . . . . 21
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 22 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 22
11. Informative References . . . . . . . . . . . . . . . . . . . . 23 11. Informative References . . . . . . . . . . . . . . . . . . . . 23
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 25
A.1. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 25 A.1. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 25
A.2. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 25 A.2. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 25
A.3. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 25 A.3. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 25
A.4. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 25 A.4. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 25
A.5. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 26 A.5. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 26
A.6. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 26 A.6. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 26
A.7. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 26 A.7. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 26
A.8. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 26 A.8. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 26
A.9. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 26 A.9. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 26
A.10. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 27 A.10. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 27
A.11. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 27 A.11. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 27
A.12. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 27 A.12. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 27
A.13. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 28 A.13. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 28
A.14. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 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
skipping to change at page 14, line 52 skipping to change at page 14, line 52
update each type of report block separately), and also makes it update each type of report block separately), and also makes it
easier to require compliance with a particular report block. easier to require compliance with a particular report block.
5.2. Correlating RTCP XR with RTP data 5.2. Correlating RTCP XR with RTP data
There are some classes of metrics that can only be interpreted with There are some classes of metrics that can only be interpreted with
knowledge of the media codec that is being used (audio MOS scores knowledge of the media codec that is being used (audio MOS scores
were the triggering example, but there may be others). In such cases were the triggering example, but there may be others). In such cases
the correlation of RTCP XR with RTP data is needed. Report blocks the correlation of RTCP XR with RTP data is needed. Report blocks
that require such correlation need to include the payload type of the that require such correlation need to include the payload type of the
reported media, and must signal details and parameters of the payload reported media. In addition, it is necessary to signal the details
format to which that payload type is bound. and parameters of the payload format to which that payload type is
bound using some out-of-band means (e.g., as part of an SDP offer/
answer exchange).
5.3. Correlating RTCP XR with the non-RTP data 5.3. Correlating RTCP XR with the non-RTP data
There may be situations where more than one media transport protocol There may be situations where more than one media transport protocol
is used by one application to interconnect to the same session in the is used by one application to interconnect to the same session in the
gateway. For example, one RTCP XR Packet is sent to the gateway. For example, one RTCP XR Packet is sent to the
participating endpoints using non-RTP-based media transport (e.g., participating endpoints using non-RTP-based media transport (e.g.,
using SIP) in a VOIP session. One crucial factor lies in how to using SIP) in a VOIP session. One crucial factor lies in how to
handle their different identities that are corresponding to different handle their different identities that are corresponding to different
media transport. media transport.
skipping to change at page 16, line 11 skipping to change at page 16, line 13
metric blocks that rely on the Measurement information block [MI] metric blocks that rely on the Measurement information block [MI]
must specify the response in case the new RTCP XR metric block is must specify the response in case the new RTCP XR metric block is
received without an associated measurement information block. In received without an associated measurement information block. In
most cases, it is expected that the correct response is to discard most cases, it is expected that the correct response is to discard
the received metric. In order to reduce measurement information the received metric. In order to reduce measurement information
repetition in one RTCP XR compound packet containing multiple metric repetition in one RTCP XR compound packet containing multiple metric
blocks, the measurement information shall be sent before the related blocks, the measurement information shall be sent before the related
metric blocks that are from the same reporting interval. Note that metric blocks that are from the same reporting interval. Note that
for packet loss robustness if the report blocks for the same interval for packet loss robustness if the report blocks for the same interval
span over more than one RTCP packet then each must have the span over more than one RTCP packet then each must have the
measurement identity information even if though they will be the measurement identity information even though they will be the same.
same.
5.5. Expanding the RTCP XR block namespace 5.5. Expanding the RTCP XR block namespace
The consumption of XR block code points isn't a major issue. However The consumption of XR block code points isn't a major issue. However
if XR block codes points is really close to run out of space, it if XR block codes points is really close to run out of space, it
might be desirable to define new fields in the XR report block or might be desirable to define new fields in the XR report block or
define one XR block type for vendor-specific extensions, with an define one XR block type for vendor-specific extensions, with an
enterprise number included to identify the vendor making the enterprise number included to identify the vendor making the
extension. extension.
skipping to change at page 23, line 21 skipping to change at page 23, line 21
[G1020] ITU-T, "ITU-T Rec. G.1020, Performance parameter [G1020] ITU-T, "ITU-T Rec. G.1020, Performance parameter
definitions for quality of speech and other voiceband definitions for quality of speech and other voiceband
applications utilizing IP networks", July 2006. applications utilizing IP networks", July 2006.
[H323] ITU-T, "ITU-T Rec. H.323, Packet-based multimedia [H323] ITU-T, "ITU-T Rec. H.323, Packet-based multimedia
communications systems", June 2006. communications systems", June 2006.
[MI] Wu, Q., "Measurement Identity and information Reporting [MI] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-05, ID draft-ietf-xrblock-rtcp-xr-meas-identity-06,
April 2012. April 2012.
[P.NAMS] ITU-T, "Non-intrusive parametric model for the Assessment [P.NAMS] ITU-T, "Non-intrusive parametric model for the Assessment
of performance of Multimedia Streaming", ITU-T of performance of Multimedia Streaming", ITU-T
Recommendation P.NAMS, November 2009. Recommendation P.NAMS, November 2009.
[PDV] Hunt, G., Clark, A., and Q. Wu, "RTCP XR Report Block for [PDV] Hunt, G., Clark, A., and Q. Wu, "RTCP XR Report Block for
Packet Delay Variation Metric Reporting", Packet Delay Variation Metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-pdv-02, December 2011. ID draft-ietf-xrblock-rtcp-xr-pdv-02, December 2011.
skipping to change at page 25, line 10 skipping to change at page 25, 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-12 A.1. draft-ietf-avtcore-monarch-13
The following are the major changes compared to 12:
o Editorial Changes.
A.2. 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.2. draft-ietf-avtcore-monarch-11 A.3. 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.3. draft-ietf-avtcore-monarch-10 A.4. 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.4. draft-ietf-avtcore-monarch-09 A.5. 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.5. draft-ietf-avtcore-monarch-08 A.6. 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.6. draft-ietf-avtcore-monarch-07 A.7. 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.7. draft-ietf-avtcore-monarch-06 A.8. 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.8. draft-ietf-avtcore-monarch-05 A.9. 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.9. draft-ietf-avtcore-monarch-04 A.10. 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.10. draft-ietf-avtcore-monarch-03 A.11. 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.11. draft-ietf-avtcore-monarch-02 A.12. 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.12. draft-ietf-avtcore-monarch-01 A.13. 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 28, line 21 skipping to change at page 28, line 30
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.13. draft-ietf-avtcore-monarch-00 A.14. 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. 21 change blocks. 
35 lines changed or deleted 43 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/