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

Sean Leonard <dev+ietf@seantek.com> Sat, 03 January 2015 19:25 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 7144C1A00BE; Sat, 3 Jan 2015 11:25:25 -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 IGGNa_UpVfeT; Sat, 3 Jan 2015 11:25:24 -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 1526A1A0055; Sat, 3 Jan 2015 11:25:24 -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 045E922E260; Sat, 3 Jan 2015 14:25:16 -0500 (EST)
Message-ID: <54A841E0.7070306@seantek.com>
Date: Sat, 03 Jan 2015 11:24:16 -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: John Levine <johnl@taugh.com>, apps-discuss@ietf.org, "arcmedia@ietf.org" <arcmedia@ietf.org>
References: <20150103191748.19958.qmail@ary.lan>
In-Reply-To: <20150103191748.19958.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/arcmedia/xxcGjCTyJzEhKFPJUA5XEB5Pq20
Subject: Re: [arcmedia] [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: Sat, 03 Jan 2015 19:25:25 -0000

On 1/3/2015 11:17 AM, John Levine wrote:
>> Here's a diff, and the changed text.
>> (Not sure if it will be accepted by the IETF mailing list...guess we're
>> about to find out)
> I'm with Murray.  It seems harmless but pointless.  One the things a WG
> will have to do is to figure out what counts as an archive data format.
> If you want us to consider ISO 9660, I want us to consider ANSI INCITS 27.

If it's used in regular commerce on the Internet, I don't have a problem 
with ANSI INCITS 27.

But I think your suggestion is a bit tongue-in-cheeck. .iso files are 
*everywhere* on the Internet, and can contain payloads that seriously 
affect the security of Internet-connected systems. I believe there is a 
certain popular website out there just dedicated to "hunting" for them. 
And to-date it still doesn't have a media type.

A few e-mails back, it was stated that "No other work is in scope for 
this working group" [except what's in the charter]. So the natural 
evolution is to be sure that the charter includes everything that should 
be in-scope.

Sean