draft-ietf-xrblock-rtcp-xr-jb-04.txt   draft-ietf-xrblock-rtcp-xr-jb-05.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 V. Singh Intended status: Standards Track V. Singh
Expires: June 20, 2013 Aalto University Expires: June 22, 2013 Aalto University
Q. Wu Q. Wu
Huawei Huawei
December 17, 2012 December 19, 2012
RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer RTP Control Protocol (RTCP) Extended Report (XR) Block for Jitter Buffer
Metric Reporting Metric Reporting
draft-ietf-xrblock-rtcp-xr-jb-04.txt draft-ietf-xrblock-rtcp-xr-jb-05.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 Jitter Buffer metrics for a (XR) Block that allows the reporting of Jitter Buffer metrics for a
range of RTP applications. 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 36 skipping to change at page 1, line 36
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 June 20, 2013. This Internet-Draft will expire on June 22, 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 19 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . 3 1.1. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4
3. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 5 3. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Jitter Buffer Metrics Block . . . 5 3.2. Definition of Fields in Jitter Buffer Metrics Block . . . 5
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 8 4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
5.3. Contact information for registrations . . . . . . . . . . 9 5.3. Contact information for registrations . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. draft-ietf-xrblock-rtcp-xr-jb-04 . . . . . . . . . . . . . 14 A.1. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 15
A.2. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 14 A.2. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 15
A.3. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 14 A.3. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 15
A.4. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 14 A.4. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 15
A.5. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 14 A.5. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
1.1. Jitter Buffer Metrics Block 1.1. Jitter Buffer Metrics Block
This document defines a new block type to augment those defined in This document 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 jitter buffer The new block type provides information on jitter buffer
configuration and performance. configuration and performance.
skipping to change at page 3, line 27 skipping to change at page 3, line 27
Instances of this Metrics Block refer by Synchronization source Instances of this Metrics Block refer by Synchronization source
(SSRC) to the separate auxiliary Measurement Information block (SSRC) to the separate auxiliary Measurement Information block
[RFC6776] which contains information such as the SSRC of the measured [RFC6776] which contains information such as the SSRC of the measured
stream, and RTP sequence numbers and time intervals indicating the stream, and RTP sequence numbers and time intervals indicating the
span of the report. span of the report.
1.2. RTCP and RTCP XR Reports 1.2. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in [RFC3550]. [RFC3611]
defined an extensible structure for reporting using an RTCP Extended defines an extensible structure for reporting using an RTCP Extended
Report (XR). This document defines a new Extended Report block for Report (XR). This document defines a new Extended Report block for
use with [RFC3550] and [RFC3611]. use with [RFC3550] and [RFC3611].
1.3. Performance Metrics Framework 1.3. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the The Performance Metrics Framework [RFC6390] provides guidance on the
definition and specification of performance metrics. The RTP definition and specification of performance metrics. The RTP
Monitoring Architectures [RFC6792] provides guideline for reporting Monitoring Architectures [RFC6792] provides guideline for reporting
block format using RTCP XR. Metrics described in this draft are in block format using RTCP XR. Metrics described in this draft are in
accordance with the guidelines in [RFC6390][RFC6792]. accordance with the guidelines in [RFC6390]and [RFC6792].
1.4. Applicability 1.4. Applicability
Real-time applications employ a jitter buffer to smooth out jitter Real-time applications employ a jitter buffer to smooth out jitter
introduced on the path from source to destination. These metrics are introduced on the path from source to destination. These metrics are
used to report how the jitter buffer at the receiving end of RTP used to report how the jitter buffer at the receiving end of RTP
stream behaves as a result of jitter in the network and are stream behaves as a result of jitter in the network and are
applicable to a range of RTP applications. applicable to a range of RTP applications.
These metrics reflect how terminal-related factors effect real-time These metrics reflect how terminal-related factors affect real-time
application quality and are useful to provide better end-user quality application quality and are useful to provide better end-user quality
of experience (QoE). of experience (QoE).
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
skipping to change at page 5, line 26 skipping to change at page 5, line 26
compound RTCP packet as this Metrics Block, this Metrics Block should compound RTCP packet as this Metrics Block, this Metrics Block should
be discarded. be discarded.
3.1. Report Block Structure 3.1. Report Block Structure
JB Metrics Block JB Metrics Block
0 1 2 3 0 1 2 3
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 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=NJB | I |C|Reserved | block length=3 | | BT=NJB | I |Cg | Rsvd. | block length=3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB nominal | JB maximum | | JB nominal | JB maximum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB high water mark | JB low water mark | | JB high water mark | JB low water mark |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
skipping to change at page 6, line 15 skipping to change at page 6, line 15
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to the
accumulation period characteristic of cumulative measurements. accumulation period characteristic of cumulative measurements.
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. instantaneous value.
Jitter Buffer Configuration (C): 1 bit Jitter Buffer Configuration (Cg): 2 bits
This field is used to identify the jitter buffer method in use at This field is used to identify the jitter buffer method in use at
the receiver, according to the following code: the receiver, according to the following code:
0 = Fixed jitter buffer 0 = Fixed buffer size and delay
1 = Adaptive jitter buffer 1 = Adaptive buffer size
Reserved: 5 bits 2 = Adaptive playout Delay
3 = Adaptive buffer size and delay
Reserved (Rsvd.): 4 bits
These bits are reserved. They MUST be set to zero by senders These bits are reserved. They MUST be set to zero by senders
ignored by receivers (See [RFC6709] section 4.2). ignored by receivers (See [RFC6709] section 4.2).
Block Length: 16 bits Block Length: 16 bits
The length of this report block in 32-bit words, minus one and The length of this report block in 32-bit words, minus one, in
MUST be set to 3, in accordance with the definition of this field accordance with the definition in [RFC3611]. This field MUST be
in [RFC3611]. The block MUST be discarded if the block length is set to 3 to match the fixed length of the report block. The block
set to a different value. MUST be discarded if the block length is set to a different value.
jitter buffer nominal delay (JB nominal): 16 bits jitter buffer nominal delay (JB nominal): 16 bits
This is the current nominal jitter buffer delay in milliseconds, This is the current nominal jitter buffer delay in milliseconds,
which corresponds to the nominal jitter buffer delay for packets which corresponds to the nominal jitter buffer delay for packets
that arrive exactly on time. It is calculated based on the time that arrive exactly on time. It is calculated based on the
for packets spent in the jitter buffer. This parameter MUST be difference between the receipt time and the playout time for the
packet that arrives exactly on time. This parameter MUST be
provided for both fixed and adaptive jitter buffer provided for both fixed and adaptive jitter buffer
implementations. implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF MUST be reported. measurement is unavailable, the value 0xFFFF MUST be reported.
jitter buffer maximum delay (JB maximum): 16 bits jitter buffer maximum delay (JB maximum): 16 bits
This is the current maximum jitter buffer delay in milliseconds This is the current maximum jitter buffer delay in milliseconds
which corresponds to the earliest arriving packet that would not which corresponds to the earliest arriving packet that would not
be discarded. In simple queue implementations this may correspond be discarded. It is calculated based on the difference between
to the nominal size. In adaptive jitter buffer implementations, the receipt time and the playout time for the earliest arriving
this value may change dynamically. This parameter MUST be packet. In simple queue implementations this may correspond to
the size of the jitter buffer. In adaptive jitter buffer
implementations, this value may vary dynamically from JB low water
mark to JB high water mark (See below). This parameter MUST be
provided for both fixed and adaptive jitter buffer provided for both fixed and adaptive jitter buffer
implementations. implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF MUST be reported. measurement is unavailable, the value 0xFFFF MUST be reported.
jitter buffer high water mark (JB high water mark): 16 bits jitter buffer high water mark (JB high water mark): 16 bits
This is the highest value of the jitter buffer nominal delay in This is the highest value of the jitter buffer nominal delay in
milliseconds which occurred at any time during the reporting milliseconds which occurred at any time during the reporting
interval. interval. This parameter MUST be provided for adaptive jitter
buffer implementations and its value MUST be set to JB maximum for
fixed jitter buffer implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF MUST be reported. measurement is unavailable, the value 0xFFFF MUST be reported.
jitter buffer low water mark (JB low water mark): 16 bits jitter buffer low water mark (JB low water mark): 16 bits
This is the lowest value of the jitter buffer nominal delay in This is the lowest value of the jitter buffer nominal delay in
milliseconds which occurred at any time during the reporting milliseconds which occurred at any time during the reporting
interval. interval. This parameter MUST be provided for adaptive jitter
buffer implementations and its value MUST be set to JB maximum for
fixed jitter buffer implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF MUST be reported. measurement is unavailable, the value 0xFFFF MUST be reported.
4. SDP Signaling 4. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. However XR blocks MAY
without prior signaling. be used without prior signaling (see section 5 of RFC3611).
4.1. SDP rtcp-xr-attrib Attribute Extension 4.1. SDP rtcp-xr-attrib Attribute Extension
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP [RFC4566] attribute "rtcp-xr" defined
in [RFC3611] by providing an additional value of "xr-format" to in [RFC3611] by providing an additional value of "xr-format" to
signal the use of the report block defined in this document. signal the use of the report block defined in this document.
xr-format =/ xr-jb-block xr-format =/ xr-jb-block
xr-jb-block = "jitter-bfr" xr-jb-block = "jitter-bfr"
4.2. Offer/Answer Usage 4.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters
applies. For detailed usage in Offer/Answer for unilateral applies. For detailed usage of Offer/Answer for unilateral
parameter, refer to section 5.2 of [RFC3611]. parameter, refer to section 5.2 of [RFC3611].
5. IANA Considerations 5. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to general guidelines on IANA considerations for RTCP XR, refer to
[RFC3611]. [RFC3611].
5.1. New RTCP XR Block Type value 5.1. New RTCP XR Block Type value
skipping to change at page 12, line 13 skipping to change at page 13, line 13
Geoff Hunt wrote the initial draft of this document. Geoff Hunt wrote the initial draft of this document.
8. Acknowledgments 8. Acknowledgments
The authors gratefully acknowledge reviews and feedback provided by The authors gratefully acknowledge reviews and feedback provided by
Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor, Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin Raviraj, Albrecht Schwarz, Tom Taylor, Hideaki Yamada,Claire Bi,Colin
Perkin, Dan Romascanu and Glen Zorn. Perkin, Dan Romascanu, Kevin Gross and Glen Zorn.
9. References 9. References
9.1. Normative References 9.1. Normative References
[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.
skipping to change at page 13, line 25 skipping to change at page 14, line 25
[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.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", July 2006. Description Protocol", July 2006.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design [RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709, Considerations for Protocol Extensions", RFC 6709,
September 2012. September 2012.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, August 2012.
9.2. Informative References 9.2. Informative References
[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.
[RFC6776] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, August 2012.
[RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures [RFC6792] Hunt, G., Wu, Q., and P. Arden, "Monitoring Architectures
for RTP", RFC 6792, November 2012. for RTP", RFC 6792, November 2012.
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-jb-04 A.1. draft-ietf-xrblock-rtcp-xr-jb-05
The following are the major changes to previous version : The following are the major changes to previous version :
o Some editorial change changes based on the discussion with Glen. o Some editorial change changes based on the discussion with Glen
and Kevin on the list.
A.2. draft-ietf-xrblock-rtcp-xr-jb-03 A.2. draft-ietf-xrblock-rtcp-xr-jb-03
The following are the major changes to previous version : The following are the major changes to previous version :
o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC. o Reduce the "jb cfg" to 1-bit based on discussion in the WGLC.
o Other editorial change changes aligning with PDV,Delay draft. o Other editorial change changes aligning with PDV,Delay draft.
A.3. draft-ietf-xrblock-rtcp-xr-jb-02 A.3. draft-ietf-xrblock-rtcp-xr-jb-02
 End of changes. 25 change blocks. 
52 lines changed or deleted 65 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/