draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01.txt   draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt 
Audio/Video Transport Working Group G. Hunt Audio/Video Transport Working Group G. Hunt
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: July 22, 2012 Telchemy Expires: July 23, 2012 Telchemy
R. Huang R. Huang
Q. Wu, Ed. Q. Wu, Ed.
Huawei Huawei
January 19, 2012 January 20, 2012
RTCP XR Report Block for Burst/Gap Discard metric Reporting RTCP XR Report Block for Burst/Gap Discard metric Reporting
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-01.txt draft-ietf-xrblock-rtcp-xr-burst-gap-discard-02.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of Burst and Gap Discard metrics for use in a range of RTP reporting of Burst and Gap Discard metrics for use in a range of 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
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 22, 2012. This Internet-Draft will expire on July 23, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Burst and Gap Discard Report Block . . . . . . . . . . . . 3 1.1. Burst and Gap Discard Report 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 . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 5
3. Burst/Gap Discard Block . . . . . . . . . . . . . . . . . . . 6 3. Burst/Gap Discard Block . . . . . . . . . . . . . . . . . . . 6
3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6 3.1. Report Block Structure . . . . . . . . . . . . . . . . . . 6
3.2. Definition of Fields in Burst/Gap Loss Report Block . . . 6 3.2. Definition of Fields in Burst/Gap Loss Report Block . . . 6
3.3. Derived metrics based on reported metrics . . . . . . . . 7 3.3. Derived metrics based on reported metrics . . . . . . . . 8
4. Considerations for Voice-over-IP applications . . . . . . . . 9 4. Considerations for Voice-over-IP applications . . . . . . . . 9
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 11 6.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 11
6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 11 6.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 11
6.3. Contact information for registrations . . . . . . . . . . 11 6.3. Contact information for registrations . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Changes from previous version . . . . . . . . . . . . . . . . 14 9. Changes from previous version . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 6, line 17 skipping to change at page 6, line 17
Metrics in this block report on Burst/Gap Discard in the stream Metrics in this block report on Burst/Gap Discard in the stream
arriving at the RTP system. arriving at the RTP system.
3.1. Report Block Structure 3.1. Report Block Structure
Burst/Gap Discard metrics block Burst/Gap Discard 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=NBGD |I| resv. | block length = 2 | | BT=NBGD |I| resv. | block length = 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Packets Discarded in Bursts | Total... | | Threshold | Packets Discarded in Bursts |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Packets expected in bursts | Reserved. | | Total Packets expected in bursts | Reserved. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Burst/Gap Loss Report Block 3.2. Definition of Fields in Burst/Gap Loss Report Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Burst/Gap Discard Report Block is identified by the constant A Burst/Gap Discard Report Block is identified by the constant
NBGD. NBGD.
skipping to change at page 7, line 13 skipping to change at page 7, line 8
cumulative measurements (I=0) (the Cumulative Duration). cumulative measurements (I=0) (the Cumulative Duration).
Reserved (resv): 7 bits Reserved (resv): 7 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
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 Delay block, the block length is equal to 2. the Delay block, the block length is equal to 3.
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].
Threshold: 8 bits
The Threshold is equivalent to Gmin in [RFC3611], i.e. the number
of successive packets that must be received prior to and following
a lost packet in order for this lost packet to be regarded as part
of a gap.
Packets lost in bursts: 24 bits Packets lost in bursts: 24 bits
The total number of packets lost during loss bursts. The total number of packets lost during loss bursts.
If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE SHOULD If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE SHOULD
be reported to indicate an over-range measurement. If the be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFFFF SHOULD be reported.
Total packets expected in bursts: 24 bits Total packets expected in bursts: 24 bits
The total number of packets expected during loss bursts (that is, The total number of packets expected during loss bursts (that is,
the sum of received packets and lost packets). the sum of received packets and lost packets).
If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE SHOULD If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE SHOULD
be reported to indicate an over-range measurement. If the be reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFFFF SHOULD be reported.
Reserved (resv): 16 bits Reserved (resv): 8 bits
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
3.3. Derived metrics based on reported metrics 3.3. Derived metrics based on reported metrics
The metrics described here are intended to be used as described in The metrics described here are intended to be used as described in
this section, in conjunction with information from the Measurement this section, in conjunction with information from the Measurement
Information block [MEASID], discard block [DISCARD] (which MUST be Information block [MEASID], discard block [DISCARD] (which MUST be
present in the same RTCP packet as the Burst/Gap Discard block). present in the same RTCP packet as the Burst/Gap Discard block).
 End of changes. 11 change blocks. 
10 lines changed or deleted 17 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/