draft-ietf-xrblock-rtcp-xr-pdv-07.txt   draft-ietf-xrblock-rtcp-xr-pdv-08.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track Q. Wu Intended status: Standards Track Q. Wu
Expires: March 25, 2013 Huawei Expires: March 30, 2013 Huawei
September 21, 2012 September 26, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block for Packet Delay RTP Control Protocol (RTCP) Extended Report (XR) Block for Packet Delay
Variation Metric Reporting Variation Metric Reporting
draft-ietf-xrblock-rtcp-xr-pdv-07.txt draft-ietf-xrblock-rtcp-xr-pdv-08.txt
Abstract Abstract
This document defines an RTP Control Protocol (RTCP) Extended Report This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) block that allows the reporting of Packet Delay Variation (XR) block that allows the reporting of Packet Delay Variation
metrics for a range of RTP applications. metrics for a range of RTP applications.
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 30, 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 33 skipping to change at page 2, line 33
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12
5.3. Contact information for registrations . . . . . . . . . . 12 5.3. Contact information for registrations . . . . . . . . . . 12
5.4. New registry of PDV types . . . . . . . . . . . . . . . . 12 5.4. New registry of PDV types . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 19 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 19
A.1. draft-ietf-xrblock-rtcp-xr-pdv-06 . . . . . . . . . . . . 19 A.1. draft-ietf-xrblock-rtcp-xr-pdv-08 . . . . . . . . . . . . 19
A.2. draft-ietf-xrblock-rtcp-xr-pdv-05 . . . . . . . . . . . . 19 A.2. draft-ietf-xrblock-rtcp-xr-pdv-06 . . . . . . . . . . . . 19
A.3. draft-ietf-xrblock-rtcp-xr-pdv-04 . . . . . . . . . . . . 19 A.3. draft-ietf-xrblock-rtcp-xr-pdv-05 . . . . . . . . . . . . 19
A.4. draft-ietf-xrblock-rtcp-xr-pdv-03 . . . . . . . . . . . . 19 A.4. draft-ietf-xrblock-rtcp-xr-pdv-04 . . . . . . . . . . . . 19
A.5. draft-ietf-xrblock-rtcp-xr-pdv-02 . . . . . . . . . . . . 20 A.5. draft-ietf-xrblock-rtcp-xr-pdv-03 . . . . . . . . . . . . 19
A.6. draft-ietf-xrblock-rtcp-xr-pdv-01 . . . . . . . . . . . . 20 A.6. draft-ietf-xrblock-rtcp-xr-pdv-02 . . . . . . . . . . . . 20
A.7. draft-ietf-xrblock-rtcp-xr-pdv-00 . . . . . . . . . . . . 20 A.7. draft-ietf-xrblock-rtcp-xr-pdv-01 . . . . . . . . . . . . 20
A.8. draft-ietf-avt-rtcp-xr-pdv-03 . . . . . . . . . . . . . . 20 A.8. draft-ietf-xrblock-rtcp-xr-pdv-00 . . . . . . . . . . . . 20
A.9. draft-ietf-avt-rtcp-xr-pdv-03 . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
1.1. Packet Delay Variation Metrics Block 1.1. Packet Delay Variation Metrics Block
This draft defines a new block type to augment those defined in This draft defines a new block type to augment those defined in
[RFC3611], for use in a range of RTP applications. [RFC3611], for use in a range of RTP applications.
The new block type provides information on Packet Delay Variation The new block type provides information on Packet Delay Variation
skipping to change at page 5, line 10 skipping to change at page 5, line 10
16- bit values 0xfffe and 0xffff are used as flags for "over- 16- bit values 0xfffe and 0xffff are used as flags for "over-
range" and "unavailable" conditions, a 0:16 quantity has range range" and "unavailable" conditions, a 0:16 quantity has range
0.0 to 1 - 3/65536 = 0.9999542 0.0 to 1 - 3/65536 = 0.9999542
3. Packet Delay Variation Metrics Block 3. Packet Delay Variation Metrics Block
Metrics in this block report on packet delay variation in the stream Metrics in this block report on packet delay variation in the stream
arriving at the RTP system. The measurement of these metrics are arriving at the RTP system. The measurement of these metrics are
made at the receiving end of the RTP stream. Instances of this made at the receiving end of the RTP stream. Instances of this
Metrics Block refer by Synchronization source (SSRC) to the separate metric block refer by Synchronization Source (SSRC) to the separate
auxiliary Measurement Information block [MEASI] which contains auxiliary Measurement Information Block [MEASI] which contains
measurement intervals. This metric block relies on the measurement measurement intervals. This metric block relies on the measurement
interval in the Measurement Information block indicating the span of interval given by the value of the "Measurement Duration (Interval)"
the report and SHOULD be sent in the same compound RTCP packet as the field in the Measurement Information Block to indicate the span of
measurement information block. If the measurement interval is not the report and MUST be sent in the same compound RTCP packet as the
received for this metric block, this metric block MUST be discarded ( Measurement Information Block. If the measurement interval is not
See section 5.4 of[MONARCH]for timing details). received for this metric block, this metric block MUST be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
PDV metrics block PDV metrics block
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NPDV | I |pdvtyp |Rsv| block length=4 | | BT=NPDV | I |pdvtyp |Rsv| block length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pos PDV Threshold/Peak | Pos PDV Percentile | | Pos PDV Threshold/Peak | Pos PDV Percentile |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neg PDV Threshold/Peak | Neg PDV Percentile | | Neg PDV Threshold/Peak | Neg PDV Percentile |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mean PDV | Reserved | | Mean PDV | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in PDV Metrics Block 3.2. Definition of Fields in PDV Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Packet Delay Variation Metrics Report Block is identified by the A Packet Delay Variation Metrics Report Block is identified by the
constant NPDV. constant NPDV.
skipping to change at page 6, line 15 skipping to change at page 6, line 15
Interval Metric flag (I): 2 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Packet Delay variation This field is used to indicate whether the Packet Delay variation
metrics are Sampled, Interval or Cumulative metrics [MONARCH], metrics are Sampled, Interval or Cumulative metrics [MONARCH],
that is, whether the reported values applies to the most recent that is, whether the reported values applies to the most recent
measurement interval duration between successive metrics reports measurement interval duration between successive metrics reports
(I=10) (the Interval Duration) or to the accumulation period (I=10) (the Interval Duration) or to the accumulation period
characteristic of cumulative measurements (I=11) (the Cumulative characteristic of cumulative measurements (I=11) (the Cumulative
Duration) or is a sampled instantaneous value (I=01) (Sampled Duration) or is a sampled instantaneous value (I=01) (Sampled
Value). The value I=00 is reserved, and MUST NOT be used. If the Value). The value I=00 is reserved, and MUST NOT be used. If the
value I=00 is received, it MUST be ignored by the receiver. value I=00 is received, then the XR block MUST be ignored by the
receiver.
Packet Delay Variation Metric Type (pdvtyp): 4 bits Packet Delay Variation Metric Type (pdvtyp): 4 bits
Packet Delay Variation Metric Type is of type enumerated and is Packet Delay Variation Metric Type is of type enumerated and is
interpreted as Integer. This field is used to identify the Packet interpreted as an unsigned, 4-bit integer. This field is used to
Delay Variation Metric Type used in this report block, according identify the Packet Delay Variation Metric Type used in this
to the following code: report block, according to the following code:
bits 014-011 bits 014-011
0: MAPDV2, Clause 6.2.3.2 of [G.1020], 0: MAPDV2, Clause 6.2.3.2 of [G.1020],
1: 2-point PDV, Clause 6.2.4 of [Y.1540]. 1: 2-point PDV, Clause 6.2.4 of [Y.1540].
Rsv.: 2 bits Rsv.: 2 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
skipping to change at page 7, line 12 skipping to change at page 7, line 12
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of [RFC3611].
Positive PDV Threshold/Peak: 16 bits Positive PDV Threshold/Peak: 16 bits
This field is associated with the Positive PDV percentile and This field is associated with the Positive PDV percentile and
expressed in Milliseconds with numeric format S11:4. The term expressed in Milliseconds with numeric format S11:4. The term
Positive represents that the packets are arriving later than the Positive represents that the packets are arriving later than the
expected time. expected time.
If the measured value is more negative than -2047.9375 (the value If the measured value is less than -2047.9375 (the value which
which would be coded as 0x8001), the value 0x8000 SHOULD be would be coded as 0x8001), the value 0x8000 SHOULD be reported to
reported to indicate an over-range negative measurement. If the indicate an over-range negative measurement. If the measured
measured value is more positive than +2047.8125 (the value which value is greater than +2047.8125 (the value which would be coded
would be coded as 0x7FFD), the value 0x7FFE SHOULD be reported to as 0x7FFD), the value 0x7FFE SHOULD be reported to indicate an
indicate an over-range positive measurement. If the measurement over-range positive measurement. If the measurement is
is unavailable, the value 0x7FFF MUST be reported. unavailable, the value 0x7FFF MUST be reported.
Positive PDV Percentile: 16 bits Positive PDV Percentile: 16 bits
The percentages of packets in the RTP stream for which individual The percentages of packets in the RTP stream for which individual
packet delays were less than the Positive PDV Threshold. It is packet delays were less than the Positive PDV Threshold. It is
expressed in numeric format 8:8 with values from 0 to 100th expressed in numeric format 8:8 with values from 0 to 100th
percentile. percentile.
If the measurement is unavailable, the value 0xFFFF MUST be If the measurement is unavailable, the value 0xFFFF MUST be
reported. reported.
skipping to change at page 9, line 14 skipping to change at page 9, line 14
3.3. Guidance on use of PDV metrics 3.3. Guidance on use of PDV metrics
This subsection provides informative guidance on when it might be This subsection provides informative guidance on when it might be
appropriate to use each of the PDV metric types. appropriate to use each of the PDV metric types.
MAPDV2 (Clause 6.2.3.2 of [G.1020]) is the envelope of instantaneous MAPDV2 (Clause 6.2.3.2 of [G.1020]) is the envelope of instantaneous
(per-packet) delay when compared to the short term moving average (per-packet) delay when compared to the short term moving average
delay. This metric could be useful in determining residual delay. This metric could be useful in determining residual
impairment when an RTP end system uses an adaptive de-jitter buffer impairment when an RTP end system uses an adaptive de-jitter buffer
which tracks the average delay variation, provided the adaptive de- which tracks the average delay variation, provided that the averaging
jitter buffer have similar averaging behaviour as the MAPDV2 behavior of the adaptive algorithm is similar to that of the MAPDV2
algorithm. algorithm.
2-point PDV (Clause 6.2.4 of [Y.1540]) reports absolute packet delay 2-point PDV (Clause 6.2.4 of [Y.1540]) reports absolute packet delay
variation with respect to a defined reference packet transfer delay . variation with respect to a defined reference packet transfer delay .
Note that the reference packet is generally selected as the packet Note that the reference packet is generally selected as the packet
with minimum delay based on the most common criterion (See section 1 with minimum delay based on the most common criterion (See section 1
and section 5.1 of [RFC5481] ). In an RTP context, the two "points" and section 5.1 of [RFC5481] ). In an RTP context, the two "points"
are at the sender (the synchronization source which applies RTP are at the sender (the synchronization source which applies RTP
timestamps) and at the receiver. The value of this metric for the timestamps) and at the receiver. The value of this metric for the
packet with index j is identical to the quantity D(i,j) defined in packet with index j is identical to the quantity D(i,j) defined in
Section 6.4.1 of [RFC3550] and the packet index i should be set equal Section 6.4.1 of [RFC3550] and the packet index i should be set equal
to the index of the reference packet for the metric in practice. The to the index of the reference packet for the metric in practice. The
metric includes the effect of the frequency offsets of clocks in both metric includes the effect of the frequency offsets of clocks in both
the sender and receiver end systems, so it is useful mainly in the sender and receiver end systems, so it is useful mainly in
network where synchronisation is distributed. As well as measuring network where synchronization is distributed. As well as measuring
packet delay variation in such networks, it may be used to ensure packet delay variation in such networks, it may be used to ensure
that synchronisation is effective, for example where the network that synchronization is effective, for example where the network
carries ISDN data traffic over RTP [RFC4040]. The metric is likely carries ISDN data traffic over RTP [RFC4040]. The metric is likely
to be useful in networks which use fixed de-jitter buffering, because to be useful in networks which use fixed de-jitter buffering, because
it may be used to determine the length of the required de-jitter it may be used to determine the length of the required de-jitter
buffer, or to determine if network performance has deteriorated such buffer, or to determine if network performance has deteriorated such
that existing de-jitter buffers are too small to accommodate the that existing de-jitter buffers are too small to accommodate the
observed delay variation. observed delay variation.
3.4. Examples of use 3.4. Examples of use
(b) To report MAPDV2 [G.1020]: (b) To report MAPDV2 [G.1020]:
Pos PDV Threshold = 50.0; Pos PDV Percentile = 95.3; Neg PDV Pos PDV Threshold = 50.0; Pos PDV Percentile = 95.3; Neg PDV
Threshold = 50.0 (note this implies -50ms); Neg PDV Percentile Threshold = 50.0 (note this implies -50ms); Neg PDV Percentile
= 98.4; PDV type = 1 (MAPDV2) = 98.4; PDV type = 0 (MAPDV2)
causes average MAPDV2 to be reported in the Mean PDV field. causes average MAPDV2 to be reported in the Mean PDV field.
Note that implementations may either fix the reported Note that implementations may either fix the reported
percentile and calculate the associated PDV level or may fix a percentile and calculate the associated PDV level or may fix a
threshold PDV level and calculate the associated percentile. threshold PDV level and calculate the associated percentile.
From a practical implementation perspective it is simpler to From a practical implementation perspective it is simpler to
use the second of these approaches (except of course in the use the second of these approaches (except of course in the
extreme case of a 100% percentile). extreme case of a 100% percentile).
skipping to change at page 13, line 8 skipping to change at page 13, line 8
measurements and how they are processed to generate the reported measurements and how they are processed to generate the reported
metric. This should include the units of measurement, how values metric. This should include the units of measurement, how values
of the metric are reported in the three 16-bit fields "Pos PDV of the metric are reported in the three 16-bit fields "Pos PDV
Threshold/Peak", "Neg PDV Threshold/Peak" and "Mean PDV" within Threshold/Peak", "Neg PDV Threshold/Peak" and "Mean PDV" within
the report block, and how the metric uses the two 16-bit fields the report block, and how the metric uses the two 16-bit fields
"Pos PDV Percentile" and "Neg PDV Percentile". "Pos PDV Percentile" and "Neg PDV Percentile".
o The review process for the registry is "Specification Required" as o The review process for the registry is "Specification Required" as
described in Section 4.1 of [RFC5226]. described in Section 4.1 of [RFC5226].
o Entries in the registry are integers. The valid range is 0 to 15 o Entries in the registry are unsigned 4-bit integers. The valid
corresponding to the 4-bit field "pdvtyp" in the block. Values range is 0 to 15 corresponding to the 4-bit field "pdvtyp" in the
are to be recorded in decimal. block. Values are to be recorded in decimal.
o Initial assignments are as follows: o Initial assignments are as follows:
* 0: MAPDV2, Clause 6.2.3.2 of [G.1020], * 0: MAPDV2, Clause 6.2.3.2 of [G.1020],
* 1: 2-point PDV, Clause 6.2.4 of [Y.1540] * 1: 2-point PDV, Clause 6.2.4 of [Y.1540],
* 2-15: Reserved for future use.
6. Security Considerations 6. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
This block does not provide per-packet statistics so the risk to This block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of [RFC3611]
does not apply. does not apply.
7. Contributors 7. Contributors
Geoff Hunt wrote the initial version of this document. Geoff Hunt wrote the initial version of this document.
8. Acknowledgments 8. Acknowledgments
The authors gratefully acknowledge the comments and contributions The authors gratefully acknowledge reviews and feedback provided by
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Jing Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada, Jing Zhao,
Zhao,Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn,Shida Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn, Shida Schubert,
Schubert, Benoit Claise, Adrian Farrel, Pete Resnick. Benoit Claise, Adrian Farrel and Pete Resnick.
9. References 9. References
9.1. Normative References 9.1. Normative References
[G.1020] ITU-T, "ITU-T Rec. G.1020, Performance parameter [G.1020] 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.
[MEASI] Hunt, G., "Measurement Identity and information Reporting [MEASI] Hunt, G., "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-10,
April 2012. August 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
skipping to change at page 17, line 47 skipping to change at page 17, line 47
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", January 2008. Specifications: ABNF", January 2008.
[Y.1540] ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and [Y.1540] ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and
availability performance parameters", November 2007. availability performance parameters", November 2007.
9.2. Informative References 9.2. Informative References
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [MONARCH] Hunt, G., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-13, May 2012. ID draft-ietf-avtcore-monarch-22, September 2012.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, March 2009. Applicability Statement", RFC 5481, March 2009.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011. Development", RFC 6390, October 2011.
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-xrblock-rtcp-xr-pdv-06 A.1. draft-ietf-xrblock-rtcp-xr-pdv-08
The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-07,6:
o Editorial change based on IESG Review.
A.2. draft-ietf-xrblock-rtcp-xr-pdv-06
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-05: draft-ietf-xrblock-rtcp-xr-pdv-05:
o Editorial change based on IESG Review. o Editorial change based on IESG Review.
o SDP element update based on pete's suggestion. o SDP element update based on pete's suggestion.
o Clarify the value of PDV in the applicability section. o Clarify the value of PDV in the applicability section.
o Clarify measurement point and timing in section 3. o Clarify measurement point and timing in section 3.
A.2. draft-ietf-xrblock-rtcp-xr-pdv-05 A.3. draft-ietf-xrblock-rtcp-xr-pdv-05
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-04: draft-ietf-xrblock-rtcp-xr-pdv-04:
o Move Geoff Hunt from author list to Contributors section based on o Move Geoff Hunt from author list to Contributors section based on
his suggestion. his suggestion.
A.3. draft-ietf-xrblock-rtcp-xr-pdv-04 A.4. draft-ietf-xrblock-rtcp-xr-pdv-04
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-03: draft-ietf-xrblock-rtcp-xr-pdv-03:
o Editorial changes based on Gen-Art Review and Secdir Review. o Editorial changes based on Gen-Art Review and Secdir Review.
A.4. draft-ietf-xrblock-rtcp-xr-pdv-03 A.5. draft-ietf-xrblock-rtcp-xr-pdv-03
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-02: draft-ietf-xrblock-rtcp-xr-pdv-02:
o Make definition of pdvtype get alignment with IANA section. o Make definition of pdvtype get alignment with IANA section.
o Make Guidance on use of PDV metrics get alignment with RFC5481. o Make Guidance on use of PDV metrics get alignment with RFC5481.
o Other Editorial changes. o Other Editorial changes.
A.5. draft-ietf-xrblock-rtcp-xr-pdv-02 A.6. draft-ietf-xrblock-rtcp-xr-pdv-02
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-01: draft-ietf-xrblock-rtcp-xr-pdv-01:
o Updated references. o Updated references.
o Allocate one more bit for Interval metric flag to indicate sampled o Allocate one more bit for Interval metric flag to indicate sampled
metric can be used. metric can be used.
o Add a few clarification text for failure mode. o Add a few clarification text for failure mode.
A.6. draft-ietf-xrblock-rtcp-xr-pdv-01 A.7. draft-ietf-xrblock-rtcp-xr-pdv-01
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-00: draft-ietf-xrblock-rtcp-xr-pdv-00:
o Fix typos or nits in the definition of Negative PDV Threshold/ o Fix typos or nits in the definition of Negative PDV Threshold/
Peak. Peak.
o Fix nits in Numeric format S7:8. o Fix nits in Numeric format S7:8.
o remove the text that is relevant to tag field. o remove the text that is relevant to tag field.
o Add text in SDP signaling section to clarify indicationof metric o Add text in SDP signaling section to clarify indicationof metric
unavailable. unavailable.
A.7. draft-ietf-xrblock-rtcp-xr-pdv-00 A.8. draft-ietf-xrblock-rtcp-xr-pdv-00
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-avt-rtcp-xr-pdv-03: draft-ietf-avt-rtcp-xr-pdv-03:
o Updated references. o Updated references.
A.8. draft-ietf-avt-rtcp-xr-pdv-03 A.9. draft-ietf-avt-rtcp-xr-pdv-03
The following are the major changes to previous version : The following are the major changes to previous version :
o Changed BNF for SDP following Christian Groves' and Tom Taylor's o Changed BNF for SDP following Christian Groves' and Tom Taylor's
comments (4th and 5th May 2009). comments (4th and 5th May 2009).
o Updated references. o Updated references.
Authors' Addresses Authors' Addresses
 End of changes. 27 change blocks. 
71 lines changed or deleted 82 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/