IETF Logo Mail Archive

Re: [core] multipart/core

Klaus Hartke <hartke@projectcool.de> Wed, 06 June 2018 18:52 UTC

Return-Path: <hartke@projectcool.de>
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 8B3F312F1A2 for <core@ietfa.amsl.com>; Wed, 6 Jun 2018 11:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001] autolearn=no 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 md5L4g1rk3bh for <core@ietfa.amsl.com>; Wed, 6 Jun 2018 11:52:12 -0700 (PDT)
Received: from wp382.webpack.hosteurope.de (wp382.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8597::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95032130FAC for <core@ietf.org>; Wed, 6 Jun 2018 11:52:12 -0700 (PDT)
Received: from mail-io0-f182.google.com ([209.85.223.182]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1fQdXV-0006Cd-VC; Wed, 06 Jun 2018 20:52:10 +0200
Received: by mail-io0-f182.google.com with SMTP id u4-v6so8853449iof.2 for <core@ietf.org>; Wed, 06 Jun 2018 11:52:09 -0700 (PDT)
X-Gm-Message-State: APt69E2RAgP0gIV3YFvmmCnymRDfL++AAWRvywhV6peK+aA86/pdfgb5 ocEPjnDPCcj0teA1Vjdb0zgBpRkn2ZjnNTIJRdA=
X-Google-Smtp-Source: ADUXVKLQEvOOCqsUqjdIx7VS+Ij/eCnn2yDA0GFX6qEHsTaUbN9+wE3Y49ry4/18VSbjIvyz1TDxJJ3SyQvy7eSvt8U=
X-Received: by 2002:a6b:c6c9:: with SMTP id w192-v6mr3975598iof.131.1528311128707; Wed, 06 Jun 2018 11:52:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:1202:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 11:51:27 -0700 (PDT)
In-Reply-To: <2F2ED8C8-DE45-4187-98C9-3DF56F3C2081@tzi.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> <1677921f-3c58-9aa4-747f-89b6a4297f52@isode.com> <C0D4D7C5-99B7-4225-9D48-52A34ABFAFC0@tzi.org> <24375.1528307244@localhost> <2F2ED8C8-DE45-4187-98C9-3DF56F3C2081@tzi.org>
From: Klaus Hartke <hartke@projectcool.de>
Date: Wed, 06 Jun 2018 20:51:27 +0200
X-Gmail-Original-Message-ID: <CAAzbHvb-E5EVPc1sC-9zFXe_2-i5SfsfQFoikU4f7K1rg6McmA@mail.gmail.com>
Message-ID: <CAAzbHvb-E5EVPc1sC-9zFXe_2-i5SfsfQFoikU4f7K1rg6McmA@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, core <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1528311132; de78ea0c;
X-HE-SMSGID: 1fQdXV-0006Cd-VC
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/YLw8qqmwHIpy7-6wbQOLcI5d3KI>
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 18:52:22 -0000

Carsten Bormann wrote:
> multipart-core = [* multipart-part]
> multipart-part = (type: uint .size 2 / text, part: bytes / null)
>
> Where “text” is a media type string (possibly including parameters).  Does this have a use case we care about?)

For evolvability, we should add rules for processing parts that look
invalid at the moment. I can imagine the need for other representation
metadata in addition to the content format in the future, so there
might be a map in place of the uint. I wouldn't want to bloat the
format right now, though. Let's keep it small and focused, and allow
for evolving it later should the need arise.

Klaus

v2.23.0 | Report a Bug | By Email