Re: [core] CoAP Content format encoding for structures syntax and format parameters

Christian Groves <Christian.Groves@nteczone.com> Fri, 26 August 2016 06:12 UTC

Return-Path: <Christian.Groves@nteczone.com>
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 C1B7412D17E for <core@ietfa.amsl.com>; Thu, 25 Aug 2016 23:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=nteczone.com
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 FPa1pLjT7jDI for <core@ietfa.amsl.com>; Thu, 25 Aug 2016 23:12:17 -0700 (PDT)
Received: from msh03.myshophosting.com (msh03.myshophosting.com [101.0.109.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 669F312D127 for <core@ietf.org>; Thu, 25 Aug 2016 23:12:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nteczone.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=RFTUIknjPjKKIef1cF2/iJgCiNJXOZTBPnFI/bRILp8=; b=JK7qbt0bXjV2UNX1tSgbyhf8qr pzv5IIlYcyENf71g084I17yfPM2158aBkxZ71OaKlC0n8Iy3wcmhfEKmesvGOKd6wl2i4sOnsUH5O tgUYmcGL1T6BOwBMLnIQxTR5PhecGKw5z8Ic3d/Xsv1W924Rszyn5hQXNZzZojUSPFhGoz8AtKXaM XGzoiOyI8jlz2wrfvs4ns5LVUV0JxjeBuWpmrbAHP89e7agUu8xXZQfn1MNraTK8xJWKhPyGhoc95 pRn+afnCbO4VDjLetp+9/+iHFDA7LOpDWgQiYCECjBLqZGM+rQdDXcM1OeIFpY+sTIrAYeuOfmisN H2TbAzXg==;
Received: from ppp118-209-39-238.lns20.mel4.internode.on.net ([118.209.39.238]:52411 helo=[192.168.1.22]) by msh03.myshophosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <Christian.Groves@nteczone.com>) id 1bdANC-000feP-LP for core@ietf.org; Fri, 26 Aug 2016 16:12:14 +1000
To: core@ietf.org
References: <A45C9D5B-6D11-448E-A78A-91DEDA87E454@smartthings.com>
From: Christian Groves <Christian.Groves@nteczone.com>
Message-ID: <16edc592-d071-4c45-da84-b570fdd500a7@nteczone.com>
Date: Fri, 26 Aug 2016 16:12:09 +1000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <A45C9D5B-6D11-448E-A78A-91DEDA87E454@smartthings.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - msh03.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: msh03.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Authenticated-Sender: msh03.myshophosting.com: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ptvwolzAoalzCROXdLzOYpsIR1A>
Subject: Re: [core] CoAP Content format encoding for structures syntax and format parameters
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Aug 2016 06:12:18 -0000

Hello Michael,

The current senml draft requests 6 identifiers for the various 
senml+(encoding) options. Looking at 
https://www.iana.org/assignments/media-types/media-types.xhtml 
registering each structured syntax suffix seems to be the practise.

With regards to the parameters wouldn't the parameters first have to be 
defined by the content-format registration? As senml+json doesn't have 
parameters "version=2" would not be possible. If you wanted to define 
parameters I suppose new link attribute would be needed?

Regards, Christian


On 20/08/2016 8:12 AM, Michael Koster wrote:
> Hi,
>
> What is the curent thought wrt the CoAP content-format encoding for structured syntax media identifiers, like link-format+json, senml+cbor?
>
> Does each combination need to have its own IANA registered code, or is there a scheme for structured identifier codes in CoAP?
>
> Likewise, what is the preferred way to transmit media type parameters, for example with "application/senml+json; version=2" how do we transmit the version=2 part?
>
> Best regards,
>
> Michael
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>