draft-ietf-xrblock-rtcp-xr-pdv-05.txt   draft-ietf-xrblock-rtcp-xr-pdv-06.txt 
Audio/Video Transport Working Group A. Clark Audio/Video Transport Working Group A. Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Intended status: Standards Track Q. Wu Intended status: Standards Track Q. Wu
Expires: March 3, 2013 Huawei Expires: March 18, 2013 Huawei
August 30, 2012 September 14, 2012
RTCP XR Report Block for Packet Delay Variation Metric Reporting RTCP XR Report Block for Packet Delay Variation Metric Reporting
draft-ietf-xrblock-rtcp-xr-pdv-05.txt draft-ietf-xrblock-rtcp-xr-pdv-06.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines a Real-Time Control Protocol (RTCP) Extended
reporting of Packet Delay Variation metrics for a range of RTP Report (XR) block that allows the reporting of Packet Delay Variation
metrics for a range of Real-time Transport Protocol (RTP)
applications. 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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 3, 2013. This Internet-Draft will expire on March 18, 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 18 skipping to change at page 2, line 18
1.1. Packet Delay Variation Metrics Block . . . . . . . . . . . 3 1.1. Packet Delay Variation 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
2.2. Notations . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Notations . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Packet Delay Variation Metrics Block . . . . . . . . . . . . . 5 3. Packet Delay Variation Metrics Block . . . . . . . . . . . . . 5
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5
3.2. Definition of Fields in PDV Metrics Block . . . . . . . . 5 3.2. Definition of Fields in PDV Metrics Block . . . . . . . . 5
3.3. Guidance on use of PDV metrics . . . . . . . . . . . . . . 8 3.3. Guidance on use of PDV metrics . . . . . . . . . . . . . . 9
3.4. Examples of use . . . . . . . . . . . . . . . . . . . . . 9 3.4. Examples of use . . . . . . . . . . . . . . . . . . . . . 9
4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11 4. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 12 5.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 12
5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12 5.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 12
5.3. Contact information for registrations . . . . . . . . . . 12 5.3. Contact information for registrations . . . . . . . . . . 12
5.4. New registry of PDV types . . . . . . . . . . . . . . . . 12 5.4. New registry of PDV types . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 18 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 19
A.1. draft-ietf-xrblock-rtcp-xr-pdv-05 . . . . . . . . . . . . 18 A.1. draft-ietf-xrblock-rtcp-xr-pdv-06 . . . . . . . . . . . . 19
A.2. draft-ietf-xrblock-rtcp-xr-pdv-04 . . . . . . . . . . . . 18 A.2. draft-ietf-xrblock-rtcp-xr-pdv-05 . . . . . . . . . . . . 19
A.3. draft-ietf-xrblock-rtcp-xr-pdv-03 . . . . . . . . . . . . 18 A.3. draft-ietf-xrblock-rtcp-xr-pdv-04 . . . . . . . . . . . . 19
A.4. draft-ietf-xrblock-rtcp-xr-pdv-02 . . . . . . . . . . . . 18 A.4. draft-ietf-xrblock-rtcp-xr-pdv-03 . . . . . . . . . . . . 19
A.5. draft-ietf-xrblock-rtcp-xr-pdv-01 . . . . . . . . . . . . 18 A.5. draft-ietf-xrblock-rtcp-xr-pdv-02 . . . . . . . . . . . . 20
A.6. draft-ietf-xrblock-rtcp-xr-pdv-00 . . . . . . . . . . . . 19 A.6. draft-ietf-xrblock-rtcp-xr-pdv-01 . . . . . . . . . . . . 20
A.7. draft-ietf-avt-rtcp-xr-pdv-03 . . . . . . . . . . . . . . 19 A.7. draft-ietf-xrblock-rtcp-xr-pdv-00 . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 A.8. draft-ietf-avt-rtcp-xr-pdv-03 . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
1.1. Packet Delay Variation Metrics Block 1.1. Packet Delay Variation Metrics Block
This draft defines a new block type to augment those defined in This draft defines a new block type to augment those defined in
[RFC3611], for use in a range of RTP applications. [RFC3611], for use in a range of RTP applications.
The new block type provides information on Packet Delay Variation The new block type provides information on Packet Delay Variation
using one of several standard metrics. (PDV) using one of several standard metrics,, for example, Mean
Absolute Packet Delay Variation 2 (MAPDV2) (Clause 6.2.3.2 of
[G.1020]), or 2-point PDV (Clause 6.2.4 of [Y.1540]).
The metrics belong to the class of transport metrics defined in The metrics belong to the class of transport metrics defined in
[MONARCH] . [MONARCH].
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 defined an extensible structure for reporting using an RTCP Extended
Report (XR). This draft defines a new Extended Report block that Report (XR). This draft defines a new Extended Report block for use
must be used in accordance with [RFC3550] and [RFC3611]. 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 [MONARCH] provides guideline for reporting Monitoring Architectures [MONARCH] provides guideline for reporting
block format using RTCP XR. The XR Block described in this document block format using RTCP XR. The XR Block described in this document
are in accordance with the guidelines in [RFC6390] and [MONARCH]. are in accordance with the guidelines in [RFC6390] and [MONARCH].
1.4. Applicability 1.4. Applicability
These metrics are applicable to a wide range of RTP applications in These metrics are applicable to a wide range of RTP applications in
which the application streams are sensitive to delay variation which the application streams are sensitive to delay variation.
[RFC5481]. Application designers can know the range of delay variation they must
accommodate, whether they are designing fixed or adaptive buffer
systems. Network manager also can constrain delay variation to
ensure the quality of real-time applications, and monitor this metric
(possibly to compare with a numerical objective or Service Level
Agreement) [RFC5481].
2. Terminology 2. Terminology
This document uses ABNF from [RFC5234] as a terminology statement.
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].
2.2. Notations 2.2. Notations
This report block makes use of binary fractions. The terminology This report block makes use of binary fractions. The terminology
used is used is
skipping to change at page 5, line 8 skipping to change at page 5, line 8
though note that use of flag values at the top of the numeric though note that use of flag values at the top of the numeric
range slightly reduces this upper limit. For example, if the range slightly reduces this upper limit. For example, if the
16- bit values 0xfffe and 0xffff are used as flags for "over- 16- bit values 0xfffe and 0xffff are used as flags for "over-
range" and "unavailable" conditions, a 0:16 quantity has range range" and "unavailable" conditions, a 0:16 quantity has range
0.0 to 1 - 3/65536 = 0.9999542 0.0 to 1 - 3/65536 = 0.9999542
3. Packet Delay Variation Metrics Block 3. Packet Delay Variation Metrics Block
Metrics in this block report on packet delay variation in the stream Metrics in this block report on packet delay variation in the stream
arriving at the RTP system. Instances of this Metrics Block refer by arriving at the RTP system. The measurement of these metrics are
Synchronization source (SSRC) to the separate auxiliary Measurement made at the receiving end of the RTP stream. Instances of this
Information block [MEASI] which contains measurement intervals. This Metrics Block refer by Synchronization source (SSRC) to the separate
metric block relies on the measurement interval in the Measurement auxiliary Measurement Information block [MEASI] which contains
Information block indicating the span of the report and SHOULD be measurement intervals. This metric block relies on the measurement
sent in the same compound RTCP packet as the measurement information interval in the Measurement Information block indicating the span of
block. If the measurement interval is not received for this metric the report and SHOULD be sent in the same compound RTCP packet as the
block, this metric block SHOULD be discarded. measurement information block. If the measurement interval is not
received for this metric block, this metric block MUST be discarded (
See timing details in section 5.4 of[MONARCH]).
3.1. Report Block Structure 3.1. Report Block Structure
PDV metrics block PDV metrics block
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NPDV | I |pdvtyp |Rsv| block length=3 | | BT=NPDV | I |pdvtyp |Rsv| block length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Pos PDV Threshold/Peak | Pos PDV Percentile | | Pos PDV Threshold/Peak | Pos PDV Percentile |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neg PDV Threshold/Peak | Neg PDV Percentile | | Neg PDV Threshold/Peak | Neg PDV Percentile |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mean PDV | unused | | Mean PDV | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in PDV Metrics Block 3.2. Definition of Fields in PDV Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Packet Delay Variation Metrics Report Block is identified by the A Packet Delay Variation Metrics Report Block is identified by the
constant NPDV. constant NPDV.
[Note to RFC Editor: please replace NPDV with the IANA provided [Note to RFC Editor: please replace NPDV with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 2 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Packet Delay variation This field is used to indicate whether the Packet Delay variation
metrics are Sampled, Interval or Cumulative metrics, that is, metrics are Sampled, Interval or Cumulative metrics [MONARCH],
whether the reported values applies to the most recent measurement that is, whether the reported values applies to the most recent
interval duration between successive metrics reports (I=10) (the measurement interval duration between successive metrics reports
Interval Duration) or to the accumulation period characteristic of (I=10) (the Interval Duration) or to the accumulation period
cumulative measurements (I=11) (the Cumulative Duration) or is a characteristic of cumulative measurements (I=11) (the Cumulative
sampled instantaneous value (I=01) (Sampled Value). Duration) or is a sampled instantaneous value (I=01) (Sampled
Value). The value I=00 is reserved, and MUST NOT be used. If the
value I=00 is received, it MUST be ignored by the receiver.
Packet Delay Variation Metric Type (pdvtyp): 4 bits Packet Delay Variation Metric Type (pdvtyp): 4 bits
Packet Delay Variation Metric Type is of type enumerated and Packet Delay Variation Metric Type is of type enumerated and is
should be interpreted as Integer. This field is used to identify interpreted as Integer. This field is used to identify the Packet
the Packet Delay Variation Metric Type used in this report block, Delay Variation Metric Type used in this report block, according
according to the following code: to the following code:
bits 014-011 bits 014-011
0: MAPDV2, Clause 6.2.3.2 of [G.1020], 0: MAPDV2, Clause 6.2.3.2 of [G.1020],
1: 2-point PDV, Clause 6.2.4 of [Y.1540]. 1: 2-point PDV, Clause 6.2.4 of [Y.1540].
Rsv.: 2 bits Rsv.: 2 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field SHOULD be set to zero such a definition, the bits in this field MUST be set to zero and
and MUST be ignored by the receiver. ignored by the receiver.
Block Length: 16 bits Block Length: 16 bits
The length of this report block in 32-bit words, minus one. For The length of this report block in 32-bit words, minus one. For
the Packet Delay Variation Metrics block, the block length is the Packet Delay Variation Metrics block, the block length is
equal to 4. equal to 4.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of [RFC3611].
skipping to change at page 8, line 38 skipping to change at page 8, line 46
If the measured value is more negative than -2047.9375 (the value If the measured value is more negative than -2047.9375 (the value
which would be coded as 0x8001), the value 0x8000 SHOULD be which would be coded as 0x8001), the value 0x8000 SHOULD be
reported to indicate an over-range negative measurement. If the reported to indicate an over-range negative measurement. If the
measured value is more positive than +2047.8125 (the value which measured value is more positive than +2047.8125 (the value which
would be coded as 0x7FFD), the value 0x7FFE SHOULD be reported to would be coded as 0x7FFD), the value 0x7FFE SHOULD be reported to
indicate an over-range positive measurement. If the measurement indicate an over-range positive measurement. If the measurement
is unavailable, the value 0x7FFF MUST be reported. is unavailable, the value 0x7FFF MUST be reported.
Reserved: 16 bits Reserved: 16 bits
These bits are reserved for future definition. They SHOULD be set These bits are reserved for future definition. They MUST be set
to zero by the sender and MUST be ignored by the receiver. to zero by the sender and ignored by the receiver.
3.3. Guidance on use of PDV metrics 3.3. Guidance on use of PDV metrics
This subsection provides informative guidance on when it might be This subsection provides informative guidance on when it might be
appropriate to use each of the PDV metric types. appropriate to use each of the PDV metric types.
MAPDV2 (Clause 6.2.3.2 of [G.1020]) is the envelope of instantaneous MAPDV2 (Clause 6.2.3.2 of [G.1020]) is the envelope of instantaneous
(per-packet) delay when compared to the short term moving average (per-packet) delay when compared to the short term moving average
delay. This metric could be useful in determining residual delay. This metric could be useful in determining residual
impairment when an RTP end system uses an adaptive de-jitter buffer impairment when an RTP end system uses an adaptive de-jitter buffer
skipping to change at page 11, line 15 skipping to change at page 11, line 15
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. XR blocks MAY be used
without prior signaling. without prior signaling.
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.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in [RFC3611])
xr-format =/ xr-pdv-block xr-format =/ xr-pdv-block
xr-pdv-block = "pkt-dly-var" [ "," pdvtype ] [ "," nspec "," pspec ] xr-pdv-block = "pkt-dly-var" [ "," pdvtype ] [ "," nspec "," pspec ]
pdvtype = "pdv=" "0" ; MAPDV2 ITU-T G.1020 pdvtype = "pdv=" ( "0" ; MAPDV2 ITU-T G.1020
/ "1" ; 2-point PDV ITU-T Y.1540 / "1" ; 2-point PDV ITU-T Y.1540
/ 1*2DIGIT ;Value 2~15 are valid and / 1*2DIGIT ) ;Value 2~15 are valid and
;reserved for future use ;reserved for future use
nspec = "nthr=" fixpoint ; negative PDV threshold (ms) nspec = ("nthr=" fixpoint) ; negative PDV threshold (ms)
/ "npc=" fixpoint ; negative PDV percentile / ("npc=" fixpoint ) ; negative PDV percentile
pspec = "pthr=" fixpoint ; positive PDV threshold (ms) pspec = ("pthr=" fixpoint) ; positive PDV threshold (ms)
/ "ppc=" fixpoint ; positive PDV percentile / ("ppc=" fixpoint) ; positive PDV percentile
fixpoint = 1*DIGIT "." 1*DIGIT ; fixed point decimal fixpoint = 1*DIGIT "." 1*DIGIT ; fixed point decimal
DIGIT = %x30-39 DIGIT = <as defined in Section 3.4 of [RFC5234]>
When SDP is used in offer-answer, a system sending SDP may request a When SDP is used in offer-answer, a system sending SDP may request a
specific type of PDV measurement. In addition, they may state a specific type of PDV measurement. In addition, they may state a
specific percentile or threshold value, and expect to receive the specific percentile or threshold value, and expect to receive the
corresponding threshold or percentile metric, respectively. The corresponding threshold or percentile metric, respectively. The
system receiving the SDP SHOULD send the PDV metrics requested, but system receiving the SDP SHOULD send the PDV metrics requested, but
if the metric is not available, the system receiving the SDP MUST if the metric is not available, the system receiving the SDP MUST
send the metric block with the flag value indicating that the metric send the metric block with the flag value indicating that the metric
is unavailable. is unavailable.
skipping to change at page 16, line 14 skipping to change at page 16, line 14
8. Acknowledgments 8. Acknowledgments
The authors gratefully acknowledge the comments and contributions The authors gratefully acknowledge the comments and contributions
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho,
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Jing Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada,Jing
Zhao,Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn,Shida Zhao,Kevin Gross, Colin Perkins, Charles Eckel, Glen Zorn,Shida
Schubert. Schubert, Benoit Claise, Adrian Farrel, Pete Resnick.
9. References 9. References
9.1. Normative References 9.1. Normative References
[G.1020] ITU-T, "ITU-T Rec. G.1020, Performance parameter [G.1020] ITU-T, "ITU-T Rec. G.1020, Performance parameter
definitions for quality of speech and other voiceband definitions for quality of speech and other voiceband
applications utilizing IP networks", July 2006. applications utilizing IP networks", July 2006.
[MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-06,
April 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time
Applications", RFC 3550, July 2003. Applications", RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", November 2003. Protocol Extended Reports (RTCP XR)", November 2003.
[RFC4040] Kreuter, R., "RTP Payload Format for a 64 kbit/s [RFC4040] Kreuter, R., "RTP Payload Format for a 64 kbit/s
Transparent Call", April 2005. Transparent Call", April 2005.
[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.
[RFC5226] Narten, T., "Guidelines for Writing an IANA Considerations [RFC5226] Narten, T., "Guidelines for Writing an IANA Considerations
Section in RFCs", May 2008. Section in RFCs", May 2008.
BCP 26 BCP 26
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", January 2008.
[Y.1540] ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and [Y.1540] ITU-T, "ITU-T Rec. Y.1540, IP packet transfer and
availability performance parameters", November 2007. availability performance parameters", November 2007.
9.2. Informative References 9.2. Informative References
[MEASI] Hunt, G., "Measurement Identity and information Reporting
using SDES item and XR Block",
ID draft-ietf-xrblock-rtcp-xr-meas-identity-06,
April 2012.
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [MONARCH] Hunt, G., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-13, May 2012. ID draft-ietf-avtcore-monarch-13, May 2012.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
Applicability Statement", RFC 5481, March 2009. Applicability Statement", RFC 5481, March 2009.
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric [RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric
Development", RFC 6390, October 2011. Development", RFC 6390, October 2011.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-pdv-05 A.1. draft-ietf-xrblock-rtcp-xr-pdv-06
The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-05:
o Editorial change based on IESG Review.
o SDP element update based on pete's suggestion.
o Clarify the value of PDV in the applicability section.
o Clarify measurement point and timing in section 3.
A.2. draft-ietf-xrblock-rtcp-xr-pdv-05
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-04: draft-ietf-xrblock-rtcp-xr-pdv-04:
o Move Geoff Hunt from author list to Contributors section based on o Move Geoff Hunt from author list to Contributors section based on
his suggestion. his suggestion.
A.2. draft-ietf-xrblock-rtcp-xr-pdv-04 A.3. draft-ietf-xrblock-rtcp-xr-pdv-04
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-03: draft-ietf-xrblock-rtcp-xr-pdv-03:
o Editorial changes based on Gen-Art Review and Secdir Review. o Editorial changes based on Gen-Art Review and Secdir Review.
A.3. draft-ietf-xrblock-rtcp-xr-pdv-03 A.4. draft-ietf-xrblock-rtcp-xr-pdv-03
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-02: draft-ietf-xrblock-rtcp-xr-pdv-02:
o Make definition of pdvtype get alignment with IANA section. o Make definition of pdvtype get alignment with IANA section.
o Make Guidance on use of PDV metrics get alignment with RFC5481. o Make Guidance on use of PDV metrics get alignment with RFC5481.
o Other Editorial changes. o Other Editorial changes.
A.4. draft-ietf-xrblock-rtcp-xr-pdv-02 A.5. draft-ietf-xrblock-rtcp-xr-pdv-02
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-01: draft-ietf-xrblock-rtcp-xr-pdv-01:
o Updated references. o Updated references.
o Allocate one more bit for Interval metric flag to indicate sampled o Allocate one more bit for Interval metric flag to indicate sampled
metric can be used. metric can be used.
o Add a few clarification text for failure mode. o Add a few clarification text for failure mode.
A.5. draft-ietf-xrblock-rtcp-xr-pdv-01 A.6. draft-ietf-xrblock-rtcp-xr-pdv-01
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-xrblock-rtcp-xr-pdv-00: draft-ietf-xrblock-rtcp-xr-pdv-00:
o Fix typos or nits in the definition of Negative PDV Threshold/ o Fix typos or nits in the definition of Negative PDV Threshold/
Peak. Peak.
o Fix nits in Numeric format S7:8. o Fix nits in Numeric format S7:8.
o remove the text that is relevant to tag field. o remove the text that is relevant to tag field.
o Add text in SDP signaling section to clarify indicationof metric o Add text in SDP signaling section to clarify indicationof metric
unavailable. unavailable.
A.6. draft-ietf-xrblock-rtcp-xr-pdv-00 A.7. draft-ietf-xrblock-rtcp-xr-pdv-00
The following are the major changes to previous version The following are the major changes to previous version
draft-ietf-avt-rtcp-xr-pdv-03: draft-ietf-avt-rtcp-xr-pdv-03:
o Updated references. o Updated references.
A.7. draft-ietf-avt-rtcp-xr-pdv-03 A.8. draft-ietf-avt-rtcp-xr-pdv-03
The following are the major changes to previous version : The following are the major changes to previous version :
o Changed BNF for SDP following Christian Groves' and Tom Taylor's o Changed BNF for SDP following Christian Groves' and Tom Taylor's
comments (4th and 5th May 2009). comments (4th and 5th May 2009).
o Updated references. o Updated references.
Authors' Addresses Authors' Addresses
 End of changes. 32 change blocks. 
72 lines changed or deleted 99 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/