RE: [AVT] draft-ietf-avt-rtp-vmr-wb-03: MIME type
"Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se> Thu, 09 September 2004 22:13 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08122 for <avt-archive@ietf.org>; Thu, 9 Sep 2004 18:13:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5XE4-0006bk-H4 for avt-archive@ietf.org; Thu, 09 Sep 2004 18:17:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5WmS-0001mT-Ho; Thu, 09 Sep 2004 17:48:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C5Wam-0007U0-Is for avt@megatron.ietf.org; Thu, 09 Sep 2004 17:36:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03990 for <avt@ietf.org>; Thu, 9 Sep 2004 17:36:30 -0400 (EDT)
Received: from av3-2-sn4.m-sp.skanova.net ([81.228.10.113]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5Weh-0005e6-G1 for avt@ietf.org; Thu, 09 Sep 2004 17:40:36 -0400
Received: by av3-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id 7B34137E6D; Thu, 9 Sep 2004 23:35:58 +0200 (CEST)
Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av3-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 6780037E4D; Thu, 9 Sep 2004 23:35:58 +0200 (CEST)
Received: from vit (h239n2fls31o265.telia.com [217.208.189.239]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with SMTP id 2DFA237E49; Thu, 9 Sep 2004 23:35:58 +0200 (CEST)
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, sassan.ahmadi@nokia.com, IETF AVT WG <avt@ietf.org>
Subject: RE: [AVT] draft-ietf-avt-rtp-vmr-wb-03: MIME type
Date: Thu, 09 Sep 2004 23:35:58 +0200
Message-ID: <GHEPIJKACEKDGLKODIGJEEFHCPAA.gunnar.hellstrom@omnitor.se>
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.6604 (9.0.2911.0)
In-Reply-To: <413C5A1C.9060804@ericsson.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
A few comments on draft-ietf-avt-rtp-vmr-wb-03: <GH1> 4.2.1 Last paragraph: This paragraph is a bit strange to me: "Beyond plain text, there are many formats for representing what might be known as "rich text". An interesting characteristic of many such representations is that they are to some extent readable even without the software that interprets them. It is useful, then, to distinguish them, at the highest level, from such unreadable data as images, audio, or text represented in an unreadable form. In the absence of appropriate interpretation software, it is reasonable to show subtypes of "text" to the user, while it is not reasonable to do so with most non textual data. Such formatted textual data should be represented using subtypes of "text". " What does it want to say? Is it that there are kinds of text coding expressed in images or on video that are better declared as image or video media? E.g. postscript coded text would rather be an image medium? The thought that text is readable even without the software that interprets it is strange and does not produce any distinguishing definition. I think encrypted text should still be declared as text, but it is impossible to read without interpreting software. So the comments rather create confusion than clarification. I think that the definition that 4.2.1 starts with is sufficient to define what text is. The last paragraph could be limited to: "Beyond plain text, there are many formats for representing what might be known as "rich text". Coding is often intermixed control information and text contents. Such formatted textual data should be represented using subtypes of "text". " <GH2> 4.2.4 last paragraph: "Note that although in general this document strongly discourages the mixing of multiple media in a single body, it is recognized that many so-called video formats include a representation for synchronized audio, and this is explicitly permitted for subtypes of "video"." It is also common that text for subtitling is multiplexed into the file or stream. I suggest that the word "text" is added so that the paragraph reads: "Note that although in general this document strongly discourages the mixing of multiple media in a single body, it is recognized that many so-called video formats include a representation for synchronized audio and text, and this is explicitly permitted for subtypes of "video"." ---- Regards Gunnar Hellstrom ------------------------------------------- Gunnar Hellstrom Omnitor AB Renathvagen 2 SE 121 37 Johanneshov SWEDEN +46 8 556 002 03 Mob: +46 708 204 288 www.omnitor.se Gunnar.Hellstrom@Omnitor.se -------------------------------------------- _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] draft-ietf-avt-rtp-vmr-wb-03: MIME type Magnus Westerlund
- [AVT] RE: draft-ietf-avt-rtp-vmr-wb-03: MIME type sassan.ahmadi
- RE: [AVT] draft-ietf-avt-rtp-vmr-wb-03: MIME type Gunnar Hellstrom
- RE: [AVT] draft-ietf-avt-rtp-vmr-wb-03: MIME type Gunnar Hellstrom