RE: [AVT] Retransmission draft

"vsathe@san.rr.com" <vsathe@san.rr.com> Thu, 04 December 2003 19:22 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09776 for <avt-archive@odin.ietf.org>; Thu, 4 Dec 2003 14:22:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARz3M-0004II-79 for avt-archive@odin.ietf.org; Thu, 04 Dec 2003 14:22:20 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4JMKv8016502 for avt-archive@odin.ietf.org; Thu, 4 Dec 2003 14:22:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARz34-0004CE-Sq; Thu, 04 Dec 2003 14:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ARyJg-0000xx-Es for avt@optimus.ietf.org; Thu, 04 Dec 2003 13:35:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06249 for <avt@ietf.org>; Thu, 4 Dec 2003 12:50:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ARxcG-0005XO-00 for avt@ietf.org; Thu, 04 Dec 2003 12:50:16 -0500
Received: from relay1.softcomca.com ([168.144.1.67]) by ietf-mx with esmtp (Exim 4.12) id 1ARxcF-0005WN-00 for avt@ietf.org; Thu, 04 Dec 2003 12:50:16 -0500
Received: from M2W071.mail2web.com ([168.144.251.180]) by relay1.softcomca.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 4 Dec 2003 12:49:31 -0500
Message-ID: <184670-220031244174931954@M2W071.mail2web.com>
X-Priority: 3
Reply-To: vsathe@san.rr.com
X-Originating-IP: 66.185.162.194
X-URL: http://mail2web.com/
From: "vsathe@san.rr.com" <vsathe@san.rr.com>
To: avt@ietf.org
Subject: RE: [AVT] Retransmission draft
Date: Thu, 04 Dec 2003 12:49:31 -0500
MIME-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 04 Dec 2003 17:49:31.0792 (UTC) FILETIME=[F8BF6100:01C3BA8E]
Content-Transfer-Encoding: quoted-printable
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

With this disclaimer, I am now confused about the prespective with which I
should read this draft as a (potential) implementator. I understand that
Matsushita may have some IPR in this submission. But now are you saying
that you really don't know why anyone should use this scheme? Would it be
possible to give a scenario or two where the proposed mechanism may be
superior to follow? What is the point in sending this off to IETF RFC
track? 

Thanks in advance for your explanation. 

Vinay Sathe
Multirate Systems

right, how about this:

"This document provides an RTP packet retransmission mechanism for repair of
streaming media.  The purpose of this paragraph is to make the reader aware
that the retransmission mechanism described in this document may be
encumbered by patent applications filed from Matsushita.  For details on the
IPR statement, please visit the IETF IPR web page
http://www.ietf.org/ietf/IPR.

However, packet retransmission is not the only means for streaming clients
and servers to cope with packet losses.  A detailed description of options
for repair of streaming media is given in RFC2354.  Therefore, implementers
of this protocol shall take into account that there are in fact other
mechanisms, such as forward error correction (FEC) or packet interleaving
that represent an alternative to solve the problems packet retransmission
tries to solve.    In particular RFC2733 and RFC2198 present FEC and
redundant packet transmission schemes that might well fit to the needs of
the implementer. "

José


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt