Subject: [AVT] [Technical Errata Reported] RFC5760 (2117)

From: RFC Errata System <[email-masked]>
Date: Mon, 5 Apr 2010 04:25:39 -0700 (PDT)

The following errata report has been submitted for RFC5760,
"RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5760&eid=2117

--------------------------------------
Type: Technical
Reported by: Alfred Hoenes <[email-masked]>

Section: B.4, pg.65

Original Text
-------------
      The packet fields will contain the values:

|     Header Distribution Block
|     Distribution Type:                        1
      Number of Data Buckets:                   40
      Multiplicative Factor:                    0
      Packet Length field:                      18 (18 * 4 => 72 bytes)
|     Minimum Loss Value:                       0
|     Maximum Loss Value:                       39

|     Bucket values are the same as the initial data set.

|     Result
|     Selecting one of the three methods outlined above might be done by
      a congestion parameter or by user preference.  The overhead
      associated with processing the packets is likely to differ very
      little between the techniques.  The savings in bandwidth are
|     apparent, however, using 20, 52, and 72 octets respectively.
      These values would vary more widely for a larger data set with
      less correlation between results.

Corrected Text
--------------
      The packet fields will contain the values:

|     RSI report fixed header;
|     -- Sub-report Block --
|     Sub-Report Block Type:                    4 (Loss distribution)
      Number of Data Buckets:                   40
      Multiplicative Factor:                    0
      Packet Length field:                      18 (18 * 4 => 72 bytes)
|     Minimum Distribution Value:               0
|     Maximum Distribution Value:               39

|     Bucket values are the same as the initial data set, represented
|     in 12 bits each.

|  Result
|     Selecting one of the two methods outlined above might be done by
      a congestion parameter or by user preference.  The overhead
      associated with processing the packets is likely to differ very
      little between the techniques.  The savings in bandwidth are
|     apparent, however, using 20 and 72 octets respectively.
      These values would vary more widely for a larger data set with
      less correlation between results.

Notes
-----
Rationale: See preceding reort, eid=2115 !
Also, there are only two examples le ft in the published appendix.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5760 (draft-ietf-avt-rtcpssm-19)
--------------------------------------
Title               : RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback
Publication Date    : February 2010
Author(s)           : J. Ott, J. Chesterfield, E. Schooler
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG