Re: [AVT] Summary of 3GPP timed text draft

John Lazzaro <lazzaro@CS.Berkeley.EDU> Mon, 07 July 2003 19:57 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12090 for <avt-archive@odin.ietf.org>; Mon, 7 Jul 2003 15:57:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zc6h-0000bm-Dx for avt-archive@odin.ietf.org; Mon, 07 Jul 2003 15:57:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67Jv30x002311 for avt-archive@odin.ietf.org; Mon, 7 Jul 2003 15:57:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zc6f-0000YP-Uy; Mon, 07 Jul 2003 15:57:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zc5w-0000Py-Sh for avt@optimus.ietf.org; Mon, 07 Jul 2003 15:56:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12014 for <avt@ietf.org>; Mon, 7 Jul 2003 15:56:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zc5v-0001rH-00 for avt@ietf.org; Mon, 07 Jul 2003 15:56:15 -0400
Received: from snap.cs.berkeley.edu ([128.32.34.209] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19Zc5p-0001rB-00 for avt@ietf.org; Mon, 07 Jul 2003 15:56:09 -0400
Received: (from lazzaro@localhost) by snap.CS.Berkeley.EDU (8.11.6/8.9.3-ZUUL) id h67JtiA21422 for avt@ietf.org; Mon, 7 Jul 2003 12:55:44 -0700
Date: Mon, 07 Jul 2003 12:55:44 -0700
From: John Lazzaro <lazzaro@CS.Berkeley.EDU>
Message-Id: <200307071955.h67JtiA21422@snap.CS.Berkeley.EDU>
To: avt@ietf.org
Subject: Re: [AVT] Summary of 3GPP timed text draft
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>

>  "Jose Rey" <rey@panasonic.de> writes:
>
> The open issues/TODO list includes:
>
> - resilient transport: repetition, fragmentation, retransmission, FEC
> (other?). It is our opinion that repetition should be included at the
> very least.

Is RTCP expected to be normally used with this payload format?  If so,
maybe the core idea behind the RTP MIDI resiliency -- a "recovery journal"
in every packet coding the recent past, whose contents grow and shrink
as the sender examines RTCP RR reports which indicate the highest 
sequence number the receiver has received -- could be the starting
point of a timed text resiliency scheme.  For the default 5 second
RTCP sending rate, and text that is not sent too frequently, one
could imagine a recovery journal approach would be more efficient
that simple repetition.  But you need RTCP to make it work ...

-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu     www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------

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