[arcmedia] Spencer Dawkins' No Objection on charter-ietf-arcmedia-00-00: (with COMMENT)

"Spencer Dawkins" <spencerdawkins.ietf@gmail.com> Tue, 13 January 2015 22:42 UTC

Return-Path: <spencerdawkins.ietf@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 8BE831B2AE6; Tue, 13 Jan 2015 14:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=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 PiC6Z5yxbnxO; Tue, 13 Jan 2015 14:42:22 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CCB7E1B2A96; Tue, 13 Jan 2015 14:41:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150113224130.4724.29830.idtracker@ietfa.amsl.com>
Date: Tue, 13 Jan 2015 14:41:30 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcmedia/Pv1KUT1Ohh_GxBd6bwxfE8wguSU>
X-Mailman-Approved-At: Tue, 13 Jan 2015 15:03:37 -0800
Cc: arcmedia@ietf.org
Subject: [arcmedia] Spencer Dawkins' No Objection on charter-ietf-arcmedia-00-00: (with COMMENT)
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: Tue, 13 Jan 2015 22:42:27 -0000

Spencer Dawkins has entered the following ballot position for
charter-ietf-arcmedia-00-00: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/charter-ietf-arcmedia/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Just a few nits:

In this text:

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.

<< I found myself wondering if archive met these criteria. I guess it
does, and I guess that the RFC6838 process will be used, but I'm just
guessing both of those. If the charter said that more plainly, I'd wonder
less. >>

In these two paragraphs:

The working group will use draft-seantek-kerwin-arcmedia-type as its
initial input.  It 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.

<< I'm guessing "that same document" is
draft-seantek-kerwin-arcmedia-type, but "The W3C TAG work on packaging
and archives" is the closest possibility. Maybe this could be clearer?
>>

In this text: 

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.

<< Perhaps "the working group will conclude"? I know what you mean, but
"fold" may not be as obvious for ESL types. >>