[AVT] More comments on draft-rey-avt-rtp-3gpp-timed-text-01.txt
jan.vandermeer@philips.com Mon, 10 November 2003 14:57 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21811 for <avt-archive@odin.ietf.org>; Mon, 10 Nov 2003 09:57:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDTo-0008Pk-Rn for avt-archive@odin.ietf.org; Mon, 10 Nov 2003 09:57:26 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAAEvOUw032340 for avt-archive@odin.ietf.org; Mon, 10 Nov 2003 09:57:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJDTR-0008Or-2f; Mon, 10 Nov 2003 09:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AJCZd-0005vO-Ex for avt@optimus.ietf.org; Mon, 10 Nov 2003 08:59:21 -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 IAA19744; Mon, 10 Nov 2003 08:59:07 -0500 (EST)
From: jan.vandermeer@philips.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AJCZb-0004op-00; Mon, 10 Nov 2003 08:59:19 -0500
Received: from gw-nl5.philips.com ([212.153.235.109] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1AJCZZ-0004om-00; Mon, 10 Nov 2003 08:59:17 -0500
Received: from smtpscan-nl1.philips.com (smtpscan-nl1.philips.com [130.139.36.21]) by gw-nl5.philips.com (Postfix) with ESMTP id 6D1565AA15; Mon, 10 Nov 2003 14:59:09 +0100 (MET)
Received: from smtpscan-nl1.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 82AD919C4C; Mon, 10 Nov 2003 14:59:07 +0100 (MET)
Received: from smtprelay-nl2.philips.com (smtprelay-eur2.philips.com [130.139.36.35]) by smtpscan-nl1.philips.com (Postfix) with ESMTP id 821E919C45; Mon, 10 Nov 2003 14:59:06 +0100 (MET)
Received: from ehvrmh02.diamond.philips.com (ehvrmh02-srv.diamond.philips.com [130.139.27.125]) by smtprelay-nl2.philips.com (8.9.3p3/8.8.5-1.2.2m-19990317) with ESMTP id OAA28722; Mon, 10 Nov 2003 14:59:05 +0100 (MET)
To: rey@panasonic.de, 'IETF AVT WG' <avt@ietf.org>
Cc: avt-admin@ietf.org, Colin Perkins <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, 'Dave Singer' <singer@apple.com>
X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000
Message-ID: <OF74A164F8.98E19243-ONC1256DDA.003AF4A3@philips.com>
Date: Mon, 10 Nov 2003 14:57:05 +0100
X-MIMETrack: Serialize by Router on ehvrmh02/H/SERVER/PHILIPS(Release 6.0.2CF1|June 9, 2003) at 10/11/2003 14:57:07
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=_mixed 004CD08BC1256DDA_="
Subject: [AVT] More comments on draft-rey-avt-rtp-3gpp-timed-text-01.txt
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>
Dear Jose, all, I will not be in Minneapolis either but would like to provide some input on the issue of transport of 3GPP timed text. I know this input is very late; my appologies for that. As you know also MPEG is working on timed text; currently the Committe Draft (CD) is ballotted, and MPEG schedules to enter the next phase in about one month and to finish the work in July 2004. The end-result will be part 17 of MPEG-4, defining MPEG-4 text streams. Through liaisons, MPEG tries to harmonize its work with the work that is already carried out in 3GPP and also with ongoing work in W3C. Most important in this respect is that MPEG focusses at maximum commonality with the timed text format defined by 3GPP for download. In summary, the current CD of MPEG-4 part 17 specifies streaming of the 3GPP timed text format by defining a very straightforward way to transcode the 3GPP format into the MPEG-4 structure of a decoder configuration and text access units. Please find the Committee Draft (a public document) attached to this email. So far, 3GPP expressed through liaison statements to be very pleased with the work done by MPEG. Once the work is finished, the timed text format can be streamed using "RFC#simple", draft-ietf-avt-mpeg4-simple-08.txt, that is scheduled to be published as RFC very soon. In summary this approach would work as follows: - media type: "video", - MIME subtype name: mpeg4-generic, - streamType (required parameter in RFC#simple): indicates MPEG-4 text stream as defined in ISO 14496-17, - profile-level-id (required parameter in RFC#simple): specifies the functional subset as defined in the current 3GPP timed text specification, - config (required parameter in RFC#simple): carries the decoder configuration specified for text streams in ISO 14496-17, - the RTP payload contains either (a) one fragment of a text access unit or (b) one or more complete text access units, - the RTP payload carries one AU-header for each carried text access unit, - in the RTP payload the concatenated AU-headers preceed concatenated data of text access units, as defined in RFC#simple, - each AU-header contains (at least) the following information on the associated text access unit: (a) the size of the text access unit, (b) the time stamp of the text access unit, - if deemed necessary, the AU-header may also carry the index of a text access unit (fragment) and/or an indication whether the associated text access unit is a random access point. In RFC#simple the fields in the AU-header are configurable, but if desired one or two new modes for RFC#simple could be defined with fixed length fields, for example one using an 8 bit AU-size field (for most common applications) and another using 16 bits AU-size field for applications using (very) large text access units. The above "RFC#simple approach" has a high level of commonality with draft-rey-avt-rtp-3gpp-timed-text-01.txt. There are some small differences that can be fixed either way, but roughly the "RFC#simple approach" is a simplified version of draft-rey-avt-rtp-3gpp-timed-text-01.txt. In particular, the "RFC#simple" approach does not have the advanced error resiliency measures that are in draft-rey-avt-rtp-3gpp-timed-text-01.txt. In my view not only in IETF, but also in 3GPP and in MPEG a number of basic issues should be discussed, such as: - are the error resiliency features of draft-rey-avt-rtp-3gpp-timed-text-01.txt sufficiently valuable to justify their complexity (note that a partly corrupted subtitle may not have much more value to the user than a missing one); - is it desirable to define a 3GPP timed text transport solution based on draft-rey-avt-rtp-3gpp-timed-text-01.txt next to the one that will be available based on RFC#simple; - is it desirable that draft-rey-avt-rtp-3gpp-timed-text-01.txt specifies a mode or an extension of RFC#simple; - how can a timing conflict (if any) between release 6 of 3GPP and part 17 of MPEG-4 be resolved (note that such conflict will only exist if 3GPP adopts streaming of timed text as a work item and if 3GPP decides that this functionality has to be in release 6). I hope you will have a fruitful discussion on this subject in Mineapolis. But, this is not just an IETF issue. Therefore, as both 3GPP and MPEG are main "customers" of a timed text streaming solution, I suggest that IETF requests 3GPP and MPEG to advice IETF as to the most desirable direction for resolving this issue. Note that both 3GPP and MPEG will have meetings where this issue can be discussed well before the end of this year. Best regards, Jan van der Meer
- [AVT] More comments on draft-rey-avt-rtp-3gpp-tim… jan.vandermeer