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

Carsten Bormann <cabo@tzi.org> Tue, 07 August 2018 15:12 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 6B790130E54 for <core@ietfa.amsl.com>; Tue, 7 Aug 2018 08:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] 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 B-I04N9HkK7u for <core@ietfa.amsl.com>; Tue, 7 Aug 2018 08:12:52 -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 8F29B130E47 for <core@ietf.org>; Tue, 7 Aug 2018 08:12:52 -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 w77FCnAC019283 for <core@ietf.org>; Tue, 7 Aug 2018 17:12:49 +0200 (CEST)
Received: from eduroam-pool6-0443.wlan.uni-bremen.de (eduroam-pool6-0443.wlan.uni-bremen.de [134.102.25.187]) (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 41lJ0x0lcvzDX1x; Tue, 7 Aug 2018 17:12:49 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <153365440394.21495.6835684034854362898.idtracker@ietfa.amsl.com>
Date: Tue, 07 Aug 2018 17:12:48 +0200
X-Mao-Original-Outgoing-Id: 555347566.202493-d457cd177e636456040f6fea2bcb81e6
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD7A29E9-1A70-450B-BD13-FFEC52E1A4E5@tzi.org>
References: <153365440394.21495.6835684034854362898.idtracker@ietfa.amsl.com>
To: Core <core@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/jUwOWJfXd-9moJT0EpUjCLm68Z4>
Subject: [core] draft-ietf-core-multipart-ct-02.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 07 Aug 2018 15:12:55 -0000

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.