Subject: Re: [AVTCORE] [Technical Errata Reported] RFC3550 (4192)

From: Magnus Westerlund <[email-masked]>
Date: Mon, 16 Feb 2015 09:22:05 +0100

WG,

My decision is to recommend the AD to Reject this Errata.

Cheers

Magnus Westerlund

On 2015-01-28 16:43, Magnus Westerlund wrote:
> WG,
> 
> There has been quite some discussion. There appear to be substantial
> support for putting this Errata into the "Rejected" state.
> 
> Any additional feedback, please provided it by the 12th of February.
> 
> Cheers
> 
> Magnus
> 
> On 2014-12-04 02:47, RFC Errata System wrote:
>> The following errata report has been submitted for RFC3550,
>> "RTP: A Transport Protocol for Real-Time Applications".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3550&eid=4192
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Julius Friedman <[email-masked]>
>>
>> Section: 6.4.1
>>
>> Original Text
>> -------------
>> 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.
>>
>> Corrected Text
>> --------------
>> 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).
>>
>> Instructions:
>> -------------
>> This erratum 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. 
>>
>> --------------------------------------
>> RFC3550 (draft-ietf-avt-rtp-new-12)
>> --------------------------------------
>> Title               : RTP: A Transport Protocol for Real-Time Applications
>> Publication Date    : July 2003
>> Author(s)           : H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson
>> Category            : DRAFT STANDARD
>> Source              : Audio/Video Transport
>> Area                : Real-time Applications and Infrastructure
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> [email-masked]
>> https://www.ietf.org/mailman/listinfo/avt
>>
> 
> 

-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: [email-masked]
----------------------------------------------------------------------