From iana-shared@icann.org Mon Apr 1 17:06:25 2024 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 7EBC4C14F6E4 for ; Mon, 1 Apr 2024 17:06:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.924 X-Spam-Level: X-Spam-Status: No, score=-2.924 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jh8KWrNcB6Z8 for ; Mon, 1 Apr 2024 17:06:21 -0700 (PDT) Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A10F0C14F6AC for ; Mon, 1 Apr 2024 17:06:21 -0700 (PDT) Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 4A5FBE1BD9; Tue, 2 Apr 2024 00:06:21 +0000 (UTC) Received: by request6.lax.icann.org (Postfix, from userid 48) id 405FB4B078; Tue, 2 Apr 2024 00:06:21 +0000 (UTC) RT-Owner: amanda.baber From: "Amanda Baber via RT" Reply-To: iana-mime-comment@iana.org In-Reply-To: References: Message-ID: X-RT-Loop-Prevention: IANA X-RT-Ticket: IANA #1360120 X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/) X-RT-Originator: amanda.baber@icann.org CC: media-types@ietf.org, alexey.melnikov@isode.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-RT-Original-Encoding: utf-8 Precedence: bulk Date: Tue, 02 Apr 2024 00:06:21 +0000 MIME-Version: 1.0 Archived-At: Subject: [media-types] [IANA #1360120] application/vnd.msgpack registration request X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.39 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: Tue, 02 Apr 2024 00:06:25 -0000 Hi Alexey, Sending a reminder for this response from March 25th. thanks, Amanda On Mon Mar 25 19:21:46 2024, amanda.baber wrote: > Hi Alexey, > > We have fragment identifier and change author/change controller > responses from the applicant: > > === > > 1) Fragment identifier +msgpack is considered to be used with other > media types to define encoding like +json does (unless specified > otherwise). So "Fragment identifier considerations" section could be > something like this: > > The syntax and semantics of fragment identifiers specified for > +msgpack > should be as specified for "application/vnd.msgpack" > > 2) I'm a contributor of MessagePack project, who wanted to resolve the > issue of widespread use of deprecated media types. As the original > MessagePack specification author Sadayuki Furuhashi is inactive for a > while, I don't want to bother him by publishing his contacts. I would > like to include them without that if it's appropriate. > > === > > thanks, > Amanda > > On Sun Mar 17 01:42:29 2024, alexey.melnikov@isode.com wrote: > > Hi Amanda, > > > > Sorry for the slow response. > > > > This is mostly fine, but I have a small question and a bigger concern > > expressed below. > > > > > > On 01/03/2024 18:14, Amanda Baber via RT wrote: > > > > > Hi Alexey, > > > > > Can you review this registration request by March 15th? > > > > > This was originally submitted as a request for standards-tree > > > registration, but the submitter isn't affiliated with a standards > > > organization and has yet to write an I-D. > > > > > He writes, "I would like to edit the registration template to make > > > it > > > a vendor-tree ('application/vnd.msgpack') registration request, as > > > writing RFC would take some considerable time (but pretty much aim > > > to > > > do that anyway)." > > > > > thanks, > > > Amanda > > > > > === > > > > > Name: Alexander Ivanov > > > > > Email: saiv46.dev+iana@gmail.com > > > > > Media type name: application > > > > > Media subtype name: vnd.msgpack > > > > > Required parameters: N/A. > > > > > Optional parameters: N/A. > > > > > Encoding considerations: binary > > > > > Security considerations: This media type does not enforce a > > > security > > > mechanism, as it does not contain any executable content. The > > > format > > > specification does not provide any encryption or integrity checks, > > > so > > > appropriate mechanisms must be implemented at the application or > > > transport level. The format allows applications to define > > > application-specific types, so security considerations of such > > > extensions cannot be assessed. > > > > > Interoperability considerations: The specification explicitly > > > defines > > > a way to encode information (relying on standards such as IEEE > > > 754), > > > as well as limitations to allow conversion to and from other > > > encodings (such as JSON). This provides interoperability not just > > > between implementations, applications and hardware, but media types > > > as well. > > > > > Published specification: > > > https://github.com/msgpack/msgpack/blob/master/spec.md > > > https://msgpack.org/ > > > > > Applications which use this media: MessagePack has been used to > > > exchange arbitrary data between applications written in various > > > programming languages and environments, replacing existing media > > > types such as JSON. > > > > > Fragment identifier considerations: +msgpack > > > > I am not clear on what this means. > > > > > Restrictions on usage: N/A. > > > > > Provisional registration? (standards tree only): No > > > > > Additional information: > > > > > 1. Deprecated alias names for this type: application/x+msgpack > > > 2. Magic number(s): N/A. > > > 3. File extension(s): N/A. > > > 4. Macintosh file type code: N/A. > > > 5. Object Identifiers: N/A. > > > > > General Comments: > > > > > Person to contact for further information: > > > > > 1. Name: Alexander Ivanov > > > 2. Email: saiv46.dev+msgpack@gmail.com > > > > > Intended usage: COMMON > > > > > Author/Change controller: Alexander Ivanov > > > > > > > It is not clear to me how Alexander is related to the project, as the > > original > > creator of MessagePack is a different person. Can you please ask? > > > > Thank you, > > Alexey