[core] CoAP Content format encoding for structures syntax and format parameters
Michael Koster <michael.koster@smartthings.com> Fri, 19 August 2016 22:12 UTC
Return-Path: <michael.koster@smartthings.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 E8AEB12D0B0 for <core@ietfa.amsl.com>; Fri, 19 Aug 2016 15:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level:
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smartthings-com.20150623.gappssmtp.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 0jZIWcgQLwYe for <core@ietfa.amsl.com>; Fri, 19 Aug 2016 15:12:24 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43E9912D096 for <core@ietf.org>; Fri, 19 Aug 2016 15:12:24 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id ti13so19671347pac.0 for <core@ietf.org>; Fri, 19 Aug 2016 15:12:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smartthings-com.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=RSk6yPxHco9/K5MSaqTbQtPPAqMjg6AELpc+eglnOOs=; b=FN/Bd53NERNGNLeY9APSLMlvZgkT5uZJP1rtu+mh6NT8xyop/AfV+JN8mA1L7kO3jG 05SUe9gHoTheUxOW6wmp+4ZUCOyUvm1f0GJgNV/27iDJuocKDv85MAcgd31UfIytUfUP AP1egwErYGDUxgv+oCAI6ASCtCCL9P78G9/hECCXK8oxz6fiAr+4tbmFaMpb2sEROFPp NXCyaTlCLcPun6W0QByerDRKAgDP59rUgHc6X0x+MhMzzOFxhU9gDz+4PoJIGG3Fk6ei CUnBakDNasjMI2t2J3hMzWgQD/9O0QYsBZUd1cNMWa8h6x9z72xrHD5IydliQwFJtOAE 00hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=RSk6yPxHco9/K5MSaqTbQtPPAqMjg6AELpc+eglnOOs=; b=Kn14YRMmm2sy6RSjyy5X44Let4Xm8bPE40CWnG+45fv3VU42c7kc0IdNsajuKUDOC6 LSsBu+DCFtvDvyppOdK3qBhjhxIel92Rop9EsoW1ff1RukX1vGs3lp3Tjp3w8W535aoB Cs/BeBFrnjHKQVjwS9ZWVFB0cr+Jpj0/yCbW3If0QqNFV5nHJ4W1pn+rSQb5skOmNmy+ 7rvXdBfIL7D8p8fAzvWeCADL9OtIXa1dYhYoIra2m4PYMOVZ2j74uxT4ioWAgKicwx+3 Qa3wBNnBAFCzsGbaDI01GWoPDxX04baaHtmkvtG4Jd+mb2tPeFiCZwBaeGYf7hgVZ7E8 LyKw==
X-Gm-Message-State: AEkooutRWx4zySnsiTX5Y4Oy1eXSd4dmFHQkG2sfSbcrFUiSySlMExHBSlSvyVtMI1Yam7MX
X-Received: by 10.66.5.72 with SMTP id q8mr17844496paq.38.1471644743514; Fri, 19 Aug 2016 15:12:23 -0700 (PDT)
Received: from [172.28.33.5] ([162.246.216.202]) by smtp.gmail.com with ESMTPSA id 81sm8799424pfm.90.2016.08.19.15.12.22 for <core@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 19 Aug 2016 15:12:22 -0700 (PDT)
From: Michael Koster <michael.koster@smartthings.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <A45C9D5B-6D11-448E-A78A-91DEDA87E454@smartthings.com>
Date: Fri, 19 Aug 2016 15:12:20 -0700
To: core <core@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/T94CmuR0xTX6_Z0EUxsQ5j_tYD0>
Subject: [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, 19 Aug 2016 22:12:26 -0000
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] CoAP Content format encoding for structure… Michael Koster
- Re: [core] CoAP Content format encoding for struc… Christian Groves