[core] draft-ietf-core-multipart-ct

Jim Schaad <ietf@augustcellars.com> Tue, 12 February 2019 17:28 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DDC22127287; Tue, 12 Feb 2019 09:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.794
X-Spam-Status: No, score=-0.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id VAzLQazG9-ad; Tue, 12 Feb 2019 09:28:27 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE0E3128B33; Tue, 12 Feb 2019 09:28:23 -0800 (PST)
Received: from Jude ( by mail2.augustcellars.com ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 12 Feb 2019 09:27:59 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: <draft-ietf-core-multipart-ct@ietf.org>
CC: <core@ietf.org>
Date: Tue, 12 Feb 2019 09:27:54 -0800
Message-ID: <000901d4c2f8$4b69a640$e23cf2c0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdTC96VDrOIHYM79QVa0aA7suYbQ+w==
Content-Language: en-us
X-Originating-IP: []
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/v9avvZSRrIRkJA_hZ3dCZC5hEQ0>
Subject: [core] draft-ietf-core-multipart-ct
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Feb 2019 17:28:28 -0000

An interesting question has come up with respect to this content type in the
ACE Working group.

Is there a way to indicate the different content types that one can deal
with inside of this content type.   One can have an ACCEPT option of types
A, B,  C and multipart.  However, there is no way to say which types one is
going to accept in the multipart.  The multipart could return content types
of D, E, F, and G.  However the combination of all 4 may not be what is
returned but instead a combination of two of them.  Thus the client could
understand D and E or D and F but not F and G.

If you say ACCEPT 62, do you accept any combination of nested content types?
Should something about this be placed into the draft?

Also I note that this draft is currently expired and needs to be reposted.