Re: [arcmedia] Legacy formats

Matthew Kerwin <matthew@kerwin.net.au> Sun, 28 June 2015 00:43 UTC

Return-Path: <phluid61@gmail.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 7B5AD1A004B for <arcmedia@ietfa.amsl.com>; Sat, 27 Jun 2015 17:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.872
X-Spam-Level:
X-Spam-Status: No, score=0.872 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 Hy6FQPSK4O13 for <arcmedia@ietfa.amsl.com>; Sat, 27 Jun 2015 17:43:26 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 044F21A0039 for <arcmedia@ietf.org>; Sat, 27 Jun 2015 17:43:26 -0700 (PDT)
Received: by obbop1 with SMTP id op1so86322622obb.2 for <arcmedia@ietf.org>; Sat, 27 Jun 2015 17:43:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=rgdm2kQaovMMS89L0adPQfgk2oGOxRGRgoYPENus6WA=; b=KE1+LL3mg5ZJRNXenaQsv+bSwXUDzMszD0bozZA8PB26aKQ8XwD3/LpCLpakUwzgOP eXtRsH8vQoop27v68PFrDaEpuaxOMo0uB4nGVlCEc2jfP4EPS6u959E/YiVN5V4WnN1e M4XpzojuP8nIGAgjaJwK87+XlD34jrj/3xspS+wG8SMd51akPvwa8TiiVtDOSFZsrJQE JXC0pARTbhR0ohfmIapfRBSY1j9L8wQ3UDD2nJnZZTxqWQDNPAZOpp//xKh+IpERXWT5 GZrGzLvFD/w/CBxXWDoaPKDtVSc04pXu5j+6J+Q1KktVJf+rgPYbQXAHt6ya/qB1bu27 66Gw==
MIME-Version: 1.0
X-Received: by 10.202.104.211 with SMTP id o80mr7327408oik.19.1435452205445; Sat, 27 Jun 2015 17:43:25 -0700 (PDT)
Sender: phluid61@gmail.com
Received: by 10.202.226.205 with HTTP; Sat, 27 Jun 2015 17:43:25 -0700 (PDT)
Received: by 10.202.226.205 with HTTP; Sat, 27 Jun 2015 17:43:25 -0700 (PDT)
In-Reply-To: <1435448585.3504.0@mail.zedat.fu-berlin.de>
References: <1435448585.3504.0@mail.zedat.fu-berlin.de>
Date: Sun, 28 Jun 2015 10:43:25 +1000
X-Google-Sender-Auth: rEZGS8bCJZKBzTLfSp1hNJ-R4g8
Message-ID: <CACweHNDF2ObL03h3bW6BW4f=fQfmBvO5wOgT4EzP2Q6EOAfAhg@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Tim Scheuermann <tim.scheuermann@fu-berlin.de>
Content-Type: multipart/alternative; boundary="001a11410148cc3b3b05198942df"
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcmedia/cr9MuGWciagGjYAGxeM2sDp9NVs>
Cc: arcmedia@ietf.org
Subject: Re: [arcmedia] Legacy formats
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 28 Jun 2015 00:43:27 -0000

Hi Tim,

On 28/06/2015 9:43 AM, "Tim Scheuermann" <tim.scheuermann@fu-berlin.de>
wrote:
>
> Hi all,
>
> I read through the draft and wondered if Appendix A should include such
old formats like .a (.ar), or should it be limited to the most commonly
used formats?
>
> - Tim
>

My personal feeling is that we (the community, not just the WG) pursue a
select few, both as seeds and to demonstrate and expoore the utility of the
type.

To that end:

* .tar, .iso, .7z -- not currently registered (that I can see), but common
enough in the wild
* .tar.gz / .tgz -- because it's an interesting case
* .zip or gzip -- already registered under 'application', so we can explore
issues with duplicating/moving

That said, I wouldn't discourage someone from registering .a, even if just
historically.

If we get some solid work done in parallel on creating drafts of these
sorts of registrations, Appendix A doesn't necessarily need to stay in the
draft.

Cheers