[AVT] Time plan for Timed Text
"Jose Rey" <rey@panasonic.de> Thu, 15 April 2004 13:09 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21711 for <avt-archive@odin.ietf.org>; Thu, 15 Apr 2004 09:09:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BE6Qr-0007xj-9y for avt-archive@odin.ietf.org; Thu, 15 Apr 2004 08:57:29 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3FCvTEc030600 for avt-archive@odin.ietf.org; Thu, 15 Apr 2004 08:57:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BE6Jl-0005Or-Lj; Thu, 15 Apr 2004 08:50:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BE63O-0006pD-Pr for avt@optimus.ietf.org; Thu, 15 Apr 2004 08:33:14 -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 IAA19407 for <avt@ietf.org>; Thu, 15 Apr 2004 08:33:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BE63N-0004ET-00 for avt@ietf.org; Thu, 15 Apr 2004 08:33:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BE62W-0004AF-00 for avt@ietf.org; Thu, 15 Apr 2004 08:32:20 -0400
Received: from vw1.pel.panasonic.de ([194.162.191.15] helo=MailRelay.PEL.Panasonic.de) by ietf-mx with esmtp (Exim 4.12) id 1BE61l-00044a-00 for avt@ietf.org; Thu, 15 Apr 2004 08:31:33 -0400
Received: from localhost ([127.0.0.1]) by MailRelay.PEL.Panasonic.de for avt@ietf.org; Thu, 15 Apr 2004 14:33:13 +0200
Received: from MCOMREYJ ([10.10.100.173]) by mail.pel.panasonic.de with Microsoft SMTPSVC(5.0.2195.6713); Thu, 15 Apr 2004 14:27:35 +0200
From: Jose Rey <rey@panasonic.de>
To: avt@ietf.org
Date: Thu, 15 Apr 2004 14:29:02 +0200
Message-ID: <FDEEJECAGFFPBFPHMIIPMEKPHKAA.rey@panasonic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Importance: Normal
X-OriginalArrivalTime: 15 Apr 2004 12:27:35.0125 (UTC) FILETIME=[080EA850:01C422E5]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [AVT] Time plan for Timed Text
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
no, it's not a pun ;) ---- Hi all, it's been awhile since I submitted the draft-ietf-avt-rtp-3gpp-timed-text-00.txt. However to date, I haven't got much comments on it (to be exact: none). So... before you come out with those hundreds of comments I would like to remind you what is this about and propose a time plan for the draft. A bit of background info ======================== As you know the timed text draft specifies a payload format for 3GPP timed text media format (specified in 3GPP TS26.234 Rel5 and TS26.245 Rel6). This is a media format that allows the creation of decorated text that can be synchronised with audio/video/other media streams. Examples are: newscasts/movies subtitles, live tickers, karaoke, multimedia presentations.... The draft was accepted as a WG item in the last IETF Meeting in Korea and since then a new (uncommented) version is out... Time plan for Timed Text draft ============================== Assuming that Release 6 closes in September 2004 (which is a quite realistic assumption) this would be the time plan: - until **May 1st** (15 days from now): gather comments from AVT on current draft-ietf-avt-rtp-3gpp-timed-text-00 and submit new version within a week (May 7-9th) - repeat this process with the new draft a maximum of three times (3 new drafts) but probably only 2. That would mean that by the end of June a final draft should be ready. - **End June/begin July: request WGLC**. Assuming it passes this WGLC the draft would enter the rest of procedures and reviews around mid July, and would have 1.5 months to make its way to RFC which is fairly feasible. What do you think? Comments? Got a better idea? Volunteers to review? Thanks, ------------------------------- Jose Rey Mobile Multimedia Team Panasonic European Labs GmbH D-63225 Langen, Germany Tel.:+49-6103-766-134 Fax :+49-6103-766-166 Email: rey@panasonic.de Visit: www.pel.panasonic.de ------------------------------- _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Time plan for Timed Text Jose Rey
- Re: [AVT] Time plan for Timed Text Colin Perkins