draft-ietf-xrblock-rtcp-xr-jb-10.txt   draft-ietf-xrblock-rtcp-xr-jb-11.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: October 4, 2013 Aalto University Expires: October 29, 2013 Aalto University
Q. Wu Q. Wu
Huawei Huawei
April 2, 2013 April 27, 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-10.txt draft-ietf-xrblock-rtcp-xr-jb-11.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 October 4, 2013. This Internet-Draft will expire on October 29, 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 23 skipping to change at page 2, line 23
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 Operation . . . . . . . . . . . . . . . . . . . 5 3. Jitter Buffer Operation . . . . . . . . . . . . . . . . . . . 5
3.1. Idealized Jitter Buffer . . . . . . . . . . . . . . . . . 5 3.1. Idealized Jitter Buffer . . . . . . . . . . . . . . . . . 5
3.2. Fixed Jitter Buffer . . . . . . . . . . . . . . . . . . . 6 3.2. Fixed Jitter Buffer . . . . . . . . . . . . . . . . . . . 6
3.3. Adaptive Jitter Buffer . . . . . . . . . . . . . . . . . . 6 3.3. Adaptive Jitter Buffer . . . . . . . . . . . . . . . . . . 6
4. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 7 4. Jitter Buffer Metrics Block . . . . . . . . . . . . . . . . . 7
4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7 4.1. Report Block Structure . . . . . . . . . . . . . . . . . . 7
4.2. Definition of Fields in Jitter Buffer Metrics Block . . . 7 4.2. Definition of Fields in Jitter Buffer Metrics Block . . . 7
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 10 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 11
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 10 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 11 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 12
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 11 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12
6.3. Contact information for registrations . . . . . . . . . . 11 6.3. Contact information for registrations . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15 10.1. Normative References . . . . . . . . . . . . . . . . . . . 16
10.2. Informative References . . . . . . . . . . . . . . . . . . 15 10.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Metrics represented using RFC6390 Template . . . . . 16 Appendix A. Metrics represented using RFC6390 Template . . . . . 17
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 19 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 20
B.1. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 19 B.1. draft-ietf-xrblock-rtcp-xr-jb-11 . . . . . . . . . . . . . 20
B.2. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 19 B.2. draft-ietf-xrblock-rtcp-xr-jb-10 . . . . . . . . . . . . . 20
B.3. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 19 B.3. draft-ietf-xrblock-rtcp-xr-jb-09 . . . . . . . . . . . . . 20
B.4. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 19 B.4. draft-ietf-xrblock-rtcp-xr-jb-08 . . . . . . . . . . . . . 20
B.5. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 19 B.5. draft-ietf-xrblock-rtcp-xr-jb-07 . . . . . . . . . . . . . 20
B.6. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 19 B.6. draft-ietf-xrblock-rtcp-xr-jb-05 . . . . . . . . . . . . . 20
B.7. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 20 B.7. draft-ietf-xrblock-rtcp-xr-jb-03 . . . . . . . . . . . . . 21
B.8. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 20 B.8. draft-ietf-xrblock-rtcp-xr-jb-02 . . . . . . . . . . . . . 21
B.9. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 20 B.9. draft-ietf-xrblock-rtcp-xr-jb-01 . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 B.10. draft-ietf-xrblock-rtcp-xr-jb-00 . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
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.
The metric belongs to the class of transport-related end system The metric belongs to the class of transport-related end system
metrics defined in [RFC6792]. metrics defined in [RFC6792].
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]
defines 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
skipping to change at page 3, line 41 skipping to change at page 3, line 41
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]and [RFC6792]. accordance with the guidelines in [RFC6390]and [RFC6792].
1.4. Applicability 1.4. Applicability
Real-time applications employ a jitter buffer to absorb jitter Real-time applications employ a de-jitter buffer [RFC5481] to absorb
introduced on the path from source to destination. These metrics are jitter introduced on the path from source to destination. These
used to report how the jitter buffer at the receiving end of RTP metrics are used to report how the jitter buffer at the receiving end
stream behaves as a result of jitter in the network and are of RTP 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 affect real-time These metrics are corresponding to terminal related factors that
application quality and are useful to provide better end-user quality affect real-time application quality and are useful to provide better
of experience (QoE). end-user quality of experience (QoE) when these terminal-related
factors are used as inputs to calculate QoE metrics [QMB].
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 Operation 3. Jitter Buffer Operation
skipping to change at page 5, line 31 skipping to change at page 5, line 31
aligned with the delay corresponding to the earliest arriving packet aligned with the delay corresponding to the earliest arriving packet
and late edge representing the maximum permissible delay before a and late edge representing the maximum permissible delay before a
late arriving packet would be discarded. The delay applied to late arriving packet would be discarded. The delay applied to
packets that arrive on time or at their expected arrival time is packets that arrive on time or at their expected arrival time is
known as the Nominal Delay and this is equivalent to the time known as the Nominal Delay and this is equivalent to the time
difference/ buffer size difference between the on-time packets difference/ buffer size difference between the on-time packets
insertion point and the point at which packets are read out. insertion point and the point at which packets are read out.
The reference for the expected arrival time may, for example, be the The reference for the expected arrival time may, for example, be the
first packet in the session or the running average delay. If all first packet in the session or the running average delay. If all
packets arrived at their expected arrival time then then every packet packets arrived at their expected arrival time, then every packet
would be held in the jitter buffer exactly the Nominal Delay. would be held in the jitter buffer exactly the Nominal Delay.
The Jitter Buffer maximum delay is the delay that is applied to an The Jitter Buffer maximum delay is the delay that is applied to an
earliest arriving packet that is not discarded and corresponds to the earliest arriving packet that is not discarded and corresponds to the
early edge of the jitter buffer time window. early edge of the jitter buffer time window.
3.1. Idealized Jitter Buffer 3.1. Idealized Jitter Buffer
In practice jitter buffer implementations vary considerably however In practice jitter buffer implementations vary considerably however
should behave in a manner conceptually consistent with an idealized they should behave in a manner conceptually consistent with an
jitter buffer described as follows: idealized jitter buffer described as follows:
(i). Receive the first packet and delay playout by D ms. Keep (i). Receive the first packet and delay playout by D ms. Keep
the RTP timestamp and receive time as a reference. the RTP timestamp and receive time as a reference.
RTP TS[1] RTP TS[1]
receive time[1] receive time[1]
Assume that both are normalized in ticks. Assume that both are normalized in ticks.
(ii). Receive the next packet (ii). Receive the next packet
(iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive (iii). Calculate r = RTP TS[n] - RTP TS[1] and t = receive
time[n] - receive time[1]. If r = t then the packet arrived on time[n] - receive time[1]. If r = t then the packet arrived on
time. If r < t then the packet arrived late and if r > t then the time. If r < t then the packet arrived late and if r > t then the
packet arrived early. packet arrived early.
(iv). Delay playout of packet by D + (r -t) (iv). Delay playout of packet by D + (r-t)
(v). Go back to (ii) (v). Go back to (ii)
Note that this idealized implementation assumes that the sender's RTP Note that this idealized implementation assumes that the sender's RTP
clock is synchronized to the clock in the receiver which is used to clock is synchronized to the clock in the receiver which is used to
timestamp packet arrivals. If there is no such inherent timestamp packet arrivals. If there is no such inherent
synchronization, the system may need to use an adaptive jitter buffer synchronization, the system may need to use an adaptive jitter buffer
or other techniques to ensure reliable reception. or other techniques to ensure reliable reception.
3.2. Fixed Jitter Buffer 3.2. Fixed Jitter Buffer
skipping to change at page 7, line 9 skipping to change at page 7, line 9
delay and has variable size or variable delay. It allows the nominal delay and has variable size or variable delay. It allows the nominal
delay to be set to a low value initially, to minimize user perceived delay to be set to a low value initially, to minimize user perceived
delay, however can automatically extend the late edge (and possibly delay, however can automatically extend the late edge (and possibly
also retract the early edge) of buffer window if a significant also retract the early edge) of buffer window if a significant
proportion of packets are arriving late (and hence being discarded). proportion of packets are arriving late (and hence being discarded).
4. Jitter Buffer Metrics Block 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 MUST be sent
sent in the same compound RTCP packet as the measurement information 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 MUST
be discarded. be discarded.
4.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 |
skipping to change at page 8, line 15 skipping to change at page 8, line 15
I=01: Sampled Value - the reported value is a sampled I=01: Sampled Value - the reported value is a sampled
instantaneous value. 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.
In this document, Jitter Buffer Metrics can only be sampled , and
cannot be measured over definite intervals. Also, the value I=00
is reserved for future use. Senders MUST NOT use the values I=00
or I=10 or I=11. If a block is received with I=00 or I=10 or
I=11, the receiver MUST discard the block.
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
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, 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
skipping to change at page 8, line 44 skipping to change at page 9, line 5
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 time
spend in the jitter buffer for the packet that arrives exactly on spend in the jitter buffer for the packet that arrives exactly on
time. This parameter MUST be provided for both fixed and adaptive time. This parameter MUST be provided for both fixed and adaptive
jitter buffer implementations. jitter buffer implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
measurement is unavailable, the value 0xFFFF MUST be reported. over-range measurement. If the 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 time spent in the be discarded. It is calculated based on the time spent in the
jitter buffer for the earliest arriving packet In simple queue jitter buffer for the earliest arriving packet In simple queue
implementations this may correspond to the size of the jitter implementations this may correspond to the size of the jitter
buffer. In adaptive jitter buffer implementations, this value may buffer. In adaptive jitter buffer implementations, this value may
vary dynamically. This parameter MUST be provided for both fixed vary dynamically. This parameter MUST be provided for both fixed
and adaptive jitter buffer implementations. and adaptive jitter buffer implementations.
If the measured value exceeds 0xFFFD, the value 0xFFFE MUST be The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
measurement is unavailable, the value 0xFFFF MUST be reported. over-range measurement. If the 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
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 The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
measurement is unavailable, the value 0xFFFF MUST be reported. over-range measurement. If the 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. 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 The measured value is unsigned value. If the measured value
reported to indicate an over-range measurement. If the exceeds 0xFFFD, the value 0xFFFE MUST be reported to indicate an
measurement is unavailable, the value 0xFFFF MUST be reported. over-range measurement. If the measurement is unavailable, the
value 0xFFFF MUST be reported.
5. 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).
5.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-buffer"
5.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 [RFC3264], the SDP Offer/
defined in [RFC3611] for unilateral "rtcp-xr" attribute parameters Answer usage defined in [RFC3611] for unilateral "rtcp-xr" attribute
applies. For detailed usage of Offer/Answer for unilateral parameters applies. For detailed usage of Offer/Answer for
parameter, refer to section 5.2 of [RFC3611]. unilateral parameter, refer to section 5.2 of [RFC3611].
6. 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].
6.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.]
6.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-buffer" in the
"RTCP XR SDP Parameters Registry". "RTCP XR SDP Parameters Registry".
6.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
skipping to change at page 15, line 12 skipping to change at page 16, line 12
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.
10. References 10. References
10.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.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with the Session Description Protocol (SDP)", RFC 3264,
June 2002.
[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
Considerations for Protocol Extensions", RFC 6709,
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.
10.2. Informative References 10.2. Informative References
[QMB] Clark, A., "RTP Control Protocol (RTCP) Extended Report
(XR) Blocks for QoE Metric Reporting",
ID draft-ietf-xrblock-rtcp-xr-qoe-06, February 2013.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
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.
[RFC6709] Carpenter, B., Aboba, B., and S. Cheshire, "Design
Considerations for Protocol Extensions", RFC 6709,
September 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. Metrics represented using RFC6390 Template Appendix A. Metrics represented using RFC6390 Template
RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC RFC EDITOR NOTE: please change XXXX in [RFCXXXX] by the new RFC
number, when assigned. number, when assigned.
a. jitter buffer nominal delay Metric a. jitter buffer nominal delay Metric
* Metric Name: jitter buffer nominal delay * Metric Name: jitter buffer nominal delay in RTP
* Metric Description: The "expected arrival time" is the time * Metric Description: The "expected arrival time" is the time
that a RTP packet would arrive if there was no delay that a RTP packet would arrive if there was no delay
variation. The delay applied to packets that arrive at their variation. The delay applied to packets that arrive at their
expected time is known as the Nominal Delay. expected time is known as the Nominal Delay.
* Method of Measurement or Calculation: See section 4.2, jitter * Method of Measurement or Calculation: See section 4.2, jitter
buffer nominal delay definition [RFCXXXX]. buffer nominal delay definition [RFCXXXX].
* Units of Measurement: See section 4.2, jitter buffer nominal * Units of Measurement: See section 4.2, jitter buffer nominal
skipping to change at page 16, line 38 skipping to change at page 17, line 38
* Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for
measurement timing and section 4.2 paragraph [RFCXXXX] for measurement timing and section 4.2 paragraph [RFCXXXX] for
Interval Metric flag. Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
b. jitter buffer maximum delay Metric b. jitter buffer maximum delay Metric
* Metric Name: jitter buffer maximum delay * Metric Name: jitter buffer maximum delay in RTP
* Metric Description: It is the current maximum jitter buffer * Metric Description: It is the current maximum jitter buffer
delay for RTP traffic which corresponds to the earliest delay for RTP traffic which corresponds to the earliest
arriving packet that would not be discarded. arriving packet that would not be discarded.
* Method of Measurement or Calculation: See section 4.2, jitter * Method of Measurement or Calculation: See section 4.2, jitter
buffer maximum delay definition and section 3, the last buffer maximum delay definition and section 3, the last
paragraph [RFCXXXX]. paragraph [RFCXXXX].
* Units of Measurement: See section 4.2, jitter buffer maximum * Units of Measurement: See section 4.2, jitter buffer maximum
skipping to change at page 17, line 26 skipping to change at page 18, line 26
* Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for
measurement timing and section 4.2 paragraph [RFCXXXX] for measurement timing and section 4.2 paragraph [RFCXXXX] for
Interval Metric flag. Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
c. jitter buffer high water mark Metric c. jitter buffer high water mark Metric
* Metric Name: jitter buffer high water mark * Metric Name: jitter buffer high water mark in RTP
* Metric Description: It is the highest value of the jitter * Metric Description: It is the highest value of the jitter
buffer nominal delay for RTP traffic which occurred at any buffer nominal delay for RTP traffic which occurred at any
time during the reporting interval. time during the reporting interval.
* Method of Measurement or Calculation: See section 4.2, jitter * Method of Measurement or Calculation: See section 4.2, jitter
buffer high water mark definition [RFCXXXX]. buffer high water mark definition [RFCXXXX].
* Units of Measurement: See section 4.2, jitter buffer nominal * Units of Measurement: See section 4.2, jitter buffer nominal
delay definition [RFCXXXX]. delay definition [RFCXXXX].
skipping to change at page 18, line 15 skipping to change at page 19, line 15
* Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for * Measurement Timing: See section 4, 1st paragraph [RFCXXXX] for
measurement timing and section 4.2 paragraph [RFCXXXX] for measurement timing and section 4.2 paragraph [RFCXXXX] for
Interval Metric flag. Interval Metric flag.
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
d. jitter buffer low water mark Metric d. jitter buffer low water mark Metric
* Metric Name: jitter buffer low water mark * Metric Name: jitter buffer low water mark in RTP
* Metric Description: It is the lowest value of the jitter * Metric Description: It is the lowest value of the jitter
buffer nominal delay for RTP traffic which occurred at any buffer nominal delay for RTP traffic which occurred at any
time during the reporting interval. time during the reporting interval.
* Method of Measurement or Calculation: See section 4.2, jitter * Method of Measurement or Calculation: See section 4.2, jitter
buffer low water mark definition [RFCXXXX]. buffer low water mark definition [RFCXXXX].
* Units of Measurement: See section 4.2, jitter buffer low water * Units of Measurement: See section 4.2, jitter buffer low water
mark definition [RFCXXXX]. mark definition [RFCXXXX].
skipping to change at page 19, line 10 skipping to change at page 20, line 10
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
Appendix B. Change Log Appendix B. 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.
B.1. draft-ietf-xrblock-rtcp-xr-jb-10 B.1. draft-ietf-xrblock-rtcp-xr-jb-11
The following are the major changes to previous version :
o Comments in WGLC and from PM-DIR review are addressed in this
version.
B.2. draft-ietf-xrblock-rtcp-xr-jb-10
The following are the major changes to previous version : The following are the major changes to previous version :
o Add some text to section 3.2 to clarify how fixed jitter buffer is o Add some text to section 3.2 to clarify how fixed jitter buffer is
used. used.
o Other Editorial changes. o Other Editorial changes.
B.2. draft-ietf-xrblock-rtcp-xr-jb-09 B.3. draft-ietf-xrblock-rtcp-xr-jb-09
The following are the major changes to previous version : The following are the major changes to previous version :
o Incorporate proposed changes by Kevin and proposed text by Alan to o Incorporate proposed changes by Kevin and proposed text by Alan to
address interoperability report issue. address interoperability report issue.
o Add new appendix to format metrics using RFC6390 template. o Add new appendix to format metrics using RFC6390 template.
B.3. draft-ietf-xrblock-rtcp-xr-jb-08 B.4. draft-ietf-xrblock-rtcp-xr-jb-08
The following are the major changes to previous version : The following are the major changes to previous version :
o Rewrote descriptive text and definitions for clarification. o Rewrote descriptive text and definitions for clarification.
B.4. draft-ietf-xrblock-rtcp-xr-jb-07 B.5. draft-ietf-xrblock-rtcp-xr-jb-07
The following are the major changes to previous version : The following are the major changes to previous version :
o Add one new section to discuss jitter buffer operation. o Add one new section to discuss jitter buffer operation.
B.5. draft-ietf-xrblock-rtcp-xr-jb-05 B.6. 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.
B.6. draft-ietf-xrblock-rtcp-xr-jb-03 B.7. 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.
B.7. draft-ietf-xrblock-rtcp-xr-jb-02 B.8. 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.
B.8. draft-ietf-xrblock-rtcp-xr-jb-01 B.9. 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.
B.9. draft-ietf-xrblock-rtcp-xr-jb-00 B.10. 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. 40 change blocks. 
85 lines changed or deleted 115 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/