Re: [media-types] Review requested for draft-bormann-cbor-04

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 15 July 2013 16:09 UTC

Return-Path: <derhoermi@gmx.net>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFAD11E8178 for <media-types@ietfa.amsl.com>; Mon, 15 Jul 2013 09:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lq9C81lfUF6T for <media-types@ietfa.amsl.com>; Mon, 15 Jul 2013 09:09:37 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 32F1C11E8175 for <media-types@ietf.org>; Mon, 15 Jul 2013 09:09:37 -0700 (PDT)
Received: from netb.Speedport_W_700V ([84.180.239.219]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0MFPyK-1UtH9F3aeC-00EMmk; Mon, 15 Jul 2013 18:09:34 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John R Levine <johnl@taugh.com>
Date: Mon, 15 Jul 2013 18:09:33 +0200
Message-ID: <8978u81mmkgt0r1k73b0186e7s348er3g5@hive.bjoern.hoehrmann.de>
References: <alpine.BSF.2.00.1307151113100.45887@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1307151113100.45887@joyce.lan>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:GAJb9vsuHy78Pj1H7+cDKTDWIPWjt9+VpL8Kdr0YBSPMBZAoOwu lgh6LlD8KR0qq1DpYTE5RasA9y0GkRNXblAB29DMHO92JMILb9ru+ZNwIAidiMS2adLNriQ mhTiJs3hYTN+ENN5RLNUYmoNd3lF8qzqNBIkxM9rcBytFI/HnBvW+ba4VCSM8H3+yh0cofz Okc6+cWCpJF38w9FO92dw==
Cc: Media Types list <media-types@ietf.org>
Subject: Re: [media-types] Review requested for draft-bormann-cbor-04
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 16:09:42 -0000

* John R Levine wrote:
>draft-bormann-cbor-04 describes a new binary structured data format called 
>Concise Binary Object Representation (CBOR), and proposes a media type for 
>it.  The media type info in the draft is:
>
>7.3.  Media Type ("MIME Type")
>
>    The Internet media type [RFC6838] for CBOR data is application/cbor.
>
>    Type name: application
>
>    Subtype name: cbor
>
>    Required parameters: n/a
>
>    Optional parameters: n/a
>
>    Encoding considerations:  none; CBOR is a binary format

Then it's 'binary', not 'none'.

>    Security considerations:  Same as for the base document

This could use an additional sentence explaining why there is and what
is a "base document" in this context, and why the higher-level format
does not introduce any new security considerations.

>    Applications that use this media type:  None yet, but it is expected
>       that this format will be deployed in many protocols and
>       applications.

This should provide more contextual detail than "many". Is there a
particular kind of application that would use it, like backup and
archival software or 3d modeling applications or Office programs?

>    Additional information:
>      Magic number(s): n/a
>      File extension(s): .cbor
>      Macintosh file type code(s): n/a
>
>    Person & email address to contact for further information:
>      Carsten Bormann
>      cabo@tzi.org

The typical rendering is more like `Carsten Bormann <cabo@tzi.org>`.

>    Author:
>      Carsten Bormann
>      cabo@tzi.org
>
>    Change controller:
>      Carsten Bormann
>      cabo@tzi.org

Making Carsten Bormann the change controller requires some rationale,
including where RFC 6838 allows that, especially considering that the
draft-bormann-cbor-04 document appears to be "Standards Track".
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/