IETF Logo Mail Archive

Re: [media-types] (No subject)

John Levine <johnl@taugh.com> Sun, 17 March 2024 16:26 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7A7C14F5FD for <media-types@ietfa.amsl.com>; Sun, 17 Mar 2024 09:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.859
X-Spam-Level:
X-Spam-Status: No, score=-6.859 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="lIvTzHs3"; dkim=pass (2048-bit key) header.d=taugh.com header.b="gf9dQZoy"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hrG46NHbJGBD for <media-types@ietfa.amsl.com>; Sun, 17 Mar 2024 09:26:51 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39DA4C14F5F6 for <media-types@ietf.org>; Sun, 17 Mar 2024 09:26:50 -0700 (PDT)
Received: (qmail 38820 invoked from network); 17 Mar 2024 16:26:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=97a265f719c9.k2403; bh=HMkJLmAWl7ydCzsq9S7GqyXAnA99BA9wzFDIgkJdVjo=; b=lIvTzHs309+OkfwU314evQ9sXeEIOkVyY3a8skmMGUDUBGfIsry+yoM2/fdGNnBHroa9q7YLPVNqJf9H1Ox/DW8XXzrMlyah5DmhM4g2hP131ZvddbhXL6+ZnswBIBnI4ANx/YXBBsE8YK8LQzURG5VxBzLtjhEgVLuD+06I92aRCDemxpVpJB43SVJz6KW5tCmaGR/sSwW8JzcyyixTP2yjR+n5uMUyGYB5WLYerVCm77mny5Nt2sVkGyULXq2XEvRFUF5UIeYeixqaSi3oTnJtUngRTSoNGrPx84KQtkuBqZmicnGWP4jXMuwboSsCBMXcuA29yD0cCOKNYd8UVA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=97a265f719c9.k2403; bh=HMkJLmAWl7ydCzsq9S7GqyXAnA99BA9wzFDIgkJdVjo=; b=gf9dQZoy/anZ/EEFJxWmwu6Q8lA9Pq97zYBJ2vG/yWNsxMpnsIkSlIwyndcsZbtQx/JjQprPgQsbDZST2l/WWRo+aVvzMno20A1lhrbqRQq567/e7wl6AMjEXZ1xmQ94/nUbIl5c0lCC0M1hw5o6FbFFHGKd/Z9wta1Hnk/KBjseOXt/3VbVFbmxdGKDii5fPInr4HOTSAMSYRQyeI0OoqwkVH1BiWNoXuqKRCAzqNJwKW7NAZQLLwSGsFx4VuT6BzCJ8tKBEt4heJlSGwhpvvgsz95sqbRx0BBOt1KwrmEy8YDQANDqYsXTNWYiKwPW4ITvF72o3iOs3gLQ6pvEOg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 17 Mar 2024 16:26:49 -0000
Received: by ary.qy (Postfix, from userid 501) id 0A1C4858A949; Sun, 17 Mar 2024 12:26:48 -0400 (EDT)
Date: Sun, 17 Mar 2024 12:26:48 -0400
Message-Id: <20240317162649.0A1C4858A949@ary.qy>
From: John Levine <johnl@taugh.com>
To: media-types@ietf.org
Cc: cxres+ietf@protonmail.com
In-Reply-To: <42yi_dyePamk208Mbsepf-pFHCB_WS6Md4g3j8xC5PfBVJ10OL5NpW95gSFOt5DOBz-QUKtyd2UxdisvllBGycXnEv71hJud4wE8tihc9q0x@protonmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/si84qgMciQafO9k3Y0_7tEiJFDA>
Subject: Re: [media-types] (No subject)
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2024 16:26:56 -0000

WIt appears that Rahul Gupta  <cxres+ietf@protonmail.com> said:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>Hi Alexey,
>
>Thank you for your comments.
>
>I had been very careful in stating in the draft that if the `content-type` header is follows the pattern defined in RFC2046 ie
>`multipart/something` followed by the "boundary "parameter, it will continue to be processed as before. Only when a "boundary" is not defined
>and "no-boundary" is defined, (ie a `content-type` header that is considered illegal by RFC2046 and when multipart message is not to be
>processed as of today) will the new standard kick-in. Therefore, I do not see how any existing implementation will break. What am I missing?

Multipart is widely used in email messages where you have no idea what
software the recipient is using, much less any control over it. I do
not think it would be a good idea to invent something that is not
backward compatible.

Honestly, if you're worried about performance when generating
structured data on the fly, I'd use CBOR.

R's,
John

v2.23.0 | Report a Bug | By Email