draft-ietf-avtcore-monarch-15.txt   draft-ietf-avtcore-monarch-16.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 21, 2012 Unaffiliated Expires: December 22, 2012 Unaffiliated
P. Arden P. Arden
BT BT
June 19, 2012 June 20, 2012
Guidelines for Use of the RTP Monitoring Framework Guidelines for Use of the RTP Monitoring Framework
draft-ietf-avtcore-monarch-15.txt draft-ietf-avtcore-monarch-16.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) (RFC3611) block type to report new metrics regarding
media transmission or reception quality, following RTCP guidelines media transmission or reception quality, following RTCP guidelines
established in RFC5968. This memo suggests that a new block should established in RFC5968. This memo suggests that a new block should
contain a single metric or a small number of metrics relevant to a contain a single metric or a small number of metrics relevant to a
single parameter of interest or concern, rather than containing a single parameter of interest or concern, rather than containing a
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 December 21, 2012. This Internet-Draft will expire on December 22, 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 12 skipping to change at page 3, line 12
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. RTP Monitoring Framework . . . . . . . . . . . . . . . . . . . 7 3. RTP Monitoring Framework . . . . . . . . . . . . . . . . . . . 7
3.1. Overview of the RTP Monitoring Framework . . . . . . . . . 7 3.1. Overview of the RTP Monitoring Framework . . . . . . . . . 7
3.2. Location of RTP Monitors . . . . . . . . . . . . . . . . . 9 3.2. Location of RTP Monitors . . . . . . . . . . . . . . . . . 9
4. Issues with reporting metric block using RTCP XR extension . . 11 4. Issues with reporting metric block using RTCP XR extension . . 10
4.1. Using compound metrics block . . . . . . . . . . . . . . . 11 4.1. Using compound metrics block . . . . . . . . . . . . . . . 10
4.2. Correlating RTCP XR with the non-RTP data . . . . . . . . 11 4.2. Correlating RTCP XR with the non-RTP data . . . . . . . . 10
4.3. Measurement Information duplication . . . . . . . . . . . 11 4.3. Measurement Information duplication . . . . . . . . . . . 10
4.4. Consumption of XR block code points . . . . . . . . . . . 12 4.4. Consumption of XR block code points . . . . . . . . . . . 11
5. Guidelines for reporting metric block using RTCP XR . . . . . 13 5. Guidelines for reporting metric block using RTCP XR . . . . . 12
5.1. Contain the single metrics in the Metric Block . . . . . . 13 5.1. Contain the single metrics in the Metric Block . . . . . . 12
5.2. Include the payload type in the Metric Block . . . . . . . 13 5.2. Include the payload type in the Metric Block . . . . . . . 12
5.3. Use RTCP SDES to correlate XR reports with non-RTP data . 14 5.3. Use RTCP SDES to correlate XR reports with non-RTP data . 13
5.4. Reduce Measurement information repetition across 5.4. Reduce Measurement information repetition across
metric blocks . . . . . . . . . . . . . . . . . . . . . . 14 metric blocks . . . . . . . . . . . . . . . . . . . . . . 13
6. An example of a metric block . . . . . . . . . . . . . . . . . 16 6. An example of a metric block . . . . . . . . . . . . . . . . . 15
7. Application to RFC 5117 topologies . . . . . . . . . . . . . . 17 7. Application to RFC 5117 topologies . . . . . . . . . . . . . . 16
7.1. Applicability to Translators . . . . . . . . . . . . . . . 17 7.1. Applicability to Translators . . . . . . . . . . . . . . . 16
7.2. Applicability to MCU . . . . . . . . . . . . . . . . . . . 18 7.2. Applicability to MCU . . . . . . . . . . . . . . . . . . . 17
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 21 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 20
11. Informative References . . . . . . . . . . . . . . . . . . . . 22 11. Informative References . . . . . . . . . . . . . . . . . . . . 21
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 24 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23
A.1. draft-ietf-avtcore-monarch-15 . . . . . . . . . . . . . . 24 A.1. draft-ietf-avtcore-monarch-16 . . . . . . . . . . . . . . 23
A.2. draft-ietf-avtcore-monarch-14 . . . . . . . . . . . . . . 24 A.2. draft-ietf-avtcore-monarch-15 . . . . . . . . . . . . . . 23
A.3. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 24 A.3. draft-ietf-avtcore-monarch-14 . . . . . . . . . . . . . . 23
A.4. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 24 A.4. draft-ietf-avtcore-monarch-13 . . . . . . . . . . . . . . 24
A.5. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 25 A.5. draft-ietf-avtcore-monarch-12 . . . . . . . . . . . . . . 24
A.6. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 25 A.6. draft-ietf-avtcore-monarch-11 . . . . . . . . . . . . . . 24
A.7. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 25 A.7. draft-ietf-avtcore-monarch-10 . . . . . . . . . . . . . . 24
A.8. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 25 A.8. draft-ietf-avtcore-monarch-09 . . . . . . . . . . . . . . 24
A.9. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 26 A.9. draft-ietf-avtcore-monarch-08 . . . . . . . . . . . . . . 25
A.10. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 26 A.10. draft-ietf-avtcore-monarch-07 . . . . . . . . . . . . . . 25
A.11. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 26 A.11. draft-ietf-avtcore-monarch-06 . . . . . . . . . . . . . . 25
A.12. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 26 A.12. draft-ietf-avtcore-monarch-05 . . . . . . . . . . . . . . 25
A.13. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 27 A.13. draft-ietf-avtcore-monarch-04 . . . . . . . . . . . . . . 25
A.14. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 27 A.14. draft-ietf-avtcore-monarch-03 . . . . . . . . . . . . . . 26
A.15. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 27 A.15. draft-ietf-avtcore-monarch-02 . . . . . . . . . . . . . . 26
A.16. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 28 A.16. draft-ietf-avtcore-monarch-01 . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 A.17. draft-ietf-avtcore-monarch-00 . . . . . . . . . . . . . . 27
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)
[RFC3550] are being developed for the purpose of collecting and [RFC3550] are being developed for the purpose of collecting and
skipping to change at page 8, line 17 skipping to change at page 8, line 17
supplement the existing RTCP packets and provide more detailed supplement the existing RTCP packets and provide more detailed
feedback on reception quality and RTCP NACK [RFC4585] that provides feedback on reception quality and RTCP NACK [RFC4585] that provides
feedback on the RTP sequence numbers for a subset of the lost packets feedback on the RTP sequence numbers for a subset of the lost packets
or all the currently lost packets. Ultimately the metric information or all the currently lost packets. Ultimately the metric information
collected by RTP monitors within the RTP monitoring framework may go collected by RTP monitors within the RTP monitoring framework may go
to the network management tools beyond the RTP monitoring framework, to the network management tools beyond the RTP monitoring framework,
e.g., as shown Figure 1, the RTP monitors may export the metric e.g., as shown Figure 1, the RTP monitors may export the metric
information derived from the RTP monitoring framework to the information derived from the RTP monitoring framework to the
management system using non-RTP means. management system using non-RTP means.
+-------------------+ +-----------+ +----------+
| Management <-------------------------+ |Third Party| |Management|
+-------------> System <--------------| | |RTP Monitor| >>>>>>>>| System |<<<<<
| | | | | +-----------+ ^ +----------+ ^
| +---------^---------+ | | : ^ ^ ^
| | | | : | ^ ^
| | | | +---------------+ : | +-------------+ +-------------+
+----------+ RTP/RTCP +Intermediary--+ RTP/RTCP +-------------+ | | +-----------+ | : | |+-----------+| |+-----------+|
|RTP Sender| Stream | RTP System | Stream |RTP Receiver | | | |RTP Monitor| |..:...|.......||RTP Monitor||........||RTP Monitor||
|+-------+ |--------->| +-------+ |----------->| +-------+ | | | +-----------+ | | |+-----------+| |+-----------+|
|| | | | | RTP | | | | | | | | |------+------>| |------->| |
|| |<+-------------|Monitor|<---------------+--- | | | | RTP Sender | |RTP Mixer or | |RTP Receiver |
|| | | MB | +-------+ | MB | | | | | | | |Translator | | |
|| | | Report +--------------+ Report | | | | | +---------------+ +-------------+ +-------------+
|| | | | | | | |
|| | | RTP/RTCP +------------+ | | | | |
|| RTP | | Stream | | | | RTP | | |
|| | |---------------------> Third Party| | | | | |
|| | | | RTP Monitor|-->| | | | |
||Monitor|<----------------------+ | || |Monitor| | |
|| | | MB +------------- || | | | |
|| | | Report || | | | |
|| | | || | | | |
|| | | RTCP +------------+ || | | | |
|| | | Stream | | || | | | |
|| | |---------------------> Third Party| || | | | |
|| | | | RTP Monitor--->| | | | |
|+-------+ | | | || +-------+ | |
| | +------------+ || | |
+----------+ |+-------------+ |
| |
+----------------+
Figure 1: RTP monitoring Framework ----> RTP media traffic
..... RTCP control channel
>>>>> Non-RTP/RTCP management flows
Figure 1: Example showing the components of the RTP monitoring
framework
RTP may be used with multicast groups, both Any Source Multicast RTP may be used with multicast groups, both Any Source Multicast
(ASM) and Source Specific Multicast (SSM). These groups can be (ASM) and Source Specific Multicast (SSM). These groups can be
monitored using RTCP. In the ASM case, the RTP monitor is a member monitored using RTCP. In the ASM case, the RTP monitor is a member
of the multicast group and listens to RTCP XR reports from all of the multicast group and listens to RTCP reports from all members
members of the ASM group. In the SSM case, there is a unicast of the ASM group. In the SSM case, there is a unicast feedback
feedback target that receives RTCP feedback from receivers and target that receives RTCP feedback from receivers and distributes it
distributes it to other members of the SSM group (see figure 1 of to other members of the SSM group (see figure 1 of [RFC5760] ). The
[RFC5760] ). The RTP monitor will need to be co-located with the RTP monitor will need to be co-located with the feedback target to
feedback target to receive all feedback from the receivers (this may receive all feedback from the receivers (this may also be an
also be an intermediate system). In both ASM and SSM scenarios, intermediate system). In both ASM and SSM scenarios, receivers can
receivers can send RTCP XR reports to enhance the reception quality send RTCP reports to enhance the reception quality reporting.
reporting.
3.2. Location of RTP Monitors 3.2. Location of RTP Monitors
As shown in the Figure 1, there are several possible locations from As shown in the Figure 1, there are several possible locations from
where RTP sessions can be monitored. These include end-systems that where RTP sessions can be monitored. These include end-systems that
terminate RTP sessions, intermediate-systems that are an active part terminate RTP sessions, intermediate-systems that are an active part
of an RTP session, and third-party devices that passively monitor an of an RTP session, and third-party devices that passively monitor an
RTP session. Not every RTP sessions will include monitoring, and RTP session. Not every RTP sessions will include monitoring, and
those sessions that are monitored will not all include each type of those sessions that are monitored will not all include each type of
monitor. The performance metrics collected by RTP monitors can be monitor. The performance metrics collected by RTP monitors can be
skipping to change at page 22, line 16 skipping to change at page 21, line 16
[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.
[MEASI] Wu, Q., "Measurement Identity and information Reporting [MEASI] 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-06, ID draft-ietf-xrblock-rtcp-xr-meas-identity-07, June 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-03, May 2012.
[QOE] Hunt, G., Clark, A., Wu, Q., Schott, R., and G. Zorn, [QOE] Hunt, G., Clark, A., Wu, Q., Schott, R., and G. Zorn,
"RTCP XR Blocks for QoE Metric Reporting", "RTCP XR Blocks for QoE Metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-qoe-00, February 2012. ID draft-ietf-xrblock-rtcp-xr-qoe-01, May 2012.
[RFC1122] Braden, R., "Requirements for Internet Hosts -- [RFC1122] Braden, R., "Requirements for Internet Hosts --
Communication Layers", RFC 1122, October 1989. Communication Layers", RFC 1122, October 1989.
[RFC2959] Baugher, M., Strahm, B., and I. Suconick, "Real-Time [RFC2959] Baugher, M., Strahm, B., and I. Suconick, "Real-Time
Transport Protocol Management Information Base", RFC 2959, Transport Protocol Management Information Base", RFC 2959,
October 2000. October 2000.
[RFC3393] Demichelis, C., "IP Packet Delay Variation Metric for IP [RFC3393] Demichelis, C., "IP Packet Delay Variation Metric for IP
Performance Metrics (IPPM)", RFC 3393, November 2002. Performance Metrics (IPPM)", RFC 3393, November 2002.
skipping to change at page 24, 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-15 A.1. draft-ietf-avtcore-monarch-16
The following are the major changes compared to 15:
o A few modification to the figure 1.
o Change RTCP XR reports into RTCP reports in the section 3.1.
o References Update.
A.2. 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.2. draft-ietf-avtcore-monarch-14 A.3. 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.3. draft-ietf-avtcore-monarch-13 A.4. 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.4. draft-ietf-avtcore-monarch-12 A.5. 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.5. draft-ietf-avtcore-monarch-11 A.6. 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.6. draft-ietf-avtcore-monarch-10 A.7. 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.7. draft-ietf-avtcore-monarch-09 A.8. 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.8. draft-ietf-avtcore-monarch-08 A.9. 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.9. draft-ietf-avtcore-monarch-07 A.10. 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.10. draft-ietf-avtcore-monarch-06 A.11. 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.11. draft-ietf-avtcore-monarch-05 A.12. 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.12. draft-ietf-avtcore-monarch-04 A.13. 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.13. draft-ietf-avtcore-monarch-03 A.14. 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.14. draft-ietf-avtcore-monarch-02 A.15. 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.15. draft-ietf-avtcore-monarch-01 A.16. 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 12 skipping to change at page 27, line 21
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.16. draft-ietf-avtcore-monarch-00 A.17. 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. 28 change blocks. 
102 lines changed or deleted 98 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/