Re: Scope of application/* media types (was: Protocol changes in draft-allbery-usefor-usepro-00)

"Charles Lindsey" <chl@clerew.man.ac.uk> Wed, 03 January 2007 05:15 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1yT4-0005JC-L5 for usefor-archive@lists.ietf.org; Wed, 03 Jan 2007 00:15:14 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1yT3-0001Ev-6m for usefor-archive@lists.ietf.org; Wed, 03 Jan 2007 00:15:14 -0500
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 l035CbtP063951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jan 2007 22:12:37 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l035CbEi063950; Tue, 2 Jan 2007 22:12:37 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from lon-mail-4.gradwell.net (lon-mail-4.gradwell.net [193.111.201.130]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l035CUvo063863 for <ietf-usefor@imc.org>; Tue, 2 Jan 2007 22:12:31 -0700 (MST) (envelope-from news@clerew.man.ac.uk)
Received: from [80.175.135.89] ([80.175.135.89] helo=clerew.man.ac.uk country=GB ident=postmaster#pop3#clerew^man$ac^uk) by lon-mail-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.237) id 459b3b3c.1769a.567 for ietf-usefor@imc.org; Wed, 3 Jan 2007 05:12:28 +0000 (envelope-sender <news@clerew.man.ac.uk>)
Received: from clerew.man.ac.uk (localhost [127.0.0.1]) by clerew.man.ac.uk (8.13.7/8.13.7) with ESMTP id l035CRMJ018072 for <ietf-usefor@imc.org>; Wed, 3 Jan 2007 05:12:27 GMT
Received: (from news@localhost) by clerew.man.ac.uk (8.13.7/8.13.7/Submit) id l035CR65018069 for ietf-usefor@imc.org; Wed, 3 Jan 2007 05:12:27 GMT
To: ietf-usefor@imc.org
Xref: clerew local.usefor:24001
Path: clerew!chl
From: Charles Lindsey <chl@clerew.man.ac.uk>
Subject: Re: Scope of application/* media types (was: Protocol changes in draft-allbery-usefor-usepro-00)
Message-ID: <JB9A47.2xI@clerew.man.ac.uk>
X-Newsreader: NN version 6.5.2 (NOV)
References: <JA8C4p.Anu@clerew.man.ac.uk> <873b7i9b2m.fsf@windlord.stanford.edu> <JAHJs5.FHC@clerew.man.ac.uk> <877iwagy21.fsf_-_@windlord.stanford.edu>
Date: Tue, 02 Jan 2007 19:28:55 +0000
Lines: 71
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

In <877iwagy21.fsf_-_@windlord.stanford.edu> Russ Allbery <rra@stanford.edu> writes:

>Charles Lindsey <chl@clerew.man.ac.uk> writes:
>> Russ Allbery <rra@stanford.edu> writes:
>>> Charles Lindsey <chl@clerew.man.ac.uk> writes:

>>>> 26. [-1] (4.2,4.3) Removed requirement that
>>>> application/news-[groupinfo,checkgroups] MUST NOT be used except with
>>>> relevant control messages.

>> Application types are intended to cause applications to be invoked, with
>> possible side effects.

>Could you provide a reference for this?  I don't see this statement in RFC
>2046.  The closest that it has is:

>   The "application" media type is to be used for discrete data which do
>   not fit in any of the other categories, and particularly for data to
>   be processed by some type of application program.  This is
>   information which must be processed by an application before it is
>   viewable or usable by a user.

OK. Perhaps I was carried away by the propensity of Microsoftware to
execute anything that is remotely executable even if the user just blinks
:-( .

And it is certainly the case that application types are mostly intended to
be processed by application programs that may have side effects beyond
fancy forms of display. And RFC 2046 goes to considerable lengths to warn
agains possible side effects of obeying an application/postscript.

>> In this case, the side efect is that a line gets added/changed in the
>> Newsgroups file.

>I don't agree with this interpretation, and I don't see anything in the
>text of the application/news-groupinfo registration that reflects this.

I doubt if you would be sending an application/group-info in an
article/message unless you thought that the recipient might want to use it
for exactly that purpose.

>It sounds to me like you're confusing the newgroup control message with
>the application/news-groupinfo MIME media type.  They're not the same
>thing.

But are clearly related.

>> OK, in that case what you need to say is:

>>     This media type is intended to be used in conjunction with the
>>     newgroup control message as described in section 5.2.1. It MUST NOT be
>>     automatically invoked in any other context without explicit human
>>     intervention.

>> and similarly for checkgroups.

>I disagree with adding anything like this to our document.

OK. In which case the existing sentences at the start of 4.2 and 4.3 will
suffice.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl@clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5