Re: [arcmedia] FW: [apps-discuss] Proposed charter for arcmedia

Sean Leonard <dev+ietf@seantek.com> Fri, 02 January 2015 13:35 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: arcmedia@ietfa.amsl.com
Delivered-To: arcmedia@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA311A872D for <arcmedia@ietfa.amsl.com>; Fri, 2 Jan 2015 05:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PflqNDAeNrKd for <arcmedia@ietfa.amsl.com>; Fri, 2 Jan 2015 05:35:55 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AA661A3BA6 for <arcmedia@ietf.org>; Fri, 2 Jan 2015 05:35:55 -0800 (PST)
Received: from [192.168.123.7] (unknown [23.241.1.22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F13AE22E265; Fri, 2 Jan 2015 08:35:52 -0500 (EST)
Message-ID: <54A69E82.7070308@seantek.com>
Date: Fri, 02 Jan 2015 05:34:58 -0800
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: arcmedia@ietf.org
References: <CAL0qLwYdnW+o4WUb72VM6yuEP8-jBxQ-KgYQm7KP2Sq9E6dp5g@mail.gmail.com> <CAPRnXtkg5GzLmPOWP=DrV8gTvgV+XDhOi=n3OZ86Yrhw+hOgJA@mail.gmail.com> <CAL0qLwad-UcKECA=m7Zqhw+VZ6wy=bFPVKs_ik+fqjPW7-U7cQ@mail.gmail.com> <54A41D6C.9010501@ninebynine.org> <DM2PR0201MB096001DD5DBB2C67ED9BFE53C35C0@DM2PR0201MB0960.namprd02.prod.outlook.com> <54A51EA1.8090900@ninebynine.org> <CAPRnXtk0kwV-urb0j1bEHGUjejgbfVC6Dcsm_8UDJ+Uq1TunPA@mail.gmail.com> <54A69820.6060903@ninebynine.org>
In-Reply-To: <54A69820.6060903@ninebynine.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/arcmedia/mWVdSdggAq5jc3OUaqcdsgk0HkU
Cc: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>, Graham Klyne <gk@ninebynine.org>, Larry Masinter <masinter@adobe.com>
Subject: Re: [arcmedia] FW: [apps-discuss] Proposed charter for arcmedia
X-BeenThere: arcmedia@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of creating a new top-level media type, \"archive\", for archive bundles." <arcmedia.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcmedia>, <mailto:arcmedia-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/arcmedia/>
List-Post: <mailto:arcmedia@ietf.org>
List-Help: <mailto:arcmedia-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcmedia>, <mailto:arcmedia-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2015 13:35:56 -0000

On 1/2/2015 5:07 AM, Graham Klyne wrote:
> Hi Stian,
>
> On 02/01/2015 10:54, Stian Soiland-Reyes wrote:
>> I think the whole point of the archive/ type is the general
>> archive/file fall-back, as discussed in the BOF - e.g. the OS/browser
>> can do "I don't know how to deal with this
>> archive/grahams-latest-thing, I'll just throw it at
>> Winzip/7Zip/Archive Manager and hope for the best" - it's a similar
>> default as Notepad for text/* and Gimp for image/*.
>
> I don't know what was said at the BoF.  This being the IETF, it didn't 
> officially happen unless it also appears on the mailing list.
>
> Is this something that you think should appear in the charter?
>
> I'm not entirely convinced that archive/<unknown> has a safe fallback 
> like text/<unknown> ...

The BoF was an official BoF...and minutes were taken. So I think the 
minutes need to be posted to the mailing list. (I forgot who took the 
minutes.)

But yes, this stuff was explicitly discussed; one common motivator is 
that archive/* should have fallback handling that is more specific than 
application/octet-stream. As of 2015, many file archive programs are 
swiss-army knives, handling a wide array of formats.

Cheers,

Sean