IETF Logo Mail Archive

Re: [media-types] Thoughts on suffixes, single and multiple

Russ Housley <housley@vigilsec.com> Wed, 03 April 2024 19:45 UTC

Return-Path: <housley@vigilsec.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 8CB7FC14F5FB for <media-types@ietfa.amsl.com>; Wed, 3 Apr 2024 12:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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=vigilsec.com
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 aiFzJaJF0VAq for <media-types@ietfa.amsl.com>; Wed, 3 Apr 2024 12:44:58 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 C9F45C14F5FA for <media-types@ietf.org>; Wed, 3 Apr 2024 12:44:58 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 2F80911EF51 for <media-types@ietf.org>; Wed, 3 Apr 2024 15:44:58 -0400 (EDT)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 1828111F259 for <media-types@ietf.org>; Wed, 3 Apr 2024 15:44:58 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Message-Id: <EFA7766E-4944-4000-B0BC-59BE119381B9@vigilsec.com>
Date: Wed, 03 Apr 2024 15:44:47 -0400
To: media-types@ietf.org
X-Mailer: Apple Mail (2.3731.700.6)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:content-type:content-transfer-encoding:mime-version:subject:message-id:date:to; s=pair-202402141609; bh=AUJ1hwNdhVEpbAYh4peRUxf1PnWDL4h6mA+oPtti7GM=; b=YBrX9qwccMrswRyb+XcXMD6KpNoA14P7TmpONFT2FI32uN8D5RWwwG8FT1tg2p4S1vnidUYzphzUKGbhyUjTQrT1ZL5+QwjDYTFxKmuOaKv8CxvQLMuSTyE7lB7bUWnATIJvSzfkIGI/5q4kt8dlDvloISQmfWLdo83/11Bq2RqgJJESDv/d/LEIfmlnkCR+F63bD7pzf1b15evWgW1DaJLZMzJ9arw8cyt71cytsNyU2ZnyJEKpTRg4YYcFhA3dyPkwGj2G6KMFGrGS6ww5XW1QU5GlskB62FCcmB1Cdu0Af04vaM50sV5Z+tDqQC1Mbw7ZsOFdkCN5qCa/nliuxA==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/mW7jx0ndkpniBm77H1D8NKGxX9w>
Subject: Re: [media-types] Thoughts on suffixes, single and multiple
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: Wed, 03 Apr 2024 19:45:02 -0000

I engaged with this mail list a very long time ago about multiple suffixes.  (See https://mailarchive.ietf.org/arch/msg/media-types/cQpM6z8nz-PACQ2GkujVbYOH3r0/.)  At the time, I was working on the document that became RFC 9399.

Section 7 talks about the various formats that an image might appear.  At the time, we were trying to decide what media type to use for a compressed SVG image.  The choices were image/svg+xml+gzip and image/svg+xml-compressed.

As you can see in Section 7, we went with image/svg+xml+gzip.

I hope the final resolution of this thread leads to a outcome that allows image/svg+xml+gzip to appear in the IANA registry.

Russ

v2.23.0 | Report a Bug | By Email