draft-ietf-xrblock-rtcp-xr-discard-01.txt   draft-ietf-xrblock-rtcp-xr-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: June 11, 2012 Telchemy Expires: October 20, 2012 Telchemy
G. Zorn G. Zorn
Network Zen Network Zen
Q. Wu Q. Wu
Huawei Huawei
December 9, 2011 April 18, 2012
RTCP XR Report Block for Discard metric Reporting RTCP XR Report Block for Discard metric Reporting
draft-ietf-xrblock-rtcp-xr-discard-01.txt draft-ietf-xrblock-rtcp-xr-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 a simple discard count metric for use in a range of RTP reporting of a simple discard count metric 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 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 11, 2012. This Internet-Draft will expire on October 20, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 5, line 12 skipping to change at page 5, line 12
defined in [RFC5725] is available to report on packets which are defined in [RFC5725] is available to report on packets which are
not recovered by any repair techniques which may be in use. not recovered by any repair techniques which may be in use.
3. Discard Metric Report Block 3. Discard Metric Report Block
3.1. Report Block Structure 3.1. Report Block Structure
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 |E| resv. | block length = 2 | | BT=NBGD | I |DT | resv.| block length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| number of packets discarded | | number of packets discarded |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Report Block Structure
3.2. Definition of Fields in Discard Metric Report Block 3.2. Definition of Fields in Discard Metric Report Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Discard Metric Report Block is identified by the constant ND. A Discard Metric Report Block is identified by the constant ND.
[Note to RFC Editor: please replace ND with the IANA provided RTCP [Note to RFC Editor: please replace ND with the IANA provided RTCP
XR block type for this block.] 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 Basic Loss/Discard This field is used to indicate whether the Discard metric is an
metrics are sampled,Interval or Cumulative metrics, that is, sampled,Interval or Cumulative metric, that is, whether the
whether the reported values applies to the most recent measurement reported values applies to the most recent measurement interval
interval duration between successive metrics reports (I=10) (the duration between successive metrics reports (I=10) (the Interval
Interval Duration) or to the accumulation period characteristic of Duration) or to the accumulation period characteristic of
cumulative measurements (I=11) (the Cumulative Duration) or to the cumulative measurements (I=11) (the Cumulative Duration) or to the
value of a continuously measured or calculated that has been value of a continuously measured or calculated that has been
sampled at end of the interval (I=01) (Sampled Value). sampled at end of the interval (I=01) (Sampled Value).
Early indication flag (E): 1bit Discard Type (DT): 2bits
This field is used to indicate whether packets are discarded due This field is used to identify the discard type used in this
to early arrival or due to late arrival. This field MUST be set report block. The discard type is defined as follows:
to '1' if packets are discarded due to too early arrival and MUST
be set to '0' otherwise. 01: packets are discarded due to too early arrival.
10: packets are discarded due to too late arrival.
11: packets are discarded due to both early arrival and late
arrival.
Reserved (resv): 5 bits Reserved (resv): 5 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 2.
skipping to change at page 12, line 24 skipping to change at page 12, line 24
[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.
9.2. Informative References 9.2. Informative References
[MONARCH] Wu, Q., "Monitoring Architectures for RTP", [MONARCH] Wu, Q., "Monitoring Architectures for RTP",
ID draft-ietf-avtcore-monarch-04, August 2011. ID draft-ietf-avtcore-monarch-12, April 2012.
[RFC4588] Rey, J., "RTP Retransmission Payload Format", RFC 4588, [RFC4588] Rey, J., "RTP Retransmission Payload Format", RFC 4588,
July 2006. July 2006.
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, July 2006. Correction", RFC 5109, July 2006.
[RFC5725] Begen, A., "RTCP XR Report Block for Post-Repair Loss [RFC5725] Begen, A., "RTCP XR Report Block for Post-Repair Loss
metric Reporting", metric Reporting", RFC 5725, February 2010.
ID draft-ietf-rtcp-xr-postrepair-loss-02, February 2010.
[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.
Authors' Addresses Authors' Addresses
Geoff Hunt Geoff Hunt
Unaffiliated Unaffiliated
Email: r.geoff.hunt@gmail.com Email: r.geoff.hunt@gmail.com
 End of changes. 11 change blocks. 
19 lines changed or deleted 23 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/