Subject: [core] draft-ietf-core-multipart-ct-02.txt

From: Carsten Bormann <[email-masked]>
Date: Tue, 7 Aug 2018 17:12:48 +0200

We did a minor update:  During the early allocation process, it became clear that we want to allocate the content-format number out of the Expert-Review space, so this mechanism is useful with small nested media-types (possibly even recursively).  We submitted a new version with just this change today.

If you see a problem with going from a two-byte to a one-byte content format number for this pretty widely applicable mechanism, please do shout out now…

Grüße, Carsten

> Name:		draft-ietf-core-multipart-ct
> Revision:	02
> Title:		Multipart Content-Format for CoAP
> Document date:	2018-08-07
> Group:		core
> Pages:		8
> Status:         https://datatracker.ietf.org/doc/draft-ietf-core-multipart-ct/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-core-multipart-ct-02
> Diff:           https://tools.ietf.org/rfcdiff?url2=draft-ietf-core-multipart-ct-02.txt
> 
> Abstract:
>   This memo defines application/multipart-core, an application-
>   independent media-type that can be used to combine representations of
>   several different media types into a single CoAP message-body with
>   minimal framing overhead, each along with a CoAP Content-Format
>   identifier.