RE: [AVT] 3GPP timed text draft: more generic?
"Jose Rey" <rey@panasonic.de> Mon, 11 August 2003 08:16 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 EAA09820 for <avt-archive@odin.ietf.org>; Mon, 11 Aug 2003 04:16:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19m7qm-0001Kq-BA for avt-archive@odin.ietf.org; Mon, 11 Aug 2003 04:16:21 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7B8GKWx005132 for avt-archive@odin.ietf.org; Mon, 11 Aug 2003 04:16:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19m7qW-0001KD-SI; Mon, 11 Aug 2003 04:16:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19m7qK-0001Jt-JW for avt@optimus.ietf.org; Mon, 11 Aug 2003 04:15:52 -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 EAA09804 for <avt@ietf.org>; Mon, 11 Aug 2003 04:15:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19m7qH-0003pI-00 for avt@ietf.org; Mon, 11 Aug 2003 04:15:49 -0400
Received: from mail.pel.panasonic.de ([194.162.191.12]) by ietf-mx with esmtp (Exim 4.12) id 19m7qH-0003pF-00 for avt@ietf.org; Mon, 11 Aug 2003 04:15:49 -0400
Received: from atrgreyj ([10.78.238.55]) by mail.pel.panasonic.de with Microsoft SMTPSVC(5.0.2195.6713); Mon, 11 Aug 2003 10:15:44 +0200
From: Jose Rey <rey@panasonic.de>
To: Colin Perkins <csp@csperkins.org>
Cc: avt@ietf.org
Subject: RE: [AVT] 3GPP timed text draft: more generic?
Date: Mon, 11 Aug 2003 10:15:44 +0200
Message-ID: <NGBBJIBNJOKHDHFKEOMHKEGFFCAA.rey@panasonic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <20030728061758.2c17d347.csp@csperkins.org>
Importance: Normal
Reply-By: Tue, 5 Aug 2003 13:30:00 +0200
X-Message-Flag: Follow up
X-OriginalArrivalTime: 11 Aug 2003 08:15:44.0187 (UTC) FILETIME=[C2CA80B0:01C35FE0]
Content-Transfer-Encoding: 7bit
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: 7bit
Hi all, --snip Colin Perkins wrote: > A specific payload format for 3GPP timed text might be > appropriate, but I > would like to understand the options and alternatives before > we make that > choice. Is 3GPP the only body doing timed and/or decorated > text? If not, > what are the alternatives, and how do they relate? > > -- at the moment there are at least two more standardisation bodies interested in timed text: MPEG and W3C. - MPEG is currently defining their own TT format based on 3GPP TT (see Committee Draft of ISO/IEC 14496-17 from July'03 Meeting in Trondheim) by defining the access unit structure, the stream type, the object type indication and decoder specific info of the timed text samples. The definition of these items enables the transport over RTP using the mpeg4simple draft. The work in MPEG is assumed to be finalised around July 2004. - W3C is at a very early stage in defining a timed text authoring format. It has recently (May'03) published a draft for use cases and requirements of a timed text authoring format: http://www.w3.org/TR/2003/WD-tt-af-1-0-req-20030515/. This draft has a rather long list of requirements and lists many functionalities. In my understanding W3C targets to a generic format with rich functionality. I don't know how quick it may develop (anyone?). None of these above is an option for us, because 1) the only timed text format in 3GPP is 3GPP timed text 2) 3GPP has not adopted the mpeg4simple for transport and 3) for this 3GPP timed text format we need an RTP payload format within the current 3GPP Release 6 schedule (i.e. March'04). cheers, Jose > -----Original Message----- > From: Colin Perkins [mailto:csp@csperkins.org] > Sent: Monday, July 28, 2003 3:18 PM > To: Jose Rey > Cc: avt@ietf.org > Subject: Re: [AVT] 3GPP timed text draft: more generic? > > > --> "Jose Rey" <rey@panasonic.de> writes: > > > > Hi all, > > > > during the presentation of the payload format for 3GPP > timed text some > > concerns arose on whether this work should be more generic. On the > > other hand I also emphasized the fact that there's a > deadline to meet > > here for 3GPP Release 6: March '04. > > > > It is our opinion that, in this case, a more specific > payload format for > > the 3GPP timed text format is the right way to go. Does > anybody think > > otherwise? We would like to hear comments/critic on this, > in order to > > progress to working group work item. How could it be made > more generic? > > Colin Perkins > csp@csperkins.org _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- Re: [AVT] 3GPP timed text draft: more generic? Colin Perkins
- [AVT] 3GPP timed text draft: more generic? Jose Rey
- RE: [AVT] 3GPP timed text draft: more generic? Jose Rey
- RE: [AVT] 3GPP timed text draft: more generic? Jose Rey
- Re: [AVT] 3GPP timed text draft: more generic? Colin Perkins