IETF Logo Mail Archive

[AVTCORE] [Technical Errata Reported] RFC3550 (4192)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 04 December 2014 01:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C731A6F58 for <avt@ietfa.amsl.com>; Wed, 3 Dec 2014 17:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5wS-ylkLUFC2 for <avt@ietfa.amsl.com>; Wed, 3 Dec 2014 17:48:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id D5D771A00D8 for <avt@ietf.org>; Wed, 3 Dec 2014 17:48:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6282D181CD3; Wed, 3 Dec 2014 17:47:37 -0800 (PST)
To: schulzrinne@cs.columbia.edu, casner@acm.org, ronf@bluecoat.com, van@packetdesign.com, rlb@ipv.sx, alissa@cooperw.in, keith.drage@alcatel-lucent.com, roni.even@mail01.huawei.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20141204014737.6282D181CD3@rfc-editor.org>
Date: Wed, 03 Dec 2014 17:47:37 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/fZuxBy9-CRrYv6YJaOxObOnAHjk
X-Mailman-Approved-At: Thu, 04 Dec 2014 09:48:04 -0800
Cc: juliusfriedman@gmail.com, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] [Technical Errata Reported] RFC3550 (4192)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 01:48:13 -0000

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 <juliusfriedman@gmail.com>

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

v2.23.0 | Report a Bug | By Email