Re: [Ace] [core] New Version of draft-fossati-core-multipart-ct-04.txt

Peter van der Stok <> Tue, 05 June 2018 15:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 64DB51310F3; Tue, 5 Jun 2018 08:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YGQ8rOem7Q7M; Tue, 5 Jun 2018 08:25:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AEE3E1310F2; Tue, 5 Jun 2018 08:25:42 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 705FB181D0286; Tue, 5 Jun 2018 15:25:41 +0000 (UTC)
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 2, -10, 0, , d41d8cd98f00b204,, :::::, RULES_HIT:2:41:72:152:355:379:582:599:800:962:967:973:983:988:989:1152:1189:1208:1212:1221:1260:1313:1314:1345:1431:1436:1437:1516:1517:1518:1535:1575:1588:1589:1592:1594:1606:1730:1776:1792:2068:2069:2198:2199:2525:2528:2559:2568:2570:2635:2682:2685:2691:2693:2703:2741:2827:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3354:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4120:4250:4321:4605:4860:5007:6117:6119:6261:7875:7903:8603:8957:9010:9025:9163:9177:10004:11658:12379:12740:13139:13161:13229, 0, RBL:error, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:26, LUA_SUMMARY:none
X-HE-Tag: wax62_3160f9a61ed45
X-Filterd-Recvd-Size: 9608
Received: from (imap-ext []) (Authenticated sender: by (Postfix) with ESMTPA; Tue, 5 Jun 2018 15:25:39 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_1c965083b32967a55b0041c0a7f18ad2"
Date: Tue, 05 Jun 2018 17:25:38 +0200
From: Peter van der Stok <>
To: Carsten Bormann <>
Cc: core <>, ace <>
Organization: vanderstok consultancy
In-Reply-To: <>
References: <> <>
Message-ID: <>
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: []
Archived-At: <>
Subject: Re: [Ace] [core] New Version of draft-fossati-core-multipart-ct-04.txt
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Jun 2018 15:25:45 -0000

Hi Carsten et al.

I have looked at the multipart draft, and I am happy to see that the
CBOR array is maintained as proposed in est-coaps.
So now we have two drafts that both propose an almost identical new
media type.

The choice will be determined by the delay needed to (pre-)register the
new media type.
Will anyone start doing that for the multipart draft within a
foreseeable delay.
If not, I am happy to pre-register the new media type as specified in
coaps-est to avoid delaying est-coaps.

Looking forward to your reaction,

many thanks for your trouble to create an indenpendent draft.

Carsten Bormann schreef op 2018-06-05 16:55:

> In, Klaus has proposed to introduce a media type for efficiently combining multiple representations, along with the Content-Format numbers of their media types, into a single representation.
> I believe we have needed such a media type in other places, so I have extracted the content of that PR, and revved draft-fossati-core-multipart-ct (of 2013 vintage) with that.  This would give us a media type multipart/core for general use.  (Thanks are due to Klaus and Thomas for helping me with this little exercise.)
> CoAP-EST is due to be finished very soon, and extracting this media type from the CoAP-EST draft should only be done if we can avoid creating a hazard for CoAP-EST to be delayed by this.
> I don't see such a hazard unless we are having fundamental problems with the approach (but do accept its limited use in the CoAP-EST space).
> So it would be useful to get some quick reactions on whether we can go ahead with this.
> If you don't want to read the draft right now, its technical content is:
> multipart-core = [* multipart-part]
> multipart-part = (type: uint .size 2, part: bytes / null)
> (Where "type" is the content-format identifier.)
> Grüße, Carsten
>> Name:        draft-fossati-core-multipart-ct
>> Revision:    04
>> Title:        Multipart Content-Format for CoAP
>> Document date:    2018-06-05
>> Group:        Individual Submission
>> Pages:        5
>> URL:  
>> Status:
>> Htmlized:
>> Htmlized:
>> Diff: 
>> Abstract:
>> This memo defines multipart/core, an application-independent media-
>> type that can be used to combine (even recursively) several different
>> media types into a single CoAP message-body with minimal framing
>> overhead, along with a CoAP Content-Format identifier.
> _______________________________________________
> core mailing list