IETF Logo Mail Archive

Re: [core] multipart/core

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 06 June 2018 14:44 UTC

Return-Path: <alexey.melnikov@isode.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 3C24D130F4D for <core@ietfa.amsl.com>; Wed, 6 Jun 2018 07:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 4Mri5DjVyxEZ for <core@ietfa.amsl.com>; Wed, 6 Jun 2018 07:44:20 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 50474130DCA for <core@ietf.org>; Wed, 6 Jun 2018 07:44:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1528296259; d=isode.com; s=june2016; i=@isode.com; bh=lzeW+wapTFRkzVRNH4r/6Avj7fGdxohhrfPX1Oe93dY=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=JkmghiUJ9UX+brVj86LiCzxTVx8TtNf0TrSFI+X2mrFy3TgFm45TeqRLiRAUY4GcvvaSjq uINBCHSWucXpVL8fTwX/b/2J4dmJ9MMt37mxxu7DNtGbOZQZsIeNWoRqoNuBbUDCvcUaea yEGsqQHY8C5aRJJriOcXf8ZahM/e9PE=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <WxfzQwBcJh-d@statler.isode.com>; Wed, 6 Jun 2018 15:44:19 +0100
To: Carsten Bormann <cabo@tzi.org>, peter van der Stok <consultancy@vanderstok.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, core <core@ietf.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>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <1677921f-3c58-9aa4-747f-89b6a4297f52@isode.com>
Date: Wed, 06 Jun 2018 15:44:15 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
In-Reply-To: <F61A4181-E14F-4B58-8A0B-FE3EA30C3D09@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/t8Ao58ZUN7zRkKhaN-mO7MzHNpY>
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 14:44:23 -0000

Hi,
I would like to quickly insert AD interrupt.

I had a quick look at draft-fossati-core-multipart-ct-04 and I think the 
proposed definition of multipart/core is syntactically incompatible with 
MIME. Please read sections 5.1 and 5.1.1 of RFC 2046. In particular, all 
multipart media types have to use syntax specified in RFC 2046, which 
this proposal violates.

To be clear, I am not against registering a media type which uses CBOR 
syntax for a collection of other media types. However this media type 
name can't use the "multipart" top level media type. You can either 
define a new "application" media type (e.g. application/multipart-core) 
or you can define a new top level media type different from "multipart". 
The process for definining a new top level media type is slightly more 
comlicated, so you should evaluate whether you want to do this.

Best Regards,
Alexey

v2.23.0 | Report a Bug | By Email