Re: [ietf-types] Registration of media type application/senml+json

Cullen Jennings <fluffy@cisco.com> Sun, 24 October 2010 22:49 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F49E3A6452 for <ietf-types@core3.amsl.com>; Sun, 24 Oct 2010 15:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.219
X-Spam-Level:
X-Spam-Status: No, score=-110.219 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1Hyl+L0mHNz for <ietf-types@core3.amsl.com>; Sun, 24 Oct 2010 15:48:57 -0700 (PDT)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:1::39]) by core3.amsl.com (Postfix) with ESMTP id 685D33A659C for <ietf-types@ietf.org>; Sun, 24 Oct 2010 15:48:56 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id o9OMoI5m024030 for <ietf-types@iana.org>; Sun, 24 Oct 2010 15:50:38 -0700
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADNVxEyrR7Ht/2dsb2JhbAChXnGebJs1hUgEhFSFeYMG
X-IronPort-AV: E=Sophos;i="4.58,233,1286150400"; d="scan'208";a="374082484"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 24 Oct 2010 22:50:18 +0000
Received: from [192.168.4.4] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9OMoGvb013826; Sun, 24 Oct 2010 22:50:16 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="iso-8859-1"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <1q9i969n6lp2esvkjfep4djsilat59bpkj@hive.bjoern.hoehrmann.de>
Date: Sun, 24 Oct 2010 16:50:18 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <40A22527-3C65-4D12-BA78-7719BFD94716@cisco.com>
References: <FFD51C60-9887-47E4-B207-B5BC1AFBD67E@cisco.com> <1q9i969n6lp2esvkjfep4djsilat59bpkj@hive.bjoern.hoehrmann.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
X-Mailer: Apple Mail (2.1081)
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [208.77.188.39]); Sun, 24 Oct 2010 15:50:39 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Registration of media type application/senml+json
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2010 22:49:01 -0000

Thank you very much for the helpful comments. All your points should be fixed in the next revision. 

DIff of the draft from old version is at 
http://svn.resiprocate.org/rep/ietf-drafts/fluffy/draft-jennings-senml.diff.html


On Sep 21, 2010, at 3:52 PM, Bjoern Hoehrmann wrote:

> * Cullen Jennings wrote:
>> Type name:  application
>> 
>>  Subtype name:  senml+json
>> 
>>  Required parameters:  none
>> 
>>  Optional parameters:  none
>> 
>>  Encoding considerations:  Must be encoded as binary.  See additional
>>  constraints in [RFC4627].
> 
> If I understand correctly, this type is just a specialization of the
> application/json type. If so this should simply say the considerations
> are the same as for application/json.

fixed

> 
>>  Interoperability considerations:  JSON allows new fields to be
>>  defined and applications should be able to ignore fields they do not
>>  understand to ensure forward compatibility with extensions to this
>>  specification.
> 
> I think "JSON allows new fields to be defined" is misleading here.
> Perhaps you mean to say: if the name of a name-value pair in an
> object is not recognized, the pair should be ignored?

yep - that's what I was trying to get at - fixed - thanks 


> 
>>  Published specification:  RFC-AAAA
>> 
>>  Applications that use this media type:  N/A
> 
> This should be a general description of the type of application
> that uses the type, for instance, Office applications, Multimedia
> applications, Cartography applications, Web browsers, ...

fixed 

> 
>>  Additional information:
>> 
>>  Magic number(s):  none
>> 
>>  File extension(s):  senml
>> 
>>  Macintosh file type code(s):  none
>> 
>>  Person & email address to contact for further information:  Cullen
>>  Jennings <c.jennings@ieee.org>
>> 
>>  Intended usage:  COMMON
>> 
>>  Restrictions on usage:  None
>> 
>>  Author:  Cullen Jennings <c.jennings@ieee.org>
>> 
>>  Change controller:  
> 
> As this is a registration in the standards tree through IETF consensus,
> this should say The IETF or The IESG; I forgot which is more popular.

fixed

> -- 
> 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/