Re: [AVT] 3GPP timed text draft: more generic?

Colin Perkins <csp@csperkins.org> Mon, 11 August 2003 10:04 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 GAA11850 for <avt-archive@odin.ietf.org>; Mon, 11 Aug 2003 06:04:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19m9Wz-0004w5-LE for avt-archive@odin.ietf.org; Mon, 11 Aug 2003 06:04:01 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7BA4186018967 for avt-archive@odin.ietf.org; Mon, 11 Aug 2003 06:04:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19m9Wy-0004vN-TI; Mon, 11 Aug 2003 06:04:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19m9WG-0004vC-BO for avt@optimus.ietf.org; Mon, 11 Aug 2003 06:03: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 GAA11846 for <avt@ietf.org>; Mon, 11 Aug 2003 06:03:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19m9WC-0004QS-00 for avt@ietf.org; Mon, 11 Aug 2003 06:03:12 -0400
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 19m9WC-0004QC-00 for avt@ietf.org; Mon, 11 Aug 2003 06:03:12 -0400
Received: from alor ([130.209.247.84]:54010 helo=csperkins.org) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.04) id 19m9Vj-0005fS-00; Mon, 11 Aug 2003 11:02:43 +0100
Date: Mon, 11 Aug 2003 11:02:37 +0100
Subject: Re: [AVT] 3GPP timed text draft: more generic?
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: avt@ietf.org
To: Jose Rey <rey@panasonic.de>
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <NGBBJIBNJOKHDHFKEOMHKEGFFCAA.rey@panasonic.de>
Message-Id: <EFE5C849-CBE2-11D7-B8F1-000A957FC5F2@csperkins.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
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

On Monday, Aug 11, 2003, at 09:15 Europe/London, Jose Rey wrote:
> 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?).

I believe SMPTE may also have timed text work in their Digital Cinema 
group?

> 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).

I agree that using the MPEG4-simple format doesn't make sense, and that 
the W3C schedule looks to be too long for 3GPP requirements.

-- 
Colin Perkins
http://csperkins.org/


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