[arcmedia] WG Action: Formed 'Archive' Top-Level Media Type (arcmedia)

The IESG <iesg-secretary@ietf.org> Mon, 09 February 2015 20:49 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: arcmedia@ietfa.amsl.com
Delivered-To: arcmedia@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B37071A8777; Mon, 9 Feb 2015 12:49:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9CksCOdfufWY; Mon, 9 Feb 2015 12:49:57 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D651A88DD; Mon, 9 Feb 2015 12:49:55 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150209204955.8127.28748.idtracker@ietfa.amsl.com>
Date: Mon, 09 Feb 2015 12:49:55 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcmedia/hMUiNTSKJ4w2f3dkrHIDP2g8h8I>
X-Mailman-Approved-At: Mon, 09 Feb 2015 13:04:49 -0800
Cc: arcmedia WG <arcmedia@ietf.org>
Subject: [arcmedia] WG Action: Formed 'Archive' Top-Level Media Type (arcmedia)
X-BeenThere: arcmedia@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 09 Feb 2015 20:49:58 -0000

A new IETF working group has been formed in the Applications Area. For
additional information please contact the Area Directors or the WG Chair.

Please note that a co-chair will be added soon.

'Archive' Top-Level Media Type (arcmedia)
Current Status: Proposed WG

  Dave Crocker <dcrocker@bbiw.net>

Assigned Area Director:
  Barry Leiba <barryleiba@computer.org>

Mailing list
  Address: arcmedia@ietf.org
  To Subscribe: http://www.ietf.org/mailman/listinfo/arcmedia
  Archive: http://www.ietf.org/mail-archive/web/arcmedia


Archive formats are used to aggregate multiple files and other data into
a single object, often with data compression and/or confidentiality
protection (encryption).  This working group will create an "archive"
top-level media type.

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".

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.

The working group will use draft-seantek-kerwin-arcmedia-type as its
initial input for a Standards Track document that creates a top-level
media type for archive formats.  The document will specify rules for
registering subtypes under that new top-level type, considering at a
minimum the issue of type suffixes, fragment identifiers, and
internationalization.  The W3C TAG work on packaging and archives,
currently in progress, will also be considered.

Either in that same document or in one of more follow-on documents, 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 conclude, without having produced any RFCs.

No other work is in scope for this working group.

  Jun 2015 - Base document
  Dec 2015 - Registrations document(s) (if separate from the base)