Re: [core] multipart/core

Carsten Bormann <cabo@tzi.org> Wed, 06 June 2018 18:36 UTC

Return-Path: <cabo@tzi.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 81399129619 for <core@ietfa.amsl.com>; Wed, 6 Jun 2018 11:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 bjT3sU9dZJ6w for <core@ietfa.amsl.com>; Wed, 6 Jun 2018 11:36:09 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 BF7A6128CF3 for <core@ietf.org>; Wed, 6 Jun 2018 11:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w56Ia3EI025034; Wed, 6 Jun 2018 20:36:04 +0200 (CEST)
Received: from [172.18.144.189] (unknown [46.183.103.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 411HS31RmqzDXPq; Wed, 6 Jun 2018 20:36:03 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <24375.1528307244@localhost>
Date: Wed, 06 Jun 2018 20:35:59 +0200
Cc: core <core@ietf.org>
X-Mao-Original-Outgoing-Id: 550002957.188701-250c4a5aafab067888388678fd0a25c0
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F2ED8C8-DE45-4187-98C9-3DF56F3C2081@tzi.org>
References: <ba113ac028c50ee08625d508a89bb169@bbhmail.nl> <CAAzbHvYRgHsSOMgYSxvQOsbZVjnCO+h2r=2LV4vS5a2yJ1s=bA@mail.gmail.com> <20273.1527881373@localhost> <CAAzbHvagy43fX2VDOrG2MzFzfV1-bsE+b7t4GkkU=1wRiiGiJA@mail.gmail.com> <5727.1528220965@localhost> <4AEB441B-CCE5-49B7-8F42-4D0BC8381BA3@ericsson.com> <b0e5e09f1aeff2f553c244013486fbab@bbhmail.nl> <F61A4181-E14F-4B58-8A0B-FE3EA30C3D09@tzi.org> <1677921f-3c58-9aa4-747f-89b6a4297f52@isode.com> <C0D4D7C5-99B7-4225-9D48-52A34ABFAFC0@tzi.org> <24375.1528307244@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/J5Cq6ysT5QDkFosng1xmtMkJ36A>
Subject: Re: [core] multipart/core
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 06 Jun 2018 18:36:12 -0000

Hi Michael,

> On Jun 6, 2018, at 19:47, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> The only other name I might imagine is application/multipart-cbor, as
> slightly more descriptive, but it's a bikeshed question.

There is not that much CBOR there….  But the interesting point about this specific format is not so much the razor-thin CBOR envelope, but that this is using Content-Format identifiers from the CoRE Parameters registry — hence the “core” in the proposed name.  We may want to create similar formats that use string-based media-type names.  (We also could put in string-based media-types as an alternative to Content-Format Identifiers into this media type, though, if we want to reduce the number of such formats:

multipart-core = [* multipart-part]
multipart-part = (type: uint .size 2 / text, part: bytes / null)

Where “text” is a media type string (possibly including parameters).  Does this have a use case we care about?)

Grüße, Carsten