From nobody Fri Jul 12 04:12:57 2019 Return-Path: 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 D41C71202E4 for ; Fri, 12 Jul 2019 04:12:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no 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 I79m345ib3yX for ; Fri, 12 Jul 2019 04:12:54 -0700 (PDT) Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) (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 A762F1200E3 for ; Fri, 12 Jul 2019 04:12:54 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora2.lax.icann.org (Postfix) with ESMTPS id 25FF31E05CC for ; Fri, 12 Jul 2019 11:12:54 +0000 (UTC) Received: from [192.168.217.110] (p548DCE40.dip0.t-ipconnect.de [84.141.206.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 45lVdC144KzyVH; Fri, 12 Jul 2019 13:12:31 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann Date: Fri, 12 Jul 2019 13:12:30 +0200 Cc: draft-ietf-core-senml-etch@ietf.org X-Mao-Original-Outgoing-Id: 584622749.013574-dd1c467516a44fa8048e53bcc934cd47 Content-Transfer-Encoding: quoted-printable Message-Id: To: media-types@iana.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [media-types] Media-type registrations for senml-etch+json and senml-etch+cbor X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2019 11:12:56 -0000 =C2=BBThe Sensor Measurement Lists (SenML) media type and data model can be used to send collections of resources, such as batches of sensor data or configuration parameters. The existing media types (defined in RFC 8428) are useful for the traditional operations GET, PUT, POST. The CoAP iPATCH, PATCH, and FETCH methods enable accessing and updating parts of a resource or multiple resources with one request. For using these methods to access and operate on resources represented with the SenML data model, the present document defines variants of the SenML media types, for JSON and CBOR representations only.=C2=AB Please review the media-type registrations as proposed in=20 draft-ietf-core-senml-etch-04, copied below (RFC-AAAA is the=20 RFC-to-be from that). Gr=C3=BC=C3=9Fe, Carsten 5.2. senml-etch+json Media Type Type name: application Subtype name: senml-etch+json Required parameters: none Optional parameters: none Encoding considerations: Must be encoded as using a subset of the encoding allowed in [RFC8259]. This simplifies implementation of a very simple system and does not impose any significant limitations as all this data is meant for machine to machine communications and is not meant to be human readable. Security considerations: See Section 4 of RFC-AAAA. Keranen & Mohajer Expires January 9, 2020 [Page 6] Internet-Draft FETCH & PATCH with SenML July 2019 Interoperability considerations: Applications MUST ignore any key value pairs that they do not understand unless the key ends with the '_' character in which case an error MUST be generated. This allows backwards compatible extensions to this specification. Published specification: RFC-AAAA Applications that use this media type: Applications that use the SenML media type for resource representation. Fragment identifier considerations: N/A Additional information: Magic number(s): none File extension(s): senml-etchj Windows Clipboard Name: "SenML FETCH/PATCH format" Macintosh file type code(s): none Macintosh Universal Type Identifier code: org.ietf.senml-etch-json conforms to public.text Person & email address to contact for further information: Ari Keranen ari.keranen@ericsson.com Intended usage: COMMON Restrictions on usage: None Author: Ari Keranen ari.keranen@ericsson.com Change controller: IESG 5.3. senml-etch+cbor Media Type Type name: application Subtype name: senml-etch+cbor Required parameters: none Optional parameters: none Encoding considerations: Must be encoded as using [RFC7049]. Keranen & Mohajer Expires January 9, 2020 [Page 7] Internet-Draft FETCH & PATCH with SenML July 2019 Security considerations: See Section 4 of RFC-AAAA. Interoperability considerations: Applications MUST ignore any key value pairs that they do not understand unless the key ends with the '_' character in which case an error MUST be generated. This allows backwards compatible extensions to this specification. Published specification: RFC-AAAA Applications that use this media type: Applications that use the SenML media type for resource representation. Fragment identifier considerations: N/A Additional information: Magic number(s): none File extension(s): senml-etchc Macintosh file type code(s): none Macintosh Universal Type Identifier code: org.ietf.senml-etch-cbor conforms to public.data Person & email address to contact for further information: Ari Keranen ari.keranen@ericsson.com Intended usage: COMMON Restrictions on usage: None Author: Ari Keranen ari.keranen@ericsson.com Change controller: IESG From nobody Fri Jul 19 00:15:27 2019 Return-Path: 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 DB046120118 for ; Fri, 19 Jul 2019 00:15:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no 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 maxXboh-qypU for ; Fri, 19 Jul 2019 00:15:24 -0700 (PDT) Received: from lamora.getmail.no (lamora.getmail.no [84.210.184.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13BC31200C1 for ; Fri, 19 Jul 2019 00:15:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id 6C8CE60D83; Fri, 19 Jul 2019 09:15:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at lamora.get.c.bitbit.net Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2F844OHMGw72; Fri, 19 Jul 2019 09:15:09 +0200 (CEST) Received: from hjemme.reinholdtsen.name (cm-84.212.222.24.getinternet.no [84.212.222.24]) by lamora.getmail.no (Postfix) with SMTP id B3DE160D89; Fri, 19 Jul 2019 09:15:09 +0200 (CEST) Received: (nullmailer pid 13656 invoked by uid 10001); Fri, 19 Jul 2019 07:15:10 -0000 From: Petter Reinholdtsen To: media-types@ietf.org In-Reply-To: References: <20181031102655.GI17721@w3.org> Date: Fri, 19 Jul 2019 09:15:10 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Archived-At: Subject: Re: [media-types] Mime type for patch files? X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2019 07:15:26 -0000 [Petter Reinholdtsen] > I do not understand the way forward from here. Can someone who know the > process bring some clarity? Who make decisions? Who are just making > comments on the sideline? What am I supposed to do now to try to get a > registered mime type for patches? I still do not quite understand what to do next, but assume sending in the IANA form might be a good start. I have started on a pad to draft the answers to the form fields on . Please help me fill in a good set of answers, and I'll try to submit the application by the end of the month. -- Happy hacking Petter Reinholdtsen