IETF Logo Mail Archive

Re: MPEG asks for MIME review for the MPEG21 file format

Chris Lilley <chris@w3.org> Tue, 22 May 2007 16:45 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4MGjnMF081216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 May 2007 09:45:49 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l4MGjnAQ081215; Tue, 22 May 2007 09:45:49 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4MGjm8U081209 for <ietf-xml-mime@imc.org>; Tue, 22 May 2007 09:45:48 -0700 (MST) (envelope-from chris@w3.org)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by homer.w3.org (Postfix) with ESMTP id 0303E4F08B; Tue, 22 May 2007 12:45:46 -0400 (EDT)
Date: Tue, 22 May 2007 18:45:00 +0200
From: Chris Lilley <chris@w3.org>
X-Mailer: The Bat! (v3.95.6) Home
Reply-To: Chris Lilley <chris@w3.org>
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <18169720.20070522184500@w3.org>
To: Graham Klyne <GK@ninebynine.org>
Cc: Dave Singer <singer@apple.com>, Martin Duerst <duerst@it.aoyama.ac.jp>, Anne van Kesteren <annevk@opera.com>, Larry Masinter <LMM@acm.org>, ned.freed@mrochek.com, ietf-liaisons@ietf.org, "'Christian Timmerer (ITEC)'" <christian.timmerer@itec.uni-klu.ac.at>, ietf-types@alvestrand.no, ietf-xml-mime@imc.org
Subject: Re: MPEG asks for MIME review for the MPEG21 file format
In-Reply-To: <4651C7C1.7000703@ninebynine.org>
References: <E94B6002-BAE6-4D08-98A3-89E8D46504F3@stewe.org> <AE61ED01-9B91-4D5D-8654-AF8DD1B86EA2@stewe.org> <464814BE.4090208@ninebynine.org> <p06240821c26e59493bca@[17.202.35.52]> <4649B0BA.4040002@ninebynine.org> <p0624084bc26f9de750bc@[17.202.35.52]> <002901c798b8$0f9ab4f0$2ed01ed0$@org> <892351513.20070518031209@w3.org> <op.tsidc6yf64w2qv@annevk.hotspot.sfr.fr> <6.0.0.20.2.20070518194309.08d1ee50@localhost> <p0624083ec273750809d7@[17.202.35.52]> <1132641919.20070520023450@w3.org> <465162D6.6060301@ninebynine.org> <1501897203.20070521172603@w3.org> <4651C7C1.7000703@ninebynine.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

On Monday, May 21, 2007, 6:24:33 PM, Graham wrote:

GK> Chris Lilley wrote:
>> On Monday, May 21, 2007, 11:13:58 AM, Graham wrote:
>> GK> For clarification: this would be the case only when a suitable MIME
>> GK> content-transfer-encoding header is applied, n'est pas? 

>> If its compressed on the fly, yes. If its stored compressed on the server, then Content-Encoding is used.

GK> Ah, I hadn't considered Content-encoding here.

GK> I note that this header is defined by RFC2616 and registered only for use with
GK> HTTP
GK> (http://www.iana.org/assignments/message-headers/perm-headers.html), which
GK> suggests that it is defined only as part of an HTTP protocol transfer.

Yes, I was talking of HTTP here.

Clearly if one uses, for example, FTP then that isn't an option. But then, neither is the Internet Media type :)

GK> #g

GK> (being rather language-lawyer-ish at this point?)





-- 
 Chris Lilley                    mailto:chris@w3.org
 Interaction Domain Leader
 Co-Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG

v2.23.0 | Report a Bug | By Email