[core] application/senml+json in coap content format
chrysn <chrysn@fsfe.org> Thu, 31 January 2013 17:22 UTC
Return-Path: <chrysn@fsfe.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D2A21F8414 for <core@ietfa.amsl.com>; Thu, 31 Jan 2013 09:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.164
X-Spam-Level:
X-Spam-Status: No, score=0.164 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_AT=0.745, J_CHICKENPOX_43=0.6, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTA1B7u7lQxr for <core@ietfa.amsl.com>; Thu, 31 Jan 2013 09:22:44 -0800 (PST)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::2]) by ietfa.amsl.com (Postfix) with ESMTP id 49D7721F84FC for <core@ietf.org>; Thu, 31 Jan 2013 09:22:42 -0800 (PST)
Received: from mail.amsuess.com (vie-188-118-253-253.dsl.sil.at [188.118.253.253]) by prometheus.amsuess.com (Postfix) with ESMTPS id 22EC342AFB for <core@ietf.org>; Thu, 31 Jan 2013 18:22:38 +0100 (CET)
Received: from hephaistos.amsuess.com (poseidon-stable [10.13.14.225]) by mail.amsuess.com (Postfix) with SMTP id EA8894C138 for <core@ietf.org>; Thu, 31 Jan 2013 18:22:36 +0100 (CET)
Received: (nullmailer pid 3336 invoked by uid 1000); Thu, 31 Jan 2013 17:06:07 -0000
Date: Thu, 31 Jan 2013 18:06:07 +0100
From: chrysn <chrysn@fsfe.org>
To: core@ietf.org
Message-ID: <20130131170606.GA14325@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [core] application/senml+json in coap content format
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 17:22:45 -0000
hello core people, as of experimenting with coap (especially core-interfaces), i'd like to transfer sensor data as application/senml+json. however, i didn't find any attempt to register that mime type at the content-format registry set up in draft-ietf-core-coap-13 -- even though extensive use thereof is made in the examples in draft-shelby-core-interfaces-03. * is there a type in use even though it's not yet published? * if not, what should i use until one gets allocated? * which document do i need to watch for a future allocation? (i'd assume draft-jennings-senml-10) * (being new here,) is this list the right place for such questions? * researching current use, i found a glitch in draft-shelby-core-interfaces-03 section 5.8 -- given what the response looks like, the answer to the GET request should be typed application/link-format. are there better places to report such things than here? best regards chrysn -- A beginning is the time for taking the most delicate care that the balances are correct. -- Princess Irulan, Manual of Muad'Dib