Re: [arcmedia] [apps-discuss] Proposed charter for arcmedia
Dave Crocker <dhc@dcrocker.net> Wed, 31 December 2014 20:42 UTC
Return-Path: <dhc@dcrocker.net>
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 E2DB21A1AA1; Wed, 31 Dec 2014 12:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 IslfUdrbSn0t; Wed, 31 Dec 2014 12:42:53 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A17C1A1A7D; Wed, 31 Dec 2014 12:42:53 -0800 (PST)
Received: from [172.29.108.161] (wsip-72-214-58-13.sd.sd.cox.net [72.214.58.13]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id sBVKghDI013980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 31 Dec 2014 12:42:47 -0800
Message-ID: <54A45FBD.1070701@dcrocker.net>
Date: Wed, 31 Dec 2014 12:42:37 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
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>
In-Reply-To: <54A41D6C.9010501@ninebynine.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 31 Dec 2014 12:42:48 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/arcmedia/Befd0HTPYN0947K9XxfzQ6KDb94
X-Mailman-Approved-At: Wed, 31 Dec 2014 20:23:07 -0800
Cc: arcmedia@ietf.org, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [arcmedia] [apps-discuss] Proposed charter for arcmedia
X-BeenThere: arcmedia@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 31 Dec 2014 20:42:55 -0000
The proffered text is all reasonable, but it needs a small bit of enhancement, for broader readership and a bit of IETF formality: I suggest adding an opening sentence that sets the context a little more. Something like: Archive formats are used to aggregate multiple files and other data into a single object, often with data compression and/or confidentiality protection (encryption). > There has been recent work to register media types for archive > formats such as “tar” (a POSIX standard format). There are already > several similar media types for archive formats, such as “gzip” and > “zip” (see, for example, RFC6713), all of which are registered under > the top-level media type “application”. In order for the first paragraph to be able to stand alone, per formal IETF requirements -- that paragraph is circulated as a description of the intended effort -- I suggest moving some text to be its last sentence: This working group will create an “archive” top-level media type. > > We create top-level media types only rarely, only with Standards > Track RFCs, and only when one or more media types get special (or > common, in the case of more than one) handling that does not fit > under an existing top-level media type. RFC6838 defines this > process. > > This working group will create an “archive” top-level media type in a > Standards Track document, using draft-seantek-kerwin-arcmedia-type as Replace this sentence with: The working group will use draft-seantek-kerwin-arcmedia-type as initial input. (It doesn't help the charter to cite intended status.) > its initial input. It will specify rules for registering subtypes > under that new top-level type. All of the usual things will be > considered, including type suffixes, fragment identifiers, and > internationalization. Replace sentence with: The rules will at least include consideration of type suffixes, fragment identifiers, and internationalization. > Either in that same document or in a second one, it will produce an > initial set of registrations under the new top-level media type. > > The main document will include an Implementation Status section, > described by RFC6982, to record known projects that will either > produce or consume content using the new media type. If by the first > milestone there appears to be no implementations of the new media > type expected, the working group will fold having produced no RFCs. > > No other work is in scope for this working group. > > Milestones: - June 2015: Base document - December 2015: Registrations > document (if separate) d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [arcmedia] Fwd: Proposed charter for arcmedia Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Stian Soiland-Reyes
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Stian Soiland-Reyes
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Graham Klyne
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Mark Nottingham
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Dave Crocker
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Larry Masinter
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Matthew Kerwin
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Dave Crocker
- Re: [arcmedia] FW: [apps-discuss] Proposed charte… Graham Klyne
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Graham Klyne
- Re: [arcmedia] FW: [apps-discuss] Proposed charte… Stian Soiland-Reyes
- Re: [arcmedia] FW: [apps-discuss] Proposed charte… Graham Klyne
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Sean Leonard
- Re: [arcmedia] FW: [apps-discuss] Proposed charte… Sean Leonard
- Re: [arcmedia] FW: [apps-discuss] Proposed charte… Graham Klyne
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Larry Masinter
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Sean Leonard
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Sean Leonard
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Sean Leonard
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Sean Leonard
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Murray S. Kucherawy
- Re: [arcmedia] [apps-discuss] Proposed charter fo… Larry Masinter