RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 3550, "RTP: A Transport Protocol for Real-Time Applications", July 2003

Source of RFC: avt (rai)

Errata ID: 4192
Status: Rejected
Type: Technical
Publication Format(s) : TEXT

Reported By: Julius Friedman
Date Reported: 2014-12-03
Rejected by: Ben Campbell
Date Rejected: 2015-07-22

Section 6.4.1 says:

sender's octet count: 32 bits
      The total number of payload octets (i.e., not including header or
      padding) transmitted in RTP data packets by the sender since
      starting transmission up until the time this SR packet was
      generated.  The count SHOULD be reset if the sender changes its
      SSRC identifier.  This field can be used to estimate the average
      payload data rate.

It should say:

sender's octet count: 32 bits
      The total number of payload octets 
      transmitted in RTP data packets by the sender since
      starting transmission up until the time this SR packet was
      generated.  The count SHOULD be reset if the sender changes its
      SSRC identifier.  This field can be used to estimate the average
      payload data rate.

Notes:

Where as payload octets is defined as the total number of data octets contained in a Rtp Packet minus the 12 Header octets for Rtp Packets.

Padding octets as well as octets which occur in the contributing source list should also be included as they may differ on a per packet basis and would make the total calculation invalid.

During TCP communication any application layer header should NOT be included in the total bytes count when including the header length.

Any Rtcp packet counters should include the total length of the packet (header, padding and any other data).
--VERIFIER NOTES--
Rejected based on discussion in avtcore

Report New Errata