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

Graham Klyne <GK@ninebynine.org> Mon, 21 May 2007 16:25 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 l4LGP5qH095341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 09:25:05 -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 l4LGP5QP095340; Mon, 21 May 2007 09:25:05 -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 sb7.songbird.com (sb7.songbird.com [208.184.79.137]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4LGP3P1095319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-xml-mime@imc.org>; Mon, 21 May 2007 09:25:04 -0700 (MST) (envelope-from GK@ninebynine.org)
Received: from [127.0.0.1] (mail.songbird.com [208.184.79.10]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l4LGOfUV006757; Mon, 21 May 2007 09:24:42 -0700
Message-ID: <4651C7C1.7000703@ninebynine.org>
Date: Mon, 21 May 2007 17:24:33 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Chris Lilley <chris@w3.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
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>
In-Reply-To: <1501897203.20070521172603@w3.org>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: gk@ninebynine.org
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>

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.

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

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

#g

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

-- 
Graham Klyne
For email:
http://www.ninebynine.org/#Contact