draft-ietf-xrblock-rtcp-xr-jb-06.txt   draft-ietf-xrblock-rtcp-xr-jb-07.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: July 14, 2013 Aalto University Expires: July 30, 2013 Aalto University
Q. Wu Q. Wu
Huawei Huawei
January 10, 2013 January 26, 2013
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-06.txt draft-ietf-xrblock-rtcp-xr-jb-07.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 July 14, 2013. This Internet-Draft will expire on July 30, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 16 skipping to change at page 2, line 16
Table of Contents Table of Contents
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 Operation . . . . . . . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 3.1. Fixed Jitter Buffer . . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in Jitter Buffer Metrics Block . . . 5 3.2. Adaptive Jitter Buffer . . . . . . . . . . . . . . . . . . 5
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 6
4.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 8 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6
4.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 8 4.2. Definition of Fields in Jitter Buffer Metrics Block . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 9 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 9 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 9
5.3. Contact information for registrations . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 6.3. Contact information for registrations . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . . 13 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
A.1. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . . 14
A.2. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . . 14
A.3. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 14 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.4. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 14 A.1. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 15
A.5. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 14 A.2. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 A.3. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 15
A.4. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 15
A.5. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 15
A.6. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 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 5, line 5 skipping to change at page 5, line 5
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].
3. Jitter Buffer Metrics Block 3. Jitter Buffer Operation
A jitter buffer is required to absorb delay variation in network
delivery of media packets. A jitter buffer works by holding media
data for a period of time after it is received but before it s played
out. Packets that arrive relatively early are held in the jitter
buffer relatively longer. Playout can fail if packets arrive too
early and find no available jitter buffer space to be held until time
for playout. Playout can also fail if packets are delayed
excessively by the network and arrive too late after they are
scheduled to be played.
The jitter buffer can be considered as a time window with one side
(the early side) aligned with the delay corresponding to the early
arriving packet and the other side (the late side) representing the
maximum permissible delay before a late arriving packet would be
discarded. The Jitter Buffer delay is referred to as the time spent
in the jitter buffer. The Jitter Buffer Nominal delay is the delay
that is applied to a packet that arrives at its expected time (i.e. 0
jitter) - and corresponds to the late window of the jitter buffer.
The Jitter buffer maximum delay is the delay that is applied to an
earliest arriving packet that is not discarded and corresponds to the
early window of the jitter buffer.
Note that when a packet arrives at its expected time (i.e. 0 jitter),
this packet will fall between left window and right window and we
also call this packet as the packet that arrives exactly on time.
The jitter buffer nominal delay uses this packet as the reference
packet. The reference point would typically be selected as the first
packet. However the reference point could also be selected based on
some other common criterions, e.g., a running average of the delay.
3.1. Fixed Jitter Buffer
A receiver can use either a fixed or adaptive jitter buffer method.
A fixed jitter buffer method is a simple implementation with the
fixed jitter buffer size but may not do a good job of accommodating
varying network performance. The fixed jitter buffer may also have
extra buffer memory and therefore incur extra media latency compared
to an adaptive implementation.
3.2. Adaptive Jitter Buffer
An adaptive jitter buffer method has adaptive jitter buffer size and
may adjust jitter buffer delay during playback in response to
changing network performance. The jitter buffer delay is typically
adjusted to minimize media latency while also minimizing of lost data
due to packets arriving too early or too late.
4. Jitter Buffer Metrics Block
This block describes the configuration and operating parameters of This block describes the configuration and operating parameters of
the jitter buffer in the receiver of the RTP end system or RTP mixer the jitter buffer in the receiver of the RTP end system or RTP mixer
which sends the report. Instances of this Metrics Block refer by which sends the report. Instances of this Metrics Block refer by
SSRC to the separate auxiliary Measurement Information block SSRC to the separate auxiliary Measurement Information block
[RFC6776] which describes the measurement interval in use. This [RFC6776] which describes the measurement interval in use. This
Metrics Block relies on the measurement interval in the Measurement Metrics Block relies on the measurement interval in the Measurement
Information block indicating the span of the report and should be Information block indicating the span of the report and should be
sent in the same compound RTCP packet as the measurement information sent in the same compound RTCP packet as the measurement information
block. If the measurement interval is not received in the same block. If the measurement interval is not received in the same
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 4.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| Rsvd. | block length=3 | | BT=NJB | I |C| 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
3.2. Definition of Fields in Jitter Buffer Metrics Block 4.2. Definition of Fields in Jitter Buffer Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Jitter Buffer Metrics Report Block is identified by the constant A Jitter Buffer Metrics Report Block is identified by the constant
NJB. NJB.
[Note to RFC Editor: please replace NJB with the IANA provided [Note to RFC Editor: please replace NJB with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 2 bits Interval Metric flag (I): 2 bits
This field is used to indicate whether the Jitter Buffer metrics This field is used to indicate whether the Jitter Buffer metrics
are Sampled, Interval or Cumulative metrics: are Sampled, Interval or Cumulative metrics:
I=01: Sampled Value - the reported value is a sampled
instantaneous value.
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
instantaneous value.
Jitter Buffer Configuration (C): 1 bit Jitter Buffer Configuration (C): 1 bit
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 jitter buffer
1 = Adaptive jitter buffer 1 = Adaptive jitter buffer
Reserved (Rsvd.): 5 bits Reserved (Rsvd.): 5 bits
skipping to change at page 6, line 39 skipping to change at page 7, line 39
Block Length: 16 bits Block Length: 16 bits
The length of this report block in 32-bit words, minus one, in The length of this report block in 32-bit words, minus one, in
accordance with the definition in [RFC3611]. This field MUST be accordance with the definition in [RFC3611]. This field MUST be
set to 3 to match the fixed length of the report block. set to 3 to match the fixed length of the report block.
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 that arrive exactly on time. It is calculated based on the time
difference between the receipt time and the playout time for the spend in the jitter buffer for the packet that arrives exactly on
packet that arrives exactly on time. This parameter MUST be time. This parameter MUST be provided for both fixed and adaptive
provided for both fixed and adaptive jitter buffer 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. It is calculated based on the difference between be discarded. It is calculated based on the time spent in the
the receipt time and the playout time for the earliest arriving jitter buffer for the earliest arriving packet In simple queue
packet. In simple queue implementations this may correspond to implementations this may correspond to the size of the jitter
the size of the jitter buffer. In adaptive jitter buffer buffer. In adaptive jitter buffer implementations, this value may
implementations, this value may vary dynamically from JB low water vary dynamically. This parameter MUST be provided for both fixed
mark to JB high water mark (See below). This parameter MUST be and adaptive jitter buffer implementations.
provided for both fixed and adaptive 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 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. This parameter MUST be provided for adaptive jitter interval. This parameter MUST be provided for adaptive jitter
skipping to change at page 8, line 5 skipping to change at page 9, line 5
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. This parameter MUST be provided for adaptive jitter interval. This parameter MUST be provided for adaptive jitter
buffer implementations and its value MUST be set to JB maximum for buffer implementations and its value MUST be set to JB maximum for
fixed jitter buffer implementations. 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 5. 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. However XR blocks MAY [RFC4566] for signaling the use of XR blocks. However XR blocks MAY
be used without prior signaling (see section 5 of RFC3611). be used without prior signaling (see section 5 of RFC3611).
4.1. SDP rtcp-xr-attrib Attribute Extension 5.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 5.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 of 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 6. 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 6.1. New RTCP XR Block Type value
This document assigns the block type value NJB in the IANA "RTCP XR This document assigns the block type value NJB in the IANA "RTCP XR
Block Type Registry" to the "JB Metrics Block". Block Type Registry" to the "JB Metrics Block".
[Note to RFC Editor: please replace NJB with the IANA provided RTCP [Note to RFC Editor: please replace NJB with the IANA provided RTCP
XR block type for this block.] XR block type for this block.]
5.2. New RTCP XR SDP Parameter 6.2. New RTCP XR SDP Parameter
This document also registers a new parameter "jitter-bfr" in the This document also registers a new parameter "jitter-bfr" in the
"RTCP XR SDP Parameters Registry". "RTCP XR SDP Parameters Registry".
5.3. Contact information for registrations 6.3. Contact information for registrations
The contact information for the registrations is: The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com) Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
6. Security Considerations 7. 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 8. Contributors
Geoff Hunt wrote the initial draft of this document. Geoff Hunt wrote the initial draft of this document.
8. Acknowledgments 9. 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, Kevin Gross and Glen Zorn. Perkin, Dan Romascanu, Kevin Gross and Glen Zorn.
9. References 10. References
9.1. Normative References 10.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.
[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 [RFC6776] Wu, Q., "Measurement Identity and information Reporting
using SDES item and XR Block", RFC 6776, August 2012. using SDES item and XR Block", RFC 6776, August 2012.
9.2. Informative References 10.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.
[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-05 A.1. draft-ietf-xrblock-rtcp-xr-jb-07
The following are the major changes to previous version :
o Add one new section to discuss jitter buffer operation.
A.2. 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. and Kevin on the list.
A.2. draft-ietf-xrblock-rtcp-xr-jb-03 A.3. 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.4. draft-ietf-xrblock-rtcp-xr-jb-02
The following are the major changes to previous version : The following are the major changes to previous version :
o Add some explanation text in the SDP offer/answer section. o Add some explanation text in the SDP offer/answer section.
o Add some text in applicability section to explain the use to o Add some text in applicability section to explain the use to
report jitter buffer metrics. report jitter buffer metrics.
o Other editorial change changes aligning with PDV,Delay draft. o Other editorial change changes aligning with PDV,Delay draft.
A.4. draft-ietf-xrblock-rtcp-xr-jb-01 A.5. draft-ietf-xrblock-rtcp-xr-jb-01
The following are the major changes to previous version : The following are the major changes to previous version :
o Outdated reference update o Outdated reference update
o Add one Editor notes to ask clarification on the use of reporting o Add one Editor notes to ask clarification on the use of reporting
jitter buffer metrics. jitter buffer metrics.
o Other Editorial changes. o Other Editorial changes.
A.5. draft-ietf-xrblock-rtcp-xr-jb-00 A.6. draft-ietf-xrblock-rtcp-xr-jb-00
The following are the major changes to previous version : The following are the major changes to previous version :
o Boilerplate updates. o Boilerplate updates.
o references updates o references updates
o allocate 32 bit field in report block for SSRC o allocate 32 bit field in report block for SSRC
o Other editorial changes to get alignment with MONARCH draft. o Other editorial changes to get alignment with MONARCH draft.
 End of changes. 30 change blocks. 
64 lines changed or deleted 120 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/